> For the complete documentation index, see [llms.txt](https://help.paintscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.paintscout.com/support/invoicing-and-payments/payments/manual-credit-card-payments.md).
# Take a Credit Card Payment
Take a credit card payment directly on an invoice using Stripe or PaintScout Payments.
Use this workflow to charge a credit card directly on an invoice when [Stripe](/support/invoicing-and-payments/payments/payment-processing-with-stripe.md) or [PaintScout Payments](/support/invoicing-and-payments/payments/paintscout-payments.md) is connected.
Before you start, make sure credit card payments are enabled for the invoice.
1\. Open the invoice and scroll to the **Payments** table.
2\. Click **+Add/Request Payment**.
3\. Select **Take Credit Card Payment.**
4\. Enter the payment amount and add a note if needed.
5\. Enter the customer's payment information and click **Pay.**
6. After the charge is submitted, the payment appears in the **Payments** table
* If the processor needs extra time to confirm the payment, you may see **Processing** before the payment resolves to **Successful** or **Failed**.
## Related articles
---
# 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://help.paintscout.com/support/invoicing-and-payments/payments/manual-credit-card-payments.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.
