Paper 046: Competitive Payment Provider Analysis

Date: 2026-04-03

Status: Complete

Research Scope: Stripe alternatives, crypto payment processors

Executive Summary

GetRida currently uses Zero Hash Connect (ZHC) for stablecoin deposits and Juno for bank rails. This paper analyzes five alternative payment providers to identify opportunities for multi-payment support, instant activation, and improved developer experience.

Key Findings:

BTCPay Server offers zero-fee crypto acceptance but requires self-hosting infrastructure
Coinbase Commerce provides instant crypto onboarding but documentation is deprecated/limited
Paddle & Lemon Squeezy are merchant-of-record platforms handling tax/compliance automatically
Crypto.com Pay has zero transaction fees but charges payout fees
Inline checkout (Paddle, Lemon Squeezy) provides better UX than redirect flows

Recommendation: Prioritize Lemon Squeezy for fiat payments (merchant-of-record model simplifies compliance) and BTCPay Server for zero-fee crypto self-custody option.

1. Coinbase Commerce (Crypto Payment Processor)

Payment Flow

Mechanism: Redirect to hosted payment page or inline button SDK
Flow Type: Both redirect and inline (via JavaScript SDK)
Integration: Button SDK embeds checkout popup; page redirection available as fallback

Activation Speed

Instant: No KYC or approval process for accepting crypto
Status: Documentation appears deprecated (commerce.coinbase.com/docs redirects to empty page)
Note: Coinbase Commerce may be sunset or merged into newer CDP (Coinbase Developer Platform) products

Fee Structure

Transaction Fee: 0% (zero fees claimed)
Payout Fee: Applied when withdrawing funds
Supported: BTC, ETH, USDC, and other ERC-20 tokens

Supported Currencies

Crypto: BTC, ETH, USDC, DAI, DOGE, LTC, BCH, and other major cryptocurrencies
Fiat Pricing: Can price in fiat (USD, EUR, etc.), converted to crypto at checkout
Settlement: Crypto only (no fiat settlement)

Developer UX

API Complexity: Simple REST API with payment creation endpoints
SDKs: JavaScript Button SDK for inline checkout
Docs Quality: ⚠️ Poor — primary docs URL returns empty page; legacy docs fragmented
Webhook Support: Yes, for payment status updates
Integration Time: ~1 hour (if docs were functional)

Strengths

Zero transaction fees
Instant merchant onboarding
Non-custodial (merchant controls private keys)

Weaknesses

Documentation appears deprecated/abandoned
No fiat settlement option
Uncertain product roadmap (may be discontinued)

2. BTCPay Server (Self-Hosted Crypto)

Payment Flow

Mechanism: Self-hosted invoice system; redirect or embedded checkout
Flow Type: Redirect to invoice page, or inline via iFrame/API
Integration: REST API (GreenField API) or legacy BitPay-compatible API

Activation Speed

Instant (once deployed)
Deployment Time: 30 min - 2 hours depending on hosting method (Docker recommended)
Infrastructure Required: Self-hosted server or VPS

Fee Structure

Transaction Fee: 0% (zero fees)
Network Fee: Paid by customer (blockchain fees for BTC/Lightning)
Hosting Cost: ~$5-20/month for VPS

Supported Currencies

Crypto: BTC, Lightning Network, optional altcoins (via plugins)
Fiat Pricing: Price in any fiat currency; converted to crypto at checkout
Settlement: Crypto only (direct to merchant wallet)

Developer UX

API Complexity: Moderate — GreenField API is well-documented REST
SDKs: None official; community libraries for Node.js, Python, PHP
Docs Quality: Excellent (comprehensive, open-source)
Webhook Support: Yes, for invoice status updates
Integration Time: 2-4 hours (including deployment)

Strengths

Zero fees (only network fees paid by customer)
Full self-custody (merchant owns private keys)
Open-source (no vendor lock-in)
Lightning Network support (instant settlements)

Weaknesses

Requires self-hosting (infrastructure overhead)
No fiat settlement (crypto only)
No compliance handling (merchant responsible for tax/AML)

3. Paddle (Stripe Alternative, Merchant of Record)

Payment Flow

Mechanism: Inline checkout (Paddle.js SDK) or overlay checkout
Flow Type: Inline (embeds iframe in page) or overlay popup
Integration: JavaScript SDK with event callbacks for items/totals

Activation Speed

Delayed: 1-3 business days for account approval
Domain Approval Required: Payment link domains must be whitelisted
KYC: Required for live mode

Fee Structure

Transaction Fee: 5% + $0.50 per transaction
Currency Conversion: Included (no additional fees)
VAT/Tax Handling: Included (Paddle is merchant of record)
Payout Fee: None

Supported Currencies

Fiat: 30+ currencies (USD, EUR, GBP, etc.)
Crypto: None
Payment Methods: Cards, PayPal, Apple Pay, Google Pay

Developer UX

API Complexity: Low — Paddle.js SDK abstracts most complexity
SDKs: JavaScript (Paddle.js), REST API, webhooks
Docs Quality: Excellent — step-by-step tutorials, CodePen examples
Webhook Support: Comprehensive event system
Integration Time: 2-4 hours for inline checkout

Strengths

Merchant of Record (Paddle handles tax, VAT, compliance)
Inline checkout (better UX than redirect)
Subscription management built-in
Automatic localization (30 currencies, 200+ markets)

Weaknesses

Higher fees than Stripe (5% + $0.50 vs ~2.9% + $0.30)
Delayed activation (requires approval)
No crypto support

4. Lemon Squeezy (Stripe Alternative, Merchant of Record)

Payment Flow

Mechanism: Redirect to hosted checkout or overlay (Lemon.js)
Flow Type: Redirect or overlay iframe
Integration: REST API to create checkout URL, then redirect or use Lemon.js for overlay

Activation Speed

Instant for test mode
1-2 business days for live mode approval
No Domain Whitelisting: Unlike Paddle, no waiting for domain approval

Fee Structure

Transaction Fee: 5% + $0.50 (base)
Additional Fees:
+1.5% for international (non-US) payments
+1.5% for PayPal
+0.5% for subscription renewals
Example: $20 product with 20% VAT = $24 total → $2.06 platform fee → $17.94 net
Payout Fee:
Free for US bank accounts (via Stripe)
1% for non-US bank accounts
$0.50 (US) or 3% capped at $30 (non-US) for PayPal

Supported Currencies

Fiat: USD, EUR, GBP, and other major currencies
Crypto: None
Payment Methods: Cards, PayPal, Apple Pay

Developer UX

API Complexity: Low — simple REST API for checkout creation
SDKs: JavaScript (Lemon.js), official SDKs for Node, PHP, Go, Python
Docs Quality: Excellent — clear guides, API reference, examples
Webhook Support: Yes, with custom data passthrough
Integration Time: 1-2 hours

Strengths

Merchant of Record (handles tax/VAT globally)
Faster activation than Paddle (no domain approval)
Custom pricing via API (dynamic pricing per checkout)
Expiring checkout URLs (useful for limited-time offers)
Webhook custom data (pass user_id, session_id, etc.)

Weaknesses

Higher fees for international/PayPal payments (can reach 8%+)
No crypto support
Payout fees for non-US accounts

5. Crypto.com Pay (Crypto Payment Gateway)

Payment Flow

Mechanism: Redirect to payment page or inline button SDK
Flow Type: Both redirect and inline (via JavaScript SDK)
Integration: Button SDK (similar to Coinbase Commerce) or page redirection

Activation Speed

Instant for accepting payments
Dashboard Access: Sign up for merchant account, generate API keys immediately
No KYC for Test Mode

Fee Structure

Transaction Fee: 0% (zero fees)
Payout Fee: Applied when withdrawing to bank or wallet
Fiat Payouts: Fee varies by currency (USD: min $100, EUR: min €130, AUD: min $150)
Crypto Payouts: Blockchain fee + min settlement amount
Transmittance Fee: May apply for international wire transfers (third-party bank fees)

Supported Currencies

Crypto: CRO, BTC, ETH, USDC, DOGE, and 100+ tokens supported by Crypto.com App
Fiat Pricing: Price in USD, EUR, AUD, CAD, GBP, and 30+ fiat currencies
Settlement: Both crypto and fiat (merchant can choose settlement currency)

Developer UX

API Complexity: Moderate — REST API with payment creation, refunds, subscriptions
SDKs: JavaScript Button SDK, mobile SDK examples available
Docs Quality: Good — comprehensive API reference with code examples
Webhook Support: Yes, configurable per payment or global
Integration Time: 2-3 hours

Strengths

Zero transaction fees (merchant receives full fiat amount)
Pay Rewards program (customers earn CRO rebates)
Subscription support (recurring crypto payments)
Fiat settlement option (unlike BTCPay/Coinbase Commerce)

Weaknesses

Payout fees (can be higher than transaction fee models)
Minimum settlement amounts ($100 USD, 0.01 BTC, etc.)
Complex underpayment handling for on-chain wallets
Customer must have Crypto.com App for best UX (other wallets incur network fees)

Comparison Matrix

|----------|-----------|------------|-----------------|------------|--------|------|-----------|--------------|

| Coinbase Commerce | Redirect/Inline | Instant | 0% | Yes | ✅ | ❌ | ✅ | ❌ |

| BTCPay Server | Redirect/API | Instant | 0% | None* | ✅ | ❌ | ⚠️ | ❌ |

| Paddle | Inline | 1-3 days | 5% + $0.50 | None | ❌ | ✅ | ✅ | ✅ (MoR) |

| Lemon Squeezy | Redirect/Overlay | 1-2 days | 5-8%+ | 0-3% | ❌ | ✅ | ✅ | ✅ (MoR) |

| Crypto.com Pay | Redirect/Inline | Instant | 0% | Yes | ✅ | ✅ | ✅ | ❌ |

*Self-hosting required

**Only blockchain network fees (paid by customer)

Recommendations for GetRida

1. Primary Fiat Rails: Lemon Squeezy

Why:

Merchant-of-record model eliminates tax/VAT complexity
Faster activation than Paddle (no domain approval)
Custom pricing via API (useful for dynamic pricing)
Webhook custom data passthrough (track user_id, session_id)

Use Case: Multi-currency fiat payments for users without crypto wallets

2. Zero-Fee Crypto Option: BTCPay Server

Why:

Zero fees (merchant keeps 100% minus network fees)
Full self-custody (no counterparty risk)
Lightning Network support (instant settlements)
Open-source (no vendor lock-in)

Use Case: Power users who want self-custody and zero fees

Trade-off: Requires self-hosting infrastructure (~$10/mo VPS)

3. Crypto-to-Fiat Settlement: Crypto.com Pay

Why:

Zero transaction fees
Fiat settlement option (unlike Coinbase/BTCPay)
Subscription support (recurring crypto payments)

Use Case: Users who want to pay in crypto but merchant prefers fiat settlement

Trade-off: Payout fees and minimum settlement amounts

Implementation Priority

Phase 1: Fiat Support (Week 1-2)

1. Integrate Lemon Squeezy for fiat checkout

Use checkout overlay (Lemon.js) for inline UX
Pass custom data (user_id, session_id) via API
Listen to webhooks for order completion

Phase 2: Zero-Fee Crypto (Week 3-4)

2. Deploy BTCPay Server on VPS

Docker deployment (~1 hour)
GreenField API integration
Lightning Network node setup (optional but recommended)

Phase 3: Crypto-Fiat Bridge (Week 5-6)

3. Integrate Crypto.com Pay as fallback

Button SDK for inline checkout
Configure fiat settlement (USD)
Set up webhooks for payment confirmation

Developer Experience Ranking

1. Lemon Squeezy — Simplest API, best docs, fastest integration

2. Paddle — Excellent docs, but more complex inline checkout setup

3. Crypto.com Pay — Good docs, moderate API complexity

4. BTCPay Server — Great docs, but requires infrastructure knowledge

5. Coinbase Commerce — ⚠️ Deprecated/broken docs

Cost Analysis (Example: $100 Transaction)

|----------|-----------------|------------|-----------------|

| Lemon Squeezy (US) | $5.50 (5.5%) | $0 | $94.50 |

| Lemon Squeezy (Intl) | $7.00 (7%) | 1% | $92.07 |

| Paddle | $5.50 (5.5%) | $0 | $94.50 |

| Crypto.com Pay | $0 | ~$2-5 | $95-98 |

| BTCPay Server | $0 | $0* | $100 |

*Customer pays blockchain network fees

Conclusion

For GetRida's multi-payment strategy:

1. Lemon Squeezy solves fiat payments with automatic tax handling

2. BTCPay Server provides zero-fee crypto self-custody

3. Crypto.com Pay bridges crypto users who want fiat-like UX

Next Step: Build Lemon Squeezy integration first (highest ROI, lowest friction). Deploy BTCPay as "pro" tier option. Add Crypto.com Pay if demand for crypto-to-fiat exists.

Paper Status: Complete

Research Time: 1 hour

Sources: Official documentation, API references, fee schedules

Confidence: High (based on 2026 documentation, may change)