Skip to main content
SmartRetry supports a broad range of payment methods. You specify the payment method using the payment_method field inside the payment_instrument object in your request body.

​
Supported values

​
Specifying a payment method

Pass payment_method inside the payment_instrument object:

​
Card-specific fields

When using cards, include the card details in payment_instrument:
SmartRetry has access to card details and transaction data as part of the retry and optimization process. All sensitive data is encrypted in transit and at rest.

​
Token-based payments

After a successful transaction, SmartRetry returns an 88-character token in the response. You can store this token and use it in place of raw card data for future charges from the same customer. Pass the token in the payment_instrument object:
This removes the need to re-transmit raw card data, simplifying repeat billing and reducing PCI scope.

​
Currency support

SmartRetry supports 50+ currencies using ISO 4217 codes. Pass the currency code in the top-level currency field.
Supported currencies include: USD, EUR, GBP, JPY, KWD, CNY, AUD, CAD, CHF, SEK, NOK, DKK, RUB, ILS, INR, BRL, MXN, ZAR, SGD, HKD, NZD, AED, SAR, TRY, PLN, CZK, HUF, THB, PHP, MYR, BGN, RON, IDR, KRW, COP, UAH, VND, QAR, BHD, EGP, MAD, KES, UGX, NGN, OMR, ARS, CLP, JOD, PYG, RWF, and more.

​
Retry and recovery support

SmartRetry’s intelligent retry engine works by analyzing decline reasons and re-routing transactions through a different acquirer, 3DS configuration, or card parameter. Retry coverage varies by payment method:

Best retry coverage

cards and digital_wallets receive the most comprehensive retry logic, including acquirer routing, ECI-level adjustments, and 3DS optimization.

Method-dependent

bnpl, online_banking, rtp, direct_debit, and other methods are subject to the retry capabilities supported by the connected acquirer or provider.
SmartRetry only retries transactions that have a realistic chance of succeeding. Hard declines - such as stolen card or permanent do-not-honor responses - are not retried to avoid unnecessary processing.