PAYIN DOCUMENTATION

From first request
to a checked payment.

Choose the product you operate. Current PayIn QR and Link receive USDC to your wallet. PayIn Open is a separate gateway you deploy and run yourself.

PayIn QR / Link

Wallet preparation, creation, management access and payment confirmation for the current hosted product. No merchant account balance is created; a business must check the payment result before fulfillment.

Getting started with PayIn

Prepare a receiving wallet, create a QR or payment link, and check a completed payment.

Create QR codes and payment links with the API

The current PayIn link creation request, returned URLs and handling of private management access.

Payment notifications and fulfillment

Verify payment notifications, reconcile uncertain results and keep fulfillment idempotent.

PayIn Open reference

These complete guides describe an independent self-hosted system: operator credentials, address pools, order and deposit services, monitoring and webhook integration. They do not describe the current hosted QR/Link API. Historical Cloud / Pro onboarding is retired; use these references with the Open version you actually run.

English reference

Deposits API Orders API API Reference Order Payment Example Address Management Address Pool Setup AI-Assisted Deployment API Integration Deposit Service Introduction to PayIn Order Payment Service Payment Links Quick Start with MCP Server Security Best Practices Supported Networks Supported Tokens Testnet vs Mainnet Webhooks PayIn Open

中文自托管参考

充值 API 订单 API API 参考订单支付示例地址管理地址池设置 AI 辅助部署 API 集成充值服务介绍订单支付服务支付链接通过 MCP 服务器快速开始安全最佳实践 Open 部署中的网络配置 Open 部署中的代币配置测试网 vs 主网 Webhooks PayIn Open

Keep payment and delivery separate.

A callback, return URL or wallet signature is not sufficient evidence that an order should be fulfilled. Verify persisted payment records and keep your own fulfillment action idempotent. Refunds are separate transfers arranged with the customer.

Read notification and fulfillment guidance →