Skip to content
Book a walkthrough

Menu

Book a walkthrough
  • payments@example.com
  • security@example.com

Search

A rail, a market, a rate.

The platform, in full

Everything that moves money posts to the same ledger.

Book a walkthrough
See the rate sheet

Four services, one record. You can adopt them in any order most teams start with payouts and pull treasury in once the balances get large enough to matter.

  • Payments
  • Treasury
  • Compliance
  • Developer API

The platform

Four services, one ledger of record.

Payments

Accept and pay out in 24 currencies through one integration, on local rails wherever they clear faster.

Median settlement 0.4s

Treasury

Hold, convert and sweep balances across entities on a schedule, without a spreadsheet in the loop.

24 currencies held

Compliance

KYB, sanctions screening and an audit trail your reviewers can read without booking a call.

SOC 2 Type II · PCI DSS L1

Developer API

Typed SDKs, idempotent endpoints and a sandbox that mirrors production behaviour, not a mock of it.

First call to live in 6 days

How it runs

Three surfaces your teamactually works in.

block-tech-app-1
01 Onboarding

Your entities, modelled once

An implementation engineer maps your legal entities, currencies and fee logic onto the ledger with you, in a shared sandbox. Nothing goes to production until last month's payout file replays clean against it.

See the integration steps
block-tech-laptop-1
02 Payouts

One call, the fastest rail

Send a payout intent and Basis picks the rail that clears soonest in the beneficiary's country, retries on the right failure codes, and returns a reason your support team can read when it cannot.

Read the rate sheet
block-tech-saas-1
03 The close

A month you can sign off

Every movement is double-entry with a rail reference, an FX timestamp and an entity attribution. Finance closes from the ledger and exports the same figures the auditor asks for.

Talk to an engineer

What comes with it

Support that reads the ledger too.

A named engineer

One person who knows your entity model, from the sandbox key through your first signed-off close.

  • Shared Slack channel
  • Four-hour response, business hours

Uptime you can cite

A public status page with per-rail history, and SLA credits written into the contract rather than the sales deck.

  • Per-rail incident history
  • Webhook alerts on degradation

An audit pack, quarterly

Attestations, penetration test summaries and the reconciliation evidence your reviewers ask for, sent before they ask.

  • SOC 2 Type II report
  • Nightly reconciliation evidence
Pick a starting point

Most teams begin with payouts.

Tell us which rails you clear on today and we will scope the first service, the sequence for the rest, and what your close looks like at the end of it.
Book a walkthrough Read our story