> For the complete documentation index, see [llms.txt](https://docs.bizon.one/08.01/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bizon.one/08.01/api-payment-gateway/workflows.md).

# Workflows

## <mark style="color:blue;">Using payment page</mark>

1. The customer presses the "Pay" button on a seller's website.
2. The seller handles the customer's payment request and sends a create request to the API, specifying a description of the purchase, payment amount and other details if needed (see Order creation).
3. Gateway responds with a URI of the payment page and order ID.
4. The seller saves the order ID and redirects the customer to the URI.
5. The customer fills up a payment form on the payment page.
6. Gateway processes authorization using the cardholder's credentials and redirects the cardholder back to the seller's website.
7. The seller requests order information using a saved order ID (see Order information) and depending on the order status renders the result page for the customer.

## <mark style="color:blue;">Server-to-server</mark>

1\.   Customer enters payment info and presses the "Pay" button while on a seller's website.

2\.   Sellers handle the customer's request and send an authorised request to the API (see Order authorization).

3\.   Gateway creates orders and handles payment using payment info received from the seller.

4\.   Gateway responds with the authorization results.

5\.   Seller handles the authorization results and renders the result page for the customer.

## <mark style="color:blue;">Charge-off through back-office</mark>

After the successful payment via the payment page is performed charge-off of funds from the customer's card such methods:

1\.   Enabling autocharge in the project (the delay of autocharge is set in minutes).

2\.   Manually charge-off of funds in the back-office ("Orders => Needed order => Charge").


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bizon.one/08.01/api-payment-gateway/workflows.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 `build a script that syncs our docs to a CMS` 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.