Arc
Arc Technical Briefing
Published September 20, 2022
Supported by Modern Treasury , IowaEDA and Brale
Overview
Arc is a B2B financing platform for software companies, pairing Arc Advance (revenue-based financing) with Arc Treasury (a deposit account for the same customer profile). This briefing walks through the Arc customer onboarding flow — NDA, API credentials for banking, accounting, and billing — and the unified data model Arc has built across all three. Live demos connect Capital One via Plaid sandbox, accounting data via Codat, and billing via Stripe, with each sync landing in Arc's GraphQL backend as canonical data events. Behind the scenes, Arc normalizes data across multiple aggregators per domain using virtual SQL views, preserves raw provider data for traceability, and optimizes connector selection for long-term stable recurring connections — because Arc re-syncs this data continuously to monitor risk on outstanding balances and surface upsell opportunities.
0:00 Introduction to Arc — B2B financing for software companies
Arc is a B2B financing platform for software companies. The team started with Arc Advance (revenue-based financing) last year and recently launched Arc Treasury (a deposit account for the same customer profile) to create an integrated financing plus banking experience.
1:30 Customer onboarding — NDA and API credentials
The Arc signup flow: sign an NDA so customers feel safe sharing financials, then request API credentials for banking, accounting, and billing providers — three independent data domains Arc needs to underwrite.
2:30 Multiple aggregators per data domain
Arc connects to multiple providers per data type — banking is the most mature aggregator space, accounting is growing, and billing / subscription providers (Stripe, Recurly) are the newest frontier. Arc picks the best connector per customer's bank.
3:00 Plaid sandbox — Capital One OAuth
Live demo connecting a Capital One account through the Plaid sandbox. Behind the scenes Arc's GraphQL backend records the bank connection, company, and user and receives asynchronous Plaid webhooks as transactions sync.
4:30 Codat for accounting, Stripe for billing
Same pattern applied to accounting (Codat sandbox on a medium US company syncs balance sheet and P&L updates) and billing (a Stripe test key connects in one step, with invoice history syncing over a longer window).
7:00 Underwriting decision and financing offer
After data syncs, Arc's dashboard surfaces a financing offer with cost and maximum limit. Customers can fund into their existing bank account (ACH delay) or Arc Treasury (instant upon approval, no onboarding re-KYC if already set up).
9:00 Unified data model over banking, accounting, and billing
Arc normalizes data from every connector into a canonical schema — ARN-style unique IDs, merchant cleanup, shared data events — so the backend services operate on a single model while raw provider data is preserved for traceability.
11:00 Continuous sync, risk monitoring, and upsell
Because Arc carries outstanding balances, it selects connectors optimised for long-term stable recurring connections (webhook-driven updates), not just one-off underwriting. The same data powers risk monitoring and future-opportunity discovery.
13:00 Virtual SQL views and the unified architecture
Arc unifies data using virtual SQL views (chosen for tooling compatibility across their TypeScript ORM and Luca analytics stack) with a plan to move to materialized tables for performance as volume grows.
Presented by Raven Jiang — Arc · LinkedIn · website
Topics: Data Infrastructure, Lending, Capital Markets
