POINTS

POINTS journal · compliance

Agent banking, and the compliance shape of an AI-agent bank account.

How an AI-agent bank account actually opens under the same KYC and CIP rules as any other US deposit account — who the legal accountholder is and where POINTS sits as the application layer. Coming soon: savings, checking, and credit features through a regulated partner bank. In development; not available today.

CIP · 31 CFR § 1020.220
KYB on sponsor
Banking: coming soon

Section 01 · The accountholder

The operator entity is the bank’s customer. The agent is a sub-identity.

A checking account in the US still has a single, named legal accountholder on the signature card and the bank’s records. When the customer is a business, that name is an entity — a corporation, an LLC, a partnership — tied to an EIN. When the customer is a person, it is an individual tied to an SSN or ITIN. The bank does not know, and does not record, whether the entity is operated by a human, a team, or software running an autonomous workflow.

For an AI-agent account that means the bank account sits on the operator’s entity. The agent itself is a sub-identity keyed to that sponsor: merchant descriptors, card plastics, ledger seats, and API tokens all hang off the operator. The bank opens one account per operator; everything the agent does is bounded by that single contracted relationship. If that relationship ends — the entity dissolves, the operator fails a re-CIP refresh, or the sponsor revokes the agent — the deposit account closes with it, and every sub-ledger seat under it goes to zero.

This is the structural reason an agent cannot, today, open its own bank account in its own name: there is no verifier of an agent’s identity that satisfies CIP’s documentary requirement, and no path for the agent itself to be recorded as a beneficial owner of anything. The bank’s customer has to be a legal person, human or entity, named on the signature card.

Section 02 · CIP mapping

Five CIP elements, and where the agent falls between them.

FinCEN’s Customer Identification Program rule, 31 CFR § 1020.220, requires a bank to collect and verify five elements before opening an account: name, date of birth or date of formation, address, identification number, and documentary verification of that identifier. For an individual customer the identification number is an SSN or ITIN and the documentary check is a government photo ID. For an entity customer the identification number is an EIN, and documentary verification runs against formation papers, an operating agreement, or a Secretary of State filing.

Entity customers also trip the beneficial-ownership prong. The bank has to identify and verify any individual who owns 25 percent or more of the legal entity, plus the single individual who controls it. That control prong is the one that lands squarely on the operator of an AI agent: the natural person behind the entity, not the agent itself, is who the bank records as the beneficial owner.

Section 03 · The banking layer (coming soon)

A regulated partner bank as BIN sponsor (coming soon).

Banking features are coming soon through a regulated partner bank; this section describes the planned design and is not available today. In that design, the partner bank holds the PAN on the issued cards and the deposit ledger, with program management, KYC orchestration, ledger APIs, and card issuance handled by the program partner.

The planned account model opens one deposit account per operator entity, with the agent represented as a sub-ledger seat rather than a separate bank customer. The agent is the operator of the bot on top of the account. The bank customer, on file, is the operator entity.

Section 04 · The application layer

POINTS wraps a verified identity around a regulated rail.

POINTS is the application layer. We mint the agent identity, sponsor-gate the operator through KYB and KYC, project a trust score that translates into per-transaction caps and a vendor allowlist, and expose a clean ledger and card-issue surface to the builder. We do the CIP collection, the beneficial-ownership capture, the KYB on the sponsor, and the SAR monitoring.

In the planned design, the deposit account lives at a regulated partner bank, not at POINTS. That is the structural fact: POINTS is not the bank. Banking features are coming soon; in development and not available today. Our role is the platform that wraps a verified identity and a programmable underwriting layer around it.

Obligation matrix

Same bank, three different liability profiles.

Eleven obligations we get asked about from operators standing up a new agent fleet. The first column is the planned regulated deposit account at a partner bank (coming soon; not available today). The second is an agent-branded card on that account. The third is the internal POINTS wallet or the on-chain treasury sweep — neither of which is a deposit account.

  • 01

    CIP collection (31 CFR § 1020.220)

    Operator checking · Bank collects name, formation, address, EIN, and documentary verification of the operator entity at account-open.

    Agent-branded card · Card program inherits the CIP record from the deposit account; no separate CIP runs at card issuance.

    POINTS wallet / treasury · No CIP — internal wallet is not a deposit account and is not a bank customer relationship.

  • 02

    KYB on the sponsor operator

    Operator checking · Bank runs business verification on the operating entity against formation papers and Secretary of State filings.

    Agent-branded card · Card program reuses the KYB packet; vendor allowlist and per-tx caps ride on top of the sponsor KYB outcome.

    POINTS wallet / treasury · POINTS runs an internal KYB equivalent to gate the wallet; nothing flows out of scope of the operator KYB.

  • 03

    Beneficial-ownership capture

    Operator checking · Bank records each 25%+ owner of the entity plus the single control-prong individual; CIP verifies each.

    Agent-branded card · Inherits the deposit account BO record. The agent itself is not a beneficial owner of the entity.

    POINTS wallet / treasury · Internal-only; the on-chain treasury does not create a new BO record at the partner bank.

  • 04

    OFAC / sanctions screening

    Operator checking · Bank screens operator entity and every beneficial owner at account-open and at periodic refresh.

    Agent-branded card · Card program screens each cardholder (the agent sub-ID) and the merchant at authorization.

    POINTS wallet / treasury · POINTS screens internal counterparties; the regulated OFAC obligation sits with the bank, not with us.

  • 05

    314(b) information sharing

    Operator checking · Bank may share CIP/transaction data with other 314(b) participating financial institutions on request.

    Agent-branded card · Card-side transactions flow through the same partner-bank rails and inherit 314(b) eligibility.

    POINTS wallet / treasury · Out of scope — internal wallet balances are not deposited funds at a partner bank.

  • 06

    BSA / AML monitoring

    Operator checking · Bank operates the transaction-monitoring program across the deposit account and reports to FinCEN.

    Agent-branded card · Card authorization stream lands in the same monitoring pipeline; POINTS surfaces operator-facing alerts.

    POINTS wallet / treasury · POINTS runs a parallel rules engine on the on-chain treasury for operator dashboards.

  • 07

    SAR filing

    Operator checking · Bank files SARs at its sole discretion based on the monitoring output.

    Agent-branded card · Inherits from the deposit account — no separate SAR obligation at the program manager.

    POINTS wallet / treasury · POINTS files no SARs on internal wallet flows; we escalate to the partner bank when its rules trip.

  • 08

    CIP documentation retention (5 years)

    Operator checking · Bank retains CIP records for the operator entity and beneficial owners for five years.

    Agent-branded card · Inherits — card program keeps no separate CIP archive outside the deposit record.

    POINTS wallet / treasury · No bank CIP record is created for the internal wallet.

  • 09

    1099-INT / 1099-B tax reporting

    Operator checking · Bank issues 1099-INT on deposit interest to the operator entity (and 1099-B if a brokerage sweep is enabled).

    Agent-branded card · Card cash-back rebates are not 1099-reportable unless they cross IRS thresholds; treated as marketing.

    POINTS wallet / treasury · Internal wallet on-chain treasury is enumerated to the operator under standard crypto tax rules, not 1099.

  • 10

    State money-transmitter licensing

    Operator checking · Bank holds the issuing licenses; POINTS does not touch the deposit funds itself.

    Agent-branded card · Card BIN sponsor liability runs at the partner bank; POINTS sits outside the MTL coverage.

    POINTS wallet / treasury · Internal wallet is a closed-loop ledger inside POINTS and is not licensed as a money transmitter.

  • 11

    Card BIN sponsor liability

    Operator checking · In the planned design, liability sits with the regulated partner bank as BIN sponsor (coming soon).

    Agent-branded card · Agent-branded card stock rides on the partner-bank BIN; the operator entity is the responsible party on disputes.

    POINTS wallet / treasury · No card BIN is issued against the internal wallet — it has no Visa BIN and no liability profile.

Next step

Open an agent account on regulated rails.

The operator mint flow mirrors the model above: KYB on the operating entity and a sub-ledger agent seat keyed to the sponsor. Banking features are coming soon through a regulated partner bank; in development and not available today.

Disclaimer

POINTS is not a bank. Coming soon: savings, checking, and credit features through a regulated partner bank. In development; not available today. This post describes the planned design for an AI-agent bank account and is not legal advice.