Custom payment domain
Connect your branded domain to InAppify payments using CNAME and TXT records, DNS verification, and HTTPS activation
A custom payment domain, such as pay.example.com, hosts bank-redirection intermediary pages and bank callbacks for your project's merchant-gateway payments. It is a project-level setting shared by its apps, not a separate domain per app.
It does not change the bank's domain or move your landing page and every payment link to this hostname. InAppify-gateway payments continue to use the platform payment domain.
Prerequisites and dashboard path
Ensure you can edit your domain's DNS, choose a dedicated payment subdomain, and have permission to manage project gateways. Select the project and open Project settings → Gateway custom domain. The domain-setup notice in Payment gateways also links here.
Each project has one payment domain. A hostname cannot simultaneously belong to another project, and InAppify-reserved domains cannot be registered.
1. Register the subdomain
Enter only a hostname such as pay.example.com in Payment subdomain, then select Connect domain. Do not include https://, a port, path, or query string.
The dashboard displays DNS record details after registration. Copy those exact values; documentation examples are not replacements for your project values.
2. Add DNS records
Create both records in your DNS provider's dashboard using the values shown by InAppify:
| Record type | Example name | Value |
|---|---|---|
| CNAME | pay.example.com | Exact target shown in the InAppify dashboard |
| TXT | _inappify-payment.pay.example.com | Ownership-verification value shown after registration |
CNAME points the subdomain to the payment service; TXT proves ownership. Both must be correct.
Some DNS providers append the root domain automatically. For example.com, you may need to enter pay and _inappify-payment.pay. Check that the resulting full names match InAppify's record table without duplicating the domain suffix.
The TXT value starts with inappify-verification=. Copy the entire value unchanged. Do not publish API or gateway credentials as TXT. Do not replace the CNAME target with an invented hostname or IP.
3. Verify DNS
Once DNS changes are publicly visible, return to InAppify and choose Check. Verification requires both the ownership TXT and expected CNAME target.
If the TXT value is unavailable after reloading, use the page's action to generate a new verification value, then replace the old TXT value in DNS. Regeneration resets previous verification and activation; avoid doing this unnecessarily on an active domain.
4. Activate HTTPS
DNS verification is not the final step. The hostname also needs a valid HTTPS certificate and an active payment route. Pending HTTPS activation means DNS is verified but the domain is not ready for final use.
Use Refresh status to check progress. If the status persists, coordinate activation with support. Do not assume a fixed activation time or immediate readiness; wait for Active and secure before treating the merchant-gateway path as ready for live purchases.
Understand the statuses
- Pending DNS: ownership and destination records have not been verified.
- Pending HTTPS: DNS is verified, but secure activation remains incomplete.
- Active and secure: verification and activation are complete; the domain can serve project merchant-gateway payments.
- Disconnected: the domain is revoked and not ready for merchant-payment routing.
Coordinate with the gateway provider
If your provider restricts callback domains, the custom domain must match its merchant configuration. Do not guess callback URLs; coordinate required merchant settings with support. DNS configuration does not replace merchant approval or source-IP restrictions.
After activation, review the payment gateway and test redirection, return, and purchase results.
Troubleshooting and disconnection
- Invalid hostname: enter a valid hostname without a protocol or path.
- Domain assigned to another project: check the selected project and previous domain assignment; duplicate assignment is rejected.
- DNS not verified: check the full TXT name, current verification value, and CNAME target. If DNS proxying hides the CNAME, review settings for exposing the direct record. DNS propagation may not be immediate.
- HTTPS not activated: contact support if the status persists; DNS verification alone is insufficient.
Choose Disconnect and review the confirmation before revoking the domain. Merchant gateways may no longer be selected, and an available InAppify fallback gateway may be used instead. Review in-flight purchases and alternative routing before disconnecting or re-registering. This action does not delete records from your DNS provider.