> ## Documentation Index
> Fetch the complete documentation index at: https://docs-alpha.pepay.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Why Pepay

> Why Pepay exists, what it is, and what it delivers.

**Multi-chain payments for modern commerce - one integration, dollar-precise settlement, non-custodial by default.**

Pepay is the routing and settlement layer for AI and Web3 commerce, abstracting away chains, tokens, and settlement the same way Stripe abstracted away card networks.

## Why Pepay?

Payments should not stop at chain borders, but builders run into the same problems repeatedly:

* **Fragmented chains and tokens**: every new chain adds edge cases, tooling, and operational overhead.
* **Settlement ambiguity**: "\$49.00" is simple in Web2, but harder when value moves across tokens and chains with decimals, confirmations, and inconsistent standards.
* **Custody and risk tradeoffs**: many easy solutions rely on centralized custody, creating risk and compliance friction.
* **Embedded UX is brittle**: as commerce moves into apps, wallets, and AI interfaces, payments cannot depend on "send users to a wallet, hope they come back."
* **Real commerce is disconnected**: even when crypto payments work, turning that into real-world purchasing (inventory, fulfillment, receipts) is usually a separate problem.

Pepay exists because **the future of commerce is chain-agnostic and increasingly AI-driven**, and it needs payment rails that are as predictable as the systems merchants already use.

## What is Pepay?

Pepay's vision is to become the **universal, non-custodial settlement fabric** for AI agents and Web3 commerce. We support the payment patterns real businesses need (one-off, embedded checkout, subscriptions, and more) without forcing merchants to rebuild their existing stack.

In short: **Pepay is the adapter that makes every digital dollar usable across any chain, wallet, and commerce workflow.**

## What Pepay Delivers

### Core capabilities (live)

* **Multi-chain payments (one integration)**: build once, accept payments across supported chains and tokens through a unified API and SDK surface.
* **Dollar-precise settlement ("perfect to the dollar")**: price and reconcile in USD terms while Pepay handles multi-chain complexity underneath for predictable settlement.
* **Non-custodial by default**: merchants retain custody by default, reducing counterparty risk and simplifying the operating model.
* **Embedded payments**: payment flows that live inside your product experience (apps, checkout flows, AI interfaces) instead of bouncing users across wallets and browser hops.
* **Commerce API layer + extended commerce APIs**: Pepay is not only "send funds to an address." We attach payments to a merchant commerce API layer, including the ability to buy real products (for example, Amazon) with crypto through Pepay's commerce experience and APIs.

### In development

* **Seamless multi-chain subscriptions stack**: cross-chain recurring payments with fiat-precise billing behavior (trials, retries/dunning, and more) designed for subscription businesses and agentic commerce.

## Why Teams Choose Pepay

### 1) Settlement that matches how merchants operate

Teams do not want "close enough" settlement - they want invoice-like certainty (amounts, receipts, reconciliation). Pepay is built around dollar-precise settlement and merchant-friendly reconciliation.

### 2) Non-custodial by default

Custody is where risk concentrates. Pepay is designed so merchants retain custody by default, which keeps architecture cleaner and reduces operational surface area.

### 3) Embedded UX that fits modern products

Pepay is built for embedded payments, including AI-native commerce experiences where attention already lives and drop-off is expensive.

### 4) Payments that connect to real commerce

Most stacks stop at "accept crypto." Pepay goes further by connecting payment rails to a commerce API layer, including extended commerce flows like purchasing Amazon items with crypto.

### 5) Built to ship, not just demo

Pepay prioritizes real integrations and real flows - the product is designed for production environments, not just proof-of-concept checkouts.

## Pain Points - Solved by Pepay

| Pain Point                            | Typical Approach (Without Pepay)                            | With Pepay                                                                                            |
| ------------------------------------- | ----------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
| **Multi-chain acceptance**            | Integrate chain-by-chain, maintain brittle adapters         | **One integration** for multi-chain payments and commerce surfaces                                    |
| **Settlement ambiguity**              | Token decimals, price drift, reconciliation headaches       | **Dollar-precise settlement** and reconciliation-friendly semantics                                   |
| **Custody risk**                      | Processor custody or centralized wallets become the default | **Non-custodial by default** (merchant retains custody)                                               |
| **Embedded checkout**                 | Wallet redirects, browser hops, drop-off                    | **Embedded payments** designed for modern app and AI experiences                                      |
| **Fragmented regional rails**         | Use a different rail or provider for each region            | **One API** for stablecoin deposit and off-ramp flows across several regions                          |
| **Real-world product purchase**       | Payments are disconnected from commerce fulfillment         | **Extended Commerce APIs** (for example, buy Amazon items with crypto) attached to the merchant layer |
| **Recurring revenue / subscriptions** | "Subscriptions" are either custodial or not fiat-precise    | **Multi-chain subscriptions stack** built for fiat-precise recurring billing (in development)         |

## The Pepay Advantage

### One integration -> multiple payment surfaces

Pepay is designed so the same core rails can support:

* **Payments (now)**
* **Commerce checkout and purchasing (now)**
* **Subscriptions (building)**

### Designed for predictable operations

* **Precision**: dollar-denominated intent and clean reconciliation.
* **Safety**: non-custodial posture by default.
* **Composability**: built for embedded and programmatic payment flows (apps and agents).

### Unique wedge: commerce APIs, not just "payments"

Pepay pairs payment rails with a merchant commerce API layer, enabling crypto spending on real products, not just crypto transfers.

## Key Takeaway

Pepay turns fragmented multi-chain value transfer into simple, reliable payment and commerce flows:

* **One integration**
* **Dollar-precise settlement**
* **Non-custodial by default**
* **Embedded payments for modern apps and AI experiences**
* **A commerce API layer that unlocks real purchasing (for example, Amazon)**
* **Subscriptions stack in progress**

## Get API keys

API keys are created in the Pepay Dashboard (login required).

<Card title="Pepay Dashboard Login" icon="key" href="https://pepay.io/sign-in">
  Sign in to get API keys for server-to-server integrations.
</Card>

Need access or help onboarding? Email `support@pepay.io`.

## Environments (deployment vs network)

Pepay separates **where** you send requests from **which network** the request operates on:

* **Base URL** selects the deployment. Default for examples: `https://api-beta.pepay.io`.
* `environment=devnet|mainnet` selects the network context for endpoints that support it.

## API reference

<Columns cols={2}>
  <Card title="API Spec" icon="terminal" href="/api-spec/overview">
    SDK-scoped reference docs for Pepay endpoints.
  </Card>

  <Card title="OpenAPI" icon="file-code" href="/api-reference/openapi.json">
    Download the OpenAPI spec for SDK-supported routes.
  </Card>
</Columns>