# PayArrive

> Merchant APIs and MCP for BSC official USDT. Reading documentation does not activate a merchant or execute API calls.

API version: 0.1.0-alpha
Content revision (SHA-256): 9cea670b4c60f3a95f3bc34129a944b60c0115748e6c805adbb1251d795a80f7
Example revision (SHA-256): c7601fe3434980d40e1e3f086b5549da98b6632015fd047cc122919db816a7a7

## Documentation

- [Merchant guide](https://payarrive.com/docs/merchant-guide.md): Trusted backend identity, sessions, integer amounts, cursor recovery and unique credit.
- [Merchant OpenAPI](https://payarrive.com/docs/merchant-openapi.yaml): Five server-side operations, with schemas and synthetic examples.
- [SDK quickstart](https://payarrive.com/docs/#sdk-quickstart): Install @payarrive/merchant and call all five API operations.
- [SDK and MCP package](https://payarrive.com/downloads/payarrive-merchant-0.1.0.tgz): Locally installable version 0.1.0 artifact, including the payarrive-mcp command.
- [Business MCP](https://payarrive.com/docs/#merchant-mcp): Codex stdio and authenticated HTTP configurations, exact tool inputs and scoped Server Key authentication.
- [Runnable example](https://payarrive.com/docs/example/README.md): Seven source files; synthetic default and explicit real API mode, both using an isolated local PostgreSQL example ledger.
- [Documentation MCP](https://payarrive.com/docs/#documentation-mcp): Three public read-only tools, without merchant credentials.
- [Rendered guide](https://payarrive.com/docs/): The same canonical guide with stable section links.

Start with the guide and then the merchant OpenAPI. Keep Server Keys in the merchant backend or authorized MCP host environment, never model arguments. Business MCP uses scoped, revocable Server Keys; document lookup has no business authority. Treat checkout URLs and client tokens as sensitive short-lived capabilities. Download and remote endpoint availability require an actual installation check; this index makes no host compatibility or deployment claim.