Truly non-custodial
ArgusPulse never holds, moves, or controls funds. HD addresses derive from your extended public key only. Your private key never leaves your infrastructure, so there is no settlement risk and no counterparty exposure.
Deposit monitoring, an HD payment gateway, signed webhooks, real-time SSE, and AML/OFAC screening. One API. Flat fee, 0% of payment volume.
Free pilot for the first few merchants, in exchange for feedback. No volume fees, ever.
// HMAC-SHA256 verified · delivered with retries + DLQ { "event": "deposit.confirmed", "network": "TRON", "asset": "USDT", "amount": "1500.00", "address": "TLa2f6...9xQk", "confirmations": 20, "txHash": "9c3f...e71a", "screening": { "status": "clear" } }
Monitors the chains your customers actually pay on
Six things that make ArgusPulse different from a payment gateway and from a raw node provider.
ArgusPulse never holds, moves, or controls funds. HD addresses derive from your extended public key only. Your private key never leaves your infrastructure, so there is no settlement risk and no counterparty exposure.
Predictable SaaS pricing, whatever your throughput. Not 0.5% like NOWPayments, not 1 to 2% like Coinbase Commerce or BitPay. High-volume and thin-margin merchants keep every cent.
EVM networks, TRON with native USDT TRC-20, Solana, and Bitcoin. Reorg-safe persistent cursors and configurable confirmation thresholds on every chain.
Deposit monitoring, HD payment gateway, HMAC-signed webhooks with DLQ and replay, a real-time SSE stream, and AML/OFAC screening. No stitching together four vendors.
Deploy in your own VPC or on-prem for full data sovereignty. Managed SaaS, managed dedicated, or self-hosted. A single Docker image, no microservice sprawl.
Every detected counterparty is screened automatically against a configurable sanctions and blocklist, with the OFAC SDN seed included. Alerts surface in the dashboard or over webhook, so basic compliance does not need a separate vendor.
Blockchain notification infrastructure versus crypto payment gateways. ArgusPulse sits at the intersection.
| Capability | ArgusPulse | Tatum | Alchemy / QuickNode | NOWPayments | Coinbase / BitPay |
|---|---|---|---|---|---|
| Signed deposit/withdrawal webhooks | HMAC + DLQ | ✓ | ✓ | · | · |
| Reorg-safe persistent cursor | ✓ | Partial | ✓ | · | · |
| HD-address payment gateway | ✓ | · | ✗ | ✓ | ✓ |
| Non-custodial | Core | ✓ | ✓ | Custodial | Custodial |
| AML/OFAC screening built-in | ✓ | Partial | ✗ | Partial | ✓ |
| Self-host / on-prem | ✓ | ✗ | ✗ | ✗ | ✗ |
| Pricing | Flat SaaS, 0% volume | Credits | Compute units | 0.5% of volume | 1 to 2% of volume |
| Real-time SSE stream | ✓ | Partial | ✓ | ✗ | ✗ |
| Multi-language SDKs | TS · Python · PHP | TS/Py/Java/.NET | TS/Py | Plugin | Plugin |
Three official SDKs. Pick your stack and ship in an afternoon.
# install npm install @arguspulse/sdk // verify a webhook and stream deposits import { ArgusPulse } from "@arguspulse/sdk"; const argus = new ArgusPulse({ apiKey: process.env.ARGUS_KEY }); argus.webhooks.verify(payload, signature); for await (const ev of argus.deposits.stream()) console.log(ev);
# install (sync + async clients included) pip install arguspulse # verify a webhook from arguspulse import ArgusPulse argus = ArgusPulse(api_key=os.environ["ARGUS_KEY"]) argus.webhooks.verify(payload, signature) for ev in argus.deposits.stream(): print(ev)
# install (Guzzle 7, Laravel example included) composer require arguspulse/sdk // verify a webhook use ArgusPulse\Client; $argus = new Client(apiKey: getenv("ARGUS_KEY")); $argus->webhooks()->verify($payload, $signature);
Because ArgusPulse never holds, controls, or transmits customer funds, it sits outside the definitions that trigger Money Services Business registration or equivalent licensing in most jurisdictions. You integrate an infrastructure API, not a money transmitter.
| Region | Framework | Non-custody relevance |
|---|---|---|
| USA | FinCEN MSB / CFTC | Non-custodial infrastructure APIs typically outside the MSB definition |
| EU/EEA | MiCA (live Jul 2026) | No CASP authorisation required for pure monitoring infrastructure |
| UK | FCA crypto-asset regime | No funds transmission, so a reduced registration surface |
| UAE | VARA / CBUAE | Non-custodial analytics and monitoring not classified as VASP activity |
| Global | FATF guidance | Non-custodial software not a VASP under the FATF R.15 interpretation |
This is informational, not legal advice. Consult qualified counsel for your jurisdiction and use case.
Early access is open. The first few merchants get a free pilot in exchange for feedback. You will talk to the person building it.