Describe the merchants you serve and the information your team requests. Makeform creates a structured merchant services application form for business, ownership, banking, processing, and document details.
Route completed applications to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a starting brief, tailor it to your workflow, or send it to the builder. Each structure is an editable example.
Audience
Brick-and-mortar retailers applying for card acceptance
Format
Multi-step application with location and processing details
Prompt size
271 chars
Example form structure
Multi-step application with location and processing details
Business and location details
Owners and ownership percentages
Monthly volume and ticket size
Equipment requested
Supporting documents
Suggested routing tags
New applications
Documents pending
Underwriting review
Ask for monthly card volume and average ticket separately; one total cannot show how transaction size and volume shape the merchant profile.
Step 1
Apply
merchant enters business and owner details
Step 2
Document
bank and processing files are attached
Step 3
Review
underwriting team checks the submitted file
Step 4
Follow up
missing details route back to the applicant
Why structured intake matters
A guided application keeps related facts and files together, making missing answers easier to spot.
Conditional sections show channel-specific questions only when a merchant selects that channel.
Separate volume, ticket, and channel fields provide consistent inputs instead of one estimate.
Label every requested upload and keep it attached to the merchant's submission.
Built for acquisition teams
Start with the applicant's sales environment, then adjust questions, documents, and routing.
Locations, terminals, volume, ticket sizes, and transaction-method mix.
Website, products, fulfillment, refunds, subscriptions, and card-not-present share.
Capture agent, pricing, equipment, and internal notes beside merchant sections.
Repeat address, contact, volume, and equipment fields for each location.
Application workflow
Generate, refine, and publish the form, then route each application for follow-up.
Name the business types, channels, figures, owners, bank details, equipment, and documents needed.
Require critical answers and branch to ecommerce or retail questions by sales channel.
Share or embed the form, then notify the assigned review inbox after submission.
Send summary fields onward, tag incomplete files, and request specific missing items.
Online form vs static packet
A useful intake method keeps ownership, processing, banking, and document details connected.
Field guide
Use these six sections as a practical checklist, then match field wording and document requests to your processor's actual review workflow.
Business profile
Keep legal and public-facing names separate. Capture entity, tax ID, operating history, contacts, website, and addresses in structured fields.
Ownership
Use a repeatable owner section with separate identity, role, contact, and ownership fields instead of one ambiguous text box.
Processing profile
Monthly volume, ticket sizes, and channel percentages answer different questions. Numeric fields also simplify comparison with statements.
Products and delivery
Ask what is sold, when customers pay, and how fulfillment works. Show website, refund, and subscription questions conditionally.
Banking and documents
Keep settlement details and supporting files together. A separate labeled upload for each item makes missing documents visible.
History and review
Ask about processor history and chargebacks, then let applicants review and confirm their submission before your team assesses it.
Related tools
Pair the core application with forms for payment authorization, credit requests, vendor intake, and ongoing account questions.
Collect structured company, reference, and requested-credit details for a separate commercial review process.
Open toolCreate a payment collection workflow for businesses that need a customer-facing card payment form.
Open toolBuild an authorization intake with payer details, payment instructions, and acknowledgment fields.
Open toolGather organization, contact, offering, and qualification details from prospective vendors.
Open toolTurn an accepted vendor into a trackable setup checklist with owners and required steps.
Open toolRoute early questions from vendors and suppliers before a full application is needed.
Open toolFAQ
Practical answers for processors, ISOs, sales teams, and operations staff building merchant intake.
It collects business, owner, banking, transaction, equipment, and document details from a payment-processing applicant. The processor or ISO reviews the resulting file; the form does not decide approval.
Include business identity, addresses, contacts, website, owners, settlement banking, volume, ticket sizes, channel mix, fulfillment, processor history, equipment, and labeled uploads. Remove fields your process does not use.
Yes. Conditional logic can show retail applicants location and terminal questions while ecommerce applicants see website, fulfillment, refund, subscription, and card-not-present questions.
Yes. Add a labeled upload for each requested item. Before publishing, choose file types, retention practices, and access settings appropriate for the information collected.
Use a repeatable principal group with separate name, role, contact, and ownership-percentage fields. This is clearer than combining multiple owners in one paragraph.
Yes. Add a separate section for agent ID, office, pricing, equipment, source, and notes. Keep internal labels distinct from applicant questions.
Yes. Makeform is unlimited free for generation, editing, publishing, and responses. The paid tier only removes the Makeform badge.
No. The form organizes information; it does not approve applicants, verify answers, set terms, or guarantee an account. Communicate review steps and decisions separately.
Replace scattered merchant packets.
