Stripe

Stripe connects as a company-scoped connector via OAuth. The admin authorises once; Stripe syncs financial event data into the entity graph.

What syncs

Stripe yields event data only:

• Customers — become external-contact entities or link to existing ones via email-based identity resolution.
• Invoices — become invoice entities with amount, due date, status (paid, open, overdue), and linked customer.
• Payments — update invoice status when received. A payment event against an open invoice auto-resolves any overdue-invoice situation linked to it.
• Subscriptions — become subscription entities with current status, renewal date, and linked customer.

Situation detection

Finance-critical situation types typically configured against Stripe data:

• Invoice 14 days overdue with no payment event.
• Subscription renewal within 30 days for a customer with declining activity.
• Failed payment on an active subscription.
• Customer lifetime value crossed a threshold — trigger a relationship-hub update.

Auto-resolution example

An overdue-invoice situation is created at day 14. Stripe reports payment at day 17. The situation auto-resolves — you don’t have to close what the event stream closed.

Write-back

Stripe write-back is not currently supported. The connector is read-only — invoice sends, refunds, and subscription changes happen in Stripe’s UI or via Stripe’s own automation. The AI can surface the situation and draft a follow-up email (via Gmail or Outlook), but cannot mutate Stripe state.

Cross-system context

Stripe’s real value in Qorpera is cross-system correlation. An overdue invoice (Stripe) + two unanswered follow-ups (Gmail) + a renewal in 60 days (HubSpot) compose into a single situation the reasoning engine treats as one decision — not three independent notifications.