WooCommerce
- Plugin (.zip) — The archive is published with the next release — the guide explains installing from the repository.
Integrations
Accept crypto the way you already sell.
Pick how your business sells today. Every path ends the same way: a confirmed payment and an order status your team can act on.
Path 1 of 5
A plugin for your shop's CMS
Checkout gets a «Crypto» payment method; the plugin creates the payment, sends the customer to it and moves the order when the payment is confirmed.
Who it is for
Online shops on WooCommerce (WordPress), OpenCart 3.0 or 4.0, PrestaShop 1.7.8 or 8, Magento 2.4.6+. You install it like any other payment plugin.
What you need
- Admin access to the shop, served over https.
- An API key with two permissions: create_invoice and read.
- A webhook endpoint in the cabinet for the plugin's URL, and its secret.
Steps
- Download the archive for your CMS below and upload it in the shop's admin panel.
- Ask CryptoLike support for access to the test environment: in its cabinet create a ck_test_ API key with create_invoice and read; its API URL is the test API URL.
- Switch on test mode, paste the key ID, the secret and the test API URL into the plugin settings and press «Check connection».
- Copy the webhook URL from the plugin, add it as a webhook endpoint in the cabinet with every invoice event, and paste the endpoint secret back into the plugin.
- Place a test order and pay it on a test network. Then switch test mode off, restore the default API URL and paste a live key.
What the customer gets
At checkout the customer chooses «Crypto» and lands on the payment page: asset and network, the amount to send, address with a QR code and the time left. After payment they return to your order page.
Statuses and webhooks
Paid → the order moves to the status you chose (Processing by default). Payment detected → the order keeps waiting. Expired → cancelled, or left pending if you prefer. Late and partial payments are held for your decision. Each webhook is signature-checked and applied once.
Guides and downloads
OpenCart
- OpenCart 3.0 (.ocmod.zip) — The archive is published with the next release — the guide explains installing from the repository.
- OpenCart 4.0 (.ocmod.zip) — The archive is published with the next release — the guide explains installing from the repository.
PrestaShop
- Module (.zip) — The archive is published with the next release — the guide explains installing from the repository.
Magento 2
- Composer package (.zip) — The archive is published with the next release — the guide explains installing from the repository.
- app/code archive (.zip) — The archive is published with the next release — the guide explains installing from the repository.
Path 2 of 5
A shop on Хорошоп
Хорошоп does not take third-party payment plugins, so CryptoLike connects to the shop from our side through its API.
Who it is for
Shops on the Хорошоп platform that sell in hryvnia and want crypto as one more payment method — without a developer.
What you need
- A Хорошоп plan with API access and a separate admin account for CryptoLike.
- A payment method «Cryptocurrency» of the simple type in your shop.
- Prices in a currency CryptoLike accepts — USD, EUR, UAH, GBP or CAD, all enabled by default; nothing to request from support.
Steps
- In Хорошоп create an admin account only for CryptoLike.
- Add the payment method «Cryptocurrency» and say in its description that the payment link arrives by e-mail.
- In the cabinet open Integrations → Хорошоп, enter the shop domain, login and password, press «Check».
- Choose the payment method and the order statuses for paid and expired payments. Save.
- Place a test order and follow it in the sync log.
What the customer gets
Within about a minute of the order the customer gets an e-mail from CryptoLike with your shop's name, the order number, the amount and a link to the payment page.
Statuses and webhooks
Paid → the order is marked paid and gets your status (В обробці by default). Expired or cancelled → your status (Не доставлено by default), or no change. Every step is in the cabinet's sync log. No webhook setup is needed.
Guides and downloads
Path 3 of 5
Your own site or app: API and SDKs
From API call to payment status: one POST creates the payment, the payment page collects it, a signed webhook tells your server.
Who it is for
Teams with their own backend — marketplaces, SaaS, games, services with a custom checkout or a mobile app with a server.
What you need
- A server that keeps the secret — never a browser or a mobile app.
- An API key: create_invoice and read (plus create_address for permanent deposit addresses).
- An https endpoint for webhooks.
Steps
- Ask CryptoLike support for access to the test environment, create a ck_test_ API key in its cabinet and point your server at its API URL.
- Install the SDK for your language, or sign requests yourself (HMAC-SHA256).
- Create a payment: POST /v1/invoices with amount, currency and your order_id.
- Send the customer to checkout_url, or embed the page with the widget.
- Handle invoice.* webhooks: verify the signature, skip repeats by event_id, answer 2xx.
- Go through the go-live checklist and switch to a live key.
What the customer gets
The payment page with your name and logo: asset and network, the amount to send, address with a QR code, the time left and a status that updates live.
Statuses and webhooks
new → pending → paid. underpaid, expired and cancelled each come with a next step for the customer. Webhooks are signed, retried with backoff and carry an event_id for deduplication.
Guides and downloads
HTTP API
TypeScript / Node.js
npm install @cryptolike/sdkPre-release: until the package is published, install from the repository — see the guide.
Python
pip install cryptolikePre-release: until the package is published, install from the repository — see the guide.
Go
go get github.com/Petya88/Cryptolike/sdk/goPre-release: until the package is published, install from the repository — see the guide.
PHP
composer require cryptolike/sdkPre-release: until the package is published, install from the repository — see the guide.
Path 4 of 5
A payment link, no code
Create a payment in the cabinet or in Telegram, send the link, see when it is paid.
Who it is for
Freelancers, B2B invoices, sales in messengers and social networks — whenever there is no checkout to integrate.
What you need
- A CryptoLike account; payment links need no account verification.
- Optional: the CryptoLike Telegram bot linked to your account.
Steps
- In the cabinet open Invoices → Create payment: amount, currency and a description the customer will see.
- Share the link — copy it or send it straight to a messenger. In the bot the /invoice command does the same.
- Follow the status in the cabinet or get a Telegram message when the payment is confirmed.
What the customer gets
The same payment page as online shops use: amount, network, address, the time left and a live status.
Statuses and webhooks
Every status is in the cabinet and in notifications. Webhooks are optional here — add an endpoint only if another system needs the result.
Guides and downloads
Cabinet
Telegram bot
Path 5 of 5
Payment inside your page: the widget
The customer stays on your checkout: the payment page opens in a frame in your layout, in your theme and language.
Who it is for
Sites with their own checkout that do not want to send the customer to another page.
What you need
- A server that creates the payment (API, SDK or a plugin) — the widget only shows it.
- Your site's origin in the allowed list: cabinet → Settings, the Integration card, Allowed origins.
- A Content-Security-Policy on your page that allows the script and the frame.
Steps
- Add your site's origin to the allowed list in the cabinet.
- Create the payment on your server and pass only the invoice id to the page.
- Load /widget/v1/cryptolike.js and call CryptoLike.mount(element, { invoiceId }).
- Use the paid and expired events to update your interface; confirm the order from the webhook.
What the customer gets
The payment page inside your checkout. It resizes with its content and follows your accent colour and language.
Statuses and webhooks
Events on the page are for the interface only. The order is confirmed by the signed webhook or by GET /v1/invoices/{id} from your server.
Guides and downloads
Checkout widget
Compare the ways
Time to launch assumes a test payment before going live; payouts also need a verified account.
| Way | Time to launch | Developer needed? | Customisation | Where the payment happens |
|---|---|---|---|---|
| CMS plugin | 30–60 minutes | No | Order statuses, expiry behaviour, checkout texts | CryptoLike payment page |
| Хорошоп connector | About 15 minutes | No | Order statuses, e-mail language, shop name | CryptoLike payment page, link by e-mail |
| API or SDK | 1–3 days | Yes, back end | Full: your flow and data around the payment | CryptoLike payment page or embedded |
| Payment link | 5 minutes | No | Amount, currency, description | CryptoLike payment page |
| Widget | A few hours on top of the API | Yes, front end | Placement, theme, accent colour, language | Inside your page |
Before you launch
The same four things apply to every path except the payment link.
API key
Developers → API keys. ck_test_ keys go with test networks and are refused on mainnet (401 auth.test_key); ck_live_ keys move real funds. Give a key only what it needs: a shop never needs withdraw.
Webhook secret
Every endpoint has its own secret, shown once. Check X-Signature over the raw body and refuse events whose timestamp is more than 5 minutes off your clock.
Test mode
A ck_test_ key with the test API URL from CryptoLike support runs the same flow on test networks — test coins have no value. Pay one order, underpay one, let one expire.
Go-live checklist
- The live key sits in the server's environment, not in code or in a browser.
- The webhook endpoint is on https and subscribed to every invoice.* event.
- The signature is checked and repeated events are skipped by event_id.
- Orders change status only from the webhook or the API — never from the return page.
- One paid and one expired test payment went through end to end.
- Someone on the team receives notifications about payments that need a decision.
Start with a test key.
Create an account, get the test environment from support and make the first payment on a test network with a ck_test_ key.