Integration checklists
An overview of the available integration checklists.
These MOR/SOR 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 sequence diagrams to help you conceptualize the various interactions.
You can use these checklists and sequence diagrams while developing and testing your commerce connector.
Completing these checklists helps ensure your commerce connector can pass the tool-specific certification, and that any client sites built with the tool can successfully complete the production checkout certification.

Sequence diagrams

The following sequence diagrams depict the core commerce flow, subscription acquisitions, merchant-initiated auto-renewals, key order and fulfillment events, and how customers use their account portals to create and save payment sources. You can consult these sequence diagrams while working your way through the various integration checklists.

Core commerce 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. You can find the same diagram, along with accompanying text, on the Process flow page.
Core Commerce.png
1MB
Image

Subscription acquisitions

In this illustration, we depict the interactions that occur while using a third-party subscription service to build an acquisition checkout and process the orders response.
Subscription acquisitions.png
546KB
Image

Subscription auto-renewals

Subscription auto-renewals.png
219KB
Image
This diagram depicts a standard, merchant-initiated autorenewal that uses a third-party subscription service. 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.
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.
Order and fulfillment events.png
585KB
Image

Source creation in customer portals

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.
Create sources in customer portal.png
65KB
Image
Last modified 1mo ago