Stripe and payments

Why Stripe?

Card payments are serious infrastructure — vaulting card numbers, 3-D Secure, fraud screening, payouts. Platypus doesn't reinvent any of that: every payment is processed by Stripe, and specifically by the venue's own Stripe account.

What that means for buyers

When you buy a ticket, your card details go to Stripe, never to Platypus, and the charge is made by the venue itself — it's the venue's name on your statement, the venue's refund to give. Checkout happens right on the event page (or inside the venue's own website when embedded), card step included, and your tickets arrive by email as a PDF.

What that means for venues

• You need a Stripe account with charges enabled — free to create; Stripe's per-transaction fees apply as with any Stripe business.
• You paste restricted API keys into the Platypus admin and Platypus verifies them before anything is stored (encrypted). Setup is a five-minute guided page: Stripe payments setup.
• Refunds are handled in your Stripe dashboard today — you have full merchant control.
• Stripe's test mode works end to end, so you can rehearse a purchase with a test card before going live.

Does Platypus touch the money?

No. Ticket revenue settles from Stripe to the venue's bank account directly. Platypus bills the venue separately — a flat subscription plus $1 AUD per ticket sold (details).

What's coming

A hosted onboarding option (Stripe Connect) is on the roadmap — venues would click through Stripe-hosted setup instead of creating and pasting keys, and gain in-app refunds. Current status: Features & roadmap.