# Commerce infrastructure

The following diagram provides an overview of the common architecture used when integrating with Digital River's [Global Seller Services](https://www.digitalriver.com/global-seller-services/). At a high level, these integrations consist of a client and commerce ecosystem.

![](/files/-Mbb54-1c0QoJZBQqMZ0)

For each step in an integration's workflow, the following provides a more detailed explanation:

1. Core Services integrates with the Commerce Platform (CP) and Online Properties to handle identity management, MyAccount, and data synchronization services.
2. Online Properties supports the customer's MyAccount self-service and browse services.
3. Any customer actions that may result in a transaction are redirected to the CP storefront.
4. For all incoming traffic, the CP's storefront manages the commerce experience.
5. The CP's self-service admin tools support product, pricing, and promotions management.
6. A subscription management extension in the CP provides a self-service UI for the customer.
7. Digital River provides fraud, tax, payment, and legal compliance services via headless APIs that are embedded in the CP.
8. Subscription renewals leverage Digital River's payment optimization services to maximize renewal rates.
9. Client physical fulfillment and services provisioning systems receive and process orders.
10. Client accounting and finance systems receive remittance details from Digital River via reports, APIs, and Digital River Dashboard.


---

# Agent Instructions: 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/ecosystem-overview.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.
