Reversing an Authorized Payment Workflow

This workflow describes the sequence of events that comprises reversing an authorization, also known as cancelling a payment, with Klarna.

Figure:

Authorization Reversal Workflow
  1. The customer begins to checkout on the merchant website and either chooses the Klarna payment option or uses the Klarna widget.
  2. The merchant sends either a HOP or inline session API request to
    Cybersource
    . For more information, see Creating a HOP Session and Creating an Inline Session.
  3. Cybersource
     responds with the initiated status and either a Klarna redirect URL or Klarna pre-approval token.
  4. The merchant either redirects the customer to a Klarna URL or sets the Klarna widget to a unique token.
  5. The customer completes the checkout using either the Klarna URL or widget. If the customer used the Klarna URL, the customer is redirected to the merchant website.
  6. The merchant sends an authorization API request to
    Cybersource
    . For more information, see Authorize a Payment.
  7. Cybersource
     responds to the merchant with the
    PENDING
     status and an authorization request ID.
  8. The merchant sends periodic check status requests to
    Cybersource
     with the authorization request ID.
  9. Cybersource
     responds to the merchant with the
    AUTHORIZED
     status when the authorization is complete.
  10. The customer or merchant decides to cancel the payment.
  11. The merchant sends an authorization reversal API request to
    Cybersource
    . For more information, see Reverse an Authorized Payment.
  12. Cybersource
     responds to the merchant with the
    AUTH_REVERSED
     status.
  13. The merchant displays a payment cancellation confirmation to the customer.