Decline Code 65: Activity Limit Exceeded
Decline code 65 is returned when a transaction would exceed the cardholder's activity limit — a cap set by the issuing bank on the number or total value of transactions allowed in a specific period (daily, weekly, or monthly). This is a soft decline because the limit resets automatically. It's one of the most recoverable decline codes with an 80-90% success rate on properly timed retries.
Affected Percentage
~4% of all declines
Recovery Rate
80-90% recoverable
Recommended Action
Retry with strategy
Common Causes
Daily transaction count limit reached
Many banks limit the number of transactions a cardholder can make per day (often 10-20). A flurry of purchases can exhaust this limit before your charge processes.
Daily spending amount exceeded
Banks set maximum daily spending thresholds. If the customer made a large purchase earlier that day, your recurring charge may push them over the limit.
Monthly velocity cap reached
Some cards have monthly transaction count limits. Near the end of the month, customers with many subscriptions may hit this ceiling.
Bank-imposed transaction frequency rules
Certain issuing banks have anti-fraud rules that limit how many transactions can occur within a short window (e.g., 5 transactions within 1 hour).
Recommended Retry Strategy
Timing
Retry the next calendar day, ideally in the morning (9-11am customer local time) when the daily limit has reset and few transactions have occurred.
Max Retries
2-3 retries over 3-5 days
Reasoning
Activity limits reset automatically (usually daily). A retry the next day almost always succeeds. If your charge is being crowded out by the customer's other spending, trying in the morning before other charges hit increases success.
Best Practices
- 1
Retry the next calendar day — activity limits almost always reset daily at midnight in the bank's timezone.
- 2
Schedule retries for the morning hours when the customer's daily limit is fresh and competition from other charges is minimal.
- 3
If you process multiple charges for the same customer (e.g., multiple subscriptions), batch them into a single transaction to use only one limit slot.
- 4
Consider moving your billing cycle to the 1st of the month when customers are less likely to have hit monthly limits.
- 5
No customer notification is typically needed for activity limit declines — a next-day retry almost always resolves it silently.
How Rezoki Handles This Automatically
Rezoki recognizes activity limit declines as highly recoverable and schedules an automatic retry for the next calendar day during morning hours. Because these declines are almost always resolved by a simple timing change, Rezoki does not send dunning emails for the first retry — avoiding unnecessary customer alarm. If the next-day retry also fails (rare), Rezoki retries once more 2-3 days later and only then considers light-touch outreach. This approach recovers 80-90% of activity limit declines silently, without the customer ever knowing there was a problem.