Integration Guides
Stripe Billing
Keep Stripe Billing as your subscription engine and process every payment through Primer
FunnelFox
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
Recurring Payments
Choose the right payment type and token for first payments and renewals
Save Payment Methods
Vault payment methods on the first payment for use in later renewals
Declined Payments
Separate hard declines from soft declines before scheduling a retry
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