Let every server be a terminal. Let every iPad be a point of sale.
Restaurant platforms in APAC live and die by turn time. Tapped puts certified contactless payments inside your POS, no leased terminal, no reconciliation across two vendors, no six-week hardware wait. Settle in the server's hand.
Used by ordering platforms, full-service POS, QSR back-office, ghost-kitchen rollups, and hospitality SaaS across APAC.
The four ways Tapped fits the restaurant pos flow.
A generic payments API doesn't know where the tap should happen, when the authorisation should hold, or how the tip should split. These are the things we built for your vertical specifically.
Pay-at-the-table without hardware
Servers tap a guest's card on the ordering iPhone or iPad they already carry. No POS terminals to lease, no PED replacement cycle, no batch reconciliation at 2am.
Split checks in-line with orders
Our SDK handles tips, splits, item-level voids, and open tabs natively, all wrapped in a single authorisation the scheme recognises. Your POS emits one intent; we emit one clean transaction.
Tip capture & gratuity-pool payouts
Tap Ledger separates gratuity from principal at authorisation time, holds it in a gratuity sub-account per venue, and payouts nightly to a staff-pool account. Your operators stop hand-cutting cheques.
Kiosk & counter modes
Same SDK, three form factors: server-held, counter-fixed, and unattended kiosk. Certified independently so your QSR and full-service operators share one stack.
Kanpai.POS, 4,800 stores live.
We were about to sign a hardware deal for 3,000 PEDs. Tapped made it unnecessary in a single weekend of integration, our servers tap on the same iPad they already carry orders on.
Questions restaurant pos platform teams actually ask us.
We get them on every call. If yours isn't answered here, the sales team has the longer version.
How quickly can we go live in production?+
Median go-live from sandbox key to first production tap across restaurant pos platforms is 12 days. Fastest to date was 9 days (OrbitSalon); typical range is 2–4 weeks depending on how deeply you want sub-merchant onboarding embedded.
Which acquirers / PSPs do you route to?+
Tapped Onboard is PSP-agnostic. Your sub-merchants end up routed to Stripe, Adyen, Airwallex, or a local sponsor bank depending on market, card type, and cost, you see one API and one blended rate; we handle the routing.
Do we need to become a payment facilitator?+
No. Tapped operates as the PayFac under its own MAS / BSP / BNM (etc.) licences per market. You're a distribution platform, not a regulated entity. The regulatory surface sits with us, not you.
Can we offer our own platform fee on top of tap-to-pay?+
Yes. You set a take rate per merchant (or per transaction type), Tapped settles to you the spread net of interchange+ and our platform fee. Most restaurant pos platforms see 30–60 bps margin on card volume.
What about refunds, disputes, chargebacks?+
Full dispute API with automated evidence packaging from the metadata you pass at authorisation. Dispute win rate across the restaurant pos vertical was 68% in 2025, materially above the scheme average of 43%.
See the restaurant pos sandbox in 20 minutes.
Walk a sales engineer through your integration goals; leave with a sandbox key, a shortlist of the three highest-impact endpoints for restaurant pos, and a 12-day go-live plan.