Skip to main content
Every capability below works the same way on any account a token belongs to: personal or business, yours or a connected customer’s. A handful of onboarding operations require a specific account type. They’re listed in How accounts work.

Funding sources

Link bank cards and bank accounts via Plaid, then pull funds on demand.

Wallets & transfers

Spend accounts, deposits, withdrawals, and internal or cross-account transfers.

Virtual cards

Spend controls, lock/unlock, PINs, wallet provisioning, and bulk issuance up to 10,000.

Card status, locks & limits

What each card status means and how to read a card’s current limit.

Gift cards

Thousands of brands, offer comparison, stock checks, and discount pricing.

Open loop cards

Generate hosted card links that recipients claim, with full link lifecycle control.

Send money

Look up recipients by phone or email and transfer funds, including rewards, to other Fluz wallets.

Transactions

Query all activity and annotate with memos, categories, and attachments.

Approvals & requests

Request manager approval for cards, transfers, purchases, and limit changes.

Authorized users

Add team members, issue them cards, and route approvals.

Go deeper

API reference

Every query, mutation, and type in the GraphQL schema.

Code examples

Copy-paste scripts for single operations: tokens, cards, money movement.

Changelog

Recent updates, additions, and breaking changes.
Building for customers instead? Every capability on this page works identically on connected accounts. Send a customer-scoped OAuth token instead of your own. You’ll need an OAuth Integration application that Fluz has activated. See Build a platform.