Custom domains
Serve your forms from your own domain, such as forms.acme.com, so Razorpay and Cashfree checkouts work.
Every form in your organization can be served from one domain of your own, such
as forms.acme.com, instead of chatform.in. It is a Pro feature, and only an
owner or admin can set it up. An organization has one domain.
A domain is also what lets payments work. Razorpay and Cashfree take payments only on a website you registered with them, and that has to be your address, not chatform.in. Until your domain is Live, the gateway options in verified payments stay locked.
Connect a domain
In a form's Share tab, under the link, enter a subdomain in Custom domain and press Connect.
Use a subdomain, not your main website. Entering acme.com is refused with a
suggestion such as forms.acme.com, so that your site keeps working. The
domain has to be one you control, because the next step proves it.
Add the two DNS records
Chatform shows two records to add at the company that runs your DNS:
| Type | Name | Value |
|---|---|---|
CNAME | your subdomain, such as forms | where chatform serves from |
TXT | _chatform plus your subdomain, such as _chatform.forms | chatform-verify= and a code |
The CNAME sends visitors to chatform. The TXT proves the domain is yours. Names are shown relative to your root domain, which is what DNS dashboards ask for, and each cell has a copy icon.
Set up automatically. When your DNS provider supports Domain Connect, chatform shows a Set up automatically button that adds both records after one consent screen. Otherwise it shows a link to your provider's DNS page when it recognises the provider.
If your DNS is on Cloudflare, turn off the proxy (the orange cloud) on the CNAME record.
Wait for it to go Live
The status reads Waiting for DNS, then Live. Chatform checks by itself while the Share tab is open and keeps checking when you leave, and Check now asks straight away. DNS changes usually show up within minutes but can take up to 24 hours. A line under the status says what is missing, such as the CNAME or TXT record.
If it never validates the status becomes Failed, and Try again starts over.
What changes once it is Live
- Forms are served at
https://forms.acme.com/<slug>. - A form's chatform.in link sends visitors to the same form on your domain. Embeds written before the domain existed keep working.
- Only forms are served there. Your domain has no dashboard or marketing site.
- Verified payments can be connected, and their forms can be published.
Removing the domain sends forms back to their chatform.in links and locks verified gateway payments until another domain is Live.
Register the domain with your gateway
Razorpay and Cashfree also need the domain added in their own dashboards. The steps, with your domain filled in, are in Register your domain with the gateway. Stripe needs nothing.
From the API
These endpoints need the payment scopes, which no key preset
includes, and the Pro plan.
| Endpoint | Scope | What it does |
|---|---|---|
GET /v1/domains | payment:read | The domain with its records, or null. Reads the stored state |
POST /v1/domains | payment:write | { "hostname" } connects a subdomain; 201, pending until DNS validates |
POST /v1/domains/check | payment:write | Asks Cloudflare now instead of waiting for the next check |
DELETE /v1/domains | payment:write | Removes the domain |
status is pending, active or failed, and each record is { type, name, value }. A main domain is a 422. A hostname another organization holds is a
409 that returns the TXT record which would move it to you. The
API reference has every field.
After status is active, register the domain in the gateway's dashboard as
described above.
Consent
Agreeing to terms, a waiver, a code of conduct. Put the wording in `description`. By default the only answer is yes; add decline=true when a refusal has to be a real answer you can route on: an eligibility gate, a policy someone may decline.
Verified payments
Take payment on your own Razorpay, Cashfree or Stripe account, and move on only once the gateway confirms it.