EPD Commerce is one place to take payments online: charge cards once, bill customers on a schedule, refund what you need to, and let your software (or an AI agent) do all of it through a clean REST API.

Choose how you want to start

What you can build

How EPD works at a glance

You hold an API key

A sandbox key (epd_test_sk_...) for testing, a live key (epd_live_sk_...) for real money. The key alone decides which mode every request runs in. There is no separate sandbox host.

You call one base URL

All REST traffic goes to https://api.epd.com/v1. Pin your code to a version date with the epd-version header — e.g. 2026-02-11.

EPD does the heavy lifting

Card vaulting, recurring billing, smart retries, and signed webhooks — all built in.

Webhooks tell you what happened

For anything asynchronous (settlement, renewals, chargebacks), EPD POSTs a signed JSON event to your endpoint.

Start here, by role

Base URL

All API requests are sent to a single production base URL:

https://api.epd.com/v1

There is no separate sandbox host. Whether a request runs in live or sandbox mode is determined by the API key you send.

Sandbox keys are created inside the Demo Company that EPD provisions alongside your real company at sign-up — switch companies from the profile avatar (top right) before creating a key. Live keys are created inside your real company. Use a sandbox key while building and testing, and a live key once you are ready to accept real payments.