Conversation
✱ Stainless preview buildsThis PR will update the kotlin openapi python typescript ✅ grid-kotlin studio · code
|
e807c55 to
8ef3a80
Compare
Greptile SummaryThis PR centralizes sandbox test case documentation by extracting duplicated inline patterns from OpenAPI descriptions and product-specific sandbox pages into a set of reusable Mintlify snippets, and adds a new top-level Key changes:
Confidence Score: 4/5
|
| Filename | Overview |
|---|---|
| mintlify/api-reference/sandbox-testing.mdx | New centralized sandbox testing page for the API reference; imports and composes all shared snippets correctly. |
| mintlify/ramps/platform-tools/sandbox-testing.mdx | Fixes credential variable name (SANDBOX_API_KEY → SANDBOX_CLIENT_ID) throughout; replaces inline account-pattern tables with shared snippets, but omits SandboxQuotePatterns from the cross-currency quotes section while the equivalent payouts page includes it. |
| mintlify/payouts-and-b2b/platform-tools/sandbox-testing.mdx | Refactored to use shared snippets; correctly includes SandboxQuotePatterns in the cross-currency quotes section, and fixes inline comment accuracy (003 = slow payment, not account closed). |
| mintlify/snippets/sandbox-quote-patterns.mdx | New snippet defining quote-specific test patterns, which differ from transfer patterns for the same suffixes (e.g., 003 = slow payment vs account closed in transfers). |
| mintlify/snippets/sandbox-transfer-patterns.mdx | New snippet with the transfer-level test patterns table; standardizes on suffix 005 for timeout, resolving a prior inconsistency where 009 was mentioned in one section. |
| mintlify/snippets/sandbox-beneficiary-verification.mdx | Replaces the INR/UPI-specific sandbox-vpa-validation.mdx with a generalized beneficiary verification snippet applicable to all account types that support the feature. |
| mintlify/snippets/sandbox-vpa-validation.mdx | Deleted; replaced by the more general sandbox-beneficiary-verification.mdx snippet. |
| openapi/paths/customers/customers_external_accounts.yaml | Removed inline sandbox testing documentation from the endpoint description; now points to the dedicated sandbox testing guide. |
| openapi/paths/platform/platform_external_accounts.yaml | Same cleanup as customers_external_accounts.yaml — inline sandbox patterns removed from the platform external accounts POST description. |
| openapi/paths/quotes/quotes.yaml | Removed inline sandbox testing patterns from the quotes POST description; reference updated to the new sandbox testing guide. |
Flowchart
%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[Sandbox Testing Content] --> B[api-reference/sandbox-testing.mdx\nnew canonical page]
A --> C[payouts-and-b2b/platform-tools/sandbox-testing.mdx]
A --> D[ramps/platform-tools/sandbox-testing.mdx]
B --> S1[sandbox-external-accounts.mdx]
B --> S2[sandbox-beneficiary-verification.mdx]
B --> S3[sandbox-transfer-patterns.mdx]
B --> S4[sandbox-quote-patterns.mdx]
B --> S5[sandbox-uma-addresses.mdx]
C --> S1
C --> S2
C --> S3
C --> S4
D --> S1
D --> S2
D --> S3
D -. missing .-> S4
E[sandbox-vpa-validation.mdx\ndeleted] -. replaced by .-> S2
style D fill:#ffe0e0
style S4 fill:#ffe0e0
Comments Outside Diff (1)
-
mintlify/ramps/platform-tools/sandbox-testing.mdx, line 326 (link)Missing
SandboxQuotePatternsin ramps quote testingThe ramps page has a "Failed conversions" section that walks through off-ramp quote testing (e.g., suffix
002for insufficient funds), but the quote-specific pattern table (sandbox-quote-patterns.mdx) is never imported or included here. This matters because quote patterns behave differently than transfer patterns for the same suffixes:- Suffix
003in transfer →Account closed/invalid — transfer fails immediately - Suffix
003in quote →Long payment — completes after approximately 6 minutes
The payouts sandbox page correctly includes
<SandboxQuotePatterns />before its "Creating Quotes with Test Accounts" section. The ramps page is missing the equivalent, so ramps users will only see transfer patterns and may be confused when quote results don't match expectations.Consider adding the import and snippet to the ramps page in the same way it was added to the payouts page:
import SandboxQuotePatterns from '/snippets/sandbox-quote-patterns.mdx';And placing
<SandboxQuotePatterns />in the cross-currency quotes section. - Suffix
Prompt To Fix All With AI
This is a comment left during a code review.
Path: mintlify/ramps/platform-tools/sandbox-testing.mdx
Line: 326
Comment:
**Missing `SandboxQuotePatterns` in ramps quote testing**
The ramps page has a "Failed conversions" section that walks through off-ramp quote testing (e.g., suffix `002` for insufficient funds), but the quote-specific pattern table (`sandbox-quote-patterns.mdx`) is never imported or included here. This matters because quote patterns behave differently than transfer patterns for the same suffixes:
- Suffix `003` in **transfer** → `Account closed/invalid — transfer fails immediately`
- Suffix `003` in **quote** → `Long payment — completes after approximately 6 minutes`
The payouts sandbox page correctly includes `<SandboxQuotePatterns />` before its "Creating Quotes with Test Accounts" section. The ramps page is missing the equivalent, so ramps users will only see transfer patterns and may be confused when quote results don't match expectations.
Consider adding the import and snippet to the ramps page in the same way it was added to the payouts page:
```
import SandboxQuotePatterns from '/snippets/sandbox-quote-patterns.mdx';
```
And placing `<SandboxQuotePatterns />` in the cross-currency quotes section.
How can I resolve this? If you propose a fix, please make it concise.Last reviewed commit: fa378c3
8ef3a80 to
1bc74a0
Compare
| @@ -0,0 +1 @@ | |||
| The flows for creating external accounts in sandbox are the same as in production. The **last 3 digits** of an external account's primary identifier (account number, IBAN, CLABE, Spark wallet address, etc.) determine the test scenario when that account is used in transfers or quotes. For identifiers with a domain part (e.g. PIX email keys), append the test digits to the username portion — for example, `testuser.002@pix.com.br`. | |||
There was a problem hiding this comment.
is this hard to manage on our side? Or is the logic just split('@')[0][-3:]
1bc74a0 to
fa378c3
Compare
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|

No description provided.