ChainUp Open platform

Chinese Version

After the final payment page is assembled as: https://service.xxx.com/platform/pay.html?appKey=xxx&openId=xxx&token=xxx&orderNum=xxx

Step 2: Payment Page

Payment Page

Open Platform Guidelines

Changelog

SDK Description

SDK（RSA）

SDK RSA Description

Country Code

The final login page is stitched together as : https://service.xxx.com/platform/login.html?appKey=xxx&redirectUrl=xxx After successful login with code redirect to redirectUrl

Step 1: Login

OAuth authorization login page (accessed in browser)

It is necessary to package the data in the parameter table into JSON strings and use rsa for parameter encryption and signature as data and sign in the body

Step 2: Get Token

Get token and openId by code

Refresh Token

Step 1: Create Payment Order

Create a payment order

The interface URL is provided by the docking merchant, and the parameter passed in the first step of creating the order: notifyPage After the payment is completed, the payment result will be notified through the URL corresponding to the notifyPage.

Step 3: Notify Page

Payment result callback interface

It is necessary to package the data in the parameter table into JSON strings and use rsa for parameter encryption and signature as data and sign in the body.

Query Payment Order

Merchant Daily Posting Statement

Cancel Pending Orders

This interface is exclusively available for hybrid cloud SaaS + merchants. To use it, the merchant's API must be confirmed via callback. The callback URL is: https://xxxx.xxxx.xxx/nofity/transferToMerchantAuthCheck. Merchants need to provide the callback domain https://xxxx.xxxx.xxx to the platform for configuration. The callback method is fixed as: /nofity/transferToMerchantAuthCheck. After receiving the callback, the merchant must perform signature verification. The verification method is the same as that used for requesting this interface (if the request uses MD5, the callback should also use MD5 rules for verification; if the request uses RSA, the callback should also use RSA for verification).

Payment needs to call back

Deduct the user's assets to the open platform account and call back the merchant API for confirmation

Either the UID or OpenID of the payee must exist, and if both are present, the OpenID takes precedence.

Coin Grants/Refund

Coin Grants / Refund

(openId, userId, mobileNumber, email) One of these four must be provided.

Get User Top-up Records

User Cash Withdrawal Records

Merchant Backstage Coin Gift Record

Other Transfer Record

Broker Share Record

Contract Fee Sharding Record

Contract Fee Inquiry

Contract Broker Role Inquiry

Contract Trial Bonus Distribution Record

Recovery contract bonus

Finance & Mining Pool - Participation Record - Pledge Currency Query

Query Participation Record

Finance & Mining Pools - Participation Records - Participation Records Inquiry

To register a user, you need to provide either an email or a mobile number. If you choose to provide a mobile number, you must also include the country code.

API access instructions

API documentation

Payment Page

Query Parameters

Response