Stripe, Airwallex and Cross-Border Payment Account Opening Guide
Compare account requirements and settlement routes for Stripe, Airwallex, Wise Business, Payoneer, WorldFirst, and PayPal, including repatriation to Mainland China and local overseas settlement.
Do not choose a cross-border payment account from brand recognition alone. First align the operating entity, website or product, customer countries, payment methods, settlement bank, currencies, tax and contract evidence, and the route by which funds stay overseas or return to Mainland China.
Stripe, Airwallex, Wise Business, Payoneer, WorldFirst, and PayPal serve overlapping but different payment, collection, and treasury needs. Product availability, onboarding, pricing, reserves, and transfer routes vary by registered entity and corridor. Wavesteam can design and integrate the system; the provider decides account approval and regulated money movement.
1. Separate checkout, collection, and business banking
| Need | Typical product category | Key question |
|---|---|---|
| Accept cards or local methods on a website/app | Payment gateway/acquiring | Is the merchant entity and business category supported in the selling markets? |
| Receive marketplace or B2B transfers in several currencies | Collection accounts | Are local account details available for the entity and payer type? |
| Hold, convert, and pay suppliers | Multi-currency business account | Which currencies, beneficiaries, controls, and fees are available? |
| Move funds to Mainland China | Provider conversion/withdrawal and receiving bank | What purpose, documents, limits, FX, and bank review apply? |
| Keep funds for overseas costs | Overseas business bank or eligible provider balance | Does the entity have a lawful operating and tax purpose for retention? |
One provider may cover several rows, but an account that receives marketplace payouts is not automatically an ecommerce card gateway, and a payment gateway is not automatically a full business bank.
2. Prepare a consistent onboarding evidence pack
Providers commonly request the legal entity and registered address, directors and beneficial owners, identity and address evidence, tax and registration numbers, bank account, website or app, product and pricing, refund and delivery policies, expected countries, currencies, volume and average ticket, supply or fulfillment evidence, and source of funds.
The site, contract, invoices, fulfillment, payment descriptor, and bank beneficiary should tell the same business story. Borrowing another entity's account or presenting a shell storefront creates freezes, reserves, tax uncertainty, and termination risk. Wavesteam maps the required fields and technical evidence; the client and advisers confirm the lawful entity, tax, goods, and commercial arrangement.
3. Compare providers on the full money path
Build one matrix covering:
- supported entity countries, customer countries, currencies, and methods;
- onboarding, review time, prohibited/restricted activities, and ongoing checks;
- card/local-method charges, FX markup, transfer, withdrawal, dispute, refund, and account fees;
- rolling reserves, delayed settlement, negative balances, and chargeback handling;
- settlement accounts, beneficiary names, local account details, and transfer purpose evidence;
- API, hosted checkout, webhooks, connected/platform accounts, reconciliation, and sandbox;
- account ownership, team roles, MFA, logs, termination, export, and backup provider.
Do not compare a Hong Kong public card rate with a Mainland China B2B collection quote as if they were the same transaction. Currency, payment method, card origin, entity, volume, and negotiated terms matter. Recheck official pricing and the logged-in offer before contracting.
4. Repatriation and overseas retention are business decisions
For funds returning to Mainland China, identify the receiving entity and bank, trade or service purpose, contract, invoice, customs or delivery evidence, taxes, currency conversion, and expected frequency. The payment provider transferring funds does not guarantee that the receiving bank accepts every purpose or document.
Keeping funds overseas can support advertising, suppliers, payroll, tax, and refunds, but requires an appropriate entity, account, accounting, and authorization. Do not leave material balances at a payment provider solely because the interface allows it; assess safeguarding, deposit protection where relevant, concentration, access continuity, and a second route.
5. Design the application so the provider can change
The business system owns order, customer, invoice/evidence, fulfillment, refund, and accounting references. A payment adapter maps provider customer, intent, charge, transfer, payout, fee, dispute, and balance events without replacing internal business truth.
Verify webhooks, use idempotency, preserve raw events, and reconcile provider transactions to internal orders and bank payouts. Never use a browser success page as settlement proof. Keep provider keys in managed secrets, grant least privilege, and ensure the client entity owns the production account.
Wavesteam delivers the entity and money-flow diagram, provider matrix, onboarding evidence checklist, API proof, payment state model, reconciliation design, data responsibilities, and fallback/migration plan. Our cross-border ecommerce guidance can inform the wider store architecture, but final approval, pricing, tax, foreign-exchange treatment, and bank acceptance remain with the responsible institutions and professional advisers.
This article is for payment and system planning only and is not legal, tax, foreign-exchange, or financial advice. Verify current requirements with each provider, bank, and relevant authority.