Create a Stripe customer record from each new Hitpay order
Each order created in Hitpay adds a customer in Stripe from the buyer’s details, so the people who pay you through Hitpay also have a record in your Stripe account.
Hitpay
Stripe2 steps Setup ~5 min Used on 481 sites Free to import

What this workflow does
Businesses that take payments in Hitpay but bill or report through Stripe end up with buyers in one system and not the other. Copying customer details across by hand is slow and easy to get wrong. This workflow creates the Stripe customer when the Hitpay order comes in.
The Hitpay trigger fires when an order is created successfully. FlowMattic passes the order data to Stripe, whose Create Customer action adds a new customer from the values you map, such as the buyer's name and email, if the order carries them.
Stripe's step here has no matching logic and adds a fresh record on every run. A repeat buyer places a new order, so they get another Stripe customer each time unless you check first. The tips show how to look the buyer up by email before creating. Task History shows the Stripe response for every order.
Moving buyers to Stripe subscriptions
A shop sells a starter kit through Hitpay and later offers a refill plan billed in Stripe. Each kit buyer already has a Stripe customer record when the plan launches.
One customer list for reporting
Finance reports on customers from Stripe. Hitpay buyers now appear there too, so the list covers both payment routes.
Regional checkout with central billing
A business uses Hitpay for local buyers and Stripe for invoicing. Customers from Hitpay orders can be invoiced in Stripe without re-entering their details.
How this workflow runs
What happens at each step once the workflow is on, and what you need before you import it.
Hitpay Order CreatedFires when an order is created successfully in your Hitpay account. The order data, including whatever buyer details Hitpay sends, becomes available to map.
Stripe Create CustomerCreates a new customer in Stripe from the Hitpay order. Map the buyer's email and name, and any other details a test run shows, into the customer.
What you need
- FlowMatticCore
- Hitpay 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" step before Create Customer, then a Filter that continues only when no customer is found, so repeat Hitpay buyers don't create duplicates.
- Map the Hitpay order reference into the Stripe customer's description, if the step offers one, so you can trace each customer back to the order that created them.
- Run a test order after import and check which buyer fields Hitpay sends. If an order arrives without an email, add a Filter so those orders skip the Stripe step.
Questions about this workflow
Will a returning Hitpay buyer get a second Stripe customer?
Yes, as imported. Create Customer always makes a new record. Add a Find Customer by Email step and a Filter before it to reuse the existing customer.
Will the Hitpay buyer be charged again in Stripe?
No. The Stripe step just stores the buyer as a customer. The payment itself stays in Hitpay, and nothing is billed through Stripe unless you add that yourself.
Which Hitpay orders start the workflow?
Every order Hitpay reports as created successfully. If you only want some, add a Filter after the trigger on a field such as the amount, if the test data shows it.
Can I also create a Stripe subscription for these buyers?
Stripe has a Create Subscription action you can add after Create Customer, mapping the new customer's ID. Test it with a known price first.
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