← Back to blog

Payment Processor RFP Checklist for U.S. Merchants

November 13, 2026
Payment Processor RFP Checklist for U.S. Merchants

A strong payment processor RFP does three things: it shows vendors your real transaction profile, it forces every bid into the same itemized pricing format, and it asks for the reporting that lets you confirm the contracted rate is the rate you pay. Build the checklist around those three goals and the comparison almost runs itself. Pricing transparency is the deciding factor in most bids, which is why we built PaySec around Network Offset Pricing that passes through true wholesale interchange, with no minimums, no long-term contracts and detailed transaction reporting.

This checklist is written for restaurant groups, healthcare practices, ecommerce stores, CBD retailers and SaaS marketplaces. Use it as a working document: copy each section into your RFP, then score the answers.

Paysec
Make Payment Costs Easier to Compare
PaySec’s Network Offset Pricing and detailed transaction reporting support transparent payment costs, without minimums or long-term contracts.
Visit

TL;DR

  • Gather 12 months of processor statements and your volume, ticket size and card-present mix before you write a single question.
  • Require every bidder to price on the same itemized template: interchange, assessments, markup, per-transaction fees and every monthly or annual fee.
  • Ask for transaction-level reporting that shows interchange detail, so you can verify the contracted pricing line by line.
  • Verify PCI and security credentials on the official registries, and add your industry's requirements (healthcare, CBD, subscriptions).
  • Score with weights, compare total annual cost on your own data, and then audit the first statements against the proposal.

Table of Contents

Step 1: Gather the data vendors need to bid accurately

Vendors can only quote what you show them. Merchant Advisory's guide to issuing a payments RFP lists the background a good RFP should give: a business overview and mission, what you sell, headquarters and legal entity locations, headcount, where your customers are, average transaction value, monthly transaction count and volume, projected volumes for the next 12 months, how you process today, the third-party providers involved, your PCI compliance status, whether the solution is ecommerce, POS or omnichannel, and the regions and currencies you process in.

Add the items that move price the most:

  • Card-present vs. card-not-present split. A restaurant that is 95% swipe and dip prices very differently from a SaaS company that is 100% online.
  • Merchant Category Code (MCC). Risk classification affects eligibility and pricing, especially for CBD and other high-risk categories.
  • Chargeback and refund rates. Be honest. A bid built on accurate numbers holds up after onboarding.
  • Your current fee schedule and at least 12 months of statements. LegalClarity's RFP guide recommends attaching a year of statements so vendors submit tighter, more realistic proposals. Statements also expose seasonal swings, which matters for restaurants and retailers.
  • Average ticket and ticket range. Many fee structures behave differently on a $9 order than on a $4,000 B2B invoice.

Involve every team that touches payments before you finalize the scope. Merchant Advisory notes that bringing in all connected teams early helps capture every requirement. In practice that means finance (reconciliation and reporting), operations (terminals, tips, refunds), IT (integration) and whoever owns compliance.

Step 2: Pricing questions that make bids comparable

Pricing is where RFP responses diverge most, so this section needs the tightest structure. Do not accept a headline rate. Give bidders a fee template and require them to fill in every line.

Ask which pricing model is being quoted

The three models you will see are flat rate, interchange-plus and network offset. PaymentBrief's PSP selection RFP kit asks vendors to state their default model (blended, interchange-plus or other) and, for interchange-plus, to confirm interchange is passed through at actual network cost with no markup, plus a full sample fee schedule covering margin, per-transaction fee, monthly and gateway fees and any minimum monthly fee. Copy that structure.

Three payment processor pricing models compared

As a rule of thumb, LegalClarity explains that interchange-plus passes through the actual interchange rate set by the card networks and adds a fixed markup, so you see every cost component on the statement. For businesses with meaningful volume, it typically costs less than flat-rate pricing because you benefit from lower interchange categories such as basic debit and non-rewards cards.

Network Offset Pricing goes a step further. It is built on true wholesale interchange, so the card network cost is offset rather than marked up, and the structure is designed to eliminate hidden fees and flat-rate markups. Our own positioning is that merchants typically save 30-60% compared with major processors. For a side-by-side explanation, see our guide to flat-rate vs. interchange-plus vs. Network Offset pricing and our overview of how Network Offset Pricing works.

Require a line-by-line fee schedule

Your pricing template should have a row for each of these, with a dollar amount or percentage and a note on how often it is charged:

  1. Interchange, passed through at cost or not
  2. Card network assessments
  3. Processor markup, in basis points
  4. Per-transaction authorization fee
  5. Monthly or annual fees (gateway, statement, platform, account)
  6. Monthly minimums and shortfall charges
  7. Batch fees
  8. PCI-related fees
  9. Chargeback and dispute fees
  10. Cross-border and currency conversion charges, if you sell internationally
  11. Setup, integration, training and terminal fees
  12. Early termination or cancellation fees

LegalClarity points out that charges such as PCI non-compliance fees, batch fees, statement fees and gateway fees often sit outside the headline rate, and that authorization or misuse fees can rise with excessive retries on declined cards. If a bidder leaves a row blank, require them to write "none." A blank is not an answer.

For our own plans, the answers are straightforward: no monthly minimums, no long-term contracts, and terminal placement at $0 per month under Free Placement. Plan options (Network Offset, Flat Rate and Custom Enterprise) are on our pricing page.

Ask for a worked example on your own data

Give each bidder the same three sample months from your statements and ask them to calculate your total cost under their proposal. Then build one spreadsheet that compares total annual cost, not rates. A bid that looks cheaper by 0.10% can lose once monthly fees and per-item charges are counted. For a deeper walkthrough of the math, our interchange-plus merchant checklist shows how to calculate the components and negotiate markup.

Step 3: Processing capabilities and integrations

List the ways you take payments, then ask bidders to confirm support for each one in writing.

  • In-store: terminals, countertop and handheld devices, tip handling, split checks, offline mode. Ask what the hardware costs and who supports it.
  • Online: hosted checkout, embedded payment fields and direct API access; SDK coverage for your stack; webhook behavior and retry policy.
  • Mobile and field payments: card entry on a phone or tablet for delivery, service or pop-up sales.
  • ACH and bank transfers: useful for large invoices where card fees add up.
  • Recurring billing: card-on-file tokenization, retry logic on failed renewals, customer portals.
  • Authentication and fraud tools: 3D Secure handling, address and CVV checks, velocity rules.
  • Authorization performance: approval rates by issuer and geography, and what the processor does to improve them.
  • Multi-currency and split payments: relevant to marketplaces and international sellers.

These capability questions mirror what published RFP templates ask of gateways, such as hosted checkout, API coverage, 3DS handling and webhook policy. Whichever list you use, ask vendors to answer "supported today," "on the roadmap" or "not supported," and attach a date to anything on the roadmap.

Our merchant services cover in-store processing, an eCommerce gateway, mobile payments, ACH and bank transfers, recurring billing, enhanced data optimization and fraud prevention under one account, which means one reporting view and one statement across channels. Developers can review the payment gateway API, and subscription businesses can see our recurring billing solution.

Step 4: Reporting and data access

Reporting is how you prove that the price in the contract is the price on the statement. It is also the section most RFPs skip.

PaymentBrief's RFP kit asks whether transaction-level reporting is available in real time or in batches, whether raw transaction data is available through an API with full metadata (card type, issuer country, authorization code, decline reason, fees and settlement date), which reconciliation file formats are supported, whether interchange detail is shown per transaction for interchange-plus verification, and how long history is retained. It also argues that transaction-level data access is one of the most undervalued dimensions of provider selection, because teams without clean, machine-readable data spend far more time on reconciliation.

Turn that into RFP questions:

  1. Is reporting real time or batch, and what is the delay?
  2. Does each transaction show the interchange category, interchange amount, assessment and markup?
  3. Can we export to CSV or through an API for our accounting system?
  4. How are deposits matched to batches and fees?
  5. How many months of history can we access?
  6. Can you provide a sample report from a live merchant account?

This is a core strength of our platform: PaySec provides detailed transaction reporting and real-time reporting, so finance teams can see what each transaction cost and reconcile deposits without chasing support.

Step 5: Security and compliance

Security items are pass or fail. A bidder that cannot document them should not reach the scoring round.

Card data security

The PCI Security Standards Council's guidance for small merchants advises checking that payment terminals are PCI PTS approved, payment applications are PCI validated, and encryption solutions are PCI P2PE validated. For card-not-present transactions, it advises confirming that the service provider appears on the Mastercard or Visa registry of compliant service providers.

Put these in your RFP as documentation requests:

  • PCI DSS attestation of compliance for the processor and gateway
  • Terminal and application validation status
  • Tokenization and encryption approach
  • Independent audit reports such as SOC 2
  • Incident response and breach notification process

PaySec operates at PCI DSS Level 1 and SOC 2 compliance, and we handle compliance as part of the service so merchants are not left to assemble it themselves. If you are working through your own PCI obligations, this practical PCI compliance guide for small businesses is a clear walkthrough of what the requirements mean day to day.

Industry-specific requirements

Ask each bidder to confirm in writing that they support your sector's rules. Healthcare practices should ask how the processor handles payment data connected to patient accounts and should have their compliance officer or healthcare attorney review the answer against HIPAA obligations. CBD and other high-risk retailers should ask about underwriting criteria, approval timelines and reserve requirements. The next section covers each sector.

Step 6: Adjust the RFP for your industry

The same checklist applies to everyone, but the weight of each question changes. Use this table to decide what to emphasize.

Business typeAdd to your RFPWhy it matters
Restaurant chainsTerminal hardware cost and support, tip adjustment, pay-at-table, multi-location reporting, behavior during internet outagesThin margins and high card-present volume make per-transaction cost and uptime the main drivers
Healthcare practicesCompliance documentation, patient payment plans, recurring billing, statement clarity for office managersPayments touch patient accounts, so documentation and reporting need to be clean
Ecommerce storesGateway fees, checkout options, fraud tools, authorization rates, cart and platform integrationsCard-not-present transactions carry more fraud exposure and more fee line items
CBD retailersUnderwriting criteria, approval speed, reserve terms, backup processing, documented acceptance of your categoryApproval and continuity risk are as important as the rate
SaaS and marketplacesRecurring billing, retry logic, split payments, API coverage, ACH, payout reportingFailed renewals and payout flows directly affect revenue

B2B sellers should add one more item: enhanced data (Level 2 and Level 3) support. Passing richer invoice data with commercial card transactions can qualify them for lower interchange categories, so ask each bidder whether they support it and how. Our interchange optimization guide explains the approach, and enhanced data optimization is part of our merchant services.

PaySec serves merchants across SaaS, restaurants, eCommerce, healthcare, CBD and other high-risk retail, with fast approvals including high-risk verticals. You can see sector-specific detail on our industries page.

Step 7: Contract and service terms

A low rate can be undone by contract terms. Put each of these in the RFP and require a direct answer:

  • Term and renewal. Is there a minimum term? Does the agreement auto-renew?
  • Termination. Are there early termination fees or equipment lease obligations?
  • Price changes. Can the processor change markup or add fees during the term? What notice is required?
  • Reserves and holds. Under what conditions can funds be held?
  • Funding speed. When do deposits arrive, and what are the cutoff times?
  • Support. Hours, channels, named contact, escalation path and response targets.
  • Onboarding. Typical approval time, what documents are needed, and who guides you through setup.
  • Equipment. Who owns the terminals, what happens if one fails, and the replacement process.
  • Data portability. Can you export tokens and transaction history if you leave?

Our terms are simple: no long-term contracts, no hidden fees and no minimums. That makes the contract section of your scorecard quick to complete for us, and it is a useful benchmark for every other bidder.

Step 8: Score proposals and compare total cost

Once responses arrive, use a weighted matrix so the decision is documented and defensible. LegalClarity suggests weighting pricing at 30-40%, technical fit at 20-25%, security and compliance at 15-20%, support and service levels at 10-15%, and industry experience at 5-10%. Adjust the weights to your situation: a high-risk merchant may give approval and continuity more weight, while an enterprise ecommerce team may emphasize technical fit.

A simple scoring sheet looks like this:

CategoryWeightQuestions to score
Total cost of processing35%Annual cost on your sample data, fee completeness, price-change protection
Technical fit20%Integrations, channels, uptime, authorization performance
Security and compliance15%PCI validation, SOC 2, sector requirements
Reporting and data10%Transaction-level detail, exports, interchange visibility
Support and service10%Response targets, onboarding, named contacts
Contract terms5%Term, termination, reserves, funding speed
Industry experience5%Comparable merchants, references

Score each response from 1 to 5 per question, multiply by the weight, and total. Have at least two people score independently, then reconcile differences. Ask the top two or three bidders for references from merchants in your sector and for a live demonstration of the reporting view with a real statement.

For cost, do not compare effective rates alone. Convert every proposal into annual dollars using your own volume and ticket mix, including all fixed fees. Our 90 day playbook on card network fees offers a method for tracking cost over time once you switch.

Step 8: Score proposals and compare total cost

Step 9: Audit markup after you sign

The RFP does not end at signature. The first few statements are your proof that the proposal matches reality, and a markup audit is the follow-through.

  1. Calculate your effective rate. Divide total fees by total card volume for the month. Repeat for three months to smooth out swings.
  2. Sort every line into three groups. Pass-through costs (interchange and network assessments), processor markup (basis-point spread, authorization fees, monthly fees) and extras (PCI fees, minimums, annual fees, duplicate gateway charges).
  3. Match each line to your proposal. Any fee that was not in the fee schedule is a discrepancy to raise in writing.
  4. Check interchange categories. With transaction-level detail, you can see whether eligible transactions are landing in the expected category, particularly for commercial cards and card-present sales.
  5. Track markup separately. Your markup-only rate should stay constant unless you agreed to a change. If the effective rate moves while volume mix is stable, ask why.
  6. Keep a log. Record date, fee, amount and the explanation received.

With a Network Offset structure this audit gets shorter, because wholesale interchange is passed through and there are no hidden fees to hunt for. Our guides on eliminating hidden merchant fees and hidden charges ecommerce merchants often miss list the line items worth checking on any statement. If you want to understand the cost you cannot negotiate, start with interchange fees explained.

Our perspective: ask for transparency first

Most RFPs spend pages on features and a single line on price. We think that is backwards. Features are easy to match across serious providers. Price structure is where merchants lose money, and it is where the answers differ most.

Our view is simple: the best RFP question is "show me every dollar." When a pricing model passes through true wholesale interchange and shows each component on the statement, you can verify it. That is the idea behind Network Offset Pricing: merchants can offer customers flexible payment options while retaining full revenue, and the cost structure is visible instead of buried.

We designed PaySec for the merchants who read their statements: restaurant operators watching margins, practices that need clean documentation, ecommerce owners comparing gateway costs, CBD retailers who want fair processing, and SaaS marketplaces that need recurring billing and payout visibility. Our approach is no minimums, no long-term contracts, detailed transaction reporting, PCI DSS Level 1 and SOC 2 compliance, and savings that typically land between 30% and 60% versus major processors.

If your RFP rewards transparency, total cost and reporting detail, we are comfortable being scored on it.

PaySec Marketing Team

See what a transparent bid looks like

If you want a proposal that fits the template above, send us your statements. We will show you pricing built on wholesale interchange, with plan options of Network Offset, Flat Rate or Custom Enterprise for high-volume merchants, free terminal placement at $0 per month, and merchant services for in-store, online, mobile, ACH and recurring payments. You can review plans on our pricing page or start from the PaySec home page.

Paysec

Merchants who want to see how the numbers work first can read how Network Offset Pricing works and then bring their own statements to the conversation.

FAQ

How many vendors should I invite to a payment processor RFP?

Three to five is a workable range. Fewer than three gives you little to compare, and more than five makes careful scoring slow. Choose vendors that already serve your industry and can show comparable merchants, then hold every one to the same fee template and deadline.

How long should the RFP process take?

Plan for several weeks from issuing the RFP to a signed agreement: time for vendors to answer, for your team to score, and for demonstrations and reference checks with the finalists. Give vendors a firm response deadline and one round of clarifying questions, and share every answer with all bidders so the comparison stays fair.

What is the most common mistake in a processor RFP?

Comparing headline rates instead of total cost. A single percentage hides monthly fees, per-item charges and add-ons. Require an itemized fee schedule, apply every bid to the same sample months of your own data, and compare annual dollars.

Do I need an RFP if I only process a modest volume?

A shorter version still helps. Collect statements, ask two or three providers for an itemized quote on the same template, and compare total cost, contract terms and reporting. Even a one-page version of this checklist makes the quotes comparable.

What should I ask for in a processor's reporting?

Ask for transaction-level detail that shows the interchange category, interchange amount, assessments and markup for each sale, along with exports in formats your accounting team uses and enough history to review past statements. That visibility is what lets you confirm contracted pricing is being applied.

Sources