Comment on page
Learn how a standard flow works in the Direct Integrations option
The following sequence diagrams outline a standard Direct Integrations 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:
When identifying and describing your products in the Digital River APIs, you can use several approaches.
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 guest or registered customer.
When a new customer checks out on your storefront, you can use the Digital River APIs to create a customer and a checkout. The checkout contains the transaction's tax details and assigned selling entity. Your commerce platform should update the user interface with this tax information and use the selling entity to display compliance disclosures.
The immediate response contains either a
201 Createdstatus code. In the event of an error, update the status of the commerce platform and render the appropriate message to storefront customers. If an order is created, use the response's data to update the status of the commerce platform's order.
Once an order is successfully screened for fraud or customers complete the steps necessary to push payment, Digital River creates the order accepted and ready to fulfill event. If an order asynchronously fails due to suspected fraud or because the payment window closes without funds, we create an order blocked or charged failed event, respectively.
Once an order's
accepted, 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
POST/fulfillmentsrequest that specifies the fulfilled quantity, the cancelled quantity, or both. Depending on the configuration of that request, Digital River initiates a funds capture and/or authorization reversal.