For Payfacs & Embedded Payments ISVs in the Trades
Payments attach rate, residuals, and disputes, joined back to the account that generated them
Your processor, your CRM, and your GL each key the merchant differently, so attach, net take rate, and dispute losses never read against the account.
A data warehouse built specifically for payfacs and embedded payments ISVs serving the trades. Connect the processor, the CRM, onboarding, and the GL. Live in about 48 hours.
The join, made visible
Every system you run — and the answers you can't get today.
One shared key across every system. No exports, no VLOOKUP — the tools you already run, finally answering the questions that matter.
Good morning, Morgan.
Q3 Revenue Review
Renewal due in 71 days. Usage down 12% QoQ and two support escalations open — flagged at risk by the renewal model.
Synopsis is a data warehouse for vertical SaaS companies monetising embedded payments in the field trades, live on your own systems in about 48 hours. Stripe Connect submerchant activity, Stripe Billing subscriptions, Persona onboarding, Salesforce accounts, NetSuite revenue, and dispute portal records land in one warehouse keyed to the same merchant and account. Questions like what our payments attach rate is by segment and what activated accounts net us after processor cost and disputes become single queries. Updated August 2026.
Popular pairings
The pairings that tie payments revenue back to an account.
Your processor, your CRM, and your GL each key the merchant differently. One account key is what makes attach, take rate, and dispute loss readable.
Stripe Connect + Salesforce
Synopsis integrates Stripe Connect submerchant activity with the Salesforce account that owns it, so attach rate reads by segment, rep, and office.
Stripe Connect + NetSuite
Synopsis connects Stripe Connect volume, residuals, and fees to NetSuite revenue, so net take rate is a measured number per account.
Persona + Salesforce
Synopsis joins Persona onboarding and KYC status to the Salesforce account record, so a stalled activation is visible while it can still be rescued.
Stripe Billing + Stripe Connect
Synopsis integrates Stripe Billing subscription status with Stripe Connect payments activity, so an account paying for software but not processing is on a list.
Adyen for Platforms + NetSuite
Synopsis syncs an ISV on Adyen for Platforms to the same NetSuite revenue view, so the analysis does not depend on which processor you chose.
Salesforce + Zendesk
Synopsis joins the Salesforce account to its Zendesk dispute and support history, so margin erosion has a cause attached to it.
Questions
Answers before you ask.
Why don't our processor, our CRM, and our GL agree on payments revenue per account?
Because each system keys the merchant differently: the CRM tracks the company, the payments platform tracks the merchant account and its sub-merchants, the payout file tracks a settlement batch, and the GL tracks a deposit. Synopsis resolves them to one account key in one warehouse, so attach rate, gross volume, net take rate, residuals, and dispute losses all read against the account that produced them. Synopsis brings the records together for analysis; it doesn't replace your systems of record.
Can we tie every residual back to the connected account and the settlement month?
Yes. Every residual ties to the connected account and the settlement month, with fee variances itemized. Per-account net take rate comes off the connected-account fee detail your platform reports: interchange, scheme fees, processing fees, dispute fees, refund fees, and Radar fees per connected account. Network costs revise for up to two months after the transaction, so Synopsis carries both the provisional and the settled figure and labels which one you are reading.
We are moving from one payments platform to another. Can we report across both?
Yes. Both platforms land in the same warehouse keyed to the same account and the same merchant, so attach rate, net take rate, and dispute drag read across the old book and the new one while the migration runs. Volume that moved and volume that stalled read as separate rows, and the reporting does not wait for the cutover to finish.
Does Synopsis integrate Stripe Connect with Salesforce?
Yes. Stripe Connect submerchant activity and Salesforce accounts land in one warehouse keyed to the same customer, so payments attach rate, residuals, and disputes read by account and segment in one query. The same holds for Adyen for Platforms, Payrix, Finix, Stripe Billing, NetSuite, and the rest of a software company's systems.
We run a system that isn't listed here. Can you connect it?
Usually, yes. The AI builds the connector from an export or an API, and a new system is typically flowing in days. If it can produce a file, it is a candidate.
How long until we can start asking questions?
Your first connected systems are answering questions in about 48 hours, and a full rollout lands in days, not a multi-quarter data project.
Do we need a data team or anyone who knows SQL?
No. We configure your warehouse with you and connect the systems you already run; your team just asks questions in plain English. Nobody has to write SQL or babysit pipelines unless they want to.
Does Synopsis replace the software we already use?
No. Your systems of record — ERP, CRM, accounting, and the rest — stay exactly where they are. Synopsis sits on top and joins them into one place you can query, so you report across everything instead of exporting from each tool.
Where does our data live, and is it secure?
Your data stays in your own warehouse — we don't keep a copy. Access is governed per user and every query is audit-logged. Synopsis is SOC 2 Type II, and you can review our live security posture in the Trust Center.
How is this different from a BI tool or a stack of dashboards?
BI tools chart data that something else already had to clean and join. Synopsis does that upstream work — connecting your systems, resolving entities, and enforcing your metric definitions — then answers in plain English, builds the dashboards, and traces every number back to its source.
Get started
See it on your own data.
Most demos take about 30 minutes. Bring a question you've been waiting months to answer — we'll reply within 24 hours.
Book a 30-minute demo
See Synopsis run against embedded payments monetization data.
We'll be in touch within 24 hours.