Merchant-Initiated vs. Customer-Initiated Transactions Explained
Learn when a charge is a merchant initiated transaction or customer initiated, and how correct stored-credential flags lift approvals and defend disputes.

Photo: Pixabay
On this page 8 sections
- CIT vs. MIT: How a Merchant-Initiated Transaction Differs
- The Stored Credential Framework in Plain English
- Types of MITs: Recurring, Installment, Unscheduled and Industry Charges
- A Worked Example: One Student, Five Charges
- Why the First Transaction ID Matters
- How Wrong Recurring Payment Indicators Cause Declines and Lost Disputes
- Getting Customer Consent the Networks Will Accept
- Questions to Ask Your Gateway About MIT Flagging
Key takeaways
- A charge you key in while the client approves it on the phone is customer-initiated, even if the card is already stored.
- Every MIT should carry the network transaction ID from the authenticated first charge. Cards migrated from another provider are where that link most often breaks.
- Check two labeling errors first: unscheduled charges sent as recurring, and renewals sent as ordinary e-commerce sales.
- Stored-credential rules come from Visa and Mastercard. Auto-renewal disclosure requirements come from state law, and in some cases federal law, and apply separately.
A customer-initiated transaction (CIT) is a charge the cardholder takes part in at that moment. They click "pay," tap a card, or read you the number over the phone. A merchant-initiated transaction (MIT) is a charge you run on a card you already have on file, with no customer involved, because they agreed in advance to let you. Visa and Mastercard expect every charge on a stored card to carry a flag saying which kind it is, and that flag affects whether the card issuer approves it.
Your gateway usually sets these flags in the background, so most merchants never look at them until something goes wrong. A mislabeled renewal can be declined as suspicious. And when a customer later claims they never agreed to a charge, a transaction history that contradicts your signed agreement makes the dispute harder to win. Both problems are fixable, and most of the fix comes down to knowing what correct flags look like and asking your gateway the right questions.
CIT vs. MIT: How a Merchant-Initiated Transaction Differs
The test is one question: was the cardholder actively involved in this specific payment? If yes, it's a CIT, even when the card is already saved. A gym member who buys a smoothie at the front desk with the card in their profile is making a CIT. So is an online shopper who checks out with a stored card, and so is a client who calls your office and approves a charge while you key it in.
If the cardholder wasn't involved, it's an MIT. Monthly dues pulled automatically on the first of the month are MITs. So is a minibar charge a hotel posts after checkout, and so is a bookkeeper billing this month's hours to the card on file under the engagement letter.
Keyed entry confuses a lot of offices. Typing a card number by hand only describes how the card got into the system. It doesn't decide the transaction type. A charge the client approves on the phone is customer-initiated. A charge you run on a stored card under a standing agreement, while the client is not on the line, is merchant-initiated. If your staff charge stored cards by phone, your virtual terminal for keyed and phone payments needs a way to mark which is which.
One-time sales where you don't keep the card fall outside these rules. The flags matter only when you store a card or use one you stored.
The Stored Credential Framework in Plain English
A stored credential is a card number, or a token that stands in for one, that you keep so you can charge it later. The stored credential framework is the set of card network rules covering three things: how you get permission to store the card, how you tell the issuer you're storing it, and how you label each later charge. These are network rules set by Visa and Mastercard. They are not federal law, and they are not one processor's pricing or policy. Both networks follow the same logic, though their technical field names differ.
Everything starts with the first charge, which is a CIT that announces you are storing the card. Run it with every check available: the card security code, address verification and, for online sales, 3-D Secure authentication if you use it. An approval on that transaction tells the issuer the card works and that the person agreeing to future charges had it in hand. If you aren't charging anything yet, as with a free trial, many gateways can run a zero-dollar account verification flagged as the initial storage. Confirm with your processor how yours handles that case.
From then on, each charge gets a label. It is either a CIT using a stored credential or an MIT, and an MIT also states which kind of MIT it is. Each MIT also points back to the first charge through a reference number the network returned when that charge was approved.
None of this replaces the cardholder's agreement, which you need before you store anything. Our guide on how to store a customer's card on file safely and legally covers the security side.
Types of MITs: Recurring, Installment, Unscheduled and Industry Charges
MITs come in two groups. One group covers charges the customer authorized in advance as a standing instruction. The other covers charges that follow from a purchase the customer already made.
Standing Instructions and the Unscheduled Card-on-File Transaction
Recurring charges run at fixed intervals with no set end date. The amount can be fixed or variable. Gym dues, software subscriptions and an accounting firm's monthly retainer all fit.
Installment charges split one purchase into a set number of payments on a schedule, such as a training camp paid in three parts.
An unscheduled card-on-file transaction has no fixed schedule. Something specific triggers it. A consulting firm charges the card when it invoices for hours worked. A prepaid account tops itself up when the balance runs low. A martial arts studio charges a belt-test fee when the student tests.
Recurring and installment flags are the recurring payment indicators. Unscheduled charges are the ones most often sent under those flags by mistake, because billing software tends to treat anything automated as "recurring."
Industry-Practice Charges: Incremental, Delayed and No-Show
Some MITs exist because certain businesses can't know the final amount when the customer starts. Hotels are the clearest case. An incremental authorization raises the hold during a stay, and a reauthorization renews it when the stay is extended. A delayed charge covers the minibar or damage found after checkout. A no-show charge covers a guaranteed reservation the guest never used.
A resubmission type also exists for retrying a declined charge on goods or services already delivered. Each of these is limited to certain merchant categories, so confirm which ones yours allows. A hotel payment processing setup should support them without workarounds.
A Worked Example: One Student, Five Charges
The scenario below is illustrative. A martial arts studio signs up a student online for a monthly membership. During signup the student agrees to monthly billing and agrees that belt-test fees will be charged to the card on file.
| Event | Who initiated it | Correct flag | Points back to |
|---|---|---|---|
| Online signup, first month charged | Customer | CIT, initial storage (security code checked, 3-D Secure if used) | Creates the original transaction ID |
| Monthly dues after that | Studio | MIT, recurring | Original ID |
| Belt-test fee charged after the test | Studio | MIT, unscheduled card on file | Original ID |
| Student buys gloves at the front desk with the saved card | Customer | CIT, using stored credential | Not required |
| Student calls to buy a seminar seat and approves it on the phone | Customer | CIT, using stored credential (phone order) | Not required |
Two of the four charges after signup are customer-initiated even though the card is stored. Suppose the studio's software labeled everything after signup as recurring. Then the belt-test fee, the gloves and the seminar seat would all carry the wrong flag. Gyms juggle this mix of dues, add-on fees and walk-up purchases every day. Our guide to gym membership billing that survives chargebacks covers the contract side.
Why the First Transaction ID Matters
When the initial CIT is approved, the network returns a transaction identifier. Your gateway should save it and send it with every MIT on that card. It tells the issuer that a charge made with no customer present traces back to a transaction where the cardholder was present and verified.
Without that link, an MIT looks like a stray card-not-present charge. It usually arrives without the card security code too, since that code isn't kept with a stored card. To an issuer's fraud model, that combination looks weak.
The link tends to break in predictable places. Processor and gateway migrations are the most common: tokens move to the new system, but the original IDs sometimes stay behind. Customer lists imported from a spreadsheet or an old system have no IDs at all. Long-tenured customers may have cards stored before your current setup existed. The networks have provisions for credentials stored without an original ID, but handling varies, so ask your processor what happens to those cards. Reissued and expired cards cause a separate problem, which account updater for saved cards addresses.
How Wrong Recurring Payment Indicators Cause Declines and Lost Disputes
Issuers build risk models around what each transaction type should look like. When the label doesn't match the transaction, you pay for it in a few specific ways.
Renewals sent as ordinary online sales. The issuer sees a customer-initiated, card-not-present charge with no security code and no device data from the shopper. It may decline the charge as likely fraud. It may also return a soft decline, meaning a decline that asks for extra steps such as customer authentication, which a customer who isn't there can't complete. That happens more often with cards issued outside the U.S.
Unscheduled charges sent as recurring. A "recurring" charge that lands on scattered dates with varying amounts doesn't match the pattern the issuer expects for that label.
Retrying declines the issuer said not to retry. Both networks restrict repeated attempts after certain decline responses and can charge fees for excessive reattempts. Ask your processor for the current limits. Our piece on smart retries for failed subscription payments covers retry timing.
You can estimate what bad flags cost you. Take the number of extra renewals that decline each month, multiply by your average charge, and multiply again by the share you never recover through retries or dunning. As an illustrative case with assumed numbers, a studio that loses ten extra renewals a month at $60 each and never recovers half of them is giving up $300 a month. Run the formula with your own decline reports. The total is the ceiling on what fixing your flags is worth.
Disputes follow similar logic. When a customer says "I canceled" or "I never agreed," your evidence is the agreement they accepted, the authenticated first charge, any notices you sent and your cancellation records. Correct flags and a consistent transaction ID make the charge history back up that account. If renewals go out labeled as ordinary e-commerce sales, your own data says the customer started payments they never made. Our guide to why subscription renewals get disputed goes deeper on evidence.
Getting Customer Consent the Networks Will Accept
Visa and Mastercard require a stored-credential agreement before you save a card. In language the customer actually sees, it should state:
- Which types of charges you'll make with the card
- The amount, or how it will be calculated
- When charges happen, or what triggers them
- How to cancel
- How you'll notify the customer of changes
Capture an affirmative action, such as a checkbox the customer ticks or a signature, store it with a timestamp, and send a confirmation. The networks add their own disclosure requirements for free trials and introductory pricing, so check those before you launch a trial offer.
Where the agreement lives depends on the business. Professional services firms can put card-on-file authorization in the engagement letter and say whether invoices will be charged automatically. Hotels belong in the reservation terms, which should spell out no-show and incidental charges. Gyms and studios should list dues and add-on fees in the membership contract, so a belt-test charge never surprises anyone.
State automatic renewal laws are a separate layer. They are law, not network rules, and they can require more disclosures and specific cancellation methods. See what subscription businesses must disclose under auto-renewal laws. This is general information. Have a qualified attorney review your terms.
Questions to Ask Your Gateway About MIT Flagging
- Does the recurring billing module set MIT recurring flags automatically, or do we configure them?
- Can we mark a charge as unscheduled card on file separately from recurring, including charges keyed through the virtual terminal?
- Do you store the network transaction ID from the first CIT and send it with every MIT, and where does it appear in a transaction record?
- If we migrate saved cards from another provider, do the original IDs come with them? If not, how are those cards flagged?
- Does the initial storage transaction run with the security code, address verification and 3-D Secure where available?
- How do decline reasons appear, and does the system stop retrying when the issuer says not to?
Start with a test you can run this week. Open a handful of recent renewals and one unscheduled charge in your gateway's transaction detail, and look for the stored-credential fields and the reference ID. If you can't find them, that's your first question for support. If you're comparing payment gateway options, MannyPay works with NMI, Authorize.net and Clover, and a specialist responds to free quote requests within one business day.
This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.


