One review.
Every detail.
Compare recipients, destination networks and amounts side by side. Catch a mistake before it becomes a transaction.
One workspace to compose a batch, review the total and follow each transfer. A clearer way to move value.
Make a batchCompose. Review. Run the simulation.
It is the complete picture of what you are about to send.
Compare recipients, destination networks and amounts side by side. Catch a mistake before it becomes a transaction.
See the payment total and estimated network fees together. Batching simplifies the workflow; it does not make network fees disappear.
Completed, processing or needs attention: each transfer has its own outcome. Retry a failed item without resending the successful ones.
Our ambition is an interface that works across all blockchains. Each connection needs its own tested integration, assets and settlement rules.
Check the complete batch before execution. The demo flags duplicate recipient names and invalid amounts.
Planned production checks would surface address risks and network mismatches before a transfer is authorized.
Separate completed transfers from failed ones. Try the failure scenario in the payment desk to see a targeted retry.
Concept controls, not a security guarantee. Real protection requires tested integrations, reliable risk data and independent implementation review. Confirmed blockchain payments are generally irreversible.
No. This is an interactive product concept. Values, fees and statuses are simulated locally in your browser. It does not connect wallets, inspect actual addresses or move funds.
Not necessarily. The batch is a shared workflow. A production route may require multiple transactions and wallet signatures, particularly across different networks. A single interface does not make cross-chain execution atomic.
The demo keeps successful payments marked as complete and lets you retry only the failed one. Production recovery would require checking confirmed on-chain status before retrying to prevent duplicate sends.
That is the long-term compatibility goal. Each blockchain has different transaction formats, assets, signing rules and settlement behavior. Actual support would be limited to specifically implemented and tested integrations.
You can edit a batch before confirming the simulation. A real transaction may be cancellable before broadcast in some workflows, but confirmed blockchain payments generally cannot be reversed by the interface.
Many payments. One move.