Key takeaways
- Card acceptance is the wrong default for four and five figure ag invoices; ACH costs far less and settles in 1-3 business days.
- Seasonal revenue confuses underwriters, so bring two or three years of history that shows the pattern is normal for your crop.
- Level 2 and Level 3 data can lower interchange on commercial card payments when you do take them.
Central Valley agriculture payment processing has a shape you do not see in most industries: enormous invoices, long payment terms, revenue that arrives in a few concentrated months, and buyers who still think a check in the mail is a normal way to settle a fifty thousand dollar load. From the almond and pistachio operations around Madera and Kern, to the dairy supply chain in Tulare, to the packing and cold storage businesses along Highway 99, the payment problems rhyme even when the crops do not.
Cards are the wrong rail for most of your volume
Interchange on a card transaction is roughly proportional to the ticket. On a two hundred dollar retail sale that is a rounding error. On a forty thousand dollar invoice for inputs or a truckload of product, it is real money, often more than the margin on the line item itself. Surcharging is regulated and California's fee-display rules complicate it further, so the cleaner answer is to move large B2B settlement to ACH, which settles in 1-3 business days at a flat or near-flat cost regardless of size.
Keep card acceptance for what it is good at: small equipment parts, retail farm stands, agritourism, u-pick weekends, feed store counters and anything where the buyer is a consumer and speed matters more than cost.
Get the invoice out of the mail
Most late payments in ag are not disputes, they are friction. The invoice went to a general email, sat in a folder, and nobody chased it until the grower needed the cash. Sending terms through invoicing and payment links with a pay-now button that defaults to bank debit does more for your days sales outstanding than any collections script. Add automatic reminders at seven, fourteen and thirty days past due and let the system do the awkward part.
If you push receivables into QuickBooks, note that Flux syncs one way: Flux pushes into QuickBooks. Your bookkeeper still owns the ledger; the payments system just stops making them retype things.
Seasonality and how underwriters read it
An underwriter looking at a stone fruit packer sees six months of heavy volume and six months of almost nothing, and the automated risk model flags it. You fix that with history and explanation, not argument. Bring:
- Two or three years of statements so the seasonal curve is visibly repeating
- A short written explanation of your harvest and billing calendar
- Buyer concentration information, since a few large buyers is normal in ag but reads as risk without context
- Any contracts or marketing agreements that support projected volume
The same conversation matters mid-season. If you are about to run five times your normal monthly volume because harvest arrived, tell your processor first. Unannounced volume spikes trigger holds, and a hold during harvest is genuinely damaging.
When you do take commercial cards
Some buyers insist on paying by corporate or purchasing card, often to capture rebates. If you accept, capture Level 2 and Level 3 data: tax amount, customer code, invoice number, line item detail, unit of measure, freight. Passing that data can qualify the transaction for lower commercial interchange rates. It requires a gateway that supports the fields and a workflow that actually populates them, but on large tickets the savings are meaningful. Ask your provider directly whether your setup submits Level 3, because many merchants assume they do and do not.
Use pass-through pricing so you can verify it. If your statement bundles everything into a single blended rate, you have no way to confirm the interchange qualification you are paying a gateway to achieve.
Fraud and account takeover in ag
Ag has a specific fraud problem: business email compromise. Someone spoofs a supplier, sends updated bank details, and a payables clerk in Fresno wires or ACHes payment to the wrong account. This is not a card fraud problem, but it is a payments problem and it costs more than chargebacks ever will.
- Never change a vendor's bank details based on an email alone. Call a known number.
- Require dual approval on any payment above a set threshold.
- Use payment links you generate rather than bank details typed into email bodies.
On the card side, if you sell direct to consumers online, standard fraud screening with address verification handles most of what you will see.
Cross-border and settlement speed
Valley exporters dealing with buyers abroad face slow, expensive correspondent banking. Some now settle a portion of receivables in stablecoins on Solana or the XRP Ledger, which arrive instantly to the merchant wallet rather than waiting days on wires. It is not a fit for everyone, and California's Digital Financial Assets Law governs digital-asset business activity in the state, so confirm your position with counsel before building it into your process.
The practical checklist
- Move invoices over roughly one thousand dollars to bank debit by default
- Keep cards for consumer and small-ticket sales
- Submit Level 3 data on commercial cards you cannot avoid
- Warn your processor before harvest volume hits
- Verify vendor banking changes by phone, always
Agriculture does not need exotic payment technology. It needs cost discipline on big tickets, invoices that are easy to pay, and a processor who does not panic when a quiet spring turns into a very loud August. Other Valley operators face parallel issues; the discussion in Payment Processing for E-commerce Brands in the Central Valley covers the consumer-facing side in more depth.
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