HoneyBook can do more than create an invoice. A business can build an invoice into the same client workflow used for services, contracts and booking, allow the client to pay online, establish a payment schedule, track payment status and receive the resulting funds through its connected financial setup. Current U.S. payment options include cards and ACH bank transfer, while payments received externally by cash, check or another outside method can be recorded manually.
Understanding that sequence prevents an important misconception:
a client paying an invoice and money reaching the business’s bank account are not the same event.
Processing occurs in between.
How an Invoice Fits Into HoneyBook
HoneyBook invoices are created through the Smart File system.
An Invoice & Pay block includes the invoice and payment page. The file can also be designed around other steps in the client’s experience, allowing invoicing to sit alongside the broader booking process.
The invoice can contain the services and amounts being billed, taxes, discounts or service charges where appropriate.
Payment settings can then establish:
- due dates;
- a payment schedule;
- available payment methods;
- autopay settings;
- late fees;
- client tipping where enabled.
HoneyBook currently supports both standard and recurring invoice configurations.
What Payment Methods Can Clients Use?
For U.S. businesses, HoneyBook currently documents several possibilities.
ACH bank transfer
The client enters bank information during checkout.
ACH costs less to process than cards under HoneyBook’s current fee schedule, but it takes longer to clear.
Credit or debit card
Clients can pay using supported card networks.
HoneyBook distinguishes ordinary cardholder-entered payments from card-on-file transactions.
Apple Pay and Google Pay
Supported mobile wallets can be used in qualifying HoneyBook checkout experiences when the client’s device and browser are configured appropriately.
Cash or check
If the business receives money outside HoneyBook, it can record the payment manually rather than processing the transaction through HoneyBook.
This last category is useful because payment tracking and payment processing are separate concepts. HoneyBook can keep an invoice record updated even when HoneyBook did not move the money.
Current HoneyBook Transaction Fees
At the time of this review, HoneyBook publishes the following U.S. transaction fees:
| Payment type | Published fee |
|---|---|
| ACH bank transfer | 1.5% |
| Visa/Mastercard, cardholder entered | 2.9% + $0.25 |
| American Express/Discover | 3.4% + $0.09 |
| Card on file | 3.4% + $0.09 |
| Cash/check outside HoneyBook | No HoneyBook transaction fee |
These are transaction charges, not HoneyBook membership prices.
A business using the $29 Starter subscription, for example, does not thereby eliminate card-processing fees.
That is why payment volume can matter when evaluating the total cost of the platform.
How Long Do HoneyBook Payments Take?
Current published processing times vary substantially by method.
HoneyBook says card payments through Smart Files generally take approximately 2–3 business days, while U.S. ACH payments generally take approximately 7–8 days.
Payments collected through lead forms are currently listed at approximately 5–7 business days, regardless of payment type.
HoneyBook further notes that card payments submitted before 4:00 p.m. Pacific Time typically deposit after two business days, while those submitted later generally require three.
These are estimated processing windows, not guarantees that every transaction will settle at exactly the same time.
Bank holidays, verification issues and payment problems can affect the path.
Why ACH and Card Payments Behave Differently
ACH and card rails have different economics and settlement processes.
In HoneyBook, that tradeoff is visible directly:
ACH → lower processing cost, slower processing
Card → higher processing cost, faster processing
A business asking clients to pay large invoices may therefore care considerably about the difference.
For example, 1.5% and 2.9% + $0.25 are relatively close when looking at percentages in isolation, but the dollar difference increases as invoice size rises.
On the other hand, waiting 7–8 days for ACH may be undesirable when cash timing is more important than the lower fee.
The correct method depends on the business’s economics and client experience.
Payment Schedules, Deposits and Autopay
HoneyBook allows businesses to divide invoice totals into payment schedules.
That makes it possible to collect, for example, a booking payment first and another payment later rather than asking for the entire project value at once.
Current invoice settings also support autopay controls.
This matters for longer client engagements because the invoice becomes part of the project’s timeline.
A payment schedule is therefore not just a financial setting. It can define milestones in the business’s operational process.
Automations can also respond to payment events. HoneyBook’s current Automations 2.0 documentation includes triggers for a first payment and an invoice being paid in full.
Can You See Whether a Payment Is Still Processing?
Yes.
HoneyBook’s payments area distinguishes statuses such as paid, processing, upcoming and overdue payments.
Its homepage payment overview also provides a current-month summary based on those categories.
That distinction is useful when reconciling an invoice against money actually available in a bank account.
An invoice can show client activity before settlement is complete.
What About Refunds?
HoneyBook currently allows qualifying payments processed through the platform to be refunded from the business side.
Its July 2026 refund documentation says refunds are sent back to the client’s original payment method and generally take 7–14 business days after processing. Refunds are initiated by debiting the business’s linked checking account.
The documentation also says HoneyBook adds the original processing fee back to the refunded amount so the client receives the full refund.
Payments originally made outside HoneyBook are handled differently: they can be recorded as refunded in HoneyBook, but the actual money movement must be handled using the outside method.
What Happens With a Chargeback?
A chargeback is different from an ordinary refund.
It begins when the client disputes a payment through the financial institution associated with the payment method.
HoneyBook’s current dispute documentation says card disputes can lead to the disputed amount plus a $10 dispute fee being debited from the linked bank account or recovered from future payments when necessary. The client’s bank ultimately decides the dispute outcome.
HoneyBook may help collect supporting evidence for eligible card disputes, but it does not control the issuing bank’s final decision.
HoneyBook’s documentation also warns that ACH disputes operate differently and may not provide the same opportunity to contest the transaction through HoneyBook.
For businesses providing higher-value services, this makes good documentation important.
A contract, communication history, invoice and evidence that agreed services were delivered can become more than administrative records.
Invoice, Payment and Deposit Are Three Separate Things
A useful mental model is:
Invoice → Client Payment → Processing → Deposit
The invoice establishes what is owed.
The client payment is the transaction initiated against that obligation.
Processing covers the period while the transaction moves through the payment system.
The deposit is when funds reach the destination available to the business.
Treating those as separate stages makes HoneyBook’s payment statuses and timing considerably easier to interpret.
Where Smart Files Fit
A payment may be technically financial, but HoneyBook treats it as part of the client experience.
The same Smart File can help a client understand the services, sign a contract and reach an invoice or payment action rather than receiving disconnected documents from several different services.
That integration is one of the main reasons the payment system cannot be evaluated purely as a payment processor.
For the document architecture behind it, read How HoneyBook Smart Files work.