Merchant-initiated transactions (MITs) allow merchants to charge a customer's payment method at a later time, without the customer being present. MITs are initiated by the merchant, rather than the customer, and are typically used for subscription-based businesses, installment payments, split payments, and penalty payments.
MITs require saved payment information, for information about how to save payment information see our dedicated guide Saving payment information.
Merchant-initiated transactions provide several benefits to merchants:
- Increased customer retention: With MITs, merchants can set up recurring payments, making it easier for customers to continue using their services or products.
- Reduced operational costs: MITs automate the payment process, eliminating the need for manual payments and reducing administrative tasks and costs.
- Improved cash flow: By automating the payment process, merchants can improve cash flow by ensuring timely payments.
Merchants who wish to use MIT from their backend system need to integrate the IXOPAY platform REST API.
To perform a merchant-initiated transaction, merchants have to provide a
referenceUuid field that points to the previous transaction ID that stored the payment instrument.
This way, merchants can easily charge customers' stored payment information without requiring additional authorization from the customer.
Typically, merchant-initiated transactions are started with one of these transaction types:
- Debit: A payment transaction where the funds are immediately transferred.
- Preauthorize: A payment transaction where the merchant reserves the amount of the payment on the customer's card but does not transfer funds until a capture API call is made. If the merchant needs to void the transaction, the funds will be deallocated. For details, see our article on saving payment information.
- Incremental authorization: A follow-up payment transaction to a previous preauhtorize transaction that increases or prolongs the authorized amount on the customer's card. For details, see our article on saving payment information.
To indicate what kind of payment a merchant is planning, a transaction indicator is used.
You should supply a
transactionIndicator when creating a new transaction,
if a merchant does not provide a transaction indicator, a default value will be used.
For debit and preauthorize transactions, the default transaction indicator is
SINGLE, which indicates a one-time payment.
For register transactions, the default transaction indicator is
INITIAL, which indicates the first of a series of payments.
For merchant-initiated transactions, the following transaction indicators are relevant:
|A subsequent payment in a series of payments, it is initiated by the merchant. Follows a customer initiated transaction with transaction indicator |
|A single payment with stored payment information, it is initiated by the merchant.|
For a full list of transaction indicators, please see our separate transaction indicators page in the reference.
When initiating a merchant-initiated transaction, merchants must ensure that they have the customer's explicit consent to charge their payment method. Merchants must also ensure that they have the necessary authorization to charge the payment method.
Merchants should also keep in mind that authorization requirements may vary depending on the payment method and the customer's location. For example, some payment methods may require preauthorization or authorization for the entire payment amount before the merchant can initiate an merchant-initiated transaction.
It is important to note that the first payment made using a credit card must have strong customer authentication (SCA) enabled.
In this section, we explore different use cases for merchant-initiated transactions and how to implement them using the IXOPAY platform.
- Recurring payments (subscriptions): Merchants can offer subscription-based services and charge their customers on a regular basis (e.g., weekly, monthly, yearly). With recurring payments, the merchant stores the customer's payment information and initiates payments at regular intervals without the need for the customer to take any action. The customer is usually notified beforehand about the recurring nature of the payments and has the option to cancel at any time. For more information, refer to the getting started guide on recurring payments.
- Installments or split payments (buy now, pay later): Merchants can offer customers the option to pay for their purchases in installments. This can be useful for large purchases that customers may not be able to pay for in one go.
Steps to use:
- Save payment details, see our guide Saving payment information.
- Optionally, notify the customer about upcoming payment.
- Make a debit API call on merchant's backend with the
- Invoice customer, repeat steps 2–3 until the full amount is paid or subscription is cancelled.
Single payments can be used for delayed charges (provide service now, but charge the actually consumed service later) and penalty charges (no-show penalty for hotels, other penalties as examples). Here are some common use cases:
- Delayed Charges: Merchants can offer services or goods to customers without charging them immediately, and instead charge them later.
- Penalty Charges: Merchants can charge customers for penalties such as no-show fees for hotels or late return fees for rental services.
Steps to use delayed charges:
- Save payment details using a preauthorize API call with the
CARDONFILE-MERCHANT-INITIATEDtransaction indicator. See our guide Saving payment information for more details.
- Provide service or goods to customer.
- Make a capture API call on merchant's backend.
Steps to use penalty charges: