Skip to main content

Compliance & Security

Ottu maintains the highest security certifications in the payment industry. This page covers what those certifications mean for your business and how to request compliance documentation.

PCI DSS Level 1

The Payment Card Industry Data Security Standard (PCI DSS) is the global security standard for any organization that handles credit card data. There are four compliance levels — Level 1 is the most stringent.

What Level 1 Means

  • Annual on-site security assessment by a Qualified Security Assessor (QSA)
  • Quarterly network vulnerability scans by an Approved Scanning Vendor (ASV)
  • Annual penetration testing
  • Continuous monitoring of all systems that store, process, or transmit cardholder data

How This Protects Your Business

When you use Ottu's hosted checkout page or Checkout SDK, card data never touches your servers. Customers enter their card details directly on Ottu's PCI-certified infrastructure. This significantly reduces your own PCI compliance scope:

Integration MethodYour PCI ScopeWhat It Means
Hosted Checkout (redirect)SAQ ASimplest — you don't handle any card data
Checkout SDK (embedded)SAQ A-EPCard data passes through Ottu's SDK, not your servers
Direct API (server-to-server)SAQ DFull PCI compliance required on your side
tip

Most merchants use the Hosted Checkout or SDK approach, which keeps their PCI burden minimal. See the Developer Documentation for integration options.

ISO 27001

ISO/IEC 27001 is the international standard for Information Security Management Systems (ISMS). It covers:

  • Risk assessment and treatment
  • Access control and identity management
  • Business continuity and disaster recovery
  • Incident management and response
  • Physical and environmental security
  • Supplier relationship security

What This Means for Merchants

Ottu operates under a formally audited security management framework. Every process — from how code is deployed to how data is stored — follows documented, reviewed, and certified procedures.

Data Security Practices

PracticeDetail
Encryption in transitTLS 1.2+ for all API and dashboard connections
Encryption at restAES-256 for stored data
TokenizationCard numbers replaced with tokens — original PAN never stored on merchant systems
Access controlRole-based access with multi-factor authentication
MonitoringReal-time security monitoring and anomaly detection
Incident responseDocumented incident response plan with defined notification timelines

Requesting Compliance Documentation

Merchants can request the following documents for their own audits, procurement processes, or customer assurance:

DocumentDescriptionHow to Request
Attestation of Compliance (AoC)PCI DSS Level 1 compliance attestationContact your account manager
ISO 27001 CertificateCurrent ISO 27001 certificationContact your account manager
Security QuestionnaireSIG, CAIQ, or custom questionnaire completionEmail [email protected]
Penetration Test SummaryExecutive summary of latest penetration test (under NDA)Email [email protected]
Data Processing Agreement (DPA)GDPR-compliant data processing termsEmail [email protected]

Frequently Asked Questions

Do I need my own PCI DSS certification?

It depends on your integration method. If you use Ottu's Hosted Checkout or SDK (recommended), your PCI scope is minimal (SAQ A or SAQ A-EP). If you handle card data directly via the API, you'll need full PCI DSS compliance (SAQ D).

Where is my data stored?

Ottu's infrastructure is hosted in secure, certified data centers. Contact your account manager for specific data residency information relevant to your region.

What happens during a security incident?

Ottu follows a documented incident response plan. Affected merchants are notified within the timelines specified in their service agreement. The incident response team investigates, contains, and remediates the issue, followed by a post-incident review.

Can I get a copy of the penetration test results?

Yes — an executive summary of the latest penetration test is available under NDA. Contact [email protected].

What's Next?