Pay an Invoice with a Credit Card: Buyer and Seller Checklist
Pay an invoice with a credit card: buyer checkout steps, seller acceptance and surcharge rules, remittance matching, and when ACH or wire is the better rail.
Bottom line
To settle an invoice by card, open the seller's payment link, customer portal, or virtual terminal, then keep the authorization receipt with the invoice number. Sellers who accept cards must disclose any card surcharge where law and card-brand rules allow it, and must still match remittance to the invoice. US card networks and state rules limit when surcharges are allowed and how they are disclosed; treat surcharge % as a compliance review, not a silent fee. Terms context: net 30 example. Fee rules: credit card surcharge laws by state, processing fees. Follow-up: invoice follow-up email.
Is it right for you?
- Buyer: confirm the portal URL matches the seller's known domain
- Buyer: enter the exact invoice number in the remittance / reference field
- Buyer: save the card authorization email next to the PDF invoice
- Seller: enable card on the invoice or portal with clear fee/surcharge text
- Seller: verify surcharge legality for the customer's state and brand rules
- Seller: auto-apply or manually match the settlement to the open invoice
- Fail if the payment posts to unapplied cash with no invoice reference
Quick answer
“Pay invoice with credit card” covers two jobs: the buyer completing checkout without losing the invoice reference, and the seller posting the deposit to the right AR open item.
ACH and check remain cheaper for many B2B flows; cards win when the buyer needs rewards, float, or same-day payment. Price the acceptance cost into the deal or a disclosed surcharge where permitted.
Buyer steps (pass/fail)
| Step | Action | Pass | Fail |
|---|---|---|---|
| 1 | Open the seller's hosted invoice link or portal from a known email/domain | HTTPS + seller brand you recognize | Lookalike domain → call AP contact before paying |
| 2 | Confirm amount = invoice total (or approved partial) | Matches PDF | Extra “fees” not disclosed on invoice |
| 3 | Enter card; put invoice # in reference | Auth success + invoice # on receipt | Blank reference → expect unapplied cash delay |
| 4 | Archive receipt with the invoice PDF | Audit folder complete | Receipt only in email trash |
Seller acceptance and surcharge notes
Turn on card payments in your billing tool (Stripe, Melio, QuickBooks Payments, processor virtual terminal, etc.). Show the payment methods on the invoice PDF and in the reminder sequence.
Surcharging card payments is regulated: some U.S. states restrict or ban it, and card brand surcharge programs require registration, caps, and clear disclosure. Do not invent a silent “processing fee” on the checkout page without counsel/compliance review.
If you absorb fees, bake the cost into price. If you surcharge where allowed, show the cash/ACH price and the card price before authorization.
Net terms still matter: a card paid on day 45 of a Net 30 invoice is still late even if the processor settles next day. See the Net 30 worked-date examples elsewhere on this site.
Posting and remittance matching
Settlement batches often land as a bulk deposit. Without the invoice number, cash sits in Unapplied Cash and aging stays wrong.
Require invoice # on the portal form. For emailed “please charge my card” requests, write the number into the virtual-terminal reference field before authorizing.
Aging and collections after mis-posts: AR aging report, dunning process, payment reminder email.
When card is the wrong rail
Large B2B invoices often exceed card velocity limits or earn high interchange. Offer ACH for those amounts and keep card for smaller or urgent balances.
International cards can fail AVS/CVV or FX markup. State the accepted card brands and currencies on the invoice.
Buyer checklist before you enter the card
Confirm the payment link or portal hostname matches the supplier’s known domain. Card-to-invoice phishing is common: a fake PDF with a “Pay now” button. When in doubt, navigate from a bookmarked supplier portal instead of the email button.
Check amount, currency, invoice number, and whether convenience fees or surcharges appear before you submit. Screenshot the review page. If the total exceeds the invoice without a disclosed fee, stop and call AP’s known number.
Know your card’s commercial terms: some corporate cards block certain merchant category codes; some require pre-approval above a threshold. A failed authorization overnight can miss an early-pay discount window.
Decide whether rewards points are worth a surcharge. A 3% fee can erase card rewards on large invoices; ACH may be cheaper even if it earns no points.
Seller acceptance, surcharges, and disclosures
If you accept cards, say so on the invoice and in the portal. Ambiguous “online payments” language creates support tickets. List brands (Visa, Mastercard, Amex) you actually process.
Surcharges: U.S. rules vary by state and by card-network programs. Disclose the fee clearly before payment, never as a surprise on the receipt only. For state-level orientation see credit card surcharge laws by state, then confirm with your processor counsel for your nexus.
Cash discount vs surcharge: some sellers price a card price and a lower cash/ACH price. Document which model you use so sales and AR do not contradict each other on sales calls.
Chargeback risk: ship or deliver before capturing when your industry expects it, keep proof of service, and match remittance advice to invoice numbers so friendly fraud is easier to fight.
Posting, remittance matching, and partial pays
When a card payment lands, post it to the correct invoice immediately. Unapplied cash in a holding account creates duplicate collections calls and angry customers who already paid.
Partial payments: decide whether the portal allows underpays. If yes, age the remainder and send an updated statement. If no, reject and ask for full amount or a written short-pay reason (debit memo).
Multi-invoice checkout: require the buyer to select invoice IDs; do not accept a single unlabeled card charge against “open balance” without remittance detail.
Failed auth / expired cards: send an automatic retry notice once, then offer ACH instructions. Endless quiet failures show up as past-due even though the buyer “thought it paid.”
Refunds and credits: refund to the same card when required by processor rules; issue credit memos for negotiated adjustments so revenue recognition stays clean.
When card is the wrong rail
Very large B2B invoices: wire or ACH usually wins on fee and on maker-checker controls inside the buyer’s treasury team.
International buyers: cross-border card fees and currency conversion can exceed a well-prepared wire. Quote Incoterms and banking details early.
Recurring retainers: store-on-file card with clear authorization, or better, ACH mandate. Unexpected monthly card charges spike chargebacks.
Customers who prohibit card surcharges in their vendor master: respect the master data; offer ACH and note it in your CRM so sales does not promise card-only checkout.
Fraud and ops red flags
New pay-to bank details in an email thread: verify out-of-band before any card-to-ACH switch. Invoice-to-pay fraud often starts with a “updated banking” note.
Mismatched bill-to and cardholder names can be legitimate (employee paying on behalf of company) but deserve a quick check on high amounts.
Velocity: multiple cards tried in minutes against one invoice often means a stolen-card test. Freeze the portal attempt and contact the known AP email.
Keep a one-page internal runbook: who can issue refunds, who calls the processor, and how you document evidence for chargebacks. Train AR backups, not only the primary cashier.
Related AR language: when the invoice is due later but the buyer still wants to pay by card on or before the due date, align the card capture with the same due-date math used in your Net 30 examples on this site.
Processor and reconciliation workflow
End of day: download processor settlements and match batch totals to AR cash receipts. Differences often come from fees withheld, partial captures, or currency conversion on cross-border cards.
Merchant category and statement descriptor: set a descriptor the buyer will recognize on the card statement (“ACME INV”) so they do not file a chargeback out of confusion.
Tokenization for repeat buyers: store tokens only through your processor’s vault, never raw PAN in your CRM. Limit who can trigger a charge on a saved card.
Month-end: reconcile surcharge revenue (if any) separately from product revenue so finance can report cleanly.
When a chargeback arrives, pull the signed invoice, delivery proof, and checkout disclosure screenshot within the processor deadline. Late evidence packages lose winnable cases.
FAQ
Can I force every customer to pay by card?
Contract and relationship decide. Many buyers refuse card fees; offer ACH as the default.
Does paying by card extend Net 30?
No. The due date stays the due date; the rail only changes how cash moves.
Who eats the processor fee?
Either bake it into the price, or show a lawful surcharge up front. Hiding a processing add-on at checkout is how chargebacks start.
What reference should appear on the statement?
The invoice number (see invoice vs receipt vs bill) plus customer name if space allows.