X9 Payment QR

Overview

The ASC X9 Payment QR Code Standard is a U.S. effort to define a single, rail-agnostic QR code format for payments, led by the Accredited Standards Committee X9, Inc. (X9) — the ANSI-accredited standards body for the U.S. financial-services industry. The effort was launched on August 13, 2024 by X9's X9A4 workgroup ¹³. The goal is to "establish the content of a QR code for payments," emphasize interoperability, and cover both merchant-presented and consumer-presented QR codes, so that all information needed to execute a payment is encoded "without the customer or merchant having to share financial account details" ¹³. The QR payload uses EMV-formatted data, a CRC checksum, and a digital signature for authenticity, and is designed to route over multiple instant rails rather than only card networks ².

History

X9 is the ANSI-accredited standards committee for U.S. financial services. On August 13, 2024 X9 announced that it had begun work on a new QR code payments standard, citing the need to "accelerate the adoption of instant payments," which in the United States lags many other countries ¹³. The standard is being developed by the X9A4 workgroup, the QR-code standards work group responsible for standardizing QR code payments ¹. In parallel, X9 published a related security standard, X9.148, "QR Code Protection Using Cryptography," on January 7, 2025, which guides the financial-services industry in deploying cryptography to create trusted, secure QR codes and complements the ongoing payment-content standard ⁴. X9 has indicated it intends to submit its specification to the International Organization for Standardization (ISO) for possible global adoption after industry review ⁵.

Technical specification

The standard encodes payment data in a structured, EMV-formatted QR payload ². EMV QR data uses a TLV (tag-length-value) structure — for example the data object 000201 represents Tag 00, Length 02, Value 01 ⁶ — so the X9 code inherits the same field-grammar used by the EMVCo Merchant-Presented Mode QR specification.

Security is layered on top of the EMV payload:

• A CRC checksum detects basic corruption or tampering at the EMV level ².
• A digital signature verifies authenticity; signatures rely on digital certificates issued by the X9 Financial PKI rather than platform-specific keys ².

The code carries structured payment data including amount, merchant, payment reference and more, and defines four QR-code lifecycle statuses — Active, Initiated, Paid, Cancelled ².

Rail-agnostic routing. The standard is explicitly rail-agnostic: a participating bank, wallet or app can scan and process the payment over FedNow, RTP, ACH credit push, or push-to-card, and it is described as "fully capable of supporting payments over SEPA Instant" as well ². Because the payload carries no raw account credentials, settlement occurs over the chosen rail without exposing account details ¹².

Use cases

The standard targets both merchant-presented (static or dynamic merchant code at point of sale) and consumer-presented codes ¹, aiming at "the last mile" of instant-payment adoption at the U.S. point of sale. By riding FedNow, RTP, ACH or push-to-card, it supports bill pay, in-store and online merchant payments, and account-to-account transfers, all from a single scannable artifact. An early demonstration was shown with Star One Credit Union and Payfinia over the FedNow network ².

Implementations

There is no public, official reference encoder/SDK for the X9 Payment QR Code Standard; the specification is distributed through X9 rather than as open source. Because the payload is EMVCo-style TLV, general-purpose EMV QR tooling can parse the underlying field structure, but the X9-specific signature and PKI layer require X9 Financial PKI certificates and are not covered by public libraries ². The only demonstrated implementations to date are vendor pilots such as the Payfinia / Star One Credit Union demo over FedNow ².

Comparison

Where FedNow and the RTP network are the underlying settlement rails, the X9 Payment QR Code standard is a presentation/initiation layer that sits above them: one scanned code can be routed over FedNow, RTP, ACH credit push or push-to-card ². It is conceptually similar to EMVCo's Merchant-Presented Mode QR (and reuses its EMV-TLV grammar) but adds a CRC plus a digital signature backed by the X9 Financial PKI for authenticity, and is designed to be rail-agnostic rather than card-centric ²⁶. The related X9.148 standard provides the cryptographic-protection framework for QR codes generally ⁴.

Fun facts

• X9 launched the effort partly because U.S. instant-payment adoption "lags far behind many other countries," and a standardized payment QR is meant to close that "last mile" at the point of sale ¹.
• The QR's authenticity rests on certificates from the X9 Financial PKI rather than device-platform keys such as wallet passkeys ².

Status

In development / early deployment. The content standard was launched by the X9A4 workgroup on August 13, 2024 ¹, with the companion cryptographic-protection standard X9.148 published January 7, 2025 ⁴. As of mid-2025 the standard had been demonstrated in vendor pilots (Payfinia / Star One Credit Union over FedNow) ², and X9 plans to submit the specification to ISO for potential global adoption ⁵.

Sources

1. X9 Launches Effort to Create Payment QR Code Standard — Businesswire, 2024
2. X9 Payment QR Code Standard — Matera, 2025
3. X9 To Develop New QR Code Payments Standard — Digital Transactions, 2024
4. X9 Publishes Standard for QR Code Protection Using Cryptography — Businesswire, 2025
5. ASC X9 Webinar — Introduction to QR Code Payments — Accredited Standards Committee X9
6. EMV QR Hub — EMV TLV structure — EMV QR Hub

Deployments

No country reports mention this standard by name.