Payment Service Provider (PSP)

What Is a Payment Service Provider?

A payment service provider (PSP) is a third-party company that enables businesses to accept electronic payments: credit cards, debit cards, digital wallets, bank transfers, and increasingly, cryptocurrency. The PSP acts as an intermediary between the consumer making a payment and the merchant receiving it, handling the technical, financial, and regulatory complexity so the merchant does not have to.

Before PSPs existed, merchants needed to establish their own merchant accounts with acquiring banks, integrate separately with card networks, and build or buy fraud detection systems. This was expensive, time-consuming, and out of reach for smaller businesses. PSPs changed this by aggregating those relationships and offering them through a single API or dashboard. Companies like Stripe, Adyen, PayPal, and Square are well-known examples.

The term PSP is sometimes used interchangeably with "payment processor" or "payment gateway," but these are actually distinct layers in the payments stack. A PSP typically encompasses both functions plus additional services: a true all-in-one solution for accepting and managing payments.

How It Works

When a customer pays for something online or in-store, the PSP orchestrates a multi-step process that happens in seconds:

1. The customer enters payment details at checkout (card number, wallet credential, or bank login). The PSP captures and encrypts this data.
2. The PSP routes the encrypted transaction to the relevant acquirer, which forwards it to the card network (Visa, Mastercard) or bank network.
3. The issuing bank checks the customer's account for sufficient funds and fraud signals, then approves or declines the transaction.
4. The approval response flows back through the network to the PSP, which notifies the merchant in real time.
5. During settlement (typically 1 to 3 business days later), the PSP coordinates the actual fund transfer from the customer's bank to the merchant's bank account, minus any applicable fees.

What PSPs Provide

A full-stack PSP bundles several capabilities that would otherwise require separate vendors:

• Checkout and gateway: hosted payment pages, embeddable widgets, and APIs for capturing payment credentials securely
• Processing and acquiring: transaction routing, authorization, and in some cases direct acquiring relationships with card networks
• Fraud prevention: machine learning models, rule engines, and tools like 3D Secure to reduce chargebacks
• Settlement and reconciliation: automated fund disbursement and reporting so merchants can match payments to orders
• Multi-currency and multi-method support: acceptance of cards, wallets, bank transfers, and local payment methods across geographies
• Compliance: PCI DSS scope reduction, Strong Customer Authentication (SCA) under PSD2, and regulatory reporting

PSP vs. Payment Gateway vs. Payment Processor

These three terms describe different layers of the payments stack, though they are often confused:

Modern full-stack PSPs like Adyen have taken this integration further by building their entire payments infrastructure in-house rather than assembling third-party components. This single-stack approach allows them to offer smart transaction routing, unified reporting, and tighter fraud controls.

PSP Business Models

PSPs typically operate under one of two models:

• Aggregator model: the PSP onboards merchants under its own master merchant account. Merchants do not need their own acquiring relationship. This is the model used by Stripe and PayPal, and it allows very fast onboarding. The tradeoff is less control over transaction limits and fund-holding policies.
• Dedicated merchant account model: the PSP provides each merchant with its own merchant ID and direct acquirer relationship. Adyen uses this approach. It offers more flexibility and higher transaction limits but requires more onboarding effort.

Some providers also operate as payment facilitators (PayFacs), a regulated category where the PSP is the merchant of record and sub-merchants operate under its umbrella.

Fee Structures

PSP fees are typically structured as a percentage of each transaction plus a fixed per-transaction fee. For card payments, this often falls in the range of 1.5% to 3.5% per transaction, which includes the interchange fee paid to the issuing bank, the scheme fee paid to the card network, and the PSP's own margin. Some PSPs offer volume-based pricing for larger merchants.

Regulation and Licensing

In the European Union, PSPs are regulated under the Payment Services Directive (PSD2), which requires providers to obtain a payment institution license. PSD2 mandates Strong Customer Authentication (SCA) using multi-factor verification for electronic payments and establishes security standards for APIs used by third-party providers.

In the United States, PSPs may need state-level money transmitter licenses depending on their business model. They must also comply with federal regulations around anti-money laundering (AML) and consumer protection. A proposed third directive (PSD3) is expected to further expand open banking requirements in Europe.

Crypto Payment Service Providers

A newer category of PSP has emerged to help merchants accept cryptocurrency payments. These crypto PSPs replicate the traditional PSP model: they provide checkout widgets, handle transaction processing, and offer settlement in either crypto or fiat currency.

Leading crypto PSPs include:

• BitPay: one of the earliest Bitcoin payment processors, now supporting multiple cryptocurrencies with automatic fiat conversion. Used by companies like Microsoft and AMC.
• OpenNode: a Bitcoin-focused PSP that leverages the Lightning Network for fast, low-fee transactions. Merchants can choose to hold Bitcoin or convert to fiat automatically.
• CoinGate: a multi-cryptocurrency payment platform supporting over 70 digital assets with e-commerce plugins for major platforms.

According to industry data, stablecoin transaction volume processed by businesses exceeded $1 trillion in 2025, driven by the advantages of blockchain-based settlement: lower fees (often under 1% compared to 2 to 3% for card payments), near-instant settlement instead of the traditional T+1 or T+2 cycle, and no chargebacks.

How Crypto PSPs Differ

While traditional PSPs route transactions through card networks and banking rails, crypto PSPs settle directly on blockchain networks. The fundamental difference is in the settlement layer: instead of relying on correspondent banking relationships, crypto PSPs use Bitcoin's base layer, the Lightning Network, or stablecoin transfers on various blockchains. This eliminates intermediaries from the settlement process and enables real-time finality.

For merchants interested in accepting Bitcoin payments with a familiar integration experience, our guide to Bitcoin merchant payments covers the technical and business considerations in detail.

Why It Matters

PSPs are the backbone of digital commerce. Without them, every merchant would need to build and maintain direct relationships with acquiring banks, card networks, and fraud vendors: a cost and complexity barrier that would shut out most small and mid-sized businesses from accepting electronic payments.

The PSP market is projected to grow from approximately $87 billion in 2025 to over $140 billion by 2034, driven by the expansion of e-commerce, real-time payment rails, and cryptocurrency acceptance. The market is also consolidating: PayPal and Stripe together influence the majority of payment management adoption, while full-stack acquirer-PSPs like Adyen capture an increasing share of enterprise volume.

For the Bitcoin ecosystem, the emergence of crypto PSPs represents a bridge between blockchain-native payments and the merchant infrastructure that already exists. Solutions built on layer-2 protocols like Spark and the Lightning Network can offer PSP-grade merchant tooling with the settlement advantages of Bitcoin: instant finality, low fees, and global reach without correspondent banking overhead.

Risks and Considerations

• Vendor lock-in: migrating between PSPs can be complex, involving changes to checkout flows, stored payment credentials (card vaulting), and reporting integrations. Multi-PSP strategies and payment orchestration layers help mitigate this but add architectural complexity.
• Fund-holding risk: aggregator-model PSPs hold merchant funds before disbursement. If the PSP freezes a merchant account (often triggered by fraud flags or policy violations), the merchant may lose access to revenue temporarily or permanently.
• Fee opacity: PSP pricing can be difficult to compare because total cost includes interchange, scheme fees, and the PSP's margin. Blended pricing simplifies billing but can obscure the true cost of different payment methods.
• Regulatory fragmentation: PSPs operating across jurisdictions must navigate different licensing regimes (PSD2 in Europe, state-level money transmitter licenses in the US, and emerging crypto-specific frameworks like MiCA). This creates compliance overhead and can limit which payment methods are available in each market.
• Crypto PSP risks: crypto-specific PSPs face additional challenges around price volatility (unless using stablecoins), regulatory uncertainty, and lower consumer familiarity. Merchants must decide whether to hold crypto or convert to fiat, each carrying its own risk profile.

This glossary entry is for informational purposes only and does not constitute financial or investment advice. Always do your own research before using any protocol or technology.