PRODUCT · routing engine · cards · A2A · wallets
Whaliepay routes every transaction through the rail with the best predicted success for that exact shopper. Cascading retries on failure, one tokenisation vault across all PSPs, one ledger across the lot — in 240ms p95.
Your merchant code calls one Whaliepay API. We evaluate the rule set, the live success-rate matrix, the shopper signals — and forward to the rail that wins. If the rail declines, we retry on the next-best within 200ms. The shopper never sees the failure. Your finance team sees one ledger.
Whaliepay never holds funds. Money flows from the shopper to your PSP to your bank on the existing rails. We sit in the routing decision and the reconciliation step — no merchant of record, no holding period, no extra licensing.
Four pillars run under one engine. Each one is exposed in the console, each one is auditable end-to-end, each one shows you the data behind the decision.
The engine ranks the eligible rails for each shopper using the live success-rate matrix (PSP × BIN × country × method × hour band × amount band), shopper history, and twelve signal features. The top-ranked rail wins the transaction. Re-ranked every 4 seconds, never stale.
When a charge declines on rail A, the engine retries on rail B within 200ms — same card, same shopper, same amount — without the shopper ever seeing the failure. Median uplift: +4.6% auth across our customer base, with 1.4 retries per declined attempt on average.
Cards are tokenised once and reusable across every connected PSP. Migrate acquirers, add a new region, swap a rail — no need to re-collect cards from your customers. The vault is PCI-DSS Level 1, hosted EU-only by default, with HSM-backed key wrapping and quarterly rotation.
One double-entry ledger across all PSPs, A2A providers and wallets. Auto-reconciled to your bank within 4 hours of settlement, with discrepancies surfaced for finance. Closes the month from one screen, not from eighteen PSP exports.
Whaliepay is built by people who have run payments inside merchants of all sizes. These six features are the ones you'll touch every week — not just the ones we put on the brochure.
Write routing in plain language. "EU card under €100 → Adyen, Stripe fallback. SEPA → Mollie." Version-controlled like code, deploy with a click, roll back in one tap if the data disagrees.
Split traffic between two rule sets, watch the auth rate diverge in the console, promote the winner when you've seen enough volume. The engine handles allocation and statistical significance.
We collect the fraud signals from every PSP, normalise them into one shopper-risk score, and feed it back into the routing decision. Stripe Radar, Adyen RevenueProtect, Forter, Riskified — one score.
For SCA-mandated regions, we route low-risk shoppers through frictionless 3DS, and challenge only when the issuer is likely to authenticate. Average frictionless rate across our base: 71%, up from 38% pre-Whaliepay.
If your business sits in a high-decline MCC (gaming, digital goods, subscription), we let you route by sub-MCC, by SKU, or by basket composition — the kind of granularity a single PSP would never offer.
Routing decisions go down to the issuing BIN. We've watched a single BIN range gain +12% auth by routing through a different acquirer — the engine spots that pattern in days, not in quarters.
If we can't meet these targets for one full quarter, we credit the affected customers a routing-month for free. Published on /status.html, audited by NCC Group, never adjusted retrospectively.
Connect what you already have. Whaliepay shipped its first PSP integration in late 2021 — every subsequent one has been put through the same shadow-mode validation: 48 hours mirroring your live traffic, before any production routing.
This is the live tail of our wh-cli, hooked into the staging routing engine on this site's load. Every line is a real decision: signal collection, rule evaluation, rank, forward, retry on failure.
Free routing audit on your real data. Signed NDA, results in 5 working days, projected auth-rate uplift, FX savings and retry-window impact sent back as a PDF.