Click to Pay CX Guidelines v1.1

October 2024

The EMV® Secure Remote Commerce – Click to Pay CX Guidelines (“guidelines”) provide EMVCo’s requirements and best practices for creating the best Customer Experience (CX) across key Click to Pay moments. The guidelines are a single source of truth that enable merchants and payment service providers (PSPs) implementing a Click to Pay solution to provide a consistent checkout experience.

The CX patterns, key customer interactions, example flows and resources have all been informed and validated through independent consumer research. The patterns have been designed with accessibility in mind and to meet Web Content Accessibility Guidelines (WCAG) and Level AA Conformance.

Flow Diagram

Use the interactive flowchart to understand where API/SDK calls can be made and how patterns can be applied throughout the customer journey in different checkout environments.

Full flow diagram

Scope, Constraints & References

Scope

The Guidelines are intended for merchants and payment service providers (PSPs) that are implementing Click to Pay solutions. They are based on the following assumptions:

  • The Guidelines are not intended to provide context for all scenarios or use cases, and individual SRC Systems are responsible for creating implementation instructions for their SRC System Participants
  • They do not preclude an SRC System from providing additional technical components to support their implementations

Constraints

The SRC Specifications are designed to work within a number of constraints of the payment ecosystem, including roles of various entities, transaction flows, and associated payment use cases. These constraints include, but are not limited, to the following:

  • The SRC Specifications or any implementation of the SRC Specifications are not intended to replace or interfere with any international, regional, national or local laws and regulations; those governing requirements supersede any industry standards
  • An entity providing SRC payment authorisation capability must be cognisant of the payment processing environment in which that service is provided, and ensure that the introduction of SRC does not have an adverse effect on existing processes
  • The SRC Specifications do not prescribe any single implementation approach, but describe functions and protocols and the interactions between an SRC System and its SRC Participants

References

The SRC Specifications describe a common baseline set of roles and associated functions for SRC that can be adopted to meet the unique payment ecosystem requirements of international, regional, national or local implementations.

The SRC Specifications are located at www.emvco.com and include:

  • SRC Core Specification: EMV® Secure Remote Commerce Specification
  • SRC Reproduction Requirements: EMV® Secure Remote Commerce (SRC): Click to Pay Icon Reproduction Requirements
  • SRC API: EMV® Secure Remote Commerce Specification – API
  • SRC JavaScript SDK: EMV® Secure Remote Commerce Specification – JavaScript SDK
  • SRC Version Management: EMV® Secure Remote Commerce Version Management for SRC API and JavaScript SDK Specifications
  • Guidelines: EMV® Click to Pay CX Guidelines (this document)

EMV® Secure Remote Commerce Use Cases is an informational supplement to the SRC Specifications. It describes common use case examples and is intended to be read in conjunction with the SRC Specifications.