Skip to content
Cliq

Explore

HomeDevelopersResourcesAbout UsCareersTrust Center

Who we serve

MerchantsISVs & PlatformsAgents & ISOs

Solutions

Payment ProcessingACH ProcessingTreasury & ReconciliationChargeback ManagementPrepaid Card ProgramsLendingCustom Payment Solutions

Products

Pay by CliqPayment GatewaysHosted Payment PagesPOS HardwareInvoicingAccounting IntegrationsTips by Cliq

Case studies

All Case StudiesCampGroupConcordia CollegeLendistryProspect Medical HoldingsRare Collectables

Newsroom

All NewsWhat is Agentic Commerce? Inside the Infrastructure Powering AI‑driven PaymentsHow to Reduce Chargebacks: A Merchant's PlaybookU.S. District Court Rules For Cliq in Hearing Regarding Federal Trade Commission FilingCliq Launches New Embedded Lending Solution Powered by JarisCliq Partners with Gymdesk to Revolutionize Payment Processing for Gyms and Fitness Studios WorldwideCliq’s Latest Offering Delivers Seamless Payment Processing from Businesses’ Existing Accounting SoftwareCliq Shakes Up The Auto Industry In A Partnership With Dealer Controlled SolutionsCliq Names Joanna Oliva As Company PresidentCliq Announces New Partnership with PathwardCliq Announces New Relationship with Fifth Third BankCliq Partners with Checkout ChampCliq Partners with Konnektive CRM

Contact & policies

Contact UsMerchant ApplicationPrivacy PolicyAccessibilityReport an Accessibility IssueCard Holder Policy (PDF)

Accessibility statement

Built for everyone who moves money.

Cliq wants every merchant, partner and developer to be able to use cliq.com, whatever technology or ability they bring to it. This page explains the standard we build to, what we have done so far, where we still fall short, and how to reach us when something gets in your way.

Last reviewed September 13, 2026.

Our standard

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.0 at Level AA across cliq.com. Where a newer guideline goes further, we follow it when we can, but Level AA of WCAG 2.0 is the bar we test against and hold ourselves to.

What we have done

  • Every page has one clear heading structure, a page title, landmarks, and a “Skip to content” link as the first Tab stop.
  • All text meets the 4.5:1 contrast minimum, and large headings meet 3:1, on every background we use.
  • Everything works with a keyboard alone: menus open and close (Escape returns focus), carousels, tabs and pills are real buttons, and focus is always visible.
  • Moving content can be stopped: the homepage video and the terminal-brand ticker each have a pause control, and neither starts when your device asks for reduced motion.
  • Forms have visible labels, clear error messages announced to screen readers, and no time limits.
  • Images that carry meaning have text alternatives; decorative artwork is hidden from assistive technology.
  • Text can be resized to 200% and the layout reflows on any screen width without sideways scrolling.
  • An automated WCAG 2.0 A/AA check (axe-core) runs on every route before a release.

Known limitations

  • Portals we link to for signing in (Pay by Cliq, Cards by Cliq) are separate applications with their own accessibility work; if you hit a barrier there, tell us and we will pass it on.
  • Some downloadable documents, such as programme PDFs, were produced before this standard was adopted and may not be fully tagged for screen readers. We can supply an accessible copy on request.
  • Illustrated hero scenes sit behind some headings; we keep the text on solid or veiled ground, and we are reviewing every page by eye in addition to the automated checks.

Tell us about a barrier

If any part of cliq.com is hard to use, we want to know. The report form asks for the page, what you were trying to do, and the browser and assistive technology you use; a member of the team reads every report and replies within two business days when you leave an email.

How this statement was prepared

This statement was prepared on September 13, 2026 from an automated axe-core audit of every page, a keyboard walkthrough, and a review of colour, motion and form behaviour against each WCAG 2.0 Level AA success criterion. It is updated whenever the site changes in a way that affects accessibility.