Keep control
Merchant wallets, public payment destinations and private signing authority stay under merchant control rather than inside a shared Sprey custodial wallet.
MANAGED NON-CUSTODIAL CRYPTO PAYMENTS
Sprey Processing gives merchants managed BTCPay-based payment infrastructure without taking custody of merchant funds. Customers pay merchant-controlled destinations while Sprey runs the hosting, network observation and integration layer around the payment flow.
WHY SPREY
Sprey separates three jobs that are often mixed together: your commerce system, the payment-processing infrastructure, and your wallet. That keeps responsibilities clearer and reduces the amount of infrastructure a merchant has to operate directly.
Merchant wallets, public payment destinations and private signing authority stay under merchant control rather than inside a shared Sprey custodial wallet.
Sprey runs the hosted BTCPay service, ingress and surrounding infrastructure so the merchant can focus on selling and integrating.
Capabilities are promoted as verified only after real merchant-path testing rather than because an upstream configuration page exists.
VERIFIED TODAY
The reference Store uses watch-only observation while spending authority remains in a separate merchant-controlled wallet.
Real paid-invoice end-to-end settlement has been verified on all four currently exposed USDt networks.
The verified path uses a client-controlled external Nostr Wallet Connect setup instead of a shared Sprey Lightning wallet.
Trial, expiry, recovery payment, return to active access and next-billing recalculation have been exercised.
Shareable merchant payment requests are verified on the current reference deployment.
Sprey WP Stack provides a prepared WordPress and WooCommerce storefront path into Sprey Processing.
HOW IT WORKS
COMMERCE + PROCESSING + OWNERSHIP
Your shop remains responsible for products, customers and order workflow. Sprey WP Stack is the current prepared WooCommerce implementation.
The processing layer creates and observes invoices and reports payment state without becoming the merchant's wallet.
Merchant-controlled payment destinations and signing authority stay separated from the hosted processing infrastructure.
WHAT COMES NEXT
Point of Sale, QR-specific flows, Payment Buttons, Donations, Crowdfunding and additional API/custom-integration scenarios remain outside the verified sales claim until their complete merchant flows are tested.
Open the live Processing service, inspect the technical documentation, or continue to the main Sprey site as it grows into the public product home.
DESIGN EXPLORATIONS
Direct commercial framing around merchant ownership and managed infrastructure.
Minimal framing built around the non-custodial principle and verified rails.
More technical framing around separation of commerce, processing and ownership.