> For the complete documentation index, see [llms.txt](https://university.kurvpay.com/1roOeoqsO7DNkeNJG2xS/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://university.kurvpay.com/1roOeoqsO7DNkeNJG2xS/selling-kurv/pricing-and-commissions.md).

# Pricing your Merchants

How to talk about pricing — the story, not the rate sheet.

Kurv's pricing story is a selling advantage on its own. This page covers how to *talk* about it. For a merchant's exact rates — and your commission terms — always work from current, approved figures.

## The pricing story

Kurv meets merchants where they are with a model that fits, plus a head start on hardware:

| Model                     | What to say                                                                                                 |
| ------------------------- | ----------------------------------------------------------------------------------------------------------- |
| **Flat Rate**             | "One simple, predictable rate — easy to forecast every month."                                              |
| **Zero Cost**             | "Offset your processing fees at checkout, so card acceptance costs you next to nothing."                    |
| **Interchange Plus**      | "Transparent, cost-plus pricing — you see exactly what the networks charge and Kurv's small margin on top." |
| **Free terminal options** | "New customers can start with free terminal options — less upfront cost to get going."                      |

## How to run the pricing conversation

{% stepper %}
{% step %}

### Reframe away from one rate

Merchants rate-shop out of habit. Move the conversation to **total cost of ownership** — the whole statement, add-ons, and the cost of support you can't reach all count.
{% endstep %}

{% step %}

### Anchor on transparent, choose-your-model pricing

This is the headline: Kurv lets the merchant pick **Flat Rate, Zero Cost, or Interchange Plus** — plus **free terminal options for new customers** — instead of a one-size-fits-all rate.
{% endstep %}

{% step %}

### Quote from approved figures only

Pull the merchant's actual rate and your commission structure from current, approved sources — never estimate on the spot.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
**Important:** Specific processing rates, fees, and agent commission/residual terms are set in your Kurv agent agreement and each merchant's signed contract. This page intentionally lists **no** rates or percentages — always confirm current terms with your Kurv partner manager before quoting.
{% endhint %}

{% hint style="info" %}
Need the current rate card or commission schedule? Contact your Kurv partner manager — those figures live in your agent portal, not in this hub.
{% endhint %}


---

# 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://university.kurvpay.com/1roOeoqsO7DNkeNJG2xS/selling-kurv/pricing-and-commissions.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.
