Ayolinx-Openapi
🇬🇧English
  • 🇬🇧English
  • 🇨🇳中文
  1. APIS Need Merchant To Provide
Ayolinx-Openapi
🇬🇧English
  • 🇬🇧English
  • 🇨🇳中文
  • Openapi-EN-US
    • Read before development
      • Introduction
      • Header Parameter Description
      • Signature generation rules
      • Channel description
      • Error code description
      • Callback description
      • PartnerServiceId description
    • GetAccessToken
      • Access Token B2B
    • Qris
      • APIS Ayolinx Provided to Merchant
        • Generate Qris
        • Query Qris
        • Cancel Qris
      • APIS Need Merchant to Provide
        • Payment Notify
    • EWallet
      • APIS Ayolinx Provided to Merchant
        • Get Payment Url
        • Inquiry Status
      • APIS Need Merchant to Provid
        • Payment Notify
    • VirtualAccount
      • APIS Ayolinx Provided To Merchant
        • Error Codes
        • Create VA
        • Inquiry Va
      • APIS Need Merchant To Provide
        • Callback introduction
        • Access Token B2B
          POST
        • Payment
          POST
      • Non-snap callback interface
        • Payment Notify
  1. APIS Need Merchant To Provide

Callback introduction

Merchants are required to provide two interfaces. One is the interface for generating an access token, and the other is the interface for receiving callback data.

Callback Process:#

1.
First, Ayolinx calls the access - token interface provided by the merchant to obtain the token.
2.
Then, Ayolinx requests the merchant's callback - data - receiving interface with the "Authorization Bearer token" header.
3.
The merchant verifies whether the token is legitimate. If it is, the callback is considered normal.
Modified at 2025-02-27 11:27:25
Previous
Inquiry Va
Next
Access Token B2B