UnionMeta Merchant Payment API Documentation
  1. 2. Security & Encryption Rules
UnionMeta Merchant Payment API Documentation
  • 1. Revision History
  • 2. Security & Encryption Rules
    • 2.1 Purposes
    • 2.2 Request Encryption (AES)
    • 2.3 Signature Generation (MD5)
  • 3. API List
  • 4. API
    • 4.1 Payment Result Callback Notification (Online/Dynamic QR)
    • 4.2 Payment Result Callback (Static QR)
    • 4.3 Create Order API (Online Payment)
      POST
    • 4.4 Create Order API (Generate QR)
      POST
    • 4.5 Static QR Code Generate
      POST
    • 4.6 Query Order
      POST
    • 4.7 Merchant wallet Balance
      POST
    • 4.8 Cancel Order
      POST
    • 4.9 Activate/Deactivate Static QR Code
      POST
    • 4.10 Transaction History
      POST
  • Schemas
    • CreateOrderRespData
    • RespDataCreateOrderRespData
    • CreateOrderReqParams
    • ReqParamsCreateOrderReqParams
    • CreateQrOrderRespData
    • RespDataCreateQrOrderRespData
    • CreateQrOrderReqParams
    • ReqParamsCreateQrOrderReqParams
    • GenerateStaticQrRespData
    • RespDataGenerateStaticQrRespData
    • GenerateStaticQrParams
    • ReqParamsGenerateStaticQrParams
    • MapObject
    • QueryOrderRespData
    • RespDataQueryOrderRespData
    • ReqParams
    • QueryOrderReqParams
    • OpenApiReq
    • ReqParamsQueryOrderReqParams
    • MerchantBalanceRespData
    • RespDataMerchantBalanceRespData
    • MerchantBalanceReqParams
    • ReqParamsMerchantBalanceReqParams
    • CancelOrderRespData
    • TransactionHistoryRespData
    • RespDataCancelOrderRespData
    • RespDataTransactionHistoryRespData
    • CancelOrderReqParams
    • TransactionHistoryReqParams
    • ReqParamsCancelOrderReqParams
    • ReqParamsTransactionHistoryReqParams
    • StaticQrStateOptionRespData
    • RespDataStaticQrStateOptionRespData
    • StaticQrStateOptionReqParams
    • ReqParamsStaticQrStateOptionReqParams
  1. 2. Security & Encryption Rules

2.1 Purposes

1.Authentication (matching client’s key with server’s key).
2.Data tamper-proofing (parameters are transmitted in plain text; parameters and the key are encrypted to form a signature for server matching).
Request parameters are AES encrypted for transmission in ciphertext. Requests must carry a signature. The API will process requests only after signature verification passes.
Upon onboarding, the platform will provide you with a Merchant Account and a 32-character Secret Key. This key is divided into two parts:
First 16 characters: Signature Key (signKey).
Last 16 characters: AES Encryption Key (encryptKey).
Modified at 2026-03-02 08:18:51
Previous
2. Security & Encryption Rules
Next
2.2 Request Encryption (AES)