Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://docs.umbraco.com/umbraco-commerce/reference/storefront-api/endpoints/checkout below:

Checkout | Umbraco Commerce

1. Reference
2. Storefront API
3. Endpoints

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.

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

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.

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.

GET /umbraco/commerce/storefront/api/v1/checkout/{orderId}/token HTTP/1.1
Host: 
Store: text
Accept: */*

{
  "token": "text",
  "orderNumber": "text",
  "payUrl": "text"
}

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

The checkout token for the checkout session

GET /umbraco/commerce/storefront/api/v1/checkout/{orderId}/pay/{token} HTTP/1.1
Host: 
Accept: */*

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.

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

API key specified through configuration to authorize access to the API.

The ID or the alias of the store

GET /umbraco/commerce/storefront/api/v1/checkout/{orderId}/initialize HTTP/1.1
Host: 
Api-Key: text
Store: text
Accept: */*

{
  "orderNumber": "text",
  "paymentMethod": {
    "settings": {
      "ANY_ADDITIONAL_PROPERTY": "text"
    },
    "metaDataDefinitions": {
      "ANY_ADDITIONAL_PROPERTY": "text"
    },
    "urls": {
      "continue": "text",
      "cancel": "text",
      "error": "text",
      "callback": "text"
    }
  }
}

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

Limit the properties returned in the response

Defines the properties that should be expanded in the response

API key specified through configuration to authorize access to the API.

The ID or the alias of the store

POST /umbraco/commerce/storefront/api/v1/checkout/{orderId}/confirm HTTP/1.1
Host: 
Api-Key: text
Store: text
Content-Type: application/json
Accept: */*
Content-Length: 119

{
  "amount": 1,
  "fee": 1,
  "transactionId": "text",
  "paymentStatus": "Initialized",
  "metaData": {
    "ANY_ADDITIONAL_PROPERTY": "text"
  }
}

{
  "orderNumber": "text",
  "transactionInfo": {
    "transactionId": "text",
    "authorizedAmount": {
      "currency": {
        "id": "123e4567-e89b-12d3-a456-426614174000",
        "code": "text"
      },
      "value": 1,
      "formatted": {
        "value": "text"
      }
    },
    "feeAmount": {
      "currency": {
        "id": "123e4567-e89b-12d3-a456-426614174000",
        "code": "text"
      },
      "value": 1,
      "formatted": {
        "value": "text"
      }
    },
    "baseCurrencyExchangeRate": 1,
    "paymentStatus": "Initialized"
  }
}

Last updated 4 months ago

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4