Introduction

Merchant-Initiated Transactions (MIT) are payments initiated by the merchant without the interaction of the payer. They are characterized by a lack of involvement of the payer in triggering each individual payment.
Such payments require that:

1. SCA is applied to the first transaction or action mandating the Merchant to initiate payment(s) and
2. There is an agreement between the payer and the merchant for the provision of products or services and potential costs associated with these.

Such payments can happen in the following cases:

• Recurring Payments for fixed or variable amounts
• Merchant funded installments
• The final amount is higher than the amount used at authentication time.

This can happen when additional charges are added to the initially agreed amount such as, a minibar in a hotel or fines with a rented car.

In case you would prefer to register your customer and store his credit card credentials on file, you are obliged to obtain cardholder’s consent by using Strong Customer Authentication (SCA) in your transaction request.
In order to achieve that, your cardholders must authenticate themselves during transaction processing, once the cardholder is still in session. PSD2 and scheme rules demand a 3-D Secure challenge flow to be performed in such case.

All mentioned above needs to be indicated to the Gateway, so that proper transaction flagging is applied in the authorization message.

Payment API

REST API integration specifics can be found here: REST API MIT Integration

SOAP API

SOAP API integration specifics can be found here: SOAP API MIT Integration