Crypto PSP

Crypto payment providers live or die on two things: knowing a deposit has landed, and moving funds out safely. Both are infrastructure problems, and both are what this API is for.

Derive a deposit address per customer from an xPub — a public key, so the private key never reaches us. Get a webhook the moment a transfer confirms. Prepare the outbound transaction, sign it on your own server, and broadcast it. You keep custody of every key at every step; we run the nodes, absorb the reorgs and keep the data warm.

100+ REST APIs
35+ Networks
99.99% Uptime
Start on the free plan Let's discuss your project

Some of the features you can use

Deposit Addresses

Easily generate addresses in order to be able to accept and track crypto and other digital asset deposits.

Get Notifications

Get callback notifications (webhooks) whenever there are any deposits or withdrawals to or from your addresses that you would like to be notified about.

Create Transactions

Transactions are prepared by the API and signed by you, on your own infrastructure. The private key stays in your process, so the funds stay under your control at every step.

Balances & Fees

Get information on balances, fees, and any other data on demand without having to manage or fetch vast blockchain databases and nodes.

The benefits of using Crypto APIs

Developed to save time. Designed to be robust.

Save on development time

Leverage the power of a proven blockchain infrastructure trusted by industry leaders. Integrate once, go to market in days.

Reduce maintenance costs

Our flexible pricing plans offer the best cost to performance ratio. Get access to full product suite and features. Upgrade or downgrade anytime.

Enterprise-grade security

We apply encryption to REST, encryption to memory, and encryption in transit on all sensitive data. We are fully ISO 27001 certified.

All-in-one dashboard

One dashboard for all of your crypto operations. Get API keys, generate addresses, setup webhooks, monitor failed requests, callbacks and more.

How to accept crypto payments

1

Give each customer an address

Derive a deposit address per customer from an xPub. Only the public key reaches us, so you never hand over a private key.

2

Know the moment funds land

Subscribe to a confirmed-transaction webhook on those addresses and settle the order when the callback arrives.

3

Screen before you credit

Run the sending address through AML screening if you are regulated, before the funds count as received.

4

Pay out under your own key

Prepare the outbound transaction, sign it on your own server, and broadcast it.

You might also be interested in

x402 Payments
x402 Payments
Market Data
Transactions Data
AI Compatibility
Blockchain Fees

Frequently Asked Questions

Blockchain Events

Which blockchains does the CryptoAPIs Blockchain Events API support?

Blockchain Events covers 35+ networks across EVM, UTXO, and account-based networks. The EVM chains are Ethereum, Ethereum Classic, BNB Smart Chain, Polygon, Avalanche C-Chain, Tron, Arbitrum, Base, and Optimism. UTXO chains include Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, and Zcash, plus XRP, Solana, and Kaspa. Both mainnet and testnet networks are available for most chains.

Does the Blockchain Events API support Solana?

Yes. Solana is a supported chain for Blockchain Events on both mainnet and devnet, alongside XRP and Kaspa. You can subscribe to events and receive callbacks for Solana activity through the same unified subscription flow used for the EVM and UTXO chains.

What blockchain event types can I subscribe to?

You can subscribe to confirmed coin (native) transactions, unconfirmed coin transactions, internal transactions, and token transactions for an address, as well as newly mined blocks. Confirmed coin, internal, and token transaction events also offer an each-confirmation variant that fires on every confirmation. For UTXO chains, callbacks report direction (incoming or outgoing) based on input/output address matching.

How are event notifications delivered, and are the callbacks secure?

Events are delivered as HTTPS POST callbacks (webhooks) to a URL you register. The callback URL must use HTTPS and match a domain you verify in the Dashboard beforehand. You can optionally set a callback secret key so each request carries an HMAC-SHA256 x-signature header you can verify, and every callback includes an idempotencyKey so you can safely deduplicate.

What happens if my callback endpoint is down when an event fires?

CryptoAPIs retries failed callbacks with exponential backoff. Each callback allows a 5-second response timeout, and up to 5 retries follow roughly a 5, 10, 20, 40, and 80-minute schedule. If all retries fail, every subscription sharing that event type and callback URL is marked disabled, so you should monitor delivery and re-activate subscriptions as needed.

Does the Prepare Transactions API support Solana or Bitcoin?

No. The Prepare Transactions endpoint is EVM-only, covering Ethereum and other EVM-based blockchains. There is no prepare route for Solana, Bitcoin, or other UTXO/non-EVM chains on this product.

Can I prepare ERC-20 token and NFT transfers, or only native coin transfers?

Yes, both. The Prepare Transactions API supports native EVM coin transfers as well as fungible token (ERC-20) and non-fungible token (NFT) transfers from any address. It builds the unsigned transaction payload ready for you to sign locally.

How do I go from a prepared transaction to a confirmed on-chain transaction?

Prepare the unsigned EVM transaction with Prepare Transactions, sign it, then submit it with the Broadcast Signed Transaction endpoint. You can also estimate gas costs beforehand using the EVM Blockchain Fees endpoint.

Can I estimate gas fees for an EVM transaction before sending it?

Yes. CryptoAPIs provides an EVM Blockchain Fees endpoint to retrieve current fee estimates so you can set gas parameters before signing and broadcasting. This pairs directly with the Prepare Transactions workflow.

Can I test what an EVM transaction will do before broadcasting it?

Yes. CryptoAPIs offers an EVM transaction simulation endpoint that lets you preview the outcome of a transaction before it is signed and broadcast. This helps you catch failures or unexpected results without spending gas on-chain.

What does the Verify Address / AML API do?

It provides two AML screening capabilities. Transaction screening (KYT) checks crypto transactions in real time so exchanges, PSPs, wallets and custodians can monitor activity as it happens, and address screening checks any wallet address against sanctions and fraud signals. Both return categorized compliance flags you can act on within your own workflows.

Does the AML API screen against OFAC, EU and UN sanctions lists?

Yes. Address screening checks crypto addresses against OFAC SDN, EU and UN consolidated sanctions lists. It also flags exposure to fraud-related categories such as phishing, ransomware, darknet markets and mixers.

Which blockchains does the address screening support?

The product advertises coverage across 35+ networks through a single REST endpoint, including Bitcoin, Ethereum, Polygon, BNB Smart Chain, Tron, Solana, Arbitrum, Optimism and Avalanche. One integration is meant to handle addresses across the supported chains.

Can I monitor transactions for compliance (KYT), not just addresses?

Yes. The Screen Transaction endpoint provides Know Your Transaction (KYT) checks for real-time monitoring, aimed at exchanges and custodians. This complements address screening so you can evaluate both counterparties and the transactions themselves.

Are screening calls logged for audit and compliance?

Yes. The product states that every screening call is logged and retrievable, which supports audit trails for regulatory reporting.