Protecting access
Deployments should give each operator the access needed for their role and restrict higher-risk actions such as configuration changes, refunds and administrative review. Merchants remain responsible for user lifecycle, device custody and password hygiene under their agreement.
Protecting communication and records
The public website uses HTTPS. Product deployments are planned around protected communication, transaction references, visible status and records that support investigation and reconciliation. Exact storage, backup and retention arrangements depend on the contracted configuration.
Updates and resilience
Security and reliability depend on supported devices, timely software updates, tested offline recovery and a clear escalation route. Partners and merchants should keep operating systems current, protect local networks and report abnormal behavior promptly.
No unsupported certification claims
This page does not claim a particular security certification, penetration-test result or regulatory approval. Ask us for the current security and architecture information relevant to your proposed deployment.
Report a concern
Send a concise description, affected URL or product area, reproduction steps and safe supporting evidence to info@datamega.net. Do not access data that is not yours, disrupt a merchant or publicly disclose an unresolved issue before we have had a reasonable opportunity to investigate.
Need a clear answer for your deployment?
Tell us what you are evaluating and which country or merchant setup is involved.
Contact EazSell