Skip to content

Security notices

Security and fraud notices

Use this channel if you suspect unauthorized access to your merchant account, phishing that impersonates Perper Pay, or incorrect payment authorizations. Payment-service complaints against an authorised institution follow that institution’s process once live fiat is enabled under a partner.

What to report

  • Unexpected login, PIN or secret-reveal prompts you did not initiate.
  • Payments or withdrawals you did not authorize (amount and payee confirmation on /pay is the dynamic-linking step).
  • Emails, SMS or sites asking for your project secret or session credentials.

What we record for oversight

  • Payment authorization records include event, time, IP, truncated account id, project id, amount, opaque order reference, and truncated browser agent — never passwords, PINs or tokens.
  • Signed-in merchants can review their recent rows under Payments → Authorization audit.
  • When durable host logging is enabled, the same evidence is retained for operational review.

How to contact us

  • Email security@perper.net for security / fraud notices (technology layer).
  • Email complaints@perper.net or use /complaints ticket intake (case ID + SLA clocks) for payment-service complaint timelines.
  • If funds are at risk under a live partner arrangement, also notify the authorised institution immediately.

What this is not

  • PIN is device/session step-up. Authenticator TOTP 2FA is available under /app/security (enroll + challenge after login). WebAuthn/hardware keys remain deferred.
  • Not CBCG-licensed payment-service supervision; Perper is the technology provider.

Security contact

security@perper.net

Acknowledgement targets follow the ICT diligence pack proposed defaults until contracted under heads of terms.