Quick Answer
Use prepaid accounts when recipients choose the product, can enroll and can access earnings at an acceptable total cost. Use push-to-card for supported existing cards and bank payouts where those accounts better meet the recipient’s needs. Choose using delivered funds and exception handling as well as speed.
Key Takeaways
- Separate the prepaid account product from the rail used to load it.
- Compare recipient spending and cash-access costs, including fixed charges and FX.
- Existing-card payouts require route eligibility; they do not solve card issuance.
- Keep unknown attempts reserved to prevent duplicate payouts across rails.
- Pilot enrollment, usable funds, recipient support and ledger reconciliation together.
Start with the account your recipient will use#
A prepaid card can help a contractor spend earnings without opening a conventional checking account. It earns its place when the recipient can enroll, receive the card, and use the balance at an acceptable cost. A fast transfer into an inaccessible or expensive account does little for the person waiting to be paid.
Separate three decisions: whether to offer a new prepaid account, how to fund that account, and whether to send money to a card the recipient already owns. A prepaid program is an account-and-card product. ACH and card-network transfers are ways money can reach eligible accounts. Direct deposit is a use of a bank-payment rail, commonly ACH in the United States; it is not a separate competitor to ACH.
For a platform paying U.S. contractors monthly, start with recipients’ preferred destinations and the payment deadline. Add prepaid accounts for people who want that product and meet its terms. Add push-to-card for people who already have a supported card and value quicker access. Neither choice eliminates the need to track the underlying amount owed.
Compare products and transfer methods separately#
| Choice | Recipient requirement | What the platform must establish |
|---|---|---|
| Issued reloadable prepaid account | Enrollment, identity checks required by the program, and an activated card or usable virtual account | Issuer and program manager; who owns the balance; loading method; delivery; cash access; fees; limits; closure and remaining-balance access |
| Push to an existing card | An eligible debit or prepaid card accepted for the specific transfer route | Card and corridor eligibility, funding arrangements, available-funds timing, transaction limits and authoritative status queries |
| ACH credit / direct deposit (U.S.) | An eligible receiving account and validated instructions; some prepaid accounts can receive ACH deposits | Provider cutoff, ordinary or Same Day processing, recipient availability, return handling and reconciliation |
| U.S. domestic wire | A receiving bank account and correct wire instructions | Bank cutoff and charges; Fedwire finality where that service is used; recall procedures |
| Cross-border bank payout | A supported beneficiary account and currency corridor | Local or correspondent route, FX quote, intermediary deductions, recipient charges, timing and investigations |
Do not promise instant access simply because the destination is prepaid. Card delivery and activation can take longer than the subsequent load. A virtual card may support online spending while offering no physical ATM access. Confirm the exact product rather than assuming every Visa or Mastercard logo implies identical withdrawal, bill-payment or transfer features.
Visa’s developer documentation describes transfers to eligible debit and prepaid cards and a separate account-validation capability. Visa calls its credit transfer an Original Credit Transaction (OCT). Other networks use their own products and terminology. OCT eligibility does not issue a card to someone who lacks one.
For U.S. bank accounts linked to eligible debit cards, Visa announced funds availability of one minute or less starting in April 2025, subject to its qualifications. That announcement is not a worldwide prepaid-card loading guarantee. Base your customer promise on the issuer, provider, route and recipient account actually used.
When a prepaid program helps—and when it adds friction#
Consider an opt-in program for a recurring contractor cohort that wants a reusable spending account. The useful benefit may be access rather than speed: recipients can spend from the card balance, and those without a conventional bank account may have another way to receive earnings. The CFPB distinguishes reloadable, payroll and other prepaid products; their features and protections need individual review.
Before choosing a program, ask recipients how they will use the money. Someone buying supplies online needs different features from someone withdrawing most earnings in cash. Interview both groups. Check local ATM availability, withdrawal limits, whether rent and bills can be paid, replacement-card delivery, support language and access after a lost phone or blocked card.
Prepaid is a poor fit when enrollment excludes much of the cohort, recipients mainly need bank transfers the product does not support, or withdrawals and FX consume the apparent funding advantage. A fully banked recipient may still choose a card account; having a bank account alone does not settle the decision. Compare actual cost and use rather than labeling all banked recipients unsuitable.
An existing debit card can make push-to-card simpler than new enrollment, but only after eligibility checks. A card that works for purchases can still be ineligible for that payout route. Offer another supported destination when eligibility fails before submission. Once a transfer has been submitted, resolve its outcome before sending the same obligation elsewhere.
Compare the amount the recipient can actually use#
Measure loading charges, platform fees, recipient deductions, ATM charges, FX and fixed account or card charges separately. Identify who pays each one. If the contract promises $1,000 net to the contractor, a $1,000 gross load with recipient deductions may fail that promise; obtain a quote for the agreed net amount.
A public fee schedule makes this concrete. Payoneer’s pricing page, marked updated January 1, 2026 and checked October 3, lists a $29.95 annual card fee and USD cash withdrawals of $3.15 plus up to 1.8% without currency conversion, or plus up to 3.5% with conversion. Its cards are a provider-specific business-account example, not a quote for issuing your own contractor program. Fees vary by region and account; signed-in terms and third-party ATM charges also matter.
Illustrative cash-use calculation holds cash received constant: a recipient withdraws $200 four times in a month. Assume the quoted USD withdrawal charge is $3.15 plus 1.8% per withdrawal. Each withdrawal costs $6.75; four cost $27. If these fees come from the card balance, the four withdrawals require $827 of balance to deliver $800 in cash. Assume that extra $27 is already funded; an $800 gross load alone would not cover all four withdrawals. Allocate the $29.95 annual card charge across twelve months for a further $2.50 in monthly comparison cost. That is about $29.50 to access $800 in cash, before any ATM-operator fee, receipt charge or other account charge. Annual allocation is a budgeting device; the actual annual debit happens under the account terms.
For comparison, suppose your separate bank-payout quote is $1 per transfer paid by the platform, and this recipient’s bank permits those four cash withdrawals without a charge. The recipient keeps the $800 cash amount under those assumptions, while the platform pays $1. This is an illustrative quote, not a claim about standard ACH pricing or every bank. A recipient who spends online instead can reach a different result. Run both usage patterns against the candidate program’s own fee disclosure.
Payoneer also lists an annual account charge for certain low-receipt accounts; it is separate from the card charge. Do not assume a card fee is the entire account cost or apply commercial-card terms to a consumer payroll program. Establish eligibility and the exact agreement before presenting a comparison to recipients.
Choose bank rails for their own strengths#
Scheduled U.S. contractor runs often fit ACH credits because the recipient already has an account and the platform can plan around provider cutoffs. Compare ordinary and Same Day options against your deadline, actual fees and receiving-bank availability. Submission, settlement and spendable funds are distinct events; weekend, holiday and return handling belong in the operating agreement.
For a high-value domestic exception, Fedwire provides real-time gross settlement with immediate, final and irrevocable settlement once processed. That describes Fedwire settlement, not every cross-border wire’s end-to-end delivery. Bank charges, recipient details and the bank’s own submission cutoff still affect the customer experience.
For a cross-border payout, compare the delivered currency amount rather than the advertised transfer fee. Request a quote showing source amount, FX rate, recipient amount and possible deductions. A virtual account can help identify incoming funds; it does not by itself determine the outgoing payout route. See international wires versus local payout rails.
Operate one obligation through loading, holds and returns#
Give each earned-payment obligation a durable identifier. Record recipient, amount and currency, destination version, approval, funding source, provider transfer ID and request idempotency key. Persist the attempt and request key, and reserve the obligation atomically before external submission so another worker cannot pay it simultaneously. Keep the recipient’s amount owed separate from the provider’s transfer attempts.
For a prepaid program, reconcile the platform funding movement, the issuer’s account-load record and the recipient-facing available balance. A successful funding debit need not mean the recipient can spend yet. Record pending activation, compliance holds and rejected loads explicitly, with the contracted support owner and a route for the recipient to obtain status.
If the provider times out after submission, mark the attempt unknown and query it using the stored transfer ID or the provider’s supported idempotent request flow. Authenticate callbacks and deduplicate events. Do not release the reserved obligation or switch to ACH just because a response is missing. Escalate an unresolved state for investigation; a second rail could pay the same earnings twice.
Retry or change destination only after authoritative evidence shows the original attempt was not paid and cannot subsequently complete under the provider’s status semantics. Reconcile any reserved, debited or returned funding so the replacement has available funds, and approve its destination and release. Link the replacement to the original obligation, use a separate attempt identifier and enforce the same amount-owed constraint. When money is returned after a completed payout, post the return separately and confirm what remains owed before approving a new payment.
For example, a $600 card load times out but later succeeds. The ledger keeps the $600 reserved during the unknown period, consumes that obligation once on confirmed completion, and ignores a duplicate completion callback. An ACH fallback submitted during the timeout would have created a second $600 disbursement. A dashboard that calls the timeout “failed” without confirmation conceals that risk.
Agree on program responsibilities and recipient choice#
Identify the issuer, program manager and platform responsibilities for onboarding, screening, identity records, complaints, unauthorized transactions, statements and refunds. Determine which rules apply to the actual account and customer relationship. Provider onboarding checks and the platform’s tax reporting duties are separate obligations; personal foreign-account reporting and VAT-number checks are not universal prerequisites for card payouts.
If the recipients are employees rather than contractors, payroll rules become relevant. The CFPB says employers cannot require wages on a payroll card: they must offer at least one alternative, and applicable state rules affect wage access. Review the card’s disclosures before enrollment. Do not assume employee protections transfer unchanged to a commercial contractor-account product.
Ask how a recipient accesses remaining funds after suspension, closure, expiry or replacement. Document the legally permitted handling of balances, notices and any unclaimed-property obligations. A program is incomplete if support can freeze spending but cannot explain the path to recover an eligible remaining balance.
Pilot the recipient experience and the accounting together#
Choose a small opt-in cohort with different spending and cash needs. Test enrollment, activation, a normal load, a rejected load, an unknown response, duplicate callbacks, a return and a lost-card case. Finance should be able to match the approved obligation to funding records, fees and the issuer’s outcome. Recipients should be able to see the available amount and obtain help without contacting several teams.
Track enrollment completion, usable-funds timing, recipient fees, cash-access failures, unresolved transfers and support contacts. Compare these with the existing bank-payout experience for similar recipients; avoid treating a faster average as success if a minority cannot access their earnings. Expand only when the actual program improves the promised experience and exceptions reconcile.
Frequently Asked Questions
Is a prepaid card the same as push-to-card?
No. A prepaid card is an account-and-card product funded before spending. Push-to-card is a transfer to an existing eligible debit or prepaid card account. A new prepaid program still needs enrollment, activation and a loading arrangement.
Are ACH and direct deposit different payout rails?
In the United States, direct deposit commonly uses an ACH credit. Compare the account destination, provider processing option and availability promise rather than listing ACH and direct deposit as independent networks.
When should a platform offer prepaid cards?
Offer an opt-in prepaid product when eligible recipients want its spending or cash-access features and the complete fee schedule fits their usage. Compare enrollment friction, access, support and costs with an existing bank account or eligible-card transfer.
Can a failed card payout be sent immediately through ACH?
Only after the original attempt is conclusively unpaid and cannot later complete under the provider’s status rules. A timeout is an unknown outcome, not proof of failure. Keep the obligation reserved while querying or investigating the original transfer. Reconcile the original funding and approve the replacement destination and release before sending again.
Which fees belong in the comparison?
Include account and card charges, receipt or load fees, purchases, ATM withdrawals, FX, replacement and third-party charges. Separate platform costs from recipient deductions and model how the recipient actually spends or withdraws the money.
Try a related tool
Researched and edited by the Gruv editorial team. Gruv builds cross-border billing, payouts, and finance-operations software for global businesses.
Sources
Includes 3 external sources outside the trusted-domain allowlist.
- consumerfinance.gov/consumer-tools/prepaid-cards/choose-the-righ...trusted
- consumerfinance.gov/ask-cfpb/are-there-fees-to-use-a-payroll-car...trusted
- federalreserve.gov/paymentsystems/fedfunds_about.htmtrusted
- developer.visa.com/use-cases/enhanced-funds-transferexternal
- payoneer.com/pricingexternal
- usa.visa.com/about-visa/newsroom/press-releases.releaseId...external
Educational content only. Not legal, tax, or financial advice.
Related Posts

Gift Card Payouts for Platforms When to Use Gift Cards vs Cash
For payout decisions, keep the rule simple: use gift cards for discretionary incentives. Default to direct deposit (ACH) when money is owed for work. If a payment settles an obligation rather than rewards behavior, start with a cash rail and make any exception earn extra review.

When Platforms Should Use Wires vs Local Rails for Cross-Border Payouts
Treat rail choice as product logic, not team habit. No rail wins everywhere. SWIFT and local payment rails solve different payout risks, so your job is to route each payout by destination, currency, speed, and cost, not by whichever option sounds more global or more modern.

When Instant Payout Matters for Gig Platform Payments
Instant payout is a tool, not the goal. The real operating decision is where instant timing creates measurable value, where batch timing is enough, and where both should run side by side.

