We value your privacy
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.
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.
Help Center
Answers about checkout, orders, subscriptions, integrations, and your EPD Commerce account.
How customers pay you: hosted checkout pages, QR codes, and coupons.
A secure, ready-made payment page for any product, subscription, or invoice, with no site development required.
A hosted checkout page is a secure payment page served by EPD Commerce that a merchant sends customers to for payment. It handles product selection, coupon entry, address collection, and card capture. It works on desktop and mobile without any additional setup.
No. A hosted checkout URL is enough on its own. Merchants who have no website can sell by sending a link or QR code. Merchants with a website can link to the checkout from any button, image, or text link.
Yes. Card data is captured and stored on EPD Commerce systems, not on the merchant's website. This reduces the merchant's PCI scope because the sensitive card data never touches merchant infrastructure.
Yes. Customers can store multiple physical addresses per account with one designated billing and one default shipping address. Payment methods can be stored as cards on file. During checkout the customer can pick from the address book and saved cards, or add new ones.
Yes. If a merchant has active coupons, the checkout page shows a coupon code field. Valid codes discount the order total in real time. Expired or fully redeemed codes show an inline error message.
Yes. Any subscription template exposes a hosted checkout URL. Depending on the subscription setting, billing starts on the standard renewal date or on the day the customer checks out. See Subscription Start on Sign Up.
Accept payments through a QR code that links to a hosted checkout page. No app, no card reader, no extra hardware.
The QR code encodes the hosted checkout URL for a specific product, subscription, or one-time payment link. When a customer scans it, their phone opens the checkout page in the browser. They fill in payment details and complete the purchase. The order posts to EPD Commerce in real time.
No. Any phone camera app that reads QR codes will work. The checkout opens in the phone's default browser. There is nothing for the customer to download.
Yes. QR codes are a fit for in-person tables, pop-ups, trade show booths, restaurants, service calls, and any counter without a full point-of-sale system. Print the code on a card or show it on a screen.
Yes. Because the code is a static image tied to a URL, it can be printed on invoices, menus, receipts, direct mail, packaging, or event signage.
Yes. If the underlying hosted checkout is a subscription, the QR flow starts the subscription the same way as a link. Recurring billing follows the schedule set on the subscription template.
QR code payments land in the same Payment Transaction History and Order Transactions History views as any other EPD Commerce payment. There is no separate reporting silo.
Create coupons with percentage or fixed dollar discounts, optional start and end dates, and redemption limits.
Open the coupon section in the merchant dashboard, click create coupon, then set the code, discount type (percentage or fixed amount), value, optional start and end dates, and redemption limit.
Percentage-off (for example 10% off) and fixed-amount-off (for example $20 off). Both apply to the order total at checkout.
Yes. Set the redemption limit to single-use (one customer only), limited count (a specific number of total redemptions), or unlimited.
Customers enter the coupon code in the coupon field on the hosted checkout page. The discount is applied to the order total in real time.
An inline error message explains why the coupon did not work. Common reasons include expired, redemption limit reached, or code not found.
Yes. Each coupon record shows its redemption count and remaining redemptions, which lets merchants track a campaign's usage without exporting reports.
Track every order and every payment attempt behind it.
A full order history for every customer, with status, total, products, and links to the underlying transactions.
Open the customer's profile in the EPD Commerce dashboard. The Orders tab lists every order that customer has placed, most recent first, with total, status, and product summary. Click any order to see line items and payment details.
Yes. The order list supports filtering by customer, date range, order status, and product. Search returns matches from the customer profile and from the global order view.
Common statuses include successful, pending, failed, refunded, partially refunded, and cancelled. A subscription order additionally shows the subscription state on the parent subscription record.
Each order links out to Order Transactions History and Payment Transaction History. From a single order view a merchant can see the initial payment, any retries, refunds, and adjustments.
Yes. Refunds can be started from the order detail page. For subscription orders, use Subscription Refunding and Management for the full refund flow, including partial refunds and subscription-level actions.
Customer receipt emails include order details, and hosted checkout retains a customer's basic order references. Full self-service customer portals are outside this feature.
Every payment attempt against every order in a searchable history: successes, declines, retries, refunds, and voids.
An order represents what the customer purchased. A transaction is a single attempt to move money against that order. One order can have many transactions, for example an initial charge, a retry, and a partial refund. Both are recorded and viewable.
Yes. Declines and failed attempts are recorded in the transaction history alongside successes, with the decline reason where available. This is the primary view a merchant uses to understand payment health.
Filter by date range, customer, status (approved, declined, refunded, voided), amount, and payment method. The list is exportable for reconciliation.
Yes. Quick actions on the transaction success screen let merchants refund, void, or open the underlying order without navigating away.
Yes. Refunds appear as separate negative transactions linked back to the original charge. This preserves a full audit trail and reconciliation flow.
Yes. Every subscription renewal generates a transaction that appears in Payment Transaction History with a reference to the parent subscription and order.
Manage recurring plans, refunds, billing dates, and failed-payment recovery.
Refund a single charge or a series of charges from a subscription's detail view, and pause with a resume date or indefinitely.
Open the subscription's detail view and locate the charge in the history. Choose refund and enter a full or partial amount. The refund posts to the underlying transaction and appears in Payment Transaction History.
Yes. Partial refunds are supported. Enter the amount to refund and the balance stays on the original charge.
Yes. Use the pause button in the subscription management UI. Pick a resume date or pause indefinitely. The subscription state changes to paused and renewals do not run until the subscription resumes or is manually restarted.
Yes. When a merchant pauses a subscription, the customer receives a notification explaining the pause and the resume date if one is set.
Yes. Merchants can attach an internal note or reason to the pause. It shows up on the subscription record for future context.
Active means renewals run on schedule. Paused means renewals are stopped but the subscription is not ended. Cancelled means the subscription is fully ended and will not resume without being recreated.
Bill on the customer's purchase date instead of a fixed recurring date, with a per-template toggle.
It is a per-subscription-template setting that changes when a customer's recurring billing begins. Instead of billing on the template's fixed recurring date, the system uses the customer's checkout date as the recurring anchor.
Open the subscription template and enable the bill-on-purchase-date toggle. New signups from that point forward will use their checkout date as their recurring anchor.
No. Existing subscribers remain on their current schedule. The setting affects new subscribers who sign up after the toggle is enabled.
Yes. The setting is per subscription template, so different products can use different billing anchors on the same merchant account.
For months with fewer days, the renewal falls on the last available date of that month. The following month returns to the original anniversary day when possible.
Yes. Refunds, pauses, and cancellations behave the same whether the subscription anchors to a fixed date or to the purchase date.
Automatically recover failed subscription payments with a configurable retry schedule and a dunning dashboard.
Failed payments enter a merchant-defined retry schedule. Retries can include same-day attempts. Customers receive automated notifications during the process. Subscriptions that exhaust the retry allowance or exceed the hard decline threshold are automatically paused.
Yes. Merchants configure retry rules including timing, number of attempts, and thresholds for auto-pausing subscriptions. Different merchants often want different aggressiveness. The rules are exposed in the dunning dashboard.
Yes. EPD Commerce sends automated payment failure notifications, expiring card warnings, and retry notifications. Merchants can adjust the email templates for tone and brand.
The dashboard shows failed payments, configurable retry rules, manual retry buttons, revenue at risk, recovery rates, failure reason breakdowns, and dunning performance metrics.
Yes. Every successful payment triggers a customer receipt email. The template can be adjusted in the Email templates system.
Yes. Upcoming charge emails go out ahead of a scheduled subscription renewal, letting the customer expect the charge and update their card if needed.
Connect EPD Commerce to the tools you already use, or build on the API.
EPD Payments is available as a payment processor inside HighLevel funnels, order forms, and checkout pages.
Install the EPD Payments module from the HighLevel Payments Marketplace. Inside HighLevel, authenticate with your EPD Payments account. Once connected, HighLevel routes funnel and checkout payments through EPD Payments.
Yes. Apple Pay works as a payment option in HighLevel funnels and checkout pages when EPD Payments is the selected processor.
Yes. Agencies can configure EPD Payments at the sub-account level. Each sub-account authenticates its own EPD Payments account.
No. Payment events (successful and failed payments) flow into HighLevel in real time, but CRM data such as contacts, pipelines, and campaign details is not synced by this integration.
Transactions are processed and stored in EPD Payments. HighLevel receives event notifications so workflows and reports inside HighLevel stay accurate.
For basic workflows driven by payment events, HighLevel's native automations work off the delivered events. For broader automation across tools, use the Zapier integration in EPD Commerce.
A WordPress plugin that turns EPD into a payment gateway for WooCommerce stores, with subscription support.
Install the EPD Commerce plugin from the WooCommerce plugin repository (or from a private beta link during limited release). Activate it in WordPress admin and enter your EPD Commerce API credentials.
Yes. The plugin integrates with WooCommerce Subscriptions. Merchants can create and cancel subscriptions and process recurring payments through EPD Commerce.
Yes. Customers stay in the WooCommerce checkout flow. Card capture and payment processing happen through EPD Commerce behind the scenes.
Apple Pay support depends on the EPD gateway and the underlying WooCommerce and Apple Pay configuration. Verify current support status in the plugin documentation for your version.
Not through bidirectional sync. In its current form the plugin covers payment gateway and subscription functionality. To bulk import products from your WooCommerce site into EPD Commerce, see Merchant Website Product Sync.
Everything is inside WordPress admin under the EPD Commerce settings page: API credentials, payment gateway on and off, and subscription behavior.
A listed Zapier app so you can trigger workflows on new orders, customers, payments, and subscription events.
Search for EPD Commerce in the Zapier app directory, add it to a Zap, and authenticate with your EPD Commerce account. Once connected, EPD events are available as triggers inside any Zap.
New order created, new customer created, successful payment, and subscription events (created, renewed, cancelled, paused).
Yes. Prebuilt Zap templates are available for common workflows such as sending new orders to a spreadsheet, pushing customers into a CRM, or notifying a Slack channel on a successful payment.
The integration is trigger-focused. EPD Commerce events fire Zaps in downstream tools. For inbound actions against EPD Commerce, use the Publicly Accessible API.
Yes. A common pattern is to trigger on new customer or successful payment and push the record into a CRM tool such as HubSpot or Salesforce through Zapier.
Zapier is a no-code, hosted integration platform on top of EPD Commerce events. Webhooks send raw events to any endpoint the merchant controls and are aimed at developer or engineering setups.
Real-time webhook events for payment, subscription, customer, and order activity, signed and retried on failure.
Payment events (successful, failed, refunded), subscription events (created, renewed, cancelled, paused), customer events (created, updated, deleted), and order events.
Register endpoints through the EPD Commerce API. Provide the URL to receive events and the event types you want to subscribe to. Endpoint management is also available through the merchant dashboard.
Yes. Failed deliveries are retried on a backoff schedule so a brief outage does not lose events. Delivery logs show each attempt and its result.
Every webhook request is signed. Verify the signature on your side using the shared secret from your endpoint configuration. Reject any request whose signature does not match.
Yes. The delivery logs show recent webhook attempts, response codes, and payloads. Use them for debugging or for confirming an expected event landed at your endpoint.
Webhooks send raw events to any HTTPS endpoint you control, which is a fit for developers and custom systems. The Zapier integration wraps the same events in a no-code interface for connecting to thousands of downstream tools without writing code.
Add your website URL and EPD Commerce ingests your products automatically for review and AI enrichment.
Give EPD Commerce your website URL. The platform extracts your products in the background and drops them into a review queue. You approve, edit, or reject each product before it is added to your EPD Commerce catalog.
WooCommerce is the first supported platform. Other ecommerce platforms are being added over time. The extractor also handles general websites where product data is structured.
Yes. Review, edit, and approve every product before it goes live. Edits include name, price, description, image, subscription settings, and any other product field.
After approval, EPD Commerce adds an AI context layer to your products. This structured context is designed to help AI assistants like OpenAI's ChatGPT understand and rank your products when users ask AI-driven shopping questions. See the ChatGPT Product Feed section for the direct integration.
The sync supports update requests through the API, so a merchant can refresh individual products or the full catalog when things change. Approved products in EPD Commerce are not overwritten without merchant confirmation.
Yes. The extractor recognizes subscription and recurring payment offers and imports them with the correct billing cadence where it can be inferred.
Sign-in options, team access, and your customer and product records.
Sign in with Google or a passkey in addition to email and password, and link them to an existing account.
Yes. On the login screen, choose Continue with Google and complete the Google OAuth prompt. If your Google email matches an existing EPD Commerce account, sign-in completes immediately. Otherwise you can link the Google account to your EPD account after signing in.
Yes. Passkeys let a merchant sign in with device biometrics or PIN. Register a passkey from account settings once and use it on future sign-ins from the same device.
Yes. Sign in with your existing credentials and open account settings to link a Google account or add a passkey. Both are stored alongside your existing email and password.
Traditional email and password login remains available as a fallback. You can also remove or reset a stored passkey or Google link from account settings.
Passkeys are considered stronger than passwords because they are device-bound cryptographic credentials, not something typed and reusable across sites.
Yes. Every team member added through Team Member Management can also sign in with Google or a passkey, subject to the account permission settings.
A customer and product database with global search, team roles, and a ChatGPT-ready product feed.
Every customer that transacts through EPD Commerce is stored in the merchant's CRM with contact info, address book, saved payment methods, order history, and subscription history. It is accessible from the merchant dashboard.
Use the global item search bar in the merchant dashboard. It searches customers, products, subscriptions, and orders in one place so a merchant does not have to jump between screens to find the right record.
Yes. Team Member Management supports invites by email, role-based access control (Admin, Manager, Staff, and similar), and permission settings ranging from view-only to full access.
Yes. Every action taken by a team member is recorded in an audit trail visible to the account admin, so merchants know who made which change and when.
The ChatGPT Product Feed is a structured export of a merchant's product catalog designed to be consumed by OpenAI's ChatGPT and other AI shopping tools. Once the merchant's products are in EPD Commerce, the feed is available for AI assistants to surface the merchant's products.
Yes. Team members can sign in with email and password, Google, or a passkey. Their permissions on EPD Commerce are controlled by their assigned role.
No results found. Try a different search term.
◆ Now in private beta
We respond within one business day.
◆ Now in private beta
EPD Commerce brings your operations, payments, and AI-discoverable products into one connected system.
