Build your
payment flow.
From your first payment link to a complete integration. Everything you need to build with FlowPay, in one place.
A few commands. Your first payment request.
CLI quickstartConnect your AI clientBring payment tools to your agent workspace.
MCP guideBuild it your wayYour interface. FlowPay under the hood.
API referenceInstall. Sign in. Create a payment.
01 — 03Install the CLI
Start with the FlowPay command line. The public package includes the Node.js SDK, so you can move from terminal to code when you are ready.
npm install -g --prefer-online https://api.pixuno.xyz/downloads/flowpay-cli-0.1.7.tgz
flowpay --helpUse Node.js 20 or later and an EVM settlement wallet. Your wallet address starts with 0x.
Make yourself at home
Create an account from your terminal. The CLI wizard collects your business name, recovery email and settlement wallet, then creates a device key and signs you in automatically. There is no password, email code or browser approval.
flowpay register| Field | What you need |
|---|---|
| Business name | The name your customers recognize. |
| Device key | Generated locally and used automatically for sign-in. |
| Email address | Your recovery contact. Recording it does not verify ownership. |
| Settlement wallet | Your EVM wallet address, starting with 0x. |
Already registered?
Sign in automatically using the key on the device where you registered.
flowpay loginRun flowpay init for first-time setup. Existing browser accounts may use flowpay device. flowpay logout removes the session and keeps your device key for future sign-in.
Your first payment request
Request 20 USDC on Ethereum Sepolia. The CLI returns a payment ID, deposit address, and checkout URL to share with your customer.
flowpay request 20 usdc ethChoose an amount, asset, and network.
Send the checkout URL to the payer.
Wait for the verified payment receipt.
The CLI alias eth refers to Ethereum Sepolia testnet. Use monad for Monad Testnet (chain ID 10143) and MON for its native coin. For example: flowpay request 0.01 mon monad. Use the asset and network displayed in the payment request.
Keep the command in your workflow
| Option | What it does |
|---|---|
--no-open | Creates the request without opening a browser. |
--no-wait | Returns the request without waiting for payment. |
--json | Returns structured output for your application. |
Use the returned payment ID to pick up monitoring at any time.
flowpay payment wait PAYMENT_IDGive your agent payment tools
Create requests, share checkout URLs, and monitor payment state with predictable JSON output. The payer sends the transfer from its wallet.
flowpay request 20 usdc eth --json
flowpay payment status PAYMENT_ID --json
flowpay payment wait PAYMENT_ID --jsonSet FLOWPAY_CONFIG_DIR to isolate each agent's approved credentials. Keep credentials in configuration, outside prompts and logs.
Connect your AI workspace
Use FlowPay from a compatible remote MCP client. Add the hosted connector URL, then authorize the payment tools through your FlowPay account.
https://mcp.pixuno.xyz/mcp- Add the connector
Paste the server URL into your client's remote MCP settings.
- Sign in to FlowPay
Follow the authorization page and enter your email sign-in code.
- Review the permissions
Approve scoped access through OAuth with PKCE. Manage connected apps in Developers.
Remote connector support and setup vary by client and plan.
Your product. Our payment API.
Create payment requests from your backend. Authenticate with your merchant API key and send an idempotency key to prevent duplicate requests.
/v1/paymentsCreate a paymentcurl https://api.pixuno.xyz/v1/payments \
-H "Content-Type: application/json" \
-H "x-flowpay-api-key: $FLOWPAY_API_KEY" \
-H "Idempotency-Key: order-1042" \
-d '{
"amount": "20",
"asset": "USDC",
"chain": "ethereum_sepolia",
"reference": "order-1042"
}'The response includes id, address, checkout_url, and status. Share the checkout URL with your customer.
/v1/payments/:idRead payment statecurl https://api.pixuno.xyz/v1/payments/PAYMENT_ID \
-H "x-flowpay-api-key: $FLOWPAY_API_KEY"Create and store merchant credentials in Developers. API keys belong in your server environment.
Let payment events come to you
Register an HTTPS endpoint to receive signed payment lifecycle events. Subscribe to the events your application needs.
curl https://api.pixuno.xyz/v1/webhooks \
-H "Content-Type: application/json" \
-H "x-flowpay-api-key: $FLOWPAY_API_KEY" \
-d '{
"url": "https://your-app.com/webhooks/flowpay",
"events": ["payment.completed", "payment.failed"]
}'| Event | When to use it |
|---|---|
payment.detected | A transfer has been detected. |
payment.confirmed | The payment has reached confirmation. |
payment.completed | The payment workflow is complete. |
payment.failed | The payment workflow failed. |
Verify the signature before handling an event and process repeated deliveries idempotently. Manage endpoints in Webhooks.