What is the difference between an ISO, an FSP, and a sponsor bank?
A retail ISO owns the merchant relationship — sales, support, and commercial terms. An FSP (financial service provider, also called a wholesale ISO) underwrites and sponsors retail ISOs beneath it. A sponsor bank holds ultimate program approval, network sponsorship, and custody of settlement funds, typically delegating day-to-day underwriting to the FSP. See our full explainers on sponsor banks vs. acquiring banks and what an FSP actually is for more detail.
Does a sponsor bank perform merchant underwriting itself?
Generally, no. A sponsor bank holds program approval and ultimate regulatory responsibility, but the actual underwriting work is typically performed by the FSP or a processing acquirer operating within the program the sponsor bank has approved.
What's the difference between a PayFac and an ISO partnership?
A PayFac aggregates many merchants under one master merchant account, trading faster onboarding for shared exposure to the aggregate's overall risk profile. An ISO partnership individually underwrites and approves each merchant through a retail ISO, FSP, and sponsor bank structure, trading onboarding speed for account stability. Neither is inherently better — see our full comparison for how to choose.
How are ISO residuals actually calculated?
Residual revenue is the spread between what a merchant is charged for processing and the true cost of that processing (interchange, network fees, processor cost), split among whichever parties — agent, sub-ISO, retail ISO, ISV partner — have a commercial stake in that merchant. Disputes are common mainly because the underlying transaction data often isn't shared consistently across parties. Our residuals explainer covers this in depth.
What does "AI-assisted underwriting" actually mean?
In well-designed implementations, it means AI analyzes and organizes an application — cross-referencing identity and business data, flagging inconsistencies — while a human underwriter retains the actual approval or decline decision. It should not mean the system makes final underwriting decisions autonomously. See our deeper look at AI in underwriting.
What is BIN sponsorship?
BIN sponsorship is a sponsor bank extending its card network membership and program authority to a partner (typically an FSP or fintech), so that partner can operate an acquiring program without its own direct network membership. The sponsor bank retains program approval, regulatory accountability, and custody of settlement funds throughout. Full explanation in our BIN sponsorship guide.
Does tokenization make a business "PCI compliant"?
No — and any claim that it does should be treated skeptically. Tokenization can meaningfully reduce the number of a business's systems that fall under PCI DSS scope, but PCI compliance still depends on that business's own environment, integrations, and formal assessment. See our tokenization explainer for the precise distinction.
Why does portfolio reconciliation get harder as an ISO scales?
Merchant count, processor count, and commercial complexity (agents, sub-ISOs, ISV partners) all compound at once past a certain scale, while the informal, spreadsheet-based processes that worked at small scale don't scale linearly with them. The fix is a shared transaction ledger, not just additional headcount — more in our reconciliation breakdown piece.
What's the actual difference between clearing and settlement?
Clearing finalizes transaction details between the acquiring and issuing sides of a card transaction; settlement is the actual movement of funds, which passes through the sponsor bank's custody before reaching the merchant. Authorization, clearing, and settlement are three distinct steps, not one event — see our clearing and settlement explainer.
How many card processors does a payments business actually need?
The common, well-reasoned pattern is two — a primary and a secondary serving as automatic failover — plus separate provider types (wallet processors, bank rails) for capabilities the primary processors don't cover. More processors than that adds relationship overhead without proportional benefit. See our pieces on multi-processor architecture and payment failover.
Should a payments organization build its own infrastructure or buy it?
The more useful question isn't whether an organization could build it, but where its engineering capacity creates the most competitive advantage — infrastructure that every competitor also needs is generally a stronger buy candidate than whatever actually differentiates the business. Full framework in our build vs. buy piece.
What are VAMP and ECM?
VAMP (Visa's Acquirer Monitoring Program) and ECM (Mastercard's Excessive Chargeback Merchant program) are card network programs that monitor chargeback and fraud ratios, with escalating consequences for merchants and portfolios that exceed defined thresholds. American Express and Discover maintain similar programs. See our card brand compliance explainer for what ISOs and FSPs need to monitor.
Where does NGnair fit into all of this?
NGnair provides programmable infrastructure connecting sponsor banks, ISOs, processors, and merchant channels into one operating model — it does not replace any of these regulated parties, hold merchant funds, or act as a PayFac. See why NGnair exists and who it serves for the full picture.
