Ralio runs payment agents that execute transactions (spend, payroll, treasury) on behalf of business customers, under guardrails, identity, and audit on every move. Humanos sits at the merchant boundary and verifies every transaction before it executes.
Ralio lets business agents safely execute transactions — spend, payroll, treasury — on behalf of business customers.
Humanos sits at the merchant boundary and verifies every transaction before it executes — identity, scope, counterparty, amount, validity.
Ralio today operates inside the customer’s own bank API. Every payment flows through that customer-owned channel, so Ralio’s guardrails are enough — no external system has to recognise or authenticate the agent itself. The moment the agent has to transact outside the bank API — hosted checkouts, B2B marketplaces, acquirer networks — the same approach no longer applies.
Ralio governs the agent inside the customer-owned bank API channel by design. The moment the same agent transacts at a venue the customer doesn’t own — a marketplace checkout, an acquirer, a third-party processor — the merchant side has no credential to verify, no registry to consult, no way to confirm the action is authorized.
Inside the channel, Ralio’s guardrails, identity, and audit are sufficient. Outside it, agentic payments stay off the table. Without a shared credential bridging Ralio to merchants, marketplace checkouts, acquirers, and hosted checkouts remain unreachable, and the customer’s agentic payment footprint can’t grow past the bank API.
Humanos issues a certificate scoped to the purchase — counterparty, amount ceiling, expiry — at Ralio’s request and authorized by the customer. The certificate is cryptographically signed and bound to the agent’s identity, then verified by the merchant in real time before settlement.
Within mandate, within constraints, within validity. The merchant settles. A Proof is attached to the transaction — portable, verifiable by any party.
Out of scope, expired, or revoked. Humanos requests step-up approval in real time (SMS, API), updates the mandate, and resumes once authorization is valid.
Six stages in chronological order. The animation on the right is the exact flow from our product page — adapted to Ralio’s €23,840.00 procurement order, settled at techsupply.eu.
The company’s finance lead creates a procurement agent on Ralio, connects it to the company’s bank, and defines its tasks and transaction limits. Ralio’s guardrails govern every action the agent takes inside that channel.
Finance lead authorizes scope, counterparties, ceiling, and validity. Humanos issues a machine-verifiable mandate — signed once, reusable across every merchant that verifies.
Triggered by the procurement request, Ralio’s agent calls Humanos to receive the certificate. Humanos issues it scoped to the mandate, signs it cryptographically, and binds it to the agent’s identity. The agent assembles the order at techsupply.eu and attaches the certificate to its outbound request as x-humanos-mandate.
At checkout, the merchant calls humanos.verify() directly against the certificate. Identity, scope, counterparty, amount, and validity are checked in 82 ms.
Authorized → Ralio’s agent executes the payment through the customer’s bank API channel and money moves. Not authorized → the merchant declines, and Humanos blocks at the boundary and triggers real-time step-up authorization.
Both Ralio and Humanos hold verifiable records. Ralio’s audit records every agent tool-call decision; Humanos’s registry records the certificate verification. Together they form a complete chain of authority from finance lead to merchant, independently verifiable forever.
Nothing settles on assumption. The verify call is non-optional and inline at the merchant boundary, alongside Ralio’s controls on the agent side.
Issue once, verify anywhere. The same mandate works across merchants, processors, networks, and acquirers.
Merchants check authority against Humanos directly. No bilateral relationship with the agent’s operator is required.
Each transaction emits a verifiable record attached to the settlement. Auditors query Humanos directly, with no internal log access required.
Issue a new mandate. Revoke the old one. Effective immediately, everywhere a system verifies.
Out-of-scope action? Humanos collects approval (SMS, API, KYC) and resumes execution once the mandate is updated.
External parties can check authority directly through Humanos, with no bilateral relationship required.
Issue once. Verify anywhere — merchants, processors, networks, acquirers.
External parties check authority directly, without trusting the agent’s runtime.
No new logic per venue. The integration is the verify() call.
The more systems verify against Humanos, the more valuable each mandate becomes.
Execute purchases on external B2B marketplaces — hardware, software, services.
Buy on marketplaces and aggregators with authorization the marketplace itself can verify before clearing the order.
Card networks and acquirers verify agent-initiated charges against a human mandate before authorizing the transaction.
Agents acting across partner systems, verified independently by every system they touch.
Human authorizes scope. Humanos issues a machine-verifiable mandate, reusable across every system that verifies.
Any external system runs humanos.verify(). Deterministic yes / no.
Out of scope? Request step-up authorization from the human principal in real time — API, SMS, or email.
Cryptographic Proof per action. Auditable forever. Verifiable by anyone.
At that moment, authorization must be verified, the decision must be deterministic, and the outcome must be provable. Everything else follows.
Across organizations, marketplaces, processors, and networks.
No bilateral relationship with the agent operator required.
Anyone can verify it. Forever.
