Before you sign with a merchant payment solution provider, ask these 25 essential questions. Test business fit, payment APIs and integration, payment security and compliance, settlement and reconciliation, orchestration and scale, pricing, support, and customization. Ask for proof on every answer, not promises.

Two providers can demo the same card, QR, and SoftPOS acceptance while still delivering very different results. The gap shows up after go-live: integration effort, failed transactions, settlement breaks, and exit cost.

This guide is for banks, fintechs, PSPs, and payment facilitators buying a merchant payment platform. Each question covers why it matters, a good answer, the red flag, and the business impact.

Key Takeaways

  • Financial APIs are a controlled contract for data and money movement. They are not the bank, the license, the rail, or the settlement process.

  • The first HTTP response is not the transfer. Webhooks, exception states, settlement, and reconciliation decide whether operations can run.

  • Strong financial API architecture keeps channels, orchestration, and rails apart. That is what lets you add a corridor or partner without rewriting the app.

  • Wallet APIs must protect the ledger, including freeze, limits, failed cash-out, and close. Remittance APIs must cover quote, screen, route, pay, track, and match.

  • Cross-border APIs standardize the instruction. They do not create payout reach, liquidity, or a license in a market where no partner exists.

  • Security and compliance are separate jobs. Hardened calls do not replace KYC, AML, sanctions, or an audit trail tied to the transfer ID.

  • Build, buy, or hybrid should follow license model, on-call capacity, and time-to-market. Judge a financial API platform by failed states, data ownership, and exit terms, not by endpoint count.

What Should You Ask a Merchant Payment Solution Provider Before Buying?

Ask questions that expose how the platform behaves after go-live. Use this quick-reference table of all 25.

#Question✅ Strong answer❌ Red flag
1Which segments and channels are live?Named live deployments per channelRoadmap shown as live
2Who owns licenses, funds, and merchant contracts?Written responsibility matrix"We handle all compliance"
3Which methods, schemes, and currencies are live?Coverage by market"Global coverage", no detail
4How mature are the APIs and sandbox?Docs and sandbox before signingDocs only after contract
5How do you connect to our switch and core?Proven ISO 8583 and ISO 20022 adaptersCustom build for every link
6How are merchant onboarding and KYB handled?Configurable KYB and risk tiersManual, email-based onboarding
7What will implementation need from us?Named plan, owners, assumptionsFixed date before discovery
8Which PCI DSS scope stays with us?Current AOC with clear scopeCertificate without scope
9How is card data protected?Tokenization, HSM, 3DS2Vague "bank-grade security"
10Which fraud controls can we configure?Rules your risk team editsEvery rule needs a release
11How are AML, audit, and data residency handled?Audit trail, deployment choiceOne hosting option only
12Which settlement cycles and models exist?Configurable cycles, net and splitOne fixed cycle
13Can each transaction trace to settlement?Transaction-level fee and payout linkDaily totals only
14How are reconciliation exceptions closed?Automated matching, exception queueSpreadsheets
15How are refunds and chargebacks managed?Full dispute lifecycleDisputes handled by email
16How is routing configured, with failover?Rule-based routing, tested failoverSingle route
17What peak load is proven?Load-test evidence"Millions of transactions"
18What are the DR and RTO/RPO commitments?Tested DR, contractual targetsDR "in progress"
19What does the pricing model include?Itemized modules and feesOne headline rate
20Can we configure merchant pricing?MDR and IC++ in configurationCode change per tariff
21What do change and exit cost?Rate card and exit terms"Quoted when needed"
22What do the SLAs actually cover?Severity levels, exclusions, creditsUptime figure only
23Is the provider viable long term?References with your modelLogos, no calls
24How far can we brand and customize?Configuration and white-label portalsCustom code fork
25Who owns the data, and how do we exit?Full export, token migrationVendor-controlled exit

First Step: Define What Your Business Needs

Write requirements before the first demo. Otherwise the vendor defines the scope, and every platform looks like a fit.

RequirementDefine internally
Operating modelBank, PSP, PayFac, or fintech? Who holds the license?
MerchantsSegments, MCCs, sub-merchants, marketplaces
MarketsCountries, currencies, local schemes and rails
ChannelsPOS, SoftPOS, QR, e-commerce, payment links
VolumeCurrent and three-year volume, plus peak days
SettlementCycles, currencies, split payouts
StackSwitch, core banking, ERP, KYC providers

Business Fit and Use Cases (Questions 1–3)

Start with fit. A capable merchant payment provider is still wrong if its live deployments, legal role, or coverage do not match your model.

match-the-platform-to-your-business-goals-image

Q1. Which merchant segments, channels, and use cases are live today?

  • Why it matters: Production deployments prove capability; roadmaps do not.

  • Good answer: Named live clients by channel (POS, SoftPOS, QR, gateway) and model (direct, PayFac, marketplace).

  • Red flag: Roadmap features presented as live.

  • Business impact: Buying a roadmap delays launch and shifts development cost to you.

Q2. Are you the regulated entity or the technology provider, and who owns what?

  • Why it matters: License, scheme membership, merchant contracts, and funds flow set your obligations.

  • Good answer: A written responsibility matrix for acquirer, processor, sponsor bank, and vendor.

  • Red flag: "We take care of compliance" with no detail.

  • Business impact: Gaps here become audit findings, not IT tickets.

Q3. Which payment methods, card schemes, and currencies are live in our markets?

  • Why it matters: Coverage counts only where your merchants sell.

  • Good answer: Market-by-market card schemes, QR schemes, wallets, local rails, and settlement currencies.

  • Red flag: "We support 100+ methods" without market detail.

  • Business impact: Missing local methods means lost merchant volume and slower expansion.

Technology, Payment APIs, and Integration (Questions 4–7)

Integration quality decides time to market and how much control you keep. Test in a sandbox before commercial commitment.

open-apis-seamless-integrations-real-control-image

Q4. How complete are your payment APIs, SDKs, and sandbox?

  • Why it matters: Payment APIs decide integration cost and partner onboarding speed.

  • Good answer: OpenAPI docs, SDKs, test cards, lifecycle webhooks, idempotency keys, structured errors, and a versioning policy.

  • Red flag: Documentation available only after signature.

  • Business impact: Weak APIs stretch launch timelines and partner integration cost.

Q5. How do you integrate with our switch, core banking, and processors?

  • Why it matters: Few institutions replace everything at once.

  • Good answer: Proven adapters for ISO 8583 card messaging, ISO 20022 account messaging, REST APIs, and batch files.

  • Red flag: Every connection quoted as custom development.

  • Business impact: Reusable connectors cut integration cost and modernization risk.

Q6. How are merchant onboarding, KYB, and underwriting handled?

  • Why it matters: Onboarding speed drives merchant activation and revenue.

  • Good answer: Digital applications, KYB/KYC checks, MCC-based risk tiers, and approval workflows your team configures.

  • Red flag: Manual review through email and spreadsheets.

  • Business impact: Slow onboarding loses merchants; weak underwriting raises chargeback and fraud losses.

Q7. What does implementation require from our team, and how long will it take?

  • Why it matters: Hidden internal effort is a frequent cause of budget overruns.

  • Good answer: A phased plan with named owners, assumptions, certification steps, and dependencies.

  • Red flag: A fixed go-live date promised before discovery.

  • Business impact: Realistic plans protect launch dates and board commitments.

Payment Security and Compliance (Questions 8–11)

Ask exactly which controls the provider operates and which stay with you. Payment security is shared, and certificates cover only what they name.

Q8. What is your PCI DSS status, and which requirements remain with us?

  • Why it matters: PCI DSS v4.0.1 is the only active version, and its future-dated requirements became mandatory on 31 March 2025 (PCI SSC).

  • Good answer: A current Attestation of Compliance whose scope covers the service you buy, plus a responsibility split.

  • Red flag: A logo on a slide, or an AOC for a different product.

  • Business impact: Scope gaps expand your assessment cost and breach liability.

Q9. How do you protect card and account data?

  • Why it matters: Data protection sets fraud exposure and PCI scope.

  • Good answer: Tokenization, encryption in transit and at rest, HSM-based key management, EMV 3-D Secure (3DS2), and PCI MPoC-validated SoftPOS where offered.

  • Red flag: Generic "bank-grade security" claims.

  • Business impact: Tokenization shrinks the systems touching card data, cutting compliance cost.

Q10. Which fraud and risk controls are built in, and who configures them?

  • Why it matters: Fraud patterns change faster than release cycles.

  • Good answer: Velocity limits, rule engines, merchant risk scoring, and watchlists your risk team edits.

  • Red flag: Every rule change requires vendor development.

  • Business impact: Slow controls raise fraud losses and scheme monitoring exposure.

Q11. How do you support AML, audit trails, ISO 27001 controls, and data residency?

  • Why it matters: Regulators expect traceability and, in some markets, local data storage.

  • Good answer: Sanctions screening, immutable audit logs, scoped ISO 27001 or SOC 2 reports, and cloud or on-premise options.

  • Red flag: One hosting model regardless of jurisdiction.

  • Business impact: Residency gaps can block a market launch entirely.

💡 Expert Note for Compliance and Risk Heads

Request the AOC and ISO 27001 certificate early, then compare their scope with the modules in your proposal. A certificate that excludes the settlement engine or SoftPOS app does not cover your risk.

Also Read:Evaluating the Security and Compliance of Merchant Payment Solutions

Payment Settlement and Payment Reconciliation (Questions 12–15)

A processed payment is not automatically settled or reconciled. Operating cost and merchant trust are decided here, so test it as hard as checkout.

processing-is-not-the-finish-line-image

Q12. Which settlement cycles and models are supported?

  • Why it matters: Payment settlement terms are a commercial lever with merchants.

  • Good answer: Configurable cycles such as T+0 or T+1, gross or net settlement, MDR deduction, and split payouts.

  • Red flag: One fixed cycle for every merchant.

  • Business impact: Flexible settlement wins merchants and supports PayFac and marketplace models.

Q13. Can every transaction be traced to its settlement and fees?

  • Why it matters: Finance must explain every payout line.

  • Good answer: Transaction-level links between authorization, capture, fees, refunds, and the settlement batch.

  • Red flag: Settlement reports showing daily totals only.

  • Business impact: Traceability shortens month-end close and reduces merchant disputes.

Q14. How is payment reconciliation automated, and how are exceptions handled?

  • Why it matters: Breaks between platform, scheme, and bank files cost money daily.

  • Good answer: Automated multi-way matching, an exception queue with owners and ageing, and ERP export.

  • Red flag: Finance closing breaks in spreadsheets.

  • Business impact: Manual reconciliation scales headcount with volume.

Q15. How are refunds, chargebacks, and disputes managed?

  • Why it matters: Scheme deadlines for chargeback responses are strict.

  • Good answer: Dispute workflows with reason codes, evidence upload, representment, and deadline tracking.

  • Red flag: Disputes handled outside the platform.

  • Business impact: Missed deadlines mean lost revenue and higher chargeback ratios.

What payment data and reporting will each team receive?

A dashboard is not an operating system. Ask what is real time, what is batch, and what finance can export into the ERP.

TeamMinimum data
FinanceSettlement batches, fees, refunds, chargebacks, matches
OperationsTransaction status, failures, exception age
RiskDeclines, disputes, velocity, merchant alerts
ProductAuthorization rate and method mix
TechnologyAPI faults and webhook delivery
ManagementVolume, revenue, failure trend

Confirm retention period, export format, and whether custom reports are included or charged. A view that cannot be exported will not survive month-end.

Want to see one transaction traced from authorization to settlement, fee, and reconciliation in a single record?

Payment Orchestration and Scalability (Questions 16–18)

Ask for evidence, not adjectives. Scale and resilience should be proven with test results and contract terms.

Q16. How are transactions routed, and what happens when a route fails?

  • Why it matters: Payment orchestration protects approval rates and processing cost.

  • Good answer: Rule-based routing by BIN, currency, method, or cost across acquirers, with automatic failover.

  • Red flag: A single processor route with manual switchover.

  • Business impact: Smart routing recovers revenue from declines and outages.

Q17. What volume and peak load have you proven?

  • Why it matters: Salary days and promotions break untested merchant payment processing.

  • Good answer: Load-test results, TPS benchmarks, and live references at comparable volume.

  • Red flag: "We can process millions of transactions" with no evidence.

  • Business impact: Peak-day failures cost revenue and merchant confidence.

Q18. What are your availability, disaster recovery, and RTO/RPO commitments?

  • Why it matters: Outages stop merchant revenue instantly.

  • Good answer: High availability, tested DR, and contractual RTO and RPO targets.

  • Red flag: DR plans described as "in progress."

  • Business impact: Resilience protects revenue and satisfies outsourcing regulators.

Pricing and Total Cost of Ownership (Questions 19–21)

The lowest license fee is rarely the lowest cost. Model total cost of ownership over the contract life.

Q19. What is the pricing model, and what is excluded?

  • Why it matters: Headline rates hide module, environment, and integration fees.

  • Good answer: Itemized licensed, SaaS, or per-transaction pricing covering setup, modules, support, and environments.

  • Red flag: A single rate with "extras quoted later."

  • Business impact: Hidden lines erode the business case before year two.

Q20. Can we configure merchant pricing without code changes?

  • Why it matters: Merchant pricing is your revenue engine.

  • Good answer: MDR, interchange-plus-plus, tiered, and blended pricing set in configuration and applied at settlement.

  • Red flag: Each new tariff requires a vendor release.

  • Business impact: Pricing agility protects margin and speeds sales deals.

Q21. What do change requests, upgrades, and exit cost?

  • Why it matters: Over a contract's life, change can cost more than implementation.

  • Good answer: A published rate card, included upgrades, and priced exit support.

  • Red flag: "We'll quote when needed."

  • Business impact: Predictable change costs keep the roadmap affordable.

Support, SLAs, and Vendor Viability (Questions 22–23)

You are buying a long-term partner. Confirm what support covers and that the provider will be there to deliver it.

Q22. What do your SLAs and support actually cover?

  • Why it matters: An uptime figure means little without definitions.

  • Good answer: Severity levels, response and resolution times, 24/7 coverage, exclusions, and service credits.

  • Red flag: A single uptime number with broad exclusions.

  • Business impact: Clear SLAs cap incident cost and merchant churn.

Q23. How viable is the provider, and can we speak to comparable clients?

  • Why it matters: A failing payment solution provider becomes your continuity problem.

  • Good answer: Financial stability, a credible roadmap, and reference calls matching your model.

  • Red flag: Logos without reference contacts.

  • Business impact: Vendor viability protects multi-year investment.

Customization, White-Label, and Exit (Questions 24–25)

Customization should come from configuration, and exit terms should be agreed while you still have leverage.

Q24. How far can we brand and customize without forking the code?

  • Why it matters: Custom forks miss upgrades and raise maintenance cost.

  • Good answer: White-label merchant portals, apps, and dashboards, plus configurable workflows.

  • Red flag: Core changes delivered as a one-off code branch.

  • Business impact: Configuration-led customization keeps time to market short.

Q25. Who owns the data, and how do we exit?

  • Why it matters: Lock-in removes negotiating power at renewal.

  • Good answer: Contractual data ownership, full export in standard formats, token migration, and transition support.

  • Red flag: Exit terms controlled by the vendor.

  • Business impact: A clean exit path keeps future options and pricing open.

How to Score Merchant Payment Solution Providers

Score each area from 1 to 5, multiply by its weight, and compare totals. Then apply hard fails: a high score never overrides a missing control.

CategoryWeight %Score (1–5)Weighted score
Business fit and coverage15Score (1–5)Score x Weight
APIs and integration15Score (1–5)Score x Weight
Security and compliance15Score (1–5)Score x Weight
Settlement and reconciliation15Score (1–5)Score x Weight
Orchestration and scalability10Score (1–5)Score x Weight
Pricing and TCO10Score (1–5)Score x Weight
Support and vendor viability10Score (1–5)Score x Weight
Customization and exit10Score (1–5)Score x Weight
Total100NA____ / 500

These weights are illustrative, not an industry standard. Adjust them to your model, then keep them identical across the payment provider comparison.

Reject any vendor with one of these hard fails:

  • No current PCI DSS AOC covering the service you buy

  • No API documentation or sandbox before signature

  • No transaction-level settlement data

  • Unclear regulatory responsibilities

  • No data export or exit terms

Red flags that should pause the deal:

  • Roadmap features presented as live.

  • “We handle all compliance” with no responsibility matrix.

  • Documentation or sandbox only after signature.

  • Settlement reports show daily totals only.

  • Reconciliation closes in spreadsheets.

  • Every routing or pricing change needs a vendor release.

  • Scalability claims with no load-test or reference.

  • One headline rate, with extras quoted later.

  • No reference calls that match your model.

  • Exit terms controlled by the vendor.

Two or more should stop the process until the vendor answers in writing.

Which capabilities should be non-negotiable?

Not every advanced feature belongs in the RFP. Marking everything as mandatory delays the decision.

CapabilityPriority
Methods and schemes you need nowMust-have
API documentation and sandbox before signatureMust-have
Clear compliance and PCI scope splitMust-have
Transaction-level settlement and reconciliationMust-have
Configurable fraud controlsMust-have
Named implementation planMust-have
Data export and exit termsMust-have
Multi-acquirer routingDepends on your routing strategy
Advanced analyticsDepends on volume
AI-based optimizationNice-to-have

Build, White-Label, or Off-the-Shelf: Which Model Fits?

Build only if payment infrastructure is your differentiator and you have the team and time. Most banks, PSPs, and fintechs reach market faster on a white-label payment processing solution they configure and integrate.

FactorIn-house buildWhite-label platformOff-the-shelf PSP service
Time to marketLongestWeeks to monthsFastest
Brand and merchant ownershipFullFullLimited
CustomizationUnlimited, at your costConfiguration plus scoped extensionsMinimal
Upfront costHighestModerateLowest
Ongoing engineeringHighSharedLow
Merchant pricing controlFullFullLimited
Vendor dependencyLowestModerate, if exit is definedHighest
Best fitLarge processors with mature payment teamsBanks, PSPs, fintechs launching or modernizing acquiringSmall portfolios testing demand

Weighing build, white-label, and PSP models? Get a recommendation mapped to your markets, channels, and existing stack.

What Should You Test in a Payment Provider Demo?

a-demo-should-prove-the-operating-model-image

Give the vendor your script. A demo that shows only a successful sale proves very little.

  1. Onboard a merchant through KYB and assign MDR pricing.

  2. Run a card and a QR payment, then a declined one.

  3. Trigger a routing failover.

  4. Process a partial refund and a chargeback.

  5. Show the settlement file and a reconciliation exception.

  6. Export transaction data through the api.

If the vendor cannot complete steps 3 to 5, do not move to contract talks.

How DigiPay.Guru Supports Merchant Payment Infrastructure

DigiPay.Guru is a payment infrastructure provider, not a regulated acquirer. It supplies a white-label merchant acquiring solution, while you keep the license, the merchants, and the brand.

☑️ Merchant onboarding with KYB/KYC workflows and hierarchy, including PayFac sub-merchants

☑️ POS, SoftPOS, static and dynamic QR, payment gateway, and payment links

☑️ Payment routing, orchestration, and tokenization

☑️ Configurable settlement cycles, MDR deduction, and split payouts

☑️ Reconciliation with exception management and a financial ledger

☑️ MDR, interchange-plus, and tiered pricing managed in configuration

☑️ REST APIs, webhooks, SDKs, and batch file integration

☑️ Cloud or on-premise deployment, on SaaS or licensed models

It connects to existing switches and core banking, so you can modernize one layer at a time. Standard deployments take 8 to 12 weeks, depending on scope.

Also Read: Essential Features of an Ideal Merchant Payment Solution

Final Thoughts

Choosing a merchant payment solution provider is an architecture and operating decision, not a pricing exercise. The right platform fits your license, markets, technology stack, and the workflows your teams run after go-live.

The questions that get skipped are usually the ones that cost more later. Reporting that cannot be exported, pricing that needs a release for every tariff, and a roadmap you cannot influence all show up after go-live. Treat must-haves as gates, and treat nice-to-haves as scope you can add once the operating path is proven.

Use the 25 questions as your RFP script, score every vendor on the same weights, and settle data ownership and exit before you sign. A lower first-year fee will not fix a settlement gap later.

Ready to put DigiPay.Guru through these 25 questions with your own demo script?

FAQ's

Ask about business fit, payment APIs, compliance scope, settlement and reconciliation, routing and scale, total cost, SLAs, customization, and exit. Request evidence: documentation, a sandbox, an AOC, and reference calls.

A payment gateway transmits transaction data between merchant and acquirer, mainly for online payments. A merchant acquiring solution covers the full lifecycle: onboarding, pricing, processing, settlement, reconciliation, risk, and disputes.

Compare itemized total cost of ownership, not headline rates. Include setup, modules, transaction fees, support, change requests, and exit over the full contract term.

Payment settlement and reconciliation decide operating costs and merchant trust. Without transaction-level settlement data and automated reconciliation, finance closes breaks manually and headcount grows with volume.

Build only if payments technology is a core differentiator and you have a mature payments team. Most banks launch faster, with lower risk, on a white-label platform integrated with their existing systems.

Watch for no API documentation before signing, certificates without scope, totals-only settlement reports, vague scalability claims, hidden fees, and vendor-controlled exit. Two or more should pause the deal.

author-profile

Rahul Patel

Rahul, CEO of DigiPay.Guru, is a fintech leader with over 17 years of experience in digital payments. His expertise in payment technologies, strategic vision, and innovation has helped DigiPay.Guru deliver cutting-edge fintech solutions, enabling banks, fintechs, and payment providers to accelerate digital transformation.

Get Monthly Fintech Newsletter Insights!

Related Post