> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/product/checkout/overview-how-to-customise-the-limio-modular-checkout/how-to-direct-customers-to-a-different-checkout-based-on-the-offer-they-are-purchasing.md).

# Direct Customers to Different Checkout Based on Offer

## Checkout Types on offers

You can configure on the offer which checkout to use for this specific offer. Checkout on the offers can be configured in three different ways as mentioned below.

* Standard
* External
* External-Post
* Purchase Links

<figure><img src="https://3320508512-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAw9J8ugfVIqzNtzPQiWO%2Fuploads%2Fgit-blob-55e15969c8bde2f7441224ae98f893236676f0f1%2Fimage%20(73).png?alt=media" alt=""><figcaption></figcaption></figure>

*Screenshot: Checkout configuration types*

## Standard Checkout

Standard checkout is the default Limio checkout. This checkout configuration makes use of the default Limio checkout page and authentication, and goes to /checkout.

## External Checkout

External checkout allows you to define explicitly the checkout link which is external to Limio.

This type of checkout configuration will be required where authentication is done outside Limio and then redirected to the checkout page for Limio. This can also be used when you have multiple checkout links (for example for segmentation).

In the case the user is unauthenticated and the checkout is authenticated, when Limio constructs the redirect url to be passed to the authentication flow it will fill the basket Id if the external url has the value present in the format /checkout-trial?basket={{basketId}}.

## External-Post Checkout

Using the external post checkout data can be pre-filled using the post request which is typically a HTML form.

External URL uses post request method which collects the data required for checkout in the body of the request message and this information is then used for checkout.

This type of checkout configuration is external to Limio.


---

# 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.limio.com/product/checkout/overview-how-to-customise-the-limio-modular-checkout/how-to-direct-customers-to-a-different-checkout-based-on-the-offer-they-are-purchasing.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.
