B2B Credit Card Authorization Forms for Wholesale Accounts

On this page 8 sections

1. Why Wholesale Accounts Need a Written Card Authorization
2. Fields Every B2B Credit Card Authorization Form Should Include
3. One-Time vs. Ongoing Authorization for Repeat Orders
4. Who at the Buyer's Company Can Legally Authorize Charges
5. Storing Forms and Card Data Without Breaking PCI Rules
6. Using the Form as Evidence in a Business Card Dispute
7. Replacing Paper Forms With Tokenized Card-on-File Links
8. Next Steps for Your Wholesale Accounts

Key takeaways

• A strong B2B credit card authorization form ties the charge to a named cardholder, a defined scope of orders, and documents your buyer's AP team will recognize months later.
• Ongoing authorizations should spell out which invoices you'll charge, when you'll charge them, how the buyer is notified, and how to revoke consent.
• Keep the signed authorization, but don't keep the full card number or security code on paper, in email, or in spreadsheets. Tokenize the card in your gateway instead.
• A signed form strengthens a dispute response but doesn't guarantee a win. Pair it with POs, invoices, proof of delivery, and charge notifications.

A B2B credit card authorization form is the document a distributor relies on when a buyer's accounts payable department calls months after a charge and says, "We never approved this." This guide shows what the form needs: which fields to include, who at the buyer's company should sign, and how to store forms and card data without creating PCI DSS problems. It also covers how to use the form as dispute evidence and when to replace paper with tokenized card-on-file links.

Why Wholesale Accounts Need a Written Card Authorization

Retail card disputes usually involve one shopper and one purchase. Wholesale disputes are messier. Your buyer might place weekly orders through a purchasing manager. The card might belong to the company's controller. Statements are then reconciled by an AP clerk who has never heard of your company. If the person who gave you the card leaves, nobody at the buyer's office may remember agreeing to anything.

Several wholesale patterns make this worse:

• Keyed transactions. Most distributor charges are entered by hand in a virtual terminal or ERP. That means no chip read, no PIN, and more liability on you if the charge is disputed.
• Split and partial shipments. Backorders mean one PO can produce several charges on different dates, and each one can look unfamiliar on a statement.
• Amounts that don't match the PO. Freight, fuel surcharges, substitutions, and restocking fees can make a charge differ from the number the buyer expected.
• Long gaps. AP teams often reconcile corporate card statements in batches. A disputed charge may surface well after the order shipped.

A written authorization won't stop every dispute. It does give you a clear record of who agreed, to what, and on what terms. That record is what you need when an issuer asks you to prove the charge was authorized.

Fields Every B2B Credit Card Authorization Form Should Include

Treat the form as a contract summary, not just a place to write down a card number. The fields below cover the questions a buyer's AP team or card issuer will ask.

Buyer and Account Details

• Legal business name and any DBA
• Your internal customer or account number
• Billing address and the ship-to locations covered by this card (important for multi-branch buyers)
• AP contact name, email, and phone for receipts and questions

Cardholder and Signer Details

• Name exactly as it appears on the card
• Card type (corporate card, purchasing card, or a business card in the owner's name)
• Signer's name, title, and a statement that they have authority to approve charges on this card
• Cardholder signature, if the cardholder is different from the signer

Authorization Scope

• One-time or ongoing authorization
• Which charges are covered: specific POs, all invoices on the account, or deposits only
• When charges occur: at order, at shipment, or on the invoice due date
• Whether freight, taxes, and fees are included
• Any per-transaction or monthly limit the buyer wants (optional but useful)

Terms and Signatures

• How receipts or invoices will be sent with each charge
• How to revoke or update the authorization, and how much notice you need
• Your company name as it will appear on the card statement
• Your refund and return policy, or a reference to your terms of sale
• Signature, printed name, and date

A Keyed Card Authorization Template (Illustrative)

Here is a simple layout many distributors adapt. Have an attorney review the final wording.

Putting card details on a separate, detachable section is the key design choice. You keep the signed authorization pages. The card data gets entered into your gateway once and then destroyed.

One-Time vs. Ongoing Authorization for Repeat Orders

Most wholesale accounts order repeatedly, so a recurring card authorization for B2B buyers is usually the better fit. Ongoing authorization only holds up if the scope is clear.

For ongoing authorizations, three habits reduce disputes:

1. Notify on every charge. Email an itemized receipt tied to the PO and invoice number to the AP contact on file.
2. Charge when you said you would. If the form says "on shipment," don't run the card at order entry.
3. Refresh when people change. When the buyer's signer or cardholder leaves, get a new form.

Card networks have rules for storing credentials and running merchant-initiated charges, including how the first transaction is flagged and what consent you must capture. Your gateway typically handles the technical flagging. Confirm with your processor that your setup handles stored-credential transactions correctly. When cards expire, a card account updater can keep stored cards current, but the authorization terms still need to cover the replacement card.

Who at the Buyer's Company Can Legally Authorize Charges

This is where many wholesale forms fall short. A purchasing manager can approve an order but may have no authority over the company card. A disputed charge often comes down to whether the person who signed had the right to approve it.

Common situations:

• Owner's business card. The owner is usually the cardholder and the decision-maker. One signature typically covers both roles.
• Corporate card issued to an employee. The employee is the cardholder. Company policy may limit what they can approve, so ask them to confirm they're permitted to authorize recurring vendor charges.
• Purchasing card (P-card). P-cards often carry spending limits and category restrictions set by the buyer's finance team. Get the cardholder's signature and ask about per-transaction limits up front.
• AP clerk providing a card. Ask for the cardholder's signature or a written approval from an officer. An AP clerk relaying a card number is not the cardholder.

A practical approach is to require the cardholder's signature on every form. When the signer isn't the cardholder, add a line for an officer or controller to confirm authority. Questions about agency and authority are legal questions, so treat this as general information and confirm your form language with a qualified attorney.

If you're onboarding new accounts, align the authorization with your credit process. The same signer-verification steps in vetting buyers before offering net 30 terms apply here. For buyers claiming a tax exemption, see our guide to collecting and verifying resale certificates. If your buyers include agencies, see our guide to accepting government purchase cards.

Storing Forms and Card Data Without Breaking PCI Rules

A wholesale card on file form turns into a liability if the full card number sits in a filing cabinet, an inbox, or a shared drive. PCI DSS applies to any business that stores, processes, or transmits card data. Paper and email count.

What to Do

• Tokenize immediately. Enter the card into your gateway's customer vault or your ERP's payment integration, which stores a token in place of the card number.
• Keep the signed authorization, not the card number. After tokenizing, destroy the card details section and keep the signed pages with only the card brand and last four digits.
• Restrict access. Only the people who process payments should be able to see stored payment profiles.
• Shred, don't recycle. Use cross-cut shredding or a secure destruction service for any paper with card data.

What to Avoid

• Keeping the card security code (CVV) after the transaction is authorized. Security standards treat it as data you should not retain, so confirm the specifics with your processor.
• Accepting forms by regular email or fax-to-email with full card numbers visible
• Storing card numbers in spreadsheets, CRM notes, or order comments
• Photographing forms on personal phones

Your processor can tell you which PCI self-assessment questionnaire fits your setup. The less card data you hold, the simpler that assessment usually is.

Using the Form as Evidence in a Business Card Dispute

When a buyer's AP team disputes a charge, your response is only as strong as your file. The signed form proves consent. The other documents prove the charge matched what was agreed and that the goods arrived.

Build an evidence package that includes:

1. The signed authorization showing the scope, signer, title, and date
2. The purchase order from the buyer, with the PO number matched to the charge
3. The invoice showing line items, freight, and tax that add up to the charged amount
4. Proof of delivery, such as a signed bill of lading, carrier tracking showing delivery to the ship-to address on the form, or a will-call pickup signature
5. The charge notification you emailed to the AP contact
6. Prior undisputed charges on the same card under the same authorization, if any
7. Correspondence with the buyer about the order, substitutions, or backorders

An illustrative example: a distributor ships a partial order and charges the card on shipment, as the form specifies. Months later, the buyer's AP team disputes the charge as unrecognized. The distributor responds with the signed form, the PO, the invoice for the shipped quantity, the carrier's delivery confirmation, and the receipt email sent the day of shipment. That package directly addresses each part of the claim.

Be realistic about the limits. The card issuer decides the outcome, and keyed transactions generally give merchants less protection than chip transactions. A clear statement descriptor also matters. If your legal name differs from the name buyers know, ask your processor whether your descriptor can be updated. Dispute windows and evidence requirements vary by card network and reason code, so confirm current requirements with your processor. For more on how disputes work on corporate and business cards, see our guide to chargeback rights and B2B dispute rules for business cards.

For disputes involving canceled standing orders, many of the tactics in how subscription sellers win cancelled recurring chargebacks translate directly to wholesale.

Replacing Paper Forms With Tokenized Card-on-File Links

Paper forms work, but they create handling risk at every step. Someone receives the form, someone keys the card, and someone has to remember to shred it. A digital credit card authorization form for business customers removes most of that.

The typical flow:

1. You send the buyer a secure link tied to their account.
2. The cardholder enters card details directly into the gateway's hosted page. Your staff never see the full number.
3. The buyer reviews your authorization terms and accepts them with a checkbox and typed name. The system records the date and time.
4. The gateway stores a token. Your team sees only the brand and last four digits.
5. Future invoices are charged against the token, and receipts go out automatically.

This approach also creates a cleaner dispute record, because the consent capture is time-stamped and tied to the stored card. Many distributors combine it with B2B customer payment portals that let buyers pay invoices online, so buyers who prefer to pay each invoice manually can do so. If your drivers take payment on delivery, see our guide to collecting payment from route sales and DSD delivery drivers.

On the tools side, MannyPay offers virtual terminals for keyed card payments and payment gateways such as Authorize.net and NMI, along with a QuickBooks integration. Gateway features like customer vaults and hosted card-capture pages vary, so confirm what's available for your setup. If you run a larger ERP, see adding card and ACH to NetSuite, Acumatica, or QuickBooks. For a refresher on keyed payments, read what a virtual terminal is and how it works.

Keyed and corporate-card transactions also affect what you pay. What wholesale distributors should pay in card processing fees explains the factors involved. For big B2B card orders, see how large ticket interchange can lower your rates. If you're still setting up processing, see getting a wholesale merchant account approved with big tickets and low order counts. To weigh card fees against early payment terms, see comparing 2/10 net 30 discounts with card fees. If buyers pay with AP virtual cards, see whether to accept, surcharge, or push ACH for virtual card payments.

Next Steps for Your Wholesale Accounts

Start with an audit. Pull your current authorization forms and check them against the field list above. Look for missing signer titles, vague scope language, and any stored card numbers that should have been tokenized and destroyed. Then update the template, have it reviewed by an attorney, and re-paper your highest-volume accounts first.

If you want help setting up keyed or tokenized card-on-file payments for wholesale buyers, request a free quote from MannyPay. A specialist will respond within one business day to talk through your terminal, gateway, and ERP options.

ME

About the author

MannyPay Editorial Team

Beyond the Swipe's editorial desk researches the publication's guides and news and cites its sources in every article. Articles reviewed by a named MannyPay editor carry that editor's byline.

This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.