The accounting period closure of the MB WAY POS is automatically performed at 01:00 AM, on a daily basis, at SIBS central system. The financial operations’ clearing occurs daily, at 08:00 PM. All the transactions completed in the accounting period that starts at 01:00 AM and ends at 08:00 PM are included in the clearing cycle of the day. The transactions that occur between 08:00 PM and 01:00 AM are cleared to be credited at the Merchant’s account in the clearing cycle immediately after the accounting period closure.
Nevertheless, the Merchant may customise the accounting period closure at the most convenient and suitable timings, aiming at a better financial control of his business. For this purpose, the Merchant must send an MB WAY POS closure request, via MerchantOperationalWS web service. The MB WAY POS closure will no longer be processed in an automatic way.
However, if the Merchant does not send any closure request during 7 days, the MB WAY POS closure processing reverts to the standard automatic closure at SIBS central system. If the Merchant wishes to revert the closure processing to the automatic way before reaching the seventh day, the Merchant must contact his Acquirer to perform the necessary configurations at SIBS.
MerchantOperationalWS
This web service allows the Merchant to request an MB WAY POS accounting period opening or closure.
Upon receiving a request of MB WAY POS closure from the Merchant, SIBS validates the Merchant certificate and validates if the closure request is a first request or a resubmission, and returns the necessary data for the MB WAY POS closure operation:
- Total number of operations performed during the accounting period, per operation type;
- Total number of operations, their amount and corresponding fees (Merchant Fees – MFs).
The input elements and body example to consider when performing a POS Closure request are described below:
| Attribute | Status | Type | Length | Rules / observations |
|---|---|---|---|---|
| messageType | [1-1] | String | 5 | Message code with the value ‘N0001’ |
| operationInformation | [1-1] | OperationInformation | OperationInformation entity | Operation identifier. |
| merchant | [1-1] | Merchant | MerchantEntity table | Merchant identifier. |
| messageProperties | [1-1] | MessageProperties | MessageProperties entity table | Set of general properties, present in all messages. |
<arg0><messageType>N0005</messageType><operationInformation>
<merchantOprId>1002</merchantOprId>
</operationInformation><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>
The output elements and body example to consider within a response of a POS Closure request are described below:
| Attribute | Status | Type | Length | Rules / observations |
|---|---|---|---|---|
| messageCode | [1-1] | String | 4 | This attribute informs the message type; in this case, its value is always ‘Y142’. |
| merchantOperationId | [1-1] | String | 20 | Operation unique identifier. |
| reversalRequest | [1-1] | String | 1 | Data element for requesting a reversal. For a positive response, this attribute contains the value ‘1’. Otherwise, it is populated with ‘0’ or ‘2’. |
| posID | [1-1] | String | 9 | POS identification. |
| periodNumber | [1-1] | String | 3 | Number of the POS accounting period closure that includes the returned values. |
| transactionNumber | [1-1] | String | 3 | Transaction identifier. Starts with ‘001’ for each ‘A031 Accounting Period’ and is incremented by ‘1’ at each sequentially numbered transaction. |
| messageNumber | [1-1] | String | 3 | Sequential number assigned by the terminal for each message sent to SIBS host. It starts with the value ‘000” and when it reaches the value ‘999’, it resets to ‘000’. |
| transactionVersion | [1-1] | String | 3 | Transaction version identifier. The first digit is the letter ‘V’, followed of two numeric digits that represent the version number. |
| pmIdentification | [1-1] | String | 8 | PINPAD identification. |
| mac | [1-1] | String | 3 | Message authentication code calculated with the MAC key of the PINPAD/OEM devices for message requests. |
| requestedTransaction | [1-1] | String | 4 | This attribute is used to request the terminal to activate a specific transaction, after completion of the current one. Filled with spaces if no transaction is requested. |
| responseCode | [1-1] | String | 3 | Response code that SIBS sends to the transaction started at a terminal. Positive responses contain the value “000”. Negative responses contain a value higher than “000”, which is an internal reference defined by SIBS to identify declined transactions. |
| statusCode | [1-1] | String | 3 | Return Code |
| positiveResponseInformation | [0-1] | positiveResponseInformation | See Table positiveResponseInformation entity | – |
| negativeResponseInformation | [0-1] | negativeResponseInformation | See Table negativeResponseInformation entity | – |
The several entities are defined as follows:
positiveResponseInformation entity
| Attribute | Status | Type | Lenght | Rules |
|---|---|---|---|---|
| cardID | [1-1] | String | 20 | N.A. |
| merchantAccount | [1-1] | String | 15 | Merchant account used in one or more payment terminals. |
| merchantBaseCurrencyCode | [1-1] | String | 4 | Identifies the currency code used by the Merchant. |
| totalMerchAmountSignal | [1-1] | String | 1 | Signal of the totalMerchAmount attribute, to indicate debit (signal -) or credit (signal +). |
| totalMerchAmount | [1-1] | String | 10 | Total amount of the transactions completed during the accounting period. It can be ‘debit’ or ‘credit’, depending on the totalMerchAmountSignal. |
| transactionTools | [1-12] | transactionTotals | See table TransactionTotal s Entity | – |
| ComissionTotals | [0-61] | commissionTotals | See table comissionTotalsEntity | – |
| ReceiptBody | [1-1] | String | 421 | Receipt’s text body. |
TransactionTotals entity
| Attribute | Status | Type | Length | Rules / observations |
|---|---|---|---|---|
| transactionDescription | [1-1] | String | 10 | Label returned by the host to identify the totals returned in the subsequent fields. |
| totalTransactions | [1-1] | String | 3 | Total number of transactions of the same type performed during the same period. |
| amountTotal | [1-1] | String | 10 | Total amount of the transactions informed in totalTransactions. |
ComissionTotals entity
| Attribute | Status | Type | Length | Rules / observations |
|---|---|---|---|---|
| contractDescription | [1-1] | String | 10 | Label returned by the host to identify the totals returned in the subsequent fields. |
| totalTransactions | [1-1] | String | 3 | Total number of transactions of the same type performed during the same period. |
| amountSignal | [1-1] | String | 1 | Negative (-) or positive (+) signal associated to the amount. |
| TotalAmount | [1-1] | String | 1 | Transactions total per transaction type. |
| comissionSignal | [1-1] | String | 1 | Negative (-) or positive (+) signal associated to the fee. |
| totalComission | [1-1] | String | 8 | The sum total of the fees charged on the transactions performed within the accounting period, with cards under a given acquiring agreement. |
negativeResponseInformationentity
| Attribute | Status | Type | Length | Rules / observations |
|---|---|---|---|---|
| negativeResponseData | [1-1] | String | 42 | – |
Here’s an example of the output of a POS closure request:
<return><messageCode>Y142</messageCode><reversalRequest>1</reversalRequest><posId>9999</posId><periodNumber>0</periodNumber><transactionNumber>0</transactionNumber><messageNumber>0</messageNumber><transactionVersion>V23</transactionVersion><pmIdentification>99999999</pmIdentification><mac>PPM</mac><requestedTransaction/><responseCode>0</responseCode><statusCode>000</statusCode><positiveResponseInformation><cardId>***1234 5678 9012 34</cardId><merchantAccount>99999999</merchantAccount><merchantBaseCurrencyCode>9782</merchantBaseCurrencyCode><totalMerchAmountSignal>+</totalMerchAmountSignal><totalMerchAmount>198</totalMerchAmount><transactionTotals><transactionDescription>COMPRA</transactionDescription><totalTransactions>1</totalTransactions><amountTotal>200</amountTotal></transactionTotals><commissionTotals><contractDescription>MB</contractDescription><totalTransactions>1</totalTransactions><amountSignal>+</amountSignal><totalAmount>200</totalAmount><commissionSignal>+</commissionSignal><totalCommission>2</totalCommission></commissionTotals><receiptBody>MDIKICAgICAgICAgICAgICAgICAgICAM</receiptBody></positiveResponseInformation></return