Two merchants can sell the same product to the same customers and see approval rates several points apart. That gap is pure revenue. Authorization rates respond to specific, fixable causes.
1. Send better data
Issuers score every authorization request. Requests with complete, consistent data — correct cardholder name, billing address, CVV, and a sensible merchant category code — score better than sparse ones. If you collect the postal code, pass it through.
2. Use 3-D Secure 2 selectively and correctly
3DS2 raises approval odds on transactions issuers would otherwise decline as risky, and its frictionless flow authenticates most customers without a challenge. But forcing a challenge on every transaction adds drop-off. The right setup applies 3DS where risk signals or regulation call for it.
3. Retry intelligently, never blindly
Declines split into hard (stolen card, closed account — never retry) and soft (insufficient funds, do-not-honor, issuer unavailable — retry with care). Blind instant retries look like fraud and damage your standing with issuers. Spaced, limited retries on soft declines recover real revenue.
4. Route transactions to the right acquirer
Approval odds differ by acquirer, card type and geography. Routing a European card through a connection with better issuer relationships in that market measurably lifts approvals. This is the quiet advantage of gateways with multiple acquiring connections.
5. Watch decline codes weekly
Your decline mix is a diagnosis. A spike in fraud-suspected declines points to traffic quality; insufficient-funds clusters correlate with billing dates; technical declines mean integration bugs. You cannot fix what you don’t segment.
Quick checklist
- Pass full billing data on every request
- Enable 3DS2 with risk-based challenges
- Classify declines; retry only soft codes, with backoff
- Review approval rate by issuer country and card brand monthly
- Keep descriptors and MCC accurate
Payixay routes transactions across acquiring connections and reports decline reason codes per transaction. See card processing.