Orchestration and fallback
Your checkout calls Halba once. Halba sends the payment to the primary PSP of your workspace and, if that PSP fails for technical reasons, retries once on the backup PSP, without asking the customer anything again.
Payments rescued, not lost
A technical decline on the primary PSP is not the end of the order. Halba tries the next route and the customer only sees the approval.
Primary and backup PSP
Each workspace (a brand, a country, a business line) has its own PSP connections. Today the first PSP you connect is the primary and the second is the backup.
Retry only when it makes sense
Technical declines, timeouts and PSP errors go to the backup. Lost or stolen cards, issuer fraud declines and Mastercard advice codes 03 and 21 are never retried.
3D Secure travels with the payment
When a payment already passed 3D Secure, the retry on the backup acquirer uses a 3DS Requestor Initiated authentication (3RI): the customer is not challenged twice.
Soft declines handled
If the issuer asks for strong authentication, Halba runs 3D Secure and retries the authorization, instead of returning a decline.
Fraud vendor over PSP risk
If a PSP's own risk engine blocks an order that your fraud vendor approved and guaranteed, Halba can resubmit it to the backup PSP.
Safe by design
Every PSP call carries an idempotency key and generous timeouts, so a retry never charges the customer twice. Wallet payments are not moved between PSPs: the token belongs to one PSP.
Available today
- Adyen, Stripe and Checkout.com as primary or backup
- Fallback with 3RI, soft decline recovery, PSP risk override
- Every attempt recorded and visible in the dashboard
Coming next
- Routing rules you edit in the dashboard (by country, method, amount, cost)
- More PSPs: Braintree and Nuvei
Try it in the sandbox
Connect your test PSP accounts, create an API key and send your first payment in minutes. No real money moves in the sandbox.