PayZApp-Gateway
    PayZApp-Gateway
    • Getting started
    • Authentication
    • Callback Description
    • Error Description
    • Deposit
      • Create Invoice
        POST
      • Query Invoice
        GET
      • Invoice Callback
        POST
    • Transfer
      • Unified Transfer
        • Getting Strared
        • India-INR
        • Brazil-BRL
        • Blockchain-USDT
      • Query Transfer
        GET
      • Transfer Callback
        POST
    • UPI
      • Query UTR
        GET
      • UTR Repair
        POST
    • Other
      • Get Balance
        GET

    Callback Description

    INFO
    After completing the payment, the platform will send the relevant payment results to the merchant in the form of data streams. The merchant needs to receive and process these results according to the document specifications and respond accordingly.
    Please note:
    ๐Ÿ’ก
    The same notification may be sent to the merchant system multiple times. The merchant system must be capable of handling duplicate notifications correctly.
    During back-end notification interactions, if the platform receives a response from the merchant that does not comply with the specifications or times out, the platform will consider this notification as failed and will resend it until successful (in cases where the notification repeatedly fails, the platform will make multiple notification attempts at a frequency of 60 seconds each, but the platform does not guarantee that the notification will eventually succeed).
    In cases where the order status is unclear or the payment result notification has not been received, it is advisable for the merchant to proactively contact the platform.
    Special reminders:
    ๐Ÿ’ก
    Merchants must perform signature verification for the contents of payment result notifications and verify whether the returned order amount matches the order amount on the merchant's side. This is to prevent data leaks that may lead to "false notifications" and potential financial losses.
    When handling notifications, first check the status of the corresponding business data to determine whether the notification has already been processed. If it has not been processed, proceed with the handling; if it has been processed, return the result as successful. Before performing status checks and processing of business data, use data locks for concurrent control to avoid data confusion caused by reentrant functions.
    TIP
    Please note that the notification data is in JSON format and is sent via POST request with Content-Type: application/json. Retrieve the parameters in your code accordingly, using common methods for parameter retrieval.
    Java example:
    Get the verification parameters and verify the signature
    Respond to requests
    After receiving the callback notification, please return the reply OK value (both upper and lower case), and then the platform will judge that the merchant has correctly received the response callback. All other fields will be treated as failures. Please pay attention to the spaces and ignore the case. Otherwise, the platform will retry to notify the merchant of the callback.
    ๐Ÿ“Œ
    OK
    Modified atย 2023-09-18 19:22:38
    Previous
    Authentication
    Next
    Error Description
    Built with