Supefina Payment API
English
English
  • Welcome to Supefina's API documentation
    • Quick Start
    • Signature algorithms
    • Notification callback description
    • Cashier (only for merchants in the e.commerce industry)
      • 🇲🇽Mexico
      • 🇵🇪Peru
    • Payin
      • 🇲🇽Mexico
        • SPEI
        • Cash
        • Card
        • Payin Simulation (SPEl)
        • Payin Simulation (Cash &Card)
      • 🇨🇴Colombia
        • PSE
        • Bancolombia
        • Cash
        • All-Checkout
        • Payin simulation
      • 🇵🇪Peru
        • Transfer
        • Cash
        • Wallet
        • Card
        • Payin simulation
      • 🇧🇷Brazil
        • PIX
        • Payin simulation
      • 🇪🇨Ecuador
        • Transfer
        • Cash
        • Card
        • Wallet
        • Payin simulation
      • 🇦🇷Argentina
        • Debin
    • Payout
      • 🇲🇽Mexico
        • SPEI
        • Explanation of the reason for the payout failure
        • payout simulation
      • 🇨🇴Colombia
        • Transfer
        • Transfiya
        • Explanation of the reason for the payment failure
        • Payout simulation
      • 🇵🇪Peru
        • Transfer
        • Explanation of the reason for the payout failure
        • Payout simulation
      • 🇨🇱Chile
        • Transfer
        • Payout simulation
      • 🇧🇷Brazil
        • PIX
        • Explanation of the reason for the payment failure
        • Payout simulation
      • 🇪🇨Ecuador
        • Transfer
        • EC Transfer
        • Payout simulation
      • 🇦🇷Argentina
        • Transfer
    • Inquire
      • Transaction inquiries
      • Balance inquiry
      • Credential inquiry
      • Query the settlement status
    • Dictionaries and Resources
      • Response status code
      • Dictionary table
      • Download
      • Test parameters
Con tecnología de GitBook
En esta página
  • Usage scenarios
  • Callback configuration
  • note
  1. Welcome to Supefina's API documentation

Notification callback description

AnteriorSignature algorithmsSiguienteCashier (only for merchants in the e.commerce industry)

Última actualización hace 22 días

Usage scenarios


When the user initiates the payment, when the transaction is completed, the Supefina payment system will inform the transaction result details by calling the callback interface provided by the merchant, and the merchant needs to accept and implement its own processing logic according to the response rules.

Callback configuration


  1. Before initiating a transaction, the merchant needs to configure the callback address in the < Merchant Backend - Security Center >, otherwise the transaction result will not be received normally.

  2. Multiple callback addresses can be configured. If you need to change or add a callback address, please configure it in the merchant background before initiating the transaction.

  3. In order to maintain the uniqueness of the callback address, it is recommended not to add variables such as order number and payment product to the address.

  4. To ensure the security of the transaction, Supefina will verify the callback URL field with the configured callback address.

note


  1. The payment system does not guarantee that the notification will be successful, and in some cases, the notification may fail and the merchant may not receive the callback, including but not limited to the wrong callback address provided by the merchant.

  2. The merchant system needs to verify the signature of the content of the result notification, and the signature and signature verification logic are described in the "".

  3. Some channels may have multiple callbacks in some cases, such as success and then failure, and you need to add your own processing logic.

Signature Algorithm