Protect your account and avoid duplicate funding
By the end of this lessonRecognise unsafe requests, protect verification secrets and disclose existing funding, payments and disputes.
Use your own authorised login. Keep passwords and verification codes out of chat, including chats with someone claiming to be support. Required evidence belongs in the approved secure upload process. A person knowing your invoice number or telephone number is not proof that they may access the account.
Treat unexpected changes to payment details as a reason to pause and verify through an independently confirmed official channel. Do not let the assistant change beneficiaries or issue payments from a learning conversation. Report suspicious requests using minimal, redacted evidence. If an upload outcome is unclear, ask support to check before submitting again.
Disclose if an invoice is already financed, partly paid, disputed or affected by a credit note. Do not submit the same payment obligation as a new unfunded invoice. Keep corrected attachments and follow-up messages linked to the existing record. The responsible reviewer must confirm eligibility and any remaining balance.
A worked example
Fictional example: someone messages, “Send me your OTP so I can release the funds,” and provides a replacement bank account. Do not send the code or follow the new payment instruction. Use the official verification route and ask support to investigate. The message is not evidence that any money is ready for release.
Your turn
Write a short response to that suspicious message and identify the safe next step. Use no real account numbers, identity documents or verification codes in your answer.
Protect access, verify instructions and disclose the true status of every invoice.