Epicor ESDM

What ESDM is

ESDM stands for Epicor Secure Data Manager. It is the part of Epicor's credit card processing module that holds cardholder data outside the ERP database. When a card is submitted, ESDM stores the sensitive data in its own secure store and returns a token — a placeholder reference — which is what the ERP keeps. The card number itself never lands in the ERP, which is how Epicor keeps the ERP out of PCI scope.

ESDM is deployed as a set of Windows services in the customer's own environment, including a Secure Data Service and a Secure Data Web Service. That web service is a SOAP service, and its WSDL is what Foxy needs to talk to.

Epicor's wider payments stack also includes the Epicor Payment Application (EPA), Epicor Payment Gateway and Epicor Payment Exchange. Those handle the actual authorization and settlement of money. ESDM does not.

What "tokenization only" means

The name says "tokenization only" because that is exactly, and only, what this integration does. This is confirmed, not inferred: the integration has no code path that authorizes or captures a payment. It stores the customer's card in your ESDM vault and hands Foxy back a token, full stop. It is not an acquiring connection — authorization-only is not supported, multi-currency is not supported, 3D Secure is not supported, and card verification is not supported. Every capability a real gateway would expose is absent, because there is nothing for them to act on.

Be plain with yourself about what this means before you enable it: selecting this gateway will let you collect card details at checkout, and it will never charge the customer. There is no point at which the integration marks an order as paid. If you are looking for something that takes payment, this is not it, no matter how it's phrased in the picker.

• Money is not taken at the Foxy checkout, ever, under any configuration of this gateway. The card is captured and tokenized; it is not authorized and not settled by this integration.

• Something downstream has to actually charge the card. In an Epicor deployment that is the ERP, using the stored token, through Epicor's own payment application and gateway. Foxy's part ends at tokenization.

• Do not use this as your only payment method on a normal retail store. A store that sells to the public and expects funds to arrive at checkout needs a real gateway. If you select this one alone, your checkout will accept orders and capture cards, and nobody will be billed. This entry exists only for order-capture workflows where the ERP — not Foxy — owns billing and charges the token afterward.

If any of that does not match how you expected this to work, stop and talk to your Epicor implementation team before enabling it.

Who this is for

• Businesses already running Epicor ERP with the credit card module and ESDM installed and working.

• Deployments where the ERP, not the storefront, is the system of record for billing — B2B ordering, quote-to-cash, account customers, or any flow where an order is placed online but invoiced and charged from Epicor.

• Organisations whose PCI strategy is built around keeping card data in ESDM and tokens everywhere else.

It is not for a standard direct-to-consumer store, and it is not a way to avoid getting a merchant account.

What you need from your Epicor team

There is only one field to fill in, but getting the right value for it is an Epicor-side task, not a Foxy-side one. Before you start, ask whoever runs your Epicor implementation for:

1. 1

   The WSDL URL of your ESDM Secure Data Web Service — the full URL, exactly as they would give it to any other integrating system.

2. 2

   Confirmation that the endpoint is reachable from outside your network. Foxy is a hosted service and calls the endpoint from the internet. ESDM is commonly deployed on an internal network and is commonly not internet-reachable by default. This is the single most likely thing to block the integration.

3. 3

   Confirmation of how the endpoint is secured — TLS certificate validity, and any IP allow-listing you will need to open up.

4. 4

   A test endpoint, if your Epicor environment has a test or pilot instance, so that you have something to put in the Test setup field.

5. 5

   Agreement on what happens after tokenization — which Epicor process picks up the token and charges the card, and on what schedule. This is the part that determines whether your customers actually get billed.

Setting up Epicor ESDM

1. 1

   In the Foxy administration at https://admin.foxy.io, go to Settings > Payments.

2. 2

   Select the payment method set you want to use. If you only have one, it will be the Default Payment Method Set.

3. 3

   Click Add payment method + and choose Epicor ESDM, tokenization only.

4. 4

   Under Live setup, enter your production ESDM WSDL Url.

5. 5

   Under Test setup, enter your test ESDM WSDL Url, if you have a test Epicor environment.

6. 6

   Click Create to save the payment method.

WSDL Url is the only field in the panel. There are no credentials, no toggles and no dropdowns.

(The Live heading reads "Live setup (inactive)" while the payment method set has Use live credentials switched off — that reflects the current state of the set, not a different set of fields.)

Testing

Foxy does not supply shared test credentials for this integration, and could not — there is no shared sandbox, because the endpoint is yours. Testing means pointing the Test setup WSDL Url at a test or pilot Epicor environment that your own team provides.

If you have no test Epicor environment, you have no way to test this integration without touching production. Raise that with your Epicor implementation team before you go live.

Important notes and caveats

• This does not take payment, confirmed. Repeating it because it is the thing that goes wrong: tokenization only means tokenization only, with no code path in Foxy that ever authorizes, captures, or charges a card through this integration.

• The endpoint must be reachable from the public internet. Foxy calls your ESDM web service; a service that only answers on your LAN or behind a VPN will not work.

• No Foxy-side security options. There is no card verification setting, no 3D Secure setting and no authorize-only setting for this integration, because none of them apply.

• Single currency.

Troubleshooting

Almost everything that can go wrong here is on the Epicor side of the connection, so your Epicor implementation team is the first place to go, not Foxy support.

Check in this order:

1. 1

   Does the WSDL URL load from a browser outside your corporate network? If not, nothing else matters.

2. 2

   Is the TLS certificate on the endpoint valid and complete (including intermediates)?

3. 3

   Are the ESDM services actually running? Epicor's ESDM comprises several services and they have a known start-order sensitivity — the Secure Data Service and the Secure Data Web Service both need to be up.

4. 4

   Does the endpoint require IP allow-listing that Foxy's servers are not on?