POST /payment/purchase endpoint. You switch between methods with a single discriminated paymentMethod object — { "type": "<code>", "<code>": { ...fields } } — always required and explicit, including for cards. This page is your starting point for the full payment method catalog: browse by category below, or use the quick-lookup table to jump straight to a specific method.
A method is available to your account once a connection that supports it is configured and enabled in your dashboard (see Smart Routing). The catalog below is the full set Therius supports — check the Connections page in your dashboard for what is live on your account, and contact Therius to enable a method you don’t see there.
Browse by Category
Cards & Wallets
Visa, Mastercard, Apple Pay, Google Pay, PayPal, Alipay, GrabPay, and more.
Bank Transfers
Pix, ACH, SEPA, iDEAL, BLIK, PSE, SPEI, Przelewy24, and more.
Vouchers & Cash
Boleto (Brazil), OXXO (Mexico), and Konbini (Japan).
Buy Now, Pay Later
Klarna, Afterpay, Affirm, and Zip installment options.
Asia-Pacific Methods
UPI, QRIS, FPX, PayNow, PromptPay, and GrabPay across APAC.
Latin America Methods
Efecty, Rapipago, PagoFácil, Khipu, Transbank, and more.
How Redirects Work
Most alternative payment methods (APMs) return astatus of "pending_action" along with an actionRequired.url. Your integration must redirect the shopper to that URL so they can complete authentication or payment on their bank or wallet’s page. After the shopper finishes, Therius redirects them back to the returnUrl you passed inside the method’s object.
If you’re using the Therius JS SDK, you don’t need to handle this manually — call sdk.handleAction(result.actionRequired) and the SDK manages the redirect, waits for the result, and resolves the promise for you.
Some redirect methods require additional fields in the request — such as
returnUrl, cancelUrl, or shopper details like name and email, all inside the method’s own object. These requirements are noted on each method’s page.Base Request Shape
Every request toPOST /payment/purchase shares the same base structure. paymentMethod is a discriminated object — type picks the method, and a matching key holds that method’s fields.
value: 1999 with exponent: 2 equals $19.99. For zero-decimal currencies like JPY or CLP, use exponent: 0 and pass the full integer amount.
Shared, request-level fields that apply across methods — shopper, browserInfo, lineItems, billingAddress, deliveryAddress, metadata, webhookUrl — sit alongside paymentMethod at the request root, never nested inside it.