λ.digital

Accept crypto payments with a single QR code

Multiple cryptocurrencies, multiple chains — USDT, USDC on BSC, Ethereum and Tron. Add recurring subscriptions just like in the fiat world.

pay.λ.digital

Scan to pay

Any crypto, any chain

USDTUSDC

How it works

From signup to receiving crypto in four steps.

01

Add your wallets

Register your BSC, Ethereum, or Tron addresses once in the dashboard.

02

Create a payment

One API call with amount, chain, and token. Get back a hosted checkout URL.

03

Customer pays

Redirect your customer to the checkout. They scan the QR and send crypto.

04

Funds arrive

We detect the transfer on-chain and fire a webhook. Funds land directly in your wallet.

Plans

Choose how much control you want over your payments.

Tier 1Free · No fees

Self-custody

You own your addresses. Funds go directly to your wallets — no intermediary, no our layer.

  • Add your own crypto addresses
  • BSC, Ethereum, Tron
  • USDT & USDC
  • Webhook notifications
  • 0% fee, always
  • Dashboard — full control over your payments
Tier 20.1% fee

Auto-convert

Add only your USDT address. All incoming payments in any crypto are automatically converted to USDT and forwarded to you.

  • Single USDT payout address
  • Auto-conversion from any crypto
  • Recurring subscriptions
  • Webhook notifications
  • 0.1% per transaction
  • Dashboard — full control over your payments

Not available yet — coming soon

Security

Built non-custodial from day one. Your funds, your keys.

Non-custodial

Funds go directly to your wallets. We never hold or touch your crypto at any point.

HMAC-signed webhooks

Every webhook is signed with your per-merchant secret. Verify the signature on your end.

Hashed API keys

API keys are bcrypt-hashed before storage. The plain key is shown once and never saved.

Idempotent confirmations

Payments confirm exactly once, deduplicated by txHash. Double-delivery is impossible.

Rate limiting

All public API endpoints are rate-limited per API key via Redis to prevent abuse.

Outbound-only watchers

Chain watchers make outbound RPC calls only. No inbound ports are exposed.