● Unlicensed · We never hold funds · Orchestration only

Every payment takes
the route it should have taken

Baton sits between your stack and 100+ payment providers: one API, real-time routing, automatic cascading on failure, unified reconciliation. Card data never reaches your servers; funds never reach our accounts.

+2.6ptauth rate on the piloted route
-18%cost per successful payment
100+direct connectors
POST /payments 89.00 USD Router rules v4 BIN · country · currency stripe ✔ 820ms adyen backup soft decline · retry hard decline · stop
Succeeded on first attempt Soft decline → cascade to backup Hard decline → never retry

Why add a layer on top of Stripe

Because "auth rate" and "true cost" are only meaningful when you can see several providers at once.

Auth rate

A failure should not mean a lost order

Temporary issuer declines, provider timeouts, over-eager fraud rules — all of these can succeed on another route. Baton classifies every decline as soft or hard from a unified code: soft cascades automatically, hard stops immediately so you do not get penalised by the card networks for retrying.

Cost

A lower rate is not a cheaper rate

A provider quoting 3.2% at an 81% auth rate costs far more per successful payment than one quoting 2.9%, once failed attempts are amortised. Baton computes true settled cost from settlement files and feeds it back into routing weights.

Control

Explain any incident in ten seconds

When a merchant says "I never got the webhook", you open the delivery log and read the HTTP 500 body. Every payment has a timeline; every attempt keeps its raw provider code, on one page.

Eight core capabilities, eleven console modules

From integration to reconciliation, all in the same back office.

One payments APIA single POST /payments covers every provider — authorize, capture, void, refund and resume
Cascading failoverSoft declines retry on another route; hard declines stop at once. Timeouts are queried first, never double-charged
Rule routing & A/BSplit by currency, country, BIN and amount; experiments report auth-rate and cost deltas directly
Card vaultPromote a single-use token to a long-lived vault token explicitly; your PCI scope drops to SAQ-A
Hosted checkoutHPP + client token, card fields on a separate origin, 50KB first-paint budget enforced in CI
Unified decline codesRaw provider code → unified code + soft/hard. Routing, retries, analytics and alerts share one dictionary
Reconciliation & costSettlement files normalised into true settled cost (cross-border fees and FX loss included), fed back to routing
ObservabilityTimeline per payment, every attempt, every webhook delivery; request_id threads the whole chain
OverviewPaymentsCustomersRoutingConnectorsCheckoutRiskFinanceMonitoringDevelopersSettings

Four calls to go live

Create the payment server-side with a secret key; render checkout client-side with a publishable key and a client token. Card numbers never reach your servers.

1
Create the paymentOne endpoint for every provider
2
Get a client tokenBound to amount, order and customer; expires in 24 hours
3
Render checkoutHPP or Web SDK — card fields live in an iframe on a separate origin
4
Receive webhooksDedupe by key, order by updated, retry at 1/2/3/4 minutes
# Always send an idempotency key — a network retry will not create a second payment
curl -X POST https://api.baton.example/v1/payments \
  -H "Authorization: Bearer sk_live_xxx" \
  -H "Idempotency-Key: 01J8Z..." \
  -d '{
    "reference_id": "ORDER-10240",
    "amount": 8900,
    "currency": "USD",
    "payment_method": { "token": "pm_xxx" }
  }'

# The response carries status and available_actions; render your buttons from those
{
  "uid": "PY20261116000217A7F3",
  "status": "authorized",
  "attempt_count": 2,
  "available_actions": ["capture", "void"]
}

Priced on volume, never a cut of GMV

Platform fee plus call volume, billed separately from provider rates. We do not take a percentage of your sales — that is the acquirer’s business, not ours.

Growth

$2,400/mo and up
Teams doing 10k–500k payments a month
  • Payments API + hosted checkout
  • Cascading failover and rule routing
  • Card vault
  • Delivery logs and manual replay
  • Standard email support

Enterprise

Talk to sales
Multi-entity, multi-region merchants that need an SLA
  • Everything in Growth
  • A/B experiments, attribution, cost insights
  • Custom routing strategies and approval flows
  • Enterprise SSO / SCIM, IP allowlists
  • 99.99% SLA and a dedicated contact

Frequently asked

Do you touch our funds?

No. Money flows provider/acquirer → merchant and never through us. Baton holds no licence, no float, and carries no settlement risk.

How much code has to change?

One server-side call to create a payment, and a swap of your checkout component. Keep your existing providers — start by putting only routing and cascading behind Baton.

Is card data safe?

Card numbers reach neither your servers nor our business database — only a vault reference backed by a KMS. Your PCI scope can drop to SAQ-A.

Prove it on one real payment first

We run a controlled comparison in the test environment using your own rates and providers, and hand you the delta in auth rate and cost per payment. If we cannot beat your current setup, there is nothing to sign.

Book a demo Read the API docs