Your own checkout domain

What changes for buyers

By default buyers check out on LatchPay's own checkout host. With a checkout domain they check out on a subdomain of your domain instead, for example checkout.your-domain.com: the checkout, the thank-you page and the payment all live there. Everything else stays as it is.

• Your storefront stays on Shopify, on the domain it has today. The checkout domain is an extra name that points at LatchPay.
• The theme line does not change. It learns the new host on its own the moment the domain is live, so there is nothing to paste again.
• Until the domain is live, and whenever it is paused or removed, buyers use the central checkout host exactly as before. Nothing breaks while you set it up.

It is set per store, in Settings under Checkout domain. Each store can have one.

Pick a subdomain

Choose a subdomain you do not use yet, such as checkout., pay. or secure. in front of your domain. Two names are refused on purpose:

• Your root domain (your-domain.com) and www. Pointing either at LatchPay would move your whole storefront away from Shopify.
• Your storefront domain as Shopify knows it, or any name under a .myshopify.com address. Those must keep pointing at Shopify.

You need to be able to add DNS records for the domain: at your registrar, at Cloudflare, or wherever the domain's DNS is managed. If someone else manages it for you, send them the record from the next step.

Add the CNAME record

1. 1

   Add the domain in Settings

   Type the subdomain under Checkout domain and press Add domain. The section then shows the DNS record to add, with a Copy button next to each part.

2. 2

   Create one CNAME record at your DNS provider

   Type CNAME, Name the subdomain, Value the target the section shows. LatchPay shows the Name as the full hostname (checkout.your-domain.com); some providers want only the left label (checkout) and add your domain themselves. A TTL of 300 seconds, or the provider's "automatic", is fine.

3. 3

   Cloudflare: switch the proxy off for this record

   Set the record to DNS only (the grey cloud, not the orange one). With the proxy on, Cloudflare would sit in front of the checkout and the certificate cannot be issued for it.

The TXT record, when it appears

Usually only the CNAME is needed. When the subdomain is already in use on another hosting account, the section shows a second record with the pill Ownership check: a TXT record named _vercel under your domain, with a value that proves the domain is yours. Add it next to the CNAME and press Check now. It does not move the domain and it can stay in place afterwards. This happens, for example, when the same subdomain was used for a checkout hosted elsewhere before you moved to LatchPay.

Waiting for DNS and the certificate

After you add the record the pill reads Waiting for DNS. While the Settings page is open it checks every 20 seconds on its own; Check now checks at once. DNS changes usually spread within minutes, sometimes up to an hour. Once the record is seen the pill reads Issuing certificate; the certificate takes a few minutes. When it is in place the pill turns Live and buyers are sent to your domain from their next page load.

• A domain that has waited a week reads Still waiting. Nothing is lost: add the record and check again, or remove the domain.
• Once live, LatchPay keeps checking every hour. If the record disappears, the pill reads DNS not pointing at us and buyers go back to the central checkout until the record is back. Buyers already in a checkout on your domain finish there.

Apple Pay and Google Pay on your domain

Apple Pay and Google Pay only appear on a host that is registered as a payment domain on your Whop business. For the central checkout host that is done once for every store; for your own domain LatchPay registers it on your business automatically when the domain turns live, and the section shows an Apple Pay and Google Pay line with the result. It usually completes within the hour. Cards and the other payment methods work on your domain right away.

If the line says the registration did not complete, the Payment methods card in the checkout editor explains why, most often a missing optional permission on the LatchPay app in Whop.

Pause, remove or change the domain

• Pause sends buyers back to the central checkout on their next page load. The domain and its DNS record stay; Resume runs a full check and makes it live again.
• Remove sends buyers back right away; buyers with an open checkout on your domain are sent to the central checkout too. Then delete the CNAME record at your DNS provider. The name stays reserved for your store until it no longer points at LatchPay, so nobody else can pick it up in the meantime, and it is released once the record is gone.
• Change to another subdomain: remove the current one (or pause it), add the new one and add its record. Buyers use the central checkout in between.

Troubleshooting

• Waiting for DNS for more than an hour. Check the record at your provider: the Name is the subdomain only, the Type is CNAME (not A), the Value is exactly the target shown, and at Cloudflare the cloud is grey. Remove any older A or CNAME record for the same name.
• Issuing certificate for more than fifteen minutes. A CAA record that does not allow Let's Encrypt, or a proxy in front of the record, stops the issue. Fix it and press Check now.
• Could not add. The hosting platform refused the name, usually because it is attached to another account LatchPay cannot see. Remove it here and contact support, or use a different subdomain.
• "This domain is already used by another store." Each hostname belongs to one store. If it is yours, contact support.
• "Custom checkout domains are not enabled on this deployment." The feature is switched off on the LatchPay deployment you use. Buyers use the central checkout; nothing else is affected.