Payment Layer Library

Open the Payment Layer, Not Just the Brand

A card network, PayPal, Apple Pay, Wise Card, a prepaid program, a virtual number, bank transfer, and gift-card balance do not do the same job. Use this library to identify the layer: merchant card route, checkout account, wallet handoff, account-to-card product, card program, credential design, bank rail, or closed balance. Then return to the Country Map or Route Map to see whether the live merchant or recipient actually exposes that layer.

Open the Layer

Which Layer Are You Actually Using?

Each guide follows one layer through merchant support, the underlying account or card, authentication, authorization, recurring behavior, holds, currency, payment state, refunds, and recovery. A method guide explains the layer; it does not guarantee the merchant or corridor supports it.

💳

Visa and Mastercard

Card Route Guide: the network carries the transaction, but the merchant must accept the exact card profile and the issuer still decides funds or credit, controls, 3D Secure, country, currency, recurring authorization, holds, and refunds.

🅿️

PayPal

Checkout Layer Guide: the merchant must expose PayPal, the account must be eligible, and the selected balance, card, or bank must fund the payment. Automatic payments, conversion, status, and refunds stay inside this layered route.

📱

Apple Pay

Wallet Layer Guide: Apple Pay changes how an eligible card reaches the merchant. Device, Wallet, merchant integration, issuer, currency, recurring support, authorization, and refund still depend on the underlying card route.

📲

Google Pay

Account Checkout Guide: Google Pay online checkout uses merchant integration, a Google Account or payments profile, and an eligible saved method. The underlying issuer or bank still owns final approval and refund.

🌐

Wise Card

Account-to-Card Guide: Wise Card connects an eligible Wise account and balance to a merchant card route. Country eligibility, verification, card status, balance or conversion, controls, merchant profile, recurring support, and authorization all still matter.

🎟️

Prepaid Cards

Card Program Guide: prepaid describes how funds are supplied, not what the card can do. The exact program controls registration, balance, online or international use, trials, renewals, deposits, holds, and refunds.

🧾

Virtual Cards

Virtual Credential Guide: compare reusable, merchant-locked, category-limited, and single-use numbers by the underlying account, number lifetime, merchant or category lock, recurring and delayed charges, country, currency, holds, and refunds.

🏦

Bank Transfer

Bank Rail Guide: identify the rail before comparing speed. Domestic instant systems, ACH-style payments, SEPA, wires, and SWIFT chains use different recipient details, status, references, timing, fees, cancellation, recall, returns, and reconciliation.

🎁

Gift Cards

Closed Balance Guide: gift-card value stays inside the issuer or platform. Check seller and activation, code status, account or store region, currency, eligible products, subscription and backup-payment rules, remaining balance, refunds, resale risk, and scams.

Layer Map

Same Checkout Goal, Different Payment Layers

Do not rank these as if they were equivalent competitors. First identify the layer, then check whether the live merchant or recipient exposes it. The controlling party, funding source, authentication, authorization, recurring behavior, money trail, payment state, and recovery path change with the layer.

Layer Route Role What Still Decides
Card network route Carries direct card checkout between the merchant/acquirer side and the issuing card product Exact merchant card-profile acceptance, issuing card product, funds or credit, controls, EMV 3-D Secure, billing and country rules, currency, recurring support, holds, authorization, and refund
Checkout account layer Adds a PayPal merchant lane, account state, funding source, automatic-payment agreement, transaction state, conversion, and refund layer Merchant integration, account country and status, funding method, billing agreement, currency, conversion, fees, and protection terms
Wallet / account handoff Changes how an eligible card or saved method reaches the merchant without replacing the funding decision underneath Country or region, device and software, merchant integration, saved card or method, issuer, currency, and underlying authorization
Account-to-card product Connects an eligible Wise account and balance to ordinary merchant card checkout; Wise transfer remains a separate recipient route Country and account eligibility, verification, card availability, balance or conversion, merchant restrictions, controls, recurring support, and authorization
Card program Merchant-supported transactions for an eligible prepaid-card program Card-program rules, activation and registration, billing details, balance, recurring support, country, currency, holds, and merchant policy
Virtual credential design Merchant-supported use of a reusable, merchant-locked, category-limited, or single-use virtual card Virtual-card type, underlying account, number status, merchant or category lock, recurring support, country, currency, holds, and verification
Bank / account rail Verified invoices, bank recipients, billers, business payments, and integrated account-to-account checkout Payment rail, participating institutions, recipient details, reference, timing, fees, cancellation, recall, returns, and merchant reconciliation
Closed-loop balance Matching platform, account or store region, currency, and eligible product Issuer and seller, code status, account or store region, currency, eligible products, subscription and backup-payment rules, balance, refunds, and scam risk

Where the Layer Breaks

Follow the Failed Gate, Not a New Brand

A displayed logo or saved method does not tell you which gate failed. Start with the merchant order and payment state, then separate merchant acceptance, funding or issuer decision, authentication, profile or country, cross-border route, money trail, and product-program capability before opening another route.

Return to the Corridor

The Method Layer Does Not Decide Merchant Availability

After understanding the layer, return to the payer → destination Route Map. The corridor decides whether the live merchant or recipient exposes the layer and whether the exact payer-side product, country, currency, recurring model, authentication, payment state, transfer instructions, and refund path fit.

Layer Guide ≠ Route Verdict

Use the Layer Guide, Then Recheck the Live Route

A method that works for one service can fail for another because the merchant integration, exact product, funding source, card or account country, billing profile, currency, recurring-payment setup, authentication, limits, or transaction type is different.

Confirm the transaction state before retrying. A declined checkout, pending authorization, completed charge, reversal, and refund are different states, and no alternative method guarantees approval.