Integrate once

Find the yes

Payment orchestration for high-risk merchants: routing, 3DS policy, disputes, payouts and a copilot that explains every decision.

Engine room

Outcome routing

Routing trace

Dispute countdowns

Balances & payouts

Copilot

Playbooks

Payments

Developers

Settlerock is the layer above your acquirers. One contract, outcome-scored routing, same-call rescue, and a ledger that explains itself. Built for the merchants the big PSPs decline.

Play

Engine room tour

00:17

See it route!

Reel

Nine rails behind one contract

Built for

High risk

iGaming · forex · crypto · nutra

Why us

X days ago

New

Same-call rescue, depth 2

Routing

X days ago

New

3DS policy shows its observed cost

Protect

X days ago

New

Evidence packs drafted by Copilot

Disputes

X days ago

New

Sentinel: slow bleed alerts

Monitoring

X days ago

New

USDC payouts in early access

Settle

X days ago

New

Playbooks graduate to auto

Automate

Latest from
the engine room

Shipped, not
announced.

The engine room

( The dashboard )

Every payment carries its routing trace, every balance names who holds it, every alert says why it fired. The dashboard is the product. Nothing is hidden behind an account manager.

Good morning.

· Demo Merchant · one proposal waiting for your click

Approval rate · 30 days

of payments

Same-call rescues · 30 days

kept on hop 2

Dispute ratio · 30 days

disputes · 3 open

Next payout · T+1

· SEPA

Total balance

today so far

EUR USD GBP USDC

All currencies, in EUR at indicative daily rates

Volume · 30 daysLive

Approved
Refunded

Latest payments

See all →

Sentinelopen

Slow bleed on Rail 1 · EU

7-day approval: 74.2%
30-day baseline: 85.9%
24-hour refusals: 18.4%

Suggested playbook: move share from 35% to 15% and send the rest to Rail 2 · EU.

Card payouts · 30 days

1,284 payouts

Demo Merchant· HomeSample data

Total balance

today so far

EUR USD GBP USDC

All currencies, in EUR at indicative daily rates

Volume · 30 daysLive

Approved
Refunded

Latest payments

See all →

Card payouts · 30 days

1,284 payouts

We built Settlerock so a two-person payments team can run like a ten-person one.

Open the demo

One contract. Every rail. Four pillars.

Everything below is included. Nothing is a tier:

Part of the

contract

Route

Outcome-scored routing across every rail you are approved on. Rescue refused payments in the same call.

Part of the

contract

Settle

T+1 default payouts where the partner rail supports it. No minimums. Fiat and USDC.

Part of the

contract

Protect

A 3DS policy that shows what it costs, dispute countdowns, and a sentinel tuned for small volumes.

Part of the

contract

Automate

A copilot that cites rows and playbooks that ask first. Early access.

Part of the

contract

Developers

One API, idempotent by default, with a routing trace on every payment.

Part of the

contract

Built for

iGaming, forex, digital assets, nutra, dating, fintechs. The ones others decline.

Why Settlerock?

Approvals that hold. A ratio that stays boring. Money that lands on T+1. Built for the merchants the big PSPs will not touch.

Outcome routing
Every terminal earns a score per segment from what actually got approved. Rules are an override layer, not the brain. Ten percent of traffic explores so a cold terminal can earn its share back.
Same-call rescue
A gateway refusal is retried on the next eligible terminal inside the same request, two hops deep at most. Issuer declines are never retried. The buyer sees one receipt.
It explains itself
Every payment carries a routing trace. Every alert cites the rows it fired on. Every policy shows its observed cost before you pick it. Acquirers are never named to your buyers.

Routes

every major scheme

Visa

Mastercard

Apple Pay

Google Pay

SEPA

Open banking

USDC

3-D Secure

Decisions,
explained

Where the
traffic came from

Hop one refused, hop two approved in the same call.

Routing trace

pi_01JD3K8FQ

Terminal A returned a gateway refusal (A001) 212 ms in. The rescue path tried Terminal B, which approved. The buyer saw one request and one receipt.

Strict 3DS would have cost 4.2 points of approvals.

Protect

policy · prefer

In the last 30 days, strict mode on non-SCA traffic under €50 would have added 4.2 points of drop-off for 0.1 points of fraud. The policy picker shows that number before you choose.

Slow bleed on Terminal C caught before the ratio moved.

Sentinel

SNT-0231

Approvals on one segment slipped 3 points a day for four days. No single day crossed a threshold. The sentinel compares the trend to the sibling terminal and flagged it on day four.

Evidence pack drafted from rows, not from memory.

Disputes

dp_01JD7Q4KQ

Copilot pulled the delivery confirmation, the 3DS result and the customer history into one pack and cited each row. You read it, you send it.

Playbook asked first. Then it earned auto.

Automate

pb_pause_terminal

For a month the playbook proposed pausing a terminal after three refusal spikes. Every proposal was accepted. It now runs on its own, with the same bounds.

A settings change, logged with who and when.

Audit

accounts@demo-merchant.example

Last Friday 07:47 UTC someone set require_3ds on a terminal. Approvals dropped. The sentinel linked the drop to the change, and the Copilot named the account that made it.