Merchant-directed forwarding
The payout destination is supplied by the merchant when the payment configuration is created.
About CryptPays
CryptPays is a cryptocurrency payment gateway and Merchant API for generating payment addresses, detecting supported blockchain payments, forwarding qualifying funds to merchant-configured destinations, and delivering signed payment callbacks.
Why CryptPays exists
Accepting cryptocurrency involves more than displaying an address. Applications need a current asset identifier, a compatible payout destination, network-aware payment detection, confirmation or finality, forwarding, authenticated delivery, and exact reconciliation.
CryptPays brings that lifecycle behind one HTTP integration. It is designed for online platforms, digital services, marketplaces, software products, and other businesses accepting supported cryptocurrencies. Public asset discovery and normal payment-address creation do not require merchant API credentials; signed callbacks form the verification boundary before fulfillment.
Payment model
A merchant supplies a callback URL and payout address for an enabled canonical ticker. CryptPays returns the customer deposit address, observes matching chain activity, applies the effective processing condition, and forwards a qualifying payment.
CryptPays is designed to forward qualifying payments to merchant-configured destinations rather than maintain a merchant account balance for later withdrawal. Forwarding is not described as instant: network state, finality, transaction construction, and delivery each have their own lifecycle.
Provide the canonical ticker, callback URL, and payout destination.
Give the customer the returned deposit address and correct network context.
Detect the independent blockchain deposit and its lifecycle.
Apply the chain's required confirmation or finality condition.
Forward qualifying funds and deliver the signed callback for merchant processing.
Product principles
The product is documented through integration behavior that merchants and developers can verify at the application boundary.
The payout destination is supplied by the merchant when the payment configuration is created.
Network-specific confirmation, finality, address, and transaction behavior stays behind a consistent Merchant API.
RSA-SHA256 signatures, timestamps, and stable lifecycle identifiers support authenticated, idempotent merchant handling.
The live catalog—not a marketing inventory—identifies enabled mainnet assets and their canonical tickers.
Callbacks separate the deposited amount, forwarded amount, applied percentage, and total deduction as decimal strings.
Standard pricing follows qualifying processed volume over the previous 30 days, measured in USDT equivalent.
Network families
CryptPays has processing capabilities across EVM, UTXO, Solana/SPL, and TRON families. The live Supported Assets catalog remains authoritative for current mainnet availability.
Native assets and supported token standards across enabled EVM chains.
Chain-aware transaction outputs, confirmations, and forwarding economics.
Finality-aware native and token payment processing.
Native and supported token payment flows using TRON-specific behavior.
Built for integration
CryptPays exposes the payment state and accounting fields; merchants retain control of their application, order rules, callback processing, and payout destination.
Start with a concise integration overview, then use the maintained documentation for complete endpoint and network contracts.
Open DevelopersConfirm chain state, verify callback signatures and freshness, and process the stable UUID idempotently before fulfillment.
Review SecurityReview the current validated global pricing schedule and the distinction between percentage and network-related deductions.
Review PricingExplore CryptPays
Review current assets, follow the Merchant API workflow, or send a focused product or integration enquiry.