Subscriptions
Recurring crypto billing with a native Subscription object
PayKrypt now has a native Subscription object: trials, coupons, and an invoice generated automatically every billing cycle. Chain-agnostic recurring billing, including TRC-20 USDT, non-custodial by design, since PayKrypt never auto-charges a customer's wallet.
Who this page is for
This page is for merchants who bill on a recurring cycle (SaaS plans, memberships, retainers, or cohort subscriptions) and want that recurrence modeled natively instead of hand-rolled.
PayKrypt now has a native Subscription object. A Subscription binds a customer to a recurring price; PayKrypt computes what is owed each cycle and generates the invoice for it automatically.
- A SaaS merchant can start a customer on a 14-day trial with trialEnd, then let PayKrypt generate the first renewal invoice automatically once the trial ends.
- A membership business can attach a coupon that discounts a fixed number of cycles, then let it expire back to full price without any manual bookkeeping.
Three layers, kept separate: subscription, invoice, billing
A Subscription is the recurring commitment: it is not itself a bill. Each cycle, billing computes what is owed on that Subscription and creates an Invoice: its own record with a status, a due date, and a payment link.
Billing is the process that turns a Subscription into Invoices over time: cycle computation, coupon application, and dunning on unpaid invoices. These three terms are not interchangeable in the API or the dashboard.
How collection works today: your customer approves every payment
Each cycle, PayKrypt generates an invoice and a hosted payment link and sends it to the customer, the same hosted checkout used everywhere else on PayKrypt.
PayKrypt does not auto-charge a customer's wallet. There is no standing authorization that lets PayKrypt or your business pull funds without a new approval each cycle. That is what keeps this non-custodial, and it puts your customer in control of every payment.
The Subscription's collection method accepts one value today, invoice_link. An on-chain mandate field exists for a future collection method, but it is not available yet.
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",
"couponId": "e5f6a7b8-..."
}Trials and coupons
Set trialEnd on create and the subscription starts as trialing, no invoice is generated until the trial ends.
A coupon can apply for a fixed number of cycles, every cycle, or forever. Changes take effect starting the next generated invoice only, never retroactively.
If a cycle goes unpaid
PayKrypt runs a dunning cadence on an unpaid invoice: reminder emails first, then a past-due grace period, then automatic cancellation if it stays unpaid. Paying at any point during the grace period brings the subscription back to active.
The exact dunning timeline lives in the Subscription Billing guide in the developer docs. Refer there for current day-by-day behavior rather than assuming a fixed schedule.
What your customer sees
An emailed invoice each cycle, paid on hosted checkout at gate.paykrypt.io, no PayKrypt account required.
Nothing to pay while a trial is active. The first invoice arrives once the trial ends.
Chain-agnostic by design
Recurring billing is not tied to one chain. Customers can pay each cycle with BTC, ETH, USDT and other major tokens, including TRC-20 USDT, subject to what is enabled on that cycle's payment link.
For the exact current asset and chain list, use the developer documentation rather than this page.
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 have a real Subscription object now?
Yes. PayKrypt has a native Subscription object with trials, coupons, statuses (trialing, active, past_due, paused, canceled, expired), and invoices generated automatically each billing cycle.
Does PayKrypt automatically charge my customer's wallet each cycle?
No. Each cycle generates an invoice and a payment link that the customer reviews and pays. This is non-custodial by design: an on-chain mandate for automatic charging is not available today.
What's the difference between a subscription, an invoice, and billing?
A Subscription is the recurring commitment. Billing is the process that turns it into Invoices over time. An Invoice is the actual bill for one cycle, with its own status, due date, and payment link.
What happens if my customer misses a payment?
PayKrypt runs a dunning cadence: reminders, then a past-due grace period, then automatic cancellation if it stays unpaid. See the Subscription Billing guide for the exact timeline.
Can I offer a free trial or a discount?
Yes. Set trialEnd on create for a trial period with no invoice until it ends, and attach a coupon for a fixed number of cycles, every cycle, or forever.
Which chains and assets can my customer pay with?
Recurring billing is chain-agnostic, including TRC-20 USDT, subject to what is enabled on that cycle's payment link. See the developer documentation for the current exact list.
Next steps
Start with the public Quickstart, then contact PayKrypt if you need help evaluating your integration path.