← Back to home

About Paychainly

Paychainly is crypto payment infrastructure built for developers who need to accept USDT on BNB Smart Chain — without complexity, without custody risk, and without opaque settlement windows.

Our story

Paychainly started as an internal tool. We were building a marketplace that needed to accept stablecoin payments from customers around the world. Every existing solution required either handing over custody of funds to a third party, accepting weeks-long settlement delays, or integrating a brittle library that broke every time the RPC provider had downtime.

So we built our own. A lightweight payment listener on BNB Smart Chain, HD wallet derivation for unique deposit addresses, automatic sweeping to a master wallet, and HMAC-signed webhooks so our backend could trust the incoming events. It worked. Other developers asked how we did it.

We productised it as Paychainly. The core principle has never changed: your funds go directly to your wallet, we only provide the infrastructure to detect, route, and notify.

By the numbers

99.98%

Uptime SLA

< 6s

Avg. detection time

30+

API endpoints

10+

Supported languages

Our mission

Make blockchain payments as simple and reliable as traditional payment processing — without the intermediaries.

The crypto payment experience for merchants today is fractured. Most solutions are either overly complex (run your own node, manage your own keys, write your own sweep logic) or require trusting a custodian with your funds.

Paychainly occupies the space in between: we handle the infrastructure complexity — real-time block scanning, RPC failover, nonce management, gas top-ups, webhook delivery retries — while you keep full ownership of every dollar that comes in.

What we stand for

Developer-First

We built Paychainly for engineers. Every API response is predictable, every webhook is signed, every error message is actionable. We write the docs we wish we had.

Transparency

No hidden fees. No opaque settlement periods. Every satoshi is accounted for on-chain. You can verify every transaction independently without trusting us.

Reliability Over Features

We ship fewer things but make them bulletproof. Multi-RPC failover, idempotent job processing, and automated backfill mean your payments work even when infrastructure doesn't.

Zero Custody

We never hold your funds. HD wallet derivation means each deposit address is yours. Sweep happens in seconds. Your master wallet is always in your control.

How it works

When you call POST /api/v1/addresses/generate, Paychainly derives a unique BEP-20 deposit address from your HD wallet using a BIP-44 derivation path. This address is yours — we never have the private key.

Our block scanner watches BNB Smart Chain in real time, typically detecting deposits within 6 seconds of on-chain confirmation. When a matching Transfer event is detected, we fire a signed webhook to your endpoint and begin the sweep process: BNB gas top-up from the gas wallet, then USDT transfer to your master wallet. The whole pipeline — from block confirmation to funds in your master wallet — typically completes in under 30 seconds.

If any step fails — RPC timeout, gas spike, webhook delivery error — BullMQ retries the job with exponential backoff. Nothing falls through the cracks.

The team

Paychainly is built by a small team with backgrounds across payments infrastructure, distributed systems, and blockchain engineering. We're remote-first and obsessed with reliability.

⚙️

Engineering

Backend engineers with deep experience in distributed systems, blockchain infrastructure, and payment processing at scale.

🛒

Product

Former merchant operators and payment integrators who understand what it takes to get crypto into production.

🔐

Security

Security researchers focused on key management, webhook signing, and safe fund handling across a non-custodial architecture.

Security

Security is not a feature — it's a constraint. Paychainly was designed around the principle that the worst-case scenario for a crypto payment platform is losing user funds. Every design decision is evaluated through that lens.

  • Non-custodial architecture — private keys never leave your environment. We derive addresses but cannot move funds.
  • HMAC-SHA256 webhook signing — every event is signed with your webhook secret. Replay attacks are prevented by timestamp validation.
  • AES-256 key encryption — withdrawal wallet keys are encrypted at rest before being stored in the database.
  • Idempotent transaction processing — unique constraints on txHash ensure the same deposit can never be double-credited.
  • Rate limiting + JWT authentication — all API endpoints are protected. Admin and merchant scopes are fully separated.

If you discover a security vulnerability, please contact us at security@paychainly.com. We take all reports seriously and respond within 24 hours.

Get in touch

Whether you're a developer evaluating Paychainly for your next project, a merchant looking to add crypto checkout, or a company with enterprise volume requirements — we'd love to hear from you.

Contact us →support@paychainly.com