After you submit merchant account information, the next useful question is: who has the next action, and what remains unresolved? A submission receipt establishes that information was sent. It does not establish that the business has been approved or that payments are ready to go live.
As a concrete provider example, Wells Fargo states that its merchant services are subject to application, credit review of the business and its owners, and approval. That describes its offering, not a NUMUS approval promise. Wells Fargo Merchant Services.
This guide focuses on managing the review after submission. If you are assembling information for the first time, use the merchant account application checklist. For the larger picture, including the parties involved in accepting payments, see the NUMUS merchant accounts guide.
Confirm what was submitted and who is reviewing it
Start with a short handoff record. Save the submission date, business name, application reference if provided, and the name of your contact. Ask whether you have completed an initial inquiry, a provider application or a specific follow-up request. These can be different steps.
Then clarify three points:
- Who is coordinating questions with you?
- Who is responsible for the review or decision at this stage?
- What information, action or confirmation is still outstanding?
You may work through a sales representative or another intermediary rather than speak directly with every reviewer. Ask your contact to clarify the next step without assuming that a helpful conversation constitutes an underwriting decision.
Keep one current version of your business description. If your application describes a single purchase but your website sells a recurring program, identify the difference and explain the actual offer. The aim is a consistent, accurate description across the materials a reviewer sees.
Expect questions about how the business works
Review is more than checking whether every field contains text. Stripe’s credit-underwriting explanation, for example, discusses its assessment of business model, billing practices, processing history and financial position. It also identifies advance payment before delivery as a consideration. Those are examples of Stripe’s process; another provider may evaluate your application differently. Stripe credit underwriting process.
Prepare to explain an answer in ordinary business terms: what the customer buys, when they pay, when they receive it and what happens if the purchase is cancelled. Use your actual offer and records. A new business should clearly label estimates and should not present projected transactions as processing history.
When a request is unclear, ask what it is intended to clarify. “Please explain the service” could mean the deliverables, the price, the delivery period or the difference between two website packages. Responding to the wrong question creates another exchange without resolving the first one.
Use a review-request tracker
The following fictional tracker is an organizing tool, not a required document list or an example of a NUMUS customer. Copy its structure into a private worksheet. Keep sensitive documents in the provider’s designated submission system; the tracker only needs a reference and status.
| Request | Question to clarify | Owner | Response or evidence reference | Approved channel | Current status |
|---|---|---|---|---|---|
| R01: Explain the $1,200 service | Which deliverables and delivery dates are being reviewed? | Founder | Offer summary, version 2 | Confirmed provider portal | Submitted; acceptance not confirmed |
| R02: Explain payment timing | Does the reviewer need first delivery or completion date? | Operations lead | Service schedule, version 1 | Ask contact to confirm | Clarification requested |
| R03: Resolve a business-name mismatch | Which record needs correction? | Authorized owner | Corrected record reference | Confirmed provider portal | Receipt confirmed; review pending |
| R04: Supply processing history | What should a business with no history provide? | Founder | Explanation that processing has not started | Confirmed application channel | Awaiting provider guidance |
Add columns for date received, requested response date, submission date and the next person responsible. Avoid copying full identity or bank details into a shared project tracker.
Use explicit statuses: clarification needed, preparing, submitted, receipt confirmed, and resolved by reviewer. These are your internal labels. They do not replace the provider’s official application status.
“Sent” and “resolved” are different. When someone confirms receipt, ask whether the response answers the request or whether anything remains open. Close the tracker row only when you have that confirmation, or record that the provider closed it without further detail.
If you are exploring a processing relationship, NUMUS can start with your business description and the questions you still need answered.
Respond when a document does not exist
If you cannot supply an item, explain why and ask what the reviewer can accept. For example: “This business has not processed card payments, so it has no prior processing statements. What information should we provide instead?”
Stripe explicitly tells businesses to raise unavailable information early so possible alternatives can be discussed. That does not establish that an alternative will be accepted by every provider. Stripe’s underwriting guidance.
Do not manufacture records, omit an important qualifier or send unrelated documents simply to mark a request complete. Record the question and wait for guidance about what is useful. If the answer changes a previous statement, identify the correction and which version replaces the old one.
Handle website questions as specific changes
A website request needs a precise response. Stripe’s website checklist covers such items as clear product descriptions, customer contact information and relevant fulfillment policies. Its checklist is a provider-specific example, not a universal list of legal requirements. Stripe website checklist.
For each requested change, record the page URL, what changed and when it became publicly visible. If a reviewer identified unclear delivery timing, explain the corrected wording and point to the relevant section. A generic “website updated” message makes the reviewer search for the answer.
Before responding, open the page as a customer would. Check that the offer, price and policy agree with your actual operation. If you cannot resolve a conflict yet, say what remains undecided instead of publishing a promise your business cannot meet.
Ask for the decision and its remaining conditions
When you receive an update, ask what it means for this particular application. Avoid translating “looks good” or “documents received” into “ready to process.” Request written confirmation of the decision and any remaining conditions.
Use this decision checklist:
- What is the application’s current official status?
- Which business, offer and sales channels does the response cover?
- What actions or conditions remain before activation?
- Where are the proposed agreement, pricing and funding terms to review?
- Who should answer questions about those terms?
- Who confirms the account and the intended payment setup are ready?
If a requested term or condition is unclear, resolve it with the provider before treating it as agreed. This checklist helps organize questions; it does not determine whether an offer is suitable for your business.
Keep approval, setup and go-live separate
An underwriting decision is not the same task as configuring a checkout or preparing a terminal. Adyen’s standalone-terminal guide, for example, separates obtaining a live account from account setup, payout settings and terminal preparation. That sequence is specific to its in-person product. Adyen standalone go-live checklist.
Ask for the setup checklist that applies to your actual system, who owns each action and how completion will be verified. Use the provider’s testing instructions and confirm which environment is being used before processing transactions.
There is no useful universal deadline to insert into your tracker. Ask your contact for the next expected update, what it depends on and who will follow up. Record a date for your own follow-up without promising customers a launch date based solely on an application submission.
Bring your business description and unresolved questions to an initial NUMUS conversation. An organized review record gives the people involved a shared view of what has been answered and what needs attention.
Sources are linked beside the relevant explanations. Read our editorial approach.