How it works

Paxora sits between your store and the gateways you already use. Your store, Paxora, your gateways, your bank. Nothing about where the money goes changes.

1. 01

   Vault

   The customer enters their card into a Paxora field on your page. It is tokenised in the browser straight to a PCI Level 1 vault. You get a token. Nobody in the chain except the vault ever sees the number.

2. 02

   Route

   Each payment is sent to the gateway account most likely to approve it. Rules you write run first (amount, currency, card type, issuer, time). With no rule match, Paxora picks the account with the best recent approval rate for that card type. Every decision is logged in plain language you can read.

3. 03

   Cascade

   A soft decline (insufficient funds, a network glitch, an issuer timeout) is retried on a second gateway within seconds, never the same gateway twice, at most two attempts. Hard declines (stolen card, closed account) stop immediately. Card scheme retry limits are enforced in code, not policy.

4. 04

   Recover

   Recurring charges retry on a schedule tuned to when issuers approve. Expiring cards update automatically before the first retry. Customers who still fail get a one-tap, merchant-branded card update page. Recovered revenue is counted to the dollar.

What Paxora never does

• —Holds funds. Settlement is acquirer to merchant, exactly as it is today.
• —Sees card numbers. Tokens only, end to end.
• —Replaces your acquirer. Paxora sits beside the gateways you already use.
• —Locks your data in. Vaulted cards export on your instruction.