docs: document platform-level card spending cap - #890
Conversation
Add documentation for the new `cardConfigs.maxSpendPerTransaction` field introduced in #865. This platform-level cap applies to all cards and Grid enforces the lower of the platform and card-specific values. Updates: - Card issuing docs: mention platform cap interaction - Card freeze/close docs: explain platform cap enforcement - Platform config snippets: add Card Configuration section Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub. 2 Skipped Deployments
|
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Greptile SummaryThis PR documents the platform-level
Confidence Score: 4/5The PR should not merge until the new platform configuration sections are connected to the rendered documentation pages. The documented API details match the OpenAPI contract, but both newly updated platform configuration snippets are unreferenced, leaving the principal documentation addition invisible to readers. Files Needing Attention: mintlify/snippets/platform-configuration-non-uma.mdx and mintlify/snippets/platform-configuration-uma.mdx
|
| Filename | Overview |
|---|---|
| mintlify/snippets/cards/freezing-and-closing.mdx | Accurately clarifies that the platform cap is enforced without replacing the stored card-specific value. |
| mintlify/snippets/cards/issuing-cards.mdx | Accurately documents omission semantics and lower-of-platform-and-card enforcement during card issuance. |
| mintlify/snippets/platform-configuration-non-uma.mdx | Adds a contract-aligned card configuration example, but the snippet is not referenced by a rendered documentation page. |
| mintlify/snippets/platform-configuration-uma.mdx | Adds the same contract-aligned configuration example to another snippet that is not referenced by a rendered documentation page. |
Prompt To Fix All With AI
### Issue 1
mintlify/snippets/platform-configuration-non-uma.mdx:94-109
**Configuration section remains unreachable**
When readers open the rendered platform configuration documentation, this section is absent because neither changed platform-configuration snippet is imported by a documentation page, leaving the newly documented card spending cap undiscoverable there. The UMA snippet has the same issue.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.Reviews (1): Last reviewed commit: "docs: document platform-level card spend..." | Re-trigger Greptile
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| ### Card Configuration | ||
|
|
||
| The `cardConfigs` object contains platform-level settings for cards issued by your platform. To set a platform-wide per-transaction spending cap: | ||
|
|
||
| ```bash cURL | ||
| curl -X PATCH 'https://api.lightspark.com/grid/2025-10-13/config' \ | ||
| -u "$GRID_CLIENT_ID:$GRID_CLIENT_SECRET" \ | ||
| -H 'Content-Type: application/json' \ | ||
| -d '{ | ||
| "cardConfigs": { | ||
| "maxSpendPerTransaction": 10000 | ||
| } | ||
| }' | ||
| ``` | ||
|
|
||
| - `maxSpendPerTransaction`: (Integer or null) Platform-level cap on a single transaction for every card whose authorization decisions are made by Grid. The value is in the smallest unit of each card's currency (for example, cents for USD). Grid enforces the lower of this cap and each card's configured `maxSpendPerTransaction`. Set to `null` to remove the platform cap. |
There was a problem hiding this comment.
When readers open the rendered platform configuration documentation, this section is absent because neither changed platform-configuration snippet is imported by a documentation page, leaving the newly documented card spending cap undiscoverable there. The UMA snippet has the same issue.
Prompt To Fix With AI
This is a comment left during a code review.
Path: mintlify/snippets/platform-configuration-non-uma.mdx
Line: 94-109
Comment:
**Configuration section remains unreachable**
When readers open the rendered platform configuration documentation, this section is absent because neither changed platform-configuration snippet is imported by a documentation page, leaving the newly documented card spending cap undiscoverable there. The UMA snippet has the same issue.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
Summary
cardConfigs.maxSpendPerTransactionplatform-level spending cap introduced in [platform-spending-caps]: add a platform per-transaction spending cap #865Test plan
mint devmint dev🤖 Generated with Claude Code