Skip to main content
Regentra uses Stripe in two distinct ways: platform billing for your Regentra subscription, and per-org billing for invoicing your MSP clients through the PSA module.

​
Two modes of Stripe

Handles your Regentra subscription charges — plan fees, per-seat PSA billing, and compliance tenant add-ons. This is managed automatically when you subscribe and requires no additional setup. See Billing & Subscriptions for details.

​
Setting up per-org Stripe

1

Get your Stripe API keys

In the Stripe Dashboard, navigate to Developers → API Keys and copy your Publishable key and Secret key.
2

Enter keys in Regentra

Go to Settings → Integrations → Stripe and paste both keys.
3

Test the connection

Click Test Connection to verify Regentra can communicate with your Stripe account.
4

Save

Save the configuration. You can now generate invoices that accept payment through Stripe.
Use your live API keys for production invoicing. Test keys will not process real payments. Never share your secret key — it is encrypted at rest using AES-256-GCM.

​
Invoice generation and payment

Once Stripe is connected, the invoicing flow works as follows:
  1. Technicians log billable time against tickets
  2. Time entries go through the approval workflow
  3. An admin generates an invoice from approved entries
  4. The invoice is sent to the client with a Stripe-hosted payment link
  5. The client pays online via credit card or ACH
Payment status is tracked on the invoice in Regentra:
StatusMeaning
DraftInvoice created but not yet sent
SentInvoice delivered to the client
PaidPayment received through Stripe
OverduePayment deadline has passed without payment

​
Webhook configuration

Regentra uses Stripe webhooks to receive real-time payment events (payment succeeded, payment failed, refund issued). During setup, Regentra automatically configures the necessary webhook endpoint in your Stripe account.
If you need to manually configure the webhook, the endpoint URL is available in Settings → Integrations → Stripe → Webhook URL. Subscribe to invoice.paid, invoice.payment_failed, and charge.refunded events.