Crypto payments for SaaS products
Automatic recurring payments in USDT, invoices via payment links, and monthly billing — for SaaS with international audiences.
Why SaaS products switch to crypto billing
Recurring in USDT
Stable rate — customer knows the dollar price of every renewal
Auto-retry + dunning
Charge-retry logic and notification flow out of the box
0.2% fee
No card-processing surcharge on top of subscription cost
HMAC webhooks
Signed payloads, idempotency keys, back-off retries
High-risk friendly
VPN, hosting, dev-tools — categories Stripe declines
Static wallet per customer
One address per customer — clean analytics and reconciliation
Subscriptions and invoices without card-on-file
Recurring billing without card-on-file
Customer authorises the subscription once via a static wallet address. Charges run automatically on schedule. No CVV, no expiry-renewals, no 3D-secure rejections. USDT-denominated for predictable pricing.
Subscriptions API docs →Engineer-friendly integration
REST API with Node.js, Python, and PHP SDKs. Webhooks are HMAC-signed, payloads are idempotent, the sandbox is fully wired. Ready-made invoice-flow and subscription-lifecycle examples in the docs.
Sandbox and examples →Perfect fit for
VPN services
High-risk category with frequent Stripe rejections. Crypto rails accept payments without issuer rejections, audience is crypto-native.
Hosting and VPS
Cross-border customers, instant provisioning on payment confirmation. Webhook closes the invoice — billing logic is automated.
Dev-tools and API SaaS
Recurring USDT for developer audiences. Teams pay from corporate wallets — no corporate-card setup required.
B2B SaaS with global reach
One pricing tier for customers in 180+ countries, no FX fees, no dependency on the issuer-bank rules of your region.
What you get
Crypto recurring subscriptions
Customer authorises a subscription once via static wallet, charges run automatically thereafter. USDT delivers price stability, BTC suits crypto-native audiences.
Invoices and billing links
Generate payment links with a single API call, send via email or in-product. Customer pays in one tap, invoice closes automatically.
No bank rejections
High-risk SaaS categories (VPN, hosting, dev-tools) often hit Stripe or Adyen rejections. Crypto rails work for every legal use case in 180+ countries.
Cryptoway vs Stripe Billing and Adyen
What engineers say
«Webhooks just work. Idempotency keys, signed payloads, retries — we ripped out our payment monolith and shipped recurring USDT in five days.»
FAQ
How does recurring work without card-on-file?
Customer binds a wallet to the subscription. Charges run via signed transactions from their address — they stay in control.
Can we offer a trial without payment?
Yes. Subscriptions can start with a trial period, the first charge fires after it ends.
What about refunds?
Refunds are processed manually from your admin dashboard — send the transaction back to the customer address.
How does dunning work if the wallet is empty?
Auto-retry with back-off (1h, 6h, 24h, 3 days), grace-period is configurable. Customer receives email + webhook on failed charge — you can notify in-product.
Is the sandbox realistic?
Yes — sandbox emulates blockchain confirmations, network latency, and typical failure modes. Signed webhooks, idempotency keys, all production-faithful.
How are customer wallets secured?
Cryptoway is non-custodial — funds route straight to your wallet, we hold zero balances. Every transaction is signed by the customer or your SDK, sanctions/AML screening is built in. SOC 2 Type II audit in progress.