Build on Wrenbase · Embed
A headless, composable AP/AR engine. All API, no UI.
Clean REST primitives, organizations, clients, vendors, invoicing, payments, and screening, that you compose into exactly the money platform your users need, under your own brand. You build the experience; we run the ledger and the rails.
Embedding is available through a direct arrangement. Talk to us and we'll set it up for your product.
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 client 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, clients, 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
Your users send invoices from inside your product, styled as yours.
Payments
Collect and record payments on the same rails Wrenbase runs on.
Vendor intake
Bills come in through a branded link, screened before they land.
The ledger
Money in and out on one ledger, so nothing needs reconciling.
Your brand
Sender-facing surfaces carry your logo, not ours.
Your data model
Tie every invoice and payment back to the objects in your app.
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
Embedding is a partnership
Tell us what you're building.
We fit embedding to your product and your users, so it starts with a conversation, not a signup form.
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, clients, 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.
- How much shows the Wrenbase brand?
- As little as you want. The experience is yours to style, and the sender-facing surfaces carry your brand. Wrenbase runs the engine in the background.
- 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 and white-label are handled as a direct arrangement so we can fit it to your product and your users.