This edition of the PCE Product Update summarizes the major product enhancements, launches, and platform updates delivered across PCE during Q2 2026. This quarter, we launched our flagship drop-in payment experiences — Priority Checkout and Priority Vault — expanded into the Canadian market, and strengthened fraud and mobile checkout capabilities across both widget and direct API paths.

Key Updates

Priority Checkout & Priority Vault — Branded, Drop-In Payment Experiences

Two new embeddable components that bring fully branded, PCI-compliant payment experiences to your application in minutes — no custom payment form, no PCI burden.

Priority Checkout and Priority Vault are new Ready-to-Launch components designed to give merchants the speed and security of a hosted payment experience with the brand control of a custom build:

• Priority Checkout is a fully branded, drop-in payment widget that securely captures card and ACH bank account details inside Priority's PCI-compliant hosted environment. It includes real-time card and account validation, address autocomplete, card brand identification, multi-currency support, and an optional save-for-future-use experience.
• Priority Vault is the tokenization widget that lets customers securely store and manage their cards and bank accounts for recurring payments, subscriptions, and faster future checkouts.

Both components are fully responsive, brand-customizable, and powered by Priority's secure session-based architecture — keeping raw payment data off merchant servers and dramatically reducing PCI compliance scope.

Key aspects

• Audience: SaaS platforms, marketplaces, ISVs, and enterprise merchants who want a branded payment experience without building or maintaining custom payment forms or carrying PCI burden in-house.
• Why it matters: Merchants get a production-grade, branded payment experience in days instead of months — with zero PCI scope on their servers, built-in fraud and validation features, full brand customization, and tokenized save-card / save-bank capabilities ready out of the box.

Technical details

• Session model: Your backend creates a short-lived clientSecret via POST /client-secrets, specifying widgetType: "CHECKOUT" or widgetType: "VAULT" along with businessId. The secret is passed to the frontend and consumed by the widget on initialization.
• Event callbacks: onSuccess returns the transaction (Checkout) or card/bank reference (Vault) outcome — PAYMENT.CREATE, CARD.UPDATE, CARD.DELETE. onError returns a structured payload (code, type, message, details). onChange fires on field-level changes (e.g., card brand detection, surcharge updates). onComplete fires when the session is fully closed.
• Payment methods supported: Priority Checkout supports Card and ACH bank account payments. Priority Vault supports Card and ACH bank account tokenization.

API Reference → Create a new payment or refund

Available on: These flagship components are available for merchants integrating with Priority's Ready-to-Launch Solutions — Priority Checkout for branded payment capture and Priority Vault for tokenization.

To learn more → Ready-to-Launch Solutions — Introduction · Priority Checkout · Priority Vault

3D Secure (3DS) Authentication

Enterprise-grade cardholder authentication for card-not-present transactions — shifting fraud-related chargeback liability from the merchant to the issuing bank.

3D Secure (3DS) authentication is now supported across both Priority Checkout and direct Checkout API integrations. When a cardholder successfully authenticates with their issuing bank, liability for fraud-related disputes shifts from the merchant to the issuer — reducing chargeback exposure on e-commerce, subscription, and high-risk transactions. The flow supports both frictionless and challenge experiences.

Key aspects

• Audience: Merchants accepting card-not-present transactions — through Priority Checkout or directly via Checkout APIs — particularly those in high-risk verticals or operating in markets with regulatory authentication requirements.
• Why it matters: Liability shift on authenticated transactions is the single strongest defense against fraud-related chargebacks available on card networks today. Best paired with AVS for maximum risk reduction.

Technical details

• Priority Checkout (Ready-to-Launch):

  • 3DS is built into the Priority Checkout widget and uses 3DS 2.2. No client-side authentication flow needs to be implemented by the merchant — the widget orchestrates the challenge/frictionless flow with the issuer.
  • Enablement is account-level. Contact the PCE Account Management Team to enable 3DS authentication on your merchant account. Once enabled, the widget will invoke 3DS on eligible card-not-present transactions automatically.
  • Liability shift on successful authentication is reflected in the transaction outcome returned via onSuccess. Failed authentications surface through onError.

• Checkout APIs (direct integration):

  • Pass authentication results on the payment request via the threeDSecure object. Typical fields include the ECI indicator, authentication value (CAVV), transaction identifier (XID for 3DS 1, DS Transaction ID for 3DS 2), and the authentication status.
  • Supports both 3DS 1.0.2 and 3DS 2.x (frictionless and challenge flows). The card network and issuer determine which version applies.
  • Liability shift eligibility is reflected in the payment response. Always pair with AVS data for maximum risk reduction.

API Reference → Create a new payment or refund · Get Payment Details

Available on: This feature is available for merchants using Priority's Ready-to-Launch Solutions through Priority Checkout. Additionally, 3D Secure authentication is also accessible for merchants integrated directly with Priority's Checkout APIs.

To learn more → 3D Secure (3DS) Authentication · Enabling 3DS for Payments on Priority Checkout

Canadian Dollar (CAD) Currency and Configurable Display Language

Charge Canadian customers in their local currency and present the payment experience in their language — across both direct API integrations and Ready-to-Launch components.

Priority now extends support for the Canadian market through two complementary capabilities:

• Canadian Dollar (CAD) transactions are accepted on both Priority Checkout (Ready-to-Launch) and direct Checkout API integrations, alongside US Dollar. Canadian cards are also supported across Priority Vault for storage and reuse.
• Configurable display language is available on Priority Checkout and Priority Vault. Merchants can choose the language shown in the widget from a defined set of supported options covering English and French variants (including Canadian and French regional variants). If no language is specified, the widget detects the customer's browser language and gracefully falls back to English when the browser language isn't supported.

Together, these enhancements let merchants deliver a localized, market-appropriate experience without additional development work.

Key aspects

• Audience: Merchants serving customers in Canada, French-speaking markets, or any merchant wanting to control the language displayed in the payment and vaulting experience.
• Why it matters: Opens Canadian and bilingual markets out of the box — no custom localization work, no separate integration. CAD support spans both direct API and widget paths, while the display language setting controls what's shown inside the Priority widget from a fixed, supported list of language tags.

Technical details

• Canadian Dollar (CAD) Currency — available across both paths:

  • Priority Checkout (Ready-to-Launch): amount.currency now accepts USD and CAD. Pass CAD in WidgetSDK.create() to denominate the transaction in Canadian Dollars end-to-end. Priority Vault accepts Canadian cards for tokenization and reuse alongside US cards.
  • Checkout APIs (direct integration): Pass CAD as the amount.currency value on the payment request. The transaction is denominated and settled in Canadian Dollars end-to-end. Supported alongside USD.

• Configurable Display Language (Locale) — available on Ready-to-Launch only:

  • Pass an optional locale parameter using a BCP 47 language tag in WidgetSDK.create(). Supported values: en, fr, en-fr, en-US, en-CA, fr-CA, fr-FR.
  • Fallback behavior: if locale is omitted, unsupported, or malformed, the widget detects the browser language and uses it when supported, otherwise falls back to en.
  • Scope reminder: locale only controls the language displayed inside the Priority widget — it does not localize the rest of your application or address/number formatting.

API Reference → Create a new payment or refund

Available on:

• Canadian Dollar (CAD) currency is available for merchants using Priority's Ready-to-Launch Solutions through Priority Checkout, with Priority Vault also supporting Canadian cards for tokenization. Additionally, CAD currency is accessible for merchants integrated directly with Priority's Checkout APIs.
• Configurable display language (locale) is exclusive to Priority's Ready-to-Launch Solutions and is supported on both Priority Checkout and Priority Vault.

To learn more → Priority Checkout — Integration Steps · Priority Vault — Integration Steps · Online Card Payments

Apple Pay

Offer Apple Pay across Priority Checkout and direct Checkout API integrations — Priority handles end-to-end merchant validation on the merchant's behalf.

Merchants can now accept Apple Pay through both Priority Checkout (Ready-to-Launch) and direct Checkout API integrations. Customers on supported Apple devices authenticate with Face ID, Touch ID, or passcode and complete checkout without entering card details. Priority handles Apple Pay merchant validation end-to-end on the merchant's behalf — including Apple Merchant ID, Certificate Signing Request, and domain registration — removing the manual setup overhead outlined in Apple's documentation.

Key aspects

• Audience: Merchants accepting e-commerce or mobile web payments, particularly those with mobile-heavy traffic on iOS devices.
• Why it matters: Apple Pay is the expected mobile checkout experience for iOS customers. Eliminating manual card entry drives conversion lift on mobile, while Priority's end-to-end handling of Apple's merchant validation saves significant engineering work compared to completing it manually.

Technical details

• Domain registration is a one-time setup (common to both paths): host the pre-configured domain association file at /.well-known/apple-developer-merchantid-domain-association, then register your domain via the PRTH Dashboard (Payment Methods → Domain Registration) or via POST /checkout/v3/applepay/register.

• Token submission (common to both paths): On submission, the Apple Pay token is passed in cardAccount.mobileWallet.encryptedPayload. Each token is single-use — never resubmit a consumed token.

• Priority Checkout (Ready-to-Launch):

  • Enable Apple Pay in the widget by passing paymentMethods.applePay.enabled: true in WidgetSDK.create(). Defaults to false.
  • The widget automatically hides Apple Pay on non-Safari browsers and unsupported devices, so no client-side device gating is needed.

• Checkout APIs (direct integration):

  • Apple Pay is only available on Safari on supported Apple devices. Merchants on direct API integrations are responsible for client-side device gating to show or hide the Apple Pay button as appropriate.

API Reference → Create a new payment or refund

Available on: This feature is available for merchants using Priority's Ready-to-Launch Solutions through Priority Checkout. Additionally, Apple Pay is also accessible for merchants integrated directly with Priority's Checkout APIs.

To learn more → Apple Pay Setup · Priority Checkout — Integration Steps

Visa Marketplace Identifier for Card-Not-Present Transactions

Stay compliant with Visa marketplace network requirements automatically — no integration changes needed.

Marketplace merchants processing Visa card-not-present transactions through Checkout APIs now have their marketplace identifier automatically attached to every eligible transaction. This helps ensure compliance with Visa's marketplace identification network requirements and reduces the risk of transaction misclassification.

Key aspects

• Audience: Marketplace merchants using Checkout APIs to process Visa card-not-present transactions.
• Why it matters: Visa requires marketplace identification on qualifying transactions. PCE now handles this automatically — no merchant action required, no risk of missed identifiers, and no engineering work to stay compliant as Visa rules evolve.

Technical details

• The Visa marketplace identifier is attached automatically on every eligible card-not-present Visa transaction submitted through Checkout APIs — no request-side change is required.
• Identifier is sourced from your merchant configuration at PCE.

API Reference → Create a new payment or refund

Available on: This feature is available for marketplace merchants integrated directly with Priority's Checkout APIs.

To learn more → Online Card Payments

Questions?

Reach out to the PCE Product Team for implementation guidance, customer enablement support, or additional product information.