Notifications
Overview
You can use the Notifications sections in Verifone Central to search and filter your organisation’s webhooks and email notifications.
The Notification Service allows you to get status updates on certain events/actions you subscribe to, and to automate business processes like order management, accounting, or downloading reports. Data sent in the notifications will be pushed to your email/URL.
Availability
Only users with Merchant Admin, Merchant Reviewer or Merchant Supervisor roles can access this section.
Search/filter notifications in Verifone Central
To use the information in the Notifications section in Verifone Central, follow these steps:
- Log in to your Verifone Central account.
- Navigate to Administration and click on Notifications.
3. You can select the organisation(s) for which you want to create and view the notifications. You can filter notifications by Name/Email/URL and/or use the following filters:
- Event type
- Status
Create a notification in Verifone Central
- Log in to your Verifone Central account.
- Navigate to Administration and click on Notifications.
- Click on Create new notification.
4. On the Create Notification page, provide the following information:
- Notification name – used to identify the notification configuration in the listing
- Organisation(s)
- By selecting an organisation, you apply a scope to the configuration
- By selecting a root-level organisation, the notifications will send messages for all child organisations
- By selecting the lowest level organisation, you will receive messages for the selected organisation only
- Events* – notifications will be triggered as soon as an event takes place for one of the selected transaction status updates
- Delivery Method – specifies how notifications will be delivered. Depending on the selected method, Verifone will send either an email with plain text describing the event or a webhook with the transaction payload. Possible values:
- Email – accepts only one email address
- URL – accepts only one webhook
Details of variables usage
Parameter Name | Type | Variable | Description |
---|---|---|---|
eventId | String | <uuid> (eventId) | Unique identifier for the event used for logging and audit purposes |
eventDateTime | String | <date-time> (eventDateTime) | The timestamp when the event occurred. This should be in local time, with an offset to UTC specified to ensure this can be converted between time zones. |
recordId | String | (recordId) | The unique identifier of the object that this event relates to (example: entity, device, user) |
entityUid | String | <uuid> (entityUid) | The Verifone allocated a unique ID for the entity/organization this webhook/event is for |
eoEntityUid | String | <uuid> (eoEntityUid) | The internally assigned identifier for the estate owner/customer for the event |
eventType | String | (eventType) | Trigger of the event |
estateOwner | String | (estateOwner) | The estate owner's name |
Source | String | (source) | The name of the source sending the event |
Component | String | The name of the source component sending the event | |
Received | Datetime | The timestamp when the event was received. This will be set when the event is received and does not need to be provided by the client. | |
objectType | String | Type of the notification like transaction type for now only | |
Content | Object | The associated event data. This is optional and if specified will vary according to the event type. | |
UUID | String | Same as the eventID | |
TRANSACTIONTYPE | String | Transaction type (sale, authorization) | |
INITIATORTRACEID | String | A unique ID used to differentiate multiple actions for the same transaction (capture and refund) | |
GATEWAYTRACEID | String | (traceId) | Unique ID added to differentiate transactions |
CREATEDDATETIME | Datetime | <date-time> (eventDateTime) | Timestamp of the transaction |
POI | String | (uuid) | Point of interaction connected to the organisation |
MERCHANT | String | Displays all values related to the Entity like the ID of entity, Country Code, Merchant Category Code (MCC), Merchant ID | |
AMOUNT | Float | Amount and currency used for transactions | |
INSTRUMENT | Object | Card brand, masked card number, and instrument type | |
OUTCOME | String | Displays the response code for a transaction. If the transaction is successful, the code displayed is 0000. | |
Customer | Object | Customer's details | |
Context | Object | This stores all the data related to the payment information |
Events*
Event | Description |
---|---|
TxnAccountVerificationApproved TxnAccountVerificationDeclined |
An account/card verification |
TxnAuthorisationApproved TxnAuthorisationDeclined |
An authorisation or preauthorisation |
TxnCaptureApproved TxnCaptureDeclined |
A capture or completion |
TxnDelayedChargeApproved TxnDelayedChargeDeclined |
A single message sale (auth+capture) related to a preauth chain |
TxnExtendApproved TxnExtendDeclined |
A preauth extend |
TxnPreauthIncrementApproved TxnPreauthIncrementDeclined |
An increment for a preauth |
TxnReauthorisationApproved TxnReauthorisationDeclined |
A preauth reauth |
TxnRefundApproved TxnRefundDeclined |
A refund |
TxnSaleApproved TxnSaleDeclined |
A single message sale (auth+capture) |
TxnVoidApproved TxnVoidDeclined |
A void |
Checkout Events
Event |
Description |
---|---|
Checkout - Transaction succeeded | A successful checkout transaction success |
Checkout - Transaction failed | Checkout transaction failed |
Checkout - Card token succeeded | A card token successful transaction |
Checkout - Card token failed | A failed card token transaction |
Checkout - 3DS authentication succeeded | A successful checkout 3DS transaction |
Checkout - 3DS authentication failed | Failed 3DS authentication |
Checkout - 3DS lookup failed | 3DS lookup failed |
Checkout - 3DS lookup succeeded | 3DS lookup succeeded |
Checkout - SMS delivery succeeded | Transaction SMS delivery succeeded |
Checkout - Email delivery succeeded | Transaction email delivery succeeded |
Checkout - SMS delivery failed | Transaction with SMS delivery failed |
Checkout - Email delivery failed | Transaction with email delivery failed |
Email payload for every event
here is template : RECEIVED:
array (
eventId: 51685250-b4cf-4248-9670-1b11d3503ef2,
eventDateTime : {dateTime={date={year=2021, month=11, day=3}, time={hour=11, minute=20, second=18, nano=0}}, offset={totalSeconds=0}},
recordId : 51685250-b4cf-4248-9670-1b11d3503ef2,
entityUid :9aea8c9c-d54e-4811-b8d3-6d33aa3a702c,
eoEntityUid:,
eventType:Sale Approved,
estateOwner:,
source:pdsp,
component:,
received:
objectType:TransactionEvent
content:
UUID :51685250-b4cf-4248-9670-1b11d3503ef2,
TRANSACTIONTYPE : SALE,
INITIATORTRACEID : ,
GATEWAYTRACEID : 9635938400113037,
CREATEDDATETIME : 2021-11-03T11:20:18.000Z,
POI : {},
MERCHANT : {UUID=9aea8c9c-d54e-4811-b8d3-6d33aa3a702c, LOCALE={COUNTRYCODE=NL}, CONTRACTS=[{MCC=1234, MERCHANTID=HYNW6V7SMK3A6}]},
AMOUNT :{VALUE=100.0, CURRENCYCODE=USD},
INSTRUMENT :[{INSTRUMENTTYPE=PayPal}],
OUTCOME:[{}],
CUSTOMER :,
CONTEXT:
)
Webhook payload for sales transaction
{
"eventId": "2",
"eventDateTime": "2020-03-23T11:07:28Z",
"recordId": "1",
"eventType": "TxnSaleApproved"
}
Update notifications in Verifone Central
To update notifications in Verifone Central, follow the steps below:
- Log in to your Verifone Central account.
- Navigate to Administration and click on Notifications.
- In the Notifications list, click on the arrow of the notification that you want to update.
4. You can apply these updates to a notification:
- Update the notification name
- Add/remove organisation(s)
- Add/remove events
- Change the delivery method
- Enable/Disable/Delete the notification
5. Click on Save changes.
6. A notification can be deleted only after being disabled.