Approval flow

When approval is triggered

Any transfer where amount ≥ threshold on the API key triggers the approval flow. The operation does not fail — it pauses and waits.

Flow

1. Agent calls nuez.transfer or POST /v1/transfers with an amount at or above the threshold.

2. nuez pauses execution and creates a pending approval record. The API does not return immediately — the connection stays open (long poll) for up to 5 minutes.

3. WhatsApp notification is sent to the phone number on the account. The message includes:

   • Amount and currency
   • Destination (CVU/CBU/alias and name if available)
   • Description from the request
   • Approve / Reject buttons

4. Owner responds with a tap. nuez records the decision.

5. If approved: the transfer executes over Transferencias 3.0 and a signed webhook fires. The MCP tool or API call returns with the transaction result.

   If rejected: the API call returns 402 Payment Required with "status": "rejected". The agent receives this as a tool error and can handle it in its reasoning loop.

Timeout behavior

If no response is received within 5 minutes, the pending approval expires. The API call returns 408 Request Timeout with "status": "expired". The agent should surface this to the user and retry if needed.

Handling approval in agents

For MCP agents, Claude handles the wait transparently — it receives the tool result when the approval resolves. For REST API integrations, use the GET /v1/transfers/{id} endpoint to poll status if you don’t want to hold the connection open.

Testing approval flow

Use your sandbox key (nz_sk_test_...) and set a low threshold (e.g. 1). Every test transfer will trigger the approval flow without moving real money.