# Orders

The crypto checkout service revolves around the concept of orders. Each time a payment is requested, an order is created. Orders can be updated, monitored, canceled, but never deleted.

Some methods in the order ecosystem accept bearer token authentication. This is necessary because some endpoints naturally reside in the application front-end, and your API key cannot be shared publicly under any circumstance. The only method that requires the API key exclusively is the creation of orders.

The main flow of information starts with the creation of an order. A callback URL must be provided along with the other parameters. This callback URL is the address that will be notified with relevant information and allows the client to receive up-to-date information and act accordingly. After the order was created, a payment address will be provided for the end user. Once the payment is made, a notification is sent to the previously mentioned URL, allowing the business to proceed as desired. Usually, this is where the goods or services are cleared for delivery.

{% hint style="danger" %}
Before making any order requests, make sure you set up your wallets through the stores API. Check out how you can do so here: [Store](/english/products/crypto-checkout/checkout-api/store.md)
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.cryptum.io/english/products/crypto-checkout/checkout-api/orders.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.