Payment Gateway Portugal
Card
SIBS offers card transaction acceptance services in an e-commerce environment, covering the international brands Visa, Mastercard, American Express and UnionPay (UPI).
The solution is fully compliant with the efficiency and security standards stipulated by these brands, using international security standards such as PCI-DSS and 3D Secure, guaranteeing the protection of transactions.
On Card the user has the Purchase and Token scenarios available on Sandbox.
In each of the available test scenarios, after clicking on Run in Postman, you will get an API Response and a specific Webhook Response.
Purchase
| Result Status | Status Description | StatusCode | Postman |
| Success | Success | 000 | ? |
| Failed | Invalid card data. Card number, CVV or expiration date is invalid | E0700 | ? |
| Failed | Invalid card | E0701 | ? |
Token
| Result Status | Status Description | StatusCode | Postman |
| Generation – Success | Success | 000 | ? |
| Purchase – Success | Success | 000 | ? |
| Generation – Failed | SIBS Internal Error | E9999 | ? |
| Purchase – Failed | Invalid card | E0701 | ? |
MULTIBANCO Reference
The MULTIBANCO reference payment method, also known as Payment for Services, has been optimised and, in order to make it more adapted to digital commerce, it has been included with the possibility of generating references in real time via webservices, allowing the attributes of amounts and start and end dates of validity of the reference to be parameterised immediately.
In each of the available test scenarios, after clicking on Run in Postman, you will get an API Response and a specific Webhook Response.
Generate
| Result Status | Status Description | StatusCode | Postman |
| Pay Reference – Success | Success | 000 | ? |
Expired Reference
| Result Status | Status Description | StatusCode | Postman |
| Failed | Payment reference is cancelled | E0612 | ? |
Expired Reference
| Result Status | Status Description | StatusCode | Postman |
| Failed | Payment reference is cancelled | E0612 | ? |
MB WAY
MB WAY is SIBS’ mobile solution that offers an innovative approach to online and physical payments, instant transfers, generation of MB NET virtual cards and withdrawals via smartphone, tablet or PC.
Payment card holders who are members of MB WAY can make purchases with the highest level of security guaranteed, because no payment card data is ever exposed and because there is no need for the user to authorise each debit – this authorisation is done in the MB WAY app using data that only the user knows or holds (PIN code or fingerprint).
In the context of MB WAY purchasing with an alias refers to the ability to make payments using a simplified identifier, like a phone number or a user-specific alias, rather than entering detailed account or card information.
On MB WAY the user has the Purchase with Alias and Authorised Payments scenarios available on Sandbox.
Purchase with Alias
With MB WAY, users can associate their bank account or payment details with a unique alias (a phone number). This alias allows them to make payments without needing to enter sensitive information such as account numbers or card details every time they make a transaction.
In each of the available test scenarios, after clicking on Run in Postman, you will get an API Response and a specific Webhook Response.
| Result Status | Status Description | Status Code | Run in Postman |
| Success | Success | 000 | ? |
| Failed | Operation was not accepted by the card holder | E0500 | ? |
| Failed | Invalid request, data is missing or is invalid | E0501 | ? |
| Failed | Insufficient funds | E0113 | ? |
| Failed – Non-existent alias | The provided alias has an invalid format | E0504 | ? |
| Failed – Non-existent alias | The provided alias does not exists | E0506 | ? |
Authorised Payments
MB WAY’s ‘Authorised Payments’ feature is an innovative solution that allows users to authorise recurring or one-off payments in a simple, secure and convenient way. Authorised Payments are particularly useful in situations that require the automation of payment processes, such as subscriptions, automatic payment services or periodic collections. Its main benefits include ease of use, which allows users to activate, manage and cancel payment authorisations directly from the MB WAY app, eliminating the need for manual intervention for each transaction. It enables high levels of security through the use of strong customer authentication and strict compliance with PSD2 standards, ensuring the protection of data and transactions.
There are two different types of Authorised Payments:
- One Click: for one-off payments, in which the customer can perform purchases without the need of validation;
- Subscription: automatic recurring payments (e.g. monthly, yearly subscriptions, etc.) without the need of customer authentication for each billing payment.
In each of the available test scenarios, after clicking on Run in Postman, you will get an API Response and a specific Webhook Response.
| Result Status | Status Description | Status Code | Postman |
| Oneclick – Success | Creation | 000 | ? |
| Oneclick – Success | Payment | 000 | ? |
| Oneclick – Success | Refund | 000 | ? |
| Oneclick – Success | Cancelation | 000 | ? |
| Oneclick – Failed | Cancelation | E0520 | ? |
| Oneclick – Failed | Payment | E0518 | ? |
| Subscription – Success | Creation | 000 | ? |
| Subscription – Success | Payment | 000 | ? |
| Subscription – Success | Refund | 000 | ? |
| Subscription – Success | Cancelation | 000 | ? |
| Subscription – Failed | Cancelation | E0520 | ? |
| Subscription – Failed | Payment | E0518 | ? |
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.
Notification MULTIBANCO – Asynchronous: Make request – Need action – Get response
Complex Types
MerchantNotificationRequest
Body
MerchantNotificationResponse
Body
String (Maximum 256 Text) (ex: Success)
Possible values are {“Success”, “Partial”, “Declined”, “InProcessing”, “Pending”, “Timeout”, “Error”}.
Error message
Multibanco
| Error code | Message to the Merchant | Message to the Client | Owner | What to do? |
|---|---|---|---|---|
| 10.107.0001 | Invalid payment entity | Entity not valid, Try again later. | Merchant | Please verify that the correct Merchant entity is being used. |
| 10.107.0002 | Invalid reference minimum amount | Invalid reference minimum, amount please try again. | Merchant | Please verify the parameterization in the amount |
| 10.107.0003 | Invalid reference maximum amount | Invalid reference maximum amount please try again. | Merchant | Please verify the parameterization in the amount |
| 10.107.0004 | Invalid currency | Invalid currency try again. | Merchant | Please verify the parameterization in the currency accepted |
| 10.107.0005 | Invalid NIB | Invalid NIB please try again. | Client | Please verify you are using the correct NIB |
| 10.107.0006 | Invalid reference initial date time | Invalid reference initial date time try again. | Merchant | Please verify the parameterization in time accepted |
| 10.107.0007 | Invalid reference limit date time | Invalid reference limit date time try again. | Merchant | Please verify the parameterization in time accepted |
| 10.107.0008 | Invalid Email | Invalid Email try again. | Client | Please insert the email used on the registration |
| 10.107.0009 | Payment entity is not active | Payment entity is not active, try later | Merchant | Please verify your entity, if it is the one in the SLA |
| 10.107.0010 | Reference generation not allowed for the payment entity | Reference generation not allowed try later. | Merchant | Please verify your entity, if it is the one in the SLA |
| 10.107.0011 | Payment reference not found | SIBS Internal error, Please try again later. | SIBS | SIBS Internal error, Please try again later. |
| 10.107.0012 | Payment reference is cancelled | Payment reference is cancelled. | Merchant | Please verify your reference was cancelled. |
| 10.107.0013 | Payment reference already paid | Payment reference already paid. | Merchant | Please verify your reference is already paid. |
| 10.107.0014 | Invalid operation | Invalid operation, try later. | SIBS | SIBS Internal error, Please try again later. |
| 90.000.0001 | Exception | SIBS Technical Issue 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 try again later | SIBS | Please try Again or later – Issue to be solved by SIBS |
Tokens configuration
In the “SIBS Payment Gateway 2.0” -> “Token Configuration” you can choose if you want Tokenisation at a merchant level or at a merchant and acceptor level.
SIBS Backoffice will provide a token management according to the selected setting.
Endpoints
Widget Endpoint: The <ROOT_URL> will depend on the environment where we are working.
ROOT_URL QLY
https://api.qly.sibspayments.comROOT_URL PRD
https://api.sibspayments.com To be a valid Merchant on SIBS Gateway V02.00 it will be necessary to have an authorisation token (<AuthToken>), <terminalId>.