A wholesale portal should show each known account only the payment methods you allow for them, such as ACH, card, or pay-on-invoice. Week one on Parcel Build is that first working version: account-level gates at checkout or order pay, without a full routing marketplace. You own the code. Flat monthly. See custom software for wholesalers. If ACH vs card by account is the gap, start a free 30-day build.
Which payment-method gates belong in week one (and which processor projects can wait)?
Week one can cover an account-level list of methods the buyer may use at checkout or order pay. ACH only, card only, pay-on-invoice, or a mix you already allow. A buyer should not see a method you will reject. Multi-gateway smart routing, global alternate-method catalogs, and full risk scoring engines can wait until the gate path earns its keep.
Why one checkout for every buyer creates fee surprises, failed large-card charges, and AR workarounds
Every account sees the same pay options. A large order hits card and fails, or it posts and the fee surprises finance. Another account should have used ACH or invoice and instead picks card because that is what the portal offered. AR then works around the method after the order is already in.
The stall is a missing gate. You already know which methods an account may use. Checkout does not honor that list.
What week one can cover
An allowed-method list on the known account. Checkout or order pay that shows only those methods. A clear message when a method is not available. A path for finance to change the list when the account moves from card to ACH or invoice.
On Parcel Build, week one is a first working version of that path. Flat monthly. You own the code.
What stays out of month one
Defer multi-gateway smart routing products. Defer global alternate-method catalogs. Defer full risk scoring engines. Month one is account-level method gates at checkout or order pay for known accounts.
FAQ
Is gating ACH vs card the same as showing Net 30 on the account?
No. A terms label tells the buyer when they may pay. A method gate tells them which methods they may use: ACH, card, or invoice. They can live together later. Week one can prove the gate without cloning the terms-label path.
Does week one need every payment processor connected before the first account rules go live?
No. Week one can start with the methods you already take and the accounts that already need a gate. Connecting every processor can wait until the rule path is earning its place.
Next step
If ACH vs card payment methods by wholesale account is what feels hardest, start a free 30-day build. Name that gap on the form. We scope a free 30-day build on that problem: first working version in week one, flat monthly after if you want to continue.