Where the money goes, and who can reach what

• Your own Stripe account. When you run ShipRev yourself, it connects to your own Stripe account with your own keys, and payments go to that account. ShipRev is not the merchant of record.
• No share of your revenue. ShipRev does not take a percentage of the payments your customers make.
• Records that are not rewritten. Invoice records are immutable: once written, they are not edited.

• Two separate sign-ins. Your team and your end users sign in to different places. The operator console does not accept end-user credentials, and the end-user portal does not accept your team's.
• Roles for your team. Each member of your team has one of four roles, Owner, Admin, Member or Viewer, scoped to all of your applications or to one.
• Keys you can narrow, rotate and revoke. The keys your backend holds can be limited in scope, rotated and revoked.
• End users inside their organization. Each end user works inside a buyer organization, which is created when they sign up or which they join by invitation.
• Published plans are read-only. A published plan version cannot be edited; a change means publishing a new version.

Changes to configuration, to subscriptions and to entitlement adjustments are written to an append-only change log: entries are added and never edited.

• Self-hosted. ShipRev runs in your own deployment, and identity, subscriptions, usage and entitlements are kept in its one database. Self-hosting is not available yet: the source repository is not public.
• Managed cloud. Each application runs in one of the regions we offer, chosen when you create it. The managed cloud is built but not yet open.

• Website privacy notice

Email us with what you found and the steps to reproduce it. Please do not test against accounts or data that are not yours.

contact@shiprev.dev