> 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/help-center/faq/warm-up-and-scaling.md).
# Warm-up & scaling
How long warm-up takes, how fast you can grow, which cards and countries first, and how much to keep in the balance.
Why is warm-up mandatory?
Every payment processor scores new accounts on their first weeks of activity. Small, realistic, non-linear volume builds trust; a sudden jump triggers reviews, holds and bans. Written warm-up instructions come with every setup, and replacement eligibility applies only if they were followed.
How long does warm-up take?
* **Stripe** — 14 days of rest after creation, then a demo week ($500–1,000), a 7-day pause with the first payout, then a 9-week growth schedule.
* **Shopify Payments** — demo week ($500–1,000) with payouts on daily — no pause — then the same 9-week schedule.
* **PayPal** — a minimum of 3–4 weeks before scaling; $5,000–10,000/day only after a stable month of history.
Guides: [Stripe](/guide/guides/stripe-warm-up.md) · [Shopify Payments](/guide/guides/shopify-payments-warm-up.md) · [PayPal](/guide/guides/paypal-warm-up.md).
Can I grow faster if sales are good?
No. Stay within the daily caps of your guide and increase by no more than 20–30% per week, with realistic ups and downs. Linear growth is exactly what gets flagged.
Why does the first payout matter so much?
If an account is blocked before a payout was ever made, all money is returned to customers; frozen funds stay locked for 120–180 days. On Stripe, the demo week → pause → first payout sequence proves the payout route works while the amounts are still small. Shopify Payments stays on daily payouts, so money leaves the balance continuously and no pause is needed.
Which payout mode should I use?
**Manual** on every platform (Stripe, PayPal, banks) — you request payouts yourself and never leave a $0 balance on Stripe. The one exception is **Shopify Payments: daily** payouts.
Which cards and countries first?
Credit cards only, from Tier-1 countries (US, UK, Canada, Australia, EU). Recommended warm-up markets for Stripe: France, Denmark, French Canada, Sweden (slowly — Klarna risk). Tier-2/3 cards only after selfie verification and at most 5–10% of volume.
When can I enable Klarna, iDEAL or Bancontact on Stripe?
Not in the first 2–3 weeks — no iDEAL, Bancontact, SEPA, Klarna or P24 on Stripe during that period. Introduce them gradually after selfie verification.
How much should I keep in the balance?
Stripe: never a $0 balance — keep 3–4 average order values and never less than €500. PayPal: keep 7–10% of monthly volume as a reserve; do not withdraw everything.
What products can I sell during warm-up?
Compliant beauty products (non-health) — skincare, cosmetics — with accurate product pages and complete policy pages. Restricted products or prohibited business activities void replacement eligibility.
What do I tell my PayPal rep?
Contact the rep before the first sale, using the nominee name. Declare €20,000/month TPV in HKD. Upload tracking numbers for every order from day one (Trackipay / Trackipal) and reply to any dispute within 24 hours. Details: [PayPal Warm-Up Guide](/guide/guides/paypal-warm-up.md).
---
# 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/help-center/faq/warm-up-and-scaling.md?ask=&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.