> For the complete documentation index, see [llms.txt](https://docs.digitalriver.com/home/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/home/readme.md).

# Documentation

Learn to integrate with Digital River to optimize your international global eCommerce business. Digital River provides a single solution for localized payment processing, taxes, fraud, and regulatory compliance.&#x20;

## Choose how to integrate

Select the integration option below to view appropriate documentation and API references.

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th></th><th></th><th></th></tr></thead><tbody><tr><td><strong>Have a commerce platform?</strong></td><td>If you already have a commerce technology, use the <strong>Digital River API</strong> for your build.</td><td><p><a href="https://docs.digitalriver.com/digital-river-api/">Documentation</a></p><p><a href="https://docs.digitalriver.com/digital-river-api-reference">Digital RIiver API Reference</a></p><p><a href="https://docs.digitalriver.com/digital-river-api/payments/payment-integrations-1">Payment Solutions</a></p><p><a href="https://github.com/DigitalRiver/api-sandbox#digital-river-api-postman-collection">Postman Collection</a></p><p><a href="https://docs.digitalriver.com/ecompass">eCompass</a></p></td><td><strong>Need a pre-integrated partner solution?</strong></td><td>Explore how our pre-built partner integrations can simplify your build.</td><td><a href="https://docs.digitalriver.com/partner-integrations/">Connectors</a></td></tr><tr><td><strong>Need a commerce platform?</strong><br></td><td>If you don’t have a commerce technology, use the <strong>Commerce API</strong> to build your storefront with Digital River.</td><td><p><a href="https://docs.digitalriver.com/commerce-api/">Documentation</a></p><p><a href="https://docs.digitalriver.com/commerce-api-references">Commerce API References</a></p><p><a href="https://docs.digitalriver.com/commerce-api/payments/payments-solutions">Payment Solutions</a></p><p><a href="https://github.com/DigitalRiver/commerce-api">Postman Collection</a></p><p><a href="https://docs.digitalriver.com/ecompass">eCompass</a></p></td><td></td><td></td><td></td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.digitalriver.com/home/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
