> For the complete documentation index, see [llms.txt](https://help.basiq-solutions.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.basiq-solutions.com/guide/setup-steps/step-1-order.md).

# 1. Order & first payment

Agree the setup with your manager, fill in the order form, pay the invoice — and the timeline starts.

{% hint style="info" %}
**You:** agree the setup, fill in the order form, pay the invoice and send the confirmation.\
**Basiq:** registers the company, buys and configures the domain. No action is needed from you on the company name or the domain.
{% endhint %}

{% stepper %}
{% step %}

#### Agree your setup in Telegram

Agree with your manager:

* Jurisdiction and package — UK LTD, HK Bundle or US LLC ([Setups & pricing](/guide/before-you-order/setups-and-pricing.md))
* Add-ons — Stripe, Shopify Payments, additional bank
* A specific bank, if you need one — this must be agreed **in advance**
* Anything else the setup must include (custom domain, extra services)

Rule: **1 company = 1 domain = 1 store.**
{% endstep %}

{% step %}

#### Fill in the order form

Support sends you an order form. Fill it in carefully — it fixes the exact composition of your setup, and it is where you specify the company name the invoice should be issued to.
{% endstep %}

{% step %}

#### Pay the invoice

The system issues an invoice to the company name you specified. Pay it by bank transfer (EUR) or USDT TRC-20. The first instalment is paid **before we start** — the process begins only once it is received. Add-ons take their 10% deposit upfront; extra services are paid in full before work begins.
{% endstep %}

{% step %}

#### Send the payment confirmation

Send the proof of payment to your manager — in direct messages or in your setup group. Once the payment is confirmed, the setup starts and the team begins work.
{% endstep %}

{% step %}

#### Note your start date

The timeline starts from receipt of your first payment. Setups paid on Thursday or later start from the following Monday.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
Payments are non-refundable once the process has started — including if you change your mind or a third-party platform declines the application. Read the [Payment terms](/guide/before-you-order/payment-terms-and-timelines.md) before you pay.
{% endhint %}

## While you wait

Use the incorporation time to complete Step 2 (phone numbers) and Step 3 (proxy + OctoBrowser). Both must be ready before any account is touched.

## Done when

* [ ] Order form submitted
* [ ] Invoice paid and the confirmation sent to your manager
* [ ] Manager confirmed the start date

{% content-ref url="/pages/8d7897a648fcd91cdfe61c6055c3fc9a2774e089" %}
[2. Virtual phone numbers](/guide/setup-steps/step-2-phone-numbers.md)
{% endcontent-ref %}


---

# 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://help.basiq-solutions.com/guide/setup-steps/step-1-order.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.