Mainland China In-Person POS Acquiring Guide
Compare pricing structures, POS features, onboarding, settlement, and risk controls for major in-person acquiring options in Mainland China.
For in-person payments in Mainland China, compare licensed acquiring routes on the actual merchant entity, industry, transaction mix, settlement, devices, reconciliation, risk controls, and integration—not a headline rate. The final fee and capability come from the acquirer's written offer and merchant account.
This guide supports system planning and provider comparison. It is not financial or legal advice, and Wavesteam does not provide payment clearing.
1. Decide the money path before choosing a terminal
| Route | Strong fit | Main benefit | Main limitation |
|---|---|---|---|
| Bank merchant acquiring | Established merchant seeking a direct banking relationship | Account and settlement integrated with the bank | Product, API, and service capability vary by branch and offer |
| Licensed acquiring institution | Retail, hospitality, services, and multi-location merchants | Broad acceptance, terminals, reconciliation, and operations | Pricing and risk controls are merchant-specific |
| WeChat Pay or Alipay merchant products through an approved route | QR and mini-program journeys | Familiar customer experience and mature digital integration | Entity, product, category, and scenario restrictions |
| Aggregated technology interface | A system needs one technical layer over approved channels | Unified order, callback, and reporting integration | The technology provider must not become an unlicensed fund pool |
Confirm the contracting merchant, merchant IDs, settlement account, store structure, supported transaction types, refund source, settlement cycle, fees, reserves, and dispute handling. An attractive QR product does not authorize a software company to collect customer funds and distribute them manually.
2. Normalize the quote
Ask each licensed provider for the same business profile: industry and license, cities and stores, monthly volume and count, average and maximum transaction, payment mix, refunds, peak periods, device quantity, API needs, and settlement expectation. Wavesteam organizes this comparison; the client confirms the business facts and chooses the commercial offer.
Compare:
- percentage and fixed transaction charges, including special card or channel treatment;
- terminal purchase, rental, deposit, SIM/network, paper, and replacement;
- settlement timing, withdrawal, reconciliation files, and bank-account requirements;
- merchant onboarding, store and sub-merchant management, and industry restrictions;
- refund, reversal, cancellation, partial refund, and dispute behavior;
- API/SDK, callback signatures, sandbox, rate limits, and support;
- risk holds, reserves, delayed settlement, and termination or migration.
A low percentage can be offset by device, service, or settlement costs. A bundled “zero fee” should be checked for product period, eligible volume, account conditions, and what happens after the promotion.
3. The business system still needs a payment ledger
The server creates the order and payable amount, never trusting a client-supplied total. Every attempt has a unique ID. Channel callbacks are verified and idempotent; a browser success page does not settle the order. Refunds and reversals retain independent states.
Reconcile daily among:
- business orders and internal payment entries;
- internal entries and acquirer statements;
- acquirer settlement and bank receipt.
Classify unmatched amounts, duplicates, fees, refunds, and date differences. The objective is zero unexplained money difference—not necessarily identical raw row counts.
For a chain, preserve entity, brand, store, terminal, cashier, business date, order, channel transaction, refund, fee, and settlement batch. Head-office reporting must drill back to these records.
4. Devices and offline operation need explicit tests
Evaluate countertop and mobile POS, QR scanners, printers, sound boxes, soft POS where available, and integration with cashier or ERP. Test weak network, repeated taps, callback delay and reorder, power loss, printer failure, day close, refund, and account or terminal replacement.
Offline payment acceptance, where offered, has separate amount, card, risk, and upload conditions. It is not a general promise that every QR or card transaction works without a network. The provider's official product and agreement control.
5. Security and responsibility
Keep production keys and certificates in managed secrets, separate test and production, use MFA and least privilege, and separate refund initiation from approval for material amounts. Support staff should inspect order status without editing ledger history. Avoid storing card authentication data that the business does not need.
Wavesteam implements order orchestration, channel integration, access, reconciliation, monitoring, and migration. The licensed bank or acquirer owns merchant approval, payment processing, settlement, pricing, and its platform behavior. The client owns its qualifications, merchant and bank accounts, products, and business decisions.
The deliverable should include the provider comparison, money-flow diagram, API proof, state model, reconciliation cases, device test report, operational runbook, and a fallback route. A terminal demonstration alone is not production acceptance.
This article is for merchant acquiring and system planning only. Final pricing and capabilities are governed by the licensed acquirer's agreement and current regulations.