Recurly vs Stripe Billing for Subscriptions That May Outgrow One Processor
Renewals from one country keep getting declined, and you'd like a second gateway for those customers. Recurly doesn't process cards itself. It runs plans, invoices and dunning on top of a gateway, and its list includes Stripe, Adyen, PayPal, Worldpay and Checkout.com. Stripe Billing runs on Stripe's own payments, and it can also bill payments taken by another processor, but your team writes that processor connection and some of Stripe's recovery tools don't apply to it.
Recurly or Stripe Billing, by how you take payments today
The billing fee on $100,000 billed in one month
List prices from each pricing page. Card and bank processing fees come on top of both.
| Recurly Starter platform fee | $249 |
|---|---|
| Recurly fee on billing past the first $40,000 (0.9% × $60,000) | $540 |
| Recurly Starter for the month | $789 |
Stripe Billing pay-as-you-go on the same month is 0.7% of $100,000, or $700. At $40,000 billed, the order flips: Recurly Starter costs its $249 fee alone, and Stripe Billing costs $280. Below about $35,600, Stripe Billing is cheaper again. The billing fee is rarely the deciding number, though. The processor rate underneath it is usually bigger.
Questions for both vendors about failed renewals and leaving
Which retry logic runs on our payments?
Stripe's Smart Retries work on Stripe payments, not on ones billed through another processor. Recurly Starter includes one dunning campaign, and All-Access allows several.
How would card details move if we change later?
Stored cards move between processors through a secure transfer the vendors arrange, never through a CSV. Ask how it's requested and whether subscriptions keep their billing dates.
Who issues a refund?
On Recurly, refunds go through the gateway underneath. With Stripe Billing on another processor, you refund at that processor and report it back to Stripe.
Does our checkout work with it?
Stripe Checkout can't take payments for another processor. Recurly offers recurly.js fields and hosted payment pages for collecting cards.
What counts as billing volume?
Stripe counts Billing transactions on and off Stripe, and prices one-off invoices separately. Recurly Starter includes the first $40K of billings each month before its percentage applies.
The processor code Stripe Billing leaves on your side
n-frames builds the piece Stripe's docs leave to you: the handler for each invoice.payment_attempt_required event, the charge through your other processor, and the payment record reported back to the invoice, including retries and refunds. On Recurly, we build what reacts to its subscription changes in your app, CRM and books. If you're moving between them, plans, add-ons and billing dates are mapped before the first renewal runs.
Off-Stripe payments on Billing invoices →Recurly and Stripe Billing: gateways, fees, dunning and moves
Can I use Recurly and Stripe together?
Yes. Stripe is one of the gateways Recurly bills through, so Recurly holds the plans, invoices and dunning while Stripe processes the card. In that setup you pay Recurly's fee and Stripe's processing fee, not Stripe Billing's.
Is Recurly cheaper than Stripe Billing?
Only in a narrow band. Recurly Starter's flat $249 beats Stripe Billing's 0.7% from about $35,600 to about $55,500 billed a month. Below that, Stripe's percentage is smaller. Above it, Starter's 0.9% on everything past $40K overtakes it: on $100,000 it's $789 against $700. All-Access is quoted from a $1M billing volume minimum, so ask Recurly for that number if you're near it.
Which one handles failed payments and dunning better?
On Stripe payments, Stripe Billing has Smart Retries and recovery emails built in. Recurly's strength is choice of gateway, with one dunning campaign on Starter and several on All-Access. If you'd bill some customers through a second processor on Stripe, those payments don't get Smart Retries or the recovery emails.
Can I migrate from Recurly to Stripe Billing, or the other way?
Yes, in two parts. Customers, plans and subscriptions are rebuilt on the new side with their billing dates, and stored cards move through a secure transfer between the processors involved. Plans, add-ons and proration rules don't model identically, so map them before switching and run the first renewals side by side.
Who builds a second processor into Stripe Billing?
That's code n-frames writes: the custom payment method setup, the webhook handler that charges your other processor when an invoice needs paying, and the payment records, retries and refunds reported back to Stripe so every invoice shows its real status.