AI Agents Stay Within Corporate Card Limits but Exceed Authority, Putting Approval Granularity in the Spotlight

According to a PYMNTS report dated 2026-11-17, AI agents can complete payments within a corporate card's per-transaction limit while still exceeding the scope of purchasing authority. For example, if a company approves a renewal with a designated supplier but the agent chooses a different vendor with a lower quote, that transaction falls outside the original authorization. Similarly, if rules trigger review only for purchases exceeding $1,000 per transaction, four expenditures of $900 each for the same project—totaling $3,600—would not trigger that review.
A July survey by PYMNTS Intelligence and JPMorgan found that 62% of CFOs said low-risk outbound payments are already released automatically without manual review, while 57% require dual approval or a callback confirmation. In another study, 61% of enterprises enable real-time identity verification signals only for high-value or high-risk payments.
Several fintech companies are now embedding authorization terms into the card-issuance process. In its November 10 product, Rain fixes the merchant, amount and validity period at issuance and verifies them at authorization; Ramp checks the request when an agent applies for a one-time card; Mercury gives agents access to designated virtual cards with manually set recurring limits and the ability to block by merchant; Sunrate allows agents to generate cards within company-approved workflows, restricting merchant category, amount and currency; and Corpay incorporates agent identity verification and expected-spend authorization into the card-issuance process.
Source: https://www.pymnts.com/news/b2b-payments/2026/ai-agents-put-corporate-card-spending-rules-to-the-test/
Provenance & status
- Byline
- OceanAlt Editorial
- First published
- 2026-11-18
- Last updated
- 2026-11-18
- Content type
- Newsflash
- Source material
- View original ↗
Related reading

Visa Pushes Agentic Ready to the Acquiring Side: Acquirers, Merchants and PSPs Begin Verifying 'Who Is Paying'

Fed and HKMA Speak on the Same Day: Two Compliance Tracks for Agent Payments Are Converging

HKMA and Swift Join Forces Again: Ensemble Connects to Swift Ledger, Cross-Border Clearing Layer Begins to Discuss Interoperability
Paste a payee address before you pay and see whether it's on a sanctions list, through a mixer, or tagged for fraud.
This judgement can sit inside your own product
One line of code; it touches neither your CSS nor your JS. The same pre-settlement judgement can appear in your articles, on your wallet's confirmation screen, or as an endpoint your agent calls before it pays.

