> For the complete documentation index, see [llms.txt](https://docs.pepay.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pepay.io/getting-started/key-features.md).

# Key Features

***

## Multi-Chain Model

Pepay supports multiple blockchain networks (e.g., Ethereum, Solana, BASE), allowing AI agents and merchants to transact in their preferred chain. This **polyglot** approach future-proofs Pepay against shifting market trends—adding new chains is as simple as plugging in a new module.

**Why it matters:**

* **Seamless Cross-Chain Payments**: Accept ETH, SOL, and beyond, all under one unified interface.
* **Future-Proof**: Easily adapt to emerging L2s or new blockchains without overhauling your payment logic.

***

## Self-Custody Architecture

Pepay is **non-custodial** by design, ensuring that merchants and AI agents maintain full control over their private keys. There are no third-party custodians—Pepay simply provides the payment rails. Merchants may use the KMS encrypted custodial wallets or operate with their own wallets

**Why it matters:**

* **Security & Ownership**: Your wallet, your keys. No middleman controlling your funds.
* **Trustless Transactions**: Reduce counterparty risk and remove friction in on-chain payments.

***

## Developer Testnet

Test new payment flows and integrations without risking real funds. Pepay offers a **dedicated testnet** environment to let you break things in a sandbox before going live.

**Why it matters:**

* **Safe Experimentation**: Build and iterate faster without incurring costly on-chain fees.
* **Frictionless Onboarding**: Lower the barrier to entry for developers looking to integrate Pepay into AI agent workflows or merchant platforms.

***

## Partial Payment System

Pepay’s partial payment feature enables you to accept or send payments in increments, rather than settling an invoice in full.

**Why it matters:**

* **Flexible Billing**: Allow your customers or AI agents to pay as they go.
* **Improved Accessibility**: Smaller amounts lower the commitment threshold and widen your user base.

***

## Time-Bound Invoicing

Set an **expiry period** for each invoice, ensuring payments are made within a specific window. If the deadline passes, the invoice expires automatically.

**Why it matters:**

* **Fraud Prevention**: Close payment channels before bad actors exploit them.
* **Revenue Protection**: Keeps payment expectations clear for both AI agents and end users.

***

## Multi-Platform Support

Pepay integrates with popular communication tools and AI frameworks, making it easy to embed payments where conversations and collaborations happen.

**Building Support for :**

* **Multiple AI Agent Models** (AI16z, 8n8, PyDantic, ARC, Virtuals)
* **Discord, Twitter, Telegram** connectors
* **Document Ingestion & Retrieval**: Pepay integrates with AI workflows that require data ingestion and context retrieval for transactions or invoice generation. This could include emails, addresses, or customer information.&#x20;

***

## Observability & Logging

Pepay provides logs, alerts, and health checks to ensure you have full visibility into your payment flows.

**Why it matters:**

* **Real-Time Monitoring**: Quickly diagnose issues or failed transactions.
* **Scalability**: Track metrics as your user base or number of AI agents grows.

***

## Putting It All Together

Pepay doesn’t just handle payments; it **empowers** AI agents, merchants, and users to transact seamlessly in an evolving multi-chain world. Whether you’re building an autonomous AI service, an on-chain social casino, or a retail crypto gateway, Pepay’s flexible, non-custodial, and developer-friendly architecture has you covered.

**Next Steps**

<table data-view="cards"><thead><tr><th></th><th></th><th data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Architecture &#x26; Design</strong></td><td>dive deeper into the tech</td><td><a href="/pages/QI4T6YqOuJ7rL2BrKiqm">/pages/QI4T6YqOuJ7rL2BrKiqm</a></td><td><a href="/files/53PF6z17zvkCTjyObptE">/files/53PF6z17zvkCTjyObptE</a></td><td></td><td></td></tr><tr><td><strong>Getting Started</strong></td><td></td><td></td><td><a href="/files/2ojdeD9NsYaKfuqi2FwA">/files/2ojdeD9NsYaKfuqi2FwA</a></td><td></td><td></td></tr><tr><td><strong>Check out our SDK</strong></td><td>get started with app integrations</td><td></td><td><a href="/files/GN9bh7yb1fWtIEOXDbk1">/files/GN9bh7yb1fWtIEOXDbk1</a></td><td></td><td><a href="/pages/CyH2xJQs9yWJ1S8BYNav">/pages/CyH2xJQs9yWJ1S8BYNav</a></td></tr></tbody></table>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.pepay.io/getting-started/key-features.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
