Decaf

AI-agent payments

Give agents payment authority with boundaries.

Design AI-initiated payment workflows around scoped identity, purpose, recipients, limits, budgets, approval thresholds, idempotency, and observable outcomes—not unrestricted access to money.

Now onboarding design partners.

Conceptual design-partner workflow
  1. 1Agent proposes
  2. 2Evaluate identity
  3. 3Apply policy and budget
  4. 4Human approval when required
  5. 5Execute supported workflow

Bounded jobs

Start with a job, not an open wallet.

Each example is a conceptual design-partner workflow whose controls and available routes must be reviewed.

01Conceptual design-partner workflow

Supplier invoice assistant

Propose a payment to an approved supplier within a task budget and request review above a threshold.

02Conceptual design-partner workflow

Marketplace operations agent

Prepare eligible seller payouts and surface exceptions instead of bypassing them.

03Conceptual design-partner workflow

Last-mile distribution agent

Prepare recipient communication and payment intent while keeping claim and access eligibility explicit.

04Conceptual design-partner workflow

Reconciliation agent

Associate approved status with an internal task without gaining authority to create a new payment.

Control model

Separate a request from permission to move money.

A governed workflow evaluates who is acting, why, for whom, and within which bounds before execution.

Identity and purpose

Identify the agent, user, service, business, and authorized business task.

Recipient

Confirm that the destination is known, eligible, and allowed for the task.

Amount and budget

Evaluate the operation and cumulative spend against assigned bounds.

Approval and time

Limit authority to the required window and escalate selected conditions to a person.

Idempotency and receipt

Distinguish a retry from a new action and preserve an auditable result.

Governed execution

Request. Evaluate. Approve. Execute. Prove.

Automation can prepare work while policy and human-control boundaries remain explicit.

  1. Agent proposes
  2. Evaluate identity
  3. Apply policy and budget
  4. Human approval when required
  5. Execute supported workflow
  6. Return auditable result
Conceptual design-partner model; no unrestricted autonomous spending or self-service API availability is implied.

Explore related workflows

Explore Decaf for Developers

Decaf for Developers

See the broader controlled payment platform.

Programmable payments

Understand the general payment lifecycle and operational controls.

Stablecoin payments API

Explore the fiat-edge and stablecoin infrastructure layer.

Last-mile payments

See how reach, secure claim, and eligible access stay distinct.

AI-agent FAQ

Questions about governed agent payments.

Design-partner access

Define the authority your agent actually needs.

Share the task, policy boundaries, approval rules, markets, and recipient outcomes you want to evaluate.

Now onboarding design partners.