API Integration
Description
The physical card API provides access to the underlying capabilities of the bank.
Merchants need to handle token deposits themselves.
Environment Information
Test Environment: https://test-physicalcard-api.prepaidify.com
Production Environment: https://physicalcard-api.prepaidify.com
Document Description
1. Overview
This document provides explanations for third-party integration interfaces. Target audience: technical developers.
2. Common Interface Parameters
Field Name | Variable Name | Required | Type | Base64 Encoding | Description |
---|---|---|---|---|---|
Partner ID | agentId | Y | string | N | Partner ID assigned by the institution |
Request String | reqData | Y | string | N | Request RSA encrypted data, encoded after encryption with URLEncoder |
Language | language | N | string | N | zh, en |
Signature | signature | Y | string | N | MD5 signature string |
3. Common Interface Response
Field Name | Variable Name | Required | Type | Base64 Encoding | Description |
---|---|---|---|---|---|
Response Code | respCode | Y | string | N | 00: Success, Others: Failure |
Response Description | respMsg | N | string | N | Exists in case of failure |
Request String | respData | N | string | N | Response RSA encrypted data |
4. Interface Invocation Details
Interfaces typically include three request parameters: agentId, reqData, signature.
Signature Generation Rule
Convert the body to a JSON string + md5Key, then encrypt it using MD5.
For example:
repData Generation Rule
Similarly, convert the body to a JSON string, then encrypt it using an RSA public key to obtain an encrypted string, and then base64 encode it.
For example:
Example of Usage
Note that the format should be application/x-www-form-urlencoded instead of application/json.
Response Example
Normally, all interface data needs to be decrypted using an RSA private key when receiving data from the server.
Example of Decryption:
Last updated