Build on Wrenbase · Embed
Be the money backend your app never has to build.
Building an app your users run their business on? Power the whole money side on Wrenbase, headless and fully white-labeled, down to the emails your users send. They never learn there's a second system underneath.
Embedding is available through a direct arrangement. Talk to us and we'll set it up for your product.
Just automating your own Wrenbase account instead? Developers & API →
New invoice
In YourAppPowered by Wrenbase
Screened
Chapter 1 · The gap
Your users keep leaving to get paid.
They run their work in your product, then jump to a separate tool to invoice a customer or pay a vendor. That handoff is where the money workflow breaks, and where a competitor's logo shows up in their day. Embedding keeps the whole thing inside your app.
Chapter 2 · Headless by design
All engine. No opinion on your UI.
Wrenbase ships no screens for you to bend into your product. You get the AP/AR engine as composable REST primitives: organizations, customers, vendors, invoicing, payments, and screening, each an endpoint you call from your own frontend. Your design system stays yours. There's no iframe to theme and no widget that looks like someone else built it.
- API-first: every capability is an endpoint, not a prescribed screen.
- Your frontend, your framework, your components.
- The engine handles the ledger and rails you'd never want to build.
Your frontend
Wrenbase engine
no UI shippedLedger
Payment rails
Screening on ingest
Chapter 3 · Under your brand
A full money workflow, wearing your logo.
Invoicing & payments
Your users invoice and get paid from inside your product, on the rails Wrenbase runs.
Quote-to-cash
Lightweight quotes that convert to invoices and follow through to paid, no separate CPQ.
Financial CRM & ledger
Customer and vendor records that build themselves on one ledger, so nothing needs reconciling.
Vendor management
Vendor intake, records, and screening on the bills their vendors send, all under your app.
Intelligence
Cash position, who pays late, margin per project, ready to surface in your own dashboards.
White-label, incl. email
Invoices, pay pages, and the emails your users send all carry your brand and your sending domain. Wrenbase never shows through.
Chapter 4 · Protection included
You don't have to build screening.
Every bill and vendor that moves through your embedded experience is screened the same way it is in the Wrenbase app. Sanctions checks and rules run on the way in, so your users get the protection and you never write the fraud logic yourself.
How screening works →Your product
The experience your users see and touch.
Wrenbase, underneath
Ledger
Payment rails
Screening on ingest
Common questions
Quick answers.
- What does embedding Wrenbase mean?
- Your customers get invoicing, payments, and vendor intake inside your product, under your brand. You call the Wrenbase API, and the AP/AR engine, ledger, and screening run underneath. Your users never leave your app.
- Is Wrenbase a headless AP/AR engine?
- Yes. In composable mode Wrenbase ships no user interface of its own. Every capability, organizations, customers, vendors, invoicing, payments, and screening, is a primitive you compose into exactly the experience your users need. Reach those primitives through the REST API from your own frontend, or through MCP from an AI assistant, whichever fits how you build. Either way the engine handles the ledger, rails, and screening you'd never want to build yourself.
- What's the difference between Workspace and composable?
- Same engine, two ways in. Workspace is our hosted app for businesses who want a ready-made experience. Composable is the headless API for businesses who'd rather build their own on top of the primitives. Both run on the same ledger and the same screening underneath.
- Who is this for?
- Vertical SaaS, marketplaces, and platforms your customers run their business on. If your users already manage their work in your product and keep leaving to invoice or pay someone, embedding closes that gap.
- Can I white-label Wrenbase under my own brand?
- Yes, fully. The embedded experience is yours to style, and every sender-facing surface carries your brand: the invoices, the payment pages, and the emails your users send, delivered from your own sending domain rather than ours. Your customers never see Wrenbase. The exact setup is part of the arrangement we work out with you.
- Does screening still apply?
- Yes. Every bill and vendor that flows through an embedded experience is screened the same way it is in the Wrenbase app. You get the protection without building it.
- Who holds the money and the compliance?
- Payments run on the same rails Wrenbase uses, and funds never touch your balance sheet unless you choose an arrangement where they do. We work the details out with you directly, since embedding is a partnership, not a self-serve toggle.
- How do we get started?
- Talk to us about what you're building. Embedding is handled as a direct arrangement so we can fit it to your product and your users.
Tell us what you're building.
Embedding is a partnership. We fit it to your product and your users, so it starts with a conversation, not a signup form.