Data flows in from the platforms where revenue lives. Payables flow out to whatever provider each creator picks. Same connector pattern, same audit trail, same period-aligned schedule, whether the integration is shipping sales data in or pushing a payout out.
Whether it's pulling Shopify orders, parsing an Amex CSV, or pushing a payable to Wise, every CleaRoyalty connector honors the same contract. No bespoke wiring, no special-case integrations that drift over time.
Inbound connectors pull on the period schedule. Outbound payables ship at publish. No webhooks land sales mid-period; no "fire-and-forget" payouts ride out before a statement is approved.
Every credential, every payout detail, every API token is encrypted with a per-tenant key. A breach in one tenant's connector cannot expose another tenant's data.
Every pull is checked: expected schema, expected row counts, expected totals against the prior period's baseline. Drift is caught before it reaches the engine.
Refund spikes, revenue swings, missing data, ad-spend variance. Anything that looks off lands on the dashboard and in the admin inbox before a creator opens the portal.
A failed pull retries hourly for 24 hours, riding through rate limits and transient outages. After that, the period stalls, admins are paged, and the cause and fix are surfaced.
When the pull ran, what it returned, who triggered it, which credential was used. Every connector event is in the audit trail and every export. Forever.
Sales platforms, expense systems, ad accounts, banks. Every period, the connectors fetch what they need, validate it, and stage it for the engine. Nothing for you to assemble, nothing to copy and paste.
Connect whichever payout providers your tenants need. Each artist picks their preferred method per tenant from the providers you've connected. A statement publishes, the payable lands in the right system, the artist gets paid the way they want.
Same pattern, same contract. New connectors join the catalog without disturbing tenants already in production. The platform is built to grow connector-by-connector, on demand, on a schedule the business chooses.
You name the platform during onboarding or any time after. We assess the integration scope and the data shape it returns.
Implementation follows the connector contract. Pull-based, encrypted credentials, validated, anomaly-watched, retry-then-page, logged. No bespoke shape.
The new connector is added per-tenant via the wizard. Tenants already in production are not disturbed; they opt in only when they want to.
Once shipped, the connector moves from "on request" to "available" in the catalog and is offered to any other tenant that needs it.