SIBS’ Marketplace solution also provides a list of registered Submerchants by status. This list can be extracted directly via API or through SIBS Backoffice platform.

The Daily File for the Marketplace Operator aims to provide the Marketplace Operator with a detailed view of the transactions on its Marketplace, including all information regarding splits, payouts and settlement orders that have been created or changed between the generation of the last report and the time of creating of the new report Unlike the Omni-Channel Statement for Merchants, in this file the Marketplace Operator will only view their transactions on the Marketplace solution, and not the remaining transactions on the other channels, such as SIBS Payment Gateway or Point-of-Sales (POS).

The EXTO file enables Merchants to receive, in an integrated manner, details of the transactions per reconciliation and respective fees, carried out through the different channels contracted with EATs and Acquirers, regardless of the scheme contracted. This file provides the Merchant with a complete and detailed overview of their payment business. In the specific case of the Marketplace solution, the Marketplace Operator can view all transactions carried out on its Marketplace, with information per split, respective Submerchant and associated fee, along with its transactions on the other channels, if applicable.

There are three main reporting tools provided to the Marketplace Operator: Omni-channel file (EXTO file), Marketplace daily report and other reports available on SIBS Backoffice. This tools are described in the following sections.

SIBS Backoffice is an online platform that allows Merchants, who are SIBS Customers, to access a set of useful features in the management and monitoring of business variables related to SIBS services. In the context of the Marketplace solution, SIBS Backoffice is used by the Marketplace Operator, SIBS, Acquirer, EAT and Submerchants as a backoffice tool, but also serves to register new Submerchants operating on the platform.   The features of SIBS Backoffice that are directly related to SIBS’ Marketplace solution are described in the following sections.  “Marketplace” Menu  The “Marketplace” menu is displayed for customers who have contracted the Marketplace solution. Within this menu are two additional submenus: “Parameters” and “Submerchants”. In the “Parameters” submenu, the user can define the type of validations they wish to be applied to their Submerchants and, through the “Submerchants” submenu, the Marketplace Operator has the opportunity to register new Submerchants or inquire Submerchants already registered in the solution.  Configuration In the “Parameters” submenu, the user must define who will be responsible for validating the Submerchants. This process, required by payment industry regulations, can be performed by the Acquirer(s) of the solution or can be delegated to the Marketplace Operator. By selecting the option “Validation […]

Split initiation: Post Split and Payout Information Allows the Marketplace Operator to post (send) splits and payouts of a purchase. Access via SIBS API Market: This feature requires sending parameters at the Request level that have the following characteristics: Parameters of “Post Split and Payout Information” Parameter Meaning Accepted values and their meaning Format Minimum lenght Maximum length Type “split-type” Split Type “Purchase” “Refund” String – – Mandatory “submerchant” “code” Submerchant Code – Numeric 8 8 “submerchant” “externalTransactionId” Transaction external ID – String 1 32 “originalSplitTransactionId” split original ID – String 1 14 “split” – “amount” Split Amount – Numeric 12.6 12.6 “split” “split” – “currency” Currency Code “968” – EURO Numeric 3 “splitFee” – “amount” MO free amount – Numeric 12.6 “splitFee” – “currency” MO free currency “968” – EURO Numeric 3 “SplitSchedulingDate” PayoutDate – Date – – Change Payout Scheduling Allows the Marketplace Operator to change the payout date of a split. Access via SIBS API Market: This feature requires sending parameters at the Request level that have the following characteristics: Parameters of the “Change Payout Scheduling” feature Parameters Meaning Accepted values and their meaning Format Minimum lenght Maximum lenght Type “submerchant” “code” Submerchant Code – Numeric 8 […]

Add Submerchant Allows the Marketplace Operator to add a new Submerchant.  Access via SIBS API Market: This feature requires sending parameters at the Request Level that have the following characteristics: Parameter Meaning Accepted values and their meaning Format Minimum length Maximum length Type “submerchant” “taxIdentificationNumber” Taxpayer Identification Number or Legal Person Fiscal Number  – String 1 20 Mnafatory “name” Nmae – String 1 40 Mandatory “shortName”  Short Name;  – String 1 20 Mandatory “sic” SIC – Standard Industrial Classification Code – (CAE: Classificação das Atividades Económicas)  – Decimal 1 5 Mandatory “socialObject” Business Activity – String 1 150 Optional “Settlement TypeCode” Clearing type “SPA” – Single Euro Payments Area String 3 3 Mandatory “refundMaxAmoun” Daily maximum amount for Refunds – Decimal 1 14.5 Optional “payoutTypeCode” Payout type “MAN” – Manual Payout“AUT” – Automatic Payout“SCH” – Scheduled Char 3 3 Mandatory “deferredAgreementDays” Number of days after which the payout should be made – Number 3 3 Mandatory “financial” “IBAN” International Bank Account Number – String 3 34 Mandatory “BIC” Bank International Code – String 1 11 Mandatory “address” “street” Address – String 1 40 Optional “postalCode” Postal Code – String 1 25 Optional “locality” City – String 1 20 Optional “postalLocality” […]

The Marketplace solution presupposes the availability of APIs which, in turn, make it possible to carry out a variety of operations. The following subsections detail each of these.

Split payments is the partition of funds amongst the Marketplace Operator and Submerchants. Every split is fully customized by the Marketplace Operator, who is in charge of defining split rules, according to the terms negotiated with each Submerchant, and the fees associated with the transaction, when applicable. The split request process is triggered by the Marketplace Operator via Split API. Splits can be triggered transaction by transaction, i.e. payment by payment, or in bulk, for example at the end of the day or the month. There are two types of splits: purchase and refund. A split refund annuls the split amount to be transferred, if the payout has not yet been processed. The provisioning and risk of the escrow account is the responsibility of the Marketplace Operator. In order to execute the respective transfers, the account must always be provisioned, and it cannot have negative values.