Fallback to another processor and recover lost revenue
If, at first, you don’t succeed, then try again. Primer enables you to recover lost revenue seamlessly when your processor fails or declines. Configure fallbacks to route to a secondary processor to increase the chance of a successful payment.
3%
Scheme approved
26%
7%
+20%
Add redundancy
Recover multiple payment methods. Whether it's card payments or transactions via Google Pay and Apple Pay, Primer fallbacks give you the ability to recover revenue if your primary PSP fails.
Reduce churn
Maximize customer retention: reduce cart abandonment and implement fallback strategies to ensure repeat business.
"Banxa has recovered +17% of qualifying payments using fallbacks."
Greg Rikkhachai
Head of Payments
Features
One-click activation
Log into Primer, open your payment workflow, switch on Fallbacks, and select which processors you’d like to fallback to.. simple!
3DS configured
Utilize 3DS data from the initial authorization request, eliminating the need for customers to authenticate with 3DS multiple times.
Total visibility
Whether it's through our user-friendly UI or retrieving payment details via our Payments API.
Data insights
Unlock insights and visualize metrics such as recovered revenue, declines, and more. Identify growth opportunities with precision or dive deeper into analytics with Observability Pro.
One small switch for you,
one giant uplift for payments
FAQs
What is a fallback?
A fallback is a payment recovery mechanism that’s activated when the primary processor used by a merchant fails. If a merchant is using fallbacks, Primer will automatically divert the payment to a secondary processor, enhancing the likelihood of completing successful transactions.
Can I choose what processor to fallback to?
Absolutely, you have full control over selecting the primary processor for payment processing and determining the fallback processor to which transactions will be directed if needed.
Will my customer need to go through the 3DS flow when a fallback is triggered?
No. During checkout, your customer undergoes 3DS authentication, which is incorporated into the initial authorization request. Subsequently, when the fallback processor receives the second authorization request, the 3DS data is included, ensuring that the customer doesn't need to repeat the 3DS flow.
The smartest payment decision you’ve ever made
Connect your favorite payment and commerce services, create beautiful customer journeys and expand into new markets fast.
