How to verify a payment sender domain after hours

A payment notification that arrives at 11 pm can create immediate pressure. It may claim that a supplier has changed bank details, a refund is waiting, or an account will be suspended unless payment is made. Outside normal business hours, there may be no colleague, accounts team or vendor contact available to confirm the message.

The safest response is to verify the sender domain independently before clicking a link, opening an attachment or authorising a transfer. A genuine-looking display name is not proof of identity. The domain behind the address, its authentication records and its reputation provide stronger evidence.

Start with the complete sender address

Expand the sender details in your email app and inspect the full address. A message appearing to come from “Westpac Accounts” may actually use a random Gmail address or a lookalike such as westpac-alerts.com. Pay close attention to the characters after the @, where impersonation attempts are usually revealed.

Check for substituted letters, extra words, unusual hyphens and deceptive subdomains. accounts.example.com.au belongs to example.com.au, while example.com.au.billing-help.net belongs to billing-help.net. Australian businesses commonly use .com.au, but that ending alone does not establish legitimacy because attackers can register convincing domains or compromise genuine accounts.

Treat timing and urgency as risk signals

An after-hours notification is not automatically fraudulent. Banks, payment platforms and online retailers operate continuously, and automated receipts can arrive at any time. The risk increases when the email uses urgent language, threatens a penalty or asks you to bypass established approval procedures.

A supposed supplier in Sydney may send an invoice at midnight while the finance team in Melbourne is offline. Record the amount, invoice number, sender address and requested action, then wait for an independent confirmation where possible. Use a phone number already stored in your records or found on a previous statement, rather than a number or link included in the new message.

Check authentication results

Email authentication helps determine whether a message was authorised by the domain it claims to use. SPF identifies permitted sending servers, DKIM checks whether the message carries a valid cryptographic signature, and DMARC states how receiving systems should handle failed checks.

Authentication is valuable evidence, but it is not a complete verdict. A real domain can be compromised, and a phishing email may pass authentication if it is sent from an attacker-controlled domain. Review the visible domain alongside SPF, DKIM and DMARC results rather than treating a green status as automatic proof that the payment request is genuine.

Look up the domain reputation

A domain reputation check can expose a newly registered domain, poor sending history, suspicious infrastructure or inconsistencies with the organisation named in the message. Trusted Sender Score provides about the platform information alongside tools designed to examine sender and domain trust.

Enter the domain manually into a reputable checker instead of following a link in the email. Compare the results with the supplier’s established website, previous correspondence and known contact details. If the notification uses a shortened URL, inspect the destination separately and avoid signing in through an unfamiliar page.

Compare the request with normal payment practice

Payment fraud often changes one small detail: a bank account, BSB, card destination or approval path. Compare the notification with earlier invoices and your organisation’s records. Australian businesses should be particularly careful with requests involving PayID, the New Payments Platform or instant transfers, because speed can make recovery difficult.

A legitimate refund or account change should withstand an independent callback. For an individual, this might mean opening the bank’s official app directly to check transaction activity rather than using the email button. For a business, follow dual-approval rules even when the message appears to come from a familiar supplier.

Handle links, attachments and replies safely

Do not reply to the notification until the sender has been verified. A compromised mailbox may be monitored by an attacker, allowing them to answer convincingly. Avoid opening unexpected HTML files, invoices, QR codes and compressed attachments, especially when the email asks you to enable macros or enter Microsoft 365 or banking credentials.

If a link must be inspected, hover over it on a trusted device and check the complete destination. Navigate to the organisation’s website by typing its known address or using a saved bookmark. Never enter banking passwords, one-time codes or security answers into a page reached from an unverified payment message.

Document and report suspicious activity

Save the original email with its headers, record the time it arrived in Australian Eastern or local business time, and note any domain, account number or attachment involved. Do not forward a suspicious message casually if it contains active links; use your organisation’s reporting process or provide it as an attachment to the security team.

Individuals can contact their bank promptly through an official channel if money or credentials may have been exposed. Australian businesses may also report scams to Scamwatch and notify affected customers, suppliers or staff. Review the platform’s legal notices when assessing how its checking services and information are presented, and use domain monitoring to catch future impersonation attempts before an after-hours alert becomes a payment loss.