Additionally, Authorised Payment Server-to-Server Integration is available:
Create Authorised Payment: This step allows the Merchant to initiate an Authorised Payment creation.
List Authorised Payments: Through List integration, the Merchant can request the access to their list of available Authorised Payments.
Inquiry Authorised Payment: Through Inquiry integration, the Merchant can request the inquiry of a specific Authorised Payment.
Cancel Authorised Payment: Through Cancel integration, the Merchant can request the cancellation of a specific Authorised Payment.
Integration flows
Authorised Payment
These operations allow the creation of Authorised Payments.
Authorisation/Purchase under a valid Authorised Payment
The picture below shows the authorisation/purchase under a valid Authorised Payment flow, between the Merchant and SIBS:
1.1. Cardholder input the alias in the Merchant website.
1.2. Merchant website sends the alias and payment information to the SIBS Gateway.
2.1. SIBS Gateway sends Authorised Payment purchase request to MB WAY after identifying the related Authorised Payment.
3.1. Purchase result (status) is sent from MB WAY to SIBS Gateway.
3.2. SIBS Gateway sends the purchase result to the Merchant server.
4.1. The Merchant server will reconcile internally with the Merchant website.
5.1. Merchant website display to Cardholder the status of the payment.
In point 2.1. of the flow, in case the transaction exceeds the monthly amount limit and the Merchant has the “disableMandateMBWAYFallback” feature with value “False” or “Null”, MB WAY makes a MB WAY purchase with the same value of the transaction and notifies the Merchant. If this feature has the value “True”, then the operation is declined and a notification is sent to the Client and to the Merchant.
Capture
The picture below shows the Authorised Payment capture flow, between the Merchant and SIBS:
1.1. Merchant input capture information in the Merchant website;
1.2. Merchant website send the capture information to the SIBS Gateway;
2.1. SIBS Gateway returns the capture result to the Merchant website;
2.2. The Merchant website display to Cardholder the status of the capture.
Authorisation Cancellation
The picture below shows the Authorised Payment authorisation cancellation flow, between the Merchant and SIBS:
1.1. Merchant input the Authorisation Cancellation in the Merchant website;
1.2. Merchant website sends the payment information to the SIBS Gateway V02.00;
2.1. SIBS Gateway V02.00 returns the cancellation result to the Merchant website;
2.2. The Merchant website returns the status of the cancellation.
Purchase/Capture Refund
The below flow shows the Authorised Payment purchase/capture refund flow, between the Merchant and SIBS:
1.1. Merchant input a refund request through the Backoffice or API.
1.2. Merchant website sends the refund request and details to the SIBS Gateway.
2.1. SIBS Gateway return the operation status to the Merchant website.
2.2. Merchant website returns the refund result to the Cardholder.
Authorised Payment Creation by Client
The picture below shows the Authorised Payment creation flow, between the Client and SIBS:
1.1. Cardholder input the alias in the Merchant website and accepts Authorised Payment creation.
1.2. Merchant website sends the alias and Authorised Payment information to the SIBS Gateway.
2.1. Authorised Payment creation request is sent to SIBS Gateway (MB WAY).
3.1. Cardholder should receive a push message to authorise, define monthly cap limit and expiration date.
4.1. Authorised Payment creation details (e.g. Status) is sent from MB WAY to SIBS Gateway.
4.2. SIBS Gateway sends the Authorised Payment creation result to the Merchant server.
5.1. The Merchant server internally reconciles with the Merchant website.
6.1. Merchant website displays to Cardholder the status of the creation.
Authorised Payment Creation by Merchant
The picture below shows the Authorised Payment creation flow, between the Merchant and SIBS:
1.1. Merchant inputs the alias in the Merchant Server and accepts Authorised Payment creation.
1.2. Merchant website sends the alias and Authorised Payment information to the SIBS Gateway.
2.1. Authorised Payment creation request is sent to SIBS Gateway (MB WAY).
3.1. Cardholder should receive a push message to authorise, define monthly cap limit and expiration date.
4.1. Authorised Payment creation details (e.g. Status) is sent from MB WAY to SIBS Gateway.
4.2. SIBS Gateway sends the Authorised Payment creation result to the Merchant server.
Authorised Payment Creation during Purchase/Authorisation
The picture below shows the Authorised Payment creation during a purchase/authorisation operation flow, between the Client and SIBS. The purchase/authorisation runs as defined in MB WAY (ID). Afterwards, the MB WAY creation is performed:
In MB WAY purchase/authorisation business context, the following steps will occur:
1.1. Cardholder input the alias in the Merchant website and accepts Authorised Payment creation.
1.2. Merchant website sends the alias and Authorised Payment information to the SIBS Gateway V02.00.
2.1. Authorised Payment creation request is sent to SIBS Gateway V02.00 (MB WAY).
3.1. Cardholder should receive a push message to authorise, define monthly cap limit and expiration date.
4.1. Authorised Payment creation details (e.g. Status) is sent from MB WAY to SIBS Gateway V02.00.
4.2. SIBS Gateway V02.00 sends the Authorised Payment creation result to the Merchant server.
5.1. The Merchant server internally reconciles with the Merchant website.
6.1. Merchant website displays to Cardholder the status of the creation.
If a Client performs a purchase/authorisation under a previously established Authorised Payment, the transaction is performed without a Client push notification for MB WAY authentication. SIBS Gateway returns the execution result of the authorisation request. If this operation is sucessful, the transaction shall be considered to be in the “sucess” status.
Authorised Payment List
The following diagram shows the Authorised Payment list flow, between the Merchant and SIBS:
1.1. Merchant requests Authorised Payment list, using the Backoffice or API.
1.2. Merchant website sends the list request to SIBS Gateway.
2.1. SIBS Gateway returns the Authorised Payment list to the Merchant website. Pagination data may be included.
2.2. Merchant website presents list results.
Authorised Payment Inquiry
The following diagram shows the Authorised Payment inquiry flow, between the Merchant and SIBS:
1.1. Merchant requests Authorised Payment inquiry, using the Backoffice or API.
1.2. Merchant website sends the inquiry request to SIBS Gateway.
2.1. SIBS Gateway returns the Authorised Payment data to Merchant website.
2.2. Merchant website presents Authorised Payment details.
Authorised Payment Inquiry Detail
The following diagram shows the Authorised Payment inquiry detail flow, between the Merchant and SIBS, in which the Merchant requests for Financial Data of an Authorised Payment.
1.1. Merchant requests Authorised Payment inquiry details, using the API.
1.2. Merchant website sends the inquiry detail request to SIBS Gateway.
2.1. SIBS Gateway returns the Authorised Payment Financial data to Merchant website.
2.2. Merchant website presents Authorised Payment financial data.
Authorised Payment Cancellation
The following diagram shows the Authorised Payment cancellation flow, between the Merchant and SIBS:
1.1. Merchant inputs an Authorised Payment cancellation request through the Backoffice or API.
1.2. Merchant website sends the Authorised Payment cancellation request and to the SIBS Gateway V02.00.
2.1. SIBS Gateway V02.00 sends Authorised Payment cancellation request to MB WAY after identifying the related Authorised Payment.
2.2. Authorised Payment cancellation result (Status) is sent from MB WAY to SIBS Gateway V02.00.
3.1. SIBS Gateway V02.00 returns the operation status to the Merchant website.
3.2. Merchant website presents the cancellation result.