Payout instructions in. A route, a decision and a signed record out.
The agent reads each payout instruction, selects a route across bank, fintech and stablecoin rails under your objective and your limits, acts only within your company's approval tiers, watches the corridor for changes and records every decision. SwapEazi never sends the payment: after approval you release it yourself in your own bank or rail portal, then record what landed.
Six steps, each one on the record.
An email, a list or a file: each payout's amount, destination and due date, copied as written. Anything assumed is stated; a line that cannot be read is listed and left out, never guessed.
Bank, FX platform, payout network and stablecoin rails priced at the payout's size. The agent selects under your objective, lowest cost or fastest, and shows the cost against the reference and when it lands.
Your own approval tiers decide what happens next: within the agent's own limit it goes ahead, above it it waits for the named approver, and above the most the agent may sign off it is blocked.
After approval you get the prepared instruction: beneficiary, amount, currency, reference, which of your own accounts to pay from, and the cut-off. Copy it into your bank or rail portal and release it there; SwapEazi never sends the payment. Then record what landed.
Recent reported events on each pair, such as rule changes, outages or providers leaving a route, are shown beside the payout they bear on.
One record per payout with what was read, what was assumed, the route, the limits applied and the decision, hashed and signed so an auditor can verify it later.
Without your own limits the run uses a labelled demo policy: up to EUR 10,000 the agent releases alone, up to EUR 50,000 with finance_manager sign-off, and above that it is blocked. Free runs show routes by rail with provider names masked; a router key shows the names. The same run is available to your systems at POST /api/v1/agent/run, up to 25 payouts at a time.