ESTAGE Support
IdeasMy tickets

What your buyers see

Updated October 15, 2026

The checkout experience on your published site — product picker, coupons, saved cards, secure card entry, and free checkout.

Here's what happens on the published site when someone buys through your order form. This is the experience your configuration produces — no extra setup needed.

Preview vs. published

Payments only run on your published site. In the builder preview, the card fields show a disabled mock with "Preview mode — payments work on published site." That's expected — go live to take real payments.

Choosing a product

  • If your form has one product and no options, buyers see a clean summary card — image, name, description, price, trial, and billing interval.
  • If you added multiple products (or a product with price tiers), buyers see a picker and choose one. Tiers appear as options nested under their product.

The price shown updates as the buyer switches products or tiers.

Signing in or checking out as guest

Depending on your checkout mode:

  • Guest checkout — buyers enter first name, last name, and email. There's still a "Have an account? Log in" option, and if they enter an email that already exists, the form suggests logging in instead.
  • Require login — buyers use Log In / Register tabs before paying. Signed-in buyers see a "Signed in as…" banner.

Coupons

If you left the promo-code field on, buyers see a coupon input with an Apply button:

  • It auto-validates about a second after they stop typing (pressing Enter applies it immediately).
  • On success, the discount shows clearly — a percentage off, a fixed amount off, or trial days — and the Pay button updates to the discounted total.
  • On failure, they see a specific reason ("Coupon expired", "Maximum uses reached", etc.), not just a generic error.

Coupons are managed in ESTAGE CRM, scoped per product — switching product clears an applied coupon, since codes are product-specific.

Saved cards (returning buyers)

Logged-in ESTAGE buyers with stored cards get a dropdown of their saved cards (e.g. "Visa •••• 4242 (12/27)"), plus a "Use a different card" option. Their last-used card is auto-selected, so repeat purchases are one tap. (Saved cards are a Stripe feature.)

Card entry & secure payment

For a new card, buyers enter card details in Stripe's secure fields. If their bank requires 3D Secure, the verification runs during checkout and they see a processing state. When more than one gateway is enabled, a Card / PayPal / Razorpay / Paystack / Square switch appears. With Paystack, buyers pay in Paystack's own checkout, which opens over the page — or on Paystack's checkout page, when their browser won't let it open there, and they come back to your site once they've paid.

Free checkout (100%-off coupon)

When a coupon brings the total to $0.00, the form adapts automatically:

  • The card-entry block is hidden entirely — no card needed.
  • The pay button becomes "Get for Free."
  • If a product has GDPR / consent text set in CRM, a consent checkbox appears and must be ticked to complete the purchase.
  • If a product has billing terms text, it's shown exactly as written.

After purchase

On success, buyers see the outcome you configured — a green confirmation message or a redirect to your chosen URL.

Was this helpful? Still stuck? Write to the team