Skip to content
Security & privacy

How PayXa handles devices, permissions, data and verification, written in plain language.

01Security & trust

That one rule shapes everything we build. Here is how PayXa protects merchants, customers and their money.

No badges until they are real. Bank partnerships, certifications and regulatory approvals will be shown here only once they actually exist.

Device pairing

Phones pair only via a short-lived dashboard QR. Each device has its own revocable credentials.

Permission transparency

Notification access is requested separately, explained in plain language, and only payment alerts are processed.

Sensitive data handling

We never ask for or store UPI PINs, OTPs or bank passwords. No SMS history or inbox scanning in V1.

Trusted verification

A notification alone can never mark a payment verified. Verified needs a trusted bank or PSP source.

Signed webhooks

HMAC-SHA256 signatures, timestamps, replay protection, retries with backoff and a dead-letter queue.

Account security

Two-factor sign-in, biometric app lock, role-based team access and full audit logs.

Key management

Separate test and live keys, rotation without downtime, and secrets encrypted at rest.

Disputes & reconciliation

Every state change is traceable. Conflicts go to review instead of being auto-resolved.

What the merchant app can access

  • Push notifications to show checkout and payment alerts.
  • Notification listener, approved separately, used only to read supported payment alerts. Everything else is ignored.
  • Camera, only while you scan the pairing QR.
  • Biometrics, where supported, to lock the app.
  • Internet and secure storage for syncing and an encrypted offline queue.

What PayXa never does

  • Ask for, read or store UPI PINs, OTPs or bank passwords.
  • Scan your Gmail inbox or SMS history in V1.
  • Mark a payment verified from a phone notification alone.
  • Hold, pool or settle customer funds.

Regulatory position

PayXa is designed as a direct-to-merchant payment technology platform that does not handle funds. That design may reduce regulatory complexity, but it is not an automatic approval or exemption. Exact service classification, UPI acceptance permissions and acquiring-bank agreements are under professional review. We will publish certifications and partnerships here only once they actually exist.

Report a vulnerability

Found something? Please contact us through the contact page with the subject "Security". Please do not test against real merchant accounts.

Get started

Join the sandbox today. Build your integration while we complete partner and compliance reviews for live payments.