The Payment Stack Decision
For merchants, the payment technology stack decision affects operational costs, conversion rates, international reach, and the customer experience at the most critical moment of the commerce journey. Getting this decision right has meaningful business impact. Getting it wrong means either overpaying for capabilities you do not use or missing capabilities that cost you sales.
Payment Processor vs. Payment Gateway vs. Payment Orchestrator
These terms are often used interchangeably but represent distinct roles. Payment processors handle the actual movement of money between banks and card networks. Payment gateways manage the technical communication between merchant and processor, handling card data capture and transmission. Payment orchestrators provide an abstraction layer that connects to multiple processors and gateways, enabling intelligent routing based on cost, success rate, and geography.
Small businesses typically need a processor that functions as both gateway and processor (Stripe, Square, PayPal). Larger businesses with international operations benefit from orchestration to optimize between multiple processors and minimize interchange and FX costs.
Total Cost of Ownership
Sticker price comparison of payment processing rates is insufficient for choosing between payment solutions. Total cost includes: transaction fees (flat fee plus percentage); interchange fees (passed through by some processors, bundled by others); chargeback fees (highly variable and significant for high-dispute businesses); FX markup (often the largest hidden cost for international merchants); minimum fees and monthly charges; and integration and ongoing development costs.
Conversion Rate Impact
Payment technology choices directly affect authorization rates and checkout conversion. Poorly optimized checkout flows, excessive authentication friction, and geographic payment method gaps all reduce conversion. The best payment stacks combine conversion-optimized checkout UI, smart retry logic for failed transactions, local payment method support in each market, and 3DS2 implementation that applies authentication friction only to genuinely risky transactions.