Testing Payments

Test the full purchase flow before going live. A built-in test mode toggle is coming; for now, use Stripe’s test cards on a published preview.

Proyecta Commerce is currently production-only — there’s no in-builder toggle that switches between test and live mode. The recommended pattern today is to publish your app, run a real payment with a low-value product, and immediately refund yourself.

Recommended testing flow today

1. Create a $1 (or smallest currency unit) test product in Dashboard > Commerce
2. Publish your app to its *.proyecta.live subdomain
3. Open the published URL in a separate browser tab and run the full checkout flow with your own card
4. Verify the side effects — webhook handlers ran, customer was created, entitlements granted
5. Refund the transaction from the Dashboard > Commerce > Transactions tab

This gives you full end-to-end coverage of the real money path, which is the only way to be 100% sure your integration works.

Why not just use Stripe test mode?

Today, Proyecta’s connection to Stripe runs in live mode only. A test mode toggle that lets you point Commerce at Stripe’s test environment (and use dummy cards like 4242 4242 4242 4242) is on the roadmap.

Tips

• Test the unhappy paths — declined cards, abandoned checkouts, network errors
• Test webhooks end-to-end — make sure your subscription state updates correctly when Stripe events fire
• Test cancellation — the at_billing_period_end flow is easy to overlook
• Test feature gates — call commerce.check() from a UI flow before assuming it works

Coming soon

• Test mode toggle in Dashboard > Commerce — switch your Payment Entity to Stripe test mode and use dummy cards
• Preview-mode checkout — exercise the checkout flow inside the builder without publishing
• Webhook event simulator to fire fake Stripe events at your runtime