Notifications Service
Introduction#
The Latitude notifications service is complementing service to allow Merchant partners to confirm responses from Latitude. Merchants may choose to act upon notifications, or simply use notifications for informational purposes (eg. additional logging/debugging).
Setup Pre-requisite Requirements#
| Notification endpoints | The Merchant's endpoint where notifications should be posted. There is no limit to notification endpoints. Please provide this information to your Latitude Financial Services representative |
Default settings for Notifications#
| Setting | Description |
| maxAttempt | The maximum number of reattempts should an error occur in posting to the defined notification endpoint. The default is 1 |
| condition | Conditions are rules for which notifications should be triggered. By default, all transaction types that are processed via the iFrame and API services will generate notification messages The following are the common list of transaction types. Each Merchant's integration is custom and not all transaction types will apply to every Merchant: - card number authorisations (txnType=8 or 18) - SMS attempts and corresponding account number authorisations (txnType=17) - voids (txnType=30) - refunds (txnType=20) - captures (txnType=19) > Note: all SMS attempts relating to an account number authorisations will be sent to the notification endpoint. If the Customer attempted the SMS generation 4 times, then the Merchant will receive all 4 SMS notifications. Some Merchants may opt to only receive the final account number authorisation outcome, and not prior SMS attempts. Please provide this information to your Latitude Financial Services representative |
Returned payment fields#
The default fields to be returned in the notification, if the field exists and is applicable to that form of payment method (i.e card number shopping, account number shopping or drivers license shopping).
Notifications Format and Examples#
The Latitude Payment Gateway will use the HTTPS POST method to send all notification payloads.
The message format will follow a standard JSON structure as used for API responses.
Example of Successful Purchase for Credit Card
Example of Declined Purchase for Credit Card
Example of a Successful SMS authorisation
Example of an Unsuccessful SMS authorisation
Example of Successful Capture