Paytend Payout

Paytend Payout API supports the fastest real-time remittance of funds from your Paytend account to more than 90 countries and regions around the world. Funds will be credited in local currency and support multiple currencies, providing you with convenient fund remittance services. This feature allows you to easily batch process international remittances and payments, making payments to partners, suppliers, and globally more convenient and efficient.

Paytend Payout API provides the following main features:

2.1 Global fund remittance

• Global Coverage: Supports remitting funds to more than 90 countries and regions around the world, allowing you to easily handle international remittances.

2.2 Local currency recording

• Local currency deposit: The remitted funds will be deposited in the local currency of the receiving country or region, simplifying the operation process of the payee.

2.3 Multi-currency support

• Multi-currency support: Supports multiple major currencies, allowing you to remit funds in multiple currencies to meet different payment needs.

2.4 Real-time fund remittance

• Real-time fund remittance: Funds will be remitted in the fastest real-time way, ensuring that you can quickly complete payment and remittance, improving the liquidity of funds.

2.5 Support Crypto Currencies export

• Support crytpo remittance: Funds can be remitted directly through crypto, and real-time currency conversion ensures that you can quickly complete payment and remittance, improving the liquidity of funds.

Paytend Payout API is suitable for a variety of usage scenarios, including but not limited to the following:

• International Supplier Payment: Support companies to pay global suppliers to ensure timely performance of contracts.
• Partner Sharing: Used to distribute revenue according to the partner sharing agreement.
• Global Payment: Provides an efficient way for corporation to process cross-border payments, including salary payments, remuneration and bonuses, etc.

Detailed access and integration documentation will be provided on the Paytend official website, including information such as API endpoints, authentication, request examples, and response examples. Customers can access according to the documentation and customize the integration according to their needs.

4.1 Interface communication method

• Communication Method

  Communicate using HTTPS, the message format is JSON

• Character Set

  Messages are uniformly encoded in UTF-8

4.2 Signature verification field description

• bizData: Encrypted by randomly generated AES KEY.
• randomKey: AES KEY is encrypted by Paytend public key.
• signature: The signature source string is composed of all non-empty field contents except the signature field, sorted according to the ASCII code of the message field, and connected with the "&" symbol in the manner of "field name = field value".
  • for example: Send SMS verification code to request data

{
  "randomKey":"qeM/mnvepEv5MFe7n77brQ==",
  "requestId":"20231025102930718",
  "signType":"RSA",
  "bizData":{
    "mobile":"13261402222",
    "type":"1"
  },
  "partnerId":"888666000100260",
  "version":"2.0"
}

The signature source string signature is as follows. The signature source string uses the partner RSA private key signature to generate the signature.

bizData={"mobile":"8613261402222","type":"1"}&partnerId=888666000100260&randomKey=gNx86vc1yttHs8ZWOf7+5g==&requestId=20231025095118321&signType=RSA&version=2.0

• Precautions
  • The signature algorithm of RSA is SHA256withRSA.
  • The maximum encrypted plaintext length of RSA is 117.
  • The maximum decryption ciphertext length of RSA is 128.
  • The signature field in the request data is generated by the Partner RSA private key signature.
  • The signature field in the response data is generated by the Paytend RSA private key signature.
  • randomKey and bizData plain text participate in the signature.
  • For specific implementation, please refer to the Sandbox demo in Support and Contact
  • When decrypting the returned data or verifying the signature, you need to first determine whether the field has a value. Some errors will not result in a signature, such as: The request field type is wrong.

4.3 Main interface calling process:

• Create payee. For all transfer transactions, you need to create a payee first and fill in the payee ID in the payment interface.
• Create payer (optional). For local payment in some countries, this interface supports filling in the initial payer information.
• Payment. Perform a transfer transaction through this interface.
• Query payment result.
• Refund notification. If the payment fails and the funds are returned, it will be notified through this interface.

Data security is crucial in the financial sector. Paytend Payout API uses advanced data encryption and security measures to ensure the protection of fund remittances and transaction information, complying with the security standards of the financial industry.

• Dictionary
• Local payment c2c params
• Sandbox configuration
• Sandbox demo