Fusion Payments — The interface sheet
Four surfaces, opened to the spec level.
The same four interfaces the homepage files in miniature, opened up: what each surface is for, what moves across it, and what the scoping question is.
INT-01
CRM & practice systems
Transactions and payer records pushed into the system your team already works in — a CRM, a practice-management system, a field-service platform — so nobody re-keys a payment into a second screen. The push is one-way out of the rail and idempotent: a retry never creates a duplicate record. Built today: Zoho, Salesforce and anything else Zapier reaches — through Zapier, the REST API and signed webhooks, not a direct connector, and we say so.
- push:
- txn + payer → the record your team works in
- timing:
- on capture
- shape:
- one-way, idempotent — retries never duplicate
Scoped in phase 02 — Which system, which record types, and what happens when the system is down.
INT-02
Accounting & reconciliation
Transaction and deposit workflows built to survive month-end: fees broken out rather than buried, deposits matched to the transactions that made them, and an export your bookkeeper can sign off on — a QuickBooks Online import file included today — without a weekend in spreadsheets.
- match:
- transaction ↔ deposit
- timing:
- at settlement · survives month-end
- artifact:
- a reconciliation your bookkeeper signs
Scoped in phase 02 — Chart of accounts, fee treatment, and who owns the month-end close.
INT-03
Ecommerce operations
Catalog, order, and fulfillment connections around the payment event, so an order placed online moves through pick, ship, and settle as one chain — and a refund unwinds the same chain instead of leaving three systems disagreeing about one sale.
- chain:
- order → fulfillment → settle
- timing:
- event-driven
- unwind:
- refunds walk the same chain backwards
Scoped in phase 02 — Order lifecycle, inventory source of truth, and refund behavior.
INT-04
ISV & embedded payments
Payment capability inside someone else's software: your product takes the payment, your customers onboard as sub-merchants, and Fusion carries the processing relationship, the boarding path, and the compliance surface underneath your roadmap.
- embed:
- payments inside your product
- includes:
- sub-merchant onboarding
- for:
- software companies and platforms
Scoped in phase 02 — Onboarding flow, funding model, and where support calls land.
* No vendor logos on this page on purpose. The connections that exist — Zapier, a QuickBooks Online import file, and Zoho and Salesforce through Zapier and the API — are named in plain text. Everything else is claimed per system, in a signed spec — not by a logo wall.
