Recurly Problems & Issues
Real user-reported problems, complaints, and limitations for Recurly. Based on analysis of 11 signals.
Issues by Category
Analytics and reporting are weak
One of the biggest frustrations is Recurly's weak analytics. Users have to export data to Excel to calculate churn by cohort or plan type. Built-in reporting tools are called 'useless for deeper analysis.' Dunning email performance metrics (open rates, click-throughs) aren't available despite being critical for optimization.
Limited customization options
Several users feel boxed in by Recurly's limited customization. Editing invoices or setting custom renewal notifications is harder than it should be. Users who manage complex subscriptions say Recurly doesn't make it easy - combining invoices or managing renewals on custom schedules is problematic.
Refunds create new invoices causing confusion
When issuing refunds, Recurly generates new invoices instead of updating existing ones. This creates accounting confusion and makes reconciliation difficult. For businesses processing many refunds, this quirk adds significant administrative overhead.
Steep learning curve with bugs
Users report chasing support tickets and waiting for subscriptions to load when things should be instant. The steep learning curve combined with bugs significantly slows teams down during implementation and daily operations.
Auto logout after 5 minutes of idle
Users are automatically logged out after being idle for just 5 minutes. This interrupts workflows, especially when multitasking or referencing other documents. Combined with recurring password generation requirements, daily usage becomes frustrating.
Hidden fees make costs 40% higher than expected
Users report critical pricing terms not clearly communicated. One customer agreed to what they believed was a simple consumption model but was hit with surprise overage invoices due to hidden transaction limits. Fees were buried in follow-up emails and legal contracts, never discussed in sales calls. Actual costs ended up 40%+ higher than anticipated.
Advanced features require extra payment
If you need advanced tools like extra API keys, support for multiple business units, or custom fields, they come with added costs. Hands-on support, onboarding help, and technical guidance may cost extra. These costs aren't always clear during initial evaluation.
Support passes customers around without resolution
One user reported being charged thousands for collecting on a single bill. When flagging this multiple times, they were passed around to 5 different support people and eventually told the request wouldn't be entertained. Customer service described as 'disappointing at best.'
Customer support gives inconsistent answers
Support quality is described as hit-or-miss. One G2 user said when she asked the same question to different reps, she got different answers each time. This inconsistency becomes problematic when dealing with urgent billing issues that need clear resolution.
Platform downtime affects billing operations
Users report Recurly experiencing downtime that affected customers. One user noted their pricing page went down due to application issues, negatively affecting business. For a billing platform, any downtime directly impacts revenue collection.
Some integrations are clunky
Users report difficulties with certain integrations, such as GoCardless, describing them as 'somewhat clunky.' Integration challenges can slow down implementation and create ongoing friction in payment workflows.
Regret Patterns
Common reasons users regret choosing Recurly.
Discovered costs are 40%+ higher than expected
After signing, users realize transaction fees (1.25% + $0.10) and overage charges weren't clearly communicated. What seemed like simple pricing turns into significantly higher costs. By the time bills arrive, it's too late.
Needed analytics that don't exist
Teams expecting standard SaaS analytics discover they need to export to Excel for basic cohort analysis. Building workarounds or adding external tools adds unexpected cost and complexity.
Couldn't customize billing as needed
Complex billing scenarios that seemed manageable turn out to be difficult or impossible. Editing invoices, combining them, or custom renewal schedules require workarounds or aren't supported.
Support couldn't resolve urgent issue
When critical billing problems arise, inconsistent support becomes a real problem. Being passed between reps, getting different answers, and eventually being told requests won't be entertained.
Refund accounting became a mess
The practice of creating new invoices for refunds instead of updating existing ones causes reconciliation nightmares. Finance teams spend extra time cleaning up what should be automatic.
Platform went down during critical period
Experiencing downtime when the pricing page or billing system goes down directly impacts revenue. For subscription businesses, any disruption to signup or renewal flows costs money.
When Recurly Breaks Down
Specific scenarios where Recurly fails or underperforms.
Monthly volume exceeds $40K
At $40K monthly volume, 0.9% overage fees kick in on top of transaction fees. Combined with the 1.25% + $0.10 per transaction, total payment costs become substantial. Evaluate if dunning ROI justifies the expense.
Team needs cohort analysis or churn metrics
Built-in analytics are 'useless for deeper analysis.' When data-driven decisions become important, teams must build Excel workflows or integrate external analytics tools - adding cost and complexity.
Billing complexity increases
Simple subscription models work, but complex scenarios hit limitations. Custom renewal schedules, invoice combinations, or non-standard billing logic requires workarounds or isn't supported.
Refund volume increases
Each refund creates a new invoice instead of updating existing ones. With moderate refund volumes, accounting reconciliation becomes a significant burden. Finance teams need manual cleanup processes.
Urgent support issue arises
When billing emergencies occur, inconsistent support quality becomes critical. Being passed between reps without resolution or getting conflicting answers delays problem resolution.
Integration with specific gateway needed
While major gateways are supported, some integrations like GoCardless are described as 'clunky.' Evaluate specific gateway integrations before committing.