> For the complete documentation index, see [llms.txt](https://docs.coda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coda.co/coda-webstore/web-store-integration-guides/how-it-works.md).

# How it Works

**Sync User Data**

When a customer initiates a purchase on your web store by entering their user ID or logging in, Coda starts the process by synchronizing the user's information via a UserSync API Request. This enables our partners to personalize the offerings and overall experience, ultimately boosting conversions. For more details, please refer to the Personalized Sales Guide.

**Validate Purchase**

When a customer selects a specific SKU and enters payment details on your web store, the platform sends a comprehensive package of user details, SKU ID, payment channel specifics, and more to our partners via a Validation API Request. Once the partner confirms the request, Coda authorizes the customer to proceed to payment

**Top-Up Fulfillment** 

Once the payment is successfully completed, Coda sends a Top-Up request to the partner's endpoint. This crucial step should seamlessly result in the purchased item being added to the customer’s account.

For a visual representation of this purchase flow on your web store, refer to the sequence diagram below, which illustrates each step of the process.

<figure><img src="/files/4ibO2hq6RpqzUemVjXuI" alt=""><figcaption><p>Transaction Flow on your Web Store</p></figcaption></figure>


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.coda.co/coda-webstore/web-store-integration-guides/how-it-works.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.