READING PATH / Consumers & business teams

Slow down the suspicious request

Use independent verification and prepared response steps when a message, voice or device cannot be trusted.

4 GUIDES / ABOUT 16 MINUTES

A person using a phone to pay. — Illustrative source photograph, not a current product interface. SteveMccabe45 · CC BY-SA 4.0

Use the sequence as a reading plan, not a guarantee that an account, product or implementation is safe. The checkboxes record only what you mark on this page.

All reading paths →

4 MIN READ / SOURCE CHECKED

Verify an invoice bank-detail change before paying

Verify the new destination outside the message.

Mark step 1 as read

4 MIN READ / SOURCE CHECKED

Use a callback protocol when a familiar voice asks for money

A familiar voice is not enough evidence.

Mark step 2 as read

4 MIN READ / SOURCE CHECKED

Passkeys resist phishing only if recovery does too

Protect the sign-in and plan the recovery path.

Mark step 3 as read

4 MIN READ / SOURCE CHECKED

Respond to a lost phone that holds payment accounts

Know which provider to contact and what to preserve.

Mark step 4 as read

0 of 4 reading steps marked. Progress stays on this page only; it is not a certification.