docs: update crypto wallet beneficiary documentation for Travel Rule - #839
docs: update crypto wallet beneficiary documentation for Travel Rule#839claude[bot] wants to merge 1 commit into
Conversation
Update documentation to reflect that crypto wallet external accounts now support optional beneficiary information for Travel Rule compliance: - First-party wallets (customer's self-custody) don't require beneficiary info—Grid uses the customer's verified identity - Third-party wallets on platforms with Travel Rule requirements (e.g. EU) must include a beneficiary object with beneficiaryType, fullName, and countryOfResidence This syncs the docs with schema changes in commit 3ad6a07. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
|
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
|
Greptile SummaryUpdates crypto-wallet external-account documentation to explain when Travel Rule beneficiary information is optional or required.
Confidence Score: 4/5The beneficiary field guidance should be corrected before merging because business beneficiaries following it will construct an invalid request. The shared note treats individual beneficiary fields as universal despite the API’s distinct business-beneficiary schema, while the on-ramp summary also drops a relevant third-party qualification. Files Needing Attention: mintlify/snippets/external-accounts.mdx; mintlify/ramps/accounts/external-accounts.mdx
|
| Filename | Overview |
|---|---|
| mintlify/snippets/external-accounts.mdx | Adds detailed Travel Rule guidance, but incorrectly prescribes individual-only fields for business beneficiaries. |
| mintlify/ramps/accounts/external-accounts.mdx | Updates on-ramp beneficiary messaging, with one summary bullet omitting the third-party exception stated elsewhere on the page. |
Prompt To Fix All With AI
### Issue 1
mintlify/snippets/external-accounts.mdx:1825-1826
**Business beneficiary fields are wrong**
When the third-party beneficiary is a business, this guidance prescribes the individual-only `fullName` and `countryOfResidence` fields instead of the required `legalName`, causing customers following the documentation to submit an invalid beneficiary object.
### Issue 2
mintlify/ramps/accounts/external-accounts.mdx:288
**Summary omits third-party exception**
This general on-ramp summary describes beneficiary information as optional without the third-party Travel Rule exception included earlier on the page, leaving readers who use this section as a quick reference with incomplete compliance guidance.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.Reviews (1): Last reviewed commit: "docs: update crypto wallet beneficiary d..." | Re-trigger Greptile
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| platforms with Travel Rule requirements (e.g. EU) must include a `beneficiary` | ||
| object with `beneficiaryType`, `fullName`, and `countryOfResidence`. Send only |
There was a problem hiding this comment.
When the third-party beneficiary is a business, this guidance prescribes the individual-only fullName and countryOfResidence fields instead of the required legalName, causing customers following the documentation to submit an invalid beneficiary object.
Prompt To Fix With AI
This is a comment left during a code review.
Path: mintlify/snippets/external-accounts.mdx
Line: 1825-1826
Comment:
**Business beneficiary fields are wrong**
When the third-party beneficiary is a business, this guidance prescribes the individual-only `fullName` and `countryOfResidence` fields instead of the required `legalName`, causing customers following the documentation to submit an invalid beneficiary object.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.|
|
||
| - **Instant delivery**: Spark wallets receive Bitcoin within seconds | ||
| - **No KYC required**: Self-custody wallets don't need beneficiary info | ||
| - **Beneficiary optional**: First-party wallets use the customer's verified identity |
There was a problem hiding this comment.
This general on-ramp summary describes beneficiary information as optional without the third-party Travel Rule exception included earlier on the page, leaving readers who use this section as a quick reference with incomplete compliance guidance.
Knowledge Base Used: Mintlify Documentation Site
Prompt To Fix With AI
This is a comment left during a code review.
Path: mintlify/ramps/accounts/external-accounts.mdx
Line: 288
Comment:
**Summary omits third-party exception**
This general on-ramp summary describes beneficiary information as optional without the third-party Travel Rule exception included earlier on the page, leaving readers who use this section as a quick reference with incomplete compliance guidance.
**Knowledge Base Used:** [Mintlify Documentation Site](https://app.greptile.com/lightspark/-/custom-context/knowledge-base/lightsparkdev/grid-api/-/docs/mintlify-docs-site.md)
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
Summary
Changes
Documentation (2 files):
mintlify/snippets/external-accounts.mdx- Updated Cryptocurrency tab notemintlify/ramps/accounts/external-accounts.mdx- Updated on-ramp destination bulletsContext
This syncs documentation with schema changes in commit 3ad6a07 which added the
beneficiaryfield toWalletBeneficiaryFields.yamlfor crypto wallet external accounts.Test plan
make lint- passes with only pre-existing warnings🤖 Generated with Claude Code