Send Game Currency API Required
Description
Through the request of the original factory API interface, the player role stored value, recharge operation
In the SDK value of third party interface, stored value, page stored value, fill all the stored value prepaid stored value pipeline operation. The basic parameters include the order number (orderId), ID (userId), the amount of money (amount NT), diamond number (gameCurrency), CODE server (serverCode), the current timestamp (timeStamp), MD5 signature (sign).
Domain name from the original factory and our products of negotiation.
The KEY value in the sign signature is provided by the original factory (e.g., 8–32 characters consisting of uppercase and lowercase letters or digits, with no special characters)
Processing Flow
Request URL (Use the get mode, and suggest supporting the post mode) Test server links such as：
http://domain.xxx.com/user/pay?orderId=1616548&userId=3258506&gameCurrency=100&serverCode=ld4&timeStamp=1378456412008&roleId=12045897&sign=1faec808b862af2d5a726f993477529b&proItemId=23432Request Parameters
Precautions
Regarding the issue of transparent transmission parameters, our system does not support it. The main reasons are: SDK (ios or android) In some cases, such as the network, the stored value is abnormal. The next time the SDK enters the stored value interface (or other conditions trigger), it will automatically go to the official server (ios or android) to pick up these abnormal orders for automatic compensation. but the order information may not match with your transparent transmission parameters.**
| parameter description | ||
|---|---|---|
| orderId | Unique order number, need to use the reconciliation | Required |
| userId | User ID | Required |
| proItemId | According to the rules stipulated in the commodity items ID ; | Required |
| gameCurrency | Game currency (e.g. diamond number) ; | Required |
| serverCode | server CODE | Required |
| timeStamp | Time stamp | Required |
| roleId | The role of ID, a service is required when multiple roles | Required |
| channel | Exchange channel: only types (ios, android, third) | Required |
| sign | The signature and encryption rules: ; MD5(orderId+userId+proItemId +gameCurrency+serverCode+Stored value KEY+timeStamp) ; The two sides agreed in advance of the stored value KEY: confidential value consisting of 8–32 uppercase or lowercase letters or digits, with no special characters ; | Required |
Response Result
| Returns the standard JSON format | ||
|---|---|---|
| Success | {"ret":0, "msg": "ok"} | "ret":0 Receive success |
| Failure | {"ret":1001, "msg": "Parameter error"} | ret Not 0 is wrong, Note: if there is a definition of wrong coding instructions, please inform me |
Response JSON Fields
| Parameter description | ||
|---|---|---|
| ret | Return status | Required |
| msg | Return information description | Required |
Error Codes
1001 Parameter error 1002 The user does not exist 1003 Sign error 1004 Repeat the order No. 1008 Account disabled 65535 Server error