Gather Workshop
Workshop × course registration
Register, pay, confirm — one page, three minutes
Speculative scenario: Gather Workshop runs 4–6 craft sessions per month. Google Form for registration, manual LINE confirmation, bank ATM for payment, manual screenshot matching. One registration = 10 minutes of admin work. Refunds and reschedules handled one by one via DM. The more popular the course, the heavier the admin load.
A dedicated course landing page: course info and instructor on the left, enrollment card on the right. Session selection + online payment in one step. Automatic confirmation email + LINE reminder on completion. Admin sees live registrant list, one-click export, automatic reschedule notifications. Admin overhead per registration: from 10 minutes to zero.
Register and pay on mobile in three minutes — no screenshot, no bank account
Session → details → payment → submit — all in one screen. Confirmation email and LINE notification sent instantly on completion, no waiting for the host to manually reply. First-timer discounts and group pricing calculated automatically at checkout.
Registration and payment in one step
Split flows — form first, payment later — lose people at every step. Integrated payment means "registered" equals "paid." Host never waits for a screenshot; student never hunts for a bank account number.
Real-time availability
Each session shows live remaining spots — no manual editing of form descriptions. When a session fills, registration auto-closes and a waitlist option opens. Zero manual intervention.
Already have a payment account? Share the credentials and we connect it. Starting from scratch? We walk you through the application.
Supported methods: credit card (Visa / Mastercard / JCB), ATM transfer, convenience-store code, LINE Pay, JKO Pay — students pay however they are used to, no account numbers to copy, no extra app to install. If you already have an ECPay or NewebPay merchant account, just share the merchant ID and API key; we complete integration and sandbox testing within two business days. No account yet? We help prepare the application documents (company registration or individual seller info), submit the review form, and stay with you until the account is approved — no need to figure out the rules yourself. Payment results are delivered via Webhook rather than front-end polling, so even if a student closes the browser right after paying, the server receives the notification, locks the seat, and sends the confirmation email without missing a beat.
We handle the application, not just the integration
Opening a payment merchant account is where non-technical clients get stuck most often: document requirements are fussy, review timelines vary, sandbox and production configs differ. We have a complete application-support SOP — from document prep to sandbox testing to go-live — cutting the back-and-forth.
Webhook ensures no payment goes missing
Front-end polling for payment confirmation drops orders on unstable connections. We receive payment results via provider-pushed Webhooks with idempotency guards to prevent double-charges, keeping payment status and the registrant list permanently in sync.
Multiple methods, student chooses
Card-only checkout loses older students who avoid online card transactions; ATM-only frustrates younger ones. Offering credit card, ATM transfer, and convenience-store code together means students of any age complete payment without friction.
What this build would use
- Next.js 15
- Supabase (PostgreSQL)
- ECPay
- LINE Messaging API
- Resend
- Google Calendar API
- Vercel