Payment Processing and Gateways

Quick answer

Payment processing and gateways describe the technical and financial steps that take a customer payment at checkout and turn it into funds deposited in a merchant bank account. This covers the gateway that collects and routes card or wallet data, the processor that authorizes the payment with the card networks and issuing bank, and the settlement steps that move money to the merchant.

Why it matters

How payments are processed affects revenue, conversion, costs, and customer experience. Good payment infrastructure:

• reduces checkout friction and cart abandonment;
• lowers per-transaction costs through routing and pricing;
• reduces fraud and chargebacks that hit profits and operations;
• improves cash flow via faster settlement and predictable reconciliation;
• enables more payment methods to match customer preference, increasing conversion.

Conversely, slow authorization, limited payment options, high decline rates, or opaque fees can directly reduce revenue and increase operational work.

What is payment processing and gateways?

Payment processing is the sequence of technical and financial steps that take payment data from a shopper and conclude with the merchant receiving funds. A payment gateway is the software layer that securely captures card or wallet data from checkout and sends it to a processor. Key pieces include:

• Checkout integration where the customer enters or selects a saved payment method;
• Payment gateway that encrypts and transmits payment data, provides tokenization, and returns authorization responses;
• Payment processor that routes the authorization request through card networks to the issuing bank;
• Acquirer / merchant account or PSP which receives funds and handles settlement to the merchant bank account;
• Card networks and issuing banks that approve or decline the transaction and manage chargebacks.

What it includes: capture of card or wallet data, tokenization, authorization, capture, settlement, reconciliation, and dispute handling. What it excludes: pricing decisions for products, marketing attribution, and non-monetary parts of customer experience like product pages.

A high authorization rate and low decline or fraud rate indicate a healthy payment stack. Repeated declines, long settlement times, or high chargeback rates indicate gaps in routing, fraud tools, or reconciliation.

Formula / measurement

This topic is primarily process and performance measured by several metrics rather than a single formula. Common measurable items include:

• Authorization rate = successful authorizations / authorization attempts. Tracks how often card issuers approve requests.
• Net payment cost per transaction = processing fees + chargebacks + refunds + payment-related operational costs divided by number of transactions. Example calculation is below.
• Settlement lag measured in business days between capture and funds availability.

Example calculation for net payment cost per transaction

1. Monthly revenue 100,000.00
2. Average order value 80.00 so transactions = 100000 / 80 = 1250
3. Assume blended processing fees 2.9% plus 0.30 per transaction. Fees = 100000 x 0.029 + 1250 x 0.30 = 2900 + 375 = 3275.00
4. Chargebacks and refunds = 0.8% of revenue = 800.00 (example estimate)
5. Operational payment costs (staffing, chargeback management) = 300.00
6. Total payment costs = 3275 + 800 + 300 = 4375.00
7. Net payment cost per transaction = 4375 / 1250 = 3.50 per transaction, or 4.375% of revenue

Note: the fee numbers above are illustrative. Use your own processor statements for accurate calculations.

How it works in practice

1. Customer selects a product and pays at checkout

   The merchant collects card details or a wallet token. The business measures conversion rate at checkout and which payment methods customers choose. This matters because more preferred methods typically increase conversion.

2. Gateway encrypts and tokenizes payment data

   The gateway secures the data and returns a token to store for future charges. Businesses track tokenization rates and PCI scope reduction. Tokenization reduces PCI risk and speeds repeat checkouts.

3. Processor routes authorization to card network and issuing bank

   Authorization returns approved, declined, or soft-decline codes. Merchants monitor authorization rate and decline reasons to diagnose issues like incorrect CVV, expired cards, or issuer blocks.

4. Capture and settlement

   Authorized amounts are captured and settled. Businesses measure settlement lag and reconciliation differences. Faster settlement improves cash flow forecasting.

5. Reconciliation and reporting

   Payments are reconciled to orders and accounting. Merchants measure net proceeds after fees and reconcile fees charged by providers.

6. Dispute and chargeback handling

   If a cardholder disputes a charge, the merchant manages evidence submission and monitors win rate and chargeback ratio. High chargeback ratios can lead to penalties or termination.

7. Optimization

   Ongoing steps include adding local payment methods, smart routing, retry logic, and A/B testing checkout flows. Measure the change in authorization, conversion, and net payment cost.

Key components and factors

• Payment method mix: cards, wallets, BNPL, buy now pay later, local alternatives. The mix affects authorization rates and fees.
• Pricing model: interchange plus, flat-rate, tiered. Pricing affects net cost per transaction and scalability as volume grows.
• Authorization and decline reasons: issuer declines, CVV failures, AVS mismatches. Understanding codes guides fixes that recover sales.
• Fraud prevention: risk scoring, 3D Secure, device fingerprinting. Balances preventing fraud and avoiding false declines.
• Checkout friction: number of fields, saved payment options, one-click flows. Directly impacts conversion.
• Settlement time: daily vs multi-day payout schedules affecting cash flow.
• Geography and currency: cross-border fees, local acquiring, currency conversion impacts both fees and conversion.
• Platform and integration: Shopify, custom stack, PSP plugins. Integration affects data quality, tokenization, and reconciliation effort.
• Device and traffic source: mobile users often prefer wallets; paid ads may bring higher-risk traffic affecting fraud rates.

Example scenario

Store: mid-size DTC brand with 100,000 monthly revenue and AOV 80. Current processing via single PSP with default routing.

• Transactions = 100000 / 80 = 1250
• Baseline fees = 2.9% + 0.30 per transaction. Calculated fees = 2900 + 375 = 3275
• Chargebacks/refunds = 0.8% revenue = 800
• Monthly net from operations = revenue - fees - refunds = 100000 - 3275 - 800 = 96, - actually 100000 - 4075 = 95,925

Diagnosis: Authorization rate tracking shows 95% successful authorizations and a 3% soft-decline rate due to issuer routing. Action: implement smart routing and retry logic for soft declines and add Apple Pay and Google Pay to checkout.

• Effect: recover 1.5% of previously declined transactions into successful sales. New successful authorization rate becomes 96.5%.
• Revenue impact: additional successful transactions = 1250 x 0.015 = 18.75 ≈ 19 transactions. Additional revenue = 19 x 80 = 1520.
• Additional fees on recovered revenue = 1520 x 0.029 + 19 x 0.30 = 44.08 + 5.70 = 49.78
• Net gain ≈ 1520 - 49.78 = 1470.22 monthly. ROI: if integration cost was 500 one-time, payback in one month.

Business impact: small percentage improvements in authorization and method availability can translate into material incremental revenue with low implementation cost.

Benchmarks and what is a good metric

There is no single universal benchmark for payment processing because costs and expected authorization rates vary by country, industry, payment method, and customer mix. Factors that change benchmarks include cross-border volume, AOV, product risk profile, and device mix.

• Authorization rate: higher is better. Typical healthy authorization rates vary; compare by card brand and region. A sudden downward trend indicates a problem.
• Chargeback rate: low single-digit percentages are common; high ratios require immediate remediation. Card networks often set thresholds that trigger penalties.
• Net payment cost: varies widely by model and volume. Use your statements to calculate your current blended cost and track reduction over time.

If you need specific comparisons, benchmark against similar stores by geography and AOV using processor reports or industry groups rather than global averages.

How to improve and optimize

Recommendations are prioritized by typical business impact for ecommerce merchants.

1. Enable preferred local and wallet payment methods

   What to change: add Apple Pay, Google Pay, and top local wallets for target markets. Why it works: reduces friction and card entry errors. How: configure in your gateway or Shopify payment settings and test on mobile. Monitor: checkout conversion rate and payment method uptake.

2. Implement smart routing and retry logic for soft declines

   What to change: use a gateway or processor feature that tries alternative routes or retries soft declines. Why: recovers approvals without price changes. How: enable routing rules or integrate a routing provider. Monitor: change in authorization rate and recovered transactions.

3. Reduce friction with hosted fields and tokenization

   What to change: use hosted fields or tokenization to enable autofill and one-click purchase. Why: faster UX and reduced PCI burden. How: integrate gateway SDKs to keep sensitive data out of your servers. Monitor: checkout completion rate and token reuse rate.

4. Segment fees and negotiate pricing

   What to change: review interchange line items and negotiate interchange-plus or volume discounts as you scale. Why: lowers per-transaction cost. How: request detailed statements and discuss tiers with providers. Monitor: blended fee rate and cost per transaction.

5. Use risk management tuned to your business

   What to change: configure risk rules, use 3D Secure selectively, and combine fraud scoring with manual review for high-value orders. Why: reduces chargebacks while minimizing false declines. How: test rules on a subset and measure fraud prevented and sales lost. Monitor: chargeback rate and false-decline rate.

6. Improve reconciliation and reporting

   What to change: ensure orders, settlements, and fee line items reconcile daily. Why: avoids revenue leakage and misreported margins. How: use automated CSV exports or accounting integrations. Monitor: reconciliation exceptions and days to resolve.

Best practices

• Track authorization rate by card brand, country, and device to spot patterns quickly.
• Keep a single source of truth for payment fees and reconcile monthly to prevent hidden costs.
• Offer at least one local preferred payment method per top country to lift conversion.
• Use tokenization to enable fast repeat purchases and reduce PCI scope.
• Start with conservative fraud rules and iterate to avoid unnecessary false declines.
• Measure decline reasons rather than raw decline rate to target fixes.
• Test minor checkout UX changes in A/B tests to quantify impact on payment conversion.
• Monitor settlement lag and build cash flow buffers for seasonal spikes.

Common mistakes to avoid

• Ignoring decline reason codes

  Why it happens: teams track only overall decline rate. Harmful because you miss actionable fixes like address or CVV errors. Correct approach: log and segment authorization responses and act on high-frequency codes.

• Assuming one-size-fits-all pricing

  Why it happens: default PSP pricing seems simple. Harmful because you may pay more than necessary as volume grows. Correct approach: request interchange detail and negotiate volume pricing.

• Over-relying on strict fraud rules

  Why it happens: fear of chargebacks. Harmful because false declines reduce conversion and customer trust. Correct approach: use risk scoring and progressive review for high-risk orders.

• Poor reconciliation practices

  Why it happens: manual processes and separate systems. Harmful because you may miss misapplied fees or refund mismatches. Correct approach: automate reconciliation and match settlements to orders daily.

• Not testing mobile payment flows

  Why it happens: desktop-first testing. Harmful because mobile users often convert using wallets. Correct approach: test Apple Pay and Google Pay flows on real devices and track differences.

Payment Processing and Gateways vs related concepts

Payment gateway vs Payment processor

• Payment gateway: software that captures and securely transmits payment data, often provides tokenization and frontend integration.
• Payment processor: the backend service that routes the authorization through card networks to issuing banks and handles settlement.
• Key difference: gateway handles capture and security; processor handles routing and settlement. Some providers combine both roles.

Payment service provider (PSP) vs Merchant account

• PSP: bundled service that includes gateway, processing, and sometimes a pooled merchant account for easier onboarding.
• Merchant account: a specific bank account that receives card funds, often required when using direct processors; can be provided by a PSP or an acquirer.
• Key difference: PSPs simplify setup and bundle services; dedicated merchant accounts can give more control and potentially lower fees for high-volume merchants.

Authorization vs Capture

• Authorization: an approval from the issuing bank to hold funds for a transaction.
• Capture: the final step that transfers the money after goods ship or service is provided.
• Key difference: authorization reserves funds; capture moves them into settlement.

When should you track payment processing and gateways?

• Who: founders, finance leads, ecommerce ops, and growth teams should monitor payments.
• Stage: start tracking from launch but expand depth as volume grows; advanced routing and negotiation typically matter after consistent monthly volume.
• Frequency: daily monitoring for authorizations and settlement exceptions; weekly for reconciliation; monthly for pricing and fee analysis.
• Segments: break down by payment method, country, device, customer cohort, and traffic source to identify patterns.
• Companion metrics: conversion rate, average order value, authorization rate, chargeback rate, refund rate, net payment cost, settlement lag.

Related ecommerce metrics

• Authorization rate - directly measures how often payment attempts are approved.
• Chargeback rate - indicates disputes that can lead to fines or termination by processors.
• Refund rate - affects net revenue and may correlate with fraud or product issues.
• Net payment cost - the blended fee and operational cost per transaction; key to margin analysis.
• Checkout conversion rate - influenced by payment options and checkout friction.
• Settlement lag - impacts cash flow forecasting and working capital needs.

FAQs

1. What is the difference between a payment gateway and a PSP?

   A gateway is the technology that captures and secures payment data. A PSP bundles gateway, processing, and often a merchant account into one service for simpler setup. PSPs are convenient for smaller merchants; larger merchants may prefer separate merchant accounts for lower fees.

2. How do I measure if my payments setup is cost effective?

   Calculate your net payment cost per transaction including fees, chargebacks, refunds, and operational costs, then compare that number month over month and against peer merchants in similar geographies and AOVs.

3. Why are transactions being declined even when cards are valid?

   Declines can be due to issuer fraud rules, routing issues, AVS or CVV mismatches, or insufficient funds. Log decline reason codes and work with your gateway or processor to enable smarter routing or retries.

4. Should I accept alternative payments like wallets and BNPL?

   Yes when aligned with your customer base. Wallets often increase mobile conversion, while BNPL can raise average order values. Track their adoption and net economics, since fees and return behavior differ.

5. How often should I negotiate fees with my provider?

   Review pricing when you hit new volume thresholds, during annual reviews, or when you add significant cross-border volume. Negotiate with data: present your interchange blends and volume trends.

6. What is a good authorization rate?

   There is no single good number. Focus on trends and segmentation. A sudden drop or higher declines for a specific card brand, country, or device is actionable regardless of overall percentage.

7. How can I reduce chargebacks without losing sales?

   Improve product descriptions and shipping transparency, use clear descriptors on billing statements, deploy targeted fraud rules, and maintain quick dispute response processes. Balance prevention with minimizing false declines.

8. What tracking limitations should I be aware of?

   Payment events can be processed outside standard analytics flows, so ensure server-side tracking or payment provider webhooks are captured for accurate attribution and reconciliation. Watch out for blocked third-party cookies affecting client-side attribution.