Reading an agentic-payments company

Sample note, written to show the format. There are no prices, no market caps and no named holdings. It is not a recommendation.

Agentic payments is a stack wearing a single phrase. The companies in it do not all sell the same thing, and the mistake is to compare them as if they did. This note is a reading order for the category. It is not a note on a named company.

If a number would only be credible with a data room, it does not belong here.

Five layers

Layer one is the right to issue. Someone holds a licence, a BIN or a sponsor relationship that lets a credential exist. This layer is slow, regulated and dull. It is also the layer a better model does not rewrite. The question is the licence path and the scheme relationship, not the demo.

Layer two is the credential. Virtual cards, one-time numbers, network tokens, account credentials a piece of software can present. The product questions are practical. Can a credential be created for one task and die at the end of it. Can it be paused without pausing the rest of the program. Can the descriptor on the statement be read by the person who owns the account.

Layer three is policy. Amount caps, merchant locks, time limits, a budget per agent, an exception queue. This is where “the agent pays” either becomes a control system or stays a screenshot. A company that cannot show a declined payment it meant to decline has a chat product, not a program.

Layer four is the ledger and the reconciliation. Agents are chatty. Finance teams are not. If a hundred small authorisations cannot be tied back to a task, a cost centre and a human owner, the product will be turned off by the first controller who sees the export. This layer is rarely on the pitch. Ask for it anyway.

Layer five is distribution. A developer API, a neobank that wants agents on its cards, a wallet, an expense tool. Distribution decides which of the other layers the company must own and which it can rent. An API company that rents the BIN is a different risk from a sponsor that rents the interface.

A reading order

1. Name the layer they actually sell.
2. Name the layer they rent, and what kind of partner they rent it from.
3. Ask what happens on a decline, a refund and a dispute.
4. Ask which human is on the hook. If the answer is “the model”, stop.
5. Only then look at growth. Growth in a layer they rent can leave with a contract.

What would have to be true for the category to matter is not mysterious. Software has to be allowed to pay, with limits a scheme will recognise, and with a cardholder of record a regulator already understands. The companies that matter will look, from a distance, like card programs that grew a new kind of customer. The ones that matter less will look like chat products with a card number pasted on.

Keep this file as the shape of a deep dive. Do not backfill it with invented prices.