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

# Stripe Warm-Up Guide

Environment, demo week, revenue schedule, card strategy and credential changes for Stripe.

{% hint style="danger" %}
Read this fully before accepting any payments. Not following these rules is the primary reason for holds and bans. Replacement eligibility is void if warm-up rules are not followed.
{% endhint %}

## 1. Store requirements

{% hint style="info" %}
Your placeholder store is built by Basiq as part of the setup — you do not need to create it yourself. The list below is what the store must contain; keep all of it if you edit or replace the store later.
{% endhint %}

* A homepage (Funnelish or Shopify) with basic branding
* 3 compliant beauty products (non-health) — e.g. skincare, cosmetics — each linked to its own funnel
* A footer with business details (email, address, legal info)
* **Policy pages (required):** Privacy Policy, Terms of Service, Refund Policy, Shipping Policy

## 2. Environment — always

* ✅ Access Stripe only through [OctoBrowser](https://octobrowser.org/signup/?p=10266582) + a nominee-country mobile proxy ([a-socks](https://asocks.com/c/5eB0tn) — see the [a-socks guide](/guide/guides/proxy-guide/a-socks.md))
* ✅ Set payouts to **Manual** from day one
* ✅ Payouts must go to your business bank (Airwallex / Wise / WorldFirst)
* ❌ Never use the same proxy as another Stripe account
* ❌ Never use the same email as another Stripe account
* ❌ Never change your Stripe email — the account will be flagged permanently

## 3. Initial access rules

Do **not** change immediately after receiving the account:

* Password
* 2FA device

Changing these right away risks instant suspension. Wait for gradual changes after selfie verification (section 7).

## 4. Pre-revenue phase

Let the account rest for **14 days** after creation before accepting any payments.

## 5. Revenue warm-up

### Demo week

{% stepper %}
{% step %}

#### Accept $500–$1,000 in total

{% endstep %}

{% step %}

#### Pause — do not accept new payments for 7 days

{% endstep %}

{% step %}

#### During the pause, request your first payout

{% endstep %}

{% step %}

#### After a successful payout to your bank → continue

{% endstep %}
{% endstepper %}

{% hint style="warning" %}
This protects you: if the account is blocked, frozen funds stay locked for 120–180 days. If no payouts were ever made, all money is returned to customers.
{% endhint %}

### Growth schedule

| Timeframe | Daily revenue cap        |
| --------- | ------------------------ |
| Weeks 1–2 | $0–$300/day (non-linear) |
| Weeks 3–5 | $500–$800/day            |
| Weeks 6–9 | $1,000–$2,000+/day       |

Avoid linear daily growth — Stripe flags this. Use realistic ups and downs like a real startup. Maximum increase: +20–30% per week.

## 6. Payments & card strategy

**Before selfie verification**

* ✅ Tier-1 cards only: US, UK, Canada, Australia, EU
* ❌ No Tier-2 or Tier-3 card payments
* ❌ No iDEAL, Bancontact, SEPA or Klarna in the first 2–3 weeks

**After selfie verification**

* Gradually introduce Tier-2/Tier-3 payments
* Maximum 5–10% of total volume from Tier-2/3 cards

**Recommended warm-up markets**

| Market        | Method      | Notes                           |
| ------------- | ----------- | ------------------------------- |
| France        | Credit card | Stable, good volume             |
| Denmark       | Credit card | Low risk                        |
| French Canada | Credit card | Strong market                   |
| Sweden        | Credit card | High Klarna risk — scale slowly |

## 7. Credential change sequence (after selfie verification)

Never change both credentials on the same day.

{% stepper %}
{% step %}

#### Change the password

{% endstep %}

{% step %}

#### Wait 2–3 days → change 2FA (use your company's phone number)

{% endstep %}
{% endstepper %}

## 8. Absolute don'ts

| Rule                        | Detail                                                                                         |
| --------------------------- | ---------------------------------------------------------------------------------------------- |
| Never leave a $0 balance    | Always keep 3–4 average order values in the Stripe balance (never less than €500)              |
| No local methods early      | No iDEAL, Klarna or P24 in the first 2–3 weeks                                                 |
| No production test payments | Use test keys and the test card `4242 4242 4242 4242`, any future expiry date, any 3-digit CVC |
| No login sharing            | Invite collaborators via **Settings → Team**                                                   |

## 9. If Stripe requests a review

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


---

# 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/stripe-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.