Public Warehousing & Storage.
Self-storage, farm-product and refrigerated warehousing.
- MCC
- 4225
- Category
- Transportation Services
- Cardflo support
- Yes
What MCC 4225 covers
Merchant Category Code 4225 is the ISO 18245 identifier used by the card networks for public warehousing & storage. Acquirers, issuers and regulators use this code to set interchange, scheme fees, fraud rules and reporting categories for every transaction your business processes.
Self-storage, farm-product and refrigerated warehousing. Choosing the right MCC is critical: an incorrect code can lead to higher interchange, surcharges, or, in regulated categories, declined transactions and account holds.
MCC 4225 covers public warehousing and storage facilities, including self-storage units, farm product warehousing, and refrigerated storage. Merchants range from small, independently owned self-storage sites to large national warehousing chains.
Ticket sizes vary, from monthly self-storage fees (GBP 20-500) to substantial commercial warehousing contracts (GBP 500-10,000+). Transaction frequency is often recurring, based on monthly billing cycles.
Chargeback rates are typically low. Common dispute reasons might relate to billing errors, unfulfilled access, or damage claims, though these are rarer.
Most transactions are card-not-present, facilitating recurring payments. Robust contract management and clear access/service terms are critical.
Schemes generally classify this MCC as low-risk. Cardflo's recurring billing solutions and secure Customer Vault for tokenised card data are ideal for managing the subscription-like payments common in this sector, ensuring high approval rates and secure data handling.
Public warehousing and storage providers should prioritise acceptance solutions that facilitate recurring billing and secure CNP transactions. Given the common monthly fee structure, tokenisation is essential for managing subscriptions and ensuring seamless renewals through Account Updater services.
Implement comprehensive KYC/KYB procedures during onboarding, especially for longer-term or commercial contracts, to mitigate fraud. Multi-acquirer routing can provide resilience and cost optimisation across varying transaction volumes.
Reserve expectations are generally low, reflecting the stable, recurring revenue model, but ensure clear contracts and access policies are upheld to prevent disputes.
Acquirer and acquirer assessment stance.
Low-risk standard board. Stable B2B/B2C industry with predictable recurring revenues.
Minimal fraud concerns.
Dispute and chargeback profile.
The most likely chargeback reason codes for public warehousing are 13.1 / 4853 (services not as described) and 13.6 / 4834 (point-of-interaction error).
Services not as described might relate to issues with facility access, advertised features, or climate control failures, while point-of-interaction usually refers to billing disputes or incorrect recurring charges.
To counter these, provide robust service contracts, access logs, photographic evidence of facility condition, and detailed billing statements. For billing errors, present clear sign-up terms, cancellation policies, and proof of cardholder consent for recurring payments.
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 4225
- Placement with acquirers that actively board MCC 4225 businesses in your region.
- Fleet, fuel-card and dynamic-pricing transaction flows handled natively.
- Multi-acquirer routing that survives outages during peak travel windows.
- Tokenised storage of payer credentials for repeat journeys and fleet drivers.
- Surcharge rules and pass-through fees configured per scheme and region.
- Dedicated onboarding manager experienced with transport and mobility merchants.
Payment methods typically enabled.
Onboarding checklist.
What acquirers typically ask to see when boarding MCC 4225. Cardflo collects this once and reuses it across every acquirer we route you through.
- Business registration and beneficial-owner documentation (KYB, UBO).
- Operator licence, PSV/HGV credentials or equivalent regulator reference.
- Fleet insurance and passenger liability certificates.
- Refund, delay and cancellation policy aligned with local passenger-rights rules.
- Six months of processing statements demonstrating average ticket size and daily volume.
- Six months of processing statements or bank statements demonstrating trading pattern.
See also: Know Your Customer (KYC) · high-risk merchant · smart routing.
Talk to an acquiring specialist about your MID setup.
Common questions
What are the best practices for managing recurring payments in the self-storage industry?
Utilising a secure tokenisation service and a robust recurring billing platform is essential. This allows for automated monthly payments, reduces manual errors, and improves customer retention.
Clear communication about billing dates and any changes to fees helps prevent disputes. Cardflo's robust recurring billing engine supports various schedules and payment methods.
How can storage facilities minimise chargebacks related to 'service not as described' or billing errors?
Having very clear contractual terms, providing detailed invoices for each billing cycle, and documenting all customer interactions (e. g. , in CRM systems) are key. Ensuring customers understand their access rights, insurance coverage, and notice periods helps manage expectations.
Prompt customer service to resolve any billing queries before they escalate to a chargeback is also vital.
Are there specific PCI DSS considerations for remote or unmanned storage facilities?
Even without direct staff handling cards, if an unmanned facility uses online booking or automated kiosks for payments, PCI DSS compliance is still required. Using a PCI-compliant payment gateway that handles card data off-site reduces the merchant's scope.
For physical kiosks, ensuring secure network connections and using P2PE-certified devices is best practice.
What features should a payment gateway offer to efficiently manage recurring monthly billing for self-storage units?
A payment gateway for self-storage operations should offer robust recurring billing capabilities, including tokenisation to securely store card details and a sophisticated subscription management module.
This module should support flexible billing cycles, automated retries for failed payments, and integrated Account Updater services to prevent declines from expired or reissued cards. Webhooks and APIs for real-time integration with property management systems are crucial for updating storage statuses after successful payments.
Additionally, the gateway should facilitate easy reconciliation and provide clear reporting on subscription health and churn rates.
How can public warehousing facilities best prevent and defend chargebacks related to perceived service failures, such as unfulfilled access or facility issues?
To prevent and defend against chargebacks relating to service failures, warehousing facilities must maintain meticulous operational records. This includes detailed entry and exit logs for each unit, CCTV footage of the premises, and records of maintenance schedules and climate control system performance.
For any issues reported by a client, document all communication, resolution steps, and timestamps. Clear, concise service agreements outlining access hours, responsibilities, and facility conditions, acknowledged by the customer, are paramount.
When disputing, present these operational records alongside the signed contract and any relevant communications to demonstrate service provision.
Other MCCs in Transportation Services
Related industries.
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.