Host your branded cancel page on your own subdomain. Your customers see cancel.yourcompany.com instead of chaser.cash. Takes about 10 minutes.
You create a CNAME record on your DNS provider pointing your subdomain to cname.chaser.cash.
chaser.cash verifies the CNAME and issues an SSL certificate automatically.
Your cancel page is live on your subdomain. Customers never see chaser.cash.
In your DNS provider dashboard, add a new record with these values:
Type: CNAME Host: cancel (or any subdomain you prefer) Answer: cname.chaser.cash TTL: 300
The host value becomes the subdomain. Using cancel gives you cancel.yourcompany.com. You can use any subdomain that is not already taken.
DNS changes typically take 1 to 5 minutes to propagate when TTL is set to 300. In some cases it can take up to 30 minutes. The verify button in chaser.cash checks in real time.
Go to Integrations, open the Cancellation Recovery tab, scroll to Custom domain, and enter your full subdomain:
cancel.yourcompany.com
chaser.cash checks for the CNAME record pointing to cname.chaser.cash. When verified, the domain shows a green Verified badge and SSL is provisioned automatically.
Once verified, click Open test page next to the Verified badge. This mints a real token and opens your branded cancel page on your custom domain. Confirm it loads correctly and SSL is green in the browser.
After verifying, update the cancel page URL in your application to use your custom domain instead of chaser.cash:
# Before
https://chaser.cash/cancel/{workspaceId}?token={token}
# After
https://cancel.yourcompany.com/{workspaceId}?token={token}The token minting endpoint stays the same. Only the redirect URL changes.
The verify button returns this when chaser.cash cannot find a CNAME record pointing to cname.chaser.cash. Check your DNS provider and confirm the record was saved. Wait 5 minutes and try again. DNS changes can take time to propagate.
If the verify button shows the CNAME was found but points somewhere else, update the record in your DNS provider to point to cname.chaser.cash and verify again.
If your custom domain loads but shows an SSL warning, the certificate may still be provisioning. Wait 2 minutes and reload. If the error persists, remove the domain in chaser.cash and re-add it to trigger a fresh certificate request.
Saving the domain and verifying are two separate steps. After clicking Save domain, click Verify to trigger the DNS check. The domain stays Unverified until the verify check passes.
cname.chaser.cash is an intermediary record controlled by chaser.cash. It resolves to Lovable's hosting servers (185.158.133.1) where your cancel page runs.
your-subdomain.com -> CNAME -> cname.chaser.cash -> A record -> 185.158.133.1 -> Lovable hosting -> your cancel page
Using cname.chaser.cash as the target means if chaser.cash ever changes hosting infrastructure, your domain continues working automatically. You never need to update your DNS record.