Payment creation
Create payment intents for checkout flows.
Developers · EURV API
Build With EURV.
Digital payments, built into your product. Integrate EURV into your website, application or platform through a developer-focused API.
REST-STYLE API
WEBHOOKS
SANDBOX
IDEMPOTENCY
SIGNED EVENTS
RESPONSE
Illustrative API shape — the final reference ships with the documentation.
Capabilities
Everything Payments. One API.
Ten building blocks cover the full payment lifecycle — from creation to reconciliation.
Payment requests
Request payments from customers by link or ID.
Transfers
Move EURV between eligible accounts.
Wallet services
Read balances and wallet state via API.
Transaction history
Query and filter every movement.
Webhooks
Receive real-time payment events.
Payment status
Track lifecycle from pending to settled.
Reconciliation
Match movements to references and reports.
Business accounts
Manage business-level EURV activity.
API authentication
Secure keys with scoped permissions.
From first call to live
Go Live in Six Steps.
A clear path from your first sandbox request to production traffic.
01
Developer account
Register and verify your developer profile.
02
API keys
Generate scoped sandbox keys in the dashboard.
03
Build in sandbox
Test payments and transfers — no real value moves.
04
Wire webhooks
Subscribe to events and verify signatures.
05
Go live
Request live access after review and checks.
06
Monitor & reconcile
Track status, uptime and settlement data.
API Reference
Reads Like a Spec.
Predictable resources, clear statuses and machine-readable errors. These examples show the shape of the EURV API.
- POST/v1/payments
- POST/v1/transfers
- GET/v1/transactions
- POST/v1/webhooks
- GET/v1/wallet/balance
- POST/v1/payment-requests
Illustrative examples — the final API reference is provided in the documentation.
POST/v1/payments
{
"amount": "250.00",
"currency": "EURV",
"reference": "ORDER-10294",
"description": "Hotel booking"
}
201 CREATED
{
"payment_id": "pay_9f3k2h8a",
"status": "pending",
"expires_at": "2026-08-14T18:30:00Z"
}
POST/v1/transfers
{
"amount": "120.00",
"currency": "EURV",
"recipient": "user_sarah",
"reference": "INV-2041"
}
200 OK
{
"transfer_id": "trf_7d2m4x9q",
"status": "settled"
}
GET/v1/transactions?reference=ORDER-10294
{
"data": [
{
"transaction_id": "txn_51ab77c0",
"amount": "250.00",
"direction": "credit",
"status": "settled"
}
],
"has_more": false
}
EVENTpayment.settled → your endpoint
X-EURVON-Signature: sha256=9f2c…d81a
{
"event": "payment.settled",
"payment_id": "pay_9f3k2h8a",
"amount": "250.00",
"reference": "ORDER-10294",
"timestamp": "2026-08-14T15:02:11Z"
}
ERRORmachine-readable, always
{
"error": {
"code": "insufficient_funds",
"message": "The account balance is insufficient for this transfer.",
"request_id": "req_8h2kd91z"
}
}
Environments
Test Without Moving Real Value.
Build and break things safely in the sandbox. Go live only after review — with keys that are clearly separate.
SANDBOX
Build freely.
Full API surface with simulated settlement. No real value moves — ever.
BASE URLhttps://sandbox.api.eurvora.com
API KEYsk_sandbox_4f9d…e21c
SETTLEMENTSimulated · instant
LIVE
Ship with confidence.
Production keys are issued after account review and eligibility checks.
BASE URLhttps://api.eurvora.com
API KEYsk_live_••••••••••••
ACCESSAfter review
Keys and URLs shown are illustrative. Real credentials appear only inside your developer dashboard.
Built for production
Security Is Part of the Contract.
The API is designed so safe integration is the default path, not the careful one.
HTTPS everywhere
All API traffic is encrypted in transit. Plain HTTP is refused.
Scoped API keys
Keys carry only the permissions each integration needs.
Rate limiting
Limits protect the network — with clear headers and responses.
Idempotency
Retry safely. Duplicate requests do not duplicate movements.
Webhook signatures
Verify every delivery before acting on it.
Server-side only
Financial operations belong on your backend — never in the browser.
Developer questions
Building — FAQs
Open a developer account. API keys are issued inside the developer dashboard. Availability may depend on eligibility and region.
Yes. A sandbox environment is provided for testing. No real value moves inside the sandbox. You can build and test freely before going live.
Requests are authenticated with API keys over HTTPS. Keys carry scoped permissions and should be kept server-side. Never expose API keys in client-side code.
Yes. Webhook deliveries include a signature header so your application can verify authenticity. Deliveries are retried automatically with exponential backoff.
Yes. Rate limits apply to protect the network. Details and response headers are published in the documentation, with clear 429 responses when limits are reached.
Yes. References, transaction history and reconciliation endpoints help you match payments to your own records. Every transaction carries a reference you control.
Ship EURV Payments.
From sandbox to production — one API, one ledger, full traceability. Join the developers already building on EURVON.