Skip to main content
Stripe integration must be verified against the payment adapter and configuration included in the selected SpurtCommerce release. This page describes a safe integration workflow; it does not assert that Stripe is enabled by default.

Configure

Use Stripe test-mode credentials in staging. Store secret keys and webhook signing secrets in a secret manager or protected environment variables. Never expose secret keys to browser code or commit them to Git.

Payment lifecycle

  1. Backend creates a payment intent/session using the server-calculated order amount and currency.
  2. Client completes the provider’s supported payment flow.
  3. Backend verifies the provider result and webhook signature.
  4. Order/payment state is updated idempotently.
  5. Refunds and disputes are reconciled through authorized server-side operations.
The exact object type, API version, metadata fields, and status mapping depend on the installed adapter.

Testing

Test success, decline, authentication-required, cancellation, duplicate webhook, delayed webhook, timeout, refund, and currency/rounding scenarios using Stripe test mode.

Verify

Inspect payment provider services, environment configuration, webhook routes, and package dependencies. Publish exact callback paths and required variables only after checking the release source.