Payman Connect

Your agent does the work. Payman handles the money.

Your agent does the work. When that work reaches money, Payman executes it against your customer’s own accounts: with their consent, under their limits, and with their approval on anything that moves money.

const result = await payman.forUser(userId).run("Pay the Acme invoice for $120");
// result.kind: "ok" | "needs_connection" | "approval" | "error"

Payman Connect is the execution layer, not the brain. Your agent decides that an invoice should be paid or a balance checked, calls Payman for that one step, and reads the answer back in the same turn.

Your customer connects their Payman account once, on Payman’s own pages. It holds whichever providers they use: a bank, a corporate card, an accounts-payable tool. You hold a pointer to their consent, never a bank credential, and you never build a bank integration.

The SDK carries the rest. One secret, PAYMAN_APP_KEY, and one call per action; the consent handshake, the encrypted connection store, the approval flow, and the replay all ship with it.

Start here

Quickstart

A working integration in one page.

Add it as a tool

Your agent already runs a model. This is the one tool it needs.

How it works

The loop end to end.

Next.js

The three route files the App Router needs.