6DOT50 APIs
  • Redemptions API
    • Overview
    • Process Flow
    • Requests
    • Response Models
    • Payment Codes
    • Authentication
      • POST /authentication/getToken
  • Accounts
    • GET /accounts
    • GET /accounts/{id}/transactions
  • Initiate Payment
    • POST /payments
  • User Payment Pages
    • Authentication
    • Payment Confirmation
    • Payment Status
  • Payment Status
    • GET /payments/{id}
  • List Payments
    • GET /payments
  • Support
  • PAY API
    • Overview
    • API Keys
    • Endpoints
    • Process Flow
    • Requests
    • Response Models
    • Authentication
      • POST /authentication/getToken
    • Accounts
      • GET /accounts
    • Batches
      • POST /batches
      • GET /batches
      • GET /batches/{id}
      • PUT /batches/{id}
      • GET /batches/statusCodes
      • POST /batches/{id}/payments
      • GET /batches/{id}/payments
      • POST /batches/{id}/submit
      • POST /batches/{id}/cancel
    • Members
      • GET /members/{msisdn}/exists
    • Payments
      • GET /payments/{id}
      • DELETE /payments/{id}
      • GET /payments/statusCodes
  • Support
Powered by GitBook
On this page
  1. User Payment Pages

Payment Confirmation

PreviousAuthenticationNextPayment Status

Last updated 2 years ago

After authentication, the user is required to verify and confirm their payment:

Similar to login, Cancel will immediately cancel the payment and redirect the user back to the supplied returnUrl.

When the user presses Confirm, the system will initiate the payment instruction and deduct the appropriate vouchers from the user’s 6DOT50 account and transfer the amount to the nominated accountId supplied in Initiate Payment.

Should the user have insufficient funds to process the payment, the payment will be cancelled, and the user will be redirected to the returnUrl. Upon querying the status of the payment: statusCode will be 2 (cancelled) and errorCode will be 1 (insufficient funds).

Should any other error occur during the payment process, the payment will be cancelled, and the user will be redirected to the returnUrl. Be sure to query the status of the payment on return, particularly reviewing statusCode and errorCode and display an appropriate message to the user.