Frontend

Shoppers see standard J2Commerce checkout until they choose Stripe, then Stripe hosted Checkout until they return to your site with order status updated when redirect and webhooks succeed.

What does checkout look like?

At checkout the shopper selects the payment method using the Display name you configured, optionally with display image if your theme shows payment icons. Submitting payment redirects to Stripe hosted Checkout where Stripe renders card, wallet, and other methods your Dashboard enables. The shopper completes or cancels on Stripe, then returns to J2Commerce confirmation or error flows per plugin templates and messages.

What messages appear around redirect?

onbeforepayment text can warn that wallet and card payments usually confirm immediately while bank methods may take days. onafterpayment, onerrorpayment, and oncancelpayment control text shown on return paths. Edit them in plugin Advanced tab if your shop voice differs from defaults.

Do shoppers stay on my domain for card entry?

No for Stripe Checkout flow. Card and wallet entry happen on Stripe hosted pages. If you require embedded Elements on your domain, this plugin is not that product.

What should I test on the storefront?

Test guest and logged-in checkout if both exist. Test mobile width because Stripe Checkout is responsive but your cart template might not be. Test cancel path back from Stripe to confirm oncancelpayment messaging and cart state match your policy.

What do customers see when webhooks lag?

Some async methods may show paid in Stripe before J2Commerce order status catches up if webhooks fail. Customers experience thank-you delay or pending order email confusion. Fix webhooks rather than arguing with shoppers about who is authoritative.