docs: add end-user terms disclosures guide; link refund policy in receipts#579
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Greptile SummaryThis PR adds a new "Disclosures" onboarding page for unregulated platforms, explaining the requirement to present Lightspark's End User Terms and collect consent before launch, and updates the receipts snippet to hyperlink the refund policy.
Confidence Score: 4/5The disclosures page describes a mandatory pre-launch compliance step but does not tell developers where to send evidence of their consent flow, leaving the action incomplete. The disclosures page instructs platforms to send evidence to Lightspark before launch but provides no submission channel, email, or portal link. A developer following the guide exactly cannot complete the required step without going off-docs to find a contact. This is a real gap in compliance-critical documentation. mintlify/payouts-and-b2b/onboarding/disclosures.mdx — the 'Provide evidence' section needs a concrete submission destination before this page is ready for developer-facing use.
|
| Filename | Overview |
|---|---|
| mintlify/payouts-and-b2b/onboarding/disclosures.mdx | New compliance page for unregulated platforms; instructs evidence submission but omits any contact channel or submission destination, leaving the mandatory pre-launch step incomplete. |
| mintlify/snippets/receipts.mdx | Refund policy copy updated to hyperlink a support article; both the visual example and the reference table now point to a /categories/ URL (flagged in a previous thread) rather than a specific article URL. |
| mintlify/docs.json | Adds disclosures to the Onboarding nav group; no structural issues. |
Flowchart
%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[Platform onboards] --> B[Copy Lightspark End User Terms\nand append own ToS]
B --> C[Present combined terms in\nonboarding / consent flow]
C --> D{End user\naffirmatively accepts?}
D -- No --> C
D -- Yes --> E[Record consent\nuser ID · timestamp · terms version]
E --> F[Capture screenshot\nof consent screen]
F --> G[Send evidence to Lightspark\n⚠️ destination not specified in docs]
G --> H{Lightspark\napproval?}
H -- Pending --> G
H -- Approved --> I[Make Grid available\nto end users]
Reviews (2): Last reviewed commit: "docs: add end-user terms disclosures gui..." | Re-trigger Greptile
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| <div> | ||
| <div style={secLabelMb}>Refund Policy</div> | ||
| <p style={{ margin: 0 }}>You may cancel for a full refund within 30 minutes of payment, unless the funds have already been picked up or deposited. Refund requests can be made at www.lightspark.com/refunds or by calling the number above.</p> | ||
| <p style={{ margin: 0 }}>You may cancel for a full refund within 30 minutes of payment, unless the funds have already been picked up or deposited. See the <a href="https://support.lightspark.com/hc/en-us/categories/51347651720859-Cards" style={{ color: '#1a1a1a', fontWeight: 450 }}>refund policy</a> or call the number above.</p> |
There was a problem hiding this comment.
The updated href https://support.lightspark.com/hc/en-us/categories/51347651720859-Cards is a Zendesk category URL (indicated by the /categories/ path segment) named "Cards", not a specific refund policy article URL (which would be /articles/{id}-{name}). A customer clicking "refund policy" would land on a category index page rather than the actual refund policy content. Because this is regulatory-required information on every receipt, a broken or misdirected link is a compliance gap. Verify the link resolves to the exact refund policy article and use the article-level URL (e.g. /hc/en-us/articles/...) instead.
Prompt To Fix With AI
This is a comment left during a code review.
Path: mintlify/snippets/receipts.mdx
Line: 114
Comment:
**Refund policy URL points to a category listing, not an article**
The updated href `https://support.lightspark.com/hc/en-us/categories/51347651720859-Cards` is a Zendesk *category* URL (indicated by the `/categories/` path segment) named "Cards", not a specific refund policy article URL (which would be `/articles/{id}-{name}`). A customer clicking "refund policy" would land on a category index page rather than the actual refund policy content. Because this is regulatory-required information on every receipt, a broken or misdirected link is a compliance gap. Verify the link resolves to the exact refund policy article and use the article-level URL (e.g. `/hc/en-us/articles/...`) instead.
How can I resolve this? If you propose a fix, please make it concise.| | Customer service phone | (855) 516-0103 | | ||
| | Fraud reporting | "To report fraud or suspected fraud in connection with the money transmission services, please call customer services toll-free at (855) 516-0103." | | ||
| | Refund policy | Lightspark's refund policy for transmitted funds (link or full text). | | ||
| | Refund policy | Link to Lightspark's refund policy: https://support.lightspark.com/hc/en-us/categories/51347651720859-Cards | |
There was a problem hiding this comment.
The plain-text URL in the "Lightspark regulatory disclosures" table — https://support.lightspark.com/hc/en-us/categories/51347651720859-Cards — has the same /categories/ path issue as the receipt HTML snippet above. Both the visual example and the implementation reference table should point to the specific article URL once it is confirmed.
Prompt To Fix With AI
This is a comment left during a code review.
Path: mintlify/snippets/receipts.mdx
Line: 167
Comment:
**Same category URL used in the reference table**
The plain-text URL in the "Lightspark regulatory disclosures" table — `https://support.lightspark.com/hc/en-us/categories/51347651720859-Cards` — has the same `/categories/` path issue as the receipt HTML snippet above. Both the visual example and the implementation reference table should point to the specific article URL once it is confirmed.
How can I resolve this? If you propose a fix, please make it concise.
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
…eipts Add a B2B onboarding "Disclosures" page instructing unregulated platforms to expose Lightspark's End User Terms and provide evidence of their consent flow. Update the receipts snippet to link the refund policy support article. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
pengying
force-pushed
the
06-12-docs_add_end-user_terms_disclosures_guide_link_refund_policy_in_receipts
branch
from
968129b to
09dc78f
Compare
1 participant
Add a B2B onboarding "Disclosures" page instructing unregulated platforms to
expose Lightspark's End User Terms and provide evidence of their consent flow.
Update the receipts snippet to link the refund policy support article.
Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com