Package boundary
This guide describes the core compatibility bridge for a separately installed verified NameSilo 1.3.1 module. It does not provide that missing base module, copy an installed merchant account or certify your registrar access. Use the actual signed base package's own configuration schema alongside these bridge rules. Newer independent registrar source packages are listed separately in the integration directory.
The bridge uses the configured environment (sandbox or live), encrypted api_key, allow_writes, optional payment_id, default privacy and the original connection identity. Reads target fixed NameSilo environment hosts with verified TLS. Purchases require genuine account funding/API approval and a permitted source-IP configuration under the registrar's current policy.
Register and transfer
The domain must be regular available inventory for a supported term. Register accepts 1–10 whole years where that TLD is priced/supported; transfer is one year and requires the actual authorisation code. Supply 2–13 explicit distinct nameservers. Transfers cannot silently omit the intended DNS and inherit an account default.
Registrant data uses the owning customer's real saved profile, or an explicitly verified NameSilo contact ID. Required direct fields include first/last name, address, city, state, postcode, country, email and valid local-format phone; US/CA require appropriate regional/phone formats. Restricted .ca/.eu/.us eligibility may require an existing valid contact profile or additional explicit fields. Missing data is held rather than filled from the operator's business.
Confirmation
A purchase is submitted once. Provider responses that substitute contact or nameservers remain pending review; an account-owned fresh read must match domain, intended registrant and DNS before activation. Renewal uses one legacy purchase dispatch and then confirms an advanced registry expiry through the same assigned account. A timeout or incomplete read never triggers another purchase automatically.
Nameserver writes first verify the exact account/domain and confirm the final list. Already-correct DNS is idempotent. EPP retrieval is a protected staff action after account ownership confirmation; the result is shown privately or explicitly reported delivered to the registered contact, never mixed into general sync/audit data.
Availability and limits
The bridge supports bounded batched checks of up to 20 domains; missing/contradictory results do not become available claims. Other operations retain the verified base module's own capabilities. Do not infer a contact-edit API, automated refund or registrar cancellation from these compatibility methods. Inspect the original provider account before retrying any uncertain mutation.