payment_method field inside the payment_instrument object in your request body.
Supported values
Specifying a payment method
Passpayment_method inside the payment_instrument object:
Card-specific fields
When usingcards, include the card details in payment_instrument:
SmartRetry has access to card details and transaction data as part of the retry and optimization process. Card numbers are not stored, and all sensitive data is encrypted in transit and at rest. See Security and compliance for details.
Token-based payments
For a tokenized payment, send the 88-character SmartRetrytoken at the top level of the sale or pre-authorization request. A normal successful payment response does not return a token. Retrieve a stored payment-instrument token from the transaction status response when available.
Pass the token at the top level:
Currency support
SmartRetry supports 50+ currencies using ISO 4217 codes. Pass the currency code in the top-levelcurrency 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.