Testing Payment Forms

Test every payment-enabled form end to end before sharing it with members: keep the form in Test Mode while you build, complete a test registration with a Stripe test card, verify the full post-submit experience, then switch to Live Mode so actual payments are processed.

A few minutes of testing catches pricing errors, incorrect products, broken automations, and confirmation email problems before your members do. The same process applies whether you collect membership dues, event registrations, donations, or product purchases.

Use Test Mode while building

Keep the form in Test Mode while you build it. Test Mode completes transactions without charging a real credit card, so you can experience the form exactly as your members will.

Every payment-enabled form has Test Mode and Live Mode, and the Payment element has a live/test toggle in the form builder. To add products, connect the payment gateway, and find the toggle, see Add products to a form. For donation, recurring, and manual payment setups, see Collect payments in forms, including donations.

While the form is in Test Mode, verify that:

• The correct products appear.

• Prices are accurate.

• Required fields work as expected.

• Coupons apply correctly.

• Confirmation emails are sent.

• Automations are triggered.

• Staff notifications are received.

Complete at least one full test registration before sharing the form publicly.

Simulate payments with Stripe test cards

If your form processes payments through Stripe, simulate checkout scenarios with Stripe's test card numbers while your account is in Test Mode. Test payments don't charge live cards and don't appear in live reporting.

Stripe publishes these numbers in its public Testing documentation — see the full list at Stripe's testing docs. To connect Stripe for form payments, see Connect Stripe for payment processing.

The success card below accepts any three-digit CVC and any future expiration date.

Testing these situations helps ensure your members receive clear instructions if something goes wrong during checkout.

Verify the entire experience after a test payment

A successful payment is only part of the process. After each test submission, confirm the whole member experience:

• The payment is recorded. Full transaction history lives under Payments > Transactions, with statuses such as Successful and Pending and exportable details, and the contact's Payments area records it in Payment History. See Collect payments in forms, including donations for tracking payments.

• The contact record is updated. Form responses show up in the Submissions screens, the contact record's Activity section, and the contact's Contact Details page. See Where form responses show up.

• Order details are available. Submission details include the payment amount, Order ID, and Payment status. Click the Order ID to open the order details, which can be exported.

• Confirmation emails are delivered. Confirmation emails include detailed information about the products purchased and the total amount paid. See Send confirmations after a purchase or order.

• Staff notifications arrive. The Email notification alerts your team on every submission, and the Auto responder sends a confirmation to the submitter. For payment-enabled forms, both include the payment amount and payment status. See Email notifications in forms and surveys.

• Workflows run correctly. Use the Payment Received workflow trigger, with Forms as the trigger source, to automate after a payment — see Payment Received workflow trigger. When a test produces unexpected results, Workflow History and Logs shows which steps actually ran for the contact.

• The success message or redirect displays. After submission you can show a success message, redirect to another page (including Thank You pages), or confirm a completed purchase. See Choosing What Happens After Form Submission.

Switch to Live Mode

Switch the form to Live Mode only after testing is complete. Live Mode processes actual payments through your connected payment account.

Before sharing the form publicly, complete a final pre-launch review:

• Live Mode is enabled.

• The correct payment account is connected.

• Product pricing is accurate.

• Confirmation messages are correct.

• Any linked automations are active.

Forgetting to switch a fully tested form from Test Mode to Live Mode before sending it to members is one of the most common form mistakes. See Common Form Mistakes for the other issues to check before publishing.

Best practices

• Test every payment form before publishing.

• Verify pricing, discounts, and coupons.

• Use Test Mode while building.

• Switch to Live Mode only after testing is complete.

• Complete one final review before sharing the form publicly.

• Test again after making significant changes to an existing payment form.