PayKKa OpenAPI Documentation
    英文(EN)
    • 中文(CN)
    • 英文(EN)
    • Overview
    • Interface rules
    • SDK
    • Communication security
      • Signature Generation & Verification
    • API list
      • Merchant Onboarding
        • Apply for Onboarding
        • Update Onboarding Info
        • Query Onboarding Status
        • Onboarding Notification
      • Risk Assessment
        • Submit Assessment
        • Update Assessment Info
        • Get Assessment Result
        • Assessment Notification
      • VA
        • apply
        • inquiry
        • notification
      • Remittance
        • notification
      • Order
        • create
        • update
        • inquiry
        • supplement
      • Tradesettle
        • apply
        • inquiry
        • notification
      • Balance
        • inquiry
      • Payee
        • create
        • update
        • inquiry
        • notification
      • Forex
        • pre-order
        • confirm
        • inquiry
        • notification
      • Payment
        • apply
        • inquiry
        • notification
      • file service
        • upload
    • appendix
      • Open the collection account code table
      • Product Category
      • Business categories
      • Province and city code
      • Bank code
      • industry
      • new industry
      • Country code

    Interface rules

    Basic information
    All API requests must use HTTPS access endpoints as follows:
    EndpointEnvironmentNotes
    https://open-fat.cb.paykka.comSandbox
    ProductionApply offline
    #Data format
    JSON is used as the request/response body format
    Required headers:
    Note: File upload APIs are exceptions

    Parameter compatibility#

    Request success is independent of parameter order
    Request success is independent of JSON key order
    Do not assume response JSON key order when parsing
    New API versions may:
    Add new parameters or JSON fields
    New API versions will NOT:
    Remove existing required parameters or fields
    Null values in request/response JSON may be omitted
    #Character encoding
    UTF-8 must be used for request/response bodies

    Time format#

    All timestamps must follow ISO 8601
    Timezone must be UTC (suffix "Z")
    Message example:
    {
      "date": "2023-12-04T23:25:59Z"
    }
    The above represents:
    UTC: 2023-12-04 23:25:59
    Beijing Time (UTC+8): 2023-12-05 07:25:59

    Error Handling#

    HTTP Status Codes
    Status codeDescription
    200Request processed successfully
    4xxRequest failed due to client error (invalid format, missing parameters, invalid state, insufficient balance, etc.)
    5xxServer error (network issue, system defect, etc.)

    Error Code & Message#

    When a request fails, the response body includes detailed error information:
    KeyTypeDescription
    ret_codeString(6)Error code
    ret_msgStringError message

    Common Error Codes#

    Error codeDescription
    999999Unknown error (contact support)
    010000Invalid request parameters (format error / missing fields)
    010001Too many requests
    010002Data not found
    010003Invalid data state
    010004Data integrity violation
    010005File size exceeds limit
    010100Unauthorized request (signature verification failed)
    010200Unauthorized request (signature verification failed)
    Modified at 2026-04-17 01:33:23
    Previous
    Overview
    Next
    SDK
    Built with