Skip to content

docs: update crypto wallet beneficiary documentation for Travel Rule #839

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
claude wants to merge 1 commit into
base: main
Choose a base branch
from
+8 −5
Open

docs: update crypto wallet beneficiary documentation for Travel Rule #839

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions mintlify/ramps/accounts/external-accounts.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ External accounts represent crypto wallet destinations:

- **Spark wallets**: Lightning Network wallets for instant Bitcoin delivery
- **Self-custody**: User-controlled wallets for full ownership
- **No beneficiary required**: Crypto wallets don't need compliance information
- **Beneficiary optional**: First-party wallets use the customer's verified identity; third-party wallets may require beneficiary info for Travel Rule compliance

<Tip>
Spark wallets are the recommended destination for on-ramps due to instant
Expand Down Expand Up @@ -285,7 +285,7 @@ if (await verifySparkWallet(sparkAddress)) {
### On-ramp destinations

- **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

@greptile-apps greptile-apps Bot Aug 15, 2026

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

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!

- **Reusable addresses**: Store and reuse Spark addresses for multiple conversions
- **No minimum**: Send any amount supported by Lightning Network

Expand Down
9 changes: 6 additions & 3 deletions mintlify/snippets/external-accounts.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1820,9 +1820,12 @@ curl -X POST 'https://api.lightspark.com/grid/2025-10-13/customers/external-acco
}'
```
<Note>
Crypto wallets don't require beneficiary information. Send only assets on the
named network — EVM addresses look identical across Ethereum, Base, Polygon and
Plasma, and funds sent on the wrong network are unrecoverable.
First-party crypto wallets (customer's own self-custody) don't require beneficiary
information—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`. Send only
Comment on lines +1825 to +1826

@greptile-apps greptile-apps Bot Aug 15, 2026

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.

P1 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.

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.

assets on the named network—EVM addresses look identical across Ethereum, Base,
Polygon, and Plasma, and funds sent on the wrong network are unrecoverable.
</Note>
</Tab>
</Tabs>
Expand Down
Loading