> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/revenue/invoices/charge-a-customers-saved-card-for-an-invoice.md). # Charge a customer's saved card for an invoice If a customer has a saved payment method, you can charge it directly with Charge Payment Method, as long as you have permission to charge payments. On a Draft invoice (with no autopay), it's available from the "..." menu; once the invoice has been sent (or the customer has autopay enabled), it moves to the main action bar. If Charge Payment Method is missing but you need to charge saved payment methods, contact your business's administrator to review your role. Charging runs the payment and, when it succeeds, applies it to the invoice. Your processing fee is added the same way it is on the customer's pay page; on an invoice whose fees are waived, nothing is added and you charge exactly the amount entered (see [Waive processing fees on an invoice](/revenue/invoices/waive-processing-fees-on-an-invoice.md)). Charging the full remaining balance moves the invoice to Paid; charging less than the remaining balance leaves it partially paid, or Overdue if the invoice is past due. This is different from Record Payment, which only records a payment you collected some other way without charging anything. To charge several of a customer's invoices at once — a card on file or a new card read over the phone — use **Bulk Actions → Charge payment method** on the Invoices page instead. Each invoice is charged separately. See [Bulk actions on invoices](/revenue/invoices/bulk-actions-on-invoices.md). > **Where to find it:** On the open invoice, the "..." menu (Draft) or the action bar (once sent or autopay enabled) ## Related guides * [How your customer pays an invoice online](/revenue/invoices/how-your-customer-pays-an-invoice-online.md) * [Can I reverse a payment I recorded?](/revenue/invoices/can-i-reverse-a-payment-i-recorded.md) * [Record a payment on an invoice](/revenue/invoices/record-a-payment-on-an-invoice.md) * [Bulk actions on invoices](/revenue/invoices/bulk-actions-on-invoices.md) * [Add a line item to an invoice](/revenue/invoices/add-a-line-item-to-an-invoice.md) * [Apply a discount to an invoice](/revenue/invoices/apply-a-discount-to-an-invoice.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://learn.withessential.com/revenue/invoices/charge-a-customers-saved-card-for-an-invoice.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.