Create a Stripe customer record from each new 2Checkout order
Each new 2Checkout order creates a customer in Stripe from the buyer details you map, so people who pay through 2Checkout also appear in your Stripe account’s customer list.
2Checkout
Stripe2 steps Setup ~5 min Used on 1.6k sites Free to import

What this workflow does
Some businesses take payments through more than one processor. If 2Checkout handles part of your sales and Stripe handles the rest, your customer list ends up split in two. This workflow copies buyers from 2Checkout into Stripe as customers, one order at a time.
The 2Checkout trigger, Order Created, fires when a new order is placed. The order data 2Checkout sends, including the buyer's details, becomes available to map in the next step.
Then Stripe runs Create Customer, which adds a new customer to your Stripe account from the fields you map, such as name and email. It does not charge the buyer or store a card. It also does not look for an existing customer first, so a person who orders twice through 2Checkout becomes two Stripe customers. Task History shows Stripe's response for each order.
Moving billing from 2Checkout to Stripe
You plan to bill future renewals in Stripe. Each new 2Checkout buyer is already a Stripe customer, so you have the contact record in place when you switch.
One customer list for two checkouts
International orders go through 2Checkout and the rest through Stripe. Copying 2Checkout buyers into Stripe gives you a single place to look up who has bought from you.
Sending Stripe invoices for add-ons
A buyer from 2Checkout asks for an extra service. Their Stripe customer record already exists, so you can raise an invoice in Stripe without typing their details in.
How this workflow runs
What happens at each step once the workflow is on, and what you need before you import it.
2Checkout Order CreatedFires when a new order is placed in 2Checkout. The order and buyer details 2Checkout sends with the event are passed on for mapping into Stripe.
Stripe Create CustomerAdds a new customer to your Stripe account. Connect Stripe and map the buyer's name and email from the 2Checkout order. No payment is taken in this step.
What you need
- FlowMatticCore
- 2Checkout 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.
- Place a test order in 2Checkout after import so FlowMattic captures the event. You can then check which buyer fields 2Checkout sends before mapping the Stripe customer.
- Add a Filter after the trigger if only some 2Checkout orders should reach Stripe, for example orders for one product you plan to renew through Stripe.
- Add a Google Sheets step after Stripe to log the 2Checkout order next to the new Stripe customer ID, so you can match the two records later.
Questions about this workflow
Does this charge the 2Checkout buyer again in Stripe?
No. Create Customer only adds a customer record. No charge, invoice or subscription is created in Stripe by this workflow.
What if the 2Checkout buyer is already a Stripe customer?
Create Customer always makes a new customer, so an existing buyer gets a second record in Stripe. Check Stripe for duplicate emails from time to time if your buyers order more than once.
Are past 2Checkout orders copied into Stripe?
No. Only orders placed after the workflow is turned on fire the Order Created trigger.
Which 2Checkout details can go into the Stripe customer?
Whatever 2Checkout includes in the order event. Run a test order, then map the buyer fields you see into the Stripe 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





