Blog
Notes on building
with digital assets.
Product updates, security deep dives and practical guides from the team that builds Valtu.
Featured · product
Introducing Valtu: wallet infrastructure you can verify
Wallets for every customer, deposits that are credited only when final, payouts your own team approves, and keys held in hardware enclaves you can check yourself.
Read the post →
bitcoin · payouts
Stuck Bitcoin payouts: how replace-by-fee gets them moving
When Bitcoin fees jump after a payout is sent, it can sit unconfirmed for hours. Replace-by-fee resends the same payment with a higher fee, without paying twice.
operations · fees
Why token payouts need gas, and how a gas wallet handles it
A wallet holding only USDT can't send USDT: every token transfer pays its network fee in the network's own coin. A gas wallet tops wallets up automatically, within limits you set.
custody · security
Choosing wallet infrastructure: 12 questions to ask any provider
Before you trust a provider with customer funds, ask how keys are held, who can move money, what happens on bad days, and what they can prove. Here are the questions, with our own answers.
developers · python
The Valtu Python SDK is on PyPI
pip install valtu: a signed API client, webhook verification and enclave attestation checks for Python 3.9 and later, with the same behavior as the TypeScript wallet kit.
networks · developers
One address, five networks: how EVM deposit addresses work
With Valtu, a customer's 0x address is the same on Ethereum, BNB Chain, Polygon, Base and Lisk. Here is why that works, and what it means for deposits sent on any of them.
tron · fees
TRON energy and bandwidth, explained for payment teams
USDT on Tron is cheap to move, but only if you understand energy. Here is what energy and bandwidth are, what happens without them, and the options for paying less.
operations · deposits
Deposit sweeps explained: moving customer funds to your treasury
Thousands of customer deposit addresses each holding a little is hard to manage and spend. Sweeps collect confirmed deposits into one wallet on a schedule you set.
payments · stablecoins
Deposit addresses or payment links: two ways to take stablecoin payments
A permanent address per customer suits top-ups and balances. A payment link suits invoices and checkouts. Here is when to use each, and how both work with Valtu.
stablecoins · networks
USDT on Tron, Ethereum or BNB Chain: which network should your customers use?
The same dollar token lives on several networks, with different fees, speeds and address formats. Here is how to choose which ones to offer, and how to keep customers from sending on the wrong one.
payouts · developers
Sending crypto payouts at scale: batches, approvals and limits
Paying hundreds of sellers or employees in USDT is mostly an operations problem: never paying twice, getting the right people to approve, and keeping a wallet's queue moving.
custody · security
Custodial wallet infrastructure or self-custody: what a fintech actually needs
Running your own keys gives full control and full responsibility. Custodial infrastructure takes the key work off your team. The real question is who can move funds, and how you can check it.
compliance · security
Screening crypto deposits and payouts with your own KYT provider
Connect your own Elliptic, Chainalysis, Blockaid or Webacy account: Valtu screens payout destinations before signing and deposit senders as deposits arrive, and holds risky ones for your team.
security
Verify the code that holds your keys
"Trust us" isn't a security model. How attestation and reproducible builds let anyone check what's running inside Valtu's enclaves, and what is still to come.
payments
Accepting stablecoin payments: a practical setup
A wallet layout, matching rules and settlement schedule for taking USDT and USDC payments, plus the shortcut of hosted checkouts if you'd rather not build the screen.
developers · payouts
Never pay twice: retry-safe payouts with externalId
Timeouts happen. With one field, a retried payout returns the original instead of sending the money again. How idempotency works in the Valtu API, including batches.
security · payouts
How a payout gets signed: policy, approvals, enclave
Every payout on Valtu takes the same path: your policies decide, your team approves with passkeys, and only then does the enclave sign. Here is each step.
developers
Webhooks you can trust: verify, de-duplicate, reconcile
Webhooks tell your server what happened on-chain. Three habits make them safe to build on: check the signature, de-duplicate by event id, and reconcile with the API.
networks · deposits
When is a deposit final?
Seeing a transaction isn't the same as being able to rely on it. How Valtu decides a deposit is final on each network, and the one status your ledger should credit on.
Building something with Valtu?
Start with a free test workspace, or talk to the team about your use case.