FlutterFlow Stripe Integration: 6 Steps From PaymentIntent to Payment

Create a PaymentIntent or SetupIntent on a secure server, return the client_secret to your FlutterFlow client, and confirm it with flutter_stripe or a custom action. Then register a webhook endpoint and verify its signatures so subscription events keep your app in sync. Everything else in a FlutterFlow Stripe integration builds on those three moves.

TL;DR:

• Use a SetupIntent to save a card without charging it; use setup_future_usage when the customer pays now and you want to reuse that card later.
• For subscriptions, handle invoice.paid, invoice.payment_failed, and customer.subscription.updated, then verify each signature and replay events with Stripe CLI against your endpoint before launch.
• For marketplace payouts, use Destination Charges, create connected accounts and PaymentIntents on your server, and set on_behalf_of to link each transaction to its seller.
• Apple Pay and Google Pay require custom actions with flutter_stripe, platform setup for iOS and Android, wallets enabled in Stripe, and testing on real devices.
• A basic one time payment suits an in house build, but Connect, subscription state management, and limited backend experience raise production risk.

Table of Contents

• How do you create and confirm a PaymentIntent in FlutterFlow?
• How do you save payment methods and handle subscription webhooks?
• How does Stripe Connect work for marketplace payments?
• How do you set up Apple Pay and Google Pay in FlutterFlow?
• How do you troubleshoot a broken Stripe integration?
• When should you build in-house, and when should you bring in help?
• Need Stripe working in your FlutterFlow app?
• FAQ
• Sources

How do you create and confirm a PaymentIntent in FlutterFlow?

The working sequence is short. Your server talks to Stripe with the secret key, and your FlutterFlow app only ever sees the client_secret. FlutterFlow’s Stripe docs and Stripe’s Payment Intents guidance agree on this split: create the PaymentIntent server-side, then pass its client_secret to the client to complete the payment.

Any backend that can hold a secret key works. Node with Express, Firebase Cloud Functions, and Supabase edge functions are the common picks. If you are still choosing between the last two, our Firebase vs Supabase comparison covers the tradeoffs.

Here is the minimal flow:

1. Add a server endpoint that accepts an amount, currency, and customer ID, then creates the PaymentIntent with your secret key.
2. Return only the client_secret in the JSON response.
3. In FlutterFlow, call that endpoint through an API Call or custom action when the user taps Pay.
4. Initialize the payment sheet with the returned client_secret before presenting it.
5. Confirm the payment with flutter_stripe, then handle success and failure states in your UI.
6. Test the whole path with Stripe test keys and test cards.

A few security habits matter here:

• Keep secret keys on the server and never in FlutterFlow variables or app state.
• Never log the client_secret or put it in a URL.
• Validate amounts and IDs on the server, not in the app.
• Serve every endpoint over TLS.

How do you save payment methods and handle subscription webhooks?

Use a SetupIntent when you want to save a card without charging it right now. Use setup_future_usage on a PaymentIntent when the customer pays now and you also want to reuse the card later. Either way, Stripe’s SetupIntents guidance says the usage value (on_session or off_session) shapes how well later charges succeed and how strong customer authentication is handled. A successful SetupIntent attaches the method to the Customer, as the SetupIntent API reference explains.

For subscriptions, create the subscription or Checkout Session on the server and return whatever client secret or session info the client needs, following Stripe’s subscriptions integration guide.

The app then depends on webhooks. Stripe’s subscription webhook docs tell you to register an endpoint, handle the events, and verify each one came from Stripe. Start with these:

• invoice.created
• invoice.finalization_failed
• invoice.paid
• invoice.payment_failed
• customer.subscription.updated

Pro Tip: Run the Stripe CLI against your local endpoint and replay events before you go live, and always verify the signature so a forged request never changes a subscription.

How does Stripe Connect work for marketplace payments?

If your FlutterFlow app routes money to sellers, Destination Charges are the usual fit. The platform creates the charge and funds are split automatically, as Stripe’s Connect charges docs describe. Set on_behalf_of on the PaymentIntent to link the transaction to the connected account for settlement and compliance.

Your server carries most of the Connect work:

• Create and manage connected accounts on the server, never from the client.
• Create the PaymentIntent on the platform account with the destination and on_behalf_of set.
• Keep platform secrets out of FlutterFlow entirely.
• Update your webhook logic to account for connected-account events, since Connect changes which events arrive and how settlement looks.

How do you set up Apple Pay and Google Pay in FlutterFlow?

Native wallets run through custom actions built on flutter_stripe. The PaymentIntent still comes from your server first, so the client_secret exists before you call any wallet method. FlutterFlow’s docs also call for platform config changes, and its configuration files guide explains how snippets for Info.plist, Entitlements.plist, and AndroidManifest.xml get merged into your project.

Before you build, check these items:

• Update Entitlements.plist for iOS and the Android payment config in the FlutterFlow project.
• Confirm Apple Pay and Google Pay are enabled in your Stripe Dashboard.
• Test on real devices, since simulators rarely tell the full story.
• Use HTTPS for any hosted flow.

How do you troubleshoot a broken Stripe integration?

Work through these checks in order:

1. Missing client_secret. Confirm your endpoint returns it and that the FlutterFlow API Call parses the right JSON field.
2. Payment sheet not initialized. Initialize with the client_secret before presenting the sheet, and check async results instead of assuming success, a pitfall FlutterFlow’s docs flag directly.
3. Webhook failures. Check the signing secret matches the endpoint, confirm the raw request body reaches your verification code, and replay events with the Stripe CLI.
4. Saved cards failing later. Confirm you used a SetupIntent or setup_future_usage, and check the on_session versus off_session flag.
5. Silent UI errors. Surface Stripe error messages to the user and log them server-side, minus the client_secret.

When should you build in-house, and when should you bring in help?

Our view: a basic one-time payment is a fine in-house project. Trouble starts when three things pile up: Connect marketplace logic, subscription state that has to stay correct, and a team with little backend experience. That combination is where runtime surprises show up in production. We’ve shipped FlutterFlow work through to production, and teams in that spot usually gain the most from a dedicated engineering partner who also stays on after launch.

— Alex

Need Stripe working in your FlutterFlow app?

If you would rather ship than debug webhooks, we can build it with you. Our US-based senior engineers handle the full Stripe setup in FlutterFlow, and our FlutterFlow to code migration service covers teams who need production-grade software behind their prototype. Here is what we cover:

• End-to-end Stripe payment integration in FlutterFlow
• Connect marketplace builds with destination charges
• Subscriptions, webhooks, and failed-payment handling
• Post-launch support and maintenance

We work at fixed, transparent pricing with no surprise costs. Review our pricing plans or request a scoping call, and tell us what you want to launch.

FAQ

Do I need a backend to use Stripe in FlutterFlow?

Yes, for anything beyond a hosted checkout link. PaymentIntents must be created with your secret key, which belongs on a server such as Firebase Cloud Functions, Supabase, or Node. Your FlutterFlow app only receives the client_secret.

What is the difference between a SetupIntent and a PaymentIntent?

A PaymentIntent collects a payment now. A SetupIntent saves a customer’s payment method for later charges without taking money. If you want to charge and save in one step, set setup_future_usage on the PaymentIntent.

Which webhook events matter most for subscriptions?

Start with invoice.paid, invoice.payment_failed, and customer.subscription.updated. These cover successful renewals, failed payments, and plan or status changes. Always verify the signature on every event.

Why does my payment sheet fail to open?

Most often the sheet was never initialized, or the client_secret is missing or wrong. Confirm your server returns it and that initialization finishes before you present the sheet.

Sources

• Docs
• The Payment Intents API | Stripe Documentation

Recommended

• Stripe vs Paddle: Which One Actually Fits Your SaaS?
• Ship in 6–10 Weeks, Plan Exit: Bubble vs FlutterFlow for US Founders

About Let’s Build My App

Let’s Build My App is a US-based AI development agency. We design, build, and launch production-grade custom software using AI coding tools including Claude Code and OpenAI Codex, and we migrate legacy Bubble apps onto AI-coded stacks such as React, Supabase, and Firebase. We are the #1 US-Based Bubble Agency, founded and run by Alex Dow. Book a free strategy call to scope your project.