> For the complete documentation index, see [llms.txt](https://docs.digitalriver.com/digital-river-api/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalriver.com/digital-river-api/general-resources/standards-and-certifications/integration-checklists/order-refund-synchronization.md).

# Order refund synchronization

The [checklist items](#integration-checklist) and [standards](#integration-standards) in this section cover how to consume refund and chargeback events and use them to update order refund data in your commerce system. This helps ensure that the data in your system stays in sync with the data in Digital River's system throughout the entire order life cycle.

## Integration checklist

Click any checklist item to see more detail on how to meet the integration standard.

* [ ] [After consuming an `order.charge.refund.complete` event, do you update the order refund status and other refund data in your commerce system?](#consume-refund-complete-event-and-update-refund-data)
* [ ] [After consuming an `order.chargeback` event, do you update the order refund status and other refund data in your commerce system?](#consume-chargeback-event-and-update-refund-data)

## Integration standards

These integration standards relate to synchronizing order refund states:

### Consume refund complete event and update refund data

After you [provide notification of a refund](/digital-river-api/order-management/returns-and-refunds-1/refunds/issuing-refunds.md), Digital River processes your request and emits refund-related [events](/digital-river-api/order-management/events-and-webhooks-1/events-1.md) to your [webhooks](/digital-river-api/order-management/events-and-webhooks-1/webhooks.md). When you receive the `refund.complete` and `order.charge.refund.complete` events, update your commerce system with the `state` value, and other information, delivered in the events.

### Consume chargeback event and update refund data

When Digital River processes and completes a chargeback, we create a [Sales Transaction](https://github.com/DigitalRiver/GitBook/blob/Digital-River-API-latest/developer-resources/standards-and-certifications/integration-checklists/broken-reference/README.md) with a `type` of `fraud_chargeback` or `non_fraud_chargeback` and send you both a `sales_transaction.created` and `order.chargeback` event. You should use the `order.chargeback` event to update the status of the order refund in your commerce system.

## API interfaces

| Documentation                                                                                                                   | Direct API                                                                            | PHP SDK                                                                                   |
| ------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- |
| [Events](/digital-river-api/order-management/events-and-webhooks-1/events-1.md): order.charge.refund.complete, order.chargeback | [Events](https://docs.digitalriver.com/digital-river-api-reference/2021-12-13/events) | [Events](https://github.com/DigitalRiver/digital-river-php/blob/main/docs/Model/Event.md) |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.digitalriver.com/digital-river-api/general-resources/standards-and-certifications/integration-checklists/order-refund-synchronization.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.