Everything in a PayRam server
Driftpe provisions PayRam servers for you — each with its own API key, admin login, and webhooks.
Sign up is open; most teams integrate within minutes of creating a server.
One server at a time
Each server you create is a PayRam instance Driftpe provisions on its own. Add a second server when you need staging, another brand, or a separate product.
-
Independent provisioning per server
-
Delete a server to free capacity
-
Reduce capacity only after unused servers are removed
API key
When your server is ready, Driftpe gives you an API key scoped to that PayRam server. Integrate deposits, payouts, and status from your application.
-
Credentials per server
-
Shown in dashboard and email
-
HTTP API ready to use
Admin login
Set the PayRam login email when creating a server. We generate a temporary password, email it to you, and show it once in the dashboard—PayRam asks you to set a new password on first login.
-
One admin login per server
-
Full PayRam dashboard access
-
Credentials belong to your server only
Webhooks
Configure webhook endpoints on each server so your app receives payment and wallet events from that PayRam server.
-
Per-server endpoints
-
Reliable event delivery
-
Managed from the Driftpe dashboard
Developers & AI agents
Build on PayRam's HTTP API using the official payment documentation, or connect Cursor and other agents
via the PayRam MCP — both target the server Driftpe provisions for you.
See the full flow
Watch the hero animation: create a server, provision PayRam, and get API access in under a minute.
View animated walkthrough →