Notifications
What this page covers
This page explains:
- how merchants can be informed about payment outcomes
- what notification paths may be available
- how notifications relate to reconciliation and follow-up workflows
- when technical webhook detail should be handled in separate documentation
Why notifications matter
Once a customer completes payment on a hosted page, the merchant needs a clear way to understand what happened.
For Payment Links, that may include:
- confirming that a payment was successful
- knowing when a payment failed
- identifying when operational follow-up is needed
- supporting merchant-side reconciliation
Possible notification paths
Depending on merchant setup, payment outcomes may be communicated through:
- email notifications
- webhook notifications
- merchant portal visibility
- reconciliation reports (via email or portal)
These options are configured per merchant and can have any combination of the above.
Email notifications
Email notifications are useful when the merchant wants a simple operational way to learn that a payment has been completed or needs attention.
This is often suitable for lower-volume or less technical workflows where a team member reviews outcomes manually.
Webhook or callback notifications
Webhook notifications are more suitable when the merchant wants payment outcomes delivered into their own systems.
This can support processes such as:
- updating a merchant-side payment status
- reconciling payments against invoices or references
- triggering internal business workflows
More details can be found in our Webhooks guide.
Reporting and reconciliation
Reconciliation files are also available via email, or the Merchant Portal, which also contains payment history.