Key takeaways
- PayPal Payouts needs a business account, a confirmed identity and bank account, and approved access, and PayPal names rewards as a supported use.
- Build every cashout around a unique sender_batch_id and item webhooks, and put the balance back only when an item is FAILED, RETURNED or BLOCKED.
- Fees and caps differ by the country of your PayPal account, so price your minimum cashout from your own fee page and hold earnings that can still be reversed.
Can a rewards site use PayPal Payouts?
Yes. PayPal Payouts is PayPal’s product for sending many payments at once to an email address, phone number or PayPal ID, and PayPal’s own API reference describes it as a way to send “commissions, rebates, rewards, and general disbursements.” To use it, you need a PayPal business account, a confirmed identity, email and bank account, enough balance to cover payouts plus fees, and approved access to Payouts. You then send cashouts in batches through the API (up to 15,000 payments per call) or by file upload, and track each payment through webhooks.
This guide goes deeper than our overview of rewards site payout methods: approval, the API details that prevent double payments, the fees and limits as PayPal publishes them, the policy rules that matter for a rewards (GPT) site, and how to lower the risk of a limited account. Policy and fee facts were checked on October 22, 2026.
Eligibility and approval
PayPal’s Payouts overview lists four prerequisites for every payout option:
- A PayPal business account.
- Access to PayPal Payouts, which you request on PayPal’s Payouts landing page. PayPal asks about your business needs and emails you the decision. While you wait, you can build and test in sandbox accounts.
- A confirmed identity, email and bank account linked to the business account.
- Enough funds in your PayPal balance to cover the payout total and the fees.
The same page says Payouts reach 96 countries and 24 currencies, that some countries have limited or restricted payout features, and that Venmo payouts work in the US, in USD only, with a US mobile number. Recipients who do not have an account get an email or text asking them to open one to claim the money.
The access request is where a rewards site is judged, so describe it plainly: users earn rewards for completing offers, surveys or tasks, you pay them from your own earnings, and you hold and review cashouts. Have your terms, privacy policy and payout rules live on the site before you apply. A site that reads like an income scheme, or that hides who runs it, is harder to approve and easier to limit later.
What to have ready before you request access
A live site with a clear description of how users earn, published terms that cover holds, reversals and identity checks, a support contact, the countries you serve, and a realistic estimate of monthly payout volume and average cashout size.
How the Payouts API works
The Payouts v1 API reference has four operations: create a batch payout (POST /v1/payments/payouts), show batch details, show one payout item, and cancel an unclaimed item. A batch has a sender_batch_header and an items array. Each item needs an amount and a receiver, and can carry a recipient_type (EMAIL, PHONE or PAYPAL_ID), your own sender_item_id, a note, and a purpose, which accepts values such as AWARDS, PRIZES, REBATES and CASHBACK.
POST /v1/payments/payouts
{
"sender_batch_header": {
"sender_batch_id": "cashouts-2026-10-22-0900",
"email_subject": "Your reward has arrived",
"recipient_type": "EMAIL"
},
"items": [
{
"amount": { "value": "5.00", "currency": "USD" },
"receiver": "user@example.com",
"sender_item_id": "withdrawal-48213",
"purpose": "AWARDS",
"note": "Cashout 48213"
}
]
}
sender_batch_id is your protection against paying twice
PayPal’s schema says it does not process duplicate payouts: if you send a sender_batch_id that was used in the last 30 days, the API rejects the request and links to the original payout. If you get an HTTP 5xx error, you can safely retry with the same sender_batch_id. In practice:
- Derive the batch ID from something you already store, such as a payout run ID, and save it before you call the API.
- Set
sender_item_idto your own withdrawal ID, so every webhook and report maps back to one user request. - Never retry a timed-out batch under a new ID. Look up the original first; a new ID tells PayPal it is a new payment.
- The duplicate check only covers 30 days, so keep your own unique constraint on withdrawal IDs as well. Preventing duplicate reward credits shows the same pattern for incoming credits.
A successful create call means the batch passed an initial check, and its batch_status starts as PENDING. Some values, such as phone numbers, are validated later, so a batch that was accepted can still contain items that fail.
Item statuses, webhooks and unclaimed payouts
Each item has its own transaction_status. Your ledger should react to each one:
| Status | What PayPal says it means | What your site should do |
|---|---|---|
| PENDING | Submitted and being processed | Show “sending”; keep the balance deducted |
| SUCCESS | Funds credited to the recipient | Mark paid; the money is gone for good |
| UNCLAIMED | Recipient has no account yet; returned if not claimed within 30 days | Email the user to claim it or fix the address |
| RETURNED | Funds returned, because unclaimed or because you cancelled | Put the amount back on the user’s balance |
| FAILED | Failed, and funds were not deducted from you | Put the amount back and show the reason |
| ONHOLD | Being reviewed and on hold | Wait; do not resend |
| BLOCKED | Blocked | Put the amount back and review the account before any retry |
| REFUNDED | The recipient refunded the payout | Put the amount back or close the request |
PayPal’s Payouts webhook list has three batch events (DENIED, PROCESSING, SUCCESS) and eight item events: PAYMENT.PAYOUTS-ITEM.SUCCEEDED, UNCLAIMED, RETURNED, FAILED, BLOCKED, HELD, REFUNDED and CANCELED. Batch events carry no item details, so subscribe to the item events or follow the links in the batch event to fetch each item.
According to PayPal’s webhook integration guide, your listener must answer with an HTTP 2xx, or PayPal retries each delivery up to 25 times over 3 days. Verify every message, either with the verify-webhook-signature API or by checking the signature headers against PayPal’s certificate, and never change a balance from an unverified call. As a safety net, run a daily job that fetches the status of every item still PENDING or UNCLAIMED.
Unclaimed payouts are the most common support ticket. PayPal’s Payouts FAQ says unclaimed payments expire in 30 days and the money returns to your account, that you can cancel an unclaimed payment before then, and that a recipient with an unconfirmed email cannot receive a payment. Ask users to type their PayPal email twice, and tell them to check spam for the PayPal email. Webhook vs postback explains why this outgoing side needs the same care as the incoming one.
Payouts fees and limits as published
Fees depend on the country of your PayPal account, not on where your users live. PayPal’s fees and transaction limits page says the sender pays, recipients pay nothing, the fee is a percentage (typically 2%) with a cap, and currency conversion costs extra. Two examples from PayPal’s fee pages, both marked last updated October 1, 2026:
| Your PayPal account | Domestic payout | International payout | Currency conversion |
|---|---|---|---|
| United States (US fees page) | 2%, capped at $1.00; the table lists a flat $0.25 per USD payment when using the Payouts API | 2%, capped at $20.00 | 4.00%, or another amount disclosed during the transaction |
| United Kingdom (UK fees page) | 2%, capped at 10.00 GBP | 2%, capped at 60.00 GBP | See the conversion section of the UK page |
On the US page, a flat $0.25 is more than 2% on any API payment under $12.50, and less above it. Confirm with PayPal which rate applies to your integration before you set a minimum.
Illustrative example: fee share on small cashouts
A US site pays a $3.00 cashout to a US user through the API at the listed flat $0.25: the fee is 8.3% of the payout. The same site pays $3.00 to a user abroad at 2%: $0.06, plus 4% ($0.12) if PayPal converts the currency for you. At a $10.00 minimum, the flat fee drops to 2.5%. Sample figures only, using the published US rates above; your account country and contract may differ.
Limits
One API call can carry up to 15,000 payments. PayPal says there is no limit on the total amount of a payout, but each item has a ceiling. The FAQ gives a default of $20,000 per payment, while the fees and limits page lists per-currency limits that depend on whether the recipient already has an account (for USD, 60,000 for registered and 20,000 for unregistered recipients). Rewards cashouts sit far below either figure, so the limits that matter to you are your own: per-day caps per user, caps for new accounts, and a review threshold.
PayPal policy rules that matter for rewards sites
Two documents apply: the Acceptable Use Policy (last updated October 29, 2022) and, for US accounts, the PayPal User Agreement (last updated September 14, 2026). Other countries have their own versions, so read yours. The parts a rewards site should know:
- No get-rich-quick framing. The AUP prohibits transactions that support pyramid or Ponzi schemes, matrix programs, other “get rich quick” schemes and certain multi-level marketing programs. Describe your site as a way to earn rewards for offers, not as income.
- Lottery contracts are prohibited. The AUP bans transactions associated with purchases of annuities or lottery contracts.
- Contests and sweepstakes may need approval. PayPal requires pre-approval to accept payments for gambling, gaming and any other activity with an entry fee and a prize, which it says includes games of skill and sweepstakes. The policy does not say whether entries bought with earned coins count, so ask PayPal before you pay raffle or contest prizes through Payouts.
- Virtual currency may need approval. Pre-approval also covers accepting payments for any digital representation of value, which PayPal says includes crypto currencies and virtual in-game currencies. This matters if your site also sells coin packs through PayPal.
- Fraudulent funds and linked accounts. The User Agreement’s restricted activities include sending or receiving what PayPal reasonably believes may be fraudulent funds, giving false information, refusing to confirm your identity, and controlling an account linked to another account that broke these rules.
Your own terms should say the same things in your words. Terms of service for a rewards site covers the clauses on holds, reversals and identity checks.
Account limitation risk and how to reduce it
The User Agreement says PayPal may place holds, limitations and reserves at its sole discretion, based on confidential risk criteria. It may limit an account for suspicious or unusual activity, for breaches of the agreement or the AUP, or to comply with the law, and it asks you to cooperate with requests for financial statements and documents. A limited account can stop all cashouts at once, so treat this as the main operational risk.
A rewards site becomes risky to PayPal in a few predictable ways: payouts to accounts that are obviously one person, payouts funded by offers that later reverse, sudden volume spikes, and many cashouts to countries or accounts PayPal sees as high risk. The controls that lower that risk are the same ones that protect your own margin:
- Hold earnings until they are final. Do not pay out rewards that can still be reversed by the offer source. Reward hold periods shows how to set the length by account age, amount and offer type.
- One PayPal address per person. Block a PayPal email that is already linked to another user, and flag accounts that share devices or payment details. Stop multi-accounting and VPN abuse lists the signals.
- Review first and large cashouts. The first cashout is where most fraud tries to exit. Hold it for a manual or rule-based review.
- Set KYC thresholds. Ask for stronger identity checks above a set cumulative amount, and say so in your terms before users earn. KYC for rewards sites covers how to choose the threshold.
- Grow volume steadily. Send batches on a regular schedule rather than in irregular large bursts, and keep enough balance funded so batches do not fail.
- Keep records. Store each withdrawal with the user, earning history, review decision and PayPal item ID, so you can answer PayPal quickly if it asks.
Cashout setups that invite a limited account
Paying brand-new accounts instantly with no hold, letting one PayPal email receive payouts for several users, retrying failed items under new batch IDs, paying out rewards that are still pending at the offer source, and marketing that promises users an income.
PayPal vs gift cards vs crypto
Most sites offer PayPal next to at least one other method. A short comparison:
| Factor | PayPal Payouts | Gift cards | Crypto |
|---|---|---|---|
| Cost model | Percentage with a cap, or a flat API fee, plus conversion | Set by the provider; some sell at face value | Network fee plus provider costs, both variable |
| Can you stop it after sending? | Only while UNCLAIMED | Rarely, once a code is delivered | No, transfers are final |
| What the user needs | A PayPal account in a supported country | A brand available in their country | A wallet on the right network |
| Fraud exposure | Medium: tied to a verified PayPal account | High: codes resell within minutes | High: no recovery |
| Read next | This guide | Gift card APIs for rewards apps | Cheapest crypto for payouts |
To see how payout costs change your margin per offer, try the virtual currency calculator.
Timing PayPal cashouts around Sharklio postbacks
Sharklio is a pay-per-result affiliate network: you add its offerwall to your site or app, your users earn your own currency for completed offers, and you earn per completed offer. Every credit and every reversal reaches your server as a signed server-to-server postback, so your ledger knows which rewards are still open before you put them in a PayPal batch. Users on VPNs, proxies, Tor or data center networks are blocked from the wall, and end users must be 16 or older. Publisher applications are reviewed by hand. See how the wall works, or get in touch with questions.
Frequently asked questions
Do I need a business account for PayPal Payouts?
Yes. PayPal’s prerequisites are a business account, approved access to Payouts, a confirmed identity, email and bank account, and enough balance to cover payouts and fees.
How much does PayPal Payouts cost?
It depends on the country of your account. On the US fees page (checked on October 22, 2026), domestic payouts are 2% capped at $1.00, with a flat $0.25 per USD payment listed for the Payouts API, and international payouts are 2% capped at $20.00.
What happens to an unclaimed PayPal payout?
If the recipient does not claim it within 30 days, PayPal returns the money to your account and the item status becomes RETURNED. You can also cancel an unclaimed item earlier through the API or your account.
How many payments can I send in one PayPal Payouts batch?
The Payouts API accepts up to 15,000 payments per call. There is no limit on the total amount, but each item has a per-payment ceiling.
Can PayPal limit my account for running a rewards site?
PayPal may limit any account at its discretion for suspicious activity or policy breaches. Holds on unfinished earnings, one PayPal address per user, reviews of first cashouts and clear terms all reduce the risk.
How do I avoid paying a user twice with PayPal Payouts?
Give every batch a unique sender_batch_id you store before calling the API, and retry with the same ID after a server error. PayPal rejects a reused sender_batch_id within 30 days.
Is PayPal Payouts the same as Mass Pay?
Yes. PayPal’s fee pages say PayPal Payouts includes the service formerly known as Mass Pay.