This site demonstrates one possible use of this domain. For acquisition, partnership, or investment inquiries, please use our contact link.
Merchant · Topic Cluster

Merchant Systems

Acquiring, gateway, vault, and the modern merchant stack.

Overview

The merchant payment stack spans acquiring, gateway, vault, fraud, dispute, and reconciliation. The strategic question for any merchant above a certain GMV is no longer 'which processor' but 'how do I orchestrate across multiple processors' - to optimize approval rates, manage cost, and reduce concentration risk.

Payment orchestration platforms have emerged as a category dedicated to that orchestration, sitting between the merchant and a portfolio of underlying providers.

Key concepts

Acquiring

The merchant's bank relationship that allows it to accept card payments.

Gateway and vault

The technical layer that captures, tokenizes, and routes card data.

Payment orchestration

A platform layer that routes transactions across multiple PSPs to optimize approval, cost, and resilience.

Reconciliation

Matching transaction events to settlements to bank-account credits - a non-trivial accounting problem at scale.

Sub-topics in this cluster

  • Acquiring & PSPs

    How merchants accept payments.

  • Gateway & vault

    The technical capture layer.

  • Orchestration

    Routing across multiple PSPs.

  • Reconciliation

    Matching events to settlements.

Frequently asked

What is payment orchestration?+

A platform layer that lets a merchant route transactions across multiple PSPs based on approval rate, cost, and resilience criteria.

Do I need multiple processors?+

Above a certain GMV - typically nine figures - most merchants benefit from multiple processors for approval optimization and resilience.

Sources & References

External references are cited for context and discovery. CashlessTechnology.com is not affiliated with the listed organizations unless explicitly stated.

Continue reading

Related across the knowledge graph

Cross-collection links surfaced by semantic relevance.