Unified Multi-Chain Gateway
Stop maintaining custom RPC nodes and fragile blockchain listeners. One standard REST API integration covers GRAM, USDT on TON, TRON, Base, and BSC.
Протокол
API Capabilities & Architecture
recv працює як прозорий middleware. Транзакції проходять напряму від клієнта до мерчанта, минаючи проміжні рахунки.
Cryptographic Webhooks
Payment status changes can trigger POST webhooks to your server. Payloads use HMAC-SHA256 signatures and timestamps so your backend can verify authenticity and apply replay controls.
Native Idempotency
Never credit a user twice for the same blockchain transaction. Our core protocol enforces strict idempotency, protecting your database from duplicate processing during network congestion or micro-forks.
Testnet & Sandbox Mode
Develop and test your integration safely using our Sandbox environment. Generate mock invoices and simulate blockchain confirmations without risking real capital.
Інтеграція
Безшовний флоу
Step 01
Випуск API-ключів
Генеруйте live_ ключі. Керуйте scopes для безпечної backend-інтеграції.
1
Step 02
Налаштування webhook
Налаштуйте callbacks із підписом HMAC-SHA256 для миттєвих сповіщень.
2
Step 03
Автоматизована обробка
Наші watchers відстежують транзакції 24/7 і автономно підтверджують платежі.
3
Реалізація
Готово до продакшну за лічені хвилини.
Безшовно інтегруйте наш протокол у ваш поточний workflow.
// Create Invoice via recv API
const res = await fetch("https://api.recv.money/v1/invoices", {
method: "POST",
headers: { "X-API-Key": "live_..."},
body: JSON.stringify({
title: "Order #99",
base_amount_usd: "29.00",
payable_network: "TON"
})
});
const inv = await res.json();Architecture
Developer Technical Specifications
High-performance primitives for backend integration.
- API Protocol
- RESTful JSON over HTTPS
- Authentication
- Bearer Token (API Keys)
- Webhook Security
- HMAC-SHA256 Signatures
- Rate Limits
- Up to 50,000 requests per month
Security & Compliance
API Security & Reliability
Security is implemented at the transport and application layers. API credentials are stored as hashes. Failed webhook deliveries are queued for retries according to the active plan, and integrations must remain idempotent because deliveries can repeat.
Built for Automation Engineers
Engineered specifically for backend developers building the next generation of decentralized applications, SaaS billing engines, and automated digital fulfillment systems.
- ✓SaaS founders implementing automated recurring crypto billing without fiat processors.
- ✓Web3 game developers needing instant, reliable in-game currency top-ups via TON, Base, or BSC.
- ✓Discord and Telegram bot creators building paid, automated community access layers.
- ✓Digital goods distributors that need signed webhook-driven fulfillment.
FAQ
Frequently Asked Questions
When a customer initiates a transfer, our Watchers monitor the respective blockchain. Once the transaction reaches the required confirmations, recv fires a JSON payload via HTTP POST to your pre-configured endpoint with the invoice ID, amount, and TX hash.
recv uses redundant RPC access for supported networks. If a public node drops, we fail over to backup providers. During congestion, watchers maintain state and deliver the webhook when the payment is finalized on-chain.
Idempotency ensures that no matter how many times a specific API request or webhook is retried (due to network drops or client errors), the end result is the same. In crypto, this is vital to prevent 'double-spending' or granting a user a premium subscription twice for a single blockchain transaction.
recv API utilizes a smart-matching protocol rather than generating unique wallet addresses per invoice (which is expensive and difficult to sweep). We use mathematically unique decimal suffixes (e.g., 100.000123 USDT) or network-native memos (on TON) to map a single incoming transaction on your master wallet to a specific user invoice instantly.
Currently, we provide a heavily documented, language-agnostic RESTful API that can be consumed by any modern HTTP client (Axios, Fetch, Requests). Official SDKs for TypeScript/Node.js and Go are actively in development.
Every webhook includes an 'X-recv-Signature' header. You must use your secret Webhook Key to compute an HMAC-SHA256 hash of the raw request body. If your computed hash matches our header, the payload is authentic and untampered.
We do not hard-block your API if you hit a spike. You will receive an automated alert via email and Telegram as you approach the limit (80% and 100%). Overages may be billed at a nominal rate, or you can seamlessly upgrade to the Business plan.
Yes. Developer plan subscribers have access to prioritized email support and a dedicated developer community channel where our core engineers actively assist with architecture design and debugging.
DEVELOPER PLAN
Доступ
29 $
на місяць
Необмежений обсяг. Фіксована місячна оплата.
0% TURNOVER FEESNON-CUSTODIALINSTANT PAYOUTS