<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>What the Corporate Card Already Solved on Control Plane by Karl McGuinness</title><link>https://notes.karlmcguinness.com/series/what-the-corporate-card-already-solved/</link><description>Recent content in What the Corporate Card Already Solved on Control Plane by Karl McGuinness</description><generator>Hugo</generator><language>en-us</language><managingEditor>public@karlmcguinness.com (Karl McGuinness)</managingEditor><webMaster>public@karlmcguinness.com (Karl McGuinness)</webMaster><lastBuildDate>Fri, 05 Jun 2026 13:00:00 -0700</lastBuildDate><atom:link href="https://notes.karlmcguinness.com/series/what-the-corporate-card-already-solved/index.xml" rel="self" type="application/rss+xml"/><item><title>Canceling the Card Doesn't Stop the Charges</title><link>https://notes.karlmcguinness.com/notes/canceling-the-card-doesnt-stop-the-charges/</link><pubDate>Fri, 05 Jun 2026 13:00:00 -0700</pubDate><author>public@karlmcguinness.com (Karl McGuinness)</author><guid>https://notes.karlmcguinness.com/notes/canceling-the-card-doesnt-stop-the-charges/</guid><description>Cancel a card and watch what refuses to end: the subscription bills the new number the network helpfully forwarded, the pending hotel charge settles days later, and the refund arrives through a process you do not control. Payments learned that ending an instrument is not ending an arrangement, and built machinery for the difference: reversible freezes, terminal cancellations, single-use cards that retire themselves, in-flight states between authorized and settled, chargebacks as governed compensation, and the statement that reconciles everything to one project code. This post maps each ending onto the agent task that must actually stop, and closes with the breaks, including the one where the analogy runs backward.</description></item><item><title>The Network Approves Every Transaction, Not the Card</title><link>https://notes.karlmcguinness.com/notes/the-network-approves-every-transaction/</link><pubDate>Fri, 05 Jun 2026 12:00:00 -0700</pubDate><author>public@karlmcguinness.com (Karl McGuinness)</author><guid>https://notes.karlmcguinness.com/notes/the-network-approves-every-transaction/</guid><description>A decline at the register is mild embarrassment and a tap of a different card, because the system is working: the network approves transactions, not cards. This post walks per-action authorization the way payments runs it: the plastic that proves almost nothing, the authorization that binds this amount at this merchant now, the hotel hold that expires, the freeze that declines the next swipe wherever the issuer decision is checked, and the ATM, the escape hatch every honest card program names in writing. Then the breaks: agents have no common payment-style network, their false-approval costs are unbounded, and their cardholder can be hypnotized mid-purchase.</description></item><item><title>The Contractor Gets Their Own Card</title><link>https://notes.karlmcguinness.com/notes/the-contractor-gets-their-own-card/</link><pubDate>Fri, 05 Jun 2026 11:00:00 -0700</pubDate><author>public@karlmcguinness.com (Karl McGuinness)</author><guid>https://notes.karlmcguinness.com/notes/the-contractor-gets-their-own-card/</guid><description>Crunch week. The contractor needs materials, and the project manager hands over her own card, just this once. Everything about it is convenient and everything about it is wrong, and every finance team knows exactly why. This post walks delegation the way a mature card program runs it: the contractor&amp;rsquo;s own card with a lower limit, attribution that survives the handoff, cards that die when the project closes, and caps on how many cards a project may issue, not just how big each one is. Then the three places the analogy breaks for AI agents, where the fixes have to be built.</description></item><item><title>You Approve What You Were Shown</title><link>https://notes.karlmcguinness.com/notes/you-approve-what-you-were-shown/</link><pubDate>Fri, 05 Jun 2026 10:00:00 -0700</pubDate><author>public@karlmcguinness.com (Karl McGuinness)</author><guid>https://notes.karlmcguinness.com/notes/you-approve-what-you-were-shown/</guid><description>A manager approves a conference request on their phone between meetings. Months later, the only defensible answer to &amp;lsquo;what did you approve?&amp;rsquo; is the request as rendered on that screen. This post walks the anatomy of a real approval: requests that are proposals and nothing more, reviewers who narrow instead of denying, decisions that take days without losing their place, and the disclosure that binds. Payments turned that last idea into regulation. Then the honest part: three places the analogy breaks for AI agents, and what each break demands.</description></item><item><title>Agents Need a Corporate Card, Not a Blank Check</title><link>https://notes.karlmcguinness.com/notes/agents-need-a-corporate-card-not-a-blank-check/</link><pubDate>Fri, 05 Jun 2026 09:00:00 -0700</pubDate><author>public@karlmcguinness.com (Karl McGuinness)</author><guid>https://notes.karlmcguinness.com/notes/agents-need-a-corporate-card-not-a-blank-check/</guid><description>Nobody hands a new hire the company checkbook. In a mature spend program, they get an instrument bound to an approved purpose, checked at each transaction, metered against a budget, and frozen when the reason for the spend goes away. Agent credentials today are blank checks with expiry dates. This post walks the expense-governance loop end to end, maps each control onto agent authority, and is honest about the five places the analogy breaks. Each break is something the agent stack still has to build.</description></item></channel></rss>