> For the complete documentation index, see [llms.txt](https://docs.paytweed.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.paytweed.com/getting-started/token-checkout-or-payments/flow-of-funds-purchase-to-settlement.md).

# Flow of Funds: Purchase to Settlement

## **Overview**[**​**](https://docs.paytweed.com/nft-flow-of-funds/#overview)

Tweed allows the client platform to choose out of 4 types of payment settlements:

* Paid ERC-20 Crypto settlement&#x20;
* Paid Native Crypto settlement
* Fiat settlement
* And Free-minting (no settlement)

You may use a different settlement for each asset you have.

***

## **Flow for Fiat Settlement**[**​**](https://docs.paytweed.com/nft-flow-of-funds/#flow-of-funds-fiat-settlement)

1. The buyer enters their card details and presses the "Buy" button
2. Tweed holds the value from their card
3. Tweed passes a request to the relevant claimer (according to the blockchain)
4. The claimer calls the platform's collection contract to "mint and send" the NFT
5. The collection's contract sends the NFT to the buyer's wallet
6. Tweed captures the money from the buyer's card and sends it to the platform's account
7. (optional) Tweed backend calls the webhook configured in the console with the purchase details

<figure><img src="/files/nPt6sXgscfF0ttFpnacH" alt=""><figcaption></figcaption></figure>

***

## **Flow for Crypto Settlement (Native Currency)**

1. Tweed converts the cryptocurrency to its equivalent fiat value
2. The buyer enters their card details and presses the "Buy" button
3. Tweed holds the NFT value from the buyer's card
4. Tweed passes a request to the relevant claimer (according to the blockchain)
5. Tweed's claimer calls the platform's collection contract to "mint and send" the NFT with the right amount of crypto
6. The collection's contract sends the NFT to the buyer's wallet
7. Tweed captures the money from the buyer's card
8. (optional) Tweed backend calls the webhook configured in the console with the purchase details

<figure><img src="/files/Yu79Y0FfIXpyS5rnaK6j" alt=""><figcaption></figcaption></figure>

***

## **Flow for Crypto Settlement (ERC20 Tokens)**

1. Tweed converts the ERC20 tokens value to its equivalent fiat value
2. The buyer enters their card details and presses the "Buy" button
3. Tweed holds the NFT value from the buyer's card
4. Tweed passes a request to the relevant claimer (according to the blockchain)
5. The chosen ERC20 token's amount is getting approved for the platform to withdraw
6. Tweed's claimer calls the contract's "mint and send"
7. The contract withdrow the funds from tweed's claimer&#x20;
8. The contract send the tokens to the user's wallet
9. Tweed captures the money from the buyer's card
10. (optional) Tweed backend calls the webhook configured in the console with the purchase details

<figure><img src="/files/B2V9gHqsUB9kO2sQkxc7" alt=""><figcaption></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.paytweed.com/getting-started/token-checkout-or-payments/flow-of-funds-purchase-to-settlement.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.
