FILTER BY TAG

Oney by Thunes Refund Workflow

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

Figure:

Oney by Thunes Refund 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. See Create a Session.
  3. Cybersource
    responds with
    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 API 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 a
    SETTLED
    status.
  10. The customer decides to return the purchase, and the merchant sends a refund API request to
    Cybersource
    . See Refund a Payment.
  11. Cybersource
    responds with a successful
    REFUNDED
    status to the merchant.