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

User Payment Pages

Once the payment has been initiated using POST /payments, your Merchant site must redirect the user’s browser to the following URI’s (depending on environment):

Environment
Payment Page Redirect URL

Test

https://secure.staging.6dot50.com/payment?id=paymentid

Production

https://secure.6dot50.com/payment?id=paymentid

Where paymentid is the unique PaymentID returned when initiating a payment using POST /payments.

Should the correct Payment ID be provided, a series of screens will be presented to the user to complete the payment.

PreviousPOST /paymentsNextAuthentication

Last updated 2 years ago