Fulfillments and cancellations

Learn more about the standards related to fulfilling or cancelling items.

The checklist items and standards in this section cover when and how to notify Digital River that you have fulfilled or cancelled all or part of a transaction.
Integration checklist
Click any checklist item to be provided more detail on how to meet the integration standard.
​After your system confirms a line item is fulfilled, do you use the Fulfillments API to supply Digital River with the required fulfillment data?​
​After your system confirms a line item is cancelled, do you use the Fulfillments API to supply Digital River with the required cancellation data?​
Integration standards
These integration standards relate to fulfillments and cancellations:
Provide required fulfillment data
Once you either synchronously or asynchronously receive an order in an accepted state, your integration can use the Fulfillments API to submit a POST/fulfillments with a fulfilled quantity.
When all the items in an order are fulfilled, the order transitions to a state of complete and an order.complete event is emitted. After you receive this event, you should update the order status in your system to match its state in our system.
Provide required cancellation data
To cancel items, your integration must use the Fulfillments API to submit a POST/fulfillments with a cancel quantity.
API interfaces
Documentation
Direct API
PHP SDK
​Fulfillments​
​Fulfillments​
​Fulfillments​
​Events: fulfillment.created
​Events​
​

Documentation	Direct API	PHP SDK
Fulfillments	Fulfillments	Fulfillments
Events: fulfillment.created	Events

Disclosures, compliance statements, and emails

Customer portal

Last modified 10mo ago