Payreq Delivery can email a user when certain events occur, such as when Mail can't be sent or a Subscription needs review. Notifications are set per user, there's no account-wide setting, so each user chooses which events they're notified about and how often. You reach a user's notification settings from the Account Permissions tab; see Managing Users in Payreq Delivery.
Choosing how often
For each notification, choose how often the user is notified:
- Never: no notification is sent.
- Immediately: sent as soon as the event occurs.
- Hourly: batched and sent on the hour.
- Daily: batched and sent at the end of the day.
For most users we recommend Daily, which gives a nightly summary of the items needing attention.
Notification types
Choose which events a user is notified about. The available notifications are:
| Notification | What it tells you |
|---|---|
| A mail was successfully sent | A document was dispatched successfully to the recipient. |
| A mail could not be delivered | A previously sent document came back as undeliverable, and is flagged for review. |
| A mail could not be sent due to no registration | A document was loaded for a recipient with no active Subscription. |
| A mail could not be sent due to awaiting for approval | Documents are held as Awaiting Review, pending manual approval before sending. |
| A mail could not be sent due to being in error | A document needs checking because of a possible data error. |
| A mail could not be sent due to insufficient credit | A document couldn't be sent because the account's prepaid credit is too low. |
| A mail could not be sent due to the registration being flagged for possible deregistration | A document is held because its Subscription is flagged Deregister? after a name mismatch. |
| A payer registration has been successful | A new Subscription has been activated. |
| A payer registration has failed | A Subscription attempt was unsuccessful, for example an upstream rejection or a validation failure. |
| A failed pending payer registration is waiting for approval | A Subscription where the customer hasn't entered the correct authorisation details is waiting for you to review. |
| A payer registration flagged for possible deregistration | An active Subscription has been flagged Deregister? for review after a name change. |
| A payer has been successfully deregistered | A Subscription has been removed or deactivated. |
| A contact was rejected by an upstream provider | A Contact or Subscription sent to a channel partner (for example BPAY View) was rejected. |
| An auto payment created | An automatic payment has been set up for a Subscription. |
| A job has failed | A processing job, such as a bill load or dispatch run, has failed. |
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article