Skip to content

docs: add Global Accounts tab#403

Open
patcapulong wants to merge 2 commits intomainfrom
pat/add-new-tab
Open

docs: add Global Accounts tab#403
patcapulong wants to merge 2 commits intomainfrom
pat/add-new-tab

Conversation

@patcapulong
Copy link
Copy Markdown
Contributor

Summary

  • Add a top-level Global Accounts docs tab with product-to-API mapping and implementation guides.
  • Keep Embedded Wallets as the technical primitive in Payouts & B2B while removing duplicate Embedded Wallet sidebar groups from other flow tabs.
  • Add Global Accounts hero and OG assets, including compressed WebP versions.

Test plan

  • ./node_modules/.bin/markdownlint \"mintlify/global-accounts/*.mdx\"
  • make lint
  • Local Mintlify preview at http://localhost:3001/global-accounts

Made with Cursor

Add a product-level Global Accounts docs section while keeping Embedded Wallets available as the underlying technical primitive.

Made-with: Cursor
@vercel
Copy link
Copy Markdown

vercel Bot commented Apr 27, 2026

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

Project Deployment Actions Updated (UTC)
grid-flow-builder Ready Ready Preview, Comment Apr 27, 2026 10:23pm

Request Review

@mintlify
Copy link
Copy Markdown
Contributor

mintlify Bot commented Apr 27, 2026

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

Project Status Preview Updated (UTC)
Grid 🟢 Ready View Preview Apr 27, 2026, 9:37 PM

@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps Bot commented Apr 27, 2026

Greptile Summary

Adds a new top-level Global Accounts documentation tab with 14 MDX pages covering the full integration lifecycle (overview, quickstart, account setup, security, and platform tools), hero/OG image assets, and removes the now-redundant Embedded Wallets sidebar groups from the Ramps, Rewards, and Global P2P tabs. All pages have correct frontmatter, og:image properties, language-tagged code blocks, and alt text on images.

Confidence Score: 4/5

Safe to merge — documentation-only changes with no code logic; only minor content completeness gaps.

Only P2 findings: the quickstart step 3 lacks an inline sandbox credential example, and the Postman collection page omits the import URL. No broken links, missing frontmatter, or structural issues found.

mintlify/global-accounts/quickstart.mdx and mintlify/global-accounts/postman-collection.mdx have minor content gaps worth addressing before developer-facing launch.

Important Files Changed

Filename Overview
mintlify/docs.json Adds Global Accounts tab with 4 groups; removes duplicate Embedded Wallets sidebar groups from Ramps, Rewards, and Global P2P tabs — clean structural change.
mintlify/global-accounts/index.mdx Landing page with hero image, feature cards, and capability overview; has correct frontmatter, alt text, and OG image.
mintlify/global-accounts/quickstart.mdx 8-step end-to-end sandbox walkthrough; Step 3 (Register a credential) defers entirely to another doc with no code example or sandbox shortcut, leaving the flow incomplete at a critical point.
mintlify/global-accounts/implementation-overview.mdx Object model table and core flow numbered list; well-structured and complete.
mintlify/global-accounts/authentication.mdx Summarises authentication credential types, session pattern, and sandbox shortcuts; delegates full examples to Embedded Wallets docs.
mintlify/global-accounts/withdrawals.mdx Withdrawal flow with quote creation and signed execute examples; includes production warning about payload signing.
mintlify/global-accounts/customers.mdx Covers customer types, account provisioning, and compliance requirements with appropriate Warning callout.
mintlify/global-accounts/funding.mdx Explains funding model, sandbox endpoint, and quote-based funding with correct code blocks.
mintlify/global-accounts/client-keys.mdx Explains client key security model and signing responsibilities; defers to Embedded Wallets for technical detail.
mintlify/global-accounts/exporting-wallet.mdx Describes export flow at a high level with security Warning; delegates full endpoint detail to Embedded Wallets docs.
mintlify/global-accounts/managing-sessions.mdx Covers session lifecycle, use cases, and revocation pattern; correctly delegates to Embedded Wallets technical reference.
mintlify/global-accounts/webhooks.mdx Documents webhook tracking events and idempotent processing pattern for Global Accounts.
mintlify/global-accounts/sandbox-testing.mdx Sandbox behavior and suggested test path with sandbox-specific shortcuts documented clearly.
mintlify/global-accounts/postman-collection.mdx Setup guide for Postman collection with environment variable instructions; missing the actual collection import URL/button.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Create Customer] --> B[Find Global Account\ntype=EMBEDDED_WALLET]
    B --> C[Register Credential\nPasskey / OAuth / Email OTP]
    C --> D[Fund Account\nSandbox endpoint or quote]
    D --> E[Create Withdrawal Destination\nExternalAccount]
    E --> F[Create Quote\nsource=GlobalAccount\ndest=ExternalAccount]
    F --> G{Requires signature?}
    G -->|Yes| H[Authenticate Customer\nGet Session Signing Key]
    H --> I[Sign payloadToSign]
    I --> J[Execute Quote\nGrid-Wallet-Signature header]
    G -->|No| J
    J --> K[Reconcile via\nTransaction Webhooks]
Loading

Fix All in Claude Code

Prompt To Fix All With AI
This is a comment left during a code review.
Path: mintlify/global-accounts/quickstart.mdx
Line: 71-75

Comment:
**Quickstart Step 3 skips sandbox credential registration**

Step 3 defers entirely to the Authentication doc without providing a minimal sandbox example. Since the quickstart promises "an end-to-end sandbox flow" and Step 7 (sign and execute) depends on having a registered credential and session, a developer following this guide will get blocked here before they can proceed. Even a brief inline sandbox shortcut — such as showing the email OTP registration path with `000000` — would let the flow stay self-contained for sandbox purposes.

**Context Used:** mintlify/AGENTS.md ([source](https://app.greptile.com/review/custom-context?memory=51934046-75fb-42d3-9870-f42d61cb60e3))

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: mintlify/global-accounts/postman-collection.mdx
Line: 13-14

Comment:
**No link or import URL for the Postman collection**

Step 1 says "Import the Grid Postman collection" but doesn't give the collection URL, a Run in Postman button, or a link to where it lives. Without this, the setup instructions are incomplete — developers have no way to follow Step 1. The parallel Payouts & B2B postman page (linked at the bottom) may show the expected pattern.

**Context Used:** mintlify/AGENTS.md ([source](https://app.greptile.com/review/custom-context?memory=51934046-75fb-42d3-9870-f42d61cb60e3))

How can I resolve this? If you propose a fix, please make it concise.

Reviews (1): Last reviewed commit: "docs: add Global Accounts tab" | Re-trigger Greptile

Comment on lines +71 to +75

```bash
curl -X POST "$GRID_BASE_URL/sandbox/internal-accounts/InternalAccount:019542f5-b3e7-1d02-0000-000000000002/fund" \
-u "$GRID_CLIENT_ID:$GRID_CLIENT_SECRET" \
-H "Content-Type: application/json" \
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 Quickstart Step 3 skips sandbox credential registration

Step 3 defers entirely to the Authentication doc without providing a minimal sandbox example. Since the quickstart promises "an end-to-end sandbox flow" and Step 7 (sign and execute) depends on having a registered credential and session, a developer following this guide will get blocked here before they can proceed. Even a brief inline sandbox shortcut — such as showing the email OTP registration path with 000000 — would let the flow stay self-contained for sandbox purposes.

Context Used: mintlify/AGENTS.md (source)

Prompt To Fix With AI
This is a comment left during a code review.
Path: mintlify/global-accounts/quickstart.mdx
Line: 71-75

Comment:
**Quickstart Step 3 skips sandbox credential registration**

Step 3 defers entirely to the Authentication doc without providing a minimal sandbox example. Since the quickstart promises "an end-to-end sandbox flow" and Step 7 (sign and execute) depends on having a registered credential and session, a developer following this guide will get blocked here before they can proceed. Even a brief inline sandbox shortcut — such as showing the email OTP registration path with `000000` — would let the flow stay self-contained for sandbox purposes.

**Context Used:** mintlify/AGENTS.md ([source](https://app.greptile.com/review/custom-context?memory=51934046-75fb-42d3-9870-f42d61cb60e3))

How can I resolve this? If you propose a fix, please make it concise.

Fix in Claude Code

Comment on lines +13 to +14

1. Import the Grid Postman collection.
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 No link or import URL for the Postman collection

Step 1 says "Import the Grid Postman collection" but doesn't give the collection URL, a Run in Postman button, or a link to where it lives. Without this, the setup instructions are incomplete — developers have no way to follow Step 1. The parallel Payouts & B2B postman page (linked at the bottom) may show the expected pattern.

Context Used: mintlify/AGENTS.md (source)

Prompt To Fix With AI
This is a comment left during a code review.
Path: mintlify/global-accounts/postman-collection.mdx
Line: 13-14

Comment:
**No link or import URL for the Postman collection**

Step 1 says "Import the Grid Postman collection" but doesn't give the collection URL, a Run in Postman button, or a link to where it lives. Without this, the setup instructions are incomplete — developers have no way to follow Step 1. The parallel Payouts & B2B postman page (linked at the bottom) may show the expected pattern.

**Context Used:** mintlify/AGENTS.md ([source](https://app.greptile.com/review/custom-context?memory=51934046-75fb-42d3-9870-f42d61cb60e3))

How can I resolve this? If you propose a fix, please make it concise.

Fix in Claude Code

Copy link
Copy Markdown
Contributor

@pengying pengying left a comment

Choose a reason for hiding this comment

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

some changes


## 3. Register a credential

Outbound movement from a Global Account requires customer authorization. Register a credential such as a passkey, OAuth credential, or email OTP.
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.

ask claude to reuse the passkey auth snippet

---

Client keys bind a signed Global Account action to the customer's current device.

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.

pull more from the current keys docs


The current API calls this area `Embedded Wallet Auth` because Global Accounts are powered by the embedded wallet account primitive.

## Supported credential types
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.

this is not enough either needs to pull more from the current auth docs

@@ -0,0 +1,40 @@
---
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.

a lot of these sections don't contain enough information for an actual implementation, ask claude to review the other business lines

Use the InternalAccount ID prefix in Embedded Wallet auth examples so they match the API contract and Global Accounts docs.

Made-with: Cursor
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