01 / The account behind the job
Getting paid starts
before you send the invoice.
Credit card processing for contractors lets a customer pay a contracting business by card—on site, through a payment link, or through another approved payment channel. A merchant account and its connected payment tools support the transaction. The useful question is how that setup fits the work you actually do.
A plumber collecting after a service call has a different payment timeline from a remodeler taking money before materials arrive. A commercial contractor billing several milestones has a different reconciliation problem from a maintenance business collecting a monthly service fee. An account should be reviewed for those differences.
A card payment can be approved today while the work is still ahead—and the money may become available on a separate schedule. Map all three: collection, delivery and funding.
Before comparing rates, describe what customers buy, your usual and largest payment amounts, when you collect, and how long it takes to deliver. Then compare the actual account terms and the tools needed to connect each payment to a job.
New to the terminology? Our merchant account guide explains the account, gateway and processor roles. This guide focuses on what changes when your product is work performed over time.
02 / Start with your operation
One trade category.
Several payment realities.
“Construction” is a starting point, not a complete business description. Explain the services you perform, your customer type and who has the contract with the customer. These four patterns give you a useful way to frame the conversation.
Finish the visit.
Collect on site.
Plumbing, electrical, HVAC and other service calls may finish the same day. A mobile reader or approved tap-to-pay setup can support payment at completion; a secure payment link can support a customer who is elsewhere.
Collect in stages.
Deliver over time.
A remodel or installation can involve an initial payment, material procurement, scheduled work and a final balance. Clarify the interval between each charge and the related work, including what happens when a supplier or permit delays the job.
Larger invoices.
More people approving them.
A commercial customer may require a purchase order, an approved pay application or a specific invoice format before paying. Confirm the contracting entity, authorized payer and invoice reference, particularly when a subcontractor or property manager is involved.
Repeat visits.
Clear billing permission.
A continuing service plan needs a defined price, billing frequency, scope and cancellation process. A stored card or recurring-billing feature should fit the customer agreement and the provider’s supported workflow.
These are business-model examples, not a statement that every trade, project or transaction is eligible. Specific processing arrangements require provider review.
03 / Follow the job
Six handoffs.
One connected payment record.
A useful contractor payment workflow ties the agreed scope to the invoice, the customer’s authorization, the payment result and the work record. Give every job a consistent reference so your office and field team can follow the same story.
Agree on the work and payment terms.
Define the scope, price or pricing method, expected timing and payment milestones before collecting. Identify the correct customer and contracting entity. Make cancellation, refund and change-order terms understandable; an invoice alone may not contain the complete agreement.
Keep together: accepted estimate, applicable contract, terms and job reference.
Collect the agreed initial payment.
Use the amount and timing permitted by the contract and applicable rules. Send a receipt showing what the payment covers and what remains due. Separately confirm whether your provider supports collecting that far ahead of delivery; customer agreement and provider approval address different questions.
Keep together: invoice, authorization record, receipt and planned work date.
Bill progress against a defined milestone.
Connect the next invoice to the agreed work or billing event. Record the amount already billed, prior payments and remaining balance. If an approval or inspection is part of the contract, resolve that step before treating the milestone as accepted.
Keep together: milestone description, progress evidence, required acceptance and invoice.
Make the change order visible.
Document the revised scope, price, timing and payment consequences. Obtain the approval your contract and local rules require before proceeding. Update the job total and balance; an extra charge should not arrive as a surprise because someone in the field agreed to “a little more work.”
Keep together: approved change, revised total and affected invoices.
Close the work before closing the balance.
Record completion, agreed punch-list items, handover and any acceptance required for the final invoice. Send a statement that clearly separates the original scope, approved changes, payments and remaining amount. A completion acknowledgment documents what happened; it does not eliminate dispute rights.
Keep together: completion records, customer communications and final invoice.
Match the payment to the bank activity.
Reconcile the invoice with the successful charge, processing fees, refunds, disputes, any reserve and the payout. A bank deposit can combine multiple jobs; a paid invoice and a bank deposit are not interchangeable records.
Keep together: payment reference, settlement report and accounting entry.
There is no universal contractor deposit percentage.
Residential home improvement, commercial work and different jurisdictions can have different contract and collection rules. For example, California CSLB states that home-improvement down payments generally cannot exceed $1,000 or 10% of the contract price, whichever is less, and describes written change-order requirements. That is a California home-improvement example—not a national payment template. Verify the rules for your work before setting a deposit schedule. [1]
Progress invoicing also needs to work in your software. QuickBooks, for example, describes creating multiple partial invoices from an estimate and tracking the remaining amount. That illustrates an accounting workflow; it does not establish that a given gateway, subscription or integration is included in a NUMUS processing arrangement. [2]
04 / Match the channel to the moment
At the jobsite.
At the desk. On the customer’s phone.
Choose payment methods around how your customer actually approves and pays an invoice. Confirm which methods the proposed account supports, how they are priced and who will manage them.
| Collection method | Useful situation | What to confirm |
|---|---|---|
| In-person card payment | A customer pays after a service visit or installation. | Supported reader or tap-to-pay device, field-user permissions, connectivity and receipts. Use the supported chip/contactless flow when available. |
| Hosted invoice or payment link | The payer is off site, or an office sends an invoice after review. | How the link connects to the job, invoice status, expiry and customer receipt; how failed and duplicate payments are handled. |
| Virtual terminal | Authorized staff process a permitted remotely provided payment. | Remote-entry pricing, verification tools, staff access and the approved way to receive payment details. |
| Card on file | A supported service plan or agreed later payment. | Customer permission, token storage, later-charge rules and cancellation. Never assume a prior payment authorizes every future charge. |
| Bank payment / ACH | A customer prefers to pay an invoice from a bank account. | Separate availability, authorization, timing, return exposure and pricing. Card acceptance does not automatically include ACH. |
An authorization
is not a long-term deposit.
An authorization places a temporary hold; capture completes the charge. Authorization validity depends on the transaction and supported payment method. Do not assume one card hold can remain open throughout a multi-month project. Ask your provider how the agreed initial and later payments should be collected. [3]
Store the permission.
Protect the card data.
Use your provider’s supported secure collection and tokenization tools. Keep full card numbers out of ordinary job notes and email. PCI SSC says card verification codes cannot be stored after authorization—even if the customer agrees to future charges. A saved card is not a saved CVV. [4]
Give your field team a repeatable process.
Decide who can send links, take payments, issue refunds and view reports. Train staff to confirm the job and amount before charging, check the actual payment status before retrying, and issue the correct receipt. A customer saying “my screen froze” is a reason to check the transaction record, not immediately charge again.
Before launch, test an invoice, partial payment, failed payment, duplicate attempt, approved change and refund using the provider’s test process. Verify what the customer sees and what reaches your accounting workflow.
05 / Make the economics visible
The invoice amount
is not the amount you keep.
Compare the full cost of an account against realistic transaction sizes. A percentage charge grows with the invoice; a fixed per-transaction charge repeats each time you collect. Monthly charges, hardware, gateway costs, refunds, disputes and reserves can affect the complete picture.
Illustrative commercial project / Not a quote
A $25,000 project.
A $2,500 approved change.
This fictional commercial renovation finishes at $27,500. The schedule below is an arithmetic illustration, not a recommended deposit schedule or a statement about what any jurisdiction permits.
Fixed fee held at $0.30 per charge. Adjust the percentage to see the effect; these are illustrative inputs, not available NUMUS rates.
Use the payment schedule that fits your agreement, the work and applicable rules. Splitting a payment does not make a transaction eligible or remove an account limit. Tell the provider about your largest expected charge before taking it.
To model your own monthly volume, average ticket and recurring costs, use the credit card processing fee calculator. For comparing proposals, use the merchant processing quote checklist.
If you plan to pass along a fee, resolve the rules first.
A credit-card surcharge, a cash discount and a convenience fee are different arrangements. Do not treat them as interchangeable labels for adding a percentage to an invoice. Visa and Mastercard impose conditions on credit-card surcharging and prohibit surcharges on their debit and prepaid cards; applicable law and your provider’s requirements also matter. Ask for a supported, documented setup before advertising or applying a program. [5] [6]
A simple comparison still matters: what is the customer shown, what is charged, what costs remain with your business, and how are refunds handled? A “zero cost” headline cannot answer those questions for you.
06 / Explain what sits behind the volume
Help the reviewer
understand the project pipeline.
A contractor merchant-account application should describe more than annual revenue. The reviewer needs a clear picture of who pays you, what they buy, the transaction amounts and the gap between collection and delivery. The precise information requested depends on the reviewing bank or provider.
Your business and customer relationship
Describe the legal entity, trades, operating locations, website and services. Explain whether you contract directly with the property owner or collect through another business. Identify any licenses or other documentation the reviewer requests.
Useful context: “We install commercial equipment for local businesses” is more specific than “construction services.”
Your normal and largest card payments
Separate total sales from expected card volume. Provide a typical card payment, the largest expected charge and the number of monthly payments. Label startup projections as estimates; explain seasonality or a one-off large contract.
Useful context: a $500 service ticket and a $30,000 installation payment should both be visible in the account discussion.
Your collection-to-delivery timing
Explain initial payments, progress invoices and final collection. Show how far ahead of performance you collect and what obligations remain after a charge. Include material lead times, cancellation exposure and the number of active prepaid jobs.
Useful context: provide your ordinary workflow and explain what happens when a project stalls.
Your records and processing history
If you already accept cards, be ready to provide the requested processing statements and context for refunds, disputes or holds. Use approved contracts, invoices and completion records to explain how your business documents performance.
Useful context: a cause, corrective action and current process are more informative than an unexplained dispute count.
Your cash-flow and refund plan
Explain how you fund labor and suppliers while payments are pending, and how you would address a canceled job or required refund. Ask whether any reserve, funding delay or account limit applies and how it changes as your business develops.
Useful context: show the plan for an ordinary delay and for several exceptions at once.
A larger ticket or advance payment can prompt closer review; neither alone establishes that a business is “high risk” or predicts approval. Describe the actual business accurately and use the underwriting process guide to prepare for follow-up questions.
Plan around available cash, not just sales.
An invoice due date does not guarantee customer payment. A successful card charge does not guarantee same-day availability. Ask about settlement cutoffs, weekends, account review and any reserve. Our rolling reserve simulator illustrates withholding and release timing; your agreement determines actual terms.
Intuit QuickBooks
January 2025 U.S. survey
Late invoices belong in the cash-flow conversation.
In Intuit’s survey of 2,487 U.S. small businesses, 47% reported having at least some invoices more than 30 days overdue. [7]
Our takeaway: keep customer payment timing separate from processor funding timing, and plan how your team follows up on each.
Self-reported, cross-industry survey of businesses with 0–100 employees, using paid and QuickBooks customer panels. This is not a contractor-only finding, the share of all invoices overdue, or evidence that accepting cards prevents late payment.
07 / Keep the evidence with the work
When a payment is questioned,
make the job easy to explain.
Contractor disputes can involve whether work was delivered, whether it matched the agreement, whether a cancellation was handled, or whether an expected refund was processed. Start with the actual dispute reason and your provider’s response deadline. The useful evidence differs by reason; Visa’s merchant guidance distinguishes these categories. [8]
Before there is a problem
Keep the accepted scope and terms, invoice history, approved changes, dated work records, relevant customer communications and completion evidence together. Use a card-statement descriptor the customer can recognize and give them a working support contact.
When a problem arrives
Assign an owner, preserve the relevant records, and identify the exact charge and disputed work. Build a concise timeline that answers the stated issue. Follow the provider’s evidence instructions and deadline; do not submit a pile of unrelated documents.
A change order needs more than a new invoice.
Consider a customer who approved a kitchen refit and later requested additional electrical work. Your record should connect the request, revised scope, agreed price, timing, acceptance and related charge. Photos may show work was performed; the agreement helps explain which work and price the customer authorized. Neither guarantees a dispute outcome.
A refund needs an operational owner.
Record the authorized refund decision, amount, affected invoice and original payment. Confirm the refund’s status in the provider’s system and reconcile it. If a dispute is already open, coordinate with the provider before independently refunding so you can avoid an unintended duplicate credit.
Keep customer data proportionate to the issue. A job folder should not become an unprotected archive of card details. For help making card charges recognizable, see our statement descriptor guide.
08 / Ask better questions
Choose the account
for the way you get paid.
The right comparison is between complete proposals for the same operation. Bring your actual payment channels, project timeline and transaction sizes to each conversation, then get the material terms in writing.
| Decision | What to establish |
|---|---|
| Business fit | Does the scope cover your actual trades, entity, customer types and places of operation? Who reviews material changes? |
| Ticket size & volume | What amounts and monthly volume are supported? What is the process before a larger-than-usual invoice or seasonal increase? |
| Advance collection | Does the provider support your collection-to-delivery window and progress-billing model? What conditions apply? |
| Total cost | How do card-present, keyed and online transactions differ? Include monthly, gateway, equipment, refund, dispute and other applicable charges. |
| Cash availability | What funding schedule, cutoff, reserve or hold applies? What changes after a refund, dispute, account review or closure? |
| Software & staff | Does the specific setup connect with your estimating, invoicing and accounting tools? Who implements it, and what can each staff member do? |
| Customer experience | What appears on the payment page, receipt and statement? How are deposits, balances, failures and duplicate attempts handled? |
| Support & exit | Who owns funding and dispute questions? What contract term, cancellation process, hardware obligation and data-export options apply? |
Ask for a demonstration using your workflow: one estimate, partial invoices, an approved change and a refund. A familiar software logo is not proof that the exact integration and functions you need are supported.
09 / Bring the business behind the job
A stronger first conversation.
A clearer path forward.
Your first inquiry can be straightforward: describe your trade, where you operate, what customers pay for, your expected card volume and the help you need. Add your usual and largest payment, and whether you collect before or after completing work.
“We handle commercial renovations, bill in agreed stages and sometimes take larger final payments. We want to understand account limits, payment links and how the money will reconcile to each job.”
Use your actual business details. This is an illustrative introduction, not a completed merchant application.Free working document
Your contractor
payment review planner.
Map your business, transaction sizes, billing milestones and provider questions before the conversation. Keep it with your team, or print a blank copy for the office.
Tell us about
the work.
Share your contracting model, collection timing and processing needs so the conversation starts with the right context.
Make the account
review easier.
NUMUS can help you organize the information and questions for a processing review through bank and ISO relationships.
Look at the
actual proposal.
If an option is available, review its scope, fees, funding and implementation against the business you intend to run.
An inquiry is a request for review, not account approval. Availability, eligibility, terms, tools and integrations depend on your business and the reviewing provider. Use a secure process for any documents requested later; keep card details out of the initial inquiry.
For the broader document list, see the merchant account application checklist.
10 / Frequently asked questions
The questions worth
settling before the first charge.
Can a contractor accept a deposit by credit card?
Potentially, when the account supports your business and advance-collection model, and the amount and timing comply with the contract and applicable requirements. Explain how far ahead of work you collect. There is no universal deposit percentage for every contractor or jurisdiction.
What is the best way to accept credit cards as a contractor?
It depends on how your customers pay. A supported mobile reader can fit on-site completion; a hosted payment link can fit a remotely approved invoice. Compare the complete cost, staff workflow, account limits, customer experience and connection to your accounting records.
How do progress payments work with a merchant account?
Your agreement defines the billing events. The payment setup collects the approved amounts and records each result. Connect partial invoices and prior payments to the overall job balance, and confirm the account supports the transaction sizes and time between payment and delivery.
Can I keep a customer’s card for the remaining balance?
Use a provider-supported card-on-file process with appropriate customer permission for the intended later charges. Confirm how changes, cancellation and failed collection work. Do not keep the card verification code after authorization, and do not treat a past charge as unlimited permission to charge again. [4]
Can I charge the customer an extra card-processing fee?
Some programs are possible subject to applicable law, card-network rules and provider requirements. Credit-card surcharges, cash discounts and convenience fees have distinct conditions. Visa and Mastercard prohibit surcharges on their debit and prepaid cards; ask for a compliant, supported setup instead of adding a blanket percentage. [5] [6]
Why might a processor review a large contractor payment?
A transaction can raise questions if it differs from the account’s expected size, volume or delivery pattern. Provide an accurate business description and discuss unusual invoices in advance. Splitting a charge to avoid a review or limit is not a substitute for an account that supports the actual transaction.
How soon will the money reach my bank account?
The provider’s terms determine funding timing and any conditions. Ask about cutoffs, non-business days, reserves, refunds and review-related holds. An invoice marked paid or a successful authorization does not by itself confirm that money is available in your bank account.
Does a signed contract prevent chargebacks?
No. A contract is one part of the record. Relevant evidence may also include accepted changes, delivery or completion records, customer communications and refund information. Respond to the specific dispute reason within your provider’s deadline; documentation does not guarantee the outcome. [8]
Sources, research notes & how to use this guide
Reviewed September 22, 2026. This is operational education, not a legal contract or a promise of eligibility. Examples are fictional. Product documentation illustrates the named provider’s workflow and does not imply an available NUMUS integration. Follow the requirements applicable to your work and actual processing arrangement.
- California Contractors State License Board — What is a Contract?
California home-improvement guidance; local scope matters. Checked September 22, 2026.
- Intuit QuickBooks — How to use progress invoicing in QuickBooks Online
Named-provider invoicing workflow; not a NUMUS integration claim. Checked September 22, 2026.
- PCI Security Standards Council — Are merchants allowed to request card-verification codes/values from cardholders?
Card-verification-code handling after authorization. Checked September 22, 2026.
- Visa — Merchant Surcharging Considerations and Requirements
Use current surcharge requirements; excludes the outdated 4% FAQ. Checked September 22, 2026.
- Mastercard — What merchant surcharge rules mean to you
Credit-card surcharge conditions and debit/prepaid exclusion. Checked September 22, 2026.
- Intuit QuickBooks — 2025 Small Business Late Payments Report
January 2025 cross-industry survey; population and finding are qualified in the text. Checked September 22, 2026.
- Visa — Dispute Management Guidelines for Visa Merchants
Merchant dispute guidance: evidence depends on the reason and applicable process. Checked September 22, 2026.
Our editorial approach explains how NUMUS develops and maintains resources.