Skip to content

docs: add a required fields by corridor page - #872

Merged
JasonCWang merged 1 commit into
mainfrom
docs/corridor-required-fields
Aug 28, 2026
Merged

docs: add a required fields by corridor page#872
JasonCWang merged 1 commit into
mainfrom
docs/corridor-required-fields

Conversation

@JasonCWang

@JasonCWang JasonCWang commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

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

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
@mintlify

mintlify Bot commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

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

Project Status Preview Updated (UTC)
Grid 🟢 Ready View Preview Aug 27, 2026, 11:07 PM

@vercel

vercel Bot commented Aug 27, 2026

Copy link
Copy Markdown

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

2 Skipped Deployments
Project Deployment Actions Updated (UTC)
grid-flow-builder Ignored Ignored Preview Aug 27, 2026 11:05pm
grid-wallet-demo Ignored Ignored Preview Aug 27, 2026 11:05pm

Request Review

@JasonCWang

Copy link
Copy Markdown
Contributor Author

@greptile review

@greptile-apps

greptile-apps Bot commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

Adds a documentation page that presents required sender and recipient account fields by corridor.

  • Adds generated corridor data covering currencies, payment rails, and account-type combinations.
  • Adds sender, recipient, and currency filter controls with supporting styles and client-side behavior.
  • Registers the page under Payouts & B2B account management.

Confidence Score: 5/5

The PR appears safe to merge because no blocking failure remains within the eligible follow-up review scope.

No blocking failure remains.

Important Files Changed

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
JasonCWang marked this pull request as ready for review August 28, 2026 17:26
@JasonCWang
JasonCWang merged commit 03dbbb7 into main Aug 28, 2026
10 checks passed
@JasonCWang
JasonCWang deleted the docs/corridor-required-fields branch August 28, 2026 22:07
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