MANAGED NON-CUSTODIAL CRYPTO PAYMENTS

Accept crypto.
Keep control.

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.

Bitcoin USDt TRON USDt Ethereum USDt Polygon USDt BSC External Lightning Hosted subscriptions
Non-custodialSprey does not receive, hold or forward merchant funds.
ManagedUse hosted payment infrastructure instead of maintaining BTCPay yourself.
Multi-railBitcoin, USDt and external Lightning are already verified paths.
Evidence-firstSales claims expand only after complete merchant-flow testing.

WHY SPREY

Crypto payments without giving up ownership or becoming your own infrastructure team.

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.

01

Keep control

Merchant wallets, public payment destinations and private signing authority stay under merchant control rather than inside a shared Sprey custodial wallet.

02

Skip the maintenance burden

Sprey runs the hosted BTCPay service, ingress and surrounding infrastructure so the merchant can focus on selling and integrating.

03

Start with what is proven

Capabilities are promoted as verified only after real merchant-path testing rather than because an upstream configuration page exists.

VERIFIED TODAY

Real payment paths already exercised on the reference deployment.

BTC

Bitcoin on-chain

The reference Store uses watch-only observation while spending authority remains in a separate merchant-controlled wallet.

USDt

TRON, Ethereum, Polygon and BSC

Real paid-invoice end-to-end settlement has been verified on all four currently exposed USDt networks.

LN

External Lightning

The verified path uses a client-controlled external Nostr Wallet Connect setup instead of a shared Sprey Lightning wallet.

SUB

Hosted subscriptions

Trial, expiry, recovery payment, return to active access and next-billing recalculation have been exercised.

REQ

Payment Requests

Shareable merchant payment requests are verified on the current reference deployment.

WEB

WooCommerce path

Sprey WP Stack provides a prepared WordPress and WooCommerce storefront path into Sprey Processing.

HOW IT WORKS

Simple ownership. Clear responsibilities.

1. Your storefrontWooCommerce or another merchant system owns products, cart, checkout and orders.
2. Sprey ProcessingBTCPay creates or tracks the invoice and exposes payment state to the integration.
3. Payment networkThe customer pays through Bitcoin, USDt or an enabled external Lightning path.
4. Your destinationThe payment reaches the merchant-controlled wallet or payment destination.
The payment itself happens independently of Sprey. Sprey provides hosting, blockchain and payment-state observation, and integration infrastructure. It does not receive, hold, exchange, transfer or otherwise control merchant funds.

COMMERCE + PROCESSING + OWNERSHIP

Use the parts together without coupling them into one monolith.

COMMERCE

Your storefront

Your shop remains responsible for products, customers and order workflow. Sprey WP Stack is the current prepared WooCommerce implementation.

PROCESSING

Sprey-hosted BTCPay

The processing layer creates and observes invoices and reports payment state without becoming the merchant's wallet.

OWNERSHIP

Your wallet boundary

Merchant-controlled payment destinations and signing authority stay separated from the hosted processing infrastructure.

WHAT COMES NEXT

The product grows from tested merchant flows, not from promises.

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.

When a capability passes real verification, it can move from roadmap to product page, documentation and sales material.

Start with the rails that are already verified.

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

Three focused concepts behind this combined version.

01

Your payments. Your wallet.

Direct commercial framing around merchant ownership and managed infrastructure.

Open concept 1 →

02

Accept crypto. Keep control.

Minimal framing built around the non-custodial principle and verified rails.

Open concept 2 →

03

Stay out of the wallet.

More technical framing around separation of commerce, processing and ownership.

Open concept 3 →