Not a payments API. A treasury platform per vertical.
A horizontal money-movement API hands you rails and a ledger, then leaves the vertical's actual money rules — the fuel tax, the lien-waiver gate, the three-way trust reconciliation — for you to build. DigitalTreasury ships those too.
The treasury stack is the part you can't afford to get wrong.
Building it in-house
Multi-rail integrations, a ledger that reconciles to the cent, KYB/AML/OFAC, return handling, dual approval, audit — months of work and a treasury team most software companies can't staff, before you've shipped a single vertical feature.
A horizontal treasury API
Gives you the primitives — rails, accounts, a ledger — which is real leverage. But the vertical's money logic and the operator's daily app are still yours to design, build and run on top.
DigitalTreasury
The primitives and the vertical: the money rules, the refusal discipline, and a white-labeled ops app per market — so a new product is a configuration on a proven engine, not a rebuild.
Horizontal API vs. vertical treasury platform.
| Capability | Horizontal API | DigitalTreasury |
|---|---|---|
| Multi-rail payments & ledger | ✓ | ✓ |
| Vertical money rules (tax, gates, retainage) | Build it yourself | Built in, per vertical |
| White-labeled operator app | — | Ships per vertical |
| Refuses to act on unverified numbers | — | By design |
| New market to live | A build | A configuration |
A vertical isn't done until the operator's whole day is.
Fuelry, the flagship, is a 16-screen operations app: daily agent settlements, fuel-tax determination per authority, BOL matching, supplier and dealer invoices, margin by site and grade, and a go-live gate that will not pass on demo data. That's the bar for every vertical — not just "you can call an ACH endpoint."