Notifications

Transaction notifications

After Instant Bank Transfer processes a transaction request, it sends a notification to the merchant's transaction notification URL.

The notification includes many of the same parameters included in the request, plus the transaction status, transaction fee payable by the merchant, and any applicable transaction errors.

The payin notification in the Instant Bank Transfer system has three possible states:

1. Notification Initiated – The notification could not be sent. Instant Bank Transfer attempts to make an HTTPS connection to the notification URL three times in succession. If after the third attempt, no connection is established, the notification status remains in Notification Initiated state. A payin notification with this status means the merchant did not receive the transaction results.

2. Notification Sent – An HTTPS connection with the merchant system was established and data was sent. The verification process times out after four minutes. If, for any reason, the merchant does not successfully echo back the payin notification (verification request), the notification status remains Notification Sent. This status means that it is unclear whether the merchant received a notification and processed the results of the transaction.

3. Notification Complete – Instant Bank Transfer received the verification request where the merchant echoed back the payin notification received from Instant Bank Transfer.

Return notifications

A return notification notifies the merchant that a settled payment transaction has been returned by the consumer’s bank.

When a consumer's bank returns a settled payment, Instant Bank Transfer sends a notification to the merchant's event notification URL. After verifying the content of the return notification, the data can be processed by the merchant's back office and used for account reconciliation.

For more information, see EFT Return Codes.

Verifying notifications

All notifications must be verified via a verification request sent to Instant Bank Transfer. For more information, see Verifying Transaction Notifications

Verification request

After processing the notification, the merchant system must echo back an exact copy of the original notification message to the notify verification URL

Verification response

The response to a verification request is verification_code. verification_code 0 (zero) confirms that the verification request exactly matches the original notification request.

If the merchant system doesn't send the verification request after it receives the notification, Instant Bank Transfer sends the notification again, to a maximum of three times. If Instant Bank Transfer still hasn't received the verification request after the notification is sent the third time, the notification is marked as initiated in the Instant Bank Transfer system. The support team monitors our systems for unsuccessful notifications and contacts merchants when necessary.

Verification codes are described in the table below. Note that any verification code other than 0 indicates that the data contains errors.

Verification codeDescription
0Verified
C001Could not parse verification request - invalid HTTP request
C002Could not parse verification request - invalid content
C003Could not parse verification request - invalid transaction ID
C004Verification details don't match original payment - notification not found
C005Verification details don't match original payment - notification doesn't match / exceeded 4 minute thread timeout
C006Generic error

WHAT’S NEXT
Tell your users what they should do after they've finished this page