Tokenizations Notification
Use Case
You will receive a notification whenever a tokenizations process is completed, successful or not. Fundiin will send a POST message to the Notification URL you provide us.
To ensure that a payment has been securely processed you will need to validate the signature on header using your secretKey and clientId in the same manner you compute the signature on header for a request.
Request Header
Request
| Parameter | Type | Required | Description |
|---|---|---|---|
| merchantId |  | Fundiin provides MID as a unique identifier to each merchant. | |
| notificationType | | AUTHENTICATION_STATUS. | |
| resultStatus | | Result Status | |
| resultMsg | | The result message which contains information about the result. | |
| merchantUserId | merchantUserId merchant send in API Create tokenizations Request API |
Example Request
Response
204 No Content
Result Status & Messages
| Status code | Description | Action to take |
|---|---|---|
| SUCCESS | User can linked tokenizations | Please call API Confirm Tokenizations After User Authenication Success to continue Processing |
| REJECT | The user declines linkage or does not meet the linkage requirements. | |
| ACCESS_DENIED | Access denied. | Please check your settings in merchant portal, or contact Fundiin for configurations. |
| ERROR_GENERAL | Declined due to general reasons other than the specific decline error codes provided. |