Can You Use Stripe Billing With Another Payment Processor?

Short answer: yes, but not every Stripe Billing feature works the same way. Stripe documents two ways to keep using Billing for subscriptions while a different processor takes the payment. You can integrate your own processor using custom payment methods and payment records, or mark invoices paid out of band. In both, Stripe manages the subscription and you handle the charge. Smart Retries, Stripe Checkout, the hosted invoice page and Stripe-initiated refunds don't work for those payments. Stripe's separate Orchestration product can route Billing payments to other processors, but it's in private preview.

Last reviewed against Stripe's documentation on November 1, 2026.

Gateway, processor, merchant account and billing platform

Stripe bundles all four, which is why "use Stripe Billing with another processor" sounds harder than it is. You're unbundling the billing layer from the processing layer.

How Stripe Billing manages subscriptions

Stripe Billing holds the subscription: price, billing cycle, trial, discounts and status. Each cycle it creates an invoice and, normally, charges the saved payment method through Stripe. If the charge fails, Billing runs your retry settings and moves the subscription to past due, unpaid, canceled or paused, depending on your configuration (source). With another processor, the subscription logic stays in Stripe. Only the charge moves.

How third-party payment processing works with Stripe Billing

Option 1: Integrate your own processor

This is Stripe's fuller integration (docs). The flow:

1. Create a custom payment method type in the Dashboard to represent cards processed elsewhere.

2. When a customer signs up, Stripe creates the subscription and first invoice. Your checkout collects payment through the other processor.

3. Your server creates a custom payment method that references the other processor's stored credential, then reports the outcome with a payment record and attaches it to the invoice.

4. For renewals, Stripe sends an invoice.payment_attempt_required webhook. Your server charges through the other processor and reports the result.

Stripe warns not to save sensitive payment credentials, including card numbers, with Stripe in this setup. You must report the first payment within 23 hours of creating the subscription, or it expires.

Option 2: Out-of-band invoices

The simpler, older approach (docs). Subscriptions use the send_invoice collection method. When an invoice is finalized, your server charges through the other processor and marks the invoice paid_out_of_band. Stripe has no visibility into the payment until you do, and you handle all retries. You also need to switch off Stripe's invoice emails and the customer portal's payment method updates so customers don't pay twice.

Available approaches compared

Don't confuse Orchestration with a custom integration. With Orchestration, the third-party processor still processes the payment and its terms apply, but Stripe manages the connection. Supported processors currently include Adyen, Braintree and Worldpay WPG, and disputes and settlement are handled in that processor's dashboard (source).

What happens to recurring payments and saved cards?

In the custom integration, the card lives at the other processor. Stripe only holds a reference to it. That means:

• Existing cards saved at Stripe don't move automatically. Customers paying through the other processor need a credential stored there.

• Customers can switch between custom and Stripe payment methods in the customer portal, which Stripe supports for subscriptions using custom payment methods.

• Card updates, network tokens and account updater services come from the other processor, not Stripe.

Which billing functions need extra work?

Sources: Stripe's own-processor and out-of-band documentation.

Stripe Checkout, Smart Retries, refunds and disputes

These four cause the most surprises. Checkout can't capture off-Stripe payment details, so you'll need the Payment Element or your own payment page. Smart Retries won't run, so failed renewals need your own schedule. If you rely on Smart Retries today, measure how much it recovers before moving customers off it. Refunds start at the other processor and get reported back to Stripe so invoices stay accurate. Disputes live entirely in the other processor's dashboard.

If failed payments are already your biggest leak, see how Redux's AI recovery engine works on top of your current setup.

When to keep Stripe Billing, and when to switch

• Keep Stripe Billing if it already models your plans well, most payments can stay on Stripe, and you want a second processor for some customers or regions.

• Consider another billing system if most payments will run elsewhere, you need features Stripe Billing doesn't support off-Stripe, or your business isn't in a supported country.

Implementation considerations for growing subscription businesses

• Check that your business and processor countries are on Stripe's supported lists.

• Stripe counts off-Stripe volume toward your Billing pricing.

• Build idempotent webhook handling so a renewal is never charged twice.

• Decide which processor each customer uses, and store it.

• Plan reconciliation across two payout sources.

• Budget honestly. Stripe's own guide estimates custom multiprocessor integrations take 6 to 18 months of engineering (source), though a narrow setup can be smaller.

Frequently asked questions

Can Stripe Billing charge cards through another processor?

Not directly in the standard integration. With Stripe's third-party processing integration, Stripe Billing creates the invoice and tells your server a payment is due. Your server charges the customer through the other processor and reports the result back (source). The exception is Stripe Orchestration, in private preview, where Stripe routes the payment to a supported processor for you.

Do Smart Retries work with off-Stripe payments?

No. Stripe says off-Stripe payments support automations and scheduled retries, but not Smart Retries or revenue recovery emails (source). With out-of-band invoices, you handle all retries yourself (source).

Can I use Stripe Checkout with a third-party processor?

Not with the custom processor integration. Stripe says Billing with non-Stripe processors works with the Payment Element or your own checkout, but not Checkout, because Checkout can't capture details for off-Stripe payments (source).

Does Stripe charge for subscriptions paid through another processor?

Yes. Stripe counts billing volume processed off Stripe as part of your total Billing volume, and your normal Billing pricing applies (source).

Is this the same as Stripe Orchestration?

No. The third-party processing integration means you build and run the connection to the other processor. Orchestration is a Stripe-run routing layer that sends payments to supported processors such as Adyen, Braintree and Worldpay WPG (source). It's currently in private preview.

Get help evaluating your payment stack

Redux helps subscription businesses work out whether they need a second processor and how to connect it without replacing billing unnecessarily. We'll be clear about what Stripe supports today and what you'd need to build.

Get help evaluating your payment stack

Related: how to add a backup payment processor without leaving Stripe and Stripe alternatives for subscription businesses.

Sources

• Stripe, Integrate your own processor

• Stripe, Use out-of-band invoices

• Stripe, Custom payment methods and payment records

• Stripe, Orchestration and supported features

• Stripe, Automate payment retries

• Stripe, Evaluating and managing multiple payment providers