From c1d4732fa86204dac6a2fa69619c96093154311b Mon Sep 17 00:00:00 2001
From: "claude[bot]" <41898282+claude[bot]@users.noreply.github.com>
Date: Sat, 22 Aug 2026 08:10:28 +0000
Subject: [PATCH] docs(cards): document maxSpendPerTransaction field

Document the per-transaction spending limit field added to cards in
commit 3fb42892. The OpenAPI spec and API reference pages already
include the field; this syncs the guides.

Changes:
- issuing-cards.mdx: add maxSpendPerTransaction to request table and
  example curl
- freezing-and-closing.mdx: mention maxSpendPerTransaction in intro,
  add "Updating the per-transaction limit" section with curl example

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
---
 .../snippets/cards/freezing-and-closing.mdx   | 25 ++++++++++++++++---
 mintlify/snippets/cards/issuing-cards.mdx     |  4 ++-
 2 files changed, 25 insertions(+), 4 deletions(-)

diff --git a/mintlify/snippets/cards/freezing-and-closing.mdx b/mintlify/snippets/cards/freezing-and-closing.mdx
index 2a28e4d24..81a0a6bae 100644
--- a/mintlify/snippets/cards/freezing-and-closing.mdx
+++ b/mintlify/snippets/cards/freezing-and-closing.mdx
@@ -4,11 +4,12 @@ credential revocation and wallet export. This page covers the flow,
 what each transition does, and how to handle the signing step.
 
 
-`PATCH /cards/{id}` covers both freeze / unfreeze (`state`) and funding
-source updates (`fundingSources`); see
+`PATCH /cards/{id}` covers freeze / unfreeze (`state`), funding source
+updates (`fundingSources`), and per-transaction spending limits
+(`maxSpendPerTransaction`). See
 [Funding sources](/cards/card-management/funding-sources) for the
 funding-source-only flow. The signed-retry mechanics below apply to all
-three.
+fields.
 
 ## Valid state transitions
 
@@ -126,6 +127,24 @@ curl -X PATCH "$GRID_BASE_URL/cards/Card:019542f5-b3e7-1d02-0000-000000000010" \
 `409 CARD_ALREADY_CLOSED` is returned if the card is already in the
 terminal `CLOSED` state.
 
+## Updating the per-transaction limit
+
+To set or change the per-transaction spending limit:
+
+```bash
+curl -X PATCH "$GRID_BASE_URL/cards/Card:019542f5-b3e7-1d02-0000-000000000010" \
+  -u "$GRID_CLIENT_ID:$GRID_CLIENT_SECRET" \
+  -H "Content-Type: application/json" \
+  -H "Grid-Wallet-Signature: <base64 signature>" \
+  -H "Request-Id: <requestId from prior 202>" \
+  -d '{ "maxSpendPerTransaction": 10000 }'
+```
+
+Supply a positive integer to set the limit (in the smallest unit of the
+card's currency) or `null` to clear it. Omitting the field leaves the
+current limit unchanged. `maxSpendPerTransaction` cannot be supplied
+alongside `state: CLOSED`.
+
 ## Sandbox behavior
 
 In Sandbox the state changes are instant — no issuer round-trip is
diff --git a/mintlify/snippets/cards/issuing-cards.mdx b/mintlify/snippets/cards/issuing-cards.mdx
index 69a83a6d9..9e157d3f0 100644
--- a/mintlify/snippets/cards/issuing-cards.mdx
+++ b/mintlify/snippets/cards/issuing-cards.mdx
@@ -14,7 +14,8 @@ curl -X POST "$GRID_BASE_URL/cards" \
     "form": "VIRTUAL",
     "fundingSources": [
       "InternalAccount:019542f5-b3e7-1d02-0000-000000000002"
-    ]
+    ],
+    "maxSpendPerTransaction": 5000
   }'
 ```
 
@@ -24,6 +25,7 @@ curl -X POST "$GRID_BASE_URL/cards" \
 | `platformCardId` | No | Your own identifier. System-generated when omitted, mirroring `platformCustomerId`. |
 | `form` | Yes | `VIRTUAL` in v1. `PHYSICAL` will be added later. |
 | `fundingSources` | Yes | Ordered array of `InternalAccount` ids. Each must belong to the cardholder and share one card-eligible currency. The first entry is tried first by Authorization Decisioning. |
+| `maxSpendPerTransaction` | No | Largest amount a single card transaction may authorize, in the smallest unit of the card's currency. Omit for no limit. Supported only for card programs where Grid makes the authorization decision. |
 
 The card's `currency` is derived from the funding sources at issue time
 and surfaces on the returned `Card` resource — all bound sources share