← Back to home

Choose a test payment path

Start a test payment from one entry page. Stripe uses a browser checkout. NicePay uses test merchant credentials, but it can still create a real temporary charge on the submitted card.

Demo order generation

Each provider link starts with a fresh demo order ID so repeated tests do not reuse the same recorded payment flow.

How to read this page

  • Choose the provider path from one entry page while PayBridge records the result in one shared payment lifecycle.
  • Stripe uses a browser checkout backed by a server created PaymentIntent.
  • NicePay uses test merchant credentials, but it can still create a real temporary card charge that is automatically canceled before midnight on the same day.
  • Operator login is still required for transaction detail, refunds, cancellations, audit records, and exports.

Available payment paths

One entry point with separate provider handling

Stripe browser checkout

Primary test card flow

PayBridge creates the PaymentIntent on the server, then Stripe collects card details in the browser.

  • Server creates the PaymentIntent before browser confirmation
  • Stripe fields collect card details without exposing them to PayBridge
  • The return page and webhook path converge on the same recorded payment
Open Stripe checkout

NicePay payment test

Public real card test

This route uses NicePay test merchant credentials, but the submitted card can still receive a real temporary charge before the provider cancels it later the same day.

  • The tester enters a real card and personal information they are authorized to use
  • NicePay automatically cancels the temporary test charge before midnight on the same day
  • PayBridge records the approval result while internal detail, refund, and cancellation actions stay behind operator access
Open NicePay payment test