Skip to content

docs(sandbox): move the manual cancellation suffixes to their own page - #1193

Merged
JasonCWang merged 1 commit into
mainfrom
jw/sandbox-ops-cancellations
Oct 16, 2026
Merged

JasonCWang merged 1 commit into
mainfrom
jw/sandbox-ops-cancellations

Conversation

@JasonCWang

@JasonCWang JasonCWang commented Oct 16, 2026 •

Copy link
Copy Markdown
Contributor

Moves the manual cancellation sandbox suffixes (006 and 008) off the main quote suffix table and onto their own page, Sandbox Manual Cancellations. The page is hidden from the nav and is linked from the Manual Cancellation flow in Transaction Lifecycle.

🤖 Generated with Claude Code

The 006 and 008 sandbox suffixes simulate manual cancellations. They now
live on a separate Sandbox Manual Cancellations page, linked from the
Manual Cancellation flow in Transaction Lifecycle, and no longer appear
in the main quote suffix table.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@vercel

vercel Bot commented Oct 16, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

3 Skipped Deployments
Project Deployment Actions Updated
grid-cards-demo Ignored Ignored Preview Oct 16, 2026 5:24pm UTC
grid-flow-builder Ignored Ignored Preview Oct 16, 2026 5:24pm UTC
grid-wallet-demo Ignored Ignored Preview Oct 16, 2026 5:24pm UTC

Request Review

@mintlify

mintlify Bot commented Oct 16, 2026 •

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
Grid 🟢 Ready View Preview Oct 16, 2026, 5:25 PM

Copy link
Copy Markdown
Contributor Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

@JasonCWang
JasonCWang marked this pull request as ready for review October 16, 2026 18:44
@JasonCWang
JasonCWang merged commit 4589131 into main Oct 16, 2026
9 checks passed
@JasonCWang
JasonCWang deleted the jw/sandbox-ops-cancellations branch October 16, 2026 18:44
@greptile-apps

greptile-apps Bot commented Oct 16, 2026 •

Copy link
Copy Markdown
Contributor

RetriggerView in GreptileConfidence Score: 4/5

[Low impact] The changes affect sandbox documentation for payment developers.

The PR appears safe to merge, with a non-blocking correction needed to the sandbox fallback descriptions.

Findings

  1. P2 Unlisted endings can trigger refunds ▶
Fix with agent prompt
### Issue 1
mintlify/ramps/platform-tools/sandbox-testing.mdx:237
Removing `006` and `008` makes “Any other ending succeeds normally” incorrect. Both endings still trigger refunds, as the new page explains. The shared quote table also labels unlisted endings as successful payments. Developers choosing an unlisted suffix for a normal sandbox payout can therefore trigger a cancellation instead. Exclude these endings from both fallback descriptions without restoring them to the main table.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

Moves sandbox cancellation endings 006 and 008 to a hidden page linked from the Manual Cancellation flow.

  • Sandbox cancellation suffixes have their own guide linked from the payment flow.

Reviews (1) · Last reviewed commit: "docs(sandbox): move the manual cancellat..." · Reviewed by Greptile


<Note>
In sandbox, you can use special account number patterns to test different scenarios. The **last 3 digits** determine the behavior, and the meaning depends on how the account is used. This account is the destination of the off-ramp quote below, so the quote patterns apply: **002** (quote execution failed), **003** (long payment), **004** (counterparty delivery failed), **005** (receiving bank returned the payment), **006** (user cancellation), **007** (payout and refund failed), **008** (user cancellation while processing). Any other ending succeeds normally. See "Quote destination test patterns" below for the full table.
In sandbox, you can use special account number patterns to test different scenarios. The **last 3 digits** determine the behavior, and the meaning depends on how the account is used. This account is the destination of the off-ramp quote below, so the quote patterns apply: **002** (quote execution failed), **003** (long payment), **004** (counterparty delivery failed), **005** (receiving bank returned the payment), **007** (payout and refund failed). Any other ending succeeds normally. See "Quote destination test patterns" below for the full table.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Unlisted endings can trigger refunds

Removing 006 and 008 makes “Any other ending succeeds normally” incorrect. Both endings still trigger refunds, as the new page explains. The shared quote table also labels unlisted endings as successful payments. Developers choosing an unlisted suffix for a normal sandbox payout can therefore trigger a cancellation instead. Exclude these endings from both fallback descriptions without restoring them to the main table.

Prompt To Fix With AI
This is a comment left during a code review.
Path: mintlify/ramps/platform-tools/sandbox-testing.mdx
Line: 237

Comment:
**Unlisted endings can trigger refunds**

Removing `006` and `008` makes “Any other ending succeeds normally” incorrect. Both endings still trigger refunds, as the new page explains. The shared quote table also labels unlisted endings as successful payments. Developers choosing an unlisted suffix for a normal sandbox payout can therefore trigger a cancellation instead. Exclude these endings from both fallback descriptions without restoring them to the main table.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

This branch was successfully deployed

1 active deployment
staging - mintlify — 91fdf0b3 Deployed Oct 16, 2026 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants