Workflows

The install pages put the SDK on the machine. The workflow pages explain how to operate it successfully after that point.

All operations described below execute locally on the operator's machine. WLFI does not custody, process, or facilitate any transaction.

Core workflow

1. Create or reuse a wallet - includes encrypted offline backup

2. Fund the wallet

3. Define the base spending policy

4. Add manual approval - only if some requests should pause for human review

5. Submit transfer requests

That is the main product path. Everything else is supporting configuration or maintenance.

Request execution path

Once the wallet is funded and policy exists, every transfer request follows one of two security-controlled runtime paths: it either clears policy and broadcasts immediately, or it pauses for manual approval.

The local daemon is the enforcement point: policy is checked before signing, and signing happens locally.

Read the sequence from left to right:

• Request -> Policy — The CLI submits the request to the local daemon via Unix socket. The daemon forwards it to the Policy Engine (vault-policy / PolicyEngine) for evaluation against all applicable policies. Policy always runs before signing. See Policy for how AllPolicies vs PolicySet attachments affect evaluation.

• Auto-approve path — If policy allows the request, the daemon delegates to the signer (vault-signer), which returns raw_tx_hex. The CLI then broadcasts to the EVM RPC and returns the result.

• Manual approval path — If a manual approval rule matches, the daemon pauses the request and returns an approval ID. The operator approves via local CLI. After approval, the daemon signs and the CLI broadcasts.

That second branch is configured through Manual approval.

Supporting pages

• Use cases - concrete day-to-day scenarios including gift card purchases

• Agent auth - credential rotation and migration

• Reset and uninstall - clear state or remove AgentPay

• Troubleshooting - common errors and repair

Recommended first live test

If you want one realistic end-to-end validation path, use this:

1. Run agentpay admin setup

2. Fund the wallet on the EVM network you plan to use

3. Define a modest base policy for routine transfers

4. Submit a small test transfer that should clear policy

5. Add a manual approval threshold for larger requests

6. Submit a larger test transfer that should trigger manual approval

7. Approve it through the local admin CLI

The default reference example in these docs uses BSC and USD1, but the same sequence applies on any supported EVM network once your chain and token settings are correct.