Alias operations are optional and they are originated by the Merchant, since this service type has been agreed with and positioned at SIBS. However, on what concerns the in-app operative, the alias concept applies to the user token, which is needed to invoke the MB WAY app.

MerchantAliasWSCreate

Through this web service, the Merchant may submit a “Create Merchant Alias” request for a given User after this User has made a successful “Purchase” or “Authorisation”. This operation must be accepted by the User in MB WAY app and the result is asynchronously communicated to the Merchant through the CreateMerchantAliasAsyncResult service.

After having accepted the Merchant Alias association to MB WAY, the User may cancel this association, through the MB WAY app, without notification to the Merchant. In such a case, the Merchant receives an “Unknown Alias” error if he attempts to perform a “Purchase” with that Alias.

User Token

The MerchantAliasWSCreate web service is used to request the user token creation (aliasTypeCde ‘010’). In this case, the response is synchronous, because the user does not have to make any decision (acceptance or rejection) in the MB WAY app.

Here is the element decription to consider within input of the “Create Merchant Alias” request:

Here’s a code snippet with an example of the input body to consider:

<arg0><messageType>N0001</messageType><alias><aliasName>351#960000000</aliasName><aliasTypeCde>001</aliasTypeCde></alias><merchant><iPAddress>255.255.255.255</iPAddress><posId>9999</posId></merchant><messageProperties><channel>01</channel><apiVersion>1</apiVersion><channelTypeCode>VPOS</channelTypeCode><networkCode>MULTIB</networkCode><serviceType>01</serviceType><timestamp>2001-12-17T09:30:47Z</timestamp></messageProperties><newAlias><aliasName>87567-987854-87657</aliasName><aliasTypeCde>005</aliasTypeCde></newAlias></arg0>

Below we provide you with the element decription to consider within output of the “Create Merchant Alias” request:

Below, the output body example:

<return>
<alias><aliasName>351#920000000</aliasName> <aliasTypeCde>001</aliasTypeCde></alias><operationId>5090</operationId><statusCode>000</statusCode><timestamp>2001-12-17T09:30:47Z</timestamp><token>123456789dfghjklcvvnm6789ertyui4</token>
</return>

MerchantAliasWSRemove

This web service allows the removal of a Merchant Alias created for a given User or, in the case of the in-app operative, the removal of a user token.

Here is the element decription to consider within input of the “Remover Merchant Alias” request followed by the input body example:

<arg0><messageType>N0002</messageType><alias><aliasName>87567-987854-87657</aliasName><aliasTypeCde>005</aliasTypeCde></alias><merchant><iPAddress>255.255.255.255</iPAddress><posId>9999</posId></merchant><messageProperties><channel>01</channel><apiVersion>1</apiVersion><channelTypeCode>VPOS</channelTypeCode><networkCode>MULTIB</networkCode><serviceType>01</serviceType><timestamp>2001-12-17T09:30:47Z</timestamp></messageProperties>
</arg0>

For this webservice request, consider the following output elements followed by its output body example:

<return><alias><aliasName>87567-987854-87657</aliasName><aliasTypeCde>005</aliasTypeCde></alias><statusCode>000</statusCode><timestamp>2001-12-17T09:30:47Z</timestamp></return>

Create Merchant Alias Aysnc Result

Through this web service (Not applicable for in-app operative), the Merchant receives the result of the operation “Create Merchant Alias”, upon acceptance or rejection by the User.

Although there is no service output, its delivery is validated to correctly finalise the operation through the http response.

This service is supplied by the Merchant application and must comply with the following naming:

@WebService(name="CreateMerchantAliasAsyncResult", targetNamespace="http://webservices.sibsmerchant.com/")
public class CreateMerchantAliasAsyncResult@WebMethod
public void createAliasResult(CreateMerchantAliasResult arg0)

The input elements to perform a “Crete Merchant Alias” request are described below: