GALAXY PAY - API Reference Guide
  • Payment Gateway
    • Payment solution
      • General integration steps
      • Modal checkout
        • Integration Guide for Web Desktop & Mobile Browser
      • Merchant checkout
      • Merchant Hosted Checkout
      • Pay with option
      • Pay with token
      • Fast pay
      • Pay with QR
      • Pay with E-Wallet
    • Demo
    • API Specification
      • Integration Keys
      • Definitions
        • Message Structure
        • Signature Algorithm
      • Data Flight
      • PAYMENT
        • Pay
        • Pay with create token
        • Pay with token
        • Pay with Option
        • Pay with QR
        • Checkout(for modal checkout)
        • Payment Link
        • Fast pay
      • TOKENIZATION
        • Merchants
          • Delete Token
        • Customers
          • Query Tokens
          • Remove Token
      • MANAGEMENT
        • Query Transaction
        • Refund Transaction
        • Void Transaction
        • Capture Transaction
      • IPN & CALLBACK
        • Result & IPN Callback
        • Cancel Callback
    • Appendix
      • Response Codes
      • Currencies
      • Domestic Banks
      • International Card Brands
      • eWallets
      • Payment Hubs
        • Apple Pay Validation
      • QR Payment Providers
      • Buy Now Pay Later
      • Test Information
      • Glossary
  • Payment Link
    • IPN callback
  • Archive
    • QR Payment (Old version)
      • API create QR
      • API query status
      • How to test
    • API create PaymentLink
Powered by GitBook
On this page
  • Benefits of Pay with token
  • Customer journey
  • Step 1: Pay with create token
  • Step 2: Pay with token
  • Integration
  1. Payment Gateway
  2. Payment solution

Pay with token

PreviousPay with optionNextFast pay

Last updated 5 months ago

Only apply for Domestic or International card.

APIOperation = PAY; sourceOfFund = TOKEN

Use Token created in and apiOperation = PAY to pay

Benefits of Pay with token

  1. High Security: Uses tokenization instead of card data to protect sensitive information and reduce data breach risks.

  2. Streamlined Payments: Customers don’t need to re-enter card details, making transactions faster.

  3. Reduced Declines: Network Tokens can auto-update when card changed (only apply for International Card), ensuring more stable transactions.

  4. Supports Recurring Payments: Easily handles recurring transactions without re-verifying card details.

  5. PCI DSS Compliance: Lowers compliance burdens, saving time and costs on security requirements.

Customer journey

The following sample of customer journey is for Integration method = MERCHANT HOSTED CHECKOUT and payment method = DOMESTIC CARD:

View information about terms/definitions in

Step 1: Pay with create token

  1. Customer completes order information and initiates a transaction with a payment method (for example, DOMESTIC Card). API Operation = PAY_WITH_CREATE_TOKEN

  2. Customer enters card information: Card number, Card holder name, card issue date/expired date. Then clicks "Submit" to proceeds to complete the payment.

  1. After the credentials are entered, and the payment flow is launched, the user is navigated through a secured Galaxy Pay environment that reflects the transaction ID.

  1. The flow takes the user to the login ACS page of the bank, where the user needs to complete the transaction by using the OTP sent by the bank to the registered mobile number.

  1. The customer is shown (failed/successful) on merchant website based on the transaction status from Galaxy Pay

  1. Save Token from IPN callback

Step 2: Pay with token

  1. Customer completes order information and initiates a transaction with a payment method (for example, DOMESTIC Card). API Operation = Pay, SourceOfFund = Token

  2. Customer enters token (created in Step 1) and clicks "Submit" to proceeds to complete the payment.

  1. After the credentials are entered, and the payment flow is launched, the user is navigated through a secured Galaxy Pay environment that reflects the transaction ID.

  1. The flow takes the user to the login ACS page of the bank, where the user needs to complete the transaction by using the OTP sent by the bank to the registered mobile number.

  1. The customer is shown (failed/successful) on merchant website based on the transaction status from Galaxy Pay

Integration

See integration detail in

Step 1: Use API to create token

Step 2: Use Token created in step 1 and API (Pay with token) to pay

Pay with create token
Glossary
General integration steps
Pay with create token
Pay