> ## Documentation Index
> Fetch the complete documentation index at: https://primer.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview 

## Process subscription payments with Primer

Keep your subscription engine for plans, invoices, and renewals while Primer executes every first payment, renewal, and retry.

![Process subscription payments with Primer](https://mintcdn.com/primer-cc826789/Xq555ZpUYmf8cxLp/images/light.png?fit=max\&auto=format\&n=Xq555ZpUYmf8cxLp\&q=85\&s=a57cac7a3023ea6a5c1595026a3ebeb8)

You can use Primer with your subscription engine of choice, with Primer processing every payment and the engine keeping track of plans and subscriptions.

## Integration Guides

> [card] [Stripe Billing](https://primer.io/docs/subscriptions/stripe-billing.md)
>
> Keep Stripe Billing as your subscription engine and process every payment through Primer

> [card] [FunnelFox](https://primer.io/docs/subscriptions/funnelfox.md)
>
> Primer payments power FunnelFox's subscription engine

## What Primer brings to every attempt

* **One vault, many processors.** Payment methods are tokenized once with Primer and usable across every processor you connect, today and in future, so your billing engine never needs to know where a payment is processed.
* **Network tokens.** Issued and managed automatically, improving authorisation rates on renewals and surviving card reissues.
* **Correct recurring context.** Renewals are transmitted to issuers with the proper stored-credential framing, which is essential for how issuers score recurring traffic.
* **Routing and fallbacks.** Workflows decide processor selection per attempt, including fallbacks on technical failures and different routes on later retries.
* **Decline intelligence.** Normalised decline codes across processors power the hard and soft classification that gates every retry.
* **Observability.** Every attempt, route, and outcome is visible in one place across all processors.

## Understanding subscription payments

> [card] [Recurring Payments](https://primer.io/docs/get-started/recurring-payments.md)
>
> Choose the right payment type and token for first payments and renewals

> [card] [Save Payment Methods](https://primer.io/docs/payment-services/save-payment-methods.md)
>
> Vault payment methods on the first payment for use in later renewals

> [card] [Declined Payments](https://primer.io/docs/get-started/recurring-payments.md#recover-declined-or-failed-payments)
>
> Separate hard declines from soft declines before scheduling a retry

Each guide below covers one engine: how to set it up, how payments flow, and what the engine, your team, and Primer each handle.

## Use other subscription engines

Any subscription engine can work with Primer in the same way if it supports:

* A reference to a payment method stored outside the billing engine
* A notification when a payment is due, including for each scheduled retry
* An API to record payment outcomes against invoices
* A configurable retry schedule, or the option to turn off its own automatic collection

Contact your Primer account team to discuss a subscription engine that isn't listed on this page.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.