Skip to content
Gaurav TiwariDocs

Sell Through Creem as Merchant of Record

Version 1.0.0-beta.1 Updated November 8, 2026

Selling software or digital downloads to buyers abroad means VAT across Europe and sales tax in a growing list of US states, each with its own registration and filing. For a small store, that paperwork can cost more than the sales it covers.

Creem is a merchant of record: it sells to the buyer, works out the tax and remits it. With the Creem module, buyers pay on Creem’s hosted checkout, Creem bills and renews subscriptions, and Easy Digital Downloads orders stay in step through signed webhooks that Stackless sets up for you.

Turn On the Gateway

  1. Switch on the Creem module under Stackless → Dashboard.
  2. Add your API key under Stackless → Settings → Creem and save.
  3. Go to Downloads → Settings → Payments and switch on Creem (Stackless) under Active Gateways. Save.

Creem stays off the checkout until the current mode has an API key, and for carts it can’t take.

Add Your API Keys

In the Creem dashboard, open Developers → API keys and copy your key. The Get API keys button in the Live section opens the same page. Test and live keys are separate: switch the dashboard to test mode at the bottom of the sidebar to copy the test key, which starts with creem_test_. Then fill in:

  • Title: the gateway name at checkout. Default “Card, Apple Pay or Google Pay (Creem)”.
  • Description: the text under it. Default “You’ll finish paying on Creem’s secure checkout. Creem adds any sales tax or VAT for your location before you pay.”
  • Test mode: uses Creem test mode, so no real money moves. On by default. This switch is separate from EDD’s Enable Test Mode.
  • Debug log: writes Creem activity to the EDD debug log. Off by default.
  • Live API key and Live webhook secret
  • Test API key and Test webhook secret

When you save, Stackless checks each new key with Creem, and a key in the other mode’s field gets an error. Moving a mode to a different Creem store clears the products remembered for that mode. With the gateway on, a missing API key or webhook secret for the selected mode shows an error.

You can also set these as wp-config.php constants, which win over saved settings and hide their fields: STACKLESS_EDD_CREEM_LIVE_API_KEY, STACKLESS_EDD_CREEM_LIVE_WEBHOOK_SECRET, STACKLESS_EDD_CREEM_TEST_API_KEY and STACKLESS_EDD_CREEM_TEST_WEBHOOK_SECRET.

Connect the Webhook

On a public HTTPS site there’s nothing to do. Saving an API key creates a webhook named “Stackless for EDD” in that Creem mode, subscribes it to the events below and saves its secret. The Webhook section then says, for example, “Test webhook connected: Stackless set it up in Creem and saved its secret.” A webhook already pointing at your URL is reused, and a secret you pasted yourself is never replaced.

Some sites have to add it by hand:

  • A site on a local or private address, or without HTTPS, gets a line in the Webhook section saying Creem can’t reach it.
  • If Creem refuses to create the webhook, the error after saving says why. A key without the webhook permissions is the usual cause.
  • On a copy of your live store, such as staging, the live webhook isn’t created, so the copy never joins your live Creem store’s webhooks. The test webhook still is.

To add it by hand, open Developers → Webhooks in Creem (switch to test mode first for the test endpoint) and add https://yoursite.com/wp-json/stackless-edd/v1/creem/webhook. The Webhook section shows your exact URL. Select these events, then paste the webhook secret into the field for the same mode:

checkout.completed
subscription.active
subscription.trialing
subscription.paid
subscription.update
subscription.scheduled_cancel
subscription.canceled
subscription.past_due
subscription.unpaid
subscription.paused
subscription.expired
refund.created
dispute.created

Creem signs each delivery with the creem-signature header, an HMAC-SHA256 of the raw body keyed with the webhook secret. Standard Webhooks headers are accepted too, within five minutes of their timestamp. The secret that matches decides whether the event is live or test, and each event is applied once.

Set How Tax Works

  • Prices and tax: Add tax on top of my prices (the default) or My prices already include tax.
  • Tax category: Software as a service is the default. The other choices are Digital goods or services and E-books. Creem uses it to pick the tax rate for each buyer’s country.

Turn off EDD taxes for downloads you sell through Creem, or buyers get taxed twice. With tax on top, the EDD order total stays your price, and the payment note shows what Creem charged including tax. Changing either setting starts fresh Creem products.

What Buyers See

At checkout, Creem shows as “Card, Apple Pay or Google Pay (Creem)” with the description above. In test mode, checkout adds “Test mode: no real payment will be taken.”

  • Purchasing sends the buyer to Creem’s checkout with their email filled in. Creem charges the order total, plus any tax it adds on top.
  • After paying, they come back to the receipt for their order, and Stackless reads the checkout back from Creem before marking the order paid. An expired checkout sends them back to pay the order again.
  • If Creem reports a payment in another currency or for another amount, including one where a Creem discount code was used, the order goes On Hold with a note to check it in Creem.
  • Creem orders never get one-click charges from Post-purchase Offers. The offer becomes a pay link instead.

Products in Your Creem Catalog

Every Creem checkout sells a product from your Creem catalog. Stackless creates them on first use and remembers them for each mode, so there’s nothing to set when you edit the download.

  • One-time sales use one Creem product per download, or per price option with variable pricing, and currency. It’s priced per checkout, so price changes, discount codes and Pay What You Like amounts need no new product. Carts with several items share one product named “[Store name] order”.
  • Subscriptions use one product per download or price option, schedule, recurring amount and trial length, because Creem can’t set a subscription’s price or trial per checkout.
  • A product archived or deleted in Creem is created again on the next checkout.

Subscriptions on Creem

Creem runs the renewal schedule for subscriptions it bills:

  • Creem bills every 1 to 365 days, 1 to 52 weeks, 1 to 24 months or 1 to 3 years. A plan on any other schedule is refused at checkout.
  • Creem bills the same amount every cycle, so a subscription with a signup fee or a different first payment is refused at checkout.
  • Free trials work. Creem saves the card without charging, and the subscription shows as Trial until Creem’s first charge. The trial is passed to Creem in whole days.
  • Each renewal Creem charges becomes one paid EDD renewal order. The next payment date follows Creem’s.
  • Creem’s past due, unpaid and paused show as On hold, canceled as Cancelled, expired as Expired, and a cancellation set for the end of the period as Pending cancellation.
  • After the last payment of a fixed-length plan, Stackless tells Creem to stop at the end of the period.

Cancelling from the EDD admin or the account page cancels at Creem too, at the end of the paid period or straight away. If Creem doesn’t confirm, the cancellation is refused with a message to try again or cancel at the provider.

Creem bills every subscription it takes, so the download’s Renewal mode can’t be Manual only (customer pays each renewal invoice). Checkout refuses that combination and asks the buyer to choose automatic renewal or another payment method. See Sell Downloads as Subscriptions.

When a Renewal Fails

Creem retries a failed card on its own schedule, and Stackless follows along with your Handle Renewals and Failed Payments settings:

  • When Creem reports the subscription past due, a renewal order is created and marked Failed, the subscription goes On hold, and the customer gets the Subscription payment failed email. Your retry schedule runs, but each retry only waits for Creem, which does the charging.
  • When one of Creem’s retries succeeds, that same renewal order is paid and the subscription is Active again.
  • When Creem reports the subscription unpaid, its own retries have run out. If the renewal is still unpaid when your retry period ends, the renewal order is marked Abandoned and the subscription is cancelled here and at Creem.
  • A failed Creem renewal can’t be paid from the store, so nobody is charged twice. The payment link points the customer to their subscription instead. Customers update their card in Creem’s customer portal, linked in Creem’s receipts.

Refunds and Disputes

  • EDD’s refund form on the order gets a Refund the payment in Creem (full refunds only) box, ticked by default. It refunds the whole Creem payment, and only while nothing on the order has been refunded yet. A partial amount is refused with a message to refund the full total or use the Creem dashboard, and EDD records nothing. Refund a renewal from its own renewal order.
  • Untick the box to record the refund in EDD only. The order gets the note “Payment not refunded in Creem, as the box was not ticked.”
  • Refunds made in the Creem dashboard, partial or full, are recorded on the order once. They’re scaled back to the pre-tax amount when Creem added tax on top, and a partial one is spread across the order’s items.
  • Disputes opened in Creem add an order note. Review them in the Creem dashboard.

More Than One Creem Store

Creem can be duplicated for a second Creem store. Each copy has its own keys, products, orders and webhook URL ending in /webhook/copy2 and so on. Saving a copy’s key creates its webhook in that store the same way. Constants in wp-config.php apply to the original only. See Duplicate a Payment Gateway.

Check the Connection

  • Billing Health lists Creem setup problems for the original and every copy: no API key for the current mode, a key for the other mode, a missing webhook secret, no webhook received yet and test mode left on. It also shows recent webhook events that failed.
  • With Alerts on in Extra Enhancements (“Email me about failed live payments”), failed live Creem orders and failed live calls to Creem are emailed to you.
  • Turn on Debug log to write Creem activity to Downloads → Tools → Debug Log, tagged stackless-edd-creem_gateway, while EDD debug mode is on. Keys are never logged. Copies write to the same log, with their id at the start of each line.

Limits

  • Creem charges in US dollars and euros only, from 1.00, and isn’t offered for other currencies. It works with Sell in Multiple Currencies, and Match Payment Gateways to Currencies knows its list.
  • Creem takes one subscription per checkout, with no other items in the cart, and isn’t offered for carts it can’t take. One-time carts can be any size.
  • Creem doesn’t save cards in EDD. Customers can’t renew early, resume a pending cancellation, switch renewal mode, change the payment method, pause or skip a renewal from the account page, and you can’t change the next payment date. A subscription paused in the Creem dashboard shows as On hold.
  • If your retry schedule ends before Creem’s own retries do, the subscription is cancelled at Creem when your schedule ends.
  • Subscription events need the Subscriptions module on. While it’s off they fail, and Creem keeps retrying them.

For Developers

Filters: stackless_edd_creem_gateway_checkout_args (the checkout sent to Creem, with the order, the subscription or null, and the gateway), stackless_edd_creem_gateway_product_args (a product before it’s created) and stackless_edd_creem_gateway_currencies (can narrow the list to USD or EUR). Actions: stackless_edd_creem_gateway_webhook after each applied event, and stackless_edd_creem_gateway_subscription_synced when Creem changes a subscription’s status:

add_action('stackless_edd_creem_gateway_webhook', function ($type, $object, $mode, $gateway_id) {
    if ($type === 'dispute.created') {
        error_log('Creem dispute for ' . $gateway_id . ' in ' . $mode . ' mode');
    }
}, 10, 4);

Override the checkout fields by copying the template to yourtheme/stackless-edd/creem_gateway/payment-fields.php.

Share

Was this helpful?

Still stuck? Open a support ticket