On This Page
FILTER BY TAG

Oney by Thunes Payment Workflow

This workflow describes the sequence of events that comprises a successful Oney payment.

Figure:

Oney by Thunes Payment Workflow
  1. The customer chooses the Oney payment method from among the available payment methods shown on the merchant's checkout page.
  2. The merchant sends the create a session API request to
    Cybersource
    . The session service creates a unique customer session. SeeCreate a Session .
  3. Cybersource
     responds with a
    PENDING
     status, a URL to redirect the customer, and a pre-approval token.
  4. The merchant sends the customer to the redirect URL page.
  5. The customer completes the checkout on the redirection page within 20 minutes.
  6. The merchant sends an authorization API request to
    Cybersource
     with the pre-approval token and any optional details. See Authorize a Payment.
  7. Cybersource
     responds to the merchant with one of these statuses:
    • AUTHORIZED
      : The payment is successfully authorized.
    • PENDING
      : Either the authorization is being audited by Oney or the customer has not completed the checkout using the redirection URL. The merchant should send a check status request to retrieve status updates. See Check a Transaction Status.
  8. The merchant sends a capture API request to
    Cybersource
     with the authorized amount, currency, and original authorization request ID. See Capture an Authorized Payment.
  9. Cybersource
     responds to the merchant with one of these statuses:
    • PENDING
      : The capture request is accepted but is not
      SETTLED
      . The merchant should send a check status request to retrieve status updates. See Check a Transaction Status.
    • SETTLED
      : The capture request is settled for the requested amount.
RELATED TO THIS PAGE