Integration checklists
An overview of the available integration checklists.
Last updated
An overview of the available integration checklists.
Last updated
These integration checklists are meant to assist developers and quality assurance teams. Each checklist covers features that we either require or highly recommend you build into your tool. We also provide to help you conceptualize the various interactions.
You can use these checklists and while developing and testing your commerce connector.
Completing these checklists helps ensure your commerce connector can pass the , and that any client sites built with the tool can successfully complete the .
The following sequence diagrams depict the , , , key , and . You can consult these sequence diagrams while working your way through the various integration checklists.
This visualization shows the potential webhook events that are emitted when a POST/orders
returns a state
of in_review
or pending payment
. It also demonstrates how an order in an accepted
state drives both fulfillments and cancellations and how to handle the order complete event.
In this sequence diagram, we demonstrate how customers can use their account portals to create payment sources in Drop-in that are ready for storage and how you can then save these sources to their accounts for use in future purchases. The interactions in this diagram occur outside of a standard checkout flow.
This diagram depicts the core commerce flow and shows the basic interactions between the customer, your commerce platform, the Digital River APIs, and Digital River's Global Commerce layer. The same diagram and accompanying text are on the page.
This diagram depicts an end-to-end commerce flow using the submit then redirect solution. For details on how to implement it, refer to .
In this illustration, we depict the interactions that occur while using a to build an acquisition checkout and process the order's response.
This diagram depicts a standard, merchant-initiated autorenewal that uses a . In this sequence of events (other than being notified of successful and failed renewal attempts), customers don't actively interact with either the commerce platform or Digital River.