Verify Payments
Finish payment installation with your developer, check the connection, and test before launch.
Connecting Stripe lets SaaSFunnels import your products, prices, customers, and billing activity. It does not, by itself, let a Funnel take a payment in your app. Your developer or coding agent completes that part of installation before you build a Funnel.
You do not need to authorize Stripe again. You also do not automatically need another Stripe webhook: your developer can usually extend the payment handling your app already uses.
1. Use the app installation handoff
In Setup → Install and deploy, select Copy installation instructions. This handoff includes both app installation and payment actions. Give it to your developer or coding agent, then use Payment connection to save and verify the connection.
If payment installation is incomplete, Copy payment setup prompt gives the developer a focused repair checklist. It is not a second installation or another Stripe authorization. Share prompts, not secret values.
The developer needs access to your app's source code, deployment settings, secret manager, and the Stripe account connected to this workspace. The prompt explains how to enable:
- Saving a payment method without charging it.
- Taking a one-time payment.
- Starting a subscription.
2. Have your developer finish installation
Your developer connects those actions to the app's existing payment handling and makes sure Stripe reports the result. They reuse or extend a suitable existing webhook, or create one if needed. The webhook SaaSFunnels manages for importing Stripe data does not install this handling in your app.
They save the required settings in the correct environment, deploy the app, and register its payment connection in Setup → Payment connection. The endpoint and two secrets in that form come from your developer. They are different from the Stripe webhook signing secret. Enter them only in the secure fields; do not paste them into chat.
Use the developer checklist for event coverage, signing secrets, test/live matching, and deployment verification. The developer must test payment handling with Stripe test data, including failures and retries, without live charges.
Save and check the payment connection
In Setup → Payment connection, an administrator enters the payment endpoint, signing secret, and completion secret supplied by the developer. Select Save payment connection. Verification starts automatically. To update an existing connection, select Edit connection.
Products and prices must show Ready, and all three payment actions must show Verified. Use Check payment connection to retry after repairing a failure. Saving the form does not itself mean verification passed.
Then open Review and verify. Funnel creation also requires the Stripe catalog, app activity, signed-in identity, successful discovery, and resolution of its review findings. Payment verification alone does not unlock it.
This check confirms that your app responds securely and reports support for the payment actions for the connected Stripe account. It does not create a payment or prove that a customer completed a payment journey. Automatic rechecks keep connection readiness current; they do not run payment transactions.
If a check fails:
| What you see | What to do |
|---|---|
| Check button unavailable | Finish the app connection, then have a workspace administrator save the payment connection. |
| Products and prices need refresh | Open Connect Stripe in Setup, inspect import progress, and use Retry catalog import if it failed. |
| One or more actions need setup or fail | Give your developer the payment setup prompt. They must repair the affected action, check payment-result delivery, and deploy before you retry. |
| It worked before an account, environment, or credential change | Have your developer align the app with the currently connected Stripe account and environment, then run the check again. |
Do not generate replacement credentials or reconnect Stripe simply to clear a failed payment check. First have your developer identify what is missing.
Test the first Funnel before publishing
Create your Funnel once Setup unlocks it. Your developer tests payment handling in your app's existing development environment using Stripe test data. Do not replace your working production connection or use real customer cards for setup checks.
Then test the Funnel's entry, account identity, placement, and recovery behavior in your app. Ask your developer to report payment tests separately from the connection and preview checks; a preview alone cannot establish that Stripe took a payment.
Together with your developer, verify:
- Saving a method does not charge it.
- A one-time payment creates one charge, and a subscription starts once.
- Declined or canceled payments offer recovery and never show paid success.
- Double clicks, reloads, and retries do not create duplicate payments.
- Confirmed results reach SaaSFunnels; refunds or reversals update the outcome appropriately.
- A different or unauthorized account cannot act on another customer's payment.
Funnel Preview/Test can check the experience and delivery, but simulated payment screens do not prove a Stripe transaction. Record which tests passed and which remain untested. Publish only after the applicable customer journey has passed.