🇺🇸
ReelPay Payment
  • REELPAY - FOR MERCHANT
    • What is ReelPay
    • ReelPay API Introduction
    • Contact Us
  • ReelPay - FOR DEVELOPER
    • To Get Started
      • Signature
      • API Specification Common Rules
  • Payment API
    • Hosted Checkout Page Integration
    • Native Checkout Integration
    • API Interface
    • Webhook Notification
  • SDK Instruction
  • Error Code
  • CHANGES
    • Change Record
  • REELPAY POLICY
    • ReelPay Privacy Policy
    • Disclaimer for Purchasers
    • Terms of Use
    • AML/CTF Policy
Powered by GitBook
On this page
  • Step 1: Get Checkout URL
  • Return a Checkout URL
  • Step 2: Configure Webhook to receive payout notification
  • Webhook notification
  • Example
  1. Payment API

Hosted Checkout Page Integration

Users can scan the QR code or copy the address on the hosted checkout page to make the payments.

PreviousPayment APINextNative Checkout Integration

Last updated 7 months ago

We recommend merchants to integrate with ReelPay's hosted checkout interface. You will only need two steps to start accepting crypto payments. When the integration is done. Your server will be able to call the checkout URL API and present ReelPay's hosted checkout page to your users.

Step 1: Get Checkout URL

Return a Checkout URL

POST https://pay.reelpay.com/v1/transactions/entrust

Headers

Name
Type
Description

X-Appid*

String

X-Timestamp*

String

Timestamp in seconds (10-digit). The request is valid for two minutes.

X-Sign*

String

content-type*

String

application/json

Request Body

Name
Type
Description

symbol*

String

Amount should be paid for this order (in USD by default, no more than two digits after the dot)

out_trade_no*

String

Order ID in Merchant's system

name*

String

Name of the product

image

String

The URL address of the product image

amount

String

Product Price

Response

Header

Name
Value
Required
Type
Description

X-Appid

el9q0mzllpjhducy

Y

string

X-Timestamp

1677152490

Y

string

Timestamp in seconds (10-digit). The request is valid for two minutes.

X-Sign

e0b78d93fd702aa31b07d5488cd85b4b7176d01c4ec45fd8bfaef0d1081a5ead

Y

string

content-type

application/json

Y

string

Body

{
    "code": 200,
    "message": "success",
    "data": {
        "url": "https://pay.reelpay.com/b79d2586ef7807d18c20230725183439",
        "time_expire": 1690389279,
        "trade_no": "b79d2586ef7807d18c20230725183439"
    }
}

Parameters

Name
Value
Required
Type
Description

code

200

Integer

message

success

String

data

Object

data.url

String

URL link of payment

data.time_expire

1690389279

Integer

data.trade_no

b79d2586ef7807d18c20230725183439

String

ReelPay Order ID

As a security measure, we will sign the returned data (and according to this only { code: 200 } should be signed, but it's signing all the returned body.). Additionally, it will return Appid, Sign, Timestamp in the header of the response. The signature method hmacSHA256 (body (json string)+timestamp+appKey).

Please use the data with caution if the signature verification fails. It indicates that the data has been tampered with.

Request Body Example

{
    "out_trade_no":"202307250001",
    "symbol":"USD",
    "amount":"100",
    "name":"product name",
    "image":"https://reelpay.com/product.jpg"
}

The body of HTTP is a json string .

Add the content in body of HTTP to the signature. Ensure the body content matches the signature content. As soon as ReelPay receives the request, the body content will be read and the signature will be verified.

SDK Example

import (
    reelpay "github.com/ReelPayment/sdk-go"
)
func main()  {
    transaction := reelpay.Transactions{
        AppID: "eqrbntqbi5uqvkpr",
        AppKey: "XhAlbICW10VJnWGruPL0NSnvb6946JDQ",
    }
    res := transaction.EntrustPay(&reelpay.EntrustPay{
        OutTradeNo: "jSWfrolOTdsadcYuUwkJbdw9IJUBeV",
        Symbol:     "USD",
        Amount:     "1.2",
        Name:       "Product name",
        Image:      "https://reelpay.com/product.jpg",
    })
    fmt.Println(res)
}

Step 2: Configure Webhook to receive payout notification

  • Paid

  • Transaction close

  • Transaction timeout

  • Refunded

  • Chain confirmation failed

Callback Frequency: 5s、15s、30s、3m、10m、20m、30m、30m、30m、60m、3h、3h、3h、6h、6h

Total: 24h3m50s

Callback Form:

Webhook notification

Name
Value
Required
Type
Description

X-Appid

eqrbntqbi5uqvkpr

Y

string

X-Timestamp

1690368283

Y

string

Timestamp in seconds (10-digit). The request is valid for two minutes.

X-Sign

e0c6a719ebc366da0340c1b450026a903a55c86ed5fbe0b586cd73f6be74ade6

Y

string

hmacSHA256 (body (json string)+timestamp+appKey)

X-EventType

Paid

Y

string

```json
{
   "trade_no": "uGHT9KRRvLIl4WW8JAaTWmETf3mz8D60",
   "appid": "eqrbntqbi5uqvkpr",
   "out_trade_no": "202307250001",
   "amount": "1.2",
   "status": "PAID",
   "success_time": 1690369680
 }
```
Name
Type
Description

trade_no

string

ReelPay Order ID

appid

string

Merchant APPID

out_trade_no

string

Merchant Order ID

amount

string

Transaction Amount

status

string

Transaction Status

success_time

string

Transaction Time

Return Appid, Sign, Timestamp in the header of the response. The signature method hmacSHA256 (body (json string)+timestamp+appKey).

Please use the data with caution if the signature verification fails. It indicates that the data has been tampered with.

Merchants sign to ensure information safety. Once the merchant has processed the order, please return "Success" in the body of the HTTP response if the processing has been successful. If the process fails, ReelPay will attempt to send the order again and the Webhook will retry up to 15 times ( Callback Frequency: 5s、15s、30s、3m、10m、20m、30m、30m、30m、60m、3h、3h、3h、6h、6h, Total: 24h3m50s ).

Example

Merchant's unique credential. Find it on the .

hmacSHA256 (body (json string)+timestamp+appKey). .

Merchant's unique credential. Find it on the .

hmacSHA256 (body (json string)+timestamp+appKey). .

Configure Webhook to receive notifications. ReelPay will notify merchant of the final transaction results. You can configure the Webhook URL on the

Transactions will start a request to the callback interface set by the merchant when involving the following :

The callback content is still encrypted.「For more information see the 」

Merchant's unique credential. Find it on the .

Click me to see more
AppManage page
Signature
AppManage page
Signature guide
AppManage page
Signature guide
https://pay.reelpay.com/b79d2586ef7807d18c20230725183439
AppManage page
events
Transaction Status Code
Hosted CheckOut Page
AppManage