← Back to home

Choose payment flow

Choose a provider-specific payment path from one entry page. Stripe is the primary browser checkout route. NicePay can also be exposed for test-mode public demos when feature flags and provider test credentials are enabled.

Demo order generation

Each provider link starts a fresh demo order ID so repeated test payments do not reuse the same PaymentIntent or provider transaction.

How to read this page

  • Start here to choose the provider-specific execution path.
  • Stripe is the primary browser checkout route and records a server-created PaymentIntent into the shared payment model.
  • NicePay key-in is available as a public test route when feature flags and provider test credentials are enabled.

Available payment paths

Single entry, provider-specific handling

Stripe Payment Element

Primary browser checkout

Server-created PaymentIntent with Stripe-hosted confirmation and shared payment recording.

  • Backend creates the PaymentIntent before browser confirmation
  • Return-page verification, webhooks, and refunds converge on the same payment record
  • Browser card entry stays inside Stripe-hosted fields
Open Stripe checkout

NicePay key-in

Public test flow

Merchant-hosted key-in flow retained for provider-specific approval and cancellation handling.

  • Approval, full cancellation, and partial cancellation stay on the provider path
  • Provider-specific identifiers are stored on the shared payment record
  • Merchant-hosted card entry should use only provider test credentials and test card data
Open NicePay key-in