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

# Kurv University

The sales-enablement and document library for Kurv Agents and partners — slicks, one-pagers, decks, templates, and the talking points behind them.

## What's New?&#x20;

##

## Jump in

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h3><i class="fa-folder-open" style="color:$primary;">:folder-open:</i></h3></td><td><strong>Document Library</strong></td><td>Download slicks, one-pagers, decks, and email templates.</td><td><a href="/1roOeoqsO7DNkeNJG2xS/document-library/collateral-library.md">Forms</a></td></tr><tr><td><h3><i class="fa-grid-2" style="color:$primary;">:grid-2:</i></h3></td><td><strong>Products &#x26; Services</strong></td><td>Terminals, virtual terminal, invoicing, and more.</td><td><a href="/1roOeoqsO7DNkeNJG2xS/products-and-services/products-kurvmerchant.md">Products &amp; Services</a></td></tr><tr><td><h3><i class="fa-circle-exclamation" style="color:$primary;">:circle-exclamation:</i></h3></td><td><strong>Bulletins</strong></td><td>Keep up to date with the latest bulletins.</td><td><a href="/1roOeoqsO7DNkeNJG2xS/sales-tools/solutions.md">Agent Bulletins</a></td></tr><tr><td><h3><i class="fa-handshake" style="color:$primary;">:handshake:</i></h3></td><td><strong>Selling Kurv</strong></td><td>Differentiators, ideal customers, and objections.</td><td><a href="/1roOeoqsO7DNkeNJG2xS/selling-kurv/selling-kurv.md">Overview</a></td></tr><tr><td><h3><i class="fa-compass" style="color:$primary;">:compass:</i></h3></td><td><strong>Start Here</strong></td><td>Who Kurv is, the 60-second pitch, and the partner program.</td><td><a href="/1roOeoqsO7DNkeNJG2xS/start-here/start-here.md">Overview</a></td></tr></tbody></table>

## Why merchants choose Kurv

|                                |                                                                         |
| ------------------------------ | ----------------------------------------------------------------------- |
| **30,000+ businesses**         | Powered by Kurv today.                                                  |
| **1M+ transactions / week**    | Processed across the platform.                                          |
| **24/7/365 live U.S. support** | Real people, any hour.                                                  |
| **Transparent pricing**        | Flat Rate, Zero Cost, or Interchange Plus — plus free terminal options. |
| **\~1-day approval**           | Proprietary underwriting gets merchants live fast.                      |
| **Native Tap to Pay**          | On iOS and Android — no extra hardware.                                 |

{% hint style="info" %}
**Grab-and-go:** the fastest collateral for a first meeting is the [Kurv at a Glance leave-behind](/1roOeoqsO7DNkeNJG2xS/document-library/leave-behinds.md) and the [product slicks](/1roOeoqsO7DNkeNJG2xS/products-and-services/products-kurvmerchant.md).
{% endhint %}

***

*Internal enablement resource for Kurv Agents and partners.* · Electronic Merchant Systems LLC d/b/a Kurv · (800) 726-2117 · [kurvpay.com](https://www.kurvpay.com)


---

# 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/readme.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.
