Merchant-Initiated Transaction (MIT)
Abbreviation: MIT
Pronunciation: MUR-chuhnt ih-NISH-ee-ay-tid tranz-AK-shun (EM-eye-TEE)
Also known as: Merchant-Initiated Payment, MIT
Definition
Merchant-Initiated Transaction (MIT) is a later payment initiated by a merchant under a prior customer agreement rather than through the customer actively completing the current payment. In merchant payment acceptance, it commonly covers stored payment authority, mandate or agreement, recurring or unscheduled charges, amount rules, timing, notifications, and evidence. It differs from a customer-initiated transaction because the customer is not actively participating at the moment the charge is submitted. Operationally, teams should capture valid consent, classify transactions correctly, retain mandate evidence, limit charges to agreed terms, notify customers, and handle failures or disputes.
Overview
Merchant-Initiated Transaction (MIT) is a later payment initiated by a merchant under a prior customer agreement rather than through the customer actively completing the current payment. Its practical use in merchant account and operating management depends on a clearly defined scope, authoritative record, responsible owner, and connection to the underlying customer or commercial obligation.
It differs from a customer-initiated transaction because the customer is not actively participating at the moment the charge is submitted. Related operational concepts include Recurring Billing, Subscription Renewal, and Merchant Reference, each of which should retain a separate definition and system owner.
It normally interacts with Recurring Billing and Subscription Renewal, although the exact system boundaries vary by merchant and platform. Operationally, teams should capture valid consent, classify transactions correctly, retain mandate evidence, limit charges to agreed terms, notify customers, and handle failures or disputes. A reliable implementation proves customer authority where required, verifies payment through trusted server-side events, and preserves the relationship between payment, order, and merchant records.
In merchant payment acceptance, it commonly covers stored payment authority, mandate or agreement, recurring or unscheduled charges, amount rules, timing, notifications, and evidence. The concept commonly includes stored payment authority, mandate or agreement, recurring or unscheduled charges, amount rules, timing, notifications, and evidence.
Controls for Merchant-Initiated Transaction (MIT) should use verified merchant mappings, least-privilege roles, approved settlement changes, configuration versioning, monitored production activity, reconciled statements and balances, and retained agreements. Reviews should confirm that customer-facing identity and support obligations match the responsible legal merchant. The audit scope should also preserve its distinguishing context: Merchant-Initiated is a later payment by a under a prior.
Key Takeaway
Merchant-Initiated Transaction (MIT) is a later payment initiated by a merchant under a prior customer agreement rather than through the customer actively completing the current payment. Connect it to the correct legal merchant, configuration, responsibility, settlement, and reporting records.
Sources
- Build a Stripe-hosted checkout page — Stripe (2026-08-02)
- Accept a payment with the Express Checkout Element — Stripe (2026-08-02)