Security · By the Paypled team · · Updated
Anti-phishing is not a banner.
Banners that say ‘we will never ask for your password’ do not stop phishing, because attackers copy them. A code you choose, printed on every official Paypled message, is a secret the attacker has never seen. Here is how Shield codes work and where their limits are.
A unique code, chosen by you, printed in a fixed position on every official Paypled email and SMS. Attackers can clone a logo. They cannot clone a phrase they have never seen.
Enable it in the console under Settings → Anti-phishing. If a message does not carry your code, it is not from us. Full stop.
How to set it up
Sign in, open Settings → Anti-phishing, switch on Enable Shield code, type your phrase and save. The preview on that page shows exactly where the code will appear in an official header. Pick something you will recognise instantly but that nobody could guess from your public footprint: not your company name, not your pet, not the street you live on.
If you suspect the code has been seen by someone who should not have seen it, change it. The new code applies to every message from that moment.
What to do when it is missing
Do not click. Do not reply. Forward the message to security@paypled.com and, if it referred to a transaction, check the console directly by typing paypled.com into the browser rather than following any link. Then tell the colleague who shares the account, because phishing campaigns go to the whole org chart at once.
Where this control stops
A Shield code proves a message is genuine. It does not stop someone typing their password into a fake sign-in page they reached some other way, and it does not protect a device that is already compromised. That is why it ships alongside the rest of Paypled Shield: an authenticator code on every new device, login alerts, origin-bound sessions, a withdrawal allow-list with a 24-hour cool-off, and password plus authenticator confirmation on every withdrawal.
Used together, the controls close the common path: a convincing email leads to a fake page, the fake page takes a password, the password moves money. With Shield, the email fails the first test, the password is not enough for the second, and the withdrawal cannot go to an address that was never allow-listed.
Takeaways
- Public warnings are copied; a private code is not.
- Set the code once under Settings → Anti-phishing; check for it on every message.
- Pair it with an authenticator and withdrawal allow-lists; no single control is enough.