diff --git a/ui/app/(marketing)/docs/page.tsx b/ui/app/(marketing)/docs/page.tsx index 2e0aeff..95cafb9 100644 --- a/ui/app/(marketing)/docs/page.tsx +++ b/ui/app/(marketing)/docs/page.tsx @@ -536,7 +536,7 @@ export default function DocsPage() {
xmrcheckout.com generates invoices, detects Monero payments using view-only access, - and relays status events. Setup is simple: bring your primary address and secret + and relays status events. Setup is explicit: bring your primary address and secret view key - never spend keys, never custody.
- Setup is simple and explicit: provide your primary address and secret - view key, then create invoices via the dashboard or API. We never - request spend keys or signing access. -
- > - ), - }, + { + question: "What does setup require?", + answer: ( + <> ++ Setup is explicit: provide your primary address and secret + view key, then create invoices via the dashboard or API. We never + request spend keys or signing access. +
+ > + ), + }, { question: "Do you require email or personal information?", answer: ( @@ -85,27 +85,26 @@ const faqItems: FaqItem[] = [ > ), }, - { - question: "Why is XMR Checkout free?", - answer: ( - <> -- We want to give back to the Monero community and help improve - adoption. XMR Checkout is intentionally offered as free checkout - software. -
- {donationsEnabled ? ( -- If you find XMR Checkout useful, we happily accept{" "} - - donations - - . -
- ) : null} - > - ), - }, + { + question: "What does XMR Checkout cost?", + answer: ( + <> ++ Currently, xmrcheckout.com does not charge a service fee. You can also self-host the open source + stack if you prefer. +
+ {donationsEnabled ? ( ++ If you find XMR Checkout useful, you can support development with{" "} + + donations + + . +
+ ) : null} + > + ), + }, { question: "Can XMR Checkout move funds, issue refunds, or reverse payments?", answer: ( @@ -131,30 +130,26 @@ const faqItems: FaqItem[] = [ > ), }, - { - question: "Why choose XMR Checkout instead of hosted services (e.g. NOWPayments)?", - answer: ( - <> -- The main differences are scope and data collection: XMR Checkout is - Monero-only, has no fees, and does not collect personal information. -
-+ The main differences are scope, custody model, and data collection: XMR Checkout is Monero-only, + does not require an account or email, and uses view-only access for payment detection. +
+- If you prefer a third-party hosted flow for convenience, compare - providers carefully and choose what matches your risk tolerance and - operational needs. -
- > - ), - }, - { - question: "Why choose XMR Checkout instead of BTCPay Server?", - answer: ( - <> -- BTCPay Server is a strong self-hosted option, with a primary focus on - Bitcoin (including the Lightning Network) and optional integrations - for other assets (including Monero via a plugin). XMR Checkout is - intentionally focused on Monero checkout with a view-only trust - boundary and a minimal, deterministic core. -
-- BTCPay Server configuration can be difficult, and while hosted - BTCPay options exist, they are often not configured with the Monero - plugin. For that reason we provide a basic (greenfield) integration - layer so teams can accept Monero without the requirement of - self-hosting. -
++ If you use a third-party service, review what keys and data it requires, and whether it ever takes custody + or intermediates funds. +
+ > + ), + }, + { + question: "How does XMR Checkout differ from BTCPay Server?", + answer: ( + <> ++ BTCPay Server is a general-purpose, self-hosted payment server with a primary focus on Bitcoin + and optional integrations for other assets (including Monero via a plugin). XMR Checkout is intentionally + focused on Monero checkout with a view-only trust boundary and a minimal, deterministic core. +
++ Some hosted BTCPay deployments may not include the Monero plugin by default. XMR Checkout provides a + small compatibility layer so teams can integrate without running a full BTCPay deployment. +
- Use the hosted checkout. Create invoices, query status. Control - stays with you. + Hosted invoice pages, API, and webhooks for status updates. View-only access, no fund movement.