Approval Flow

When Yebo returns REQUIRE_APPROVAL, execution pauses. Nothing runs until a human explicitly approves. For payment missions, your passkey approves the mission's limits (capabilities, per-transaction limit, payees), and every payment in the mission is checked against those limits. Per-payment device signing is live and has been exercised in production: the approver's passkey signs the exact payment (amount, payee, agent, validity window), and anyone can check it offline with yebo-verify 0.2.0. Agents resume cleanly once the continuation token is issued.

This section is available to approved partners and pilot customers.

To access the full approval-flow reference including state transitions, continuation-token semantics, expiry handling, and end-to-end examples, request access below.

Request Access | Start a Pilot

If you already have access, sign in to the developer portal: yebo.dev/login