Monthly Phone Subscription.
Monthly billing for mobile and landline phone services.
- MCC
- 4815
- Category
- Utility Services
- Cardflo support
- Yes
What MCC 4815 covers
Merchant Category Code 4815 is the ISO 18245 identifier used by the card networks for monthly phone subscription. Acquirers, issuers and regulators use this code to set interchange, scheme fees, fraud rules and reporting categories for every transaction your business processes.
Monthly billing for mobile and landline phone services. Choosing the right MCC is critical: an incorrect code can lead to higher interchange, surcharges, or, in regulated categories, declined transactions and account holds.
This MCC is highly specific, used exclusively for monthly billing by phone services, primarily mobile network operators (MNOs) and fixed-line telecom providers offering subscription plans. Transactions are typically recurring, predictable, and represent standard monthly service fees.
Ticket sizes are generally consistent for a given customer, reflecting their chosen plan.
Chargebacks are often driven by 'services not rendered' (post-cancellation billing), 'not as described' (unexpected plan changes, erroneous charges), or 'unauthorised' usage, particularly when SIM cards are stolen and used for high-value premium rate services.
Managing customer lifecycle (onboarding, upgrades, cancellations) with clear communication is key to preventing disputes.
Adherence to scheme rules for recurring transactions and merchant-initiated transactions (MITs) is paramount. Cardflo's capabilities for managing subscriptions, including dunning management and account updater services (like VAU/ABU), are critical for maintaining high approval rates and reducing involuntary churn.
Our secure tokenisation ensures compliance whilst managing recurring payment streams.
For monthly phone subscriptions, maintaining low chargeback rates hinges on impeccable customer service and transparent billing. Given the recurring nature, ensure robust 3DS2 implementation at initial subscription sign-up, as this shifts liability and reduces fraud exposure.
Your acquirer partners will value clear, auditable records of service activation and ongoing customer consent for recurring debits. With predictable ticket sizes, focus on optimising authorisation rates for renewals.
Reserves are generally not expected unless your chargeback ratios escalate significantly, indicating potential operational issues.
Acquirer and acquirer assessment stance.
Low-to-medium risk standard board. While recurring billing inherently carries some risk of 'friendly fraud' and cancellation disputes, the regulated nature of many telecom providers and stable customer base typically keeps risk manageable.
Reserves are uncommon.
Dispute and chargeback profile.
The primary dispute reason codes for this MCC are "13.1 / 4853 (services not as described)" and "10.4 / 4837 (fraudulent transaction)". 'Services not as described' often occurs due to unexpected billing post-cancellation, plan changes without clear consent, or service quality complaints.
Evidence to combat this includes service agreements, usage logs, call records, and documented communication with the customer.
'Fraudulent transaction' typically arises from unauthorised SIM card usage or account takeover; compelling evidence includes KYC documents, IP/device data at sign-up, and proof of usage patterns aligning with the legitimate cardholder.
See also: chargeback management · payment response codes · Compelling Evidence 3.0.
Book a scoping call to see how Cardflo would set you up.
How Cardflo handles MCC 4815
- Placement with acquirers that actively board MCC 4815 businesses in your region.
- Recurring-billing infrastructure designed for utility and metered-service bill runs.
- Surcharge-rule support that meets local utility-regulator requirements.
- Dunning and decline recovery flows tuned to long-tenure subscriber bases.
- Settlement and reconciliation aligned to monthly utility billing cycles.
- Dedicated onboarding manager familiar with regulated utility processing.
Payment methods typically enabled.
Onboarding checklist.
What acquirers typically ask to see when boarding MCC 4815. Cardflo collects this once and reuses it across every acquirer we route you through.
- Business registration and beneficial-owner documentation (KYB, UBO).
- Regulator licence or equivalent authority to bill for the metered service.
- Recurring-billing policy, including advance notice of upcoming charges and cancellation flow.
- Six months of processing statements or ledger extract demonstrating billing cadence.
- Cardholder-consent workflow evidence for stored credentials.
- Chargeback ratio and dispute history covering the last six months, including any Visa or Mastercard monitoring-programme status.
See also: Know Your Customer (KYC) · high-risk merchant · smart routing.
Talk to an acquiring specialist about your MID setup.
Common questions
What information should be included in a recurring billing agreement for phone subscriptions?
A recurring billing agreement for phone subscriptions must clearly state the billing frequency, amount, and the duration of the agreement. It should also include a clear cancellation policy, instructions on how to cancel, and contact information for customer service.
Notifying customers of upcoming charges and any changes to the subscription amount or terms is also a common scheme requirement.
How do account updater services (VAU/ABU) specifically benefit merchants in MCC 4815?
Account updater services such as Visa Account Updater (VAU) and Mastercard Automatic Billing Updater (ABU) are highly beneficial for MCC 4815 merchants. They automatically provide updated card numbers and expiry dates when a customer's card is reissued, preventing declines due to expired or reissued cards.
This significantly reduces passive churn and the need for manual customer contact, ensuring continuous service and revenue for monthly subscriptions.
Can 3D Secure be used for monthly phone subscription payments?
Typically, 3D Secure is applied only for the initial setup of a recurring phone subscription or when a card is updated manually.
Subsequent recurring payments are usually processed as merchant-initiated transactions (MITs) based on the initial explicit customer consent, and thus do not require real-time 3D Secure authentication. This reduces friction for the cardholder while maintaining security for the subscription term.
What strategy can minimise disputes when a customer claims they were billed after cancelling their phone subscription?
To minimise disputes regarding post-cancellation billing, implement a clear and easily accessible cancellation process, ideally with immediate confirmation of cancellation date and final billing cycle provided to the customer. Ensure your billing system is updated instantly upon cancellation to prevent erroneous charges.
When a dispute arises, provide evidence of the cancellation request, the final bill sent, and proof that no services were rendered post-cancellation date.
Showing clear communication logs confirming understanding of the cancellation terms by the customer will strengthen your defence against 'services not rendered' type chargebacks.
How should providers handle chargebacks where a customer claims a premium rate service charge on their monthly bill was unauthorised?
When a customer disputes premium rate service charges as unauthorised, gather all available evidence demonstrating the legitimacy of the charge. This includes call logs or SMS records showing access to the premium service, along with the timestamp and duration.
If the service required opt-in, provide records of customer consent. For device-based access, IP addresses and device identifiers can be useful.
It is also important to show that your systems have robust controls to prevent unauthorised access to premium services and that usage is clearly itemised on bills, giving customers visibility into these charges.
Related features.
Related guides.
Ready to improve your payments setup?
Tell us about your business. We'll match you with the right acquiring partners and the right route, typically inside a week.