SaaS
Crypto checkout for SaaS subscription billing
Accept crypto for your SaaS subscription on the customer's terms. Build per-cycle or credit-pack flows on top of the Payment Intents API without claiming a managed subscription engine.
Who this page is for
This page is for SaaS founders who sell recurring products and want crypto as one supported payment surface.
PayKrypt now has a native Subscription object with trials, coupons, and automatic per-cycle invoicing. See the dedicated Subscriptions page for the full model. This page still does not promise automatic wallet charging: your customer approves and pays each cycle.
- A B2B SaaS founder can put a customer on a Subscription with a recurring price and let PayKrypt generate the renewal invoice each cycle.
- A credit-based product can create one Payment Intent per pack purchase and credit the account after webhook verification.
Two patterns: native subscriptions and credit packs
Put a customer on a recurring price with the Subscription object and PayKrypt generates the renewal invoice (including trial and coupon handling) automatically each cycle.
Credit packs remain a manual pattern: a one-off purchase does not map to a recurring price, so you create one Payment Intent per pack and credit the account after webhook verification.
POST /v1/subscriptions
Authorization: Bearer <YOUR_SECRET_KEY>
Idempotency-Key: <unique-key-per-subscription>
Content-Type: application/json
{
"customerId": "c1a2b3c4-...",
"priceId": "a1b2c3d4-...",
"trialEnd": "2026-08-01T00:00:00.000Z"
}Renewal and churn on a customer-initiated surface
Put a recurring price on a Subscription and PayKrypt generates the renewal invoice automatically each cycle, no need to track cycles in your own database.
If a cycle goes unpaid, PayKrypt runs its dunning cadence (reminders, then past-due, then cancellation) before you need to intervene.
PayKrypt still does not auto-charge a customer's wallet: your customer approves and pays every invoice, which is what keeps this non-custodial.
What your customer sees
The customer opens hosted checkout on gate.paykrypt.io, chooses an available crypto payment option, signs the transaction, and waits for confirmations.
The customer does not need a PayKrypt account. Your SaaS app owns the account, entitlement, renewal, and churn states.
Operational details
For Subscriptions, PayKrypt generates and tracks each cycle invoice for you. Verify webhook signatures from the raw body and update entitlement on subscription.updated.v1 or invoice.paid.v1.
For credit packs, use one idempotency key per pack purchase and update entitlement only after payment.confirmed.v1.
Listen for refund events if your application needs to revoke or partially revoke access after a refund.
Settlement, fees, and pricing
Settlement happens on-chain as confirmations land. This page does not promise a specific time window.
The public marketing fee model is 1% per confirmed payment, with no setup costs and no monthly charges.
FAQ
Does PayKrypt offer a subscription engine or native recurring billing?
Yes. PayKrypt has a native Subscription object with trials, coupons, invoice-driven billing cycles, and dunning for unpaid cycles. See the dedicated Subscriptions page and the Subscriptions API docs.
What happens if a customer does not renew?
For a Subscription, PayKrypt runs its dunning cadence on the unpaid cycle invoice before canceling. Credit packs are not Subscriptions and remain fully merchant-managed: your SaaS app handles lapse, access, and reactivation.
How long does settlement take?
Settlement happens on-chain as confirmations land. This page does not promise a specific settlement-time window.
Does my customer need a PayKrypt account?
No. Hosted checkout does not require the customer to register with PayKrypt.
Which webhook events should my integration listen for?
Use payment.confirmed.v1 to extend access or credit a pack. Use the public Webhooks docs for the current event list and verification pattern.
Next steps
Start with the public Quickstart, then contact PayKrypt if you need help evaluating your integration path.