Connect PQ Intel to Stripe for automated subscription management, invoice generation, payment tracking, and billing analytics — all from within your PQ Intel dashboard.
The PQ + Stripe integration connects your Stripe account to PQ Intel's billing system, enabling automated subscription lifecycle management, real-time invoice generation, payment success/failure tracking, and billing analytics — all synced directly with your PQ Intel workspace and team plan settings.
When connected, Stripe pushes subscription events — new signups, plan upgrades/downgrades, cancellations, payment failures, and successful invoices — into PQ Intel's billing dashboard. You get real-time visibility into your MRR, churn, active subscriber counts, and payment status without leaving the app.
PQ Intel automatically provisions and deprovisions plan access based on Stripe subscription events. When a customer upgrades, downgrades, or cancels, PQ Intel applies the correct feature gates, seat limits, and tier restrictions within seconds — no manual intervention required.
Failed payment events from Stripe trigger automated dunning workflows in PQ Intel. The system sends grace-period reminders, escalates to your team via Slack or Telegram, and can automatically downgrade accounts to a free tier after a configurable number of failed attempts.
In your Stripe Dashboard, go to Developers > Webhooks and click Add endpoint. Enter the webhook URL provided in your PQ Intel Stripe settings page. Select the events you want to listen for: customer.subscription.*, invoice.*, payment_intent.*, and checkout.session.completed.
From the Stripe Dashboard, go to Developers > API keys. Copy your Publishable key (starts with pk_live_ or pk_test_) and your Secret key (starts with sk_live_ or sk_test_). Use test keys for sandbox mode first.
After creating the webhook endpoint, Stripe generates a Signing secret (whsec_...). Copy this — PQ Intel uses it to verify that incoming webhook payloads are genuinely from Stripe.
In PQ Intel, go to Settings > Integrations > Stripe. Paste your Publishable key, Secret key, and Webhook signing secret. Click Save & Verify — PQ Intel sends a test event to confirm the connection is live and authenticating correctly.
In the Stripe webhook settings, ensure you have selected all relevant events under the Listen to events on account section. PQ Intel processes customer.subscription.created, customer.subscription.updated, customer.subscription.deleted, invoice.paid, invoice.payment_failed, payment_intent.succeeded, payment_intent.payment_failed, and checkout.session.completed. Deselecting any of these will cause gaps in billing data and missed alerts.
In PQ Intel, navigate to Settings > Billing > Alerts. Configure thresholds for payment failure alerts, MRR drop notifications, and churn rate warnings. You can set percentage-based or absolute-value triggers — for example, alert the team if MRR drops more than 10% in a single day, or if more than 5 payment failures occur within an hour. Route these alerts to Slack, Telegram, or email.
Below are the Stripe webhook events that PQ Intel processes. Each event triggers specific actions in the billing pipeline.
| Event Type | Description | PQ Intel Action |
|---|---|---|
| customer.subscription.created | A new subscription has been created in Stripe | Creates a PQ Intel subscription record, provisions the plan tier, applies feature gates, sets seat limits, and triggers welcome email |
| customer.subscription.updated | An existing subscription was modified (plan change, quantity update, status change) | Updates the PQ Intel subscription record, adjusts feature gates and seat limits to match the new plan, and logs the change in billing history |
| customer.subscription.deleted | A subscription has been canceled or expired | Removes or deactivates the subscription record, downgrades the account to the free tier (if configured), and triggers a cancellation notification |
| invoice.paid | An invoice payment has succeeded | Records the invoice in PQ Intel billing history, updates MRR and active subscriber counts, and marks the subscription as paid |
| invoice.payment_failed | An invoice payment attempt failed | Logs the failed payment, increments the payment failure counter, triggers a dunning workflow (grace period, reminder email), and notifies the team |
| payment_intent.succeeded | A payment intent has completed successfully | Confirms the payment in the billing pipeline, updates payment status for the associated invoice, and logs the transaction |
| payment_intent.payment_failed | A payment intent attempt failed | Triggers a real-time alert to the team with customer details and failure reason, logs the failure for analytics, and initiates retry logic if configured |
| checkout.session.completed | A Stripe Checkout session has been completed successfully | Creates a new customer record in PQ Intel, associates the subscription, provisions the plan, and triggers onboarding workflows |
When a user signs up for PQ Intel through the billing flow, Stripe creates a subscription and sends the event to PQ Intel. The app automatically provisions the correct plan tier, applies feature gates, and sends the user a welcome email — all without manual intervention.
Stripe pushes payment_intent.payment_failed events to PQ Intel in real time. Your team gets an immediate notification via Slack or Telegram, along with the customer details and failure reason, so you can reach out proactively to prevent involuntary churn.
PQ Intel's billing dashboard ingests Stripe invoice and subscription events to display live MRR, active subscriber counts, churn rate, and plan distribution. Daily summary reports can be routed to your finance team's Slack channel automatically.
PQ Intel uses a restricted API key with read-only permissions on subscription, invoice, and payment intent resources. PQ does not modify your Stripe account, create charges, or access connected account data.
Every incoming Stripe webhook is verified using the signing secret. PQ Intel rejects any payload that doesn't include a valid stripe-signature header, preventing forgery and replay attacks.
Stripe API keys and webhook secrets are encrypted at rest using AES-256. They are never logged, displayed in plaintext after initial entry, or exposed in any PQ Intel dashboard UI.
All communication between Stripe and PQ Intel is over TLS 1.3. Webhook payloads are processed in-memory and never persisted beyond the billing analytics pipeline.
Common issues when setting up or maintaining the PQ + Stripe integration and how to resolve them.
If subscription events (created, updated, deleted) are not showing up in the PQ Intel billing dashboard, the webhook endpoint URL may be misconfigured or missing.
304/404 responses.If invoice data in PQ Intel does not match what you see in Stripe, the webhook may not be subscribed to the correct invoice events.
invoice.paid and invoice.payment_failed events. If these events were added after the initial webhook creation, click Update endpoint to save the new event selections. Also check that no Stripe API key restrictions are blocking invoice resource access.If payment failure alerts, MRR drop notifications, or churn warnings are not being delivered, the billing alert thresholds may not be configured correctly.
If PQ Intel is rejecting Stripe webhooks with signature verification errors, the signing secret in PQ Intel does not match what Stripe issued for the endpoint.
whsec_... value. In PQ Intel, go to Settings > Integrations > Stripe and paste the value into the Webhook signing secret field. Click Save & Verify to confirm the signature is now accepted.Yes. PQ Intel uses a restricted read-only API key and never modifies your Stripe account. All credentials are encrypted at rest with AES-256, all traffic uses TLS 1.3, and every webhook payload is verified using Stripe's signing secret. PQ Intel cannot create charges, modify subscriptions, or access connected account data.
Yes. PQ Intel supports connecting multiple Stripe accounts — one per workspace. If you operate separate Stripe accounts for different products or regions, you can configure each workspace with its own set of API keys and webhook endpoints. Contact support if you need more than 5 connected accounts.
Stripe automatically retries failed webhook deliveries for up to 3 days with exponential backoff. PQ Intel processes events in order and deduplicates them, so no data is lost during brief outages. If the endpoint remains unreachable, Stripe marks it as disabled in the Dashboard and sends you an email notification.
Yes. PQ Intel fully supports Stripe test mode. We recommend setting up the integration with test API keys and test webhook secrets first, verifying end-to-end event flow, and then switching to live keys. Test events appear in your PQ Intel billing dashboard with a clear test-mode indicator so you can distinguish them from production data.
When Stripe sends a customer.subscription.updated event indicating a plan change, PQ Intel adjusts the account's feature gates, seat limits, and tier restrictions within seconds. Downgrades deactivate premium features but preserve data. Upgrades immediately unlock the new plan's capabilities. All changes are logged in the billing history for audit purposes.
Yes. In PQ Intel, go to Settings > Billing > Alerts and configure custom alert rules. You can set per-event-type triggers — for example, receive alerts only for invoice.payment_failed events above a certain amount, or mute alerts for test mode events. You can also route different alert types to different channels (Slack for payment failures, email for MRR changes).
Set up the integration in under 60 seconds. Start with a 14-day free trial — no credit card required.
View plans & pricing