TESTNET · v0.1 ALPHA — Railguard Operator reference UI · not production-ready for mainnet funds

Airwallex payouts · Incident Commander

Payout incidents

An AI agent pays suppliers on Airwallex. When a transfer goes UNKNOWN, Railguard blocks the second payout, reconciles by request_id, and only then marks it CONFIRMED. Sandbox and simulator only, no real money.

Timeout or 5xx on create means UNKNOWN, never failed.

Retries are blocked while a payout claim is open.

One deterministic request_id per intent, so there is at most one transfer.

Chaos: force a timeout after create

The agent pays a supplier. Railguard drops the Airwallex response right after the transfer is created. The agent panics and pays again. Railguard blocks it, reconciles by request_id, and confirms exactly one transfer.

In-memory Airwallex simulator. No keys, no money, unlimited.

Press Force timeout to run it.

Ask the payment-ops agent

Plain-language requests. The agent can only call create_payout, get_transfer, reconcile and list_incidents. Policy and approvals live in Railguard's code.

Recorded scenarios (simulator)

Webhook deliveries

POST /v1/airwallex/webhook verifies HMAC-SHA256(x-timestamp + raw body) before parsing. Rejected deliveries are logged without payloads.

No deliveries yet.