Subscriptions
What each organization pays for
Tiers, subscriptions, invoices and prepaid balances, held on the same customer record as identity, usage and entitlements. ShipRev keeps the state; the money goes to your own Stripe account.
What it covers
Built so far
Subscriptions and invoices
Subscriptions, immutable invoice records and refund credit notes. If a payment event arrives late or goes missing, the last confirmed event stands.
Prepaid wallets
End users can hold a prepaid balance, with a record of every top-up.
Your own Stripe account
When you run ShipRev yourself, it connects with your own Stripe keys and includes a connection test. Payments go straight to your account.
Versioned tiers, synced to Stripe
Changing a tier's price in the tier editor publishes a new version, without a change to your application code. Existing subscribers keep the version they bought. Each published tier shows whether it is syncing, synced or failed to sync to Stripe.
Self-service for your end users
In the portal, end users choose a tier and check out, upgrade or downgrade, cancel and resume, and change their payment method.
How it connects
One customer, four views
- IdentityA subscription belongs to a buyer organization.
- MeteringUsage is recorded under the same organization that holds the subscription.
- EntitlementsA subscription points to a published tier version, and that version defines what the organization holds. Changing plans changes which version it points to.