Connected providers
Official connections with visible status and recovery.
Rivetra connects launched services while keeping company ownership, protected credentials, errors, and approval boundaries explicit. Connections still under provider review stay out of the production interface.
Provider map
Each launched integration has one clear job.
StripeInvoice card and ACH payment pathways
PlaidReview-first bank transaction feeds
RevenueCatCompany subscription entitlement synchronization
FirebaseAuthentication, protected data, and notificationsFailure should be understandable
Connection errors need a recovery path.
OAuth state and PKCE controls protect supported authorization flows from callback substitution and token interception. Tokens remain server-side and company scoped. The mobile app receives connection state and available provider operations rather than long-lived provider secrets.
Provider circuit breakers convert rate limits, missing scopes, expired authorization, account eligibility, and temporary outages into status recovery guidance. Publishing still depends on the provider's account type, review status, app approval, permissions, and current platform rules.
Integration setup belongs in Settings. Daily Growth, Money, and Job screens show only the resulting status, data, and actions, keeping configuration detail out of operational workflows.
Integration questions
Connections without mystery.
Does Rivetra store provider passwords?
No. Supported OAuth providers authorize access through their own login and consent flow. Rivetra stores protected tokens or connection references needed for approved operations.
Why can a provider show connected but still block publishing?
A valid login does not guarantee every account, page, location, scope, app-review permission, or media type is eligible. Rivetra reports those requirements separately.
Can integrations be disconnected?
Yes. Company administrators can disconnect supported providers and revoke the associated Rivetra connection.