An agency pays two populations on the same cycle. One is a core team on fixed recurring amounts. The other is a project-based bench whose names and amounts change from cycle to cycle. Payroll tooling built around a fixed roster handles the first well and the second badly, so the bench is paid outside that system, as separate manual transfers.

Crypto payroll for agencies treats both populations as rows in one recipient list. Each row carries its own recipient, amount, asset, and network, paid in stablecoins or crypto. The list can be different every cycle without becoming a different process.

Crypto payroll for agencies is the disbursement step of a pay cycle. It takes an approved list of people and amounts and moves each amount to a wallet address in stablecoins or crypto. The agency still runs its own payroll calculation and classification decisions in its existing system.

EukaPay's crypto payouts

cover the send and nothing before it.

A fixed-roster system stores the roster and expects edits. A mixed roster is not an edit; it is a different list. Uploading a recipient list as a CSV in the merchant dashboard makes the list itself the input, so a list unlike the last one is still one upload.

On the core team the amount repeats every cycle. On the bench it is whatever the project approved, and the same person can be paid a different amount each time they appear. Each line on the recipient list carries its own amount.

A bench recipient may be paid once and not appear on the next list. A system that provisions people requires setup before that recipient can be paid. In a list, that recipient is one row for one run, sent alongside

contractor and affiliate payouts

.

Recipients on the same list may want different assets. EukaPay sets asset and network per payout, so one line can be USDC on Ethereum and the next USDT on Tron. Your own recipient list carries both fields.

Project work is approved between cycles. An approval made after a run has been sent can be paid without rebuilding the run. A single payout covers one recipient, and the Payout API creates payouts programmatically, one payout per request.

EukaPay gives an agency three ways to send the same payout run, and a mixed roster can use more than one.

On the dashboard route the uploaded list is validated and shown with its recipients and amounts before anything is sent.

Payouts run on the same EukaPay account an agency uses to collect from clients. Collections and payouts use the same account. On the pay-in side that account gives you instant crypto-to-fiat conversion at a locked exchange rate to remove all crypto volatility, protection against chargebacks, support for a wide range of cryptocurrencies, and settlement in USD, EUR, GBP, CAD to your bank account.

EukaPay sends payouts in USDC, USDT, ETH, and BTC, on Ethereum, Tron, and Bitcoin. You top up the crypto payout balance before a run. Each payout carries its own reference that can be looked up. An agency paying

freelance talent sourced through marketplaces

puts those recipients in the same run as the core team.

Getting to a first run means

signing up

, completing verification, providing your legal business information, and generating an API key. A staging environment is available so a developer (or coding agent) can build against the payout endpoints at

docs.eukapay.com

. For a fuller walkthrough, read the

stablecoin payroll guide

.

Can one run pay salaried staff and freelancers together?

Yes. Salaried staff and freelancers go on the same list. Every recipient goes in one file, and each line carries its own amount, asset, and network.

Does the list have to be the same every cycle?

Every cycle can carry a different list. The uploaded recipient list is the input to the run, so recipients and amounts change freely between runs.

Does EukaPay calculate what each person is owed?

No. Your agency calculates what each person is owed in its existing system. EukaPay moves the approved amounts to the wallet addresses on your list.

Which assets can we pay a bench in?

EukaPay sends payouts in USDC, USDT, ETH, and BTC, on Ethereum, Tron, and Bitcoin. Asset and network are set per payout, so recipients in one run can differ.

Do we need a developer (or coding agent) to send a run?

No. The CSV upload in the merchant dashboard needs no code. A developer (or coding agent) is only needed to create payouts through the Payout API.

Can the Payout API send a whole run in one call?

The Payout API creates one payout per request, so your system makes a request per recipient. To send a prepared list in one action, upload a CSV.

How do we pay someone after the run has gone out?

Send a single payout for that recipient. It draws on the same crypto payout balance.

Can we pay a freelancer in fiat through EukaPay?

No. Fiat settlement reaches your agency's own bank account in USD, EUR, GBP, CAD. Recipients are paid in stablecoins or crypto to the address on your list.