--- title: "Account signups into Stripe customer records" description: "Turn every account signup into a Stripe customer with the business name, email and billing address already mapped, using a Zap on new submissions." url: "https://www.formformform.com/automations/stripe-customer-record-at-signup" type: static generatedAt: "2026-08-23T18:56:58.727Z" --- ![Stripe logo](/logos/integrations/stripe.svg) # Create a customer record when an account is opened Each account signup creates a Stripe customer carrying the business name, billing email and address, ready before the first invoice. When this happens New submission on your "Start your account" form Do this Create a customer in Stripe with name, email and billing address One-directional. A submission triggers the action — nothing is written back into your form. A signup form is the first moment you know a business exists. Creating the Stripe customer right then means the record is already there — name, contact, address — when someone in finance goes looking for it weeks later. Wholesale and trade teams lean on this when accounts get approved faster than anyone types them up. The customer sits in Stripe unbilled and harmless until there is something to charge for, so there is no cost to creating it early and no scramble for an address at invoice time. ## Setting it up 1. 1 Publish your account signup form and make Business Name, Business Email and Business Address required. Stripe will create a customer with an empty address without complaining, and you find out on the day the first invoice goes out. 2. 2 Decide which name belongs on the customer. Stripe shows one Name on the record and on invoices, so use Business Name there and keep Contact Name for the description — invoices addressed to a person get queried by the person's colleagues. 3. 3 In Zapier, choose formformform as the trigger app, select New Submission, connect your account, pick the signup form, and pull in a real test submission so every field has sample data to map. 4. 4 Add Stripe as the action app and choose Create Customer rather than Find or Create Customer. A signup is the first sighting of this business, so there is nothing to search for yet. 5. 5 Map Business Name to Name and Business Email to Email. Stripe sends invoices and receipts to that address, so it needs to be the accounts inbox rather than whoever happened to fill in the form. 6. 6 Map Business Address into Address Line 1. A single free-text answer lands there whole; if you invoice across borders and need the country separated out, split the question into line, city, postal code and country fields on the form first. 7. 7 Put Contact Name in Description and send Estimated Monthly Order Volume (USD) to a metadata key such as expected\_volume, so the sales conversation starts from the number they gave you. 8. 8 Submit a test application, open Customers in Stripe and check the address block is populated, then switch the Zap on. ## What maps where Using the [Wholesale Account Inquiry Form](https://www.formformform.com/templates/wholesale-inquiry-form) as the starting point. These are its real fields — swap in your own and the mapping works the same way. Form field Stripe Business Name Name on the Stripe customer Business Email Email on the Stripe customer, used for invoices and receipts Business Address Address Line 1 of the customer's billing address Phone Number Phone on the Stripe customer Contact Name Description, so the record shows who to chase Estimated Monthly Order Volume (USD) Customer metadata key for expected volume ## Variations worth knowing Flag accounts that claim a resale certificate Map "Do you have a valid resale certificate or business license?" to a metadata key on the customer. It does not change how Stripe calculates anything — it is a note for whoever raises the first invoice, telling them a certificate was claimed and needs checking before the account is treated as tax exempt. Only let approved account types through Add a Zapier filter after the trigger that continues on the Business Type answers you actually stock, so speculative applications never reach Stripe. Every submission still lands in the responses list, which means nothing is lost — the filter decides what becomes a billing record, not what gets collected. ## If something isn't arriving The customer is created but the address block in Stripe is empty. Stripe stores billing address parts separately, and the Create Customer action has one box per part. Mapping Business Address to a shipping field, or leaving Address Line 1 unmapped, produces a customer with no billing address at all. Put the answer in Address Line 1 and re-test. The same business shows up twice in the Customers list. Create Customer adds a record every time it runs, so a second application creates a second customer. Swap the action for Find or Create Customer keyed on Business Email, or search Stripe by email before invoicing and merge what you find by hand. ## Frequently asked questions Does creating the customer charge them anything? No. Creating a Stripe customer alone does not charge them. To collect at submission, add products and priced options to the form and enable secure hosted checkout; otherwise the separate invoice or subscription action controls when billing starts. Should I connect Stripe in test mode first? Yes, if you can. Zapier connects with the API keys you give it, so a test-mode key writes to your Stripe test data. Run a few real applications through, check the customers look right, then reconnect with the live key and turn the Zap on. Will the Stripe customer ID come back to the submission? No. Data travels one way: the submission triggers the Stripe action, and nothing Stripe creates is written back into the form or the stored response. If you need the ID next to the answers, export both and match them on the email address. ## Related automations - [Apply an early-bird discount to conference registrants](https://www.formformform.com/automations/stripe-apply-early-bird-coupon) Every conference registration creates a Stripe customer with the early-bird coupon already applied to their account. - [Bill extra work on the client's next invoice](https://www.formformform.com/automations/stripe-extras-onto-next-invoice) A costed change request attaches an invoice item to the client's existing Stripe customer, so extra work lands on their next invoice. - [Draft an invoice from every quote request](https://www.formformform.com/automations/stripe-draft-invoice-from-quote) Every quote request finds or creates the client in Stripe, adds an invoice item for the scope, and leaves a draft invoice to review. - [Set up a monthly donor for recurring giving](https://www.formformform.com/automations/stripe-monthly-donor-onboarding) A monthly pledge creates the Stripe customer and starts a recurring subscription at the amount the donor committed to. - [Start a subscription when someone picks a plan](https://www.formformform.com/automations/stripe-subscription-from-plan-choice) The plan someone chooses on the form becomes a Stripe subscription on the matching recurring price, with the customer created first. - [Add counter signups to your Customer Directory](https://www.formformform.com/automations/square-signups-to-customer-directory) A signup at the till or on your site becomes a Square customer profile straight away, spelled the way the customer typed it. - [All Stripe integration details →](https://www.formformform.com/integrations/stripe) - [Start from the Wholesale Account Inquiry Form →](https://www.formformform.com/templates/wholesale-inquiry-form) - [Browse every automation →](https://www.formformform.com/automations) ## Build the form first The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow. [Start free](https://app.formformform.com/register?utm_source=landing&utm_medium=bottom&utm_campaign=automations&utm_content=stripe-customer-record-at-signup)