Resource / WalletKit workflows

WalletKit starts with the operating record around a transaction.

The goal is not to hide every provider detail. WalletKit should normalize the business state teams need for product, compliance, finance, and support while preserving provider-specific context where it matters.

Use this guide: Map the first workflow before choosing integrations. The workflow determines which provider events, controls, and evidence Alloy should normalize first.
Patterns

Start with the workflow that hurts.

Payouts

Normalize payout intent, approvals, provider submission, and reconciliation state.

Open route

Finance close

Turn provider and chain events into exception queues and ledger-ready exports.

Open route

Bank controls

Keep custody boundaries clear while making controls and review state inspectable.

Open route

AI authority

Give agents bounded spend authority with receipts and human override paths.

Open route
Next step

Bring one workflow to Alloy.

We will identify the WalletKit state model, provider events, and evidence records that matter first.

Map a workflow

Useful inputs: provider stack, transaction lifecycle, approval model, webhooks, and close process.