Increase auth rates by routing failed transactions to another payment processor

Re-route failed transactions

Your customer is finally ready to checkout, but when they hit that purchase button they see an error and they can't proceed because your payment service provider is down. The customer is frustrated and ready to leave your store - you've just lost the sale at no fault of your own.

You would think that payment service outages are rare, but Safecharge survey of European merchants found that 76% of respondents experienced at least one complete outage in their payment services and 42% experienced six or more partial outages in the 12 months prior to the survey being taken. Worse still, 39% of these outages occurred during peak sales periods, 73% of which lasted between 15 minutes to 1 hour. Imagine how much financial losses that error could cost you.

It’s a common practice to have multiple Payment Service Providers when you operate in different markets. And many providers support re-routing. The problem is, it’s seldom automatic. On top of that, failover like this requires direct involvement from the gateway provider.

I know this sounds fancy, and it will be. Because you’ll need engineers to manually do the heavy lifting for you. And while this switchover is taking place, the sale might already be lost.

Luckily, you've got WhenThen to save you the technical overhead so you can just chill and let our automation template do the job!

So…

Don’t worry, we’ve got your back!

Quite literally, you need a solution that’s got your back when payment outages happen.

With WhenThen’s Next Gen Automation Template, you can automatically route transactions that fail from your default payment processor (e.g., resulting from time-outs, outages or other technical errors) to another payment processor to try to save the sale. This automatic redundancy reduces single party risk and gives you peace of mind that payment service provider outages will have a minimal impact on your customer and business.

Don't have another Payment Process to route to?

We make it easy to add a Payment Processor connection or payment operations connection. All you need to do is authenticate using O-Auth, or by providing your API keys (you'll have to take care of the commercial agreement with your Payments Service Providers). Once you're authenticated, we take care of the rest and your new connection is ready to be used in our no-code payment automations builder.

What payment processors do you support and allow fail-over orchestration to?

At WhenThen, our goal is to take care of the heavy lifting when it comes to integrations, whether that's payment processors, service providers or operations, so we're constantly expanding on the number of connections available.

To see all the partners we currently support, visit our Connections page. If you don't see a partner, reach out to an Automator today and we can find a solution to work with any partner together.

How does WhenThen determine a failed transaction?

WhenThen receives and interprets each response from your Payment Service Provider. While any provider may have different response codes that indicate a failed response, WhenThen has mapped them to a single response type that you can build logic from. A FAILED response refers to a technical inability to get a proper answer on a payment. This could be the PSP is down or the PSP encountered an error on their side which prevented them from giving an actual response to your request.

Reach out to our team today and find out how much sales you can save with WhenThen!

Source: 1. Safecharge Whitepapers