A practical checklist for Pay invoice by card or ACH

Why offer pay invoice by card or ACH at all

Giving customers the choice to pay invoice by card or ACH is one of the simplest ways to get paid faster. Different buyers have different habits. Some want the convenience and float of a card, others prefer a bank transfer for larger amounts. When you only offer one, a share of your invoices stall against a preference you could have accommodated.

This checklist walks through what to set up before, during, and after the payment so that offering both methods actually speeds up collection instead of complicating it. The order matters, because each step depends on the one before it.

Before you send: set up both rails

The first job is to make sure your business can actually accept both methods cleanly. That means having card acceptance and ACH acceptance running through one system rather than two disconnected tools. Flux provides both on a single platform, along with drop-in hosted fields and tokenization, so the setup is one integration rather than a patchwork.

While you are setting up, decide your policy on fees. Where local surcharging rules allow, Flux lets you pass the card fee to the customer at checkout. Decide in advance whether you will do that for card payments and how you will present ACH, so the customer sees consistent, honest options.

On the invoice: make the option obvious

A payment method the customer cannot find might as well not exist. The invoice should carry a clear way to pay, and it should show both card and ACH as choices rather than burying one. If the customer has to email you to ask how to send an ACH transfer, you have reintroduced the friction you were trying to remove.

Keep the call to action simple: one link, both options behind it. The less the customer has to think about how to pay, the sooner they do.

At payment: let the customer choose

When the customer clicks to pay, the checkout should present card and ACH side by side and let them pick. For the card path, Flux captures the card details inside origin-isolated iframes on payments.fluxpayments.com, so the sensitive data never touches your servers or domain. For the ACH path, the customer authorizes a bank transfer.

This is also where security reassurance pays off. Flux is SAQ-D Level 2 PCI DSS certified, so the customer is entering their details into a properly handled, isolated environment. A checkout that feels safe converts better than one that makes the buyer hesitate.

After payment: settlement and reconciliation

Once the customer pays, two things need to happen: the money needs to reach you, and the invoice needs to close. On settlement, know the timing so you can plan. With Flux, card payments settle in 1-2 business days and ACH in 1-3 business days.

On reconciliation, the payment should mark its invoice paid without manual keying. Flux offers webhooks and a QuickBooks integration that syncs transactions to the books, so a card or ACH payment can close the right invoice automatically. That is what keeps offering two methods from doubling your bookkeeping.

The quick checklist

Here is the short version you can run through before you send your next invoice. First, confirm both card and ACH acceptance are live on one platform. Second, decide your fee and surcharging policy and apply it consistently. Third, make sure the invoice shows both payment options behind a clear link.

Fourth, confirm the card path uses isolated hosted fields so card data never hits your systems. Fifth, know your settlement timing for each method. Sixth, verify that paid invoices reconcile into your books automatically. Tick all six and your pay-by-card-or-ACH flow is genuinely working, not just technically possible.