Response (with success)
Body answer
Transaction status
It is possible to receive the transaction statuses below:
- IN PROCESSING – meaning that the transaction initiated is now in processing.
- PARTIAL – it is pending to receive information.
- SUCCESS – informing transaction OK, the transaction was executed with success.
- DECLINED – indicating that the transaction was declined by an operation intervenient.
- TIMEOUT – informing a potential communication error.
- ERROR – indicating that the transaction was declined by external system.
After the transaction is in processing, it will only retrieve the “partial” status if some action is pending to be taken. After that it will send the transaction status.
Notifications (Merchant Notifications)
The Merchant can receive notifications by email or endpoint (notification assembling to the status inquiry – Checkout Status), however, only a notification will be sent for each transaction.
Notifications are sent by endpoint straight to the URL provided by the Merchant. The parameterization of this endpoint needs to be done on the SIBS Gateway Backoffice.
For email notifications, only one notification will be sent per transaction.
For URL notifications not accomplished, retries will be attempted. Each time SIBS Gateway receives a transaction, a notification will be sent with the transaction status in real time.
Every day SIBS Gateway sends a summarized email with the newest failed notifications (email needs to be registered on the Backoffice).
There is no guarantee on message order, especially if the time difference between the notifications is smaller than the time it takes to process them or by any communication or systems issues. Once the issues are sort out, new notifications will arrive in real time and old notifications will be resent. In case no notification is received, the option “Checkout Status” should be used before rejecting any transaction.
Complex types
MerchantNotificationRequest
String (Maximum 256 Text) (ex: Success)
Possible values are {“Success”, “Partial”, “Declined”, “InProcessing”, “Pending”, “Timeout”, “Error”}.
string
(“Success”, “Partial”, “Declined”, “InProcessing”, “Pending”, “Timeout”, “Error”)
string
(“MBWAY”, “CARD”, “REFERENCE”, “TOKEN”, “STATIC_QRCODE”, “MANDATE”)
string
(“AUTH”, “PURS”, “CAPT”, “CAUT”, “RFND”, “CANC”, “PREF”, “CPRF”. “CMBW”, “MAND”, “MAUT”. “MPUR”, “MITR”)
Max4Text
(“CRTN” – Mandate Creation,
“SSPN” - Mandate Suspension by Client;
“RCTV” – Mandate Reactivation by Client,
“LMUP” – Mandate Limits Update by Client,
“CNCL” – Mandate Cancellation by Client)
Max4Text
(“SCCS” – Success (applicable to all Action Codes),
“RFSD” – Refused due to validation rules (only applicable to Mandate Creation),
“RJCT” – Rejected by Client (only applicable to Mandate Creation))
Max7Text
(“ACTUAL”-Actual amount, “ESTIMATED”-Estimated amount (the final amount could be above or below), “DEFAULT”-Default amount)
If not present, the “DEFAULT” value is assumed.
If merchantInitiatedTransaction has MITType “UCOF”, the amountQualifier must be set to “ESTIMATED”.
MerchantNotificationResponse
String (Maximum 256 Text) (ex: Success)
Possible values are {“Success”, “Partial”, “Declined”, “InProcessing“, “Pending”, “Timeout”, “Error”}.
Examples
On this subchapter, it is possible to find examples of webhook notifications sent by SIBS Gateway and the answer that the customer application should give. Answering this message is very important to avoid more unnecessary notifications sent by SIBS Gateway.
Resquest example:
{
"returnStatus": {
"statusMsg": "Success",
"statusCode": "000"
},
"paymentStatus": "Success",
"paymentMethod": "MBWAY",
"transactionID": "DaBzrs8ayhQpi1EeenHe",
"transactionDateTime": "2022-11-12T16:18:53.127Z",
"amount": {
"currency": "EUR",
"value": 1.0
},
"merchant": {
"terminalId": 49180
},
"paymentType": "AUTH",
"notificationID": "2533e456-5e36-42c8-9eea-7961902f185e"
} Response example:
{
"statusCode": "200",
"statusMsg": "Success",
"notificationID": "2533e456-5e36-42c8-9eea-7961902f185e"
} Cardholder Initiated Transaction with Type Recurring example:
{
"returnStatus": {
"statusMsg": "Success",
"statusCode": "000"
},
"paymentStatus": "Success",
"paymentMethod": "CARD",
"transactionID": "s24nZiFtu15SCiW9vpDm",
"transactionDateTime": "2022-12-27T16:05:27.585Z",
"amount": {
"currency": "EUR",
"value": 11.2
},
"merchant": {
"transactionId": "6637262",
"terminalId": 45546,
"merchantName": "GOMERCIANTE DO LEGACY"
},
"paymentType": "PURS",
"notificationID": "a433453e-6e40-4f53-a80d-4985cffa36f6",
"merchantInitiatedTransaction": {
"type": "RCRR",
"validityDate": "2023-06-30T01:00:00+01:00",
"amountQualifier": "ACTUAL",
"schedule": {
"initialDate": "2022-12-27T00:00:00Z",
"finalDate": "2023-01-06T00:00:00Z",
"interval": "DAILY"
}
}
} Merchant Initiated Transaction with Type Recurring Example:
{
"returnStatus": {
"statusMsg": "Success",
"statusCode": "000"
},
"paymentStatus": "Success",
"paymentMethod": "CARD",
"transactionID": "s2K9YuqPQuC9NkdCvDA4",
"transactionDateTime": "2023-01-06T00:00:03.378Z",
"amount": {
"currency": "EUR",
"value": 11.2
},
"merchant": {
"terminalId": 45546,
"merchantName": "GOMERCIANTE DO LEGACY"
},
"paymentType": "MITR",
"notificationID": "3a9d8777-292d-48fb-971c-6e6558de0fd5",
"merchantInitiatedTransaction": {
"type": "RCRR",
"amountQualifier": "ACTUAL"
}
} Cardholder Initiated Transaction with Type UCOF Example:
{
"returnStatus": {
"statusMsg": "Success",
"statusCode": "000"
},
"paymentStatus": "Success",
"paymentMethod": "CARD",
"transactionID": "s2bDX8mjiFZU5ZwfvSvR",
"transactionDateTime": "2023-01-06T16:57:11.2Z",
"amount": {
"currency": "EUR",
"value": 102.38
},
"merchant": {
"transactionId": "3064371",
"terminalId": 45546,
"merchantName": "GOMERCIANTE DO LEGACY"
},
"paymentType": "AUTH",
"notificationID": "45d108d3-2cef-41a6-90af-a3bdb4af244a",
"merchantInitiatedTransaction": {
"type": "UCOF",
"validityDate": "2023-01-31T00:00:00Z",
"amountQualifier": "ESTIMATED"
}
}
}Merchant Initiated Transaction with Type UCOF Example:
{
"returnStatus": {
"statusMsg": "Success",
"statusCode": "000"
},
"paymentStatus": "Success",
"paymentMethod": "CARD",
"transactionID": "s2nYaNUC3hFpqd0HGq4Z",
"transactionDateTime": "2022-12-23T10:48:39.153Z","amount": {
"currency": "EUR",
"value": 5.16
},
"merchant": {
"transactionId": "6540474",
"terminalId": 45546,
"merchantName": "GOMERCIANTE DO LEGACY"
},
"paymentType": "MITR",
"notificationID": "c9786e7e-dc2a-4611-8a31-4b8197f41138",
"merchantInitiatedTransaction": {
"type": "UCOF",
"amountQualifier": "ESTIMATED"
}
} Response example:
{
"statusCode": "200",
"statusMsg": "Success",
"notificationID": "2533e456-5e36-42c8-9eea-7961902f185e"
} Error message
Card
| Error code | Message to the Merchant | Message to the Client | Owner | What to do? |
|---|---|---|---|---|
| 10.105.0001 | Invalid payment entity | Entity not valid. Please try again later. | Merchant | Please verify that the correct Merchant entity is being used. |
| 10.103.0003 | No card record | Card not valid. Please try again later. | SIBS | Please verify log. |
| 10.103.0004 | Not sufficient funds | Not sufficient funds. Please try again. | Client | Please assure that the account has enough funds |
| 10.103.0005 | Invalid card number | Card number not valid. Please try again. | Client | Please insert the correct card number |
| 10.103.0006 | Expired card | Expired card. Please verify with your bank. | Client | Please note that your card has expired |
| 10.103.0007 | Card cancelled | Your card has been cancelled. Please verify with your bank. | Client | Please verify with your bank |
| 10.103.0008 | Inactive card | Inactive card. Please verify with your bank. | Client | Please verify with your bank |
| 10.103.0009 | This card has been reported as stolen. | Pick-up card. Please verify with your bank. | Client | Please verify with your bank |
| 10.103.0 010 | Blocked card | Blocked card. Please verify with your bank. | Client | Please verify with your bank |
| 10.103.0 011 | Invalid CVV | Invalid CVV. Please verify with your bank. | Client | Please insert the correct CVV number |
| 10.103.0 012 | Card limit exceeded | Card limit exceeded. Please verify with your bank. | Client | Please verify with your bank |
| 10.103.0 013 | Wrong expiry date | Wrong expiry date. Please double check. | Client | Please insert the correct card expiration date |
| 10.105.0 014 | Invalid refund amount | N/A | Merchant | Please assure that the Refund is equal to the total amount or less. |
| 10.103.0 015 | Invalid card (Cannot process operation- fraud) | Invalid card. Please verify with your bank. | Client | Please verify with your bank |
| 10.105.0 016 | Invalid expiry date | Invalid expiry date. Please double check. | Client | Please verify with your bank or insert a valid Expiration date |
| 10.103.0 017 | Wrong code | Wrong code. Please double check. | Client | Please try again |
| 10.103.0 018 | Wrong code, 3 tentative exceed | Wrong code, 3 tentative exceeded. Please verify with your bank. | Client | Please contact you bank |
| 10.105.0 017 | Cancellation amount exceeds authorized amount. | Cancellation amount exceeds authorized amount. | Merchant | Please assure that the cancellation is equal to the total amount or less. |
| 10.105.0 018 | Authorization is cancelled | The authorisation was cancelled. | Merchant | Please assure that the Authorisation is not finalized |
| 10.105.0 019 | Authorization is already used | N/A | Merchant | Please assure that the purchase is equal to the total amount or less. |
| 10.105.0020 | Purchase amount exceeds authorized amount | N/A | Merchant | Please assure that the purchase is Equal the total amount or less. |
| 10.105.0 021 | Purchase already refunded | Purchase already refunded. | Merchant | Please assure that this operation belongs to this transaction. |
| 10.105.0022 | Amout is below commission | Amount is below comission. | Merchant | Please assure the minimum amount to allow the fee charge |
| 90.000.0001 | Exception | SIBS technical issue. Please try again later. | SIBS | Please try Again or later – Issue to be solved by SIBS |
| 90.000.0003 | Error in message format | SIBS technical issue. Please try again later. | SIBS | Please try Again or later – Issue to be solved by SIBS |