Payment domains
White-label driver payment pages on the tenant's own hostname, such as pay.example.com. The same pipeline as OCPP domains: prepare the hostname, add the two DNS records, verify, then Ivora's edge worker issues the certificate (pending_dns, dns_verified, active). A ready payment domain becomes the tenant's checkout_origin for QR codes and hosted checkout returns. Requires stations:read or stations:write. A hostname serves either OCPP or payment, not both. Not yet available in production.
5 endpoints
- getList custom payment domains and DNS/TLS readiness/v1/tenants/{tenant_id}/payment-domains
- postPrepare a tenant payment domain and its two DNS records/v1/tenants/{tenant_id}/payment-domainsIdempotent by tenant and normalized hostname.
- getRead one payment domain setup/v1/tenants/{tenant_id}/payment-domains/{domain_id}
- deleteDisable this payment domain/v1/tenants/{tenant_id}/payment-domains/{domain_id}New page loads on this hostname are refused and QR codes and checkout returns fall back to the default payment host.
- postCheck public DNS ownership and direct routing/v1/tenants/{tenant_id}/payment-domains/{domain_id}/verifyDNS verification (dns verified) does not mean TLS is active.