Understand the purpose and the basic structure of the Checkout object.

Checkouts manage the flow of the overall checkout process. When coupled with Drop-in, they can power your customer's checkout experience, from product selection to order placement. The Checkout object returns critical data points, such as the shipping amount, applicable taxes and fees, discounts, and total cost, that customers need to evaluate before they make a purchasing decision.

Checkouts allow you to create, retrieve, update and delete individual checkouts, as well as perform requests to return a list of checkouts.

Checkout flow

The high-level flow of a Checkout generally adheres to the following pattern:

  1. On your storefront, the customer selects one or more SKUs. Note: How taxes should be displayed to customers during their entire storefront experience depends on the country.

  2. You create a Checkout that is associated with the selected SKUs.

  3. Customer provides payment details via DigitalRiver.js or Drop-in.

  4. You update the Checkout with the payment source identifier returned by DigitalRiver.js or Drop-in.

  5. Digital River returns the updated Checkout to you with taxes calculated and amounts totaled.

  6. Customer reviews the checkout details and decides whether to make the purchase.

You can also associate the Checkout with a Customer and a Source. When you provide a customerIdvalue, the email and ship-to address associated with that Customer are used in the Checkout. However, any values provided by the customer during the checkout process override the values retrieved from the Customer object.

Checkout experience

The checkout experience on your storefront should include pages for customers to provide their shipping address, billing address, and payment details. You should also have an order review and submission page. And once customers make their purchase, we recommend you provide a thank you page.

As customers navigate these pages, your integration will make calls to create and update the Checkout, handle payments sources, and ultimately create the Order object.

Guidelines for displaying tax

The display of tax during the entire checkout experience should follow these guidelines (access required).