Token Linking Status API
Use Case
Token Linking Status API to gets the linking token status corresponding by merchant referenceId
Request
POST/v2/tokenizations/linking-status
| Parameter | Type | Required | Description |
|---|---|---|---|
| merchantId | Fundiin provides MID as a unique identifier to each merchant. | ||
| referenceId | The Unique reference ID of the Order. | ||
| merchantUserId | Unique identifier merchant customer. | ||
| lang | Language of returned message (vi or en), If not included, the default is en. |
Example Request
{
"merchantId": "Your merchant code",
"referenceId": "Your order number",
"merchantUserId": "Unique identifier merchant customer",
"lang": "vi"
}
Response
| Parameter | Type | Required | Description |
|---|---|---|---|
| merchantId | Fundiin provides MID as a unique identifier to each merchant. | ||
| referenceId | Merchant's Reference Id unique | ||
| merchantUserId | |||
| notificationType | AUTHENTICATION_STATUS. | ||
| resultStatus | Result status | ||
| resultMsg | The result message which contains information about the result. | ||
| linkedDate | Exact Time of Linking Completion Format: YYYY-MM-DD hh:mm:ss |
{
"merchantId": "FundiinVN",
"referenceId": "Your order number",
"merchantUserId": "Your merchant user id",
"notificationType": "AUTHENTICATION_STATUS",
"linkedDate": "2023-07-24 09:33:55",
"resultMsg": "User can linked tokenization",
"resultStatus": "SUCCESS"
}
Result Status & Messages
| Status code | Description | Action to take |
|---|---|---|
| SUCCESS | The transaction was successful. | Proceed with any necessary post-transaction activities. |
| EXPIRED | The time period the customer had for completing the payment has expired. | Prompt the customer to initiate a new transaction. |
| REJECT | The request is rejected because of risk control. | Review the transaction for potential risks and consider alternative payment methods or further risk assessment. |
| PROCESSING | The process is still in progress. | |
| ACCESS_DENIED | Access denied. | Please check your settings in the merchant portal or contact Fundiin for configurations. |
| INVALID_REQUEST | Invalid request. e.g., Invalid currency, invalid amount, etc. | Ensure that the request parameters are correct and meet the API requirements. |
| INVALID_REFERENCE_ID | The referenceId is invalid. | Please retry with a different referenceId. |
| INVALID_CLIENT_ID | The clientId is not registered. | Make sure to use a valid and registered clientId for the request. |
| INVALID_SIGNATURE | The signature is invalid. | Double-check the signature generation process to ensure its correctness. |
| INVALID_MERCHANT_ID | The merchant is not registered. | Ensure that the merchant ID is correct and registered with Fundiin. |
| INVALID_HTTP_METHOD | The server does not implement the requested HTTPS method. | Use the correct HTTP method (e.g., GET, POST, etc.) when making the request. |
| INVALID_API | API is not defined. | Check whether the request URL is correct. Ensure that the endpoint of the called API is correct. |
| DOWNSTREAM_ERROR | Partner downstream timeout. (Retriable) | Retry the request later as the error might be temporary due to partner-related issues. |
| ERROR_GENERAL | Declined due to general reasons other than the specific decline error codes provided. | Contact Fundiin support for assistance in identifying and resolving the general issue. |