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. Card numbers are not stored, and all sensitive data is encrypted in transit and at rest. See Security and compliance for details.
A payment_instrument carries exactly one credential source: card details, a SmartRetry token, or a processor provider_token (with its merchant_account, provider_key, and for Adyen provider_shopper_reference). An optional cvv can accompany any of them.

​
Token-based payments

For a tokenized payment, send the 88-character SmartRetry token inside payment_instrument (under order on a sale or pre-authorization request). No submission response returns a token. Retrieve a stored payment-instrument token from order.payment_instrument.token on the transaction status response when available.
This removes the need to re-transmit raw card data, simplifying repeat billing and reducing PCI scope.

​
Provider-token payments

If you already hold a credential issued directly by one of SmartRetry’s connected processors, send it as provider_token (1–255 characters) instead. SmartRetry forwards it to the processor as-is. This differs from token, which is a SmartRetry Payment Instrument token.
For Adyen, also send the shopperReference the credential was stored under:
Setting payment_collection: hosted_page on a sale or pre-authorization request makes payment_instrument optional and rejects token/provider_token outright - the payer supplies a fresh credential later through the hosted payment page, not at create time. Redirect the payer to the hosted_page_url returned in the sale or pre-authorization response instead of building the URL yourself.

​
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.