Stripe

Not available in 6.0.0. Stripe appears in the payment provider picker marked Coming soon and cannot be selected or enabled. This page describes what is planned. For card payments online today, use PayPal.

Why it is listed but disabled

Stripe is registered as a provider and its configuration schema is written, but the part that actually moves money — initiating a charge and confirming it by webhook — is not finished. Rather than ship a payment option that stores credentials and quietly records payments it never took, the provider is locked until the integration is complete.

You will see it in Payment Gateways → New, greyed out with a Coming soon badge. Clicking it does nothing, and the server refuses to publish a gateway on it even if the request is made directly.

What is planned

The same shape PayPal already uses:

1. The guest reaches checkout and chooses Stripe.
2. They are redirected to Stripe's hosted checkout page. Card details are entered there, on Stripe's infrastructure — they never touch your server.
3. On return, the result is verified server-side before the order is settled.
4. Independently, Stripe's webhook confirms the capture, so an order still settles if the guest never comes back — closed tab, lost signal, flat battery.

Step 4 is the part that makes a redirect flow safe to rely on, and it is the reason the provider is not being released before it works.

Refunds through the ledger, back to the original Stripe transaction, arrive with the same update.

What to use in the meantime

When it arrives

Enabling Stripe will be a version upgrade, not a configuration change — the provider unlocks itself when the integration ships. Nothing you configure now needs redoing, because there is nothing you can configure yet.

See also

• Payment Gateways — the providers you can configure today
• PayPal — the working redirect provider
• Adyen, Square & SumUp — also planned, also locked
• Payments — the ledger and refunds