Failed and unclaimed affiliate payouts: the three causes, the 30-day rule and what to tell the affiliate

By Jimi Barkway · Published 6 September 2026 · Part of the blog

What happens when an affiliate payout fails?

In shortOne of three things, and they need different fixes. PayPal or Wise refuses the payment, usually because your balance is short. The affiliate never claims it, usually because the email has no account behind it. Or the details were wrong, and the money bounces. In every case the money is still yours. What varies is how long you wait to find out.

A payout fails when PayPal or Wise says no. It also fails when they say yes and the money never lands. Both happen in most programs eventually. I read PayPal's own pages, our two integration pages and our payouts guide on 6 September 2026. I noticed that the three causes below cover almost every case they describe.

Two rules before the detail. First, a payout is never lost. A refused payment never left. An unclaimed payment comes back. A bounced payment is sent back by PayPal or Wise. Second, the affiliate does not know any of that. Not unless you tell them. The last section is the message to send.

Why do payouts fail?

In shortMost often, the balance. PayPal Payouts draws on your PayPal balance and nothing else. It will not take a shortfall from a linked bank or card. If the balance is short, PayPal refuses the whole batch. The other causes are an email with no account behind it, an unconfirmed email, and bank details with a typo.

The balance rule surprises founders every time. AffiliateRail's PayPal integration page puts it plainly. "Your PayPal balance, and nothing else. PayPal will not take a shortfall from a linked bank or card. So the balance has to cover each batch plus PayPal's fee before the payout date." Let's say your batch is 30 payouts totalling $2,400 and your balance holds $2,000. PayPal refuses the whole batch. "Nothing is half sent." You top up the $400 plus the fees and send again. Our payouts guide names an underfunded balance as "the usual" cause of a failed payout. It is the one you can prevent with a calendar reminder.

The second cause is the recipient's side. PayPal's own FAQ lists three reasons a recipient says a payment never arrived. An incorrect email address. An unconfirmed email address, because "your recipient cannot receive a payment with an unconfirmed email address". And a payment email that went to spam. In that case, PayPal says, the recipient can "log in to PayPal to view the payment". Once an email is confirmed, the payment appears "within a few minutes". Two of the three need you to cancel and resend. The unconfirmed email is the affiliate's to fix. None of them costs you the money.

The third cause is a bank account that does not exist as typed. On Wise the transfer bounces days later. AffiliateRail's Wise integration collects bank details in the partner's own portal "with the same checks Wise applies". So "a typo becomes an error on their screen rather than a failed payout three days later". That is the general principle. Catch the wrong detail at the moment the affiliate types it, when they are looking at it. Not at payday.

What does "unclaimed" mean, and what happens after 30 days?

In shortOn PayPal, an unclaimed payment is one sent to an email address with no PayPal or Venmo account behind it. PayPal notifies the recipient that money is waiting. If nobody claims it within 30 days, the money is returned to your account. You can cancel an unclaimed payment yourself before then. Then you resend it to the right address.

PayPal's processing page describes the whole cycle. "When your payout is successfully processed, recipients that already have a PayPal or Venmo account get their payment instantly. Recipients without a PayPal or Venmo account receive a notification that a payment is available. If a payment is unclaimed after 30 days, the money is returned to your account." The FAQ adds the lever you hold in the meantime. "You can only cancel payments that have an unclaimed status. Unclaimed payments will automatically expire in 30 days, and PayPal will return the money to your PayPal account."

So an unclaimed payout is a payment waiting for a person. In a small program it is usually a mistyped email. Or an affiliate who signed up with one address and uses PayPal on another. PayPal's advice is the right one. Verify the address, cancel the unclaimed payment, resend. Do that on day two, not day thirty. The PayPal article has the rest of PayPal's rules.

One more PayPal wrinkle from the same FAQ. Its currency restrictions "do not allow conversion of Argentine Pesos, Brazilian Real, or Malaysian Ringgit". And a batch in more than one currency needs "separate payment files for each currency". That is the kind of detail a tool should handle for you.

How do you stop payouts failing?

In shortFour habits. Collect payout details in the affiliate's own portal, with PayPal's or Wise's checks applied as they type. Send a one-unit test to a real account before the first batch. Fund the balance before payday, in every currency you pay in. And ask for the tax form when the affiliate joins, holding the payout until it is in. Then a form never surprises anyone on payday.

The portal is the first defence. The person typing the details is the person who knows them. On AffiliateRail an affiliate adds a PayPal email or bank details in their portal. For Wise, its own checks run on the field as they type. A wrong sort code or routing number is an error on their screen. Nothing reaches payday wrong.

The test transfer is the second. Wise's minimum is one unit of currency. The integration page's advice is to "send a one-unit test transfer to an account you control" before the first batch. One dollar, once, proves the connection, the balance and the credentials in one go.

The balance is the third, and the only one you have to do every month. Fund it before the payout date, in each currency you pay in. On Wise that means a balance per currency. On PayPal it means the batch total plus the fee. The Payouts page shows you that total before anything is sent.

The tax form is the fourth. Our payouts guide lists the reasons a partner is not eligible for a payout. "Tax form not submitted" is one of them, beside "No payout method on file" and "Balance below the minimum". The first two are payouts that quietly do not happen. They are the partner's to fix. The third rolls into the next payout on its own. A good tool tells them so, in one click, before payday rather than after.

What should the software do when a payout fails?

In shortNever mark it paid until the money has moved. Put the failure where you can see it, with the reason PayPal or Wise gave. Tell you once. Tell the affiliate nothing is lost. And resend under a new reference, so PayPal or Wise cannot confuse the retry with the refused attempt.

The first rule is the one most tools get wrong. PayPal or Wise can accept a request and fail it later. Our payouts guide is built on that, so a payout is never marked paid on acceptance alone. On AffiliateRail a payout is marked paid when the money moved. A webhook is a message the software sends your own systems when something happens, and the paid webhook follows at that moment, never on PayPal's or Wise's first yes. If your tool marks payouts paid on submission, its "paid" column is a guess.

The second rule is visibility. A failed payout lands on the Failed tab with the reason PayPal or Wise gave, you get one email, and the partner is told nothing is lost and nothing is theirs to do. Then: "Fix the cause (an underfunded balance is the usual one) and send the batch again; it goes out under a fresh reference so PayPal or Wise cannot mistake it for the refused attempt." That fresh reference is a small thing that prevents a large one. PayPal or Wise declining a retry because it looks like a duplicate.

Other tools handle it differently, and the difference tells you who holds the money. Dub's help page describes a Failed status as "an edge case that happens with PayPal payouts, where the partner's PayPal is not set up to receive payouts". The partner "will need to sort out their PayPal account and retry the payout from their end". That reads as a platform paying from its own account. The custody page confirms it. The affiliate pulls the money from Dub. Refgrow's docs say that if PayPal or Wise rejects a request, "the reserved balance is automatically refunded, the affiliate sees a safe error", and the merchant gets an alert. That reads as a tool driving your account. And Reditus gives every payout a deadline. After it, "the affected affiliates get notified and the payout moves into Overdue payouts". The custody page has who holds the money on each. The schedule article has each platform's payout clock.

What do you tell the affiliate?

In shortThe truth, on the day it happens, in three sentences. What went wrong, where their money is, and what happens next. An affiliate who hears that on day two stays. One who works it out on day thirty, from a payment that never came, does not.

The message writes itself once you know which of the three failures it was. For example, take an unclaimed PayPal payment. The payment was sent to the email on file. PayPal reports no account at that address. It comes back to you in 30 days unless they claim it. Ask them to check the email in their portal and confirm it with PayPal. Tell them you will resend the moment it is right.

Send it the day the failure shows, and send it once. The thing an affiliate remembers about your program is whether the money arrived when you said it would. When it does not, the second-best thing is a founder who noticed first.

Every PayPal and Wise fact on this page was read off PayPal's own pages, or AffiliateRail's integration pages and guide, on the date beside it in the sources. The three platform behaviours quoted are from Dub's, Refgrow's and Reditus's help pages, linked in the sources.

Common questions