When your only processor has a bad day, so does your revenue. Brands tied to one provider have nowhere to go if it goes down, starts declining more than usual or changes its terms.
Moving to another provider usually takes months. Meanwhile each failed payment is a subscriber who may never come back, and with millions of subscribers a small drop in successful payments adds up to millions in lost revenue each year.
Failover is a backup route for every payment.
Payment gateway failover means that when one processor or gateway struggles, payments go through another automatically. OpenByte works with several processors at once, so there is always another route.
That covers more than a full outage. A processor that starts declining more payments than usual is a problem even when it is still up.
Different processors accept different payments.
A processor that’s great with UK debit cards might decline far more US credit cards. OpenByte sends each payment to the processor most likely to accept it, based on card type, country, amount and what’s worked before.
Wallets such as Google Pay run through the same routing, retries and reporting as cards. See what a better authorization rate is worth to your business.
Your payments setup should change when your business does.
Adding or switching a processor is a quick setup change instead of a big project, so a better price or a better acceptance rate is never months away.
Fees vary between processors depending on card type, country and currency. OpenByte sends each payment the cheapest way that won’t hurt its chances of going through.
Most payment systems only see a card and an amount.
OpenByte also holds billing, payment history and where every subscriber came from, so each payment decision is based on the full picture. Good customers get through more often, and risky ones get extra checks.
When a retry is needed, OpenByte looks at why the payment failed and picks the best time and route for the next try. Read more about dunning management.
Most brands find out about a revenue problem at month end.
A processor starts declining more cards. An affiliate starts sending fraud. When data arrives late and in pieces, these problems show up weeks after they started.
OpenByte updates as things happen, so you can spot a change in payments, cancellations or fraud the same day.
What is payment gateway failover?
Why use multiple payment gateways?
When does failover happen?
Can we keep our current processors?
How is failover different from payment retries?
How does pricing work?
