Alternative Payment Methods: A Guide for Global Businesses

Alternative payment methods are payment options outside the traditional card payment flow. They can include digital wallets, Pay by Bank and other account-to-account payments, bank transfers, buy now pay later, local card schemes, QR payments, vouchers, and other market-specific ways customers prefer to pay. For businesses selling across markets, APMs shape checkout trust, payment completion, operational complexity, and the way finance teams handle settlement, refunds, reconciliation, and payment risk.

For a merchant, the practical question is simple: which payment methods should appear at checkout, in which markets, for which customers, and with what operational tradeoffs?

Use this guide to build that decision. When you are ready to validate availability for your own checkout, review HaiPay Checkout or talk to the payments team to confirm availability, settlement, refunds, and implementation requirements before launch.

What are alternative payment methods?

Alternative payment methods, often shortened to APMs, are ways to pay that are not the standard credit-card or debit-card payment flow. The exact boundary varies by provider and market, but most APM guides include wallets, bank-based payments, direct debit, buy now pay later, cash or voucher flows, QR payments, local card schemes, and other local payment options. Stripe and Adyen both use this kind of broad category framing in their APM explainers.

That definition matters because "alternative" does not mean niche. In many markets, a local wallet, bank transfer flow, account-to-account option, or domestic payment scheme may feel more familiar to customers than an international card checkout. The right payment mix is therefore a market decision, not just a feature list.

For B2B and cross-border businesses, APM selection usually comes down to five questions:

1. Does the customer already trust this method?
2. Does the method fit the transaction size and purchase context?
3. What does the payment flow ask the customer to do?
4. How do settlement, refunds, failures, and disputes work?
5. Can the business support the method operationally after launch?

Why alternative payment methods matter

Payment methods influence whether a customer recognizes the checkout, completes authentication, understands what will happen next, and feels comfortable paying. A card-only checkout can work well in some segments, but it can also create friction when customers expect a local wallet, bank transfer, QR code, or domestic payment network.

APMs matter most when a business is expanding across countries, selling to customers with strong local payment habits, supporting recurring or invoice-like flows, or trying to reduce friction in high-intent checkout sessions. They also matter when finance, operations, and support teams need clearer answers about reconciliation, refund timing, and failed-payment recovery.

The strongest APM strategy is not "add every method." It is "add the methods that match the buyer, market, and operating model." That is the difference between a useful checkout and a crowded one.

Main types of alternative payment methods

The table below groups common APM categories by the job they do at checkout. Availability, settlement timing, refund rules, and compliance requirements vary by country, provider, merchant category, and payment method, so every row should be confirmed before implementation.

Alternative payment methods vs card payments

Cards are still a major part of online payment acceptance, but APMs differ from cards in how the customer authorizes payment, how the payment is confirmed, and how post-payment operations work.

The goal is not to replace cards everywhere. The goal is to offer the methods that remove friction for the customers and markets you actually serve.

Pay by Bank and account-to-account payments

Pay by Bank is a bank-funded checkout flow. The customer pays from a bank account rather than typing card details. Account-to-account, or A2A, is the broader category of direct movement from one bank account to another. The Federal Reserve Pay-by-Bank note describes Pay-by-Bank as a bank-based payment model in which a transaction originates from the customer's bank account and is routed over bank payment rails to the merchant's bank account.

In some markets, Pay by Bank is closely connected to open banking. Open Banking Limited's Pay by Bank guide describes Pay by Bank as a way for customers to pay directly from their bank account, usually by choosing their bank, authenticating, and confirming the payment. It also notes that protections can differ from card payments, so merchants need to understand the specific rule set behind the flow.

For merchants, Pay by Bank can be attractive when customers trust their banking app, when card entry adds friction, or when the business wants a bank-account-funded payment option. But implementation should not start with a generic promise. Start with operational questions:

• Which markets and banks are covered?
• Is the customer redirected, embedded, or asked to scan a code?
• Is confirmation immediate or delayed?
• How are refunds initiated?
• What happens when authentication succeeds but payment confirmation is delayed?
• What support message should a customer see if the payment is pending?

Local payment examples to evaluate

The best APM set depends on where your customers are. These examples are not a recommendation to enable every method. They are common method types that teams should evaluate when building a cross-border payment roadmap.

How to choose the right APMs by market

Use a decision matrix before adding payment methods to checkout. The point is to select methods with a clear customer and operational reason.

This is where a checkout provider can help. A provider can simplify method access, hosted checkout design, routing, reporting, and payment-status handling. But each method still needs market, legal, risk, and operational validation before it becomes part of a live checkout.

Explore checkout implementation, then confirm method availability with the HaiPay payments team before making launch commitments.

A practical APM rollout plan

Do not launch alternative payment methods as a one-time feature dump. Treat them as a portfolio that should be prioritized, tested, measured, and maintained.

1. Map customer markets and payment expectations

Start with the markets, customer segments, and transaction types that matter most. A merchant selling digital services in South Korea may evaluate different payment methods from a B2B platform expanding into Europe or a marketplace serving mobile-first shoppers in Southeast Asia.

Useful inputs include checkout analytics, abandoned-payment data, support tickets, sales feedback, market research, competitor checkout reviews, and payment provider coverage.

2. Prioritize methods by opportunity and complexity

Score each method against likely demand, coverage, implementation effort, settlement complexity, refund handling, support load, and compliance risk. A method with modest search volume but strong local buyer trust may outrank a globally known method with weak fit for your audience.

3. Design the checkout experience

Customers should understand what will happen when they select a method. If the flow redirects to a bank app, opens a wallet, shows a QR code, creates a pending order, or requires offline payment, the checkout should set expectations before the customer clicks.

Avoid generic labels when a clearer local label exists. Also avoid overloading the payment step with every method at once. Grouping, ordering, localization, and device-aware presentation can matter as much as the methods themselves.

4. Define payment states and support scripts

Every method needs a state model. At minimum, document what your team will show and do for:

• Payment created
• Customer redirected
• Customer authenticated
• Payment pending
• Payment succeeded
• Payment failed
• Payment expired
• Refund initiated
• Refund completed
• Dispute, reversal, or exception

Support teams should know what the customer saw, what status is authoritative, and when to ask payments or finance for help.

5. Confirm settlement, refunds, and reconciliation

Before launch, confirm the operational details with your provider. Do not assume a wallet, bank transfer, local scheme, and BNPL method behave like a card payment after checkout. Settlement timing, fees, refund routes, dispute windows, and reporting fields can differ.

Finance teams should know how each method appears in reports, how fees are represented, how currencies are handled, and how exceptions are investigated.

6. Launch with measurement

Track method adoption and quality after launch. Useful metrics include:

• Payment-method impressions
• Payment-method selection rate
• Authorization or confirmation success rate
• Drop-off after method selection
• Pending-payment completion rate
• Refund rate
• Support contact rate by method
• Settlement exceptions
• Checkout conversion by market and device

APMs should earn their place in checkout. If a method creates more confusion than completed payments, fix the UX, adjust ordering, localize the explanation, or remove it from low-fit segments.

Implementation checklist

Use this checklist before enabling a new APM.

For HaiPay implementation planning, use HaiPay Checkout to evaluate the checkout path, then confirm method coverage with HaiPay internal documentation or product owners. Do not publish claims about specific method support until those details are confirmed.

When a checkout provider becomes useful

A single payment method can often be integrated directly. A growing cross-border checkout usually needs more structure.

Consider a checkout provider or payment orchestration approach when:

• You sell across multiple countries and need local payment methods.
• You need one checkout experience with market-specific payment options.
• You want reporting and reconciliation across several methods.
• You need to test method ordering, localization, and payment status handling.
• Your support and finance teams need consistent operational workflows.
• You want to add methods without rebuilding the checkout each time.

The provider decision should still be grounded in method coverage, integration quality, payment status clarity, settlement reporting, refund handling, compliance support, and customer experience. A broader method list is useful only if the business can operate it cleanly.

Talk to the payments team to validate the right APM mix for your markets and confirm method availability before implementation.

Common mistakes when adding alternative payment methods

Adding methods without a market reason

A long method list can slow decision-making and make checkout feel less trustworthy. Start with customer demand, not a provider catalog.

Treating every APM like a card payment

APMs can differ in confirmation timing, refunds, disputes, reversals, reporting, and customer communication. Build method-specific operating notes before launch.

Ignoring pending and expired payment states

Some methods may not complete in a single immediate authorization flow. If the customer leaves checkout, scans a code, pays offline, or confirms in a bank app, your system and support team need a clear status model.

Making unverified regional claims

"Popular in Asia" or "best for Europe" is too vague to be useful. Use market-specific research, provider documentation, and internal performance data.

Measuring only total conversion

Track method selection, drop-off after selection, payment success, pending completion, refunds, and support tickets. A method may improve trust for one segment while creating friction for another

Next step

Build the APM roadmap around the markets you serve, the customers you want to convert, and the operations your team can support. Then validate the method list with your provider before implementation.

• Explore HaiPay Checkout
• Confirm available payment methods with the HaiPay payments team
• Talk to the payments team to confirm the right payment mix for your business.