This edition of the PCE Product Update summarizes the major product enhancements and platform updates delivered across PCE during Q2 2026. This quarter, we expanded our Priority Widgets with new capabilities — including ACH bank account payments and Canadian Dollar (CAD) support on Priority Checkout and Priority Vault — extended coverage into the Canadian market, and rolled out capabilities to support marketplace merchants.

Key Updates

Priority Widgets: expanded capabilities for Priority Checkout & Priority Vault

Priority Checkout and Priority Vault — our fully white-labeled, PCI-compliant payment components — now support a broader set of capabilities, including ACH bank account payments and Canadian Dollar (CAD) transactions, so merchants can offer a payment experience that feels native to their app without touching raw card data.

Priority Checkout and Priority Vault are Ready-to-Launch components that combine the speed and security of a hosted payment experience with the brand control of a custom build. Both are fully responsive and brand-customizable, powered by Priority's secure session-based architecture, keeping raw payment data off merchant servers and reducing PCI compliance scope.

Priority Checkout supports:

• Card and ACH bank account payments in a single flow
• Saved cards and bank accounts, so returning customers check out faster
• Surcharging, so merchants can pass card-processing costs to the customer without a separate integration
• Card brand identification
• Configurable controls: toggle billing-address collection and enable or disable specific payment methods
• Address autocomplete, for faster, cleaner checkout forms
• Multi-currency support (see the CAD update below)

Priority Vault supports:

• Saved cards and bank accounts for future use, built for repeat customers
• Account Verification before tokenization: cards are validated with the network in real time, catching bad card numbers before they cause a failed payment
• AVS checks during verification, an added layer of protection against address mismatches
• Optional 3D Secure (3DS) authentication at the point of vaulting

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 surcharging, validation and verification features, full brand customization, and tokenized save-card and save-bank capabilities out of the box. If a merchant currently redirects customers off-site to pay, this keeps them on-brand instead.

Technical details

• Session model: Your backend creates a short-lived clientSecret on the server, then passes it to the frontend where the widget consumes it on initialization via WidgetSDK.create().
• Configuration: Enable saved payment methods with paymentMethods.card.enableSaving and paymentMethods.bankAccount.enableSaving. Control billing collection with billing.collectAddress and billing.infoType. Set the transaction currency with amount.currency (USD or CAD) and the display language with locale.
• Event callbacks: onSuccess returns the outcome (transaction for Checkout, card/bank reference for Vault), onError returns a structured payload, onChange fires on field-level changes (for example, card brand detection or surcharge updates), and 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.

Available on: Ready-to-Launch Solutions: Priority Checkout for branded payment capture, Priority Vault for tokenization.

To learn more: Priority Checkout Integration Steps · Priority Vault Integration Steps

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.

• Canadian Dollar (CAD) transactions are accepted on both Priority Checkout (Ready-to-Launch) and direct Accept Payments APIs integrations, alongside US Dollar. Priority Vault also accepts Canadian cards 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 covering English and French variants, including Canadian and European regional variants. If no language is specified, the widget detects the customer's browser language and falls back to English when the browser language isn't supported.

Key aspects

• Audience: Merchants serving customers in Canada, French-speaking markets, or any merchant that wants to control the language displayed in the payment and vaulting experience. A strong opener for any ISV or enterprise expanding into Canada.
• Why it matters: Opens Canadian and bilingual markets out of the box, with no custom localization work and no separate integration.

Technical details

• CAD currency, 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.
  • Accept Payments 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, alongside USD.
• Configurable display language (locale), 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 controls only the language displayed inside the Priority widget. It does not localize the rest of your application or address and number formatting.

Available on: Ready-to-Launch Solutions (Priority Checkout and Priority Vault). CAD currency is also available for merchants integrated directly with the Accept Payments APIs.

To learn more: Priority Checkout Integration Steps · Priority Vault Integration Steps

Visa Marketplace Identifier for card-not-present transactions

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

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

Key aspects

• Audience: Marketplace merchants using the Accept Payments APIs to process Visa card-not-present transactions.
• Why it matters: Visa requires marketplace identification on qualifying transactions. PCE now handles this automatically, with no merchant action required and no engineering work to stay compliant as Visa rules evolve. It's a zero-lift value-add worth raising in renewal or expansion conversations.

Technical details

• The Visa marketplace identifier is attached automatically on every eligible card-not-present Visa transaction submitted through the Accept Payments APIs. No request-side change is required.
• The identifier is sourced from your merchant configuration at PCE.
• Visa registration is required and happens at boarding. Set expectations upfront: it can take up to 30-40 days, so this is not instant-on.

Available on: Accept Payments APIs.

Contact the PCE Account Management team to initiate onboarding. Visa registration at boarding can take up to 30-40 days to complete.

Questions?

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