Payment
PromptPay, card, and bank slip in one flow.
What it does
Members pay the way they already pay — PromptPay QR, card, or bank transfer with a slip. Payment unifies all three behind one flow so the member doesn’t pick a method by jargon, and the admin doesn’t reconcile across three systems.
Key features
- PromptPay QR — Generated per order with the right amount baked in.
- Card payments — For members and guests who’d rather pay by card.
- Bank slip with auto-verification — Slip uploads land on the order and verify themselves.
- One order, one status — Regardless of method, the member sees a single “paid / pending / failed” state.
- Refunds in the same flow — Refunds owed are surfaced on the member’s order screen, not in a back channel.
- Receipts — A clean receipt is generated and stored against the order; the member can download it any time.
How it works
The member places an order — for an event, a shop item, dues, anything billable — and lands on a payment screen. They pick PromptPay, card, or bank slip. The flow handles the rest: QR code, card form, or upload. As soon as payment lands and verifies, the order updates and the member moves on.
Behind the scenes, every payment is attached to the order it belongs to. The admin sees revenue per module, per event, per cycle, with no spreadsheet stitching. When something goes wrong — a wrong amount, a duplicate transfer, a refund — the resolution stays attached to the same order.
