Merchant-Initiated vs Customer-Initiated Transactions Explained
Merchant-initiated transactions are payments a merchant starts without the customer taking part at that moment, such as a subscription renewal, an installment or a delayed charge. Customer-initiated transactions are the opposite: the customer is actively there, entering details or confirming a purchase. Card networks and issuers treat the two very differently, and merchants that label them wrongly see more declines, more disputes and, in some regions, failed authentication. This guide explains the difference and how to set up card-on-file payments correctly.
Getting merchant-initiated vs customer-initiated transactions right affects approval rates, dispute outcomes and compliance with card network rules, so it is worth understanding before you build or change a recurring billing flow.
Merchant-initiated vs customer-initiated transactions: the core difference
A customer-initiated transaction (CIT) happens when the cardholder participates: they click pay at checkout, use a saved card with a confirmation, or approve a payment in an app. A merchant-initiated transaction (MIT) happens later under an agreement the customer made earlier, with no action from the customer in that moment. The first payment that saves the card and creates the agreement is a CIT. The later charges that rely on it are MITs.
Common types of merchant-initiated transactions
- Recurring: fixed or variable charges on a regular schedule, such as memberships and subscriptions.
- Installment: a purchase split into agreed payments over time.
- Unscheduled card-on-file: charges that happen when something triggers them, such as an account balance falling below a set level.
- Delayed or follow-up charges: additional amounts after the original purchase, such as a no-show fee or a post-stay charge, when the customer agreed to them.
- Reauthorization and resubmission: a new attempt after an earlier one expired or was declined, in situations the networks allow.
Why the merchant-initiated vs customer-initiated transactions labels matter
Issuers use the transaction indicators to decide how to treat a payment. A correctly labeled renewal tells the issuer that the customer already agreed and is not present to authenticate, which supports approval. The same charge sent as an ordinary online purchase can look suspicious or trigger an authentication request that nobody is there to answer. In regions with strong customer authentication rules, such as Europe, merchant-initiated payments generally fall outside the authentication requirement after the first transaction, but only if they are correctly identified and linked to the original agreement.
How to set up card-on-file payments correctly
- Get and record consent. At sign-up, show the amount or how it is calculated, how often you will charge, how to cancel, and keep a timestamped record of the customer’s agreement.
- Mark the first payment as the initial one. Send the indicator that says the credential is being stored for later use.
- Save the network transaction ID. The authorization response for that first payment includes an identifier from the card network. Store it with the customer record.
- Reference it on every later charge. Send the right MIT type, such as recurring or unscheduled, and the original transaction ID so the issuer can connect the payment to the agreement.
- Keep the amount and timing consistent with what the customer agreed to. Surprise amounts are the most common source of disputes.
Common mistakes with merchant-initiated vs customer-initiated transactions
Sending renewals as regular online purchases, forgetting to store the original transaction ID, treating a retry after a decline as a brand-new customer-initiated payment, and converting a free trial to a paid plan without a clear agreement all cause avoidable failures. Moving to a new processor can also break the link to the original ID, which is one more reason to plan card-on-file data carefully, as described in our guide to subscription retry logic and dunning.
How tokens fit in
Network tokens and account updater services help keep stored credentials valid when cards are replaced or expire, but they do not replace the need for correct MIT labeling. Think of them as complementary. For more on the token side, read about network tokenization versus PCI tokenization.
To recap, merchant-initiated vs customer-initiated transactions differ in who starts the payment and whether the cardholder is present to authenticate. Flag each payment correctly, keep proof of the original agreement, and review how issuers treat each type. A clear model of merchant-initiated vs customer-initiated transactions makes your billing logic easier to audit.
Merchant-initiated transactions: Key Takeaways
- The first payment that saves a card is customer-initiated, and later agreed charges are merchant-initiated.
- Correct labels help approval rates and keep merchant-initiated payments outside authentication requirements.
- Store the network transaction ID from the first payment and reference it on each later charge.
- Record clear consent and keep amounts and timing in line with it.
Frequently Asked Questions
What is a merchant-initiated transaction?
A merchant-initiated transaction is a payment the merchant starts under an earlier agreement with the customer, without the customer taking part at that moment. Examples include subscription renewals, installments and agreed delayed charges.
What is a customer-initiated transaction?
A customer-initiated transaction is one where the cardholder actively takes part, such as paying at checkout. The first payment that saves a card for later use is customer-initiated.
Why do MIT and CIT labels matter?
Issuers use these indicators to decide how to treat a payment. Correct labels support approval and, in regions with strong customer authentication rules, help merchant-initiated payments avoid authentication requests nobody is present to answer.
What is a network transaction ID used for?
It is an identifier from the card network returned on the first stored-credential payment. Sending it with later merchant-initiated charges links them to the original customer agreement.
Related Reading
- Subscription Payment Retry Logic and Dunning Management
- Network Tokenization vs PCI Tokenization
- Transaction Labeling and Descriptor Optimization
- Payment Decline Codes Explained
- ACH vs Card Payments for Rent and Recurring Billing: Cost, Returns and Risk
- Payment Processor Migration: A Product Manager’s Cutover Checklist
- Payment Processing Costs: Where They Hide and How to Reduce Them
Free Payment Performance Audit
Losing revenue to declined payments?
I help online merchants recover revenue lost to declines, false fraud flags and failed renewals. Tell me a little about your payment setup and I will send back the three biggest fixes I would make across authorization rate, retry logic, tokenization and routing. No cost, no obligation.
Request a free audit →Free download
Decline Code Cheat Sheet for Merchants
The 15 most common card decline codes on one page: what each one means, whether to retry, and how to fix it.
No spam. Unsubscribe anytime. See the privacy policy.