treasury-kit

The bank account money comes from, the payouts it leaves by, and the balances in between: consent checked before the network, the payout row written before the provider is called.

@quxkit/treasury-kit·in Pro, Power, Max, Enterprise

Try it as your own:

Wilson & Co. The money desk

A retry is a lookup, never a second payment

The provider hosts the consent; we keep a reference and the four digits a human already sees: never an account number. Then the discipline that matters: the payout row is written before the provider is called, so an ambiguous call is recoverable, and the same idempotency key always answers with the same payout.

1 · The account

Nothing linked yet. The hosted flow is the provider's; this button stands in for the customer finishing it.

2 · Money out

Send $250.00, then send it again with the SAME key.

0linked accounts

not yetavailable

0payout rows

0distinct payments

The actual responses (0): everything above is this data, shaped

Build with treasury-kit →

Mobile · bundle

mobile-kit

Your app on the phone rather than merely working on one: a shell that renders only the hosts you name, deep links that open it, and copy that changes without a store review.