Connect Stripe
Connect a secure subdomain for Checkout, Payment Links, and the customer portal.
Open your domain’s DNS
- Sign in to your SaaSTech Servers Domain Portfolio External · opens new tab ↗.
- Select the individual domain to open its Domain Settings page.
- Select DNS.
Need help signing in? Find your username or password External · opens new tab ↗.
Choose an unused subdomain
Decide on a clear name such as payments. Confirm no A, AAAA, or CNAME record already uses that exact host.Manage records in SaaSTech DNSExternal · opens new tab ↗
Start in Stripe Dashboard
Open Custom domains settings, select Add your domain, and enter the complete subdomain. Stripe will display the required verification value.Open Stripe custom-domain settingsExternal · opens new tab ↗Stripe custom-domain guideExternal · opens new tab ↗
Create the CNAME
Add a CNAME for the chosen host pointing to hosted-checkout.stripecdn.com. Some DNS providers accept or require a trailing period.Add a CNAME in SaaSTech DNSExternal · opens new tab ↗
Create the verification TXT
Add the _acme-challenge record Stripe displays and paste its unique value exactly. This is required for Stripe to issue the TLS certificate.Add a TXT record in SaaSTech DNSExternal · opens new tab ↗
Wait, enable, and test
Wait for Stripe to report the domain ready, then enable it if automatic activation was disabled. Run a test-mode Checkout or Payment Link and verify the expected subdomain and secure connection.Open Stripe custom-domain settingsExternal · opens new tab ↗Check DNS with MXToolboxExternal · opens new tab ↗
Stripe connection records
| Type | Host | Value / target |
|---|---|---|
| CNAME | payments | hosted-checkout.stripecdn.com |
| TXT | _acme-challenge.payments | Copy unique value from Stripe |
payments is an example host. Replace it with the subdomain entered in Stripe. Stripe suggests TTL 300 where supported. Existing CAA records at the same host can prevent certificate issuance and should be reviewed, not deleted blindly.