Subscriptions
Coin Moebius can sell recurring subscriptions on Stripe, PayPal, and Dodo. The merchant configures the price and interval once on a product; the buy button on the site stays exactly the same. The payment provider runs the recurring billing, holds the card, retries failed renewals, and hosts the cancellation page. Coin Moebius keeps the latest status of each subscription, and your code reads it from the /status endpoint.
Setting up a recurring product
In the dashboard's Products tab, set the Billing field to Monthly or Annual instead of One time. An optional Free trial field appears for any trial days you want to grant before the first charge. Save the product.
The buy button HTML doesn't change. The same product-id="pro-plan" attribute works for one-time or recurring; the worker checks the product's billing setting at checkout time and routes through the provider's subscription API when applicable.
<coin-moebius-buy
project-id="proj_YOUR_ID"
product-id="pro-plan"
amount="9.00"
currency="USD"
label="Pro plan">
</coin-moebius-buy>What you don't have to build
The provider runs the schedule. We don't store cards. We don't run cron jobs. We don't retry failed charges. We don't send dunning emails. We don't host a cancellation page. That entire side of the system lives inside Stripe (or whichever fiat provider you've connected). You're outsourcing the hard parts of recurring billing to the company that's already running them for millions of merchants.
Subscription events
Renewals and cancellations reach us as webhook events from the provider. We sort them into five types and keep the latest status, which your server reads from the /status endpoint:
| Event | When it fires |
|---|---|
subscription.created | New signup. |
subscription.renewed | A non-initial cycle succeeded. The period end that /status returns moves forward. |
subscription.payment_failed | A cycle's card was declined. The provider's dunning retries on its schedule. |
subscription.canceled | Terminal cancellation. The buyer canceled, dunning was exhausted, or the merchant canceled. |
subscription.updated | Status change, card update, plan change. |
Identifying buyers without storing them
Coin Moebius is a payment router, not a customer database. We never store buyer names, addresses, or the provider's internal customer ids. If your application has user accounts (most subscription apps do), pass your own opaque user id as customer-ref on the buy button. The button forwards it to the worker as metadata.customerRef, we thread it through to the provider, return it from the /status endpoint, and store only that opaque string. To us it's meaningless; to you it's the foreign key into your own user system.
<coin-moebius-buy
project-id="proj_YOUR_ID"
product-id="pro-plan"
amount="9.00"
currency="USD"
customer-ref="user_bob_42"
label="Pro plan">
</coin-moebius-buy>When you need deeper buyer detail (email, card last-four, dispute notes), the dashboard links each card transaction out to the provider that handled it (Stripe, PayPal, Square, or Authorize.Net), where the buyer record actually lives. You click through; we never duplicate it.
Cancellation: link out, don't build
Buyers cancel in the provider's hosted portal: the Stripe Customer Portal or the buyer's PayPal account page. The portal handles cancellation, card updates, receipt downloads, and plan changes, all UI you don't have to build. You can send the buyer there with two calls. Your server asks for a short-lived grant with your API key, then the buyer's browser trades the grant for the portal link:
// Your server, with your API key
const grantRes = await fetch(
`https://api.coinmoebius.com/api/subscriptions/${projectId}/${subId}/portal-grant`,
{ method: 'POST', headers: { Authorization: `Bearer ${apiKey}` } },
);
const { grant } = await grantRes.json();
// The buyer's browser, with the grant from your server
const res = await fetch(
`https://api.coinmoebius.com/api/subscriptions/${projectId}/${subId}/portal-url`,
{
method: 'POST',
headers: { 'Content-Type': 'application/json' },
body: JSON.stringify({ returnUrl: 'https://you.example/account', grant }),
},
);
const { url } = await res.json();
window.location.assign(url);Which providers support subscriptions today
Stripe and PayPal work end-to-end through the hosted buy button with no extra setup: set a product to Monthly or Annual in your dashboard, paste the button on your page, and the click starts a real subscription. Dodo works through the button too, with one extra step: Dodo prices a subscription as a pre-built product, so you create the recurring product in Dodo and put its product id in this product's Dodo settings (the same id field one-time Dodo uses). In all three the provider runs the renewals and hosts the cancellation page.
Square and Authorize.Net subscriptions don't run through the hosted buy button. You create the subscription through your own integration with the provider (for Authorize.Net, that means collecting the card on your own page with Accept.js; Square has its own hosted subscription checkout you can use), then point the provider's webhook at us. From there the rest of the system (webhook routing, dashboard, status endpoint, customer linking) works exactly the same way it does for Stripe and PayPal subscriptions. See Using the API.
Crypto providers (NOWPayments) do not support recurring billing in this product. Recurring crypto is friction-heavy on every gateway we've evaluated; we'd rather ship nothing than ship a half-broken story for it.