Compliance

Home
Getting started
- About Connect
- Basic principles
- Integration methods
- Operating models
  - Full service
  - Gateway service
- Go live
Payment methods
- By country
- By payment product
- Beta programs
Accepting payments
- Payment scenarios
  - One-off payment
  - Refunds and cancellations
  - Installments
  - Single-click payments
  - Recurring & Subscription
  - Merchant initiated transaction
  - Authorization reversal
  - Tokenization
    - Card on file
    - Account Updater batch
    - Account Updater token
    - Direct Debit mandate
- Compliance
  - Privacy and Data Protection
  - EU Accessibility Act and WCAG
  - PCI DSS
  - PSD2
  - Co-badged Cards Compliance
- Handling multiple currencies
- Fraud management
  - Address verification (AVS)
  - Bank account validation
  - Card-not-present fraud
  - Card verification value (CVV)
  - Device fingerprint
  - Fraud risk triggers
  - Fraud status codes
  - Test scenarios
  - --- Line separator ---
  - ACI Fraud Prevention
  - Cybersource Decision Manager
  - Microsoft Dynamics 365
  - 3D Secure
    - Dynamic 3D secure
    - 3D secure version 2
    - 2-step 3D secure
- Smart routing
- Mobile
  - Top 10 tips
  - Mobile payments
- Industries
  - Industries
  - Digital
  - Gaming
  - Retail
  - Travel
Testing
- Test card generator
- Sandbox access
- Test cases
After the payment
- Refunds
- Chargeback handling
  - Dispute
  - Soft descriptor
  - Return policy
Developer tools
- Two-factor authentication
- API Explorer
- Ordering of payment products
- Integration Dashboards
- Configuration Center
- Hosted payment pages
  - Shopping cart
  - Subscription details
  - Compliance
- SDKs
  - Mobile and browser SDKs
    - Android SDK
    - iOS SDK
    - Swift SDK
    - JavaScript browser SDK
    - Flutter mobile SDK
  - Server SDKs
    - Java SDK
    - PHP SDK
    - Node.js SDK
    - .NET SDK
    - Python SDK
    - Ruby SDK
    - Go SDK
- Full API references
  - Server API
  - Client API
- API versioning
- Error handling
  - Response codes
  - Error codes
  - Managing exceptions
  - Idempotent requests
- Webhooks
  - Event types
  - Event structure
- Plugins
  - Magento 2
    - Overview
    - Payment products
    - Requirements
    - Installation
    - Configuration
    - Workflow tips
    - Release notes
    - Troubleshooting
  - VTEX
Reporting
- Secure file transfer
Blog
- Trending
Support
- Release Notes
  - Highlights
  - REST API
  - MyCheckout Hosted Pages
  - Webhooks
  - Server & Client SDKs
  - Other
- Old release notes
  - Overview
- FAQ
- Contact
API Reference
- Boarding
- Merchant Boarding Portal
- Pre-production/sandbox access
- Configuration Center
- Payment Console
- Production
- Configuration Center
- Payment Console
- Insights
Switch color mode Theme

Results for

Results for Searching

We have upgraded the MyCheckout hosted payment pages to conform to WCAG 2.2 Level AA and EAA. As a result, the pages are:

Fully compliant with WCAG 2.1 Level AA,
And therefore fully compliant with Clauses 9.1 to 9.4 and Clause 9.6 of the EU Accessibility Act

In addition, MyCheckout hosted payment pages meet the following clauses of EU Accessibility Act:

Clause 5 (Generic Requirements): General accessibility principles are integrated throughout the design and technical development.
Clause 12 (Documentation and Support Services): Support materials and documentation are made available and in accessible formats.

Other clauses of the EAA, which are about voice communication, video content, hardware requirements, and emergency services, are not applicable to the hosted payment pages.