CryptoBot vs Wallet Pay for Telegram: Merchant Comparison

RT
recv Teamrecv editorial and engineering team · updated June 17, 2026
alt

The surge of Telegram Mini Apps, automated bots, and paid subscription communities has turned the messaging platform into a thriving hub for digital commerce. However, many merchants integrating crypto checkouts face a recurring challenge: high transaction fees, unpredictable compliance freezes, and complex regional restrictions. Selecting the right payment processor directly impacts your business's profit margins, operational security, and user experience.

Two of the most prominent legacy names in the Telegram ecosystem are CryptoBot (specifically its merchant API, Crypto Pay) and Wallet Pay (the custodial payment system linked to Telegram’s native @Wallet). Both have processed millions in transaction volume, but their custodial structures introduce distinct hurdles for scaling merchants. In contrast, emerging architectures offer a non-custodial, zero-percent turnover alternative designed specifically for independent developers and SaaS founders.

This detailed comparison of CryptoBot vs Wallet Pay explores how they stack up against the modern architecture of the non-custodial crypto payment gateway built by recv, helping you make an informed decision for your Telegram store or bot.

Disclaimer: This comparison is for informational and educational purposes only and does not constitute financial or legal advice. Non-custodial systems do not remove a merchant's legal compliance obligations in their respective jurisdictions.


The Core Differences: Custodial Bottlenecks vs. Non-Custodial Freedom

To evaluate these platforms, you must first understand the fundamental divide in how they handle your money: Custody.

Custodial Gateways (CryptoBot & Wallet Pay)

When a customer pays you through CryptoBot or Wallet Pay, the cryptocurrency is not sent directly to your private wallet. Instead, it enters the provider’s custodial system.

  • The Process: The gateway collects the funds, updates your internal balance sheet, and holds the assets in their massive multi-sig hot wallets.
  • The Risk: Because they hold custody of your funds, they act as financial intermediaries. If their compliance algorithms flag a customer’s transaction, or if regulatory pressures shift, your entire balance can be frozen without warning. To actually secure your earnings, you must manually initiate a withdrawal, paying variable on-chain network fees and waiting for processing times.

Non-Custodial Gateways (recv)

A non-custodial payment gateway functions entirely as a secure ledger monitor rather than a digital vault.

  • The Process: For every payment request, a real-time blockchain watcher monitors public ledgers for a matching transaction (using amount, memo, tx hash, or unique time windows). Once detected, the system immediately dispatches an HMAC-SHA256 signed webhook to your server.
  • The Security: Because the recv payment gateway operates on a direct-to-wallet model, the customer's crypto goes directly into your own private wallet. The platform never holds your funds, private keys never leave your device, and there is zero risk of account freezes or custodial seizures.

The Comprehensive Comparison Table for Telegram Merchants

Feature / MetricCryptoBot (Crypto Pay)Wallet Pay (Crypto Wallet)recv
Custody ModelCustodial (Middleman holds your funds)Custodial (Middleman holds your funds)Non-Custodial (Direct-to-wallet settlement)
Turnover Fees~1% per invoice + withdrawal fees1% to 3% per transaction0% turnover fee on all volume
Pricing StructurePercentage-basedPercentage-basedFlat monthly subscription
Merchant KYC/KYBProject review; high risk of freeze if unverifiedStrict KYB, business registration, bio-IDNo KYC required for merchants
Settlement TimeDelayed (Requires manual withdrawal)Delayed (Requires manual withdrawal)Instant (Directly lands in your wallet)
Supported NetworksTON, TRON, BSC, BTC, ETHTON, BTCTON, TRON (TRC-20), Base, BSC
Supported StablecoinsUSDT, USDCUSDT (on TON only)USDT, USDC
Other Supported AssetsTON, BTC, BNB, TRX, ETHTON, BTCTON, SOL, BNB
Checkout FlowTelegram Web App or external browserSeamless inside Telegram @Wallet menuSmart Checkout (QR, deep links, mobile)
Developer ToolsStandard API, basic webhooksComplex API, strict approval processUnified API, HMAC webhooks, MCP Server, Telegram Bot
Underpayment ResolutionManual refund or support ticketManual resolution, refund hasslesIntelligent underpayment auto-resolution

Deep Dive: Why Your Choice Affects Your Profit and Operations

1. Transaction Fees: Percentage-Based vs. Flat Subscription

Traditional payment gateways penalize your growth. When using custodial providers like CryptoBot or Wallet Pay, your transaction fees scale linearly with your success.

Consider a medium-sized Telegram subscription bot or indie SaaS processing $30,000 per month in USDT:

  • CryptoBot (at ~1%): You pay $300/month in turnover fees, plus gas fees when you withdraw your funds to your secure cold wallet.
  • Wallet Pay (at ~2% average): You pay $600/month in fees.
  • The subscription model: Using the flat-rate plans on recv, you pay a predictable, flat subscription regardless of your transaction volume. The Merchant tier is just $9/month, the Developer tier is $29/month, and the Business tier is $79/month. You pay 0% turnover fees, saving you hundreds or thousands of dollars every month as you scale.

2. Merchant KYC and KYB Barriers

For international founders, digital nomads, and small indie creators, setting up merchant accounts on custodial gateways is an uphill battle.

  • Wallet Pay enforces strict Know Your Business (KYB) checks. This requires legal entity registration, bio-identification of directors, and often locks out merchants residing in various jurisdictions (including the United States, Russia, and parts of Southeast Asia due to local crypto-payment prohibitions).
  • CryptoBot offers quicker onboarding, but they maintain a silent compliance framework. If your volume suddenly spikes or your store receives a bad-faith report, they will freeze your custodial balance until you submit documents verifying the legitimate source of your funds.
  • The non-custodial route: Because the recv gateway never touches or stores your funds, there is no custodial risk to mitigate. No KYC or KYB is required for merchants to use the platform. You can configure your store and start accepting global customer payments in under a minute.

3. Network Diversity and High Gas Fees

A common trap for Telegram merchants is relying solely on Ethereum mainnet or paying exorbitant gas fees on poorly optimized chains.

  • Wallet Pay heavily restricts your choices, focusing almost exclusively on the TON network (and USDT on TON) alongside legacy BTC.
  • CryptoBot supports several chains but imposes high withdrawal minimums and network-processing markups.
  • The multi-chain advantage: To give customers maximum flexibility without exposing them to $20 Ethereum gas fees, the recv network architecture natively supports high-speed, ultra-cheap alternatives. These include TON, TON_USDT, TRON (TRC-20 USDT), Base (Coinbase L2), and BSC. Supported assets include USDT, USDC, TON, SOL, and BNB. High-fee ERC-20 Ethereum mainnet transactions are omitted entirely to keep checkouts frictionless and economical.

4. Smart Checkout Experience

Customer drop-off during the checkout phase is the silent killer of conversion rates.

  • Inside custodial Telegram apps, buyers often have to hold balances directly inside the specific bot's wallet to pay seamlessly. If they pay from an external wallet (like Tonkeeper, Trust Wallet, or Phantom), they must copy addresses and manually enter amounts.
  • If a user sends $49.90 instead of the $50.00 invoice amount due to exchange rate calculations or wallet fees, custodial processors will leave the transaction "unpaid." The merchant's bot doesn't deliver the product, and the customer is left frustrated, requiring manual customer support intervention.
  • The developer integration suite provided by recv implements Smart Checkout. It generates direct checkout links (e.g., https://recv.money/app/checkout/{id}) that render QR codes, offer native deep links into Tonkeeper and Phantom wallets, and feature intelligent underpayment resolution. If a customer is slightly short due to transaction fees, the system can auto-approve the invoice based on your customizable tolerance rules, keeping your conversion rates optimal.

Technical Integration: Automating Deliveries via Secure Webhooks

A payment gateway is only as good as its automation. When a customer pays, your server needs a guaranteed, tamper-proof notification to instantly provision access, deliver digital goods, or upgrade their membership.

Both CryptoBot and Wallet Pay use traditional HTTP API webhooks. However, validating these payloads securely is often an afterthought in basic integrations, exposing merchants to replay attacks or fake payment notifications.

To solve this, the recv network utilizes HMAC-SHA256 signed webhooks combined with an exponential backoff retry mechanism. When an invoice status updates, your endpoint receives a payload with an X-Recv-Signature header, allowing you to mathematically verify that the webhook was dispatched by recv and has not been modified.

Here is a realistic Node.js TypeScript implementation of a secure webhook receiver for your backend server:

import crypto from 'crypto';
import express from 'express';

const app = express();

// Ensure raw body is parsed to preserve string formatting for HMAC verification
app.use(express.json());

app.post('/api/v1/payments/webhook', (req, res) => {
  const signature = req.headers['x-recv-signature'] as string;
  const webhookSecret = process.env.RECV_WEBHOOK_SECRET;

  if (!signature || !webhookSecret) {
    return res.status(401).json({ error: 'Missing signature or webhook secret configuration' });
  }

  // Compute the HMAC-SHA256 signature using your private webhook secret
  const hmac = crypto.createHmac('sha256', webhookSecret);
  const payloadString = JSON.stringify(req.body);
  const computedSignature = hmac.update(payloadString).digest('hex');

  // Securely compare signatures to prevent timing attacks
  const isSignatureValid = crypto.timingSafeEqual(
    Buffer.from(signature, 'hex'),
    Buffer.from(computedSignature, 'hex')
  );

  if (!isSignatureValid) {
    return res.status(401).json({ error: 'Invalid webhook signature' });
  }

  const { invoiceId, status, amount, currency, txHash } = req.body;

  // Process payment confirmation
  if (status === 'PAID') {
    console.log(`Verified Payment: Received ${amount} ${currency} for Invoice ${invoiceId} (TX: ${txHash})`);
    
    // TODO: Add your bot/SaaS fulfillment logic here
    // e.g., db.users.update({ telegramId: req.body.metadata.userId }, { hasPremium: true })
  }

  return res.status(200).json({ received: true });
});

app.listen(3000, () => console.log('Webhook server running on port 3000'));

This ensures that your server only processes valid, authenticated transactions, protecting your digital business from exploiters attempting to spoof payment requests.


Conclusion: Which Gateway is Right For Your Telegram Business?

The best tool depends on your scale, technical requirements, and risk tolerance:

  • Choose CryptoBot (Crypto Pay) if you run a small Telegram hobby project, don't mind custodial risk, and your customers primarily store their crypto balances inside @CryptoBot already.
  • Choose Wallet Pay if you are an established, fully registered corporate entity with a strict legal structure, require native attachment-menu integration, and have the resources to navigate rigorous corporate onboarding and geographic limits.
  • Choose the non-custodial architecture of recv if you are an indie founder, SaaS developer, or bot creator who wants to maintain absolute control of your revenue. By using recv, you bypass KYC, eliminate custodial freeze risks, enjoy flat subscription pricing with 0% turnover fees, and integrate a unified developer-friendly API across TON, TRON, Base, and BSC.

Ready to protect your revenue and provide an elite checkout experience for your users? Explore our Business subscription tier or start with a free trial today.


FAQ

What is the primary difference between custodial and non-custodial Telegram gateways?

Custodial gateways (like CryptoBot and Wallet Pay) act as intermediaries that hold your customer’s funds on their own balance sheet. You must manually request withdrawals, and your account is vulnerable to regulatory freezes. Non-custodial gateways (like recv) never hold your funds. Crypto is sent directly from your customer's wallet into your private wallet, ensuring you retain 100% control of your private keys and balances at all times.

Is KYC mandatory for accepting payments on recv?

No. Because recv is non-custodial and never holds, transfers, or sits in custody of merchant funds, there is no merchant KYC or corporate KYB verification process required to launch. You can register, connect your public wallet addresses, and start receiving payments immediately.

How does the 0% turnover fee structure work?

Traditional processors charge 1% to 3% on every dollar you make, meaning your costs increase as your business grows. In contrast, recv charges no transaction percentage fees. Instead, you pay a simple, flat monthly subscription (starting with a Free Trial limited to 15 lifetime invoices, up to $79/mo for large-scale operations), allowing you to keep 100% of your incoming revenue.

Which blockchains does recv support?

The recv platform supports fast, low-cost networks including TON, TRON, Base (Coinbase L2), and BSC. You can accept popular stablecoins and native assets like USDT, USDC, TON, SOL, and BNB. Legacy, high-fee networks like Ethereum (ERC-20) mainnet are excluded to keep transaction costs minimal for your buyers.

What is Smart Checkout and how does it prevent lost sales?

Smart Checkout by recv includes interactive QR codes, direct mobile deep linking into popular self-custodial wallets like Tonkeeper and Phantom, and intelligent underpayment resolution. If a buyer pays slightly less than the invoice amount due to network fees or wallet-side conversions, the invoice auto-resolves based on your customizable threshold limits, preventing delayed deliveries and reducing customer support tickets.