Set up a custom domain

Steps

1. Choose your SSL option

Foxy offers three ways to secure your custom domain:

• Standard SSL — the default option. Requires two CNAME records in your DNS; Foxy handles the certificate.

• Bring your own SSL (BYOSSL) — available on Enterprise plans only, for merchants who need an EV or other custom certificate. Contact Foxy to get started; this option costs more due to the added setup and renewal work.

• Wildcard SSL — for covering multiple stores under one certificate. Contact Foxy for setup.

Most merchants should use Standard SSL unless they have a specific reason for one of the other two.

2. Order your custom domain

1. 1

   Go to the Foxy admin

2. 2

   Go to Store > Settings

3. 3

   Check the box for Use custom SSL

4. 4

   Click Purchase an SSL certificate in the help text that appears

5. 5

   Complete the order form and check out

Foxy’s support team will follow up within 1–2 business days to confirm the order.

3. Set up your DNS

1. 1

   Decide on a subdomain, such as secure.example.com, checkout.example.com, or store.example.com

2. 2

   Add a CNAME record for that subdomain, pointing to [your-subdomain].dns.foxycart.com. — for example, secure.example.com would point to secure.example.com.dns.foxycart.com. (include the trailing period if your DNS provider allows it)

3. 3

   Confirm the record with the dig command (Mac/Linux) or a tool like kloth.net. You should see your domain pointing to cloudfront.net, with A records listed beneath it

If you use a CAA record, add amazon.com, amazontrust.com, awstrust.com, and amazonaws.com as approved issuers, either on your root domain or your specific subdomain.

You’ll see a certificate warning if you point your DNS before Foxy confirms your SSL certificate is fully provisioned. It’s fine to set up the CNAME as soon as you place your order — it just won’t work until Foxy has approved and configured it on their end.

4. Set up anti-fraud protection

Custom domains need their own reCAPTCHA keys, since Foxy’s automatic reCAPTCHA integration can’t be applied to a domain it doesn’t control. Skipping this step leaves your store exposed to botnet card-testing attacks, which can generate large authorization fees.

1. 1

   Go to the Google Fraud Defense admin area and sign in with your Google account

2. 2

   Click Create Key

3. 3

   Enter a display name that identifies the store, such as “My Store on Foxy”

4. 4

   Leave Application type set to Web

5. 5

   Click Add a domain and enter your custom subdomain (for example, secure.example.com)

6. 6

   Click Next step, enable Will you use challenges, and leave Tick box challenge selected (or choose Easy difficulty if you prefer)

7. 7

   Click Save

8. 8

   Copy the Site Key and, from Integrate with a third-party service or plug-in, the Secret key

9. 9

   In the Foxy admin, go to the Payment page and enter the Site Key and Secret key in their matching fields

10. 10

    Save your payment settings

To test, set the reCAPTCHA option to Enabled, Always and load your checkout to confirm it displays. Set it back to Enabled, Automatically once you’ve confirmed it works.

5. Update your store to use the new domain

Before switching your live traffic to the new subdomain, review and update anything that references your old Foxy domain, including:

• Add-to-cart links, forms, and view-cart links

• Your loader.js include path

• The base attribute on the Customer Portal element, or any custom element implementation

• Your Single Sign-On endpoint, if configured

• The legacy XML API, if you use it

• Link/form signing (HMAC validation), if your script references the store domain

• Your gateway’s webhook configuration, if it points to Foxy’s ipn.php endpoint

Notes

• Do not enable the custom domain setting until Foxy has confirmed your SSL certificate is provisioned and you’ve set up your DNS. Changing the setting too early will break your add-to-cart and checkout links, along with any JavaScript or CSS includes tied to the old domain.

• Foxy charges more for BYOSSL certificates because of the added setup, renewal, and support overhead — not just certificate cost. This covers firewall and WAF configuration, DNS, load balancing, failover, monitoring, and security scanning on Foxy’s side.