Create a Stripe customer record when a new BPC payment method is created
When a payment method is successfully stored in BPC, this workflow creates a customer in Stripe from the details BPC sends, so people who save a payment method with you also have a Stripe customer record.
BPC
Stripe2 steps Setup ~5 min Used on 824 sites Free to import
What this workflow does
Businesses that take payments through more than one provider often want the same people on record in each. If BPC is where customers save their payment method, and Stripe is where you invoice or report, creating the Stripe side by hand is slow and easy to miss. This workflow makes the Stripe customer for you.
The BPC trigger, Payment Method Created, fires when a payment method is successfully stored. The details BPC sends with that event, such as the customer's name or email if they are included, become values you can map.
The Stripe step creates a new customer. Map the BPC values into the customer details. Be clear on what this does not do: the card or account saved in BPC is not copied to Stripe, so the new Stripe customer has no payment method attached. Every new BPC payment method starts a run, so someone who saves a second method gets a second Stripe customer unless you check first. Task History shows each run and Stripe's response.
One customer list for invoicing
Customers save their payment method in BPC, and a matching Stripe customer is ready for when you raise an invoice from Stripe.
Reporting across two providers
Finance keeps Stripe as the main customer list. Every person who stores a method in BPC also appears there, with the details you mapped.
Preparing a move to Stripe
While you run both providers, each new BPC customer is created in Stripe as well, so the customer list there grows alongside BPC.
How this workflow runs
What happens at each step once the workflow is on, and what you need before you import it.
BPC Payment Method CreatedFires when a payment method is successfully stored in BPC. The data BPC sends with that event is passed on so you can map it into Stripe.
- Stripe Create Customer
Creates a new customer in Stripe from the BPC data. Map the name, email or other details your test run shows. No payment method is attached to the Stripe customer.
What you need
- FlowMatticCore
- BPC AccountAccount
- Stripe AccountAccount
After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.
Make it yours
Changes worth making after you import it.
- Add Stripe's Find Customer by Email before this step and a Filter that continues only when nothing was found, so a person saving a second method in BPC does not get a duplicate.
- Map an identifier from BPC into the Stripe customer's description, if the step offers one, so you can match the two records later.
- Store a test payment method in BPC after import and check the new customer in Stripe before you rely on the workflow.
Questions about this workflow
Is the card saved in BPC copied to the Stripe customer?
No. The workflow only creates the customer record in Stripe. Payment details stay with BPC, and the Stripe customer has no payment method attached.
What if the BPC customer already exists in Stripe?
The Create Customer step does not check first, and Stripe accepts more than one customer with the same email, so you can end up with duplicates. Add a Find Customer by Email step to avoid them.
Which BPC events start this Stripe workflow?
Only Payment Method Created, which fires when a payment method is stored. Payments, refunds and checkout sessions in BPC have their own triggers and do not start this workflow.
Do I need a Stripe account connected to FlowMattic?
Yes. The customer is created in the Stripe account you connect on the Create Customer step.
More Payments workflows
Other ready-to-import templates from the same category.
Import this workflow into your WordPress site
Download the JSON, import it from the Workflows screen and connect your accounts. Every run stays on your server, with no per-task fees.
30-day money-back guarantee Unlimited workflows and runs Self-hosted