ChainUp Open platform

Chinese Version

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

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

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.

Error Code	Description
0	Success
10020	Parameter error
10001	System exception, please contact the administrator
10003	Sliding verification error
10004	Text message delivery failure
10005	Send too often, try again later
10015	Operation failure
10009	SMS verification code or email verification code is incorrect
10010	Google captcha is incorrect
50000	Http request method is not supported, the global interface is application/json call
50001	appKey is illegal
50002	The redirect url does not match the merchant configuration
50003	Permission group does not exist
50004	appKey does not exist
50005	Signature error
50006	The requested resource cannot be empty
50007	Invalid resource request
50008	Invalid item prefix
50009	Request timeout
50010	Illegal request time
50011	Network Error
50012	No permission to access resources
50013	This resource has reached its traffic limit today and is not accessible
50014	This merchant does not support such account payments
60001	The refreshed token is no longer valid
60002	Token is no longer valid
60003	Code has been used, can only be used once
60004	Invalid OPENID
70001	Order does not exist
70002	Order already exists, please do not repeat the order
70003	Order Status Exception
70004	Illegal payment users
70005	Merchant accounts are not available
70006	Insufficient account balance
70007	This currency is not supported
70008	Illegal payment amounts
70009	Types of illegal order scenarios

assetType	Common Asset Types
201	User normal balance
202	User frozen balance
207	Lockup account
208	Storage lockup account
209	Storage account
210	OTC merchant margin account
217	User OTC normal balance
218	User OTC frozen balance
221	Innovation trial zone subscription frozen token account
230	User lockup token account V2

orderStatus	Description
1	To be paid
2	Payment failure
3	Successful payment
0	Closed

orderSceneType	Scenario description `merchant definition`
1001	Sneak Peek
…	…

API access instructions

API documentation

Open Platform Guidelines

POST - Open platform access to domain names

SDK Version

Error Code

Account Type

Order Status

Order Scenario Type

API access instructions

API documentation

​POST - Open platform access to domain names

​SDK Version

​Error Code

​Account Type

​Order Status