By NUMUS editorial team
Before accepting a processing offer, turn the agreement into an operating record: who provides each service, when money moves, which charges can arise, and who handles problems or closure. A clear percentage does not answer those questions.
The goal is to obtain account-specific explanations tied to the written documents. This guide helps you prepare that conversation; it does not determine the legal effect or enforceability of a clause. Questions about personal guarantees, liability or disputed obligations belong with a qualified adviser who can review the actual agreement.
Use our processing fees guide to organize cost categories and our quote-comparison worksheet for price arithmetic. Here, concentrate on how the proposed relationship would work after the account opens.
Assemble the complete set of documents
Ask the provider to identify the documents that apply to your proposed account, including the application, agreement, fee schedule and any service-specific terms. Record the version or date, the entity named in each document and where the applicable terms can be retrieved later.
Separate a sales presentation from a written account term. If a representative's explanation appears different from the documents, describe the difference and request clarification before treating it as resolved.
Create a service list for processing, the gateway, equipment, software and any additional subscriptions. For each, ask:
- Who supplies the service and who bills for it?
- Is it included in this agreement or covered by another document?
- Who can confirm pricing, change settings and handle account questions?
- Does ending one service end the others, or is a separate request needed?
This list is a completeness check. It does not assume your arrangement contains every service or that separate providers are involved.
Make a terms-confirmation record
Use one row for each topic. Keep the answer beside a document reference, the provider contact and any remaining question. “Not applicable, confirmed by provider” is different from a blank space.
| Topic | Question to resolve | Evidence to keep |
|---|---|---|
| Term and renewal | When does the term start, and what happens at its end? | Applicable clause, dates and notice instructions |
| Recurring costs | What is charged monthly, annually or when activity is low? | Fee schedule and calculation basis |
| Funding | What starts the timing clock, and what exceptions apply? | Account-specific funding terms and reporting example |
| Reserves or holds | What can be withheld, changed, applied or released? | Reserve provision and explanation of the mechanism |
| Equipment and software | Who owns it, who supports it, and what ends its billing? | Purchase, lease or service documents as applicable |
| Support and disputes | Which team handles each problem, and how are notices received? | Contact route, portal access and escalation instructions |
| Changes and exit | How are changes communicated, and how is closure confirmed? | Notification route, closure process and remaining obligations |
Add four working fields to every row: confirmed answer, open question, responsible person, follow-up date. Avoid a single “agreement reviewed” checkbox when several answers are still missing.
Ask when funds become available and when they are sent
A phrase such as “daily funding” needs a defined starting event and destination. Ask whether it describes payment settlement, the provider initiating a transfer or money becoming available at your bank. Record the cutoff time, time zone, business-day definition and treatment of holidays.
Stripe's payout documentation, for example, separates the time needed for funds to become available from the schedule for sending available funds. Changing its payout schedule does not itself accelerate settlement. This distinction helps frame a question; it does not establish another provider's timing. Stripe: Payout schedules and settlement timing.
Ask what happens during an account review, a failed bank transfer or a change in the business. Request a sample explanation connecting a sale or batch to the payout report, including any deductions. Do not treat a general example as a funding promise for your account.
For reserves, ask for the calculation base, release conditions, reporting and circumstances that can change the arrangement. Square's payment terms provide one specific example: they describe reserve funding and permit the reserve to be increased, reduced or removed under its terms. Those provisions apply to Square, not every account. Square: Payment terms, reserve section.
Our rolling-reserve guide provides a separate worksheet for modeling an actual reserve provision. Keep that exercise separate from processing-fee totals.
If these questions reveal gaps in the proposed arrangement, start with the business context and the written terms you need clarified. Discuss your account terms.
Identify charges that depend on an event
Go beyond asking whether there is a monthly fee. Ask which charges depend on transaction activity, refunds, disputes, optional services, account changes or the end of the relationship. For each applicable charge, record the amount or formula, trigger, collection method and document reference.
For a minimum, ask what counts toward it and when a shortfall is assessed. For an annual amount, ask when the first charge occurs. For a promotional concession, record its end date and the subsequent terms. Ask how notice of pricing or service changes reaches you and which staff member will monitor that channel.
Keep equipment and software questions concrete: purchase or rental, included or separately billed, replacement support, return instructions and any separate service term. Do not infer that a device described as included has no continuing conditions; obtain the applicable answer in writing.
Plan support before the first urgent problem
Record the route for funding questions, technical failures, billing corrections and disputes. Ask which hours apply, how cases are identified and what escalation is available. Distinguish an advertised support channel from a promised response or resolution time.
Chase's support page, for example, routes users differently depending on how they established their Payment Solutions account. It illustrates why the correct support path can depend on the account arrangement, even within one brand. Chase: Payment processing support.
Decide who on your team receives notices, who can access the reporting portal and who covers absences. Ask what records can be exported and how access changes if processing stops. For disputes, confirm where notices arrive and how the provider communicates the applicable response deadline; do not substitute a generic deadline from another account.
Clarify closure before you need to use it
Ask how to request closure, where notice must go, whether timing affects charges and what confirms completion. Identify separate gateway, equipment or software arrangements that need their own answer. Record what happens to pending refunds, disputes, reserves and reporting access.
Square's payment terms explicitly address amounts that can remain owed after termination and identify provisions that survive it. That is a provider-specific example of why stopping new transactions should not be treated as proof that every responsibility has ended. Square: Termination and account closure.
Consider this fictional review note: “The sales discussion covered processing cancellation, but the proposed terminal-rental document names a separate supplier. The provider has not yet confirmed the return destination or when rental billing stops.” The useful next action is to resolve those two questions with the responsible supplier—not to invent a cancellation date or assume one notice covers both services.
Leave with answers someone else can use
Before moving forward, have another person use the record to find the funding explanation, support contact and closure instructions. If the answer depends on remembering a phone call, add the written clarification and its date.
Keep unresolved points visible. A completed record does not guarantee approval, uninterrupted processing or a particular outcome; it gives the business a clearer account of what has been confirmed. Share a summary first and request an appropriate channel if supporting documents are needed.