Create context
Describe the order, session, evidence, or agent task separately from payment facts.
Request payment without taking control of the wallet.
Create a standard Payment Request, attach business context, let the customer review and sign locally, then follow the result through a consistent status model.
Preview pilots begin with sandbox and test flows. Live merchant onboarding, pricing, settlement claims, and regional availability are not yet open.
A clearer boundary
Your system requests. The customer's wallet decides.
VelarumPay keeps merchant systems, agent systems, and wallet signing responsibilities distinct.
Request payment
Send an exact amount, asset, network, recipient, expiry, and idempotency key.
User approves
The customer reviews risk and transaction facts before signing on their device.
Observe status
Your integration reads deterministic status and events without gaining signing authority.
Integration paths
One protocol, several ways to connect.
Choose the surface that fits your application. Every supported path converges on velarum.payment_request.v1.
Integrate directly with the Platform API.
Use the published OpenAPI contract for pairing, connections, transaction contexts, Payment Requests, status, and events. Server-side services validate scopes, expiry, exact amounts, and idempotency.
Use typed helpers around the same contracts.
The JavaScript SDK packages pairing, validation, context creation, Payment Request creation, and status polling into a smaller client surface. The API and JSON Schema remain the source of truth.
Give agents request tools, never wallet keys.
The MCP server and connectors expose a deliberately small tool set for pairing, creating context, requesting payment, and reading status. They cannot approve, sign, export keys, or bypass wallet review.
Pilot fit
Start where the control model matters.
Early pilots should have a clear user, requester, payment reason, and testable approval flow.
Merchant checkout
Evaluate wallet pairing and payment requests from an order flow without asking the merchant to handle user keys.
Trusted applications
Connect software that needs user-approved payments and auditable status without custodial authority.
AI agent workflows
Let a local or hosted agent propose a purchase while preserving deterministic validation and human approval.
What your integration must preserve
Clear facts, limited scopes, and observable state.
A good integration makes it easy for the wallet user to verify the request and easy for your team to diagnose the outcome.
- Exact decimal amount strings and explicit asset identity
- Network, recipient, fee, expiry, and idempotency controls
- Transaction context separated from immutable payment facts
- Scopes limited to the capabilities your application actually needs
- Safe handling of connection tokens and deterministic error states
- No private keys, seed phrases, or signing material in your service
Selected Preview pilots
Tell us what you want to evaluate.
The first conversation should establish your use case, integration surface, intended user approval flow, and test environment. A pilot request does not approve production access.
No sensitive dataDo not include API keys, wallet addresses, seed phrases, private keys, production customer data, or signing material.
Prefer to inspect the contracts first?
The developer subdomain contains the Quickstart, REST surface, protocol schemas, and MCP guide.