> 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/peak-payment.md).

# Peak Payment

Use Peak Payment attendance, sales and membership activity in Perkville.

## Integration at a glance <a href="#capabilities-and-use-cases" id="capabilities-and-use-cases"></a>

{% hint style="info" %}

* **Eligibility** — Restrict earning by member type and member status.
  {% endhint %}

* **Attendance** — Reward check-ins, class attendance and appointments.

* **Purchases and membership sign-ups** — Qualifying purchases and sign-ups can use configured earning rules; anniversary rewards depend on the source join date.

* **Membership tier rewards** — The reviewed member-data workflow sends membership status and join date, but not membership type. Tier rewards and tier-based upgrade rewards require an additional verified membership-type mapping. Confirm your connection before enabling [Membership tiers](https://docs.perkville.com/features/earning-rules/membership-tiers.md).

* **Referral workflow** — A configured integration can create a referral from Perkville; confirm the destination and matching rules with your CSR.

Your configured rules determine which eligible activities award points and which workflows are enabled.

## Integration Steps

1. Make an API key for each location in Peak Payment
2. Email it to your Perkville Customer Success Representative securely via a secure site, like[ https://onetimesecret.com/](https://onetimesecret.com/), click “Create a secret link”, generate a password, and email it directly to the Perkville rep. Be sure to save the API Key in case there are any issues accessing the one time secret link.

<br>

## FAQ

### Do multiple locations need separate API keys?

Yes. The setup below calls for an API key for each location.

See the [Peak Payment partner profile](https://partners.perkville.com/partners/peak-payment-solutions) for additional integration information.


---

# 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/peak-payment.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.
