Payment method support matrix

Filter by method type, by processor, or search for a scheme by name or code.

A method listed here is supported by the integration. Whether it is available on your store also depends on your account, your currency and what your acquirer has enabled — resolve that at runtime with paymentSetup rather than hard-coding this table.

How to read this

TagadaPay charges money through two different arrangements, and the matrix mixes both:

TagadaPay (managed)

We are your payment provider. You hold no processor credentials — onboarding, acquiring, settlement and payouts run through TagadaPay. This is the widest method catalogue.

Bring your own processor

You hold the merchant account and give us the credentials. The method catalogue is whatever that processor supports through our connector.

Every method in the matrix falls into one of three families, which behave very differently at checkout:

Family	What the shopper does	What your integration does
Card	Enters a card number (Visa, Mastercard, American Express, Discover, JCB, Diners Club — per acquirer)	Tokenize in the browser, then charge server-to-server
Wallet	Confirms in a native sheet (Touch ID, Face ID, screen lock)	Open the sheet, receive a token, charge server-to-server
APM	Is redirected to the provider, authorises, comes back	Charge, receive a redirect URL, send the browser there, wait for the webhook

APMs are redirect-based and asynchronous. The charge call does not return a final status — it returns a requireAction with a redirect URL. The real outcome arrives on a webhook after the shopper returns. Never treat the charge response as a completed payment for an APM.

Recurring and subscriptions

The Recurring column means the method can be charged again later without the shopper present (a merchant-initiated transaction).

Cards, Apple Pay and Google Pay are reusable. On the native path the wallet is stored as a network token and rebilled on the card rails, so a subscription started with Apple Pay keeps billing after the sheet is gone. Link is Express-only and single-use — hence its — in the Recurring column.
Most APMs are single-use. The shopper authorises one specific amount on the provider’s page. If your funnel has a subscription or a post-purchase upsell, an APM will not silently rebill — design for it.

Discovering what a store can actually charge

The matrix tells you what the platform supports. It does not tell you what your store has switched on. That answer is per-store and lives behind one call:

import { getStorePaymentSetup } from '@tagadapay/core-js';

const setup = await getStorePaymentSetup({
  storeId: 'store_xxx',
  apiKey: 'tp_pk_live_***',
});

if (setup.config.apple_pay?.enabled) renderApplePayButton();
if (setup.config.klarna?.enabled) renderKlarnaButton();

import { Tagada } from '@tagadapay/node-sdk';

const tagada = new Tagada({ apiKey: process.env.TAGADA_API_KEY });
const setup = await tagada.paymentSetup.get('store_xxx');

const enabled = Object.values(setup.config).filter((m) => m.enabled);

Keys in config are two-dimensional — "<method>" when there is one provider for that method, and "<method>:<provider>" when the same method is routed through more than one. Read Alternative payment methods for the full shape.

What this matrix does not tell you

Whether a method is commercially available to you

Support in the integration is not the same as a signed agreement. Some methods need a separate contract with the scheme, or underwriting on your account. Talk to your account manager.

Per-country and per-currency limits

The Coverage column is indicative. Real availability is decided by your acquirer per market, and some methods have amount floors and ceilings. paymentSetup reflects what is actually switched on.

Refund behaviour per method

Refunds go through the processor, not the method. Some APMs settle asynchronously (vouchers in particular) and cannot be refunded before they settle. Check the specific scheme’s rules.

Processors

Every processor, and which operations each one supports.

Alternative payment methods

The redirect lifecycle, per-processor APM detail.

Apple Pay & Google Pay

Native vault vs through-processor wallets.

Overview

Payments

Web Integration

Tracking & Attribution

Node SDK

Funnels

Funnel demos

Examples

Shopify

WooCommerce

SaaS Billing

Headless SDK

Plugin SDK

Plugin CLI

Studio MCP (AI Agents)

Config MCP (AI Agents)

Hosting & A/B Testing

Internal

Payment method support matrix

Payment method support matrix

How to read this

TagadaPay (managed)

Bring your own processor

Recurring and subscriptions

Discovering what a store can actually charge

What this matrix does not tell you

Next

Processors

Alternative payment methods

Apple Pay & Google Pay

​Payment method support matrix

​How to read this

TagadaPay (managed)

Bring your own processor

​Recurring and subscriptions

​Discovering what a store can actually charge

​What this matrix does not tell you

​Next

Processors

Alternative payment methods

Apple Pay & Google Pay

Payment method support matrix

How to read this

Recurring and subscriptions

Discovering what a store can actually charge

What this matrix does not tell you

Next