Questions to Ask a Payment Processor Before Signing

Before you sign anything, ask for these in writing: a line-by-line fee breakdown (interchange + assessments + markup), a sample monthly statement, the full contract with ETF terms, funding timelines and reserve policies, PCI/SAQ guidance, chargeback support details, hardware and integration specs, and an onboarding timeline. That list covers the critical questions to ask before signing with any payment processor. Get verbal answers confirmed in writing before you commit.

Before your next processor call, run through this checklist:

What is the full fee breakdown — interchange, assessments, processor markup, gateway, batch, and statement fees?
Can you provide a sample monthly statement from a similar merchant?
What is the contract length, auto-renewal policy, and exact early termination fee (ETF) in dollars?
What are average deposit times for card-present, e-commerce, and keyed transactions?
Will you hold a rolling reserve, and if so, what percentage and for how long?
Which PCI SAQ type will I be required to complete, and why?
How does your chargeback dispute process work, and what does it cost?
What hardware, POS, and integration support is included?

Immediate next step: Request a sample monthly statement and a copy of the proposed contract before any conversation goes further. Review both before you sign.

What questions should you ask about fees before signing?
What contract terms should you verify before you commit?
How do settlement timing and reserve policies affect your cash flow?
What PCI and security evidence should you request?
What hardware and integration questions should you ask?
What support and SLA commitments should you get in writing?
How should you evaluate chargeback and dispute support?
How do you spot hidden fees on a monthly statement?
What should your onboarding timeline look like?
What are the red flags that should make you walk away?
A practical evidence checklist for your vendor review
Key Takeaways
What most merchants get wrong about processor due diligence
Card Service Professionals can review your processor terms before you sign
Useful sources for deeper reading

What questions should you ask about fees before signing?

Interchange-plus pricing is the most transparent model available, and any processor that refuses to offer it or explain it clearly is hiding margin. Tiered pricing bundles fees into “qualified,” “mid-qualified,” and “non-qualified” buckets that routinely bury markup where merchants can’t see it.

Demand a written, line-by-line fee ledger before any agreement. Here is every line item to verify:

Fee Type	What to Ask	Typical Range
Interchange	Exact pass-through rate by card type	Set by card networks
Assessment	Visa/Mastercard network fee	Set by card networks
Processor markup	Basis points or flat per-transaction	Negotiable
Gateway fee	Monthly or per-transaction	Varies by provider
Batch/settlement fee	Per daily batch	Typically a small fee per batch
Statement fee	Monthly	A monthly fee that varies by provider
PCI non-compliance fee	Monthly if not compliant	A monthly fee that processors may charge if compliance lapses
Cross-border surcharge	Per international transaction	A small percentage fee applied to international transactions
Currency conversion	Per foreign-currency transaction	A percentage fee on currency conversions

Pro Tip: Ask for a real monthly statement from a merchant in your industry and volume range. A processor willing to share one is confident in their pricing. One who deflects almost always has something to hide.

A $0.25 batch fee sounds trivial. Run two batches a day for a year and that’s $182.50 before you’ve paid anything else. Small fees compound fast, which is exactly why processors bury them.

For a deeper audit of your current or proposed statement, the payment cost audit guide from Card Service Professionals walks through each line item step by step.

What contract terms should you verify before you commit?

Legacy processors routinely lock SMBs into multi-year evergreen contracts with automatic renewals and early termination fees that can be substantial. The headline rate looks fine. The contract is where merchants get hurt.

Before signing, work through this numbered checklist:

Contract term length. Ask for the exact start and end date and whether the term auto-renews.
Auto-renewal notice window. Request language requiring at least 60 days’ written notice before renewal locks in.
ETF formula. Insist the ETF be expressed in actual dollars, not vague “liquidated damages” language.
Price-change clauses. Confirm whether the processor can raise rates mid-term and what notice they must give.
Data access after termination. Add a contract addendum guaranteeing access to your full transaction history after closure.
Dispute resolution. Confirm whether disputes go to arbitration or litigation and in which jurisdiction.

Push for month-to-month terms or a 30–90 day trial period. If the processor won’t budge on term length, negotiate a defined exit schedule with a capped ETF. Never accept verbal promises — every term belongs in the written agreement.

How do settlement timing and reserve policies affect your cash flow?

Funding speed varies more than most merchants expect. Card-present transactions typically settle in one to two business days, but e-commerce and keyed-in transactions can take longer, and weekend or holiday processing often adds another day. Ask for the exact deposit timeline for each channel you plan to use.

Reserve policies are where cash flow surprises get expensive. Some processors hold 5–10% of transactions for 90–180 days as a risk buffer, which can quietly drain working capital. If your business is seasonal or high-volume, that hold can represent a significant chunk of operating funds. If a reserve hold would strain your operations, a business line of credit can bridge the gap while reserves are being released.

Get these items confirmed in writing before you sign:

Average deposit time for card-present, e-commerce, and keyed transactions
Whether weekend or holiday processing delays apply
Reserve percentage, hold duration, and release schedule
Written confirmation if your business qualifies for a reserve exemption
Guaranteed access to transaction history after account closure

Ask the processor to walk through a $1,000 sale scenario: when does the money hit your account, and what, if anything, gets held back?

What PCI and security evidence should you request?

Processors that cannot identify which SAQ type applies to your business model are a genuine red flag. SAQ type depends on how you accept cards and whether card data ever touches your systems. The difference matters: SAQ A covers roughly 30 questions for merchants using fully hosted checkout, while SAQ D can run to approximately 330 questions for merchants storing or transmitting card data directly.

The simplest path is an architecture where card data never touches your systems at all. Hosted fields, redirect checkouts, and tokenization all accomplish this. Ask the processor explicitly whether their integration keeps you at SAQ A.

Pro Tip: Request the processor’s own Attestation of Compliance (AOC) as a service provider. A compliant processor should hand this over without hesitation. If they stall or say it’s not available, treat that as a serious warning.

PCI compliance remains the merchant’s responsibility even when a processor is fully compliant. The processor can reduce your scope, but your terminals, staff practices, and network environment are still yours to manage. Confirm your merchant level with your acquirer, and consult a Qualified Security Assessor (QSA) if you’re unsure which controls apply.

Security checklist to verify before signing:

Encryption in transit and at rest
EMV support for all card-present terminals
Tokenization for stored or recurring transactions
Breach response policy and liability/insurance coverage
ASV scan access or scan reports where applicable

What hardware and integration questions should you ask?

Compatibility problems discovered after signing are expensive. Get the answers before you commit.

Question	What to Confirm
Terminal models supported	List of certified hardware; whether it’s included, leased, or purchased
POS software compatibility	Named POS vendors and versions the processor supports
Shopping cart / gateway plugins	Which e-commerce platforms integrate natively
API and SDK access	Documentation availability, sandbox credentials, and support SLA
Integration timeline	Estimated days from contract to live processing
Device management fees	Monthly per-terminal fees, if any

Ask for a test account and sandbox credentials before go-live. If the processor doesn’t offer a sandbox environment, that’s a gap worth flagging. Also confirm who owns the hardware if you cancel — some lease agreements require returning terminals or paying a buyout.

What support and SLA commitments should you get in writing?

Processors with dedicated U.S.-based account teams resolve problems faster than ticket-based or offshore support models. When your terminal goes down at 6 PM on a Friday, “submit a ticket” is not an acceptable answer.

Request these support commitments in writing:

Support hours: 24/7 vs. business hours only, and whether phone support is included
Guaranteed first-response time and resolution window for critical issues
Whether support is U.S.-based or routed offshore
A named account manager for onboarding and ongoing questions
Escalation path for unresolved issues (name, title, direct contact)
Written SLA with defined remedies if response windows are missed

A processor who won’t commit to response times in writing probably doesn’t meet them consistently.

How should you evaluate chargeback and dispute support?

Strong processors provide an evidence-tracking dashboard and immediate chargeback notifications. Weaker ones collect a fee — often $15–$50 per dispute — and hand you a stack of paperwork to figure out yourself. The difference shows up fast in a high-volume month.

Ask for a live walkthrough of the chargeback dispute interface before you sign. A processor confident in their tools will show you. One who hedges or says “we’ll walk you through it after onboarding” is telling you something important.

Pro Tip: Request the processor’s chargeback representment win-rate metrics. Not every processor tracks this, but those who do and share it openly are the ones actually invested in helping you recover revenue.

Confirm which fraud tools are included: AVS (Address Verification Service), CVV checks, 3-D Secure authentication, and any machine-learning rules. Ask whether those rules are managed for you or whether you configure them yourself.

How do you spot hidden fees on a monthly statement?

The fees that hurt most are the ones that don’t show up in the sales pitch. Request a sample monthly statement and an exported interchange-level report for at least one full month before signing.

Statement red flags to look for:

Monthly minimum fees charged when volume falls short
PCI non-compliance fees appearing without any notice or resolution path
Batch fees listed separately from transaction fees
Statement fees billed as a flat monthly charge
Gateway fees billed in addition to processor markup
Cross-border surcharges on any card issued outside the U.S.
Currency-conversion markups on foreign-currency transactions

If you see an unexplained line item, ask for a written explanation tied to the specific contract clause that authorizes it. A processor who can’t point to the clause in the contract doesn’t have a good answer.

For a full walkthrough of what each line means, the payment processing red flags guide from Card Service Professionals covers the most common traps merchants miss.

What should your onboarding timeline look like?

A realistic onboarding timeline runs from contract signing through go-live in two to four weeks for straightforward setups, longer for custom integrations. Ask the processor to provide a written milestone plan covering: contract signed, account provisioned, hardware shipped, integration tested, pilot period, and go-live date.

Before cutover, run through this go/no-go checklist:

Funds test: process a small transaction and confirm it settles correctly
Settlement verification: confirm deposit timing matches the written agreement
Refund flow test: process a refund and verify it posts to the correct account
Reconciliation sample: match a day’s transactions to the settlement report

Request a rollback plan and a defined post-launch support window. If something breaks in week one, you need a clear path to resolution, not a general support queue.

What are the red flags that should make you walk away?

The most common mistake merchants make is fixating on the headline transaction rate while ignoring contracts and reserve policies. By the time the evergreen clause kicks in, it’s expensive to leave.

Walk away if you see any of these:

Refusal to provide a sample monthly statement
Vague or bundled pricing with no interchange-plus option
Unwillingness to share the full contract before signing
Liquidated-damages ETF language with no dollar cap
Unexplained reserve holds with no written release schedule
No chargeback dashboard or representment support

If you’ve already signed a contract with problematic terms, here are five steps to limit exposure:

Document every fee discrepancy in writing and send it to your account manager.
Request a formal contract review citing the specific clause in dispute.
Negotiate a mutual exit or fee waiver in exchange for a referral or extended notice.
Consult a business attorney if the ETF exposure is significant.
Review your options for switching processors and calculate the true cost of staying versus leaving.

A practical evidence checklist for your vendor review

Use this list to request documentation from any processor you’re evaluating:

Sample monthly statement from a similar merchant (same industry, similar volume)
Full proposed contract and terms of service for legal review
Processor’s Attestation of Compliance (AOC) as a PCI DSS service provider
ASV scan reports or scan access confirmation
Written SLA with response and resolution windows
Sandbox or test account credentials before go-live
Written reserve policy and exemption confirmation if applicable

Card Service Professionals works with U.S.-based merchants across a range of industries and can walk you through a statement review or contract checklist before you commit to any provider. The small business payment processing checklist is a practical starting point for organizing your vendor evaluation.

Key Takeaways

Signing with the wrong payment processor costs more than the difference in rates — it costs time, cash flow, and leverage you won’t get back until the contract expires.

Point	Details
Demand interchange-plus pricing	Tiered pricing hides markup; always request a line-by-line fee breakdown and a sample statement.
Negotiate contract terms upfront	Push for month-to-month or a 30–90 day trial; get the ETF formula in dollars, not vague penalty language.
Verify PCI SAQ type before signing	A processor who can’t identify your SAQ type is a red flag; target SAQ A with hosted or redirect checkout.
Get reserve and funding terms in writing	Some processors hold 5–10% of transactions for 90–180 days; confirm the release schedule before you commit.
Card Service Professionals	Offers U.S.-based statement reviews and contract guidance to help merchants avoid costly processor mistakes.

What most merchants get wrong about processor due diligence

The conventional wisdom says “compare rates.” That framing is almost always wrong, and it’s the reason so many merchants end up trapped in contracts they didn’t read carefully enough.

The rate is the easiest thing a processor can manipulate. Show a merchant 1.7% and bury a $35/month statement fee, a $0.25 batch fee, and a $79 PCI non-compliance fee, and the effective rate on a $10,000/month business climbs well past what a slightly higher headline rate would have cost. The math isn’t complicated once you run it. The problem is that most merchants never run it because they’re focused on the number they were shown, not the number they’ll actually pay.

The other mistake is treating the contract as a formality. Evergreen clauses with 60-day notice windows are standard in legacy processor agreements. Miss the window by a week and you’re locked in for another year. That’s not a loophole — it’s the business model.

The questions that actually protect you aren’t about rates. They’re about what happens when something goes wrong: when a chargeback hits, when you need to switch, when a reserve hold freezes cash you were counting on. Ask those questions first.

Card Service Professionals can review your processor terms before you sign

Signing with a processor before anyone has reviewed the contract is one of the most common and avoidable mistakes small business owners make. Card Service Professionals is a U.S.-based independent agent representing several of the country’s leading merchant service providers, which means the goal is finding the right fit for your business, not pushing a single product.

The practical value: Card Service Professionals can compare interchange-plus pricing across multiple providers, flag contract clauses that commonly trap merchants, and walk you through a statement review so you know exactly what you’re agreeing to. Cash discount programs, full electronic payment options, and current POS equipment are all on the table. No vague “effective rate” pitch, no evergreen surprises.

Ready to see what your processing actually costs? Start with a free review or visit Card Service Professionals to connect with an advisor today.

Useful sources for deeper reading

PCI Security Standards Council — Merchant Resources: Primary source for PCI DSS requirements, SAQ types, and the official vendor-question guide used throughout the security section.
PCI SSC Guide to Safe Payments: Practical PCI guidance for small merchants on tokenization, encryption, and outsourcing card processing to reduce scope.
PCI SSC Questions to Ask Your Vendors: Official checklist of security questions to ask payment terminal vendors, service providers, and processors.
Spark — The True Cost of Accepting Payments: Source for fee ranges (batch fees, statement fees, cross-border surcharges, currency-conversion markups) used in the fee table.
Celeretech — 10-Point Payment Processor Due Diligence Checklist: Covers evergreen contracts, reserve policies, SAQ guidance, and chargeback support evaluation; primary source for contract and security sections.
SmallBizHandbook — PCI DSS for Small Business: SAQ complexity reference (SAQ A vs. SAQ D question counts) used in the security section.
Compass ITC — PCI Compliance QSA Field Guide: QSA guidance on confirming merchant level and when to bring in a qualified assessor.

Uncategorized