How Global Payouts with USDC Work, Step by Step

USDC IN PLAIN WORDS

What USDC is, and what it is not.

USDC is a digital dollar issued by Circle. In Circle's words, “USDC is a fully reserved stablecoin, which is a type of cryptocurrency designed to maintain steady value.” Circle also says “USDC is a digital dollar backed 100% by highly liquid cash and cash-equivalent assets and is redeemable 1:1 for US dollars,” and that it “publishes monthly reserve attestations by a Big Four accounting firm.”

Redeemable 1:1 describes redemption through Circle itself. Circle's USDC Terms say that when Circle redeems USDC for dollars it does so at one dollar per USDC, “less fees where applicable,” and add: “Circle does not guarantee that the value of one (1) USDC will always equal 1 USD ($1) on other platforms.” Your recipients will convert through a wallet app or exchange of their choosing, at that provider's price and fees.

A stablecoin is not a bank account. Circle's terms state: “Virtual currency is not legal tender, is not backed by the government, and accounts and value balances are not subject to Federal Deposit Insurance Corporation or Securities Investor Protection Corporation protections.” USDC aims to hold the value of a dollar; it is not a bank deposit and carries no deposit insurance.

WALLETS AND ADDRESSES

What a wallet and a wallet address are.

A wallet holds the keys that control money on a blockchain. A wallet address is the public side, a little like an account number you can share: on Base and other Ethereum-compatible networks it is 0x followed by 40 letters and digits. Anyone can send to an address. Only whoever holds its keys can send from it.

Self-custody means you hold those keys, not a company. SET Private Wallets use Privy, whose security documentation says: “Our systems are non-custodial by design, ensuring that only authorized users can access their keys through sophisticated key splitting and secure execution environments.” When you sign in with your email, Privy creates your wallets, and every send from them needs your approval. SET never holds, signs or moves your funds.

NETWORKS

Why the network matters: Base.

USDC exists on many blockchains, which people also call networks or chains, and a send on one network arrives only on that network. SET payouts send USDC on Base, which Circle describes as “a secure, low-cost, builder-friendly Ethereum L2.” USDC on Base is the token contract Circle lists for Base, 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913, and SET checks every send against that contract.

Here is the catch. Base, Ethereum, Arbitrum, Optimism, Polygon and other Ethereum-compatible networks all use the same style of address, and one address can exist on all of them. An address that looks right tells you nothing about which network your recipient's app is watching. So ask each recipient for an address that accepts USDC on Base, and have them confirm the network in writing as well as the address.

If a recipient gives you an address from an app or exchange that does not support USDC on Base, the USDC still lands at that address on Base, but their app may never show it. A recipient who holds the keys to that address can reach it with a wallet app that supports Base. If an exchange or another company controls the address, getting it back is up to that company, and it may not be possible. Circle's terms put the general rule plainly: “USDC transactions are not reversible. Once you send USDC to an address, you accept the risk that you may lose access to, and any claim on, that USDC indefinitely or permanently.”

The cheapest insurance is a test. Send 1.00 USDC, the smallest payout SET allows, to each new recipient, and pay the rest once they confirm it arrived.

NETWORK FEES

Network fees: keep a little ETH on Base.

Every blockchain charges a small fee to process a transaction, often called gas. Base's documentation explains: “Every Base transaction consists of two costs: an L2 (execution) fee and an L1 (security) fee.” Base lists ETH as its currency, and the fee is paid in ETH, not in the USDC you are sending.

So the wallet you pay from needs a small amount of ETH on Base as well as the USDC for the batch. SET does not pay network fees for you today. You can buy ETH on Base with a card through Stripe's onramp inside your wallet, from $10 per purchase (Stripe decides eligibility), or have someone send a little ETH on Base to your wallet address.

You see the fee before you pay it: Privy's confirmation screen shows an estimated network fee for each send before you approve it. In my staging test on Base Sepolia, Base's test network, Privy showed an estimated fee of “<$0.01” per send. That was a test, not a price. Fees move with network demand, so read the estimate on each approval.

FINALITY AND CONFIRMATIONS

When a payout is final, and why SET waits for three confirmations.

A send is final once the network records it. There is no chargeback and no recall: no one at SET or Privy can undo it, and Circle's terms say USDC transactions are not reversible.

Base records new transactions in blocks, a few seconds apart. Its documentation says: “After roughly 2 seconds, the sequencer has built the transaction into an L2 block and distributed it to validator nodes,” and “After roughly 2 minutes, a Base batch containing the transaction has been posted to Ethereum.”

Each block added after the one holding your send is a further confirmation. SET marks a payout “Paid, confirmed on chain” only after three, and only after reading the transaction itself: it must come from your wallet, go to that recipient and move exactly that amount of USDC on Base. A send that went elsewhere or for a different amount shows “Send did not match: check and resend”, and one the network rejected shows “Send failed on chain: resend”. SET checks each send as soon as your wallet reports it, and checks any send still confirming again every 10 minutes. The screen you clicked on never decides that a payout was paid; the chain does.

STEP BY STEP

How to send a payout batch in SET.

The whole flow runs inside your SET Private Wallet, at /wallets or wallet.simpleeasytransactions.com. Payouts use only your wallet: SET records the list and checks the chain, and every send is yours to approve.

1. Sign in with your email. Privy creates your wallets; your Base address is the one listed under Ethereum, Base, Polygon, Avalanche.
2. Fund the wallet with USDC on Base, in any of three ways: buy it with a card through Stripe's onramp, $10 to $500 per purchase, with no SET fee; send money from your bank to your own account number from Bridge, set to deliver USDC on Base, for SET's 3% deposit fee; or receive USDC on Base from anyone who has your address.
3. Add a little ETH on Base for network fees.
4. Prepare your list: one recipient per line, with the wallet address, the amount in USDC and, if you like, a private reference such as an invoice number. Commas, semicolons or tabs separate the fields, and a header line is skipped. Use the template below.
5. Paste the list and choose Check and record batch. SET checks every line and your balance before anything is recorded, and nothing is sent at this step.
6. Approve each send. Use the Send remaining button, one approval each, or send one line at a time. Privy shows each payment, with the amount and recipient, and you approve it in Privy's own confirmation screen. You can stop after any send.
7. Track each line as it moves from Not sent to Confirming on chain to Paid, confirmed on chain, with a link to the transaction on Base's block explorer.
8. Choose Download report (CSV) and keep the file with your books.

address,amount,reference
0xRECIPIENT_1_BASE_ADDRESS,250.00,Invoice 1042
0xRECIPIENT_2_BASE_ADDRESS,75.50,March design work
0xRECIPIENT_3_BASE_ADDRESS,1200.00,Q3 partner share

THE RECIPIENT'S SIDE

What your recipient sees, and what they can do with USDC.

Your recipient does not need a SET wallet or an account with SET. They give you an address that accepts USDC on Base, and the USDC appears there when the send is confirmed. SET asks them for nothing: no sign-up and no identity check by SET.

With the USDC they can hold it as digital dollars, send it on, use it wherever USDC on Base is accepted, or convert it to their local currency through a wallet app or exchange they choose, at that provider's rates and fees and under the rules of their country.

Recipients in the US can open a SET Private Wallet of their own and cash USDC on Base out to their US bank by ACH through Bridge, 5 to 1,000 USDC at a time, for SET's 3% fee. In Bridge's words, “ACH funds typically land in 1–2 banking days.”

SET does not pay recipients' bank accounts in local currency today. Converting is the recipient's choice and their provider's service.

WHAT IT COSTS

What a payout costs.

SET charges no fee per payout. Your SET Payouts plan sets how many people you can pay each month: Free for up to 5, Starter $29 a month for 25, Growth $99 a month for 100. Each send pays the Base network fee in ETH, which Privy shows before you approve. Getting USDC into your wallet can cost something: Stripe shows its own fees on a card purchase, and SET's 3% applies to bank deposits. Your recipient may pay their own provider to convert USDC to local currency.

For comparison with sending money abroad the usual way, the World Bank tracks the cost of what it calls “sending and receiving relatively small amounts of money from one country to another.” Its Remittance Prices Worldwide site, last updated August 18, 2025 and read on October 2, 2026, says: “Globally, sending remittances costs an average of 6.36 percent of the amount sent.” That figure covers small personal transfers, not business wires, and it is an average, not your bank's price. For a fair comparison, put your own bank's wire fee and exchange-rate margin next to the network fee Privy shows you, plus whatever your recipient pays to convert.

RECORDS, TAX AND COMPLIANCE

Records, tax and compliance stay with you.

SET gives you a record of what was sent; it does not give tax or legal advice. Who you pay, why, and how you report it are your responsibility as the payer. The CSV report carries your reference, the amount, the status and the transaction hash for every line, which is the evidence most bookkeeping needs.

For contractors in the US, the IRS says: “If you've made the determination that the person you're paying is an independent contractor, the first step is to have the contractor complete Form W-9, Request for Taxpayer Identification Number and Certification.” The same IRS page explains when Form 1099-NEC reports nonemployee compensation. The IRS's digital assets page covers people paid with digital assets, and reminds taxpayers that the law requires them “to maintain sufficient records to establish the positions taken on federal income tax returns.”

For recipients outside the US, the IRS publishes Form W-8 BEN, the Certificate of Foreign Status of Beneficial Owner for United States Tax Withholding and Reporting (Individuals). Whether you need one from a recipient is a question for your advisor.

Sanctions rules apply to stablecoins as they do to dollars. Asked whether OFAC compliance obligations differ for digital currency, OFAC answers: “Yes, the obligations are the same.” OFAC's Sanctions List Search lets you check a name before you pay. Talk to an accountant or lawyer about your own situation before your first batch.

RISKS

Risks: what SET's checks catch, and what they can't.

Most stablecoin losses come from a wrong address, a wrong network or a slip in the amount. SET checks each list line by line before anything is recorded, and each refusal names the line to fix:

• Every address must be a Base wallet address: 0x followed by 40 hexadecimal characters.
• The zero address and the USDC contract itself are refused, because USDC sent there is lost.
• Your own wallet is refused as a recipient.
• A recipient listed twice is refused; combine the amounts into one line.
• Amounts must be in whole cents, from 1.00 to 2,500.00 USDC each.
• A batch pays at most 50 recipients and 10,000.00 USDC in total, and never more than your wallet's USDC balance.
• No payout is sent twice: before each send the page re-reads the batch and skips any payout already confirming or paid.

WHAT NO CHECK CAN CATCH

What SET cannot protect you from.

A check can tell that an address is well formed. It cannot tell whose it is. SET cannot catch a valid address that belongs to the wrong person, a typo that still forms a valid address, an address on an app or exchange that does not support USDC on Base, or an amount you meant to be different. Those are settled between you and your recipient, before you approve.

Three habits cover most of it: get each address in writing from the recipient with the network named, confirm it through a second channel such as a call, and send a 1.00 USDC test to every new recipient.

LIMITS

Limits, and what SET does not do.

• Up to 50 recipients per batch, 1.00 to 2,500.00 USDC each, and 10,000.00 USDC per batch.
• USDC on Base only. Payouts do not send other coins or use other networks today.
• One approval per recipient. A whole batch cannot be approved at once today.
• You pay network fees in ETH on Base; SET does not sponsor them today.
• SET does not pay bank accounts in local currency, convert currency for recipients, or hold funds for you.
• SET does not collect recipients' names, tax forms or identity. Your references stay in your browser and your downloaded CSV, so keep the CSV: a different browser or device will not show them.
• Sends are final.

FIELD NOTES

What I've learned building this.

• The list is checked line by line before anything is saved, and every refusal names its line. In production the batch is also checked against the wallet's USDC balance before it is recorded.
• The server stores only addresses and amounts. References such as invoice numbers stay in your browser and in the CSV you download, so SET never keeps a list of your payees' names.
• Before each send the page re-reads the batch, and it keeps each transaction hash in your browser until the server records it. A dropped connection after a send leads to a Report send button, not a second payment.
• A payout is marked paid only after the server reads the transaction from Base: from your wallet, to that recipient, exactly that amount, three confirmations deep. A scheduled check runs every 10 minutes for any send still confirming.
• Payouts went live in production on October 2, 2026, after a staging test on Base Sepolia, where Privy showed an estimated network fee of “<$0.01” per send.

HOW TO CHOOSE

How I'd choose.

• Use USDC payouts when your recipients already use USDC on Base, or are glad to, and you want to pay many of them from one list with one report.
• Use your bank when a recipient needs local currency in a bank account, or cannot receive USDC on Base.
• Before your first real batch, send 1.00 USDC to each new recipient and ask your accountant how to record the payments.

SOURCES

Where these facts come from.

Sources checked on October 2, 2026. Providers change their products and rules, so the linked pages are the final word.

• Circle: USDC
• Circle: USDC Terms (last updated December 12, 2025)
• Circle: USDC on Base
• Circle Developer Docs: USDC contract addresses
• Base Docs: Network fees
• Base Docs: Transaction finality
• Base Docs: Connecting to Base (chain ID 8453, currency ETH)
• Privy Docs: Security
• Stripe Docs: Stripe fiat-to-crypto onramp
• Bridge Docs: Processing windows & cutoff times
• World Bank: Remittance Prices Worldwide (last updated August 18, 2025)
• IRS: Forms and associated taxes for independent contractors
• IRS: Digital assets
• IRS: About Form W-8 BEN
• OFAC: FAQ 560, digital currency and OFAC compliance obligations
• OFAC: Sanctions List Search