Payments

Stripe

Set up Stripe Checkout as your card processor.

What you get

Stripe Checkout as your card processor. When a client visits your public payment page and chooses "Card," RemixCRM creates a Stripe Checkout Session and redirects them to Stripe's hosted page. Stripe handles the card form, 3D Secure, Apple Pay, Google Pay, and Link automatically.

On successful payment, Stripe redirects back to RemixCRM, which:

  1. Verifies the session was paid via the Stripe API
  2. Marks the payment row completed
  3. Stores the Stripe receipt URL
  4. Tries to match the payment to an event (by client email + event date)
  5. Fires the payment.recorded webhook

No additional UI work is needed — the public pay page automatically uses Stripe when you select it as the provider.

Prerequisites

  • A Stripe account at dashboard.stripe.com
  • Your business verified in Stripe (required to take live payments — sandbox/test mode works immediately)

Setup

1. Get your API keys

In the Stripe Dashboard:

  1. Go to Developers → API keys
  2. You'll see two keys:
    • Publishable key — starts with pk_test_… (test mode) or pk_live_… (live mode)
    • Secret key — starts with sk_test_… or sk_live_…. Click "Reveal" to see it.

Keep these handy. The secret key is sensitive — don't paste it into chat or commit it to a repo.

2. Configure in RemixCRM

  1. Go to Settings
  2. Find the Card Processor section
  3. Select Stripe
  4. Scroll to Stripe Payments below
  5. Pick Environment:
    • Test (sandbox) — use pk_test_… / sk_test_… keys. No real charges.
    • Live (production) — use pk_live_… / sk_live_… keys. Real money.
  6. Paste Publishable Key and Secret Key
  7. Click Save

3. Test the flow

  1. Visit your public pay page: https://app.remixcrm.com/pay/<your-org-slug>
  2. Fill in name, email, event date, amount
  3. Click Continue to Stripe Checkout
  4. You're redirected to Stripe — enter a test card:
    • 4242 4242 4242 4242 — succeeds
    • 4000 0000 0000 9995 — insufficient funds
    • Any future expiry, any CVC, any ZIP
  5. After payment, Stripe sends you back to RemixCRM
  6. You should see a green "Payment received" confirmation
  7. Check Settings → Reports → Payments to see the row

4. Switch to live

Once tested:

  1. Settings → Card Processor → Stripe Payments
  2. Change Environment to Live
  3. Replace both keys with pk_live_… and sk_live_…
  4. Save

Tip: Use Stripe's Restricted Keys for the secret key in production — generate one with only payment_intents.write and checkout.sessions.write permissions. Less blast-radius if it ever leaks.

How RemixCRM uses Stripe

Step API call
Client clicks "Continue to Stripe Checkout" POST /v1/checkout/sessions
Client completes payment on Stripe (handled by Stripe-hosted page)
Stripe redirects to /pay/<slug>?stripe_session_id=cs_…&paid=1 (handled by browser)
RemixCRM verifies GET /v1/checkout/sessions/{id}?expand=payment_intent
RemixCRM fetches receipt URL GET /v1/payment_intents/{id}?expand=latest_charge

All calls run server-side using your secret key. The publishable key is exposed publicly (as it must be) but it can only create sessions, not query the account.

Idempotency: each click creates a new Checkout Session. Stripe rejects double charges on the same Session, so abandoned-then-resumed sessions don't double-charge.

Webhooks (optional)

The current implementation polls the session on return to verify payment, so inbound Stripe webhooks are not required. If you want richer events (refunds, disputes, recurring billing), you can wire Stripe webhooks later — but the baseline pay flow needs no webhook setup at all.

Troubleshooting

"Stripe is not configured for this business" on the pay page

The org's payment_provider is set to stripe but stripe_secret_key is missing. Go to Settings → Card Processor → make sure all three Stripe fields are filled and saved.

Payment succeeds in Stripe but the row stays "pending" in RemixCRM

This happens when the user closes the tab before Stripe redirects back. The charge is real but the confirm step never ran. Fix: open the event's Payments tab, find the pending row, and click "Confirm." Or query the session ID in Stripe to verify and manually update.

In a future release this gap will be closed by a Stripe webhook subscription — filing this as payment.session_id_orphaned in your bug reports is helpful data.

Receipt URL is missing after payment

We fetch it via latest_charge on the PaymentIntent. If your Stripe account hasn't enabled receipts, the URL will be null. Enable receipts in Stripe Dashboard → Settings → Customer emails → "Successful payments."

"Stripe error: No such payment_intent"

The session belongs to a different Stripe account than the one whose keys are in Settings. This usually means you copied test keys but Stripe ran the session in live mode (or vice versa). Match the environment.