Webhook Services
Overview
Our webhook solution ensures that your system receives real-time notifications regarding specific events triggered within the NI system, based on your subscription to the different webhooks.
Card Replacement (Post)
This webbook serves to promptly inform your system whenever a card replacement occurs. This helps ensure that important card management activities are communicated accurately and on time. Card replacements are crucial in banking because they affect customer accounts, security, and transaction abilities.
Pin Action (Post)
This webbook serves to promptly inform your system whenever there are PIN-related actions performed on a card. It's important for maintaining card security, overseeing operations, and meeting regulatory requirements in finance. PIN-related actions, as of now we support reset pin counter only.
ThreeDS Webhook
Status:
Production
Version:
V2
Category:
Webhook
Overview
This webbook serves to instantly inform your system whenever an OTP message needs to be sent to the cardholder, this webhook is used when you need to send the OTP message from your side to the cardholder.
How It Works
When an OTP message needs to be sent to the cardholder, we will instantly send you a POST request to a specified endpoint, ensuring secure delivery of the OTP.
It communicates necessary details such as transaction amount, currency, masked pan, externalCardId
and mobile. Number. This mechanism ensures that the cardholder receives a timely and secure OTP for completing their transaction.
Once you receive this request you can send the message to the cardholder, so they can use the OTP.
3DS Webhook
ThreeDS Webhook
Status:
Production
Version:
V2
Category:
Webhook
Node | Child Node | Type | Length | Description |
---|---|---|---|---|
Authorization | Bearer xxxx | string | Authorization Header (Bearer Token) | |
Content-Type | application/json | string | Content Type |
Node Type | Type | Length | Description | |||||||
---|---|---|---|---|---|---|---|---|---|---|
id | string | 12 | Unique identifer for the request | |||||||
type | string | 10 | Type of the webhook | |||||||
timestamp | string | 30 | Timestamp of the request - Format YYYY-MM-DDtHH:MM:SS.SSS+04:00 | |||||||
details | transaction | amount | string | 18 | Transaction Amount | |||||
currency | string | 3 | Amount Currency | |||||||
merchantName | string | 100 | Merchant Name | |||||||
date | string | 30 | Request Timestamp - Format YYYY-MM-DDtHH:MM:SS.SSS+04:00 | |||||||
time | string | 30 | Request Timestamp - Format YYYY-MM-DDtHH:MM:SS.SSS+04:00 | |||||||
recipient | maskedCardNumber | string | 19 | Masked Card Number | ||||||
externalCardId | string | 20 | External Card ID | |||||||
clientId | string | 21 | Client ID | |||||||
mobilePhone | string | 32 | Mobile Phone | |||||||
string | 255 | |||||||||
language | string | 3 | Language Indicator | |||||||
OTP | string | 8 | OTP Value | |||||||
referenceNumber | string | 12 | Reference Number | |||||||
textMessage | string | 255 | Text Message |
{
"id": "688385602509",
"type": "3DSOTP",
"timestamp": "2023-10-05T08:03:41.283Z",
"details": {
"transaction": {
"amount": "657.45",
"currency": "AED",
"merchantName": "Etisalat q",
"date": "2023-10-05T08:03:41.280Z",
"time": "2023-10-05T08:03:41.280Z",
"recipient": {
"maskedCardNumber": "433366XXXXXX89416714",
"externalCardId": "43336612345605100000",
"clientId": "1234625",
"mobilePhone": "971553456789",
"email": "vikas.mane@gmail.com",
"language": "E"
}
},
"OTP": "575866",
"referenceNumber": "688385602509",
"textMessage": "657.45 , 575866 , Etisalat q , AED"
}
}
Node | Child Node | Type | Length | Description | |||
---|---|---|---|---|---|---|---|
Content-Type | application/json | string | Content Type |
Node Type | Type | Length | Description | |||||||
---|---|---|---|---|---|---|---|---|---|---|
id | string | 36 | Unique identifer ID | |||||||
type | string | 10 | Type of the webhook | |||||||
timestamp | string | 30 | Timestamp of the response - Format YYYY-MM-DDtHH:MM:SS.SSS+04:00 | |||||||
response | status | code | string | 5 | Status code of the response | |||||
description | string | 30 | Response Description |
{
"id": "b876d568-8411-4638-bdef-a1a188a4773b",
"type": "SMS",
"timestamp": "2020-07-20T06:49:02.366Z",
"response": {
"status": {
"code": "00",
"description": "successful"
}
}
}
Code | Description |
---|---|
200 | Sample Description |
400 | Bad Request |
401 | Unauthorized |
403 | Forbidden |
500 | Internal Server Error |
502 | Bad gateway |
503 | Scheduled Maintenance |
504 | Gateway Timeout |
596 | Service Not Found |
How It Works
Follow the steps below. For more details, read the Quick Start Guide.
1- Process 1
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Amet, sed at amet cras fringilla adipiscing nunc, in pulvinar. Sagittis pellentesque leo et proin convallis justo vitae in.
2- Process 1
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Amet, sed at amet cras fringilla adipiscing nunc, in pulvinar. Sagittis pellentesque leo et proin convallis justo vitae in.
3- Process 1
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Amet, sed at amet cras fringilla adipiscing nunc, in pulvinar. Sagittis pellentesque leo et proin convallis justo vitae in.
4- Process 1
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Amet, sed at amet cras fringilla adipiscing nunc, in pulvinar. Sagittis pellentesque leo et proin convallis justo vitae in.
5- Process 1
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Amet, sed at amet cras fringilla adipiscing nunc, in pulvinar. Sagittis pellentesque leo et proin convallis justo vitae in.