Update: Version 1.5.2
We’ve updated CryptoCash to make integrations more stable, notifications more convenient, and security noticeably stronger — without adding complexity to your workflows. In this article, we’ll cover what exactly has changed, why we made these updates, and what practical benefits businesses can get from them right now.
What’s new
Below are six key CryptoCash updates that directly impact transaction processing speed, integration control, and overall reliability.
1. Webhooks: transaction status updates delivered where it’s convenient for you
CryptoCash now supports webhooks for transaction statuses. The system automatically sends updates to your webhook URL — without the need to constantly request the status via the API.
This speeds up event processing and makes your integration more “event-driven”: you react to a change as it happens, rather than checking for it on a timer.
2. API Settings: platform-level control over API Keys
With this update, an API Key in CryptoCash is no longer just an “access key” — it’s a managed tool with clear boundaries.
You can define how a key should work in advance and reduce risk.
What you can now configure:
- key expiration date
- access only from specified IP addresses
- allowed actions (operations) that a specific key can perform
This approach is especially useful when keys are used across different services or teams: you can split permissions and restrict access without building workaround logic on your side.
3. Notification settings: less noise, more value
We added notification management because every team has a different working rhythm. Some teams need to receive everything, others only critical statuses, and some prefer no emails at all to avoid unnecessary noise.
Now, in your account settings, you can keep only what actually helps:
- email notifications
- dashboard notifications
- turning off what you don’t need
The idea is simple: notifications should support your processes, not interfere with them.
4. Active Currencies Telegram Bot: a quick answer to a daily question
One of the most common day-to-day scenarios in crypto processing sounds the same for everyone:
“Is this network available right now? Is this currency active?”
To solve this without manual checks or back-and-forth messaging, we’re opening public access to the CryptoCash Telegram bot for active currencies and networks.
It instantly reports changes and helps you quickly confirm the status of the currency you need — especially if you only monitor specific routes.
5. ED25519 instead of SHA256: a security upgrade
We’ve added support for ED25519 for signing and verifying data (primarily for webhook payloads). This is a move toward a more reliable cryptographic model for confirming request authenticity.
In simple terms: verifying that an event was truly sent by CryptoCash — and was not modified in transit — is now stronger and aligned with modern standards.
For integrations, this means lower risk and greater trust in automated processing flows.
6. Documentation updates
Documentation is part of the product — and we treat it the same way. Updates should exist not only in the UI and API, but also in clear instructions that help you implement changes quickly.
We’re making CryptoCash more convenient, controllable, and secure — without making things harder for teams that simply want to reliably accept and withdraw cryptocurrency via the interface and API.
If you’re already integrated, we recommend starting with two steps:
1) enable webhooks
2) configure API Keys based on your access model
If you’re only planning an integration, this is a great moment to build it “the right way” from day one — with proper security and automated status handling.
The documentation is already updated, and our support team is always available. If you need a quick walkthrough of webhook setup, key configuration, or signature verification — just message us or open the relevant section in the CryptoCash documentation.
