> For the complete documentation index, see [llms.txt](https://cranford-tech.gitbook.io/freelancer-marketplace/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cranford-tech.gitbook.io/freelancer-marketplace/key-payment-features/capturing-a-payment.md).
# Capturing a payment
Once a Customer has submitted a proposal and authorized a payment, the [status of a job](/freelancer-marketplace/key-features/job-statuses.md) will be **awaiting confirmation**. At this point, the Freelancer will be able to accept a job in their Dashboard. When they click the 'Accept Job' button:
* The status of the job is changed to **in progress**
* The payment that was authorized by the Customer is captured
You'll note in your Stripe dashboard that before the payment is captured, it looks like this:
After the payment is captured, it changes to this:
This means the payment has been processed and the funds are in your platform and the Freelancer's Stripe account (the exact division depends on what platform fee you are taking).
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://cranford-tech.gitbook.io/freelancer-marketplace/key-payment-features/capturing-a-payment.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.