Key takeaways
- B2B card acceptance can qualify for lower interchange with Level 2 and Level 3 data, so ask whether your processor supports it.
- ACH at 1-3 business days is usually cheaper than cards for large recurring invoices.
- Match your MCC and approved ticket size to what you actually sell, or expect held funds later.
If you are comparing merchant services in Chino, you are probably not running a boutique. This is a warehouse, distribution, light manufacturing and agriculture town, from the logistics parks off the 60 and Euclid to the equipment dealers and feed suppliers that still serve the dairy preserve. That B2B tilt should change your processor checklist substantially, because most merchant services marketing is written for retail.
B2B interchange works differently, and most merchants leave money on the table
When a commercial or purchasing card is used, Visa and Mastercard offer lower interchange rates if the transaction carries enhanced data. Level 2 typically means tax amount and customer code. Level 3 adds line item detail: item descriptions, quantities, unit costs, freight and duty. On a $14,000 parts order, that difference is not academic.
Many processors technically support Level 2 and 3 but do not configure it, and most gateways will silently downgrade if the fields are missing. Ask directly: does my gateway pass Level 3 data, which fields are required, and can you show me a settled transaction that qualified? Then verify it on a statement. Pass-through pricing makes the check possible, because you can see the actual interchange category rather than a blended average.
Cards are not always the right rail
For recurring invoices to established customers, ACH at 1-3 business days usually beats card economics by a wide margin, since ACH pricing is typically a small flat fee rather than a percentage. On a $40,000 monthly supply contract, the difference funds a headcount.
The practical approach for most Chino B2B sellers is a mix: ACH for known accounts and large balances, cards for smaller or one-off orders where convenience is worth the cost, and invoices with embedded payment links so your AR team stops chasing checks. If you sell internationally, stablecoin settlement on Solana or the XRP Ledger is worth understanding as well, since it settles instantly to the merchant wallet, though it adds treasury and accounting work you need to plan for.
Get your MCC and ticket profile right at application
Your merchant category code drives interchange eligibility, risk review and sometimes whether issuers allow the transaction at all. Warehousing, wholesale distribution, equipment sales and agricultural supply are all distinct codes. Being coded as generic retail because it was easier at signup means wrong interchange and awkward questions later.
The same goes for ticket size. Underwriting approves you for an average and high ticket. Run a $60,000 order on an account approved at a $3,000 high ticket and expect a hold while someone reviews it, which is a terrible way to learn the rule during a customer's month-end.
- Tell underwriting your real high ticket, including the once-a-year outlier
- Disclose seasonal spikes tied to harvest or fiscal year-end buying
- Explain your delivery timeline honestly if you take deposits on custom fabrication
- Update your processor before a major new contract, not after the first invoice
Deposits, custom orders and reserves
If you take 50 percent down on a custom build or a large equipment order, an underwriter sees future delivery risk. That can mean a rolling reserve, a percentage of settlement held and released on a 90 to 180 day lag. It is negotiable at signup and much harder to unwind later, so raise it before you sign. Ask what performance would reduce it and get the answer in writing.
Security scope in an operation with shared systems
Warehouse and manufacturing environments tend to have shared terminals, dispatch computers and office PCs on the same flat network. That expands PCI scope fast. Two changes shrink it: use hosted fields so card entry happens in the processor's iframe rather than your page, and use tokenization so stored customer cards live as tokens in your ERP instead of real numbers. Never let AR staff keep card numbers in a spreadsheet or on paper order forms, which is still depressingly common in this sector.
Disputes look different in B2B
Commercial disputes are usually about delivery, quantity or quality, not fraud. Your defense is paperwork: signed BOLs, delivery photos, purchase order references on the transaction, and a statement descriptor your customer's accounting department recognizes. Ask how the processor handles representment and who compiles the evidence. Keep an eye on your ratio anyway, since the brand monitoring programs sit around 0.9 percent to 1 percent regardless of why the dispute happened.
How to run the comparison
Pull three months of statements, calculate your true effective rate as total fees divided by total volume, and ask each processor to quote against that same volume with markup itemized. Then weight the answer by the things a spreadsheet misses: Level 3 support that actually works, an underwriter who understood your business the first time, and support that answers when a month-end invoice batch fails.
For a Chino operation, those three usually matter more than a tenth of a point on the rate sheet.
Ready to get set up with Flux?
Cards, ACH, and stablecoins in one platform, with volume-based pricing. No setup fees or contracts.
Get Started