● FINANCIAL LEGO · COMPOSE YOUR OWN STACK
Build the payments stack
your product actually needs.
Snap accounts, cards, payouts, and policies together into your own recipe. Prompt Cursor, Lovable, or Bolt and ship your stack tonight.
click a brick to try it
📥 inbound · 📤 outbound · 🏦 base
↑ every brick is a feature — add, scope, or remove anytime
your baseplate (live sandbox)
click a brick or type a command. Type reset to start over.
no idea what to build?→ scroll down and fork a stack that already works.
9 stacks · filters · detail · fork
Backed by & built with
● HOW CUSTODY WORKS · ON-CHAIN · YOU + US
Who holds the money?
You do. We co-sign.
Every Bloque account is a smart account on-chain. You have a key. We have a key. Both sign or nothing moves. Adding a brick gives just that brick permission to do one specific thing — nothing more.
The three properties
- 01You can't get locked out. Your key alone can pull everything out.
- 02We can't move money alone. Our key only signs what your rules allow.
- 03Every brick is its own scoped key. Kill it and that feature goes dead — your money stays put.
● EACH BRICK = A SCOPED KEY
Adding a brick = giving it permission.
Run plugin.add card and you create a key that can only do one thing: charge this account for card auth, up to your limit. Nothing else.
can do
- •debit main for card auth
- •only at google.com
- •max $100 / week
cannot do
- •move to another account
- •change its own limits
- •touch any other brick
$ bloque plugin.revoke card --account main
revokes the signer · balance untouched
can do
- •credit main on ACH/wire receipt
- •write the routing + acct no.
cannot do
- •debit anything, ever
- •initiate outbound transfers
- •see other brick's activity
$ bloque plugin.revoke us_virtual --account main
routing number burns · prior deposits stay
can do
- •transfers over $10k
- •need approver cfo@
- •2-of-3 if > $100k
cannot do
- •Bloque won't co-sign violations
- •runs on-chain, auditable
$ bloque policy.show transfer --account main
policy is a brick too — revocable
✦ if Bloque disappears
Your owner key is sufficient to recover funds from any account. We publish an open-source bloque-rescue tool that lets you move everything to an address of your choice without us. We've ratcheted this commitment on-chain.
✦ if you lose your key
Designate 3 guardians (founders, lawyer, another signer). 2-of-3 can rotate your key. Bloque can't do this alone — we just co-sign the rotation once guardians approve on-chain.
● STACK GALLERY · FORK & SHIP
Don’t start empty.
Start from a proven stack.
Each stack is a baseplate + bricks + the exact CLI. Fork one, swap bricks, rename, run it in sandbox, promote to live.
How a stack works
A stack is a script of bricks. Fork it to get an editable copy — your names, your limits, your policies.
Creator ops
Solo founder, 3 cards, on-chain top-ups
Solo founder · 3 cards · on-chain top-ups
The CLI · paste into your terminal
$ bloque account.create --name main $ bloque plugin.add card --account main --label ads --weekly-limit 100 --website google.com $ bloque plugin.add card --account main --label saas --monthly-limit 2000 $ bloque plugin.add polygon_deposit --account main
Money flow
inbound plugins · balance ledger · outbound plugins · transfers between accounts are free & instant
What you get
- one USD account
- 2 scoped cards (ads, saas)
- onchain USDC top-ups
Swap bricks
Policies included
- cards: site-locked only
- new plugin → approval
Community
Built a stack others should use? Submit it.
● Section · Fork flow
From template to production in 4 steps
01 · FORK
Clone the stack
Makes an editable copy of commands under your workspace.
02 · RENAME
Your names & limits
Swap main for acme, set real limits.
03 · SANDBOX
Dry-run the whole stack
Nothing leaves your workspace. See every brick land.
04 · PROMOTE
--env production
Same commands. Real rails. Signed tape.
● Section · Compare stacks
Which stack fits you?
| stack | accounts | cards | rails | best for |
|---|---|---|---|---|
| Creator ops | 1 | 2–3 | polygon_deposit | solo founder, first $100k |
| LatAm payouts | 1 | 0 | us_virtual · pix · bre-b | payroll / vendor payouts in BR+CO |
| On-chain treasury | 1 | 1 ops | polygon · offramp | crypto-native cos, mixed fiat |
| Multi-entity | 3+ | optional | us_virtual · internal | HoldCo / OpCo / Payroll |
| Team spend | 1 | 12+ | card-only | expense management, MCC rules |
| Marketplace escrow | N per-seller | 0 | inbound_ach · pix out | marketplaces, event-driven releases |
| SaaS billing reconcile | 1 | 1 vendor | us_virtual · qbo_sync | Stripe payouts, auto-book into QBO |
| Global contractor payroll | 1 | 0 | us_virtual · wire · ach · pix · bre-b | paying 100+ contractors across regions |
| Crypto OTC desk | N per counterparty | 0 | polygon · on/off-ramp · wire | OTC trading desks, bidirectional USD↔USDC |
● Section · Anatomy of a stack
What’s inside every stack
us_virtual · polygon · inbound_ach · onramp
funds flow IN
pure balance ledger · can transfer to other accounts
your baseplate
card · pix · bre-b · wire · offramp · qbo_sync
funds flow OUT
Accounts do:
- hold a balance
- transfer to other accounts (free, instant)
- carry name + metadata + policies
Accounts don’t do:
- receive external funds
- issue cards
- send to external rails
→ that’s what plugins are for
Plugins do:
- move funds in OR out of an account
- each plugin ≈ one rail / product
- composable, removable, scoped by account
● Section · Remix recipes
Small tweaks, big effect
Each recipe = swap or add a brick to adapt a stack.
6 recipes · keep going →
Recipe · Add auditor
Read-only auditor on any stack
$ bloque role.add auditor --scope read
Recipe · Swap BR → CO
Same stack, different country rail
$ bloque plugin.remove pix --account payroll $ bloque plugin.add bre_b --account payroll
Recipe · Freeze cards on alert
Webhook gates all issued cards
$ bloque webhook.add --on fraud.detected \
--run "bloque card.freeze --account main --all"Recipe · Split rent
Sub-account for one recurring bill
$ bloque account.create --name rent
$ bloque transfer.schedule --from main --to rent \
--amount 3200 --cron "0 0 1 * *"Recipe · Pre-fund the card
Isolate spend from treasury
$ bloque account.create --name cards_only $ bloque plugin.add card --account cards_only $ bloque transfer --from main --to cards_only --amount 5000
Recipe · Dual approvers on wires
Any wire > $25k needs two
$ bloque policy.add wire \
--over 25000 --approvers cfo@,founder@ --quorum 2● Section · Build from scratch
Stack Builder · 3 questions, 1 stack
No template fits? Answer 3 things, we generate the script.
What funds the account?
Pick your inbound plugin(s).
Where does money go?
Pick your outbound plugin(s).
Who's allowed what?
Pick policies & roles.
# generated from your picks $ bloque account.create --name acme $ bloque plugin.add us_virtual --account acme $ bloque plugin.add card pix --account acme $ bloque policy.add transfer --over 10000 --approver cfo@
builds into sandbox first
From beta developers
What builders are saying
“Shipped a full payment flow in our app over a weekend. The SDK just does what you'd expect.”
Alex R.
Indie hacker
“We replaced three integrations with one Bloque SDK call. Cross-border payouts that actually work.”
Sofía M.
Startup CTO
“Pasted the prompt into Cursor, hit run, and had cards issuing in under 10 minutes. Not kidding.”
Daniel K.
Freelance developer
● Who it’s for
Bricks for every seat at the table
FINANCE LEAD
See the whole stack at a glance
- every brick · one page
- policies visible
OPS ANALYST
Fork a stack, swap a brick
- template → production
- dry-run included
FOUNDER
Day 1 to production
- live rails in minutes
- audit from brick one
FAQ
Common questions
No. Accounts can only transfer to other accounts in your workspace (free, instant). External money movement always goes through a plugin — card, pix, us_virtual, polygon_deposit, offramp, etc.
The rail goes dormant — no new inbound or outbound — but historical activity stays on the ledger. Balance isn’t affected. You can re-add the plugin later.
Plugins are always scoped to an account. You can add the same plugin to multiple accounts — each gets its own rail instance (own routing number, own card PAN, own deposit address).
They’re ledger entries inside Bloque — zero fees, instant, no rail hop. Policies can gate amount, approver, and destination.
You do. Every account is a 2-of-2 smart-account on-chain. Your key alone can move everything out; Bloque’s co-signer only signs what policy allows. If we disappear, an open-source bloque-rescue tool moves your funds to any address without us.
No. Bloque holds the regulatory licenses so you don’t have to. You compose stacks; we handle KYC, AML, and compliance at the plugin boundary.
US (us_virtual, wire, ACH), Brazil (pix), Colombia (bre-b), plus stablecoins on Polygon. More LATAM rails are rolling out through 2026.
Ready to build?
Get a sandbox API key and ship your first payment flow today.