Standard flow
Learn how a standard flow works in the Direct Integrations option
Last updated
Learn how a standard flow works in the Direct Integrations option
Last updated
The following sequence diagrams outline a standard flow. They depict interactions between the customer, your commerce platform, the Digital River APIs, and Digital River. These diagrams are meant to outline Digital River's core capabilities, focusing specifically on:
Important states in an
The sequence of major
The data you must provide to use Digital River's business model
How checkouts, orders, events, and fulfillments work
Refer to the section on the page to learn about other flows.
You can use several approaches when identifying and describing your products in the Digital River APIs.
For details on your product management options, refer to the page.
Digital River is typically not involved in initial pre-checkout interactions between customers and your commerce platform. During this stage, customers land on your storefront, build a cart, confirm the cart's details, and initiate checkout. Your commerce platform typically presents them with the option of checking out as either a .
When a new customer checks out on your storefront, you can use the Digital River APIs to create a and a . The contains the transaction's tax details and assigned . Your commerce platform should update the user interface with this tax information and use the selling entity to .
When customers enter the payment entry stage, your commerce platform must render . Customers submit their payment details, and use that information to create a payment .
Explore the to better understand of how sources are created.
If customers opt to save the payment for future purchases, and that source is , you should and then . Otherwise, simply apply the source to the checkout for use in this .
Once payment is applied, use the to update the commerce platform with the transaction's final tax information and . The commerce platform should render an order review page with the appropriate .
At this point, customers typically confirm the transaction's details and submit the order. This event should trigger a . This request primarily acts as a and .
The contains either a 409 Conflict
or 201 Created
status code. In the event of an error, update the status of the commerce platform and render the appropriate message to storefront customers. If an is created, update commerce platform's order statis by using the response's data.
For , move the commerce platform's order into a ready to fulfill state and direct customers to a "Thank You" page.
If an is immediately returned as or , you'll need to handle sent by Digital River.
Once an is successfully screened for fraud or customers complete the steps necessary to , Digital River creates the . If an asynchronously fails due to suspected fraud or because the payment window closes without funds, we create an or event, respectively.
When you're notified of one of these , retrieve the order's from the event's payload and, depending on that value, move the commerce platform's order into an accepted, blocked, or payment failed state.
Once an is , the client can initiate fulfillment. As products are fulfilled or cancelled, the commerce platform updates the status of those line items and emits status change events. These events should trigger a request that specifies the fulfilled quantity, the cancelled quantity, or both. Depending on the configuration of that request, Digital River initiates a and/or .