Litecoin payment infrastructure for reviewed merchants

LitePay Gateway

Hosted checkout, REST APIs, signed webhooks, withdrawals, and administration for Litecoin payments without running a full node or storing private keys in the web application.

Hosted CheckoutLitecoin

Every payment receives a dedicated Litecoin address, a hosted checkout page, and webhook events backed by persisted blockchain state.

Created

Payment record

Address

xPub derived

Network

LitecoinSpace

Delivery

HMAC webhook

How the system works

The architecture separates merchant operations, wallet metadata, blockchain monitoring, and webhook delivery.

1

Merchant creates a payment through the dashboard or REST API.

2

The platform assigns a fresh Litecoin address from a watch-only wallet pool.

3

LitecoinSpace monitoring detects transactions and confirmation depth.

4

Signed webhooks notify the merchant as the payment state changes.

Hosted checkout

Create secure payment links with QR code, copy actions, expiration, and confirmation progress.

Developer API

Use idempotent REST endpoints with API keys, scopes, IP whitelists, and clear error objects.

Operational security

HMAC webhooks, audit logs, 2FA, secure cookies, rate limits, and withdrawal verification.

API Overview

Every endpoint accepts a `cryptocurrency` field. The current supported value is `LTC`.

Create Payment
Get Payment Status
Create Withdrawal
Balance
Transactions
API Keys
Webhooks
Health

Security by default

The product is designed around layered controls rather than a single authorization check.

Rate limiting and brute-force protection
JWT access tokens and refresh-token session design
HMAC signed webhooks with replay protection
Password hashing with Argon2 or bcrypt
CSRF, XSS, CSP, Helmet-style security headers
Audit logs, device management, and IP whitelist support

Account access process

1

Submit application

Provide business context, expected volume, and payment use cases.

2

Administrator review

The operations team approves or rejects the request with a reason.

3

Account activation

Approved merchants receive access credentials and can create API keys.