> 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/guides/help.md).

# What do you need help with?

Pick the area — banks, proxy and browser, review templates or warm-up — and follow the screens step by step.

Pick the area. Every guide walks you through the screens step by step and tells you when to involve your manager.

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h4><i class="fa-building-columns" style="color:$primary;">:building-columns:</i></h4></td><td><strong>Banks</strong></td><td>Receiving accounts, payment checks, paying suppliers, cards. One guide per bank.</td><td><a href="/guide/guides/banks.md">Banks</a></td></tr><tr><td><h4><i class="fa-globe" style="color:$primary;">:globe:</i></h4></td><td><strong>Proxy &#x26; browser</strong></td><td>The right proxy for each service and one stable OctoBrowser profile per account — GonzoProxy, a-socks, IPRoyal.</td><td><a href="/guide/guides/proxy-guide.md">Proxy Guide</a></td></tr><tr><td><h4><i class="fa-clipboard-check" style="color:$primary;">:clipboard-check:</i></h4></td><td><strong>Review templates</strong></td><td>A platform asks for documents? Open the template for that platform, prepare the pack, send it to your manager first.</td><td><a href="/guide/guides/review-templates.md">Review templates</a></td></tr><tr><td><h4><i class="fa-fire" style="color:$primary;">:fire:</i></h4></td><td><strong>Warm-up SOPs</strong></td><td>The first weeks of processing on Stripe, Shopify Payments and PayPal: amounts, pauses, growth schedule, what never to do.</td><td><a href="/guide/setup-steps/step-8-warm-up.md">8. Warm-up</a></td></tr></tbody></table>

{% hint style="danger" %}
**One rule for every section.** If a bank or a payment platform asks you for documents, a call or a verification, message your manager before you send anything. Documents sent without us are the most common way to turn a routine check into a ban.
{% endhint %}

## How the bank guides are built

Each bank guide follows the same order, so you always know where to look:

| Section                    | What it answers                                                                                  |
| -------------------------- | ------------------------------------------------------------------------------------------------ |
| Before you start           | Which proxy to use, what to change to yours after delivery                                       |
| 1. Receiving accounts      | How to create the account details for Shopify Payments, Stripe or PayPal and where to paste them |
| 2. Payment verification    | What the bank asks after the first payouts and the exact pack of screenshots that passes it      |
| 3. Pay your supplier       | Adding a payee and sending a payment                                                             |
| 4. Card                    | Getting a company card for subscriptions                                                         |
| 5. If something goes wrong | Login, OTP and review problems, and when to involve your manager                                 |


---

# 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/guides/help.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.