Generate a Link
201 Created):
card.updated webhook with the old and new payment method tokens. The new token is a gateway-native token (e.g. a Stripe pm_xxx) — store it against the customer record and use it as the paymentMethodToken on future /api/recovery/execute calls for that customer.
Custom Domain Setup
By default, card update URLs use the Revtain domain — which means your customer seesapi.revtain.com in the browser. That looks unfamiliar and can reduce trust. Set up a custom domain before going live.
1
Choose a subdomain
Pick something recognisable:
pay.yourdomain.com or billing.yourdomain.com.2
Add a CNAME DNS record
Point your chosen subdomain at Revtain:
pay.yourdomain.com → api.revtain.com3
Enable SSL
If you use Cloudflare, SSL is automatic. Otherwise ensure your DNS provider issues a certificate for the subdomain.
4
Tell Revtain your domain
Share your subdomain with your Revtain account manager during onboarding. We configure it on our end — no further action needed from you.
Branding the Card Update Page
The card update page your customers see is white-labelled to your business. To make it look right, tell Revtain your brand details during onboarding:
If
brandName is not set, Revtain falls back to your registered business name. If no logo is provided, a lock icon is shown instead.
What your customer sees: