Trusted execution 402-native payments Fiduciary optimization ERC-8004 Trustless Agents interoperable

The remittance protocol for agents — deploy an agent to find the cheapest route to send money safely.

Your agent compares providers, picks the best price, and sends money only when you confirm.

Stage → Confirm
Nothing happens until you approve
Deterministic
Same inputs → same result (auditable)
Flat fee
No FX markup
Interoperability

Works across agent and payment systems

So agents can discover routes, get a quote, and complete transfers using common formats.

Agent‑to‑agent messages
Standard message formats
Pay‑per‑request APIs
Automated paywalls for endpoints
Optional on‑chain trust signals
Identity and reputation lookups

This is a protocol + reference implementation.
Not a bank, custodian, or money transmitter.

Telegram Agent Demo
USD → KES → M‑Pesa
Live-ready
9:41
Back
RemitProtocol Agent
last seen recently
Send 10,000 KES to Mom.
3:19 PM
RemitProtocol Agent
Best Route Found: InstaSend
Cheapest total cost (including FX) for KES 10,000 net.
3:19 PM ✓✓
You send: $78.63
Mom receives: KES 10,000
Flat fee: $0.01 only
3:19 PM ✓✓
All‑in cost: ~1.13% (fees + FX)
Estimated savings vs typical apps: ~$2.05 (≈2.6%)
(illustrative; varies by corridor + time)
3:19 PM ✓✓
🧾 Staged transfer (nothing sent yet)
Route: InstaSend → M‑Pesa
Amount: KES 10,115 → Mom (+2547•••)
Net cash-out target: KES 10,000
Reply with PIN /confirm #### to execute ✅
(or /cancel to abort)
3:20 PM ✓✓
/confirm 4567
3:21 PM
Transfer Complete!
Receipt generated • Tracking ID: rp_7f3a…
You paid: $78.63 • Mom received: KES 10,000
Flat fee: $0.01 only • Saved to the audit log
3:21 PM ✓✓
Celebration gif
3:21 PM ✓✓
Message
Why RemitProtocol

Net delivery comparison

Compare what your recipient gets — after fees and FX markup.

Provider Send Mid‑market FX (ref) Applied FX rate FX markup vs mid Transfer fee M‑Pesa withdrawal Net received (KES) Explicit fees (EUR)
RemitProtocol €100 148.2 148.2 0.00% (0 bps) €0.01 KES 33* KES 14,786 €0.01
Wise €100 148.2 147.8 0.27% (≈27 bps) €1.20 KES 105 KES 14,485 €1.20
Remitly €100 148.2 145.5 1.82% (≈182 bps) €1.99 KES 105 KES 14,155 €1.99
WorldRemit €100 148.2 143.9 2.90% (≈290 bps) €2.99 KES 105 KES 13,850 €2.99

Mid‑market reference rate: 148.2 KES/EUR (illustrative; timestamped in production).

*FX markup is the hidden fee inside the exchange rate (spread vs mid‑market).

*RemitProtocol optimizes send amount to land within the lowest M‑Pesa withdrawal tier. Rates illustrative.

How it works

A five-step protocol flow for agent-native remittance

Design for intent, consent, and proof. Separate reasoning from execution. Keep everything auditable.

01

Discover

Agent checks what routes are available and who the recipient is.

02

Quote

Shows the exact cost and what arrives.

03

Optimize

Picks the cheapest way to hit the target amount.

04

Authorize

You approve with a confirm step.

05

Execute

Sends it and returns tracking + receipt.

Core primitives
RemittanceIntent (who, how much, corridor, constraints)
Quote (rates, fees, expiry, net delivered)
OptimizationResult (tier-aware recommendation)
Authorization (explicit user consent + signature)
Receipt (tracking id, ledger hash, timestamps)
Guardrails by default
Stage → confirm → execute (two-step commit)
Circuit breakers (max amount, corridor allowlist)
Backend-only API payload construction
Immutable append-only audit log
Replay protection + request integrity
Demo-ready MVP

A crisp demo that proves the thesis

Show the protocol primitives, then show the payout. Keep it simple. Make it auditable.

1) Fiduciary recommendation — Explain why the agent recommends this route (and any rounding) to hit the target.
2) Stage transfer — Show a staged summary (recipient, amount, route, and receipt preview).
3) Confirm & execute — Require explicit confirmation. Send it and return a tracking ID + receipt.
User flow

From intent to delivery in four steps

The protocol handles routing, optimization, and execution — you just say what you want.

1

You speak

“Send 5000 KES to Mom” via Telegram.

2

Agent reasons

Resolves contact, checks tiers, produces a staged intent + quote.

3

You confirm

Review breakdown + confirm with PIN. No confirmation = no transfer.

4

Money arrives

M‑Pesa payout executes. Recipient receives KES with a tracking ID.

Security & compliance posture

Built for explicit consent, auditability, and trust

We separate agent reasoning from execution, require explicit user authorization, and record all critical actions.

Explicit consent

No money moves without an explicit confirmation step.

Two-step commit: stage → confirm with PIN
Agent proposes, human disposes — never auto-executes
Session timeout: unconfirmed transfers expire

Full audit trail

Every action is logged immutably — no silent failures.

Append-only JSONL ledger for all transfer events
Timestamps + redaction (no PINs, no full numbers)
Exportable receipts and summaries

Hard guardrails

Circuit breakers that cannot be overridden by the AI.

Max transfer limit enforced in code
Single authorized user (demo mode)
Reasoning separated from execution
Open source

Trust through transparency

Protocol primitives, schemas, and reference implementation are open for audit.

Standards & interoperability

Built to work with emerging agent and payment standards

RemitProtocol complements commerce and payment protocols by specializing in remittance intents, compliance guardrails, and payout execution across rails.

A2A / Agent2Agent
A2A-compatible agent interoperability
Well-known agent card discovery
Interoperable message parts
Works across agent frameworks
x402 / 402 Payment Required
HTTP-native micropayment primitives
Pay-per-request economics
Machine-first settlement handshake
High-frequency, low-value calls
AP2-aligned mandates
Verifiable authorization artifacts
Explicit authorization boundaries
Deterministic, auditable receipts
Separation of reasoning and execution
/.well-known patterns
Discovery & capability manifests
Agent-readable capability discovery
Extensible corridor/rail metadata
Versioned manifests
ERC‑8004 (Ethereum)
Trustless Agents interoperability
Identity registry (ERC‑721 + registration file)
Reputation signals & validation hooks
Complements A2A + AP2 + x402
Positioning

Commerce protocols solve buying. RemitProtocol solves compliant remittance execution and recipient-first optimization.

Contact

Request a demo or join the waitlist

We’ll share a one‑pager, demo script, and the live Telegram walkthrough.