Security is part of how Anakalice is built.
Payments require more than an API that works. Anakalice is designed with controls for protecting credentials, separating merchant data, preventing duplicate transactions and handling payment failures safely.
The protections in place today.
Separated merchant data
Every request is limited to your own business. One business can never see another's data.
Protected credentials
Your provider keys are encrypted before they are stored and are only used at the moment a payment is made. They are never shown back to you.
Signed payment updates
Updates from providers are checked for authenticity, and the updates we send you are signed so you can verify them.
No duplicate transactions
Repeated or replayed messages are recognised and ignored, so a payment is never processed twice.
Safe outbound requests
When Anakalice sends you a notification, it checks the destination first to prevent misuse.
Encrypted connections
All traffic is served over HTTPS with modern transport security.
Careful live activation
Live processing is blocked by default and only enabled once the required checks pass.
Activity records
Sensitive actions are recorded so activity can be reviewed. Records never include secret values.
Backups and checks
Data is backed up with a tested restore process, and payments are regularly checked against provider records.
Test and live, kept apart on purpose.
Build and test in a free sandbox. No real money moves.
Live processing is switched on only after you complete verification and your provider is ready. It stays off by default.
The policies that govern using Anakalice.
Available to merchants as part of onboarding.