Skip to content

Menu

  • payments@example.com
  • security@example.com

Basis · treasury infrastructure

Treasury operationsthat close themselves.

Basis settles payouts, holds multi-currency balances, and posts every movement to a double-entry ledger your finance team can close from — no spreadsheet in between.

  • Settlement volume · 12 months

USD settled monthly · 38 markets

12.4B
Label Value
Jul 8.6
Aug 9.1
Sep 9.8
Oct 10.4
Nov 11.6
Dec 12.4
  • SOC 2 Type II
  • PCI DSS Level 1

In production

The four numbersfinance teams check first.

Pulled from the last full month across every account on the platform. The same figures sit in your dashboard the day you go live.

Monthly payouts cleared

4.1M

Median month-end close

11min

Held in customer balances

1.4B

Bank and rail partners

62

Integration

Three weeks fromsandbox key to first close.

Connect

Pull a sandbox key, point one endpoint at it, and replay last month's payout file against production behaviour.

Model

Map your entities, currencies and fee logic onto the ledger with an implementation engineer in the room.

Close

Run the first month in parallel with your old process, reconcile both ledgers, then switch the spreadsheet off for good.

Who builds on Basis

Four money flows,one settlement layer.

Split a single buyer charge across sellers, platform fee and tax withholding at capture time, then pay each party on the rail that clears fastest in their country. Sellers see a balance, not an invoice queue.

Median seller payout: same day in 31 markets.

Issue held balances to your customers, sweep them into your own treasury on a schedule, and keep every movement attributable to an entity your auditor can trace. Multi-entity from the first API call.

24 currencies held without a new banking partner.

Disburse advances the hour they are approved, collect repayments on a mandate, and post interest accruals to the ledger nightly so your loan tape and your bank balance never disagree.

Disbursement to borrower account in under 4 minutes.

Fund one pooled account, run a payment file of any size against it, and get per-employee failure reasons back instead of a batch rejection. Contractor and employee flows share one ledger.

99.4% first-attempt success on cross-border runs.

What controllers say

The people who close the bookswere the hardest to convince.

We closed February in a morning. The part I did not expect was being able to explain a variance to our auditor from the ledger itself, without asking engineering to pull anything.

Nadia Okafor Controller · Wefare Marketplace

Disbursements used to be a batch we watched. Now the loan tape and the bank balance agree every morning and nobody on my team looks at a spreadsheet to prove it.

Priya Raghavan CFO · Northpeak Lending

Three banking partners became one integration. Our FX exposure is finally a number I can look at on a Tuesday instead of a reconstruction at quarter end.

Théo Marchand VP Finance · Sablier

Per-employee failure reasons instead of a rejected file. That single difference took our payroll support tickets down by about two thirds.

Ivan Petrov Financial Operations · Latterly

Idempotent endpoints and a sandbox that actually fails the way production fails. We shipped the payout flow in nine days and have not touched it since.

Daniel Reiss Head of Payments · Kettlebridge

Held balances across four entities, swept nightly, attributable end to end. I stopped keeping a shadow ledger about six weeks in.

Marcus Aiyeola Group Treasurer · Halden Group
Start in a sandbox

See your own settlement curve.

Bring last month's payout file. We will replay it against production behaviour on a call and show you what the close looks like on the other side.
  • SOC 2 Type II
  • PCI DSS Level 1
  • ISO 27001
  • GDPR and UK GDPR