> For the complete documentation index, see [llms.txt](https://docs.mdintegrations.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mdintegrations.com/partner/exploring-features/built-in-checkout-flows.md).

# Built-in Checkout Flows

MDI checkout and payment support uses Stripe. White-label partners can use MDI's hosted checkout experience with their own Stripe credentials. This keeps payment collection in your Stripe account without requiring you to build a checkout flow.

For checkout timing relative to intake and clinical review, see the Patient Journey page.

### Use your Stripe account with white-label checkout

Connect your Stripe account to use it with the MDI white-label checkout experience. Patients complete payment in the hosted voucher and intake flow, while charges settle to your Stripe account.

Stripe credentials are connected by MDI administrators. You cannot add Stripe API keys through the Partner Portal. Contact your MDI representative to coordinate the connection.

{% hint style="info" %}
Use the white-label checkout experience when you want MDI to host payment collection and your Stripe account to receive the charge.
{% endhint %}

### Checkout by integration path

<table><thead><tr><th width="257.28125">Integration path</th><th>Where checkout happens</th></tr></thead><tbody><tr><td>Shopify / WooCommerce</td><td>Your store uses its existing checkout and payment setup. MDI is not in the payment path for the product purchase. MDI handles the post-checkout medical intake and consultation fee.</td></tr><tr><td>White-label</td><td>MDI hosts checkout and payment as part of the voucher and intake flow. Connect your Stripe account to use your credentials for the payment experience.</td></tr></tbody></table>

{% hint style="info" %}
Your Offering configuration determines the amount charged. Offering pricing is set by our Clinical team.
{% endhint %}

### Checkout timing

Payment collection occurs during the checkout step for your integration. The timing of that step is separate from payment mechanics.

The Patient Journey page documents **checkout before intake** and **checkout after intake**. That page covers sequencing. This page covers who collects payment and where the payment form appears.


---

# 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.mdintegrations.com/partner/exploring-features/built-in-checkout-flows.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.