Alternative and Local Payment Methods extend checkout beyond cards. Method intros and choose APM use the same labels. Category and Subtype classify the method. Payment flow shows where checkout completes. Billing logics show who initiates later charges for recurring and automatic debit payments.
Cash-based and buy now, pay later methods have a category without a subtype. Methods that support both direct and redirect checkout are marked as Direct / Redirect in choose APM.
Alternative and local payment methods fall into six categories.
Payments made directly from one bank or payment account to another. Includes Real-time payments, Bank redirects, Open Banking, and Direct debits.
Store money or payment credentials for faster payments on mobile. Includes stored value, staged, and pass through wallets.
Start online, complete with physical cash at a partner location or ATM. Includes vouchers paid in advance and methods paid after purchase.
Short-term and mostly interest-free deferred payments that let shoppers pay over time. Pay in 4 is four installments. Pay in 30 is one payment due in 30 days.
Pay using cryptocurrencies or stablecoins across borders with lower fees and more privacy.
Charge purchases to a mobile phone bill or prepaid balance. Popular for digital goods in low-card or cash-first markets.
| A2A subtype | Key differentiator | UX | Examples |
|---|---|---|---|
| Real-time payments | Instant, irrevocable, 24/7 | QR codes, OTPs, payment identifiers | Pix, BLIK, UPI Collect |
| Bank redirects | Customer redirected to online banking to authorize | Web or mobile redirect and bank list selection | Przelewy24, UPI Intent, iDEAL |
| Open Banking | Uses APIs through PISP providers such as Tink, VOLT, Plaid, and TrueLayer | Redirect or embedded. SCA required. | Pay by Bank |
| Direct debits | Merchant pulls funds after mandate | Mandate authorization. Delayed confirmation. | Blik Recurring |
| Digital wallets subtype | Key differentiator | UX | Examples |
|---|---|---|---|
| Stored value | The customer spends from a wallet balance funded in advance | The customer confirms in a standalone wallet app | GCash, Alipay, WeChat Pay |
| Staged | Wallet funds or linked credentials in two stages | Login and approve in the wallet environment | PayPal, Mercado Pago, Klarna, Cash App Pay |
| Pass-through | Tokenized credentials pass through without holding funds | Confirmation starts on mobile. No wallet balance is required. | MB WAY, MobilePay |
Payment flow describes where the customer completes checkout. Method pages and choose APM use Direct and Redirect.
The customer completes the payment without leaving the merchant website or app. Confirmation can still use QR codes, push notifications, or OTPs in place.
The customer is redirected to a third party site or app to authenticate and pay, then returns to the merchant after completion.
These methods support different billing logics depending on who initiates the charge and whether the customer is present. Method intros list which logics Solidgate supports for each method. Billing logic labels can differ from future_usage.payment_type. Map the two in init APM.
Billing logic describes whether later charges are initiated by the customer or the merchant. A method can use a redirect checkout for the first payment and still support recurring or unscheduled charges initiated by the merchant after mandate setup. unscheduled is a superset of Unscheduled, Recurring, and 1-click when the provider does not restrict token use.
| Flow | Initiated by | Customer present | Description | Example |
|---|---|---|---|---|
| One-time | Customer | Yes | A single payment initiated by the customer. The customer confirms through redirect, QR code, push notification, or a similar step. | One-off purchase at checkout |
| 1-click | Customer | Yes | A payment initiated by the customer that reuses stored credentials. The customer does not reenter payment details or go through a redirect. The customer confirms with a single action based on a prior authorization. | Saved wallet, no extra authentication |
| Recurring | Merchant | No | A merchant-initiated payment on a fixed schedule. Requires a prior mandate, consent or token setup by the customer. | Subscription on a fixed schedule |
| Unscheduled | Merchant | No | A merchant-initiated payment with no fixed schedule or amount. Requires a prior mandate, consent or token setup. Common for event-triggered or usage-based charges. | Post-ride or pay-as-you-go charge |
Review track APM for lifecycle and error code guidance, then open choose APM to filter alternative and local payment methods by region, category, flow, billing logics, and capabilities.