Uh oh!
There was an error while loading. Please reload this page.
docs: add a required fields by corridor page - #872
Merged
Conversation
Adds a page under Payouts & B2B > Managing accounts that lists, for every currency and payment rail, the details the sender and the recipient's account must supply. Readers filter by sender type, recipient type, and currency. The table itself is generated upstream from the payment integrations and arrives through the existing schema sync, so it stays current as corridors change. This PR carries the first copy so the page renders. Hand-written pieces: - payouts-and-b2b/depositing-funds/required-fields.mdx, the page that includes the snippet - corridor-fields.js, the filter behaviour - style.css, the filter bar and empty state, using the existing ls tokens - docs.json, one navigation entry
Contributor
Preview deployment for your docs. Learn more about Mintlify Previews.
|
The latest updates on your projects. Learn more about Vercel for GitHub. 2 Skipped Deployments
|
JasonCWang
commented
Aug 27, 2026
ContributorAuthor
@greptile review |
Contributor
Greptile SummaryAdds a documentation page that presents required sender and recipient account fields by corridor.
Confidence Score: 5/5The PR appears safe to merge because no blocking failure remains within the eligible follow-up review scope. No blocking failure remains.
|
| Filename | Overview |
|---|---|
| mintlify/corridor-fields.js | Adds delegated client-side filtering and empty-state handling for corridor rows. |
| mintlify/snippets/corridor-required-fields.mdx | Adds the generated corridor requirements table and its filter controls. |
| mintlify/payouts-and-b2b/depositing-funds/required-fields.mdx | Adds the documentation page that renders the generated corridor snippet. |
| mintlify/docs.json | Adds the required-fields page to the Managing accounts navigation group. |
| mintlify/style.css | Adds responsive filter, table, hidden-state, empty-state, and dark-mode styling. |
Reviews (2): Last reviewed commit: "docs: add a required fields by corridor ..." | Re-trigger Greptile
JasonCWang
marked this pull request as ready for review
August 28, 2026 17:26
AaryamanBhute
approved these changes
Aug 28, 2026
Uh oh!
There was an error while loading. Please reload this page.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a page under Payouts & B2B > Managing accounts that lists, for every
currency and payment rail, the details the sender and the recipient's account
must supply. Readers filter by sender type, recipient type, and currency.
The table itself is generated upstream from the payment integrations and
arrives through the existing schema sync, so it stays current as corridors
change. This PR carries the first copy so the page renders.
Hand-written pieces:
the snippet