Payments glossary

Merchant-initiated transaction (MIT)

A merchant-initiated transaction (MIT) is a payment charged to a stored card without the customer present - a subscription renewal, instalment or automatic top-up - made under a prior agreement using a token and referencing the original authorised transaction.

Payments while the customer is away

A merchant-initiated transaction is a payment the merchant triggers against a stored credential without the customer being present: a monthly subscription renewing, usage-based billing closing out the month, an instalment falling due, an account topping itself up. Because the customer cannot authenticate at the moment of charging, the payment's legitimacy rests on the mandate - an agreement established during an initial customer-initiated payment, typically authenticated with 3-D Secure.

The scheme framework

The card schemes formalised stored-credential rules so issuers can tell a legitimate absent-customer charge from a suspicious one. The initial, authenticated transaction establishes the agreement; every subsequent MIT must be flagged as merchant-initiated, carry the correct type - recurring, instalment or unscheduled - and reference the original transaction through a scheme-assigned transaction ID chain. This is not bureaucracy: issuers approve well-formed MITs at meaningfully better rates and exempt them from step-up authentication the absent customer could not complete.

MITs in South Africa

Subscription commerce, insurance premiums and SaaS billing all run on MITs, and in South Africa card-based MITs sit alongside DebiCheck debit orders as the main tools for collecting recurring revenue - cards offering immediate authorisation feedback, debit orders drawing directly on bank accounts. LekkaPay's tokenisation and recurring billing handle the token storage, MIT flags and transaction-ID chaining that scheme compliance requires.

Last updated:

Payments without the jargon.

One integration, every way Africa pays - we'll handle the acronyms.