Trust · Security & Privacy
How transaction records, access, and notifications are protected.
Security is described by the controls we actually run, not by badges. This page lists what is enabled today for ArosaPay accounts and merchant APIs.
Access
Merchant and admin sessions are backed by ArosaPay authentication with per-origin storage and session timeouts.
Multi-factor authentication is available for merchant accounts and required for admin accounts on sensitive actions.
Admin capabilities are governed by role-based permissions with sensitive-action gating.
Sign-up and password changes screen against known compromised credentials.
Records
Buyer, merchant, and admin data access is enforced at the database row level with policies scoped to identity.
Sensitive admin actions are recorded with actor, action, and target for later review.
Webhook security
Every outbound webhook carries X-ArosaPay-Signature and X-ArosaPay-Timestamp for verification and replay protection.
Events carry X-ArosaPay-Event-Id so merchants can deduplicate retries safely.
Data handling
Personal data is collected for account creation, KYC, and dispute handling. Handling is described in the privacy policy.
Access to personal data by internal reviewers is dual-controlled and logged for forensic review.
What we do not claim
No badges we haven't earned.
This page lists controls that are actually enabled. It does not assert regulatory certifications or partnerships that have not been publicly confirmed.
Read the privacy policy