Digital Banks

Financial institutions need to build reliable, scalable solutions and get them to market fast. Crypto APIs endpoints and secure tools provide a simple and cost-effective way for businesses to diversify their digital offerings, enter the blockchain, and future-proof their business model without reinventing the wheel.

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 add digital assets to a bank

1

Keep keys inside the bank

Derive addresses from an xPub so private keys never leave your perimeter.

2

Meet the screening requirement

Sanctions and AML screening on counterparties before funds move.

3

Record every movement

Full transaction history per address, for audit and reconciliation.

4

Settle under dual control

The API prepares; your systems sign; we broadcast and confirm.

You might also be interested in

Broadcast Transactions
Verify Address
HD Wallets Management
Node as a Service
AI Compatibility

Frequently Asked Questions

Verify Address

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.

Which blockchains does the Crypto APIs HD Wallets Management (xPub sync) API support?

The HD Wallet (xPub/yPub/zPub) sync API supports the EVM chains (such as Ethereum, Ethereum Classic, BNB Smart Chain, Tron), the UTXO chains (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash), and XRP. You import an extended public key and Crypto APIs derives and syncs its addresses and transactions for you.

Does the HD Wallets Management API support Solana?

No. HD wallet (xPub/yPub/zPub) sync is not available for Solana. HD wallet coverage is limited to the EVM chains Ethereum, Ethereum Classic, BNB Smart Chain and Tron, the six UTXO chains (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash) and XRP. Solana is supported by other Crypto APIs products such as transactions data and blockchain events, but not by the HD wallet endpoints.

What can I do with a synced xPub through the HD Wallets API?

Once you sync an extended public key you can list all your synced HD wallets, pull the wallet's aggregated assets and balances, retrieve wallet details, and list the wallet's transactions across all derived addresses through a single integration. The sync monitors every derived address for you, so you do not have to track individual addresses manually. Syncing and deleting an xPub each carry a subscription cost, and monitored addresses incur a daily monitoring tax.

Can I derive addresses from an xPub without calling the API or exposing keys?

Yes. Crypto APIs provides address-derivation utilities in the blockchain tools family that generate child addresses from an extended public key for EVM chains, the UTXO chains and XRP. Because HD wallets use extended public keys, derivation and wallet syncing never require your private keys. This lets you generate deposit addresses and reconcile them against a synced wallet.

Is there a free tier, and how is HD wallet usage billed?

Every API request consumes credits, with the exact amount returned in the x-credits-consumed response header and the cost varying by endpoint and blockchain. HD wallet asset and transaction reads on UTXO chains are among the heavier calls (roughly 520-530 baseline credits), and a synced xPub also adds a per-subscription cost plus daily monitoring taxes per derived address. After your monthly credit allocation is exhausted, usage continues automatically under pay-as-you-go billing. The marketing page does not state a specific free-tier allowance.

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.