> 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-8-warm-up.md).

# 8. Warm-up

Every payment processor needs a warm-up period. Follow the schedule for your processor — this is where replacement eligibility is won or lost.

{% hint style="danger" %}
Written warm-up instructions come with every setup and must be followed strictly. Replacement eligibility applies **only** if the warm-up instructions were followed.
{% endhint %}

## Pick your guide

<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-credit-card" style="color:$primary;">:credit-card:</i></h4></td><td><strong>Stripe</strong></td><td>14-day rest, demo week, growth schedule, card strategy, credential changes.</td><td><a href="/guide/guides/stripe-warm-up.md">Stripe Warm-Up Guide</a></td></tr><tr><td><h4><i class="fa-bag-shopping" style="color:$primary;">:bag-shopping:</i></h4></td><td><strong>Shopify Payments</strong></td><td>New environment, store requirements, new bank account (with screenshots), growth schedule, profile structure.</td><td><a href="/guide/guides/shopify-payments-warm-up.md">Shopify Payments Warm-Up Guide</a></td></tr><tr><td><h4><i class="fa-paypal" style="color:$primary;">:paypal:</i></h4></td><td><strong>PayPal</strong></td><td>Rep contact, warm-up amounts, tracking, disputes, PayPal reviews.</td><td><a href="/guide/guides/paypal-warm-up.md">PayPal Warm-Up Guide</a></td></tr></tbody></table>

## Universal rules (all platforms)

| Rule                  | Detail                                                                                                                                                                  |
| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| One proxy per service | Never mix proxies between different payment processor accounts                                                                                                          |
| One email per company | Use one company email (e.g. `info@yourdomain.com`) for all services of that company. Never reuse an email for the same service if the previous account there was banned |
| One phone per company | One number for all services of that company (bank, PayPal, Stripe, Shopify Payments). Never share a number between companies                                            |
| No personal numbers   | Use [Krispcall](https://try.krispcall.com/d0ye9ovwwn8s) / Quackr                                                                                                        |
| No personal bank      | Never send funds from the nominee account directly to your personal bank                                                                                                |
| Update credentials    | Within 3 weeks of receiving access ([Step 7](/guide/setup-steps/step-7-credentials.md))                                                                                 |
| Payouts               | **Manual** payouts on all platforms **except Shopify Payments** — set Shopify Payments to **daily**                                                                     |
| Non-linear growth     | Never grow revenue linearly — use realistic ups and downs                                                                                                               |

## Key numbers

| Processor            | Start                                                         | First milestone                             | Key rule                                                                         |
| -------------------- | ------------------------------------------------------------- | ------------------------------------------- | -------------------------------------------------------------------------------- |
| **Stripe**           | Rest 14 days after creation, then demo week: $500–1,000 total | Pause 7 days → request the first payout     | Never below €500 / 3–4 average order values; credit cards only, Tier-1 countries |
| **Shopify Payments** | Demo week: $500–1,000 total                                   | — (daily payouts, no pause)                 | Proxy = company country; new email and new bank account — never reused           |
| **PayPal**           | $100–200/day in week 1, credit cards only                     | Minimum 3–4 weeks of warm-up before scaling | Keep 7–10% of monthly volume as a balance reserve                                |

## If a platform requests a review

Contact your manager **immediately** — before submitting anything. Do not submit documents without consulting us first.

## Done when

* [ ] Demo week completed; first payout received (Stripe, PayPal)
* [ ] Growth stays within the weekly caps of your guide
* [ ] Balance reserve maintained

You are live. Keep following the ongoing rules in your guide, and use the [Help Center](https://help.basiq-solutions.com/help-center/) when something changes.


---

# 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-8-warm-up.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.