Allow Paytia emails through your mail filters

Paytia sends system and transactional messages from dedicated no-reply addresses. Gateways such as Mimecast, Microsoft Defender for Office 365, Proofpoint, Barracuda, and similar scanners sometimes hold, quarantine, or reject those messages as spam or bulk mail.

Ask your IT or email security team to trust (allow / permit / safe-list) the Paytia senders below so activation links, payment notifications, and other Paytia messages reach your users.

Addresses to trust

Add these exact From addresses to your organisation’s allow / permitted-senders list:

• noreply@paytia.com
• nopreply@pay729.net

If your filter supports domains (or wildcards) as well as full addresses, also allow mail from:

• paytia.com
• pay729.net (and subdomains such as *.pay729.net where your product supports that pattern)

Prefer organisation-level rules. End-user “safe sender” lists often cannot override an admin block or quarantine policy.

What these emails are

Messages from these addresses are automated Paytia platform mail — for example user activation / password links, payment or voucher notifications, and other service notices. They are not marketing blasts from an unrelated third party.

If a message is missing from the inbox, check junk, quarantine, and any “held for review” folders before changing passwords or assuming Paytia failed to send.

Mimecast

Mimecast administrators typically allow trusted senders with one of these controls (exact menu names vary by Mimecast product):

• Permitted Senders policy — permit the sender so spam, greylisting, and related reputation checks do not block delivery. See Mimecast’s guide: Configuring Permitted Senders Policy.
• Allow / Block Rules (or Allow & Block Rules) — create an Allow rule for the sender addresses or domains above. Allow rules override many policy detection actions; organisation Block rules still take precedence. See Allow & Block Rules.

Also check that no existing organisation Block rule already matches paytia.com, pay729.net, or the addresses above — a domain-wide block will keep failing delivery even after a user permits the sender personally.

Other mail filtering systems

The same idea applies outside Mimecast. In Microsoft 365, Google Workspace, Proofpoint, Barracuda, and similar products, create an organisation allow / permitted / trusted-sender entry for the addresses (and ideally the domains) listed above, then confirm there is no conflicting block or transport rule.

1. Add noreply@paytia.com and nopreply@pay729.net as trusted / allowed senders.
2. Optionally allow the domains paytia.com and pay729.net.
3. Release any messages already held in quarantine.
4. Retry the Paytia action that sends the email (for example resend the password / activation link).

Still not arriving?

If mail still does not arrive after allow-listing:

• Confirm the recipient address in Paytia is correct and that the user checked junk and quarantine.
• Ask IT for the filter’s reject / quarantine log for the message (time, sender, and reason code).
• Contact Paytia support with that log excerpt: techsupport@paytia.com.