> For the complete documentation index, see [llms.txt](https://docs.perkville.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.perkville.com/integrations/integration-reference/mindbody/creating-a-perkville-payment-type.md).

# Creating a Perkville payment type

To process rewards by showing that the customer used Perkville to pay for the item/service, you'll want to create a Perkville payment type.

Follow the steps below to set up Perkville as a payment type in MINDBODY:

1. Login to MINDBODY as the owner
2. Follow this menu path: Home => Manger Tools => Settings => Payment Methods
3. Type Perkville in the Add New Section at the top of the screen
4. Select all options except "CashEQ?" Cash EQ? should not be selected.
5. Type “Perkville Code” in PayNotes Label
6. Click the Add button to add Perkville as a payment type.

<figure><img src="https://2181708597-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSiE75SeColbiBVbet0NZ%2Fuploads%2FZfQgKmoFJY4pXHuS9fZd%2FArticle-Inline-731102.png?alt=media&amp;token=8154ab97-c40e-43da-bf3e-721a273f397f" alt=""><figcaption></figcaption></figure>


---

# 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://docs.perkville.com/integrations/integration-reference/mindbody/creating-a-perkville-payment-type.md?ask=<question>&goal=<user_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.
