PROPELOO

CRYPTO PAYMENT GATEWAY / WEB3 PAYMENTS

Accept cryptocurrency payments without the complexity.

PROPELOO engineers cryptocurrency payment gateways — from payment request generation and on-chain payment detection through settlement, multi-currency support, volatility hedging and the merchant dashboard that makes crypto acceptance as operationally simple as Stripe. Crypto payment processing is a solved engineering problem. The question is whether your implementation is production-grade.

The merchant who accepts crypto and receives volatile assets they cannot hedge will stop accepting crypto after the first market crash.

Crypto payment acceptance fails for two reasons: technical complexity (on-chain payment detection, underpayment handling, multi-chain support) and volatility risk (the merchant accepts $100 of ETH; by settlement time it is worth $85). A production crypto payment gateway solves both: automated on-chain payment detection across multiple chains and assets, and settlement in stablecoins or fiat to eliminate volatility risk. PROPELOO builds payment gateways that abstract the blockchain complexity from merchants and eliminate the volatility problem through configurable settlement options.

The crypto payment gateway stack.

System Layers

  • Payment Layer: Payment request generation, unique address per payment, expiry management
  • Detection Layer: On-chain transaction monitoring, confirmation counting, underpayment handling
  • Settlement Layer: Stablecoin settlement, fiat conversion, direct settlement, fee deduction
  • Merchant Layer: Dashboard, payment history, refund management, API integration
  • Compliance Layer: KYB for merchants, AML screening, transaction reporting

Core Technical Capabilities

  • Payment Request System

    Generate unique payment addresses per transaction, payment expiry and re-assignment, QR code generation, payment amount in local currency with live conversion, deep link for mobile wallets.

  • Multi-chain Payment Detection

    WebSocket subscriptions to Ethereum/Solana/BTC nodes for real-time transaction detection, configurable confirmation count per currency, underpayment tolerance configuration, overpayment credit or refund.

  • Settlement Options

    Instant conversion to USDC/USDT on receipt (eliminates volatility risk), periodic batch fiat conversion via exchange API, direct settlement in received currency, configurable settlement threshold.

  • E-commerce Integrations

    Shopify plugin, WooCommerce plugin, custom checkout API for headless commerce, Stripe-compatible API wrapper for easy migration, webhook notifications for order management systems.

  • Merchant Dashboard

    Payment history, revenue analytics, settlement reports, refund management, API key management, webhook configuration, supported currency management.

  • Invoice & Subscription

    Invoice generation with crypto payment link, recurring subscription billing in stablecoins, payment reminder automation, invoice status tracking.

How we think about crypto payment gateways.

A crypto payment gateway is a reliability product. Payment detection that fails means lost sales. Settlement that is slow means cash flow problems for merchants.

  • Stablecoin settlement removes the biggest merchant objection

    The #1 reason merchants refuse crypto: volatility. If a merchant receives 0.05 ETH for a $100 product, and ETH drops 20% before they can convert, they received $80. Instant conversion to USDC on payment confirmation eliminates this entirely. The merchant sees "$100 received in USDC" — no volatility risk, familiar value.

    Axiom:

  • Payment detection must be fast and reliable

    WebSocket subscriptions to blockchain nodes for real-time transaction detection. Multiple node providers for redundancy. Confirmation threshold calibrated per currency: Ethereum 1-2 blocks for USDC, 3 blocks for ETH, 6 blocks for BTC (unless Lightning). A payment gateway that takes 15 minutes to confirm a transaction loses customers.

    Axiom:

  • Underpayment handling must be explicit

    Users regularly underpay cryptocurrency amounts due to fee deduction from hot wallets or decimal errors. The gateway must handle: strict mode (reject underpayments, require top-up), tolerance mode (accept within 1% underpayment), and crediting the received amount with prompting for the difference.

    Axiom:

  • Multi-chain is table stakes by 2024

    A crypto payment gateway that only accepts Ethereum mainnet will miss users who have assets on L2s (Arbitrum, Base, Polygon), on Solana, on BNB Chain, or in Bitcoin/Lightning. Each chain requires separate payment detection infrastructure. Prioritise by where your merchants' customers actually have assets.

    Axiom:

Crypto payment gateway decisions.

  • Settlement in stablecoins vs native crypto vs fiat?

    Impact: Merchant-configurable is the production standard: stablecoin as the default (eliminates volatility without banking complexity), fiat as an option for merchants who want complete crypto exit, native for crypto-native merchants.

    • Stablecoin settlement (USDC/USDT) — eliminates volatility, stays in crypto ecosystem
    • Fiat settlement (USD via banking) — familiar to merchants, requires banking partners
    • Native crypto settlement — merchant keeps the asset, volatile
    • Merchant chooses — maximum flexibility, highest complexity
  • Address reuse strategy?

    Impact: Unique address per payment with expiry (15-30 minutes) is the production standard — enables payment tracking, prevents address reuse, allows payment reconciliation.

    • Same address per merchant — simplest, poor tracking
    • Unique address per payment — best practice, requires HD wallet
    • Unique address per payment + expiry — standard production approach
    • Payment channel (Lightning) — no on-chain footprint per payment
  • Supported chains at launch?

    Impact: Ethereum + USDC on Arbitrum/Base (low gas for small payments) + Solana + Bitcoin/Lightning covers 90% of active crypto users. Add chains based on merchant geography and customer demographics.

    • Ethereum only — single chain, deepest liquidity
    • Ethereum + Polygon (low gas) — covers most EVM users
    • EVM + Solana + Bitcoin — covers majority of crypto users
    • All major chains — maximum accessibility, highest maintenance
  • Lightning Network support?

    Impact: Lightning Network for Bitcoin payments is increasingly expected for point-of-sale and small-amount transactions. On-chain Bitcoin for large purchases where Lightning channel capacity may be insufficient.

    • No Lightning — slower BTC confirmation, less suitable for small payments
    • Lightning as primary Bitcoin — instant confirmation, low fees
    • Both on-chain and Lightning — maximum flexibility
    • Lightning only — fastest, requires Lightning infrastructure
  • Exchange API for conversion?

    Impact: Self-custody with automated CEX conversion for volume. Specialised processors for fast go-to-market. On-chain DEX conversion for fully non-custodial architecture (no exchange account required).

    • Self-custody with manual conversion — full control, operational burden
    • Binance/Coinbase API — liquid, reliable, API key management
    • Aggregator (1inch, 0x) for on-chain conversion — instant, DEX slippage
    • Specialised payment processor (B2BinPay, CoinGate) — managed, per-transaction cost

What PROPELOO builds.

  • E-commerce Crypto Gateway

    Shopify/WooCommerce plugin or headless checkout API — multi-currency acceptance, stablecoin settlement, real-time payment detection.

  • Invoice Payment Gateway

    B2B invoice payment via crypto — invoice generation, payment link, multi-currency, stablecoin settlement, accounting system integration.

  • Crypto Subscription Billing

    Recurring billing in USDC/USDT — subscription contract, automatic charge, dunning for insufficient balance, invoice generation.

  • POS Crypto Payments

    Point-of-sale crypto payment terminal — QR code generation, Lightning Network, real-time confirmation notification, cash register integration.

  • White-label Payment SDK

    Embeddable payment SDK for any product — React components, React Native, and REST API for backend integration.

  • Cross-border Payment Gateway

    International payment processing via crypto — send in fiat on one end, receive in fiat on the other, with stablecoin as the transport layer.

The crypto payment gateway stack.

  • Blockchain

    Stack: Ethereum (ethers.js), Solana (web3.js), Bitcoin (bitcoinjs-lib), Lightning (LND/CLN)

  • Payment Detection

    Stack: Alchemy Webhooks, QuickNode Streams, Custom WebSocket nodes, Helius (Solana)

  • Settlement

    Stack: 1inch API (DEX swap), Binance API (CEX), Circle (USDC), Fireblocks (custody)

  • Backend

    Stack: Node.js / Go, PostgreSQL, Redis (payment state), Kafka (payment events)

  • Integrations

    Stack: Shopify Partner API, WooCommerce REST API, Stripe-compatible API, QuickBooks (accounting)

  • Frontend

    Stack: React (checkout widget), QR code generation, Wallet deep links, Real-time payment status

Payment gateway security protects merchant revenue.

  • Replay attack prevention

    Each payment must have a unique ID and cannot be reused. Payment detection must be idempotent — processing the same transaction twice must not create double credit.

  • Address generation security

    HD wallet-derived addresses use a non-extractable master key in HSM. Even if the gateway database is compromised, the key material cannot be extracted.

  • Settlement key management

    Keys for automated settlement transactions must be in HSM with daily transaction limits. Any settlement above threshold requires manual approval.

  • Webhook authentication

    Payment notifications to merchant systems must be HMAC-signed. Unsigned webhooks accepted by merchants create injection vulnerabilities.

  • AML screening

    Incoming crypto payments should be screened against known high-risk wallets (Chainalysis or Elliptic). Merchants should not unknowingly receive proceeds of crime.

  • Double-spend protection

    For Bitcoin: wait for sufficient confirmation count before marking payment as complete. For Ethereum: monitor for chain reorganisations during the confirmation window.

From concept to live payment gateway.

  1. 01. Gateway Design

    Supported chains, settlement model, merchant onboarding, fee structure.

  2. 02. Payment Detection

    Node WebSocket connections, confirmation logic, multi-chain monitoring.

  3. 03. Address Generation

    HD wallet per merchant, unique address per payment, expiry management.

  4. 04. Settlement

    Stablecoin conversion, fiat integration (if applicable), settlement reporting.

  5. 05. Merchant Dashboard

    Payment history, analytics, API key management, webhook configuration.

  6. 06. Integrations

    Shopify, WooCommerce, REST API, SDK.

  7. 07. KYB & Launch

    Merchant KYB, AML setup, beta merchants, monitoring.

Crypto payment gateways we have shipped to production.

Three payment integrations handling real merchant volumes.

  • Crypto checkout for e-commerce platform processing $1.2M monthly

    Challenge: E-commerce operator needed crypto checkout as an alternative payment rail — generating a per-order payment address, detecting confirmation, crediting the order, and settling to USDC instantly without holding volatile crypto.

    Architecture: HD wallet address derivation for unique per-order addresses, mempool monitoring for zero-confirmation detection, 1-confirmation settlement trigger, instant DEX swap to USDC, webhook notification to e-commerce platform.

    Outcome: $1.2M monthly crypto checkout volume, <5s payment detection, 0.3% underpayment rate handled by tolerance engine, 100% merchant settlement in USDC.

  • Recurring crypto billing system for SaaS with stablecoin pull payments

    Challenge: SaaS company needed recurring crypto billing without requiring users to manually pay each month — stablecoin pull payments from user wallets with pre-authorised spending allowances.

    Architecture: ERC-20 approve/transferFrom for pull payments, spending allowance management UI for subscribers, automated monthly billing job, failed payment retry with grace period, invoice NFT for tax receipts.

    Outcome: 4,200 active crypto subscribers, 96% billing success rate on first attempt, 3.2% recovery via retry, LTV equal to fiat subscribers.

  • Stablecoin payment rail replacing SWIFT for B2B cross-border transfers

    Challenge: Import/export business processing $3M/month in cross-border payments needed a stablecoin rail to replace SWIFT — faster settlement (minutes vs days), lower fees (0.5% vs 3-5%), and compliance-grade transaction records.

    Architecture: Circle USDC transfer API for on/off ramp, Fireblocks custody for in-transit funds, Travel Rule compliance via Notabene, automated FX conversion at both ends, SWIFT-compatible remittance information fields.

    Outcome: 82% cost reduction vs SWIFT, average settlement time 4 minutes, $3.1M monthly volume, zero compliance incidents in 14 months.

Frequently Asked Questions

How do I handle cryptocurrency volatility as a merchant?

Configure instant stablecoin settlement: when a payment is detected and confirmed, the gateway automatically converts the received cryptocurrency to USDC or USDT. The merchant sees a payment in USDC — stable value, no volatility risk. This conversion happens on a DEX or via exchange API within seconds of payment confirmation. The conversion fee is typically 0.3–0.5%, much less than the volatility risk of holding native crypto.

What happens if a customer underpays?

Underpayment is common — users send from exchanges where the fee is deducted from the amount, or they miscalculate decimal places. Your payment gateway should support configurable tolerance: strict mode (exact amount required, payment address stays open), tolerance mode (accept payments within X% of required), or partial credit (credit what was received, send a follow-up payment link for the remainder). We configure the mode that matches your business model and risk tolerance.

How does Bitcoin Lightning payment work?

Lightning Network is a payment channel network built on top of Bitcoin. Instead of on-chain transactions (10–60 minute confirmation), Lightning payments are instant (sub-second) with near-zero fees. The gateway generates a Lightning invoice (a payment request with embedded routing information). The customer's Lightning wallet pays the invoice, and the gateway receives instant confirmation. Channel capacity limits individual payment size. Best for frequent, small payments — micropayments, subscriptions, gaming credits.

Which cryptocurrencies should I accept as a merchant?

Start with: Bitcoin (BTC) — highest brand recognition, trust from new users; Ethereum (ETH) — largest DeFi ecosystem, ERC-20 token support; USDT/USDC on Ethereum or Tron — stablecoin payments that eliminate volatility with instant settlement; and one fast/cheap chain like Polygon or BNB Chain for small transactions where Ethereum gas is prohibitive. Accepting 15+ currencies adds engineering complexity and compliance burden without proportional volume. Start narrow, add currencies as demand is confirmed.

How do crypto payment gateways handle compliance?

Compliance varies by jurisdiction and business type. At minimum: KYC for high-value transactions (typically over $1,000–$3,000), transaction monitoring for AML (screen wallets against sanctions lists like OFAC, EU, UN), record-keeping for tax reporting (payer wallet address, amount, timestamp, exchange rate). For regulated merchants (financial services, gambling, exchanges), full VASP registration may apply. We integrate Chainalysis or Elliptic for real-time wallet risk scoring and build SAR (Suspicious Activity Report) filing workflows for regulated clients.

What is the difference between a custodial and non-custodial payment gateway?

Custodial gateway: the provider holds the private keys and manages wallets on your behalf. Simpler for merchants — no key management, instant fiat conversion. Risk: the provider controls your funds (similar to keeping money in an exchange). Examples: Coinbase Commerce, BitPay. Non-custodial gateway: payments go directly to wallets you control. No counterparty risk, but you are responsible for key management, hardware security modules, and on-chain transaction monitoring. We build non-custodial gateways for clients who need full control of customer funds.

Can I accept crypto payments on my existing e-commerce platform?

Yes. We build gateway integrations for major e-commerce platforms: Shopify (via checkout extension), WooCommerce (WordPress plugin), Magento, and custom-built storefronts. Integration delivers: a payment option at checkout, a unique payment address per order, real-time payment detection, automatic order confirmation on receipt, and webhook events to your backend (payment.received, payment.confirmed, payment.expired). Integration time for a standard platform: 2–4 weeks. Custom storefronts: 4–8 weeks.

How do I convert crypto payments to fiat currency?

Three routes: (1) Off-ramp API — integrate a service like Banxa, Wyre, MoonPay or a local exchange API to auto-convert on confirmation. Typical fees: 1–2.5%. (2) Exchange withdrawal — accumulate crypto on-exchange and withdraw as fiat via bank transfer. Lower fees but manual process. (3) Stablecoin settlement — convert to USDC/USDT on-chain (0.3–0.5% fee) and hold as a stable store of value, converting to fiat when convenient. Route 1 is best for merchants who need immediate fiat. Route 3 is best for businesses that operate globally and want currency flexibility.