Glossary Hub
Payment Glossary for ISVs
Plain-language definitions written for software teams — not merchants. Every term gets a definition, how it works mechanically, and why it matters for your product, pricing, or integration decision.
Definition
One paragraph, no jargon-by-jargon loops. If a term has multiple definitions in the market, we state that and pick the ISV-relevant one.
How it works
The mechanical picture — money flow, counterparties, contracts, or code path — so the definition connects to something your team can reason about.
Why ISVs care
The decision the term actually gates: margin, liability, time-to-launch, or vendor choice. This is the section generic dictionaries skip.
Start here — the anchor terms
Four entry points most ISV payment conversations branch from.
Most-searched
Payment Facilitator
The anchor definition every other PayFac term branches from.
Read definition →Core ISV concept
What Are Embedded Payments
The revenue model — not the feature — that turns software into a payments business.
Read definition →Common confusion
PayFac vs ISO
Different models, different margins, different liability. Pick wrong and you rebuild.
Read definition →Technical baseline
What Is a Payment Gateway
The piece of infrastructure every integration talks through, regardless of provider.
Read definition →Filter by category
Click a category to narrow the list below.
All terms
19 of 19
Embedded Payments vs Integrated Payments
Embedded & integrationEmbedded payments means payment processing is built natively into the software platform — the ISV owns the payment experience, onboards merchants, and earns per-transaction revenue. Integrated payments is broader, describing any software connected to payment processing, regardless of whether the ISV monetizes transactions or controls the merchant experience.
Read definition →PayFac Meaning
PayFac & ISO modelsPayFac is an abbreviation for Payment Facilitator — an entity registered with card networks (Visa, Mastercard) that acts as a master merchant, enabling sub-merchants to accept card payments under the PayFac's merchant identification number (MID) without each sub-merchant needing their own merchant account.
Read definition →PayFac vs ISO
PayFac & ISO modelsA PayFac (payment facilitator) owns the merchant relationship and onboards sub-merchants under its master MID, while an ISO (independent sales organization) acts as a sales agent referring merchants to a processor. PayFacs earn more per transaction but carry compliance and fraud liability; ISOs earn residual income with minimal operational overhead.
Read definition →PayFac vs Merchant of Record
Merchant of RecordA PayFac facilitates payments for other businesses (sub-merchants accepting payments from their customers), while a Merchant of Record (MoR) is the legal seller — it sells your product on your behalf, handling the transaction, tax collection, and compliance as the entity on the customer's bank statement. They solve different problems for software companies.
Read definition →Payment Facilitator
PayFac & ISO modelsA payment facilitator (PayFac) is a master merchant that enables sub-merchants to accept payments without each obtaining their own merchant account.
Read definition →Payment Facilitator vs Payment Processor
Gateway & infrastructureA payment facilitator (PayFac) is a master merchant that onboards sub-merchants under its own MID, handling underwriting, compliance, and settlement. A payment processor routes transactions between merchants, card networks, and issuing banks. PayFacs use processors — they operate at different layers of the payment stack.
Read definition →Payment Gateway vs Payment Processor
Gateway & infrastructureA payment gateway is the software layer that securely captures, encrypts, and transmits payment data from the point of sale to the processor, while a payment processor routes the transaction through card networks and facilitates the actual movement of funds between issuing and acquiring banks.
Read definition →What Are Embedded Payments
Embedded & integrationEmbedded payments is the integration of payment acceptance capabilities directly within a software application's native user experience, allowing end users to pay without leaving the platform or being redirected to a third-party checkout.
Read definition →What Is a Cash Discount Program
Surcharging & feesA cash discount program is a pricing strategy where merchants set their listed prices to include card processing costs, then offer a discount to customers who pay with cash or debit. The discount effectively removes the processing fee from cash transactions, making the listed price the 'card price' and the discounted price the 'cash price.'
Read definition →What Is a Merchant of Record
Merchant of RecordA Merchant of Record (MoR) is the entity that is legally authorized to process a customer's payment and appears on the customer's bank or credit card statement. The MoR assumes liability for the transaction, including chargebacks, refunds, tax collection, and regulatory compliance.
Read definition →What Is a PayFac
PayFac & ISO modelsA PayFac (payment facilitator) is a master merchant that enables sub-merchants to accept card payments under its own merchant ID, handling underwriting, onboarding, compliance, and settlement on behalf of its sub-merchants without each needing their own merchant account.
Read definition →What Is a Payment Aggregator
PayFac & ISO modelsA payment aggregator is a service provider that processes transactions for multiple merchants under a single master merchant account, rather than requiring each merchant to establish their own merchant account with an acquiring bank. Payment aggregators bundle (aggregate) many merchants' transactions together.
Read definition →What Is a Payment Gateway
Gateway & infrastructureA payment gateway is a technology service that authorizes and encrypts payment transactions between a merchant's application and the acquiring bank's payment processor, acting as the secure intermediary that transmits cardholder data without exposing it to the merchant's systems.
Read definition →What Is an ISV in Payments
Embedded & integrationAn ISV (Independent Software Vendor) in payments is a software company that builds payment acceptance into its product so merchants can take card, ACH, and digital payments inside the application they already use to run the business — instead of bouncing out to a separate terminal or gateway.
Read definition →What Is Dual Pricing
Surcharging & feesDual pricing is a payment acceptance strategy where merchants display two prices for every item or service — a lower cash price and a higher card price — passing credit card processing costs directly to customers who choose to pay with a card.
Read definition →What Is Embedded Payments
Embedded & integrationEmbedded payments is the integration of payment processing directly into a software platform so that merchants can accept, manage, and reconcile payments without leaving the application. Rather than using separate payment hardware or third-party payment portals, the payment experience is built into the software itself.
Read definition →What Is PayFac as a Service
PayFac & ISO modelsPayFac-as-a-Service (PFaaS) is a model where a third-party provider gives ISVs the capabilities of a payment facilitator — merchant onboarding, underwriting, settlement splitting, and compliance — without requiring the ISV to register as a PayFac with card networks or maintain a sponsoring bank relationship.
Read definition →What Is Payment Reconciliation
Gateway & infrastructurePayment reconciliation is the process of matching and verifying payment transaction records across multiple systems — the application database, the payment processor's reports, and the merchant's bank account — to ensure that all funds are accurately accounted for and discrepancies are identified.
Read definition →What Is Surcharging
Surcharging & feesSurcharging is the practice of adding a fee to a transaction when a customer pays with a credit card, passing some or all of the card processing cost to the cardholder. The surcharge is disclosed at the point of sale and appears as a separate line item on the receipt.
Read definition →No terms match your filter.
Frequently asked questions
How is this glossary different from a generic payments dictionary?
Every entry is written for ISVs and software companies, not merchants or consumers. Each term gets three sections: a plain-language definition, how it works mechanically, and why an ISV's product or engineering team should care. A generic dictionary explains what a PayFac is; this glossary explains the margin and compliance trade-off between registering as one vs. using PayFac-as-a-Service.
Where do the terms come from?
The list is built from terms that recur in ISV payment evaluations — vendor contracts, RFPs, procurement reviews, and the questions engineering teams ask during integration. We add new terms when a phrase shows up repeatedly across provider docs, regulatory updates, or customer conversations and isn't already defined clearly somewhere authoritative.
Which terms matter most for an ISV evaluating payment platforms?
Start with Payment Facilitator, PayFac-as-a-Service, Embedded Payments, and Payment Gateway — those four anchor every other decision. Then add Merchant of Record if you sell your own SaaS globally, and Surcharging / Cash Discount if any of your merchants operate in low-margin verticals. The featured cards above cover the most-searched entry points.
How often is the glossary updated?
Reviewed quarterly, plus ad-hoc updates whenever card-network rules, PCI scope, or key provider terminology changes. The 'why ISVs care' section tends to change more often than the definitions themselves — pricing economics and compliance expectations shift faster than vocabulary does.
Can I link to a specific term from my own documentation?
Yes. Every term has a stable URL at /glossary/[slug]/ and is safe to link externally. Each page carries DefinedTerm schema so search engines and LLMs can surface the definition in answer boxes. If you maintain internal ISV runbooks, deep-linking to these entries is a low-maintenance way to give your team a shared vocabulary.
What if a term I need isn't here?
Use the contact form — we add new terms regularly based on what ISVs are actually running into. The turnaround for a new glossary entry is usually 3–5 business days when the term has enough ambiguity in the market to justify a dedicated page.
Explore more
5 destinations
Hub
Comparisons
Side-by-side scoring across 12 ISV criteria.
Hub
Pricing
Fee structures, hidden costs, effective rates.
Hub
Reviews
Deep-dive verdicts on individual platforms.
Hub
Solutions
Pick the integration model that fits your volume.
Tool
Revenue Calculator
Model payment revenue at your volume.
Missing a term that's blocking your team?
Request a new glossary entry and we'll publish an ISV-framed definition — definition, mechanics, and decision impact — within 3–5 business days.
Request a Term