We use cookies to understand how visitors interact with our site. This helps us improve the experience for everyone.
You can accept or decline; your choice is saved and the banner won't appear again.
A chronological record of what's new across Create, Analyze, React, and Transact.
Transact
Transaction routing
Merchants with multiple merchant accounts can now route transactions to specific MIDs based on product, subscription, or recovery path. Routing rules replace the guesswork of percentage-based splits with deterministic logic: first transaction here, all subsequent transactions there. It is available to merchants managing more than one MID inside EPD Commerce.
Transaction routing gives merchants direct control over which merchant account handles a given transaction, without relying on percentage-based allocation. Rules can be set at the product level, the subscription level, or the failed-payment recovery path, so each portion of the business runs through the account best suited for it. A card used on a customer's first transaction can be pinned to a specific MID for all future charges from that customer. Unlike percentage-only routing, it targets specific products and subscriptions directly.
The EPD Commerce Payment Vault encrypts and stores customer card data in a PCI-compliant environment so that raw card data never touches EPD Commerce servers directly. Merchants transact through a secure, tokenized layer that routes payments to their connected processor without compromising compliance posture. This release enables Easy Pay Direct merchant accounts to transact through the vault for the first time.
Card capture and encryption are handled outside EPD Commerce systems, with tokenized credentials used to authorize and settle transactions end-to-end. Existing processor connections, including Authorize.net, continue to operate as proxied backends through the vault, preserving continuity for merchants already processing on those rails. Transaction data from direct-connection merchants is routed to EMAP for unified reporting, keeping volume attribution accurate across all processor paths. The vault also supports an Account Updater mechanism that keeps stored card records current when card details change, reducing involuntary churn for subscription merchants.
Transact
Apple Pay in hosted checkout
EPD Commerce hosted checkout now supports Apple Pay across Safari, Chrome, Edge, and Firefox on Apple devices, as well as Safari and Chrome on Mac. Onboarding and merchant verification are handled at the platform level, so merchants do not need to manage Apple Pay setup separately. Apple Pay transactions appear in the same reporting view as all other payment methods, with wallet indicators included.
When a customer's browser and device support Apple Pay, the option appears automatically at checkout. One-click checkout is supported, and if a transaction is declined or canceled, the customer returns to the checkout session without losing cart state. Authorization, capture, refund, and void workflows follow the same transaction flow as card payments. Subscription and recurring billing are supported on processors that handle recurring Apple Pay credentials. Visa-backed network tokens are supported where the processor and acquirer allow it.
React
Revenue Recovery
Revenue Recovery automatically retries failed payments, routes each failure through a strategy matched to its decline reason, and contacts the customer with the right message at the right time. It covers subscription payments through Recovery Templates and failed one-time orders through Order Rescue. No manual intervention required.
The full release includes Retry & Communication Logic for setting global rules around retry frequency, communication cadence, quiet hours, and campaign limits; five default Recovery Templates each mapped to a specific decline reason; Order Rescue applying the same strategy patterns to failed one-time orders; Optimized AI Strategy, a per-template toggle that routes each failed payment to the correct strategy automatically based on decline reason; 14+ Billing Notifications with individual toggles; an editable Email Templates library; and a Revenue Recovery dashboard showing total failed payments, revenue at risk, recovery rate, and upcoming retries. Merchants can use the default strategies as shipped, edit them, or build their own. Revenue Recovery is live in beta and rolling out broadly.
Create
Product Landing Pages
Merchants can now generate a hosted, mobile-responsive landing page for any product directly from the EPD Commerce product list. Each page is built from the product's own data, structured for AI search engines and LLMs to index, and connected to EPD-hosted checkout.
The creation flow lets merchants choose from multiple pre-built templates, including VSL, agency, and service-business layouts, then review and edit the product name, price, description, FAQ, and links before publishing. A "Quick Enhance" AI step refines content from existing product data, and predefined AI prompts generate a static HTML page from the selected template. Published pages include schema markup and structured data designed to surface products in AI-driven search results from tools like ChatGPT, Perplexity, Claude, and Gemini. CTA buttons can point to the EPD-hosted checkout, a booking page, or an external URL, giving service businesses and high-ticket merchants flexibility on how they convert visitors. A final publish step prompts merchants to verify all information for accuracy before the page goes live.
The Professor: smarter analytics, subscription creation, and voice input
The Professor is EPD Commerce's plain-English analytics assistant, now updated with a refreshed interface, more useful pre-built prompts, and the ability to create subscription templates directly from a conversation. It answers questions grounded in each merchant's actual transaction data.
This release renames the AI Analytics Assistant to The Professor and introduces several interface and capability changes: a cleaner prompt layout, contextual next-step suggestions after each AI response (for example, offering to extend a query to the last six months), and improved error recovery when a query cannot be resolved. Chat history is now called The Archive. Merchants can now describe a subscription plan in plain language and The Professor will stage it for review before creation, with a required approve or decline confirmation step before any data is written. A dedicated database user with restricted, read-limited permissions governs all AI-driven data access, and a creationSource flag on products, plans, subscription templates, orders, and transactions tracks whether a record was created manually or through AI.
Custom fields for customers, payments, and subscriptions
Merchants can now define structured custom fields on customer records, payments, and subscriptions directly in the platform, without developer involvement. Fields support text input, single select, multi select, and user record references. Custom field values flow through Easy Charge, hosted checkout, API responses, and webhook events, so the data is available wherever integrations and automations need it.
Each custom field gets a stable, immutable key auto-generated from the field name at creation, which merchants can adjust before first save but not after. This makes the field safe to reference in API calls and automation workflows without risking silent breakage if a label is later renamed. The API uses a simple map structure for reading and writing values, while the definition endpoint returns full metadata including visibility and required status. Webhook events for order.created, subscription.created, customer.created, and customer.updated all carry custom field values, supporting common use cases such as passing a salesperson name across systems for attribution reporting. Field type and entity assignment are locked after creation to protect existing integrations.
