A payment didn't go through. There are three possible reasons, and they need completely different fixes. π³
1οΈβ£ The supporter's bank blocked it
2οΈβ£ Our safety checks stopped it β before it ever reached the bank
3οΈβ£ The creator's account can't currently accept payments
Here's how to tell which, and what to do. π
1οΈβ£ The supporter's bank π¦
Most declines. The bank blocked it before we saw anything, and banks don't explain themselves.
π« International transaction blocks β very common, and most people don't know they have one
π« A daily or per-transaction limit
π« Insufficient funds
π« Card expired, or details entered wrong
π« Fraud detection β new merchant, unusual amount, purchase at 3am
π« Bank verification not completed β the screen was closed too early
What to try, in order:
1οΈβ£ Pay by Bank, if available in your country. Clears more reliably than cards and costs less. Often the whole fix. π¦
2οΈβ£ Check the details β number, expiry, security code, billing address. The billing address is the one people get wrong.
3οΈβ£ Complete the bank verification screen fully. Don't close it, don't switch apps mid-way.
4οΈβ£ Ring your bank. One sentence β "I'm making an online purchase and it's being declined" β usually unblocks it immediately.
5οΈβ£ Try a different card.
2οΈβ£ Our safety checks π‘οΈ
This is the one nobody expects, so here's the honest explanation.
We run risk checks before a payment reaches the card networks at all. Not to be difficult β because stopping a fraudulent payment early protects the creator from a chargeback, and protects the whole platform's ability to take payments. π·
What can stop a payment π§
β±οΈ Too many payments too quickly. Rapid-fire attempts look like card testing, so they get slowed down.
π· Spending limits. There are caps on how much can be spent in a short window β per hour, per day, per week. They exist to protect cardholders whose details have been stolen.
π₯ Paying lots of different creators very fast. A pattern that shows up in stolen-card fraud far more than in genuine support.
π° An unusually large single payment. Not blocked β but it may need extra confirmation.
π Elevated risk across the platform. During unusual activity, limits tighten platform-wide for everyone. Temporary, and it eases automatically.
Extra confirmation (step-up) π
Sometimes you'll be asked for a one-time code rather than being blocked.
That's not a rejection β it's a checkpoint. Enter the code and the payment goes through. It's the same principle as your bank texting you before a big purchase. β
Cooldowns β³
After a run of failed or rapid attempts, there's a short cooldown before you can try again.
Retrying repeatedly makes this worse, not better. Wait it out, then try once. π«
See your own limits π
Your support history shows your spend over the last hour, 24 hours and 7 days β and your current limits.
If a payment is being stopped and you can't work out why, look there first. It's usually immediately obvious. π
3οΈβ£ The creator can't take payments right now βΈοΈ
Nothing to do with you or your card. The message will say which:
π "Wishlist plan not active" β the creator's subscription has lapsed. They need to renew.
π "Temporarily unavailable while updating page" β the creator needs to post. Recurring features pause when someone misses the 3 posts every 28 days rule.
β οΈ "Account status issue" β something on the creator's account needs resolving.
In all three: message the creator. They can usually fix it in minutes and often don't know it's happened. π¬
Recurring payments that fail π
Different problem, faster handling needed.
The supporter is notified and the payment retried. If it keeps failing, the subscription lapses β they lose access, the creator loses the income.
Usually a replaced or expired card. People forget what's attached to a card they've cancelled.
Creators: π‘
β
Watch your dashboard. Failed recurring payments show up β don't let them sit.
β
Message the supporter. Nine times out of ten it's a new bank card and a nudge fixes it in a minute.
β
Don't take it personally. A failed payment is rarely someone leaving.
Failed payments and your risk profile β οΈ
Creators: a high failure rate raises your risk classification, which can affect your reserve. See Payouts & Reserves π¦π·.
Not a punishment β a high decline rate is a recognised fraud signal, so it gets watched.
What keeps it low:
β
Sensible pricing β very large amounts decline more often
β
Clear listings, so nobody's paying for something confusing
β
Encouraging Pay by Bank where available
β
Telling supporters not to hammer retry π«
Common questions π€
"I was charged but it says failed."
Usually a pending authorisation that drops off within a few working days rather than a real charge. If it settles, message us with the date and amount. π¬
"Why do I need a code when my card worked fine?"
Extra confirmation on higher-value or unusual payments. Enter it and you're through. π
"I've been told to wait before trying again."
A cooldown after rapid or repeated attempts. Wait, then try once β don't retry through it.
"My card works everywhere else."
Usually an international block, since the platform is UK-registered. One call to your bank sorts it. π
"Why does Pay by Bank work when my card doesn't?"
Different rails. Bank payments skip card fraud rules entirely β which is why it's the first thing to try. π¦
"I've hit a spending limit β can it be raised?"
Limits protect cardholders whose details get stolen. Check your support history to see where you are; if you think there's a genuine problem, message us. π¬
"Why so many checks?"
Because every chargeback prevented is money a creator keeps. These checks are the reason payments here stay switched on. π‘οΈ
TL;DR π―
Three causes: your bank, our safety checks, or the creator's account status
Try Pay by Bank first β more reliable and cheaper π¦
A one-time code is a checkpoint, not a rejection π
Don't hammer retry β it triggers cooldowns and makes it worse π«
Your support history shows your spend and current limits β look there first π
Every check exists so creators keep their money. π³π·
