Lesson 11 of 13
Transaction types.
Channel, initiator, and credential: how to label every card payment, with an interactive classifier.
By Nagesh Koritala 7 min read Last verified: November 2026
- Lesson 1: Improve the checkout
- Lesson 2: The checkout flow
- Lesson 3: Authorization
- Lesson 4: Payment states
- Lesson 5: Capture
- Lesson 6: Clearing and settlement
- Lesson 7: Cash capture
- Lesson 8: Returns and refunds
- Lesson 9: Disputes
- Lesson 10: Tokens and stored credentials
- Lesson 11: Transaction types (this lesson)
- Lesson 12: Complete reference
- Lesson 13: Payments compliance
Every card payment you send carries labels that tell the issuer what kind of payment it is. Get them right and approvals go up, fees go down, and disputes are easier to win. Get them wrong and good payments get declined.
The labels answer three separate questions. Teams get confused when they mix them up, so learn them one at a time.
Card present (tap, chip, swipe) · E-commerce (website) · In-app · MOTO (mail or phone order, keyed by staff).
CIT: the customer is taking part right now. MIT: the merchant charges a stored card without the customer, under an agreement.
Not stored (one-time) · Initial (storing it now, with consent) · Subsequent (using a card stored earlier).
The answers combine. A phone order can be a CIT. A CIT can use a stored card (one-click checkout). An MIT always uses a stored card, and always traces back to an initial CIT where the customer agreed.
Classify a real transaction
Pick a situation. The panel shows how it should be labeled, and what your system must send.
The complete list
Card brands share the same core framework but name and split some types differently. The brand column notes where they diverge.
| Type | Family | Amount | Timing | Example | Brand notes |
|---|---|---|---|---|---|
| Customer-initiated (CIT) | |||||
| One-time purchase | CIT, not stored | Known | Now | Guest checkout | The default. No stored-credential indicator. |
| Initial storage | CIT, initial | Known | Now | “Save this card” at checkout, or the first payment of a subscription | Flag it as the first use and say what future use it enables. Authenticate here (3-D Secure where it applies). Keep the network transaction ID it returns. |
| Purchase with a saved card | CIT, subsequent | Known | Now | One-click checkout | Still a CIT because the customer is present. Flag it as using a stored credential. |
| Setting up a series | CIT, initial | Varies | Now | Signing up for a plan | Mastercard asks you to say which kind of series: credential on file, standing order, subscription, or installment. |
| Merchant-initiated: standing instructions (agreed in advance) | |||||
| Recurring (scheduled) | MIT | Fixed or variable | Fixed schedule | Monthly membership, utility bill | Visa uses one “recurring” type. Mastercard splits it: subscription (fixed amount, fixed frequency) and standing order (variable amount, fixed frequency). |
| Installment | MIT | Known total, split | Fixed schedule, fixed count | Furniture paid in 4 parts | One purchase, a set number of payments. Not a loan from a third party; that would be BNPL. |
| Unscheduled card on file (UCOF) | MIT | Fixed or variable | No fixed schedule; at an agreed trigger | Auto top-up when balance is low, usage-based billing | Both brands. The trigger must be in the customer's agreement. |
| Merchant-initiated: industry practice (follow-ons to a purchase) | |||||
| Incremental | MIT | Adds to an existing auth | During the service | Hotel stay extended | A Visa industry-practice type. |
| Reauthorization | MIT | Original or remaining amount | After the first auth expired | Back-ordered item ships late | A Visa type. For split shipments Mastercard uses partial shipment. |
| Partial shipment | MIT | Remaining amount | When later items ship | Second box of a split order | A Mastercard type. |
| Delayed (related) charge | MIT | New, related amount | After the main purchase | Minibar after hotel checkout, car rental damage | Both brands; Mastercard calls it related or delayed charge. |
| Resubmission | MIT | Same amount | After a decline | Recovering a fare for a transit ride already taken, after an insufficient-funds decline | Both brands. Visa limits it to goods or services already delivered; Mastercard's M208 is broader. Check how your gateway wants retried subscription renewals flagged. |
| No-show | MIT | Agreed penalty | After a missed booking | Hotel or appointment no-show | Both brands. Only if the policy was disclosed and accepted. |
| Channels (combine with the above) | |||||
| Card present | Channel | Any | Tap, chip, swipe | Chip or device cryptogram; counterfeit liability rules apply. | |
| E-commerce | Channel | Any | Website checkout | ECI value shows the 3-D Secure result. | |
| In-app | Channel | Any | Mobile app, often with a wallet | Usually token and cryptogram. | |
| MOTO | Channel | Any | Phone or mail order keyed by staff | Card not present and no 3-D Secure, so no fraud liability shift. The fraud and dispute risk stays with you. | |
Scheduled vs unscheduled, in one line. If you can put the next charge on a calendar when the customer signs up, it is scheduled (recurring or installment). If the charge depends on an event, it is unscheduled card on file.
Field names differ by gateway: “initiator,” “stored credential type,” “subsequent auth reason,” “recurring flag.” Mastercard also assigns each category its own code (C101 to C104, M101 to M104, M205 to M208; the full list is in lesson 12). Visa recurring charges may never be more than a year apart. Map each row above to your gateway's exact values before you build.
Sources for this guide
Card network rules change. Time limits, fees, and authorization windows here reflect published rules and provider documentation as of late 2026; confirm details with your processor before you build against them.
Sources
- Visa authorization and clearing time frame changes, April 2024 (TD Bank summary)
- Checkout.com: Visa authorization processing time frames
- Stripe: Place a hold on a payment method
- Revolut: Clearing windows by card brand
- Moov: Card-not-present best practices
- Adyen: Dispute timeframes
- Cybersource: Stored credential framework (CIT, MIT, standing instructions)
- VGS: DPAN vs MPAN
- Stripe: Apple Pay merchant tokens
- Google Pay: Payment data cryptography (PAN_ONLY and CRYPTOGRAM_3DS)
- Checkout.com: Google Pay authentication methods and liability shift
- Solidgate: Why the Apple Pay card number differs from the card
- Spreedly: Payment Account Reference (PAR)
- Visa: Authorization and reversal processing best practices
- Visa: Authorization framework time frames (2024)
- Visa: Declined transaction resubmission rules
- Visa: Dispute management guidelines for merchants
- Visa: VAMP fact sheet
- Visa: Account Updater FAQ
- Mastercard: Chargeback Guide, Merchant Edition
- Mastercard AN 5524: CIT and MIT indicators (via AIB Merchant Services)
- Mastercard Gateway: Cardholder and merchant initiated payments
- Adyen: Mastercard Transaction Link Identifier
- American Express: US Disputes Reference Guide
- American Express: International Merchant Regulations
- Adyen: Adjust authorisation (validity by brand)
- Apple: Merchant tokens (MPANs)
- Apple: Payment token format reference
- Apple: Merchant Token Notification Services
- Google Pay: Merchant-initiated transactions
- Google Pay: Token lifecycle management
- Stripe: PaymentIntent lifecycle
- Stripe: Refund object
- Stripe: Dispute object
- Stripe: Subscription object
- Stripe: Decline codes
- PCI SSC: Future-dated requirements of PCI DSS v4.x
- Report URI: SAQ A changes in PCI DSS 4.0.1
- SecureTrust: PCI DSS SAQ types
- Chargeback Gurus: Regulation II and card-not-present debit
- Baymard Institute: Cart abandonment rate statistics (updated September 2025)
- Baymard Institute: The current state of checkout UX (2025)
- Baymard Institute: Checkout optimization and average form fields (2024)
- Baymard Institute: Inline form validation
- Baymard Institute: Adaptive validation error messages
- Adobe: 2025 US holiday shopping season
- US Department of Justice: Guidance on web accessibility and the ADA
- W3C: Web Content Accessibility Guidelines (WCAG) 2.2
- Apple: Human Interface Guidelines, accessibility
- Stripe: How to increase checkout conversion
- Stripe: The checkout process, reducing friction
Your progress stays on this device.
Next: Lesson 12
Complete reference.
Authorization types, validity windows, statuses, codes, declines, disputes, and monitoring, brand by brand.
Questions about payments? Email me. I read every note.