Ayolinx-Openapi
🇬🇧English
  • 🇬🇧English
  • 🇨🇳中文
  1. Read before development
Ayolinx-Openapi
🇬🇧English
  • 🇬🇧English
  • 🇨🇳中文
  • Openapi-EN-US
    • Read before development
      • Introduction
      • Header Parameter Description
      • Signature generation rules
      • Channel description
      • Necessary parameter configuration
      • Error code description
      • Callback description
      • PartnerServiceId description
    • GetAccessToken
      • Access Token B2B
    • Qris
      • APIS Ayolinx Provided to Merchant
        • Generate Qris
        • Query Qris
        • Cancel Qris
      • Non-Snap APIS Need Merchant to Provide
        • Payment Notify
      • Snap APIS Need Merchant to provide
        • Access Token B2B
        • 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
        • Payment
      • Non-snap callback interface
        • Payment Notify
    • Convenient store
      • APIS Ayolinx Provided To Merchant
        • Create retail transaction
        • retail query
      • APIS Need Merchant to Provid Copy
        • Payment Notify
  1. Read before development

Necessary parameter configuration

I. Secret key configuration#

Merchants need to configure the secret key when requesting Ayolinx OpenAPI. Ayolinx uses it to verify whether the signature is correct. After clicking "Save" for the first configuration, Ayolinx will also generate a key pair, which the merchant uses to verify whether the callback signature is correct.
image.png

II. IP whitelist configuration#

IP whitelist configuration for merchants to request Ayolinx
image.png

III. Channel parameter configuration#

Currently, DANA and BNC Qris configurations are supported. After the configuration is completed, the merchant information will be displayed on the payment page.
image.png
image.png

IV.Merchant client - key and client - secret Configuration#

If a merchant chooses to connect to Ayolinx openapi in the SNAP way, the merchant needs to generate its own client - key and client - secret, which are used for verification when Ayolinx requests the merchant.
image.png
Modified at 2025-06-25 11:12:17
Previous
Channel description
Next
Error code description