Notifications

Open the bell in Heron to see transfer and identity-verification updates you have permission to access. Select an update to open the related resource, or mark it read. Each teammate has their own unread count and read history. Read all marks the currently counted updates as read; newer arrivals can remain unread.

Transfer updates

Notifications cover funding requests, actions required, completion, failure, cancellation, returns and refunds. Routine processing and provider review remain in the transfer timeline unless you need to act. Open the transfer for its latest status before taking action on an older notification.

Identity updates

Notifications identify the provider and cover approval, rejection, onboarding actions and new or changed follow-up requests. A document request can arrive without a change to overall verification status. Approval applies to the named provider connection, not every provider linked to the entity.

Email preferences

Open your profile and select Email notifications. Choose independently for transfers and identity:

• Action required and problems: enabled by default; includes customer actions, transfer failures/returns/refunds, identity rejection and requests for information or documents.
• Confirmations: enabled by default; includes identity approvals and completed/canceled transfers.
• Awaiting funds reminders: disabled by default; available for transfers only.
• Sandbox activity: disabled by default; enable it to receive selected sandbox emails, marked [Sandbox] in the subject.

Existing saved preferences remain in effect. Changes save automatically and do not change your in-app inbox or access permissions. Enabling emails does not send earlier events retrospectively. Reading an in-app notification does not cancel a scheduled email.

Emails can arrive after a short delay. Email-delivery failures do not remove updates from your inbox. Sign in to Heron to review sensitive identity information. Inbox history is available for 90 days; notifications describe past activity, so the linked resource may have changed.

For machine-to-machine updates, use Customer Webhooks.