Prepare a clear business overview, locate the records you already have, and identify the questions your provider needs to answer. A useful merchant account application checklist separates information that is ready from documents that have actually been requested.
Use the worksheet below to organize the conversation. It is a preparation tool, not a universal bank requirement or a promise of approval. If you need the underlying account terminology first, read our merchant account guide.
Start with a short business brief
Before gathering files, write five sentences about the business. Describe what you sell, where customers order, how they pay, when you deliver, and who handles customer questions. Use specific products and services rather than a broad label such as “e-commerce.”
Then add the legal business name, any trading name, operating location, website, and person coordinating the application. Keep this overview separate from sensitive identity or banking documents.
Provider requests can include ownership information, sales channels, processing history and expected volume, with supporting records varying by business and provider. Stripe's application guide describes these categories. Confirm what applies to your application rather than treating every example as mandatory.
For existing activity, identify the period your figures cover. For future activity, label the figures as projections. Do not combine last month's actual sales and a future growth estimate into one unexplained number.
Copy this application-readiness worksheet
Fill in the available and missing columns before your first review. A row can remain “question pending”; that is more useful than guessing. Record where a file is kept, not its sensitive contents.
| Area | Available | Missing or needs updating | Question for the reviewer |
|---|---|---|---|
| Business identity | Legal and trading names; record location: ___ | Difference to explain: ___ | Which registration or business records apply? |
| Ownership and signers | Responsible contact identified: ___ | Person or detail to confirm: ___ | Which people need verification, and how? |
| Products and sales channels | Offer summary and public URLs: ___ | Channel or offer missing from summary: ___ | Is each proposed activity supported? |
| Payment pattern | Dated figures or labeled projections: ___ | Period or definition to clarify: ___ | Which volume and transaction-size figures do you need? |
| Funding account | Bank contact or record location: ___ | Name or account detail to confirm: ___ | What proof is accepted for funding verification? |
| Existing processing | Provider names and available statement periods: ___ | Missing period or unexplained adjustment: ___ | Which statements or reports should we supply? |
| Delivery and support | Policy links and delivery outline: ___ | Inconsistency to resolve: ___ | What operational evidence is relevant? |
| Submission route | Verified recipient and instructions: ___ | Access or permission still needed: ___ | Where should sensitive records be uploaded? |
Assign one person to maintain this sheet. Add a date beside any answer that changes, and keep earlier provider requests so you can see what has already been resolved. The worksheet should show the application's status without becoming a second database of identity documents.
Have the overview ready, even if some questions remain. Tell NUMUS what you sell and ask which records are relevant to your review.
Check the website against the business you described
Open your site as a customer would, including on a phone. Follow one offer from its landing page to the final checkout step without completing a purchase. Can someone understand the purchase and find help?
Stripe's website checklist covers clear descriptions, purchase currency, accessible support, relevant fulfillment policies, and promotion terms. Those are Stripe's published expectations; they are a useful reference, while your provider must confirm its own requirements.
Use this short review to find inconsistencies:
- Offer: Does the landing page describe the same product or service as checkout?
- Price: Are the amount, currency and any recurring charges understandable?
- Delivery: Can the customer tell when and how they receive the purchase?
- Changes: Are the relevant cancellation, return and refund instructions easy to find?
- Help: Does the advertised support route work, and does someone monitor it?
Write down the page and the correction needed. A policy copied from another business may describe operations you do not have; review the wording against your actual process.
Organize processing history without hiding the context
If you already accept cards, list every relevant processing provider and the statement periods available. Ask which periods the reviewer wants before compiling a large file package. Keep the source statements intact and put your explanation in a separate note.
For example, Chase's statement support guide distinguishes sales, refunds, disputes, fees and funding. Those categories explain why a deposit total alone is not a complete picture of activity. Your provider's report format may differ.
A useful covering note identifies a period, the issue visible in it, and what changed afterward. If a refund spike followed a delayed shipment, describe the delay and the customer response accurately. Do not remove the affected month from an otherwise continuous history to make the record look cleaner.
If a statement entry is unfamiliar, use our merchant statement guide to organize your questions. Ask the current provider to explain entries you cannot reconcile.
Resolve mismatches before sending the package
Compare the business brief, website and records side by side. Different names or dates may have a straightforward explanation, but the reviewer should not have to infer it.
For a fictional example, suppose an application says “ready-to-ship homeware,” while the website advertises a collection available only by preorder. The useful correction is an accurate account of both sales models and their delivery timing. Renaming the preorder collection does not resolve the difference.
Keep a small issues log:
| Issue | Who will resolve it? | Evidence or answer | Status |
|---|---|---|---|
| Trading name differs from legal name | ___ | Explanation or requested record: ___ | ___ |
| Website timing differs from actual delivery | ___ | Updated page and operating detail: ___ | ___ |
| Requested statement period is unavailable | ___ | Provider-approved alternative: ___ | ___ |
For coaching programs, our coaching application preparation guide goes further into the relationship between payment and delivery. Keep this general checklist as the central record of requests.
For travel businesses, connect each customer payment to the trip date, supplier obligations and refund owner. Our travel merchant account guide and printable planner help organize those details before a processing review.
Taking deposits or progress payments for construction work? Our credit card processing guide for contractors and printable planner connect project milestones, transaction sizes and delivery timing to your merchant account review.
Preparing an account for a dental practice? Use our dental office credit card processing guide and comparison worksheet to document patient payment channels, processing costs and the software workflow you need.
Confirm the document handoff and next action
Ask your contact which documents are needed, whether complete files or particular pages are required, and which secure submission channel to use. Verify an unexpected upload request through a contact route you already trust. Do not paste identity numbers, bank statements or customer card details into the initial inquiry message.
After submitting requested materials, record the date, recipient and reference number. Ask what remains outstanding and who owns the next step. “Sent” and “accepted as complete” are different statuses in your own tracking sheet.
Application questions
How many months of statements should I prepare?
Ask the reviewing provider which periods and report types it requires. Gather what is available, identify gaps, and request an acceptable alternative rather than assuming a fixed number applies to every business.
What if my business has no processing history?
Say that clearly. Label estimates as estimates and ask what the provider needs for a new business. Do not create statements or present projected sales as completed transactions.
Does completing the checklist mean I will be approved?
No. Organizing the information prepares you for review; it does not determine the decision. For a bank-specific example, Wells Fargo makes its merchant services subject to application, credit review and approval. Your proposed provider determines its own requirements and terms.
Bring your business brief and unresolved questions to NUMUS. The next step is to establish which information applies to your situation and how to supply it.
Sources are linked beside the relevant explanations. Read our editorial approach.
Turn this guide into a practical next step: use the merchant account readiness checker to create a personalized preparation checklist and download it for your provider conversation.