> 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/why-kurv.md).

# Why Kurv Wins

The differentiators that win deals — and how to frame them.

Merchants have plenty of processors to choose from. These are the reasons they choose Kurv — the points to lead with and keep coming back to.

Kurv already powers **30,000+ businesses** and processes **1M+ transactions every week** — so you're never selling an unproven story.

## The differentiators that matter

| Differentiator                    | Why it lands                                                                                                                                                              |
| --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Transparent pricing, your way** | Merchants choose the model that fits — **Flat Rate**, **Zero Cost**, or **Interchange Plus** — plus **free terminal options for new customers**. No confusing statements. |
| **Fast approval**                 | Proprietary underwriting technology gets merchants live fast, not in a week.                                                                                              |
| **24/7/365 U.S. live support**    | Real people on a **350+ dedicated team**, any hour — not a chatbot and not a ticket queue.                                                                                |
| **Native Tap to Pay**             | On both **iOS and Android** — a phone becomes a terminal with no extra hardware.                                                                                          |
| **One unified platform**          | In-person, online, mobile, and invoicing on one dashboard and one deposit — with **1,000+ integrations**.                                                                 |
| **Fast, painless setup**          | Plug-and-play hardware; most merchants are running in **15–20 minutes**.                                                                                                  |

## How to frame it

{% hint style="success" %}
Lead with **pricing transparency** and **speed**. "You pick the pricing model that fits your business, most merchants are approved in about a day, and real support answers 24/7" reframes the conversation away from rate-shopping and toward value.
{% endhint %}

{% columns %}
{% column %}
**Against big processors**

Kurv answers the phone. Position responsive U.S. support and transparent, choose-your-model pricing against slow, faceless incumbents and statements no one can read.
{% endcolumn %}

{% column %}
**Against app-only players**

Kurv scales from a phone with Tap to Pay all the way to a full countertop system — on one platform with 1,000+ integrations. Merchants won't outgrow it.
{% endcolumn %}
{% endcolumns %}


---

# 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/why-kurv.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.
