Hyperswitch smart retries
How Hyperswitch decides whether a failed payment is retried and how: cascading, step-up 3DS, clear PAN and global network retries, the error code mapping behind them and the merchant configuration needed.
Hyperswitch features
Hyperswitch modules and workflows beyond basic routing that buyers evaluate separately: retries, revenue recovery, reconciliation, network tokens and payouts.
Hyperswitch revenue recovery for failed recurring payments
What the Hyperswitch revenue recovery module does for subscription businesses: retrying failed recurring payments alongside an existing subscription system, and how it differs from plain dunning.
Hyperswitch reconciliation module
How Hyperswitch reconciliation matches order management, processor and bank records on a double-entry ledger, how exceptions are handled, and what finance teams need to supply.
Hyperswitch network tokenisation
Enabling card network tokens in a self-hosted Hyperswitch: the profile flag, the token service configuration, the network and connector allow lists, and the vault fallback when a token cannot be used.
Hyperswitch payouts
Sending funds to bank accounts, cards and wallets through Hyperswitch payout connectors, with bulk uploads, payout smart retries and processor-independent tokenization of recipient details.
