AI agent payment controls should require a close file that proves the named customer authorized the specific invoice before release: matched invoice terms, buyer identity, approving user or standing rule, wallet or account ownership, refund and dispute terms, screening result, and settlement reference. Settlement proves money arrived. It does not prove the obligor accepted the invoice.

Coinbase put the issue in front of treasury and AR teams on Aug. 11. PYMNTS reported that Coinbase Business now lets businesses get paid by artificial intelligence agents through x402, which Coinbase described as an open standard for machine-to-machine payments. The same report said funds settle instantly in USDC, land in the business account, and are ready to earn rewards or withdraw on demand.

That is a rail fact. It is not the receivables answer.

A payment can arrive from a card, bank account, wallet, link, checkout, invoice portal, or token flow. The AR file still has to show who bought, who approved, what was bought, where performance is owed, and what happens if the transaction has to be unwound. The agent may have transmitted the payment instruction. It did not become the buyer.

AI agent payment controls begin with customer authority

The evidence should tie the payment instruction to the customer record and the specific invoice. The agent is only the messenger in that chain.

If the customer record names one legal entity, the file should not close because an autonomous tool reached the checkout and sent value. It should close because that customer, through an authorized person or accepted system rule, directed payment of the invoice under the terms AR expected.

The first control file is documentary. AR needs a durable record that shows the paying event belongs to the customer relationship. That record should answer five plain points before goods ship, services release, credits apply, or the receivable is marked paid.

Invoice match, owned by AR: invoice number, customer legal name, amount or accepted range, due date, tax treatment, and open balance.

Authority match, owned by sales operations or customer master data: the paying user, authorized domain, portal credential, purchase order, contract clause, or standing instruction that allowed the payment.

Rail match, owned by treasury: settlement reference, currency or token, receiving account, timing, fees, and any processor record.

Ownership match, owned by treasury with compliance support: bank account, card, wallet, or payment credential tied to the customer or to an accepted third party payer.

Exception path, owned by AR and legal: refund route, dispute terms, partial payment handling, overpayment rules, and who can amend the invoice.

None of those checks require the agent to be treated as a contracting party. In most receivables files, that would create more confusion than control. The buyer owes the money. The buyer receives the goods or service. The buyer has refund rights or dispute rights under the contract. The agent may have acted inside a workflow, but the workflow has to be tied back to the customer.

The rail is a funds question, not the authority file

Crypto changes the settlement artifact. It does not erase the ordinary AR questions.

Coinbase is explicit about the funds movement. The same PYMNTS account says Coinbase Business added payment acceptance from AI agents, Tether acceptance through links, checkouts and invoices, reusable payment links, flexible pricing, reusable product details, and collection of buyer name, email, shipping address and other details alongside the payment.

Those added buyer details matter. They are closer to the control file than the settlement speed is. A name and email can help connect the payment to a customer account. A shipping address can support fulfillment decisions. Product details can reduce the chance that a generic payment link is misapplied.

But buyer details are still claims unless the company tests them against its own records. A checkout can collect a name. The customer master can show whether that name is authorized. A wallet can transmit USDC. Treasury still has to decide whether the wallet is acceptable, whether the payer is the customer, and whether the transaction creates a refund path the company can execute.

The hard artifact is no longer the bank line item. It is the authority file that surrounds it. The same gap appears if the agent triggers a card payment, an account-to-account transfer, or a token payment. The rail tells you how value moved. It does not tell you whether the customer intended to pay that invoice on those terms.

Wallet ownership and refund rights sit beside screening

A token receipt needs more than a transaction hash. The seller needs enough evidence to decide whether it can accept, apply, refund, and screen the payment.

That is not a crypto-only concern. A card payment can come from an employee card, a procurement card, or a card used outside policy. A bank payment can arrive from a parent, affiliate, factor, or unknown third party. A wallet adds its own proof problem because the public address may not carry a customer name that AR can use.

The control file should keep the wallet or payment credential separate from the buyer identity. A customer can authorize a third party payer. A customer can pay through a custodian. A customer can use a wallet previously registered in a portal. Each case needs a different record. What fails is the loose assumption that money from any address must belong to the customer because it arrived at the checkout.

Screening belongs in the same practical file. The point is not to turn AR into a forensic blockchain shop. The point is to identify who owns screening, what data they screen, when they screen it, and what stops fulfillment if the result is unclear. If the agent supplies buyer details, those details should feed the same screening routine used for other inbound payments.

Refunds need the same discipline. If the customer returns goods or the company reverses service, can treasury send value back to the original wallet. If not, who approves an alternate route. If the token price, stablecoin issuer, or account access changes before refund, who owns the exception. These are receivables controls. They should be written before the first agent-originated checkout is treated as paid in full.

The close file needs named owners

The control should live in a close checklist, not in a product launch memo. A paid invoice should not be released from review until each owner has signed off on the evidence they control.

There is a useful parallel in an unrelated Treasury proposal. In proposed guidance for employer-sponsored contributions to Trump Accounts, the department described certification procedures that let employers rely on employee self-certification of a beneficiary’s age and dependent status, but also require validation that the receiving account is a Trump Account, according to ABA Banking Journal. Self-certification and account validation are different steps.

That distinction maps well to inbound payments. A customer-supplied detail is not account validation. A transaction record is not authority. A settlement confirmation is not acceptance of invoice terms.

Another external dependency is thinner than many teams expected. FinCEN finalized a rule removing the requirement for U.S. companies and persons to report beneficial ownership information under the Corporate Transparency Act, and the agency will delete previously reported information from the BOI database, ABA Banking Journal reported. Foreign companies still have reporting obligations for foreign individuals, but U.S. counterparty ownership evidence cannot be assumed to sit in that federal database.

That pushes more weight back into the company’s own customer file. For agent-initiated checkout, the close package should preserve:

Customer authority record: contract, portal role, purchase order, standing payment instruction, or written authorization.

Agent context record: what system, tool, or workflow initiated the checkout, if the business can capture it.

Invoice intent record: invoice number, line items, amount, allowed variance, and any flexible pricing basis.

Payment credential record: card, bank account, wallet address, custodian, or link identifier, with ownership status.

Screening record: customer, payer, wallet or account data, and the result before release.

Refund record: original return route and named exception approver if that route fails.

Coinbase said its Business suite serves more than 5,000 companies and its payment acceptance suite has powered more than 100,000 payments, according to the PYMNTS report. Scale makes the control question less theoretical. The more checkout types AR accepts, the more dangerous it is to let settlement become the whole file.

If agents start paying your invoices, the change is not that treasury needs a new philosophy of money. The change is that your release control needs a sharper line between funds received and customer authorized. The receipt can be instant. The authority file cannot be implied.