HOP Session Workflow

This workflow describes the sequence of events that comprises a successful payment using a Klarna hosted-page.

Figure:

Klarna HOP Workflow
  1. The customer begins to checkout on the merchant website and chooses the Klarna payment option.
  2. The merchant sends a HOP session API request to
    Cybersource
    . For more information, see Creating a HOP Session.
    If the customer changes their purchase selection after the merchant sends the session API request, the merchant must send an update session API request. For more information, see Updating a Session.
  3. Cybersource
    responds to the merchant with an
    INITIATED
    status and a Klarna redirect URL.
  4. The merchant redirects the customer to the Klarna URL.
  5. The customer completes checkout on the Klarna hosted-page and is redirected back to the merchant website. Klarna appends a unique authorization token to the merchant redirect URL.
  6. The merchant sends an authorization API request to
    Cybersource
    and includes the authorization token Klarna appended to the merchant URL. For more information, see Authorize a Payment.
  7. Cybersource
    responds to the merchant with the
    PENDING
    status and a request ID.
  8. The merchant sends periodic check status API requests to
    Cybersource
    with the request ID until the status updates. For more information, see Check a Request Status.
  9. Cybersource
    responds to the merchant with the
    AUTHORIZED
    status when the authorization is completed.
  10. The merchant sends a capture API request with the request ID. For more information, see Capture a Payment.
  11. Cybersource
    responds to the merchant with the
    PENDING
    status and a request ID.
  12. The merchant sends periodic check status API requests to
    Cybersource
    with the request ID until the status updates.
  13. Cybersource
    responds to the merchant with the
    SETTLED
    status when the capture is completed.
  14. The merchant displays a payment confirmation to the customer.