For enterprise & platforms
Put the money engine
inside your own product.
Give your customers invoicing, payments, and vendor intake without building any of it. Reach Wrenbase over a REST API and a live MCP server, and wire in sanctions screening, PO validation, and your own rules.
Your platform
Wrenbase engine · embedded
API · MCPInvoice sent
INV-4021 · $8,400
Payment recorded
ACH · settled
Vendor bill screened
Sanctions · PO · rules
Your customers never leave your app.
What you get to build with
One engine. Your product on top.
Embed the money engine
Invoicing, payments, and vendor intake run inside your product. Your customers never leave your app to get paid or pay a bill.
Reach it over API and MCP
Drive the whole AP/AR engine from your code over REST, or from an AI assistant over MCP. Same engine, same permissions, either way.
Wire in your own checks
Screening is pluggable. Run the sanctions and country checks Wrenbase ships, validate a PO, add your own verification rules, or all of it. Nothing gets paid outside the checks you set.
Every ingest, checked
Nothing skips the checks because it came from code.
A bill pushed through the API goes through the same screening as one typed in the app. Sanctions and country checks run on the way in, your own rules run next to them, and only then does it reach the ledger.
So an integration can't quietly slip an unchecked payable into a customer's workflow.
{ vendor: "Pixel Forge", amount: 3400 }
Screening gate
Cleared, on the ledger
One tenant per key
An API key is scoped to a single organization and never reaches another tenant's records.
Data stays separated
One customer on your platform can't see another's invoices, vendors, or payments.
Your permissions, applied
The API and MCP honor the same roles and limits a person would have in the app.
For your engineers
Two doors to the same engine.
Inside your product
What your customers actually see.
Your brand, your app, the money workflow running underneath. They never learn there's a second tool.
Send an invoice
Your users bill their clients from inside your product, on a page styled as yours.
Get paid
Card and bank payment through Stripe, recorded against the invoice automatically.
Take in a bill
Vendors submit through a link, screened before it reaches your user's inbox.
Common questions
What platform teams ask.
- What does 'embed the money engine' mean?
- If your customers already run their business on your platform, you can hand them the money workflow too, and skip building AP/AR yourself. Wrenbase runs the engine in the background while your product stays the thing your customers see.
- How do we reach Wrenbase?
- Two ways, same engine. A REST API you call from your own code, and an MCP server an AI assistant can drive directly. Invoices, payments, contacts, and the ledger are all reachable either way, with your permissions and screening applied.
- Can we plug in our own checks?
- Yes. Screening is a layer you configure. Run the sanctions and country checks Wrenbase ships, add purchase-order validation and your own verification rules, and every ingest goes through them before anything is paid. Wrenbase does the screening it ships; identity and business verification to a compliance standard is something you run or bring, and we give you the hook to wire it in.
- How is our customers' data kept separate?
- Every record is isolated to its organization. An API key is scoped to one tenant and never reaches another tenant's data, so one customer on your platform can't see another's invoices or vendors.
- How do we start?
- Read the API and MCP docs to see the surface, then talk to us about the embedding arrangement. Volume, white-labeling, and support are worked out directly with you.
Build your money platform
on our engine.
Read the docs, then talk to us about embedding. A human answers.