TXT verification guide
When micro-payment verification is not feasible, or you need to prove domain control via DNS, complete merchant verification with a TXT record. Once verified, the binding has the same effect as micro-payment verification.
What is TXT verification?
The system checks a specific TXT record on your domain. If the record value matches the verification token shown in the merchant portal, you are confirmed as the domain owner.
- Subject: pending domain binding
- Domain: apex domain / Punycode submitted in the portal
- Method: public DNS TXT lookup compared to portal token
When to use TXT verification
TXT is a fallback; prefer random micro-amount verification in the portal when possible.
Use TXT when: checkout cannot process micro-payments, cross-border receipt delays, or you prefer DNS-based proof. Log in to the merchant portal → select TXT verification for pending bindings (or contact support to enable checks).
Steps (summary)
- Log in to the portal and copy the TXT host and token for the pending binding
- Add a TXT record in DNS (see table)
- Wait for DNS propagation (minutes to hours)
- Return to the portal and click "Check TXT and verify"
| Item | Value |
|---|---|
| Host | 302wallet |
| Type | TXT |
| Value | Portal token (copy exactly, no spaces) |
| TTL | Default / 600 |
Adding TXT in DNS console
- Log in to registrar or DNS provider
- Open DNS for the domain to verify
- Add record: type
TXT, host302wallet, value = portal token - After saving, check with
dig TXT 302wallet.yourdomain.comor an online DNS tool
Note: some panels want only 302wallet in the host field—do not repeat the full domain. Cloudflare users: watch CNAME flattening rules that may affect TXT.
idnwallet.com platform notes
This guide applies to idnwallet.com / 域名钱包.com. Host prefix 302wallet is recognized by our resolver and works with CNAME to 302wallet.com.
We only verify routing—no payment data is stored. After TXT verification, the binding activates and routing is written to resolver Redis.