Taria Pay Docs

English

简体中文

English

简体中文

Appearance

Subscription plans ​

Subscription plans are for selling fixed-price memberships, service packages, or repeat-purchase plans. You configure a plan page in the merchant dashboard, then put the link on your website, in your community, or in emails. This is the no-code entry point for subscriptions — no code required.

If you already have your own product and customer system (SaaS, membership system), we recommend the API integration instead: manage users in your own system, and let Taria Pay handle payment collection and status sync, rather than maintaining plans one by one in the dashboard. See Subscriptions (API).

The current version is a customer-initiated renewal flow: each billing period, the customer goes to the subscription page and completes one stablecoin payment with their wallet. Once the payment confirms, Taria Pay records the subscription instance, the billing-period invoice, and the payment status, and lets your system extend service via webhooks or dashboard data. It is not recurring billing that automatically charges the customer's wallet.

Good for ​

  • Fixed-price memberships
  • Digital service packages
  • Repeat-purchase subscription benefits
  • B2B SaaS, communities, service packages, and anything renewed monthly, quarterly, or yearly
  • Sales flows where you don't want to create an ordinary order per buyer but still want to track subscriber status

Create a subscription plan ​

  1. Go to the merchant dashboard.
  2. Open Subscriptions.
  3. Create a plan with a name, price, currency, and description.
  4. Save and copy the plan link.
  5. Put the link on your website or send it to buyers.

The copied plan link looks like https://checkout.tariapay.com/su_<planId>; older-format links you shared before continue to work.

After a customer completes their first payment, the dashboard creates a subscription record. When the same customer pays through that plan again, it's recorded as a renewal invoice under the same subscription.

Subscription statuses ​

  • incomplete: The subscription record exists, but the first payment hasn't confirmed yet.
  • active: The most recent billing-period payment is confirmed and the current period is in effect.
  • past_due: Needs re-collection or manual handling — for example, a confirmed payment was hit by an on-chain reorg.
  • canceled: Manually canceled by the merchant.
  • expired: Reserved for a future automatic-expiry flow.

How this differs from payment orders ​

Payment orders are usually created dynamically by your server for each order — a fit for shopping carts and custom order flows.

Subscription plans are configured in the merchant dashboard — a fit for fixed-price, reusable sales pages.

If you need to automatically provision entitlements in your own SaaS or membership system, listen for payment_intent.confirmed and read sourceType=subscription, subscriptionPlanId, subscriptionId, and subscriptionInvoiceId from the payload. Don't rely solely on the customer's browser returning to the success page.

Next steps ​