Understanding Apple Pay Decline Rates in Recurly

Merchants may notice that Apple Pay transactions experience higher decline rates than other payment methods such as standard Visa or Mastercard card payments. Based on internal Recurly analytics across multiple merchants, Apple Pay decline rates commonly range between 30–35%, and in some cases can exceed 40%.

While these rates can be concerning, they are expected behavior within the Apple Pay ecosystem and are not typically indicative of a Recurly configuration or integration issue.

Why Apple Pay Declines Are Higher

Apple Pay introduces additional security layers that can increase authorization friction during recurring billing. Unlike traditional card payments, Apple Pay tokens are subject to:

• Stricter issuer risk models
• Reduced decline reason transparency
• Additional fraud-prevention logic enforced by issuing banks

As a result, declines are often returned with generic response codes (such as do_not_honor) rather than actionable details.

Common Decline Scenarios

Based on historical support cases and merchant data, Apple Pay declines most frequently occur in the following scenarios:

After a Free Trial Converts

• Initial Apple Pay verification succeeds
• First full-price renewal fails with do_not_honor
• Often due to issuer re-evaluating the transaction at higher value

After 1–3 Successful Billing Cycles

• Token remains valid
• Issuer later blocks subsequent renewals
• Common with insufficient funds or issuer policy changes

Vague or Generic Decline Codes

Typical Apple Pay declines include:

• do_not_honor
• insufficient_funds
• generic_decline

Retries and Dunning Considerations

Recurly uses Intelligent Retries by default, which dynamically schedules retry attempts based on:

• Decline reason
• Payment method type
• Historical success patterns

Because Apple Pay declines are often issuer-driven and non-descriptive, retries may occur sooner or more frequently than expected.

Some merchants may be eligible for custom retry schedules, which can space out retry attempts more conservatively. Availability depends on plan level and account configuration.

What Recurly Can and Cannot Control

Recurly Can

• Securely store and tokenize Apple Pay payment methods
• Send transactions to your configured gateway (e.g., Stripe)
• Surface decline reasons exactly as received from the gateway
• Apply retry and dunning logic based on available data

Recurly Cannot

• Override issuer or bank authorization decisions
• Force approvals on Apple Pay transactions
• Access detailed issuer decline explanations for Apple Pay

All approval and decline decisions are made by the gateway and issuing bank, not Recurly.

Recommended Next Steps

If you are experiencing high Apple Pay decline rates, we recommend the following:

1. Compare decline rates across payment methods
   Apple Pay should be evaluated independently from card-on-file payments.
2. Review declines after free trial conversions
   Consider testing shorter trials or upfront authorizations.
3. Consult your payment gateway
   Gateways such as Stripe may provide additional Apple Pay–specific insights.
4. Evaluate retry strategy
   Reach out to Recurly Support to discuss whether a custom retry schedule is appropriate.
5. Monitor trends, not individual declines
   Apple Pay performance should be assessed over time rather than on isolated failures.

Final Notes

High Apple Pay decline rates can be frustrating, but they are not uncommon and often reflect issuer-side controls rather than integration problems. Recurly Support is happy to review your account, analyze trends, and help you determine the best path forward.