Stripe or PayPal: let your members pay how they want

Every “just take Stripe” argument runs into the same wall: some countries don't have Stripe, some members refuse to enter card details on a site they don't recognise, and some people just trust PayPal more. ClubCP supports both. You pick the one that fits your club; your members get a checkout that works.

How it works

Each club configures its preferred payment provider in admin settings. Once set, the appropriate checkout flow shows for both:

• Membership purchases: members pick a plan, get redirected to Stripe Checkout or PayPal, complete the payment, and their membership is created on return.
• Event ticket purchases: same flow, with adult and child counts factored into the total before checkout. Members on a paid tier can get a discount automatically applied.

Money goes straight to you

ClubCP never holds funds. Stripe and PayPal pay your club's account directly. That keeps the platform simple (no escrow, no payouts, no compliance overhead) and means your money is your money. You handle refunds, chargebacks, and tax obligations through the provider you already use.

When something goes wrong

Payment edge cases are nasty: PayPal captures that succeed but never complete on our side, mismatched amounts, mid-flow cancellations. Every rejection path on the payment-execute endpoint now logs a structured event to GlitchTip with a stable reason code, so when something fails I see it without needing a user to screenshot the warning. The most dangerous case (“money taken, membership not created”) ships full stack traces so it can be fixed and refunded fast.