Processor evaluation guide
What Questions Should I Ask a Payment Processor?
Ask questions that turn a sales presentation into a written, comparable operating plan. Focus on who provides each service, how your payment flow works, what the agreement requires, how support is handled, and which security responsibilities remain with your business.
Before the meeting
Describe your real payment workflow first
Prepare your sales channels, typical transaction types, locations, equipment, software, settlement needs, support hours, and data-handling practices. A useful proposal should respond to those facts instead of forcing every business into the same package.
Provider and account structure
Identify every party responsible for the service
Who is the contracting party?
Ask for the legal name shown on the agreement, who manages the merchant account, and which organizations provide processing, gateway, equipment, software, funding support, or customer service.
Who owns each support issue?
Ask which team handles applications, onboarding, chargebacks, deposits, terminals, integrations, security questions, account changes, and cancellation.
What business details drive the proposal?
Confirm the channels, transaction mix, products or services, estimated activity, and technical requirements used to prepare the offer.
What changes require notice?
Ask how to report new sales channels, locations, ownership, bank accounts, products, software, or materially different transaction activity.
Agreement review
Ask where each important term appears
Term and renewal
- What is the initial term?
- Does the agreement renew automatically?
- What notice method and deadline apply?
- Which documents make up the full agreement?
Changes and cancellation
- How are material changes communicated?
- What steps close every related service?
- What equipment-return rules apply?
- How is final account status confirmed?
Proposal assumptions
- Which volumes and transaction types were assumed?
- Which optional services are included?
- Which equipment or software is required?
- Which items require separate agreements?
Documentation
- Can every representation be added in writing?
- Who can answer contract questions?
- Which document controls if materials conflict?
- Can you keep a complete signed copy?
Operations and support
Test how the service would work after onboarding
Setup
Ask for the onboarding sequence, information requested, configuration responsibilities, training resources, testing process, and criteria for moving to live transactions.
Daily workflow
Ask how staff run sales, refunds, voids, batches, receipts, tips, recurring payments, or card-not-present transactions that apply to your business.
Reporting
Request a demonstration of transaction search, settlement reports, user permissions, exports, account notices, and the records needed for reconciliation.
Support
Confirm support channels and hours, escalation paths, device-replacement procedures, outage communications, and what information should accompany a case.
Security responsibilities
Clarify what the provider covers and what remains yours
PCI SSC states that outsourcing payment processing does not remove a merchant's responsibility to protect account data. Its current guidance calls for due diligence, written acknowledgment of responsibilities, clear shared-responsibility boundaries, and ongoing monitoring of relevant service providers.
Ask the provider
- Which services are covered by its current PCI DSS assessment?
- What evidence supports that scope?
- Which responsibilities does the agreement acknowledge?
- How are remote access and support access controlled?
- How are security updates and incidents communicated?
Ask internally
- Where can card data enter the business?
- Which staff roles need payment-system access?
- Who maintains networks, devices, websites, and integrations?
- Who reviews provider status and shared responsibilities?
- Who should receive security notifications?
Compare consistently
Use the same worksheet for every proposal
Record each answer beside the exact contract section or source document. Separate confirmed facts from verbal explanations and unresolved items. Compare the complete service scope, operational fit, responsibilities, and exit process—not a single headline claim.
Common questions
Payment processor evaluation FAQ
Should I rely on the sales presentation?
No. Use it to identify questions, then verify important terms in the complete agreement and official service documentation.
Why ask who provides each service?
Processing, gateway, software, equipment, support, and other functions may involve different entities. Knowing ownership helps route issues and review obligations.
What should I ask about PCI DSS?
Ask which offered services are within the provider's assessment, request relevant evidence, and document the responsibilities assigned to each party.
What if an answer is only verbal?
Request written clarification tied to the controlling document. Treat unresolved differences as open items before making a decision.
Last editorial review: August 12, 2026. Reviewed against current FTC payment-processor sales guidance and PCI SSC third-party service-provider responsibility guidance.
Next step
Turn the answers into a documented comparison
Send each provider the same workflow summary and question list, then match every important response to the agreement or current service documentation.
To learn more about how TSYS can help improve the way your organization accepts payments, markets to new customers, or manages its HR responsibilities, get in touch by calling 585-981-8463 to get started.
CONTACT US