Build with AI
Already have an app? Ask your AI assistant to add payments.
What your customers will see.
01
Customer checks out
In your app, as it works today.
02
Your server asks Plinth
With the order's real total. Automatic, every time.
03
Plinth checkout opens
A clean page where they pick a network and pay.
04
Your app is told
A signed message. Your order flips to paid.
No payment link is made by hand and no product is set up in Plinth. Your app already knows what was bought and how much it costs; it just tells Plinth.
Three steps.
- 1
Connect your assistant
Add the Plinth MCP server with one URL and your key, or skip this and use the prompt. The server lets your assistant create and check payments, links, invoices and webhooks itself.
- 2
Ask in plain English
Paste the prompt for the kind of project you have. It tells the assistant to work inside your existing code.
- 3
Check four results
A real total is charged, the order turns paid from the webhook only, a forged webhook is rejected, a replayed one is ignored.
1. Connect your assistant (optional).
Works with any assistant that supports MCP over HTTP (Claude, Cursor, and others). The server URL is https://plinth-api.zerolayer.online/mcp. Send your secret key as a Bearer token; create a test key in your dashboard under Developers, API keys.
{
"mcpServers": {
"plinth": {
"url": "https://plinth-api.zerolayer.online/mcp",
"headers": { "Authorization": "Bearer sk_test_..." }
}
}
}claude mcp add --transport http plinth https://plinth-api.zerolayer.online/mcp --header "Authorization: Bearer sk_test_..."2. Paste the prompt for your project.
An existing shop with a cart or checkout.
Add Plinth USDC payments to THIS project. Do not create a new project and do not make payment links by hand.
This is an online store. The payment is created when the customer clicks the final pay or place-order button, with the cart total computed from the product prices stored on the server.
If a Plinth MCP server is connected, call get_integration_playbook first and follow it, and use create_payment / get_payment to test.
Otherwise read https://plinth.zerolayer.online/llms-full.txt and follow the playbook there.
Work in this order and tell me what you found before you change anything:
1. Find where an order, cart, booking or plan is created and where prices come from.
2. Add the server-side payment creation, the redirect to checkout_url, and the webhook route with signature verification.
3. Add PLINTH_API_URL, PLINTH_SECRET_KEY and PLINTH_WEBHOOK_SECRET to the project's env template (and document them there). Use test keys only.
4. Test it on a test network: a real order total is charged, the order flips to paid from the webhook only, a bad signature is rejected, a replayed event is ignored.
5. Finish with a short list: files changed, env vars to set, how to run the test.What is in the kit, and what is not yet.
- Available
MCP server (hosted)
One URL, your key in a header. 29 tools: payments, payment links, invoices, refunds, webhooks and reports, plus the integration playbook, a ready prompt and resources. It cannot change where money goes.
- Available
Plain-text docs for assistants
/llms.txt and /llms-full.txt, generated from the same playbook the MCP server serves.
- Available
Copy-and-paste prompts
One prompt, tuned for a store, a SaaS, a bot or bookings. Each ends with a checklist.
- Available
Test networks and sandbox
Try everything with test USDC. No real money moves.
- Planned
SDKs and framework starters
Not published. The REST API works from any language today.