A payout batch is the one operation where a mistake is irreversible and expensive. This gig gives you a dry run: before anything is signed, the system tells you exactly what will happen.
What you get:
- A dry-run endpoint and report for your payout file: how many rows will go out, how much reaches recipients, how much leaves the account once fees are added.
- Rows that will NOT go out, listed separately with the reason and the exact shortfall per row: an address from the wrong network, a balance that runs out partway down the file, a precision mismatch.
- Idempotency done properly: keys derived by the server, replays that prove they are the same operation before returning the old result.
- Tests that plant a hostile record under a taken key and assert the refusal.
Built for real: a payment rail across Bitcoin, Ethereum/ERC-20, Tron/TRC-20 and TON, with batch payouts and recurring charges.
What I need from you: your payout flow as it exists, and one sample file.
Delivery: ten working days.
