Some payment methods involve delayed or asynchronous settlement.
In these cases, the customer may receive instructions (e.g. to complete payment at a physical location, or via EFT), and PayWeb will await confirmation from the financial provider.
When that provider eventually confirms the payment — even hours or days later — PayWeb will automatically post a finalNotify response to the original NOTIFY_URL supplied during the Initiate step.
When Is This Used?
Examples of asynchronous flows include:
- EFT or bank transfer payment methods
- Cash deposit instructions
- Offline eWallet top-ups
Delivery Behaviour
- PayWeb sends the same payload format as the standard Notify.
- Your system must respond with a plain-text
OKto confirm receipt. - Only ports 443 (HTTPS) and 80 (HTTP) are supported.
If noOKis received, PayWeb will retry the Notify post two more times at 30-minute intervals before abandoning the attempt.