> For the complete documentation index, see [llms.txt](https://coda-payments.gitbook.io/coda-public-technical-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://coda-payments.gitbook.io/coda-public-technical-documentation/codashop-and-distribution/how-it-works.md).

# How it Works

Transaction Processing Flow

**Sync User Data**

When a customer initiates a purchase on Codashop by entering their user ID or logging in, Coda starts the process by synchronizing the user's information via a [UserSync API Request](/coda-public-technical-documentation/codashop-and-distribution/integration-guides/usersync-api-request.md). 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 Codashop, the platform sends a comprehensive package of user details, SKU ID, payment channel specifics, and more to our partners via a [Validation API Request](/coda-public-technical-documentation/codashop-and-distribution/integration-guides/validation-api-request.md). Once the partner confirms the request, Codashop authorizes the customer to proceed to payment.

**Top-Up Fulfillment** 

Once the payment is successfully processed, Coda sends a [Top-Up API request](/coda-public-technical-documentation/codashop-and-distribution/integration-guides/top-up-api-request.md) to the partner's endpoint. This crucial step ensures that the purchased item is promptly added to the customer’s account

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

<figure><img src="https://611292228-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl56STCN5yoV1K1MhVEvU%2Fuploads%2F21hO4BFOz0XYIqByhfzq%2Fapi%20flow%20(1).png?alt=media&amp;token=5ef40461-30ec-45c0-adc6-4a92c8073f52" alt=""><figcaption></figcaption></figure>