Skip to content

One simple layer for digital assets and payments

Manage crypto.Accept crypto.Keep it simple.

Your assets in one view, every status in plain words. Crypto payments for your product: one API call, a checkout page and signed webhooks.

  • Simple to use
  • Built for real products
  • No unnecessary complexity

Assets you can accept and manage

  • BTCBitcoin
  • ETHEthereum (ERC20)
  • USDCEthereum (ERC20)
  • USDTEthereum (ERC20)
  • LTCLitecoin
  • TRXTRON (TRC20)
  • USDTTRON (TRC20)

Everything in one view

Balances, pending amounts and history for every asset on one screen — with the network and status next to each number.

Built for action

Send and receive with the amount, the network fee and the destination in front of you before you confirm.

Simple integration

One POST creates a payment. Signed webhooks report the result. The docs take you from the first call to a confirmed payment.

Full payment control

One status per payment — the same on the checkout page, in the API and in your webhooks — so you always know what to tell your customer.

Two ways to start

For people. For business.

Different needs. One simple layer.

People get their crypto under control. Businesses get crypto payments without crypto complexity. Same account, same statuses, same numbers.

For people

Your crypto, under control.

  • See what you own, by asset and network
  • Send and receive with the fee shown first
  • Every status in plain words
Get started as a person

For business

Crypto payments, without crypto complexity.

  • One API call creates a payment
  • A checkout page your customer pays on
  • Signed webhooks report every status
Get started for business
POST /v1/invoices
POST /v1/invoices
{
  "amount": "49.90",
  "currency": "USD",
  "order_id": "10042",
  "return_url": "https://shop.example/thanks"
}

// 201 → { "id": "4e2b…", "status": "new", "checkout_url": "…/pay/4e2b…" }

Key features

Everything you need, without the complexity.

Asset management

Balances by asset and network, send and receive, full history with fees and transaction ids.

Payments for your product

Invoices for one-off amounts, static addresses for repeat customers. Priced in crypto or in fiat with the rate locked.

Real-time status

Payment detected. Waiting for confirmation. Payment confirmed. The same status on the checkout page, in the API and in your webhooks.

Developer friendly

OpenAPI document, typed TypeScript client, HMAC-signed webhooks with retries, an idempotency key on every POST.

A simple integration flow

From your product to crypto payments. In four steps.

  1. 1Your serviceCreates a payment with one API call
  2. 2CryptoLikeIssues the address and the checkout page
  3. 3CustomerPays from their own wallet
  4. 4Your serviceReceives a signed webhook and updates the order

Simple as that.

Built for builders

Integrate in hours, not weeks.

Three things to build: one POST to create a payment, a redirect to the checkout page, a webhook handler for the result. Addresses, confirmations and consolidation stay on our side.

  • API-first: one documented call per action
  • Signed webhooks with retries
  • Statuses named explicitly, terminal ones too
  • Built for product teams: test keys, typed client, OpenAPI
Read the docs
POST /v1/invoices
curl -X POST https://api.cryptolike.net/v1/invoices \
  -H "Content-Type: application/json" -H "Idempotency-Key: order-10042" \
  -H "X-API-Key: $KEY_ID" -H "X-Timestamp: $TS" -H "X-Signature: $SIG" \
  -d '{
    "amount": "49.90",
    "currency": "USD",
    "order_id": "10042",
    "return_url": "https://shop.example.com/orders/10042",
    "webhook_url": "https://shop.example.com/hooks/cryptolike"
  }'

FAQ

Questions, answered.

Which assets can I accept?

CryptoLike accepts Bitcoin, Litecoin, Ethereum (ERC20 tokens included) and TRON (TRC20 tokens included). The active catalogue is served by GET /v1/currencies; every asset shows its network and confirmation threshold before you use it.

How does a payment priced in fiat work?

You create the payment in USD or another enabled fiat currency. The exchange rate is locked the moment the coin is known — at creation, or when the payer chooses the coin on the checkout page — and stays fixed for the payment's lifetime. The payment stores the fiat amount, the locked rate and the crypto amount.

What if the customer pays less or more?

Less: the payment becomes underpaid, the page shows the remaining amount and the customer can top it up to the same address until the payment expires. More: the payment is paid, the whole sum is credited to you and the webhook carries overpaid_amount, so you can settle with the customer.

How do I learn that a payment is confirmed?

Subscribe a webhook endpoint: every event is signed with HMAC-SHA256 and retried with the same event id, so your handler can act once and ignore repeats. Or read GET /v1/invoices/{id} — status paid means the funds are confirmed and credited to your balance.

Do I need to run a node or hold keys?

No. You call the API and receive webhooks; addresses, confirmations, consolidation and payouts are handled by the platform. Payout addresses can be restricted to a whitelist and large payouts can require a second approval.

How are fees shown?

As a concrete amount with its unit before every action: in the payout estimate, in the API response and on the checkout page. The platform fee is set per asset and charged only when a payment is confirmed; see Pricing.

Is there a test mode?

Yes. CryptoLike keys prefixed ck_test_ work against a dev or stage instance on test networks. The reference signature vector in the docs tells you in one call whether your signing is right.

Invoice or static address — which one do I need?

An invoice is a one-off payment for a fixed amount with a time limit: an order, a top-up, a subscription charge. A static address is a permanent deposit address for one customer, where every incoming transfer is credited after the confirmations of that asset: balances, deposits, recurring funding. Both are created with one API call and report through the same webhooks.

How long does a payment take to confirm?

It depends on the asset: each one has a confirmation threshold set in the catalogue (GET /v1/currencies) and shown on the checkout page as “n of N confirmations, usually about X min”. The payer sees “Payment detected” as soon as the transfer is in the network, and “Payment confirmed” when the threshold is reached — at that moment the funds are credited to your balance.

Contact

Talk to us.

Tell us about your product and expected volumes, or ask anything about the integration. We reply by e-mail.

We reply by e-mail, usually within one business day. or write directly to hello@cryptolike.net

Ready to get started?

Start with simpler crypto.

Create an account, create a test key and make your first payment on a test network. The docs take you from the first call to a confirmed payment.