> 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/start-here/who-is-kurv.md).

# Who Is Kurv

The company, the mission, and what Kurv stands for.

Kurv is a modern payments company on a simple mission: **keep payments simple in a complex world.** We build an ecosystem of payment solutions driven by technology — but focused on connecting people.

Kurv is the brand of **Electronic Merchant Systems LLC**, bringing decades of merchant-services experience to a fresh, technology-first platform.

## Kurv by the numbers

|              |                                             |
| ------------ | ------------------------------------------- |
| **30,000+**  | Businesses powered by Kurv                  |
| **1M+**      | Transactions processed every week           |
| **350+**     | Professionals on one dedicated support team |
| **24/7/365** | U.S.-based live support                     |

## What we believe

Payments should remove complexity, not add to it. Merchants deserve efficient, transparent processing and a partner they can rely on — no hang-ups, no hurdles, no headaches. When payments just work, business owners get back the one thing they never have enough of: time to grow.

## What we stand for

| Value               | What it means for your merchants                                                       |
| ------------------- | -------------------------------------------------------------------------------------- |
| **Transparency**    | Clear, honest communication — pricing and terms with nothing buried in the fine print. |
| **Dependability**   | Consistency and care on every transaction, every day.                                  |
| **Efficiency**      | Streamlined, simple solutions that get merchants paid faster.                          |
| **Responsiveness**  | People-first support that evolves alongside the business.                              |
| **Problem-solving** | Technology-driven solutions tailored to how each merchant actually works.              |

## Why it matters to you

When you represent Kurv, you're not selling a black box. You're offering a partner your merchants can trust — backed by real technology and real people. That's what makes the conversation easy.

{% hint style="info" %}
**Company:** Electronic Merchant Systems LLC d/b/a Kurv · 250 West Huron, #400, Cleveland, OH 44113 · (800) 726-2117 · [kurvpay.com](https://www.kurvpay.com)
{% 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/start-here/who-is-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.
