Webhooks are optional but recommended for tracking transaction status in real-time.
Overview
Webhooks allow you to receive automatic notifications when order events occur. Configure them in your Rampnow Partner Dashboard to stay updated on transaction statuses without polling.Configuration Steps
Access API Hub
Navigate to the API Hub in your Rampnow Partner Dashboard.
Order Events
Your webhook will receive notifications for these order status changes:Processing
Order is being processed
Completed
Order successfully completed
Failed
Order failed or was cancelled
Implementation Example
Here’s a simple Flask server that receives webhook notifications:Webhook Payload Schema
Find different tabs below for each product wise webhook formats.
Field Descriptions
| Field | Type | Description |
|---|---|---|
createdAt | string | Webhook event creation timestamp (ISO 8601) |
eventUid | string | Unique webhook event identifier |
eventType | string | Event type (e.g., orders.processing, orders.completed, orders.failed) |
orderUid | string | Unique Rampnow order identifier |
externalOrderUid | string | External order reference |
createTime | string | Order creation timestamp (ISO 8601) |
updateTime | string | Last update timestamp (ISO 8601) |
partnerGeneratedUid | string | Your internal order ID |
orderType | string | Transaction type: buy or sell |
orderStatus | string | Current status: processing, completed, or failed |
paymentStatus | string | Payment settlement status |
paymentMode | string | Payment method used (e.g., card, google_pay) |
srcCurrency | string | Source currency code |
srcChain | string | Source blockchain or fiat |
srcAmount | number | Amount in source currency |
dstCurrency | string | Destination currency code |
dstChain | string | Destination blockchain or fiat |
dstAmount | number | Amount in destination currency |
walletAddress | string | Recipient wallet address |
walletAddressTag | string | Optional wallet tag/memo |
transactionHash | array | Blockchain transaction hash(es) |
Best Practices
Security
Security
- Use HTTPS endpoints only
- Validate webhook signatures (if provided)
- Implement rate limiting on your endpoint
- Log all incoming webhooks for debugging
Reliability
Reliability
- Return
200 OKquickly (process async if needed) - Implement idempotency using
orderUid - Handle duplicate webhook deliveries gracefully
- Set up monitoring and alerts for failures
Error Handling
Error Handling
- Always respond with status codes
- Implement retry logic on your side if needed
- Store failed webhooks for manual review
- Contact support if webhooks stop arriving
Testing Your Webhook
Use Tunneling Tool
Use tools like ngrok to expose your local server: