China versus Global Users: How Cross-Border Payment Needs Differ
When someone asks which payment platform is best, the answer depends heavily on where they stand. On the same platform, a mainland China seller, a Hong Kong entity seller and a local US seller may get different features, different fund paths and different tax obligations. This article starts with the three variables that decide everything, then looks at how each audience actually operates.
1. Three things determine what you can use
1.1 Entity eligibility
Requirements about the merchant's registered location are hard rules that do not bend for business quality. Some international acquirers require an entity in Hong Kong, Singapore, the US or Europe, so mainland China companies cannot sign up directly, while collection-account services aimed at cross-border sellers generally accept China-based entities.
1.2 Whether funds can return compliantly
Collecting money is only step one. Whether it can come back to an account you control, compliantly and at reasonable cost, is the real question. That involves settlement paths, cross-border RMB, offshore bank arrangements and whether the provider holds the relevant licences. A stable money path deserves priority over a fee difference.
1.3 Who carries the tax liability
Sales tax on physical goods is comparatively straightforward. For digital products and SaaS sold across countries, registration, filing and remittance of VAT and sales tax is ongoing work. Either build the capability yourself, or choose a merchant-of-record model where the platform acts as legal seller.
2. China-based users: plenty of options, two hard constraints
2.1 Common entity and platform combinations
- Mainland entity plus collection platforms: PingPong, WorldFirst, Payoneer and Airwallex support China-based sellers and suit marketplace stores plus some DTC acquiring needs.
- Hong Kong or Singapore entity plus international acquiring: the usual route to acquirers such as Stripe, at the cost of maintaining offshore bookkeeping, audit and tax.
- US entity: suited to SaaS aimed at the US market, but with the heaviest compliance and filing burden.
2.2 How to structure the money path
Marketplace funds usually flow from the platform to a collection account and then settle domestically. DTC funds flow from the acquirer to an offshore bank account or collection account before settlement. Both paths need buffer time for funds in transit, so do not plan ad budgets on same-day arrival.
2.3 Three things China-based users should watch
First, entity and business must match: inconsistencies between registered information, listed categories and actual shipping origin are the most common trigger for risk reviews. Second, keep dispute rates under control: cross-border e-commerce dispute rates run naturally higher, and support responsiveness plus refund policy are the most effective relief valves. Third, do not park funds on a single platform, because the working capital risk of a hold outweighs any fee difference.
3. Global users: more choices, different pitfalls
3.1 Local payment methods drive conversion
European payment habits are highly fragmented: iDEAL in the Netherlands, Bancontact in Belgium, high SEPA direct debit usage in Germany and the Nordics, and buy-now-pay-later with meaningful penetration in some markets. Offering only international cards gives away conversion. See Buy Now Pay Later Comparison for options.
3.2 Combining acquiring and wallets
The common Western setup is card acquiring plus a wallet in parallel: cards through Stripe or an equivalent acquirer, with PayPal shown alongside as a familiar choice. That balances fees and conversion; see Stripe Pros and Cons for how the two differ.
3.3 Plan tax early
EU VAT, US state sales tax and post-Brexit UK rules all trigger registration once thresholds are crossed. Digital products and SaaS that do not plan to build tax capability are better served by an MoR model.
4. A second layer: by business model
4.1 Physical e-commerce DTC
Approval rates and chargeback control dominate. Cards as the primary method, wallets as support, collection accounts for multi-currency aggregation.
4.2 Digital products
Instant delivery with no shipping evidence makes chargeback defence difficult, so MoR platforms or acquirers with strong risk tooling fit better, and tax gets solved along the way.
4.3 SaaS subscriptions
Depends on subscription billing, retry strategy and invoicing. A mature system such as Stripe Billing cuts build cost substantially; see Subscription Billing API Integration.
4.4 Marketplace sellers
Acquiring happens on the platform, so sellers mainly need payout aggregation and settlement efficiency, with coverage of the marketplaces they sell on as the key metric.
4.5 Large B2B
High value and long cycles mean bank transfers and letters of credit still dominate, with payment platforms handling collection notification and reconciliation. See Payment Transaction Flow Basics.
5. Six general recommendations
- Settle the entity question before comparing platforms; the reverse order wastes time.
- Keep at least one backup collection path so a single restriction does not stop operations.
- Put settlement timing into your cash flow model instead of treating it as a backend detail.
- Write dispute and refund processes before launch; retrofitting them costs far more.
- For multi-country selling, local payment methods and tax compliance outrank fee optimisation.
- Calculate fees against your own order values and regional mix; fixed fees hurt small tickets most.
For the full role comparison see the Cross-Border Payment Selection Matrix, and for PayPal operations see the PayPal Cross-Border Payments Guide. More payment options are listed under Payment.
Source: 16IDC original. Product capabilities, pricing and eligibility requirements follow stripe.com / www.paypal.com / www.airwallex.com and related official documentation and contract terms.