The current payment kit is based on Nuwa’s Payment Channel solution. We are working on integrating the x402 protocol to make it more flexible and scalable. Check out our demo with xNUWA.
How It Works
Under the hood, Nuwa implements unidirectional payment channels with on-chain settlement:- Off-chain receipts (SubRAV) are exchanged per request between the Nuwa Client and the AI services
- Receipts are issued by the payee (the service provider) and signed by the payer’s DID key (which is managed by the Nuwa Client, authorized by the user), and then sent back to and collected by the payee
- The service providers can take the signed receipts to claim the payment on-chain
Client Integration (HTTP)
Use@nuwa-ai/payment-kit to automatically manage payment channels and attach payment receipt headers:
MCP Integration
For Model Context Protocol tools, the same payment channel primitives are available. The Nuwa client includes a payer-side MCP client; services can opt-in using the server adapter:Wallets & Assets
Nuwa channels currently settle on Rooch using BCS-encoded receipts. Assets are identified byassetId (e.g., 0x3::gas_coin::RGas). The client can manage deposits, sub-channel authorization for multiple devices, and cooperative close.
Custodial onboarding flows are available via CADOP (see Identity). You can start with a passkey and still pay cryptographically from your DID.

