Payments · shared across every kit
One payment setup.
Every kit can use it.
paykit generates your checkout — a PayNow QR, or your own payment link or QR — tracks who's paid, and never touches the money. Set it up once — qkit, and every kit after it, checks out through the same engine.
- cap on free transactions
- 0
- cap on free transactions
- to start
- $0
- to start
- payment setup, every kit
- 1
- payment setup, every kit
How it works
Infrastructure, not another dashboard to babysit.
- 01
Connect your payment method
PayNow (UEN or mobile), or your own payment link/QR. Set it up once — reused by every kit you run.
- 02
A kit requests a checkout
qkit (and later kits) asks paykit for a checkout — paykit builds it, the customer scans or taps to pay.
- 03
You confirm, it's done
Customer taps "I've paid," you confirm receipt from your dashboard. paykit tracks the status — it never holds the money.
Why paykit
Built to be the one payment engine, not another one.
One setup, every kit
A vendor has one payment setup, not one per kit. Connect it once in paykit and it's already there for qkit today, and for whatever kit launches next — no re-onboarding, no second config screen to maintain.
Never touches the money
Customers pay straight into your own account. paykit only renders the checkout and tracks status — no funds pass through it.
Proven, not brand new
The QR engine is the same one already live in qkit — extracted, not rewritten from scratch.
Free while you're small
Unlimited transactions and revenue stats, no card required. Pro adds refund tracking — $4.99/mo, once you're doing enough volume to want it.
FAQ