Free tool
Batch payout CSV builder
Add or paste one row per payee and the builder checks each wallet address, amount and currency, totals the batch per currency and writes a CSV to download. It can write the three columns Hanko's payout importer reads (address, amount and email) or a fuller planning sheet, and it puts an apostrophe in front of any cell that starts with =, +, - or @ so a spreadsheet shows it as text instead of running it as a formula.
The example payees, addresses and amounts are made up. Building or downloading a file does not create a payout or send any money.
Add payout rows
The four rows below are examples, with made-up payees and addresses. Replace them, add rows one at a time, or paste rows from a spreadsheet. Everything you enter stays in this browser tab. It is not saved or sent, and reloading the page clears it.
Copy cells from Excel or Google Sheets, or paste CSV text. A first line with column names such as payee, address, amount, currency, memo and email is matched by name.
The file is read in your browser and put in the paste box. It is not uploaded.
Used when you add a row or paste rows without a currency column. Rows already in the list keep theirs.
Payout rows
4 of 500 rows. Skip to the summary and download
Batch summary
4 payout rows: USDC 3,730.50 across 3 rows and EUR 900.00 across 1 row.
- Rows in the batch
- 4
- Currencies
- 2
| Currency | Rows | Total |
|---|---|---|
| USDC | 3 | USDC 3,730.50 |
| EUR | 1 | EUR 900.00 |
Download the CSV
A Hanko payout batch sends one token, chosen in the app, so the file has no currency column. Import it into a payout that uses the token in the file name, and download one file per token.
Excel needs it to show accented and non-Latin names correctly when it opens a CSV. Hanko's importer and most other tools ignore it.
Preview hanko-payout-import-usdc.csv (3 rows)
address,amount,email 0x1111111111111111111111111111111111111111,1250.00,studio@example.com 0x2222222222222222222222222222222222222222,480.50, 0x3333333333333333333333333333333333333333,2000.00,
How the builder checks each row and totals the batch
Each row needs a recipient, an amount and a currency. The payee name and memo are for the people reviewing the batch, and the email is the optional third column of Hanko's import file. Rows that are completely empty are ignored.
- Recipient. A value starting with 0x is read as an EVM address and must be 0x followed by 40 hexadecimal characters; the zero address (0x and forty zeros) is rejected because a payment sent there cannot be recovered. A value of 32 to 44 base58 characters is labeled a Solana-format address. Anything else, such as a bank or contractor reference, is kept as a reference.
- Amount. It must be above zero and have no more decimal places than its currency allows: two for USD, EUR or GBP, none for JPY and three for KWD; six for USDC, USDT and EURC; eighteen for DAI and ETH. An amount with extra decimals is flagged, not rounded. A leading $, € or £ is dropped when it fits the row's currency and flagged when it does not, so $1,250 in a EUR row has to be corrected.
- Currency. An ISO 4217 code such as USD or EUR, or one of the token symbols USDC, USDT, EURC, DAI and ETH.
- Duplicates. Two rows with the same recipient get a warning on both (EVM addresses are compared without regard to letter case). A warning does not block the download, because two payments to one person can be intended.
For each currency c, the total is the sum of the valid rows in that currency: T(c) = a₁ + a₂ + … + aₙ, with n the number of those rows. The amounts are added as exact decimals, never as floating-point numbers, and nothing is converted between currencies. Because no amount is rounded, the amounts in the downloaded file add up to the total on screen.
The file writes each amount as a plain number with no symbol or thousands separator. ISO currencies get their own number of decimal places, so 1250 USD becomes 1250.00 and 5000 JPY stays 5000. Tokens get at least two decimal places and as many more as the amount needs, so 1250 USDC becomes 1250.00 and 0.125 USDC stays 0.125. A batch can hold up to 500 rows, the size of one Hanko crypto payout batch.
The columns Hanko's payout importer reads
The payout form in the Hanko app has an Import CSV button in its Recipients section. The importer looks for three columns by name, and falls back to recognising them from the data when the names differ:
| Column | Required | What the importer does with it |
|---|---|---|
address | Yes | The recipient's wallet address. A row with a missing or invalid address is reported and skipped. |
amount | Yes | The amount to send, as a plain number. A row with a missing or invalid amount is reported and skipped. |
email | No | Used to notify the recipient. |
Imported rows are added to the payout's recipient list, where they can still be edited or removed. The network and token are chosen once for the whole payout in the app, so the file has no currency column, and the builder writes one import file per token. The importer reads every amount as that token, so rows in a currency such as USD or EUR are not written to an import file: 900 in a EUR file imported into a USDC payout would be sent as 900 USDC. Those rows stay in the planning sheet. Batch payouts check every recipient as an EVM address before they run, so the import layout only takes rows whose recipient is an EVM-format address.
On Pro, a business can pay up to 500 recipients in one crypto payout batch, adding them manually, from contacts or by CSV. Single-transaction batches run on Ethereum, Base, Arbitrum and Optimism where the batch contract is configured.
The planning sheet has the columns payee, recipient, recipient_format, amount, currency, memo, email. It is for reviewing and approving a batch, and it is not an import format. If it were uploaded to the payout importer anyway, the importer would read its recipient and amount columns and ignore the currency column, so a row in another currency would be imported as an amount of the payout's token. Upload the import layout instead.
Verified businesses can send USD bank payouts by ACH or wire in batches of up to 200 recipients, using Hanko's CSV format. That bank file is a different layout, with 16 columns including the account holder, routing and account numbers and the recipient's postal address, and its template is downloaded inside the Hanko app. This builder does not ask for bank account details and does not write that file.
How the file is protected against spreadsheet formulas
Spreadsheet programs treat a cell that starts with =, +, - or @ as a formula, and a crafted formula in a payee name or memo can change what the sheet shows or try to open a link when someone opens the file. This is known as CSV or formula injection, and OWASP's description of it recommends the defence used here. Every cell that starts with one of those characters, a tab or a carriage return, or with spaces followed by one of them, is written with an apostrophe in front. Spreadsheets then show the value as text. The apostrophe stays in the file, so a payee typed as -Studio reads '-Studio when the file is opened in a text editor.
Cells that contain a comma, a double quote, a semicolon, a tab or a line break are wrapped in double quotes, and a double quote inside a cell is written twice, as RFC 4180 describes. Lines end with a carriage return and line feed, and the text is UTF-8. The optional byte order mark is for Excel, which otherwise misreads accented and non-Latin characters in a UTF-8 CSV.
| Typed in a payee or memo | Written to the file |
|---|---|
=SUM(A1:A9) | '=SUM(A1:A9) |
+44 20 7946 0000 | '+44 20 7946 0000 |
@vendor-team | '@vendor-team |
Smith, Jones & Co | "Smith, Jones & Co" |
The "Q4" retainer | "The ""Q4"" retainer" |
Zoë Müller | Zoë Müller |
Worked example: four example payees paid in USDC and EUR
The builder opens with these rows. The payees, wallet addresses, bank reference and email are made up.
| Row | Payee | Recipient | Reads as | Amount |
|---|---|---|---|---|
| 1 | Example Studio Ltd | 0x1111111111111111111111111111111111111111 | EVM address | USDC 1,250.00 |
| 2 | Example Creator | 0x2222222222222222222222222222222222222222 | EVM address | USDC 480.50 |
| 3 | Example Developer | 0x3333333333333333333333333333333333333333 | EVM address | USDC 2,000.00 |
| 4 | Example Translator | EX-BANK-0042 | Other reference | EUR 900.00 |
Three rows are in USDC: 1,250.00 + 480.50 + 2,000.00 = USDC 3,730.50. One row is in EUR, for EUR 900.00. The batch has 4 rows in 2 currencies, and the two totals are kept apart because nothing is converted.
The Hanko import file for USDC has 3 rows. Row 4 is not in it, because it is in EUR and its recipient is a bank reference rather than an EVM address. The amounts are written with two decimal places, and the missing emails are left as empty cells:
address,amount,email
0x1111111111111111111111111111111111111111,1250.00,studio@example.com
0x2222222222222222222222222222222222222222,480.50,
0x3333333333333333333333333333333333333333,2000.00,The planning sheet keeps all four rows with every column, which makes it the one to send to whoever approves the batch:
payee,recipient,recipient_format,amount,currency,memo,email
Example Studio Ltd,0x1111111111111111111111111111111111111111,EVM address,1250.00,USDC,Example: October design retainer,studio@example.com
Example Creator,0x2222222222222222222222222222222222222222,EVM address,480.50,USDC,Example: campaign video,
Example Developer,0x3333333333333333333333333333333333333333,EVM address,2000.00,USDC,Example: sprint 14,
Example Translator,EX-BANK-0042,Other reference,900.00,EUR,Example: contract translation,No cell in this example starts with a formula character, so no apostrophes are added.
Pasting rows from a spreadsheet
Cells copied from Excel or Google Sheets arrive separated by tabs, and the builder uses tabs whenever the first line has one. Otherwise it splits on commas, or on semicolons when the first line has more semicolons than commas, which is how Excel saves a CSV in locales that write decimals with a comma. Quoted cells can contain commas, quotes and line breaks. A line break inside a cell becomes a space, because each field is a single line.
When the first line has at least two recognised column names, columns are matched by name: for example payee or name, recipient, address or wallet, amount, currency or token, memo, note or reference, and email. Other columns are ignored and listed after the paste. Without a header, a first cell that looks like a wallet address means the order address, amount, email (the order of Hanko's own sample file), and anything else is read as payee, recipient, amount, currency, memo, email. Rows without a currency take the currency chosen for new rows.
An amount written as 1,250 is rejected rather than guessed, because it means 1250 in some spreadsheets and 1.25 in others. Write 1250, or 1,250.00 with a decimal point. Pasted rows beyond the 500-row limit are not added, and the message after the paste says how many were left out.
Choices to make before you download
- The layout. Download the import layout to upload into a Hanko payout, and the planning sheet for review, approval or your own records. You can download both from the same rows.
- One file per token. A Hanko payout sends one token on one network, so a batch with USDC and USDT rows becomes two import files and two payouts. Import each file into a payout that uses the token in its file name. Rows in a currency such as USD or EUR go in the planning sheet only; to pay them from an import file, enter them as a token amount instead.
- Rows that are not EVM addresses. Bank references and Solana-format addresses stay in the planning sheet and need another payment method. Hanko's bank payouts (USD by ACH or wire, and EUR by SEPA one payment at a time) are open to verified businesses only.
- Duplicate recipients. Decide whether two rows to the same address are two payments or one payment entered twice, and combine them if it is the second.
- The byte order mark. Turn it on if the file will be opened in Excel and has accented or non-Latin names. It does no harm to Hanko's importer.
- Address confirmation. Compare each address with one the payee sent you in writing. The builder checks the format, not who owns the address.
Assumptions and limitations
- The address check is about format only. It does not confirm that an address exists, belongs to the payee or can receive the token on the network you choose, and it does not verify the mixed-case checksum some EVM addresses carry. A Solana-format label only means the length and characters fit.
- Amounts are used as entered. The builder adds no network fees, exchange rates or processing costs, and it never converts one currency into another.
- Listing a currency or token here does not mean Hanko can pay out in it. The app decides which tokens and networks a payout can use.
- Downloading a file creates nothing in Hanko and moves no money. Payouts are created and sent from inside the app.
- Rows stay in this browser tab and are not saved. If analytics are on, the page records that the builder was used, copied or downloaded, with at most a currency code. Names, addresses, references, amounts and emails are never sent.
- The builder holds up to 500 rows, which is the most recipients one Hanko crypto payout batch takes. Split a larger list into several batches.
Related tools, templates and guides
Tools
- Contractor payout cost calculatorEstimate a contractor payout run's cost by group, currency and method, per recipient and per year, and check each route against Hanko's payout records.
- Commission split calculatorSplit a campaign or deal total between people by percentage or fixed amounts so the shares add up exactly to the total.
- Influencer campaign payout calculatorWork out each creator's campaign payment from fixed fees, performance bonuses you define and deductions, as an itemized schedule.
Guides
- What are batch payouts?A plain-language definition of batch payouts and how Hanko sends many payments at once.
- How to Pay Contractors in StablecoinsA practical, step-by-step guide to invoicing and paying contractors in USDC and other stablecoins.
- How to run payroll in cryptoA step-by-step guide to paying your team in stablecoins, with on-chain confirmation and fiat off-ramps.
- Global payoutsGuides to paying contractors in stablecoins or by bank transfer, running batch payouts and planning payout costs from the workspace that holds your client invoices.
Import the file into a Hanko payout
Sign up or sign in, create a payout in your Hanko workspace and choose Import CSV in the Recipients section. You pick the network and token there and can edit or remove rows before anything is sent. Creating a payout needs a workspace admin and a plan that includes payouts. Rows from this page are not carried over, and nothing on this page sends money.