The checkout endpoints provide ways of performing a checkout process against an Order. The Storefront API supports two ways of checking out an order, one using hosted checkout pages, and a more advanced option for inline payment processing.
With the hosted checkout flow it is required that before redirecting to the payment gateway a checkout token should be generated. This token is passed to the pay endpoint to ensure that only the given order can be processed in response to the checkout request. The pay endpoint should be launched in a WebView/iframe with this token which will redirect to the given Orders payment gateway for payment capture. To determine the outcome of the payment developers should monitor the WebView/iframes URL. They will be redirected to the same pay endpoint URL with either a /completed
, /canceled
or /errored
suffix.
With the inline checkout flow, it is left to the implementing developer to perform payment capture. Before a capture can begin, the order should be initialized using the initialize
endpoint which prepares the Order for capture. The initialize
endpoint will return the settings of the Orders selected payment method, along with details of expected metadata needed by the payment provider. Developers can use this data to perform an inline capture and call the confirm
endpoint when the capture is successful, passing back any metadata captured.
Redirects to the given Orders selected payment gateway for payment processing.If in Framed
mode should be redirected to as normal, or if in Framed
mode, the endpoint URL should be launched in a WebView/iframe and developers should watch for changes in the URL to detect the outcome of the transaction. Final endpoint URLs will be one of {endpointUrl}/completed
, {endpointUrl}/canceled
or {endpointUrl}/errored
. If launched in an iframe from a web context, you can also register a message
event handler to get notified of the final status. Messages will be in the format UC:{orderId}:{token}:{status}
The ID of the order being checked out
"a3140924-7f3a-4625-a378-81f05b6b9166"
The checkout token for the checkout session
"ca6f5d62-32de-4849-bbf4-643d6f945a8d"
Success
Initialization prepares the order for checkout and produces a token to be passed to the /pay
endpoint.
The ID of the order being checked out
"1ca12483-eec6-414f-bfcc-2dd2430cac4c"
The ID or the alias of the store
The base URL the checkout request originates from. Used on the checkout status pages to securly post messages back to a parent window about the checkout status.
"https://www.example.com"
Sets the mode the checkout should run in, either Redirect
(default) which follows the regular full redirect approach and after payment returns to the configured URL's in the payment provider settings, or Framed
where it is assumed the checkout will be opened in a WebView/iframe and the status of the container monitored.
Success
With inline checkout flow it's the developers responsibility to capture the transaction and confirm the payment via the /confirm
endpoint. The selected payment methods setting are returned to ease payment gateway configuation, along with details of any meta data the payment method expects to be captured.
The ID of the order being checked out
"b69092b3-4609-4640-b283-b76f44dd8dd2"
API key specified through configuration to authorize access to the API.
The ID or the alias of the store
Success
Updates the given Orders transaction info with the supplied details and transitions the order from a open
to a finalized
state
The ID of the order being checked out
"087492f4-4ff2-41fd-aebd-df1dcd198c3c"
Defines the properties that should be expanded in the response
Limit the properties returned in the response
API key specified through configuration to authorize access to the API.
The ID or the alias of the store
Success