E-commerce, affiliates and crypto on an infrastructure of neobanks and crypto exchanges — how to route money so Wise and Stripe last, and reviews pass cleanly.
The closure came from mixing compliance-“clean” and compliance-“noisy” flows on a single account. Wise won't disclose the reason, but a combination fired:
Business-to-Personal (B2P). A corporate EMI account is for B2B settlement only. Recurring payouts to affiliates' personal IBANs are red flag #1. On top of that, money coming into Wise almost always has to arrive under a matching name.
Geographic deviation. Activity was declared as EU-only at sign-up. A sudden payment to China plus a Hong Kong IBAN request, with no prior profile update, reads to the models as a shift into higher-risk activity.
Wise as “core banking.” Wise is an EMI built for transit cross-border flow — not for holding balances or running complex payout infrastructure. The usage didn't match the product, and after its regulatory remediation Wise became markedly stricter.
Takeaway: fix the architecture — don't go hunting for a “more tolerant” EMI.
Stability doesn't come from evading checks — it comes from passing them effortlessly. Every payment should read in a minute as “who, to whom, for what, under which contract, with which document.” Then a review closes in a day instead of becoming a freeze. With no classical banks in the picture, resilience comes from duplication and isolation: money moves in one direction, and each service does exactly one job.
Every account sits on the same company, same UBO, full KYB, declared flow. A separate reserve EMI per function (second anchor / crypto corridor) is about resilience and profile-fit — not about distancing money from oversight.
| Rail | Job | Providers |
|---|---|---|
| Rail 01 Acquiring | Card B2C intake, auto-payout to an anchor | Stripe |
| Rail 02 Anchor Hub | Core hub: Stripe + direct SEPA B2B/B2C, budget distribution. Two co-anchors for resilience | Airwallex + Wise Business (co-anchors; Wise = clean commerce only, see §W); Revolut as reserve |
| Rail 03 Suppliers | Pay for goods into China / HK | Airwallex or Payoneer |
| Rail 04 Affiliates | Commission payouts to individuals | Dedicated mass-payout gateway (PayPal Business, Volet) |
| Rail 05 Crypto | Fiat → crypto conversion | Kraken / Bitstamp / Binance Corporate |
The whole point of the rebuild is for Wise and Stripe to last. What killed Wise wasn't the “core account” role itself — it was the wrong flows running on it: affiliate B2P payouts, crypto next door, undeclared Asia, large balances. Take those flows off, and Wise sits comfortably alongside Airwallex as a second co-anchor. That also satisfies the §5 rule “always keep two active EMIs”: two warmed co-anchors mean that if one goes into review, the other picks up Stripe settlement within a day.
House Rule (non-negotiable): Wise = commercial counterparties only — client receipts in, supplier / contractor payments out. Owner money (salary, dividend, director's loan, any personal draw), individual affiliates and crypto never touch Wise. This is stricter than the rules strictly require, costs almost nothing, and means Wise never sees a transaction it could misread as fund-mixing.
Automated systems score deviation from profile and typology match, not intent. The goal of a warm-up isn't secrecy — it's making sure legitimate activity doesn't accidentally look like a flagged pattern and trip a false positive.
| Flagged pattern | How not to resemble it |
|---|---|
| Structuring / smurfing — amounts sized just under a threshold | Pay real invoice amounts; never split one invoice across multiple transfers |
| Pass-through — money in, ~100% straight out, nothing retained | Let funds settle and sit briefly; don't sweep every inflow out the same hour |
| Profile spike — activity jumps above declared turnover | Ramp gradually (below); raise the declared turnover before you exceed it |
| Round-number, reference-less transfers | Attach an invoice number / clear reference to every transfer |
| Name mismatch — counterparty ≠ invoice party | The name on the transfer matches the invoice party exactly |
| Third-party funding — topped up by not-you / not-the-company | Only the company funds the account, from the company's own account |
| EMI→EMI churn — funds bouncing between fintechs | Fund from a real bank; pay out to real banks |
| Dormant-then-burst — quiet, then a large payment | Keep steady, regular activity once live |
| Geography / sanctions exposure | Screen counterparties; exclude sanctioned jurisdictions entirely |
A new account is watched hardest in the first 60–90 days. The point is to build a track record before running at full volume. Anchor math for a ~€200K/month run-rate (≈ €50K/week ≈ ~€6.7K/day). Bands below are % of run-rate; scale to any turnover the same way.
| Weeks | % run-rate | € / week | Max single txn | Phase focus |
|---|---|---|---|---|
| 0 · days 0–3 | — | — | — | Full verification; declare €200K honestly; category = registered activity; EUR + SEPA; backup account live |
| 1–2 | 10–15% | €5K–7.5K | ~€10K | Clean baseline: 3–6 small documented supplier payments, 1–2 client receipts |
| 3–4 | 25–35% | €12.5K–17.5K | ~€20K | Recurring flows: monthly suppliers, normal client invoicing |
| 5–6 | ~50% | ~€25K | ~€30K | First larger payment (€30–40K) from ~week 6 — only against a contract, a known counterparty |
| 7–8 | 65–75% | €32K–37.5K | ~€40K | Counterparty list should look stable and repeating, not a churn of new names |
| 9–10 | ~85% | ~€42.5K | docs-gated | Near-full run-rate |
| 11–12 | 100% | ~€50K | docs-gated | Full run-rate; the 90-day record is now your protection |
To scale above €200K/month later — update the declared turnover first, then ramp the excess the same way.
On funding under a “neobanks-only” constraint. The cleanest warm-up funds from a real bank (SEPA / PISP) — which also clears the third-party funding and EMI→EMI churn flags. With EMI-only, funding from an established EMI is second-best: avoid rapid EMI→EMI churn and keep one stable source. A single bank rail dedicated to funding and owner-draw would materially improve the warm-up of both co-anchors — worth reconsidering even if a bank is needed nowhere else.
Re-onboarding reality: Wise links accounts by profile; a previously closed OÜ is often declined on a fresh application — not guaranteed. Don't open a “second” Wise while the first is in closure. If you rebuild the relationship later, do it clean, with correct declarations, and on this house rule from the start. While Wise is unavailable, co-anchor B is temporarily carried by Revolut or a second Airwallex profile. The full week-by-week ramp and day-0 checklist live in Vol. 01 (Operations & Warm-Up); the block/recovery procedure in Vol. 02.
Rule: never send money from a core corporate account (Revolut / Airwallex) straight to affiliates' personal bank accounts.
Require larger affiliates to register as sole trader / freelancer / company. They invoice you, and you pay them as B2B counterparties from the core account, to an account in their own name. Contract + invoice = a document behind every payout.
Wallets that tolerate payouts to individuals (PayPal Business, Volet). You move a lump sum (invoice: “Affiliate payouts funding”) from the anchor to your corporate wallet, then mass-distribute to affiliates.
Only works if the wallet KYCs the recipients itself and provides reporting (ideally DAC7). Otherwise the buffer just relocates the “business → personal” problem to a more tolerant rail. For hundreds of small payouts, a regulated mass-payout provider is preferable.
The company pays the owner dividends or salary to their personal account — a legitimate Business → Personal move (personal income, personally taxed; for an OÜ, a profit-distribution event).
Dividends, yes. But then paying affiliates from the owner's personal account is commingling: the company loses the deduction, the trail is obscured, and the owner starts to look like a money-mule. Use C to draw money out to the owner, not as an affiliate payout channel.
If affiliates must be paid in crypto: via a licensed crypto processor or a corporate exchange account (e.g. Coinspaid / a corporate account), under contract and on the books — not from personal wallets.
Selling in Europe while sourcing from China is standard e-commerce — but the neobank has to know about it in advance.
Open an Airwallex account — a neobank built from the start for e-com and Asia, with local accounts in Hong Kong and China. Flow: Stripe → Airwallex EUR → convert to USD/CNY → pay the supplier. To Airwallex's models this is a normal operation. Alternative: Payoneer Business.
Pre-notify (before the first payment): message support — “We are expanding our supply chain to China. Expect B2B transfers to HK / Mainland. Invoices will be provided.” This turns an “anomaly” into “expected activity.”
Every payment sits behind an invoice / contract (goods, quantity, Incoterms). Screen counterparties and goods — especially dual-use — against sanctions lists.
Crypto is legal; the only problem is opacity. Most neobanks dislike transfers to exchanges (Revolut is more tolerant, but with limits), and Wise prohibits crypto business outright — so this needs a separate rail.
Critical rule — no P2P. Using a corporate account for P2P trading on Binance/Bybit will get it banned within a week and flagged for AML.
A natural operating rhythm is fine. But deliberately splitting payments to “not look like pass-through” is structuring: an AML offence and a red flag in its own right, not a defence against one. Don't fragment artificially — just pay against real grounds as they arise.
Based on the Wise Europe SA case — regulated in Belgium, escalation via Ombudsfin (not the UK FOS). For other EMIs the algorithm is the same; the regulator / ADR changes. First classify the hold — the strategy depends on the type.
| Type | Signals | Win it back? |
|---|---|---|
| A. Verification / review pause | Account still visible; a specific transfer paused; email asks for a named document (proof of address, invoice, SoF). | Yes, routinely. Provide exactly what's asked — resolves in ~3–7 business days. |
| B. De-risking / offboarding | Account closed “at our discretion”; they ask for an external bank account to return the balance; support “can't give more detail.” | Sometimes. An appeal can reverse it; if not, you still recover via the closure/refund process + escalation. |
| C. External law-enforcement hold | Prolonged freeze; they respond but won't explain; sometimes they don't ask for SoF (you may not be the subject). | Not by you, not now. A SAR/FIU process may be running; Wise is legally barred from explaining. Escalation preserves rights but can't force release. |
How to tell B from C: if they keep asking you for source-of-funds / purpose documents, you're likely the subject and it's a reviewable compliance matter (push hard on documents). If they've gone quiet-but-responsive with no explanation and stopped asking for anything, an external hold is more likely — escalation and patience, not more documents.
To: Wise Europe SA — Complaints
Re: Formal complaint — held funds, account [ID], [company / reg. no.]
On [date] my company's Wise account was [blocked/closed] and a balance of €[amount] and/or a transfer (ref [ID]) has been withheld. I have provided [documents + dates]. No adequate explanation has been given. Continued retention without a lawful compliance justification amounts to a failure to execute under PSD2. I request [release / written final response] within 15 working days, failing which I will escalate to Ombudsfin and, if necessary, pursue recovery, interest and consequential loss.
No 100% same-day transit; no deliberate splitting; every OUT sits behind a document.