HOP Session Workflow
This workflow describes the sequence of events that comprises a successful payment
using a Klarna hosted-page.
Figure:
Klarna HOP Workflow
- The customer begins to checkout on the merchant website and chooses the Klarna payment option.
- The merchant sends a HOP session API request toCybersource. 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.
- Cybersourceresponds to the merchant with anINITIATEDstatus and a Klarna redirect URL.
- The merchant redirects the customer to the Klarna URL.
- 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.
- The merchant sends an authorization API request toCybersourceand includes the authorization token Klarna appended to the merchant URL. For more information, see Authorize a Payment.
- Cybersourceresponds to the merchant with thePENDINGstatus and a request ID.
- The merchant sends periodic check status API requests toCybersourcewith the request ID until the status updates. For more information, see Check a Request Status.
- Cybersourceresponds to the merchant with theAUTHORIZEDstatus when the authorization is completed.
- The merchant sends a capture API request with the request ID. For more information, see Capture a Payment.
- Cybersourceresponds to the merchant with thePENDINGstatus and a request ID.
- The merchant sends periodic check status API requests toCybersourcewith the request ID until the status updates.
- Cybersourceresponds to the merchant with theSETTLEDstatus when the capture is completed.
- The merchant displays a payment confirmation to the customer.