> 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/payments/overview.md).

# Overview

The Freelancer Marketplace template comes with pre-built workflows that allow you to process marketplace payments with Stripe Connect.

To use these pre-built payment workflows you will need to:

1. [Install the Stripe Connect - Marketplace plugin](/freelancer-marketplace/payments/installing-the-stripe-connect-marketplace-plugin.md)
2. [Enable the pre-built payment workflows](/freelancer-marketplace/payments/how-to-enable-payments.md)

{% hint style="info" %}
[Stripe Connect](https://stripe.com/connect) is a leading solution for marketplace payments
{% endhint %}

&#x20;Payments that customers make for services can be split between your marketplace and the Freelancer. EG if a Customer pays $100 for a service, your marketplace might take $20 of this (20%), with the remainder going to the Freelancer ($80 or 80%).


---

# 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/payments/overview.md?ask=<question>&goal=<endgoal>
```

`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.
