Package and credentials
The core bridge applies to the separately installed verified ResellerClub 1.3.1 registrar module. It is not a replacement base package or an imported live connection. Consult that exact package's schema for all fields. Core reads use the configured environment, reseller ID (reseller_id) and encrypted api_key; writes need explicit allow_writes. Sandbox and live use their own fixed HTTPS API destinations.
The bridge preserves the provider's documented repeated parameter encoding for nameserver/options lists. It does not transmit PHP bracket-style arrays where ResellerClub expects repeated API parameter names. Keep credentials private and configure the registrar's required API account funding/source-access controls separately.
Registration input
The record supplies the exact domain. Provider options require an existing positive provider customer ID and registrant, administrator, technical and billing contact IDs, not local EmailaBiller IDs. Supply explicit nameservers and a supported 1–10-year term. The bridge checks regular nonpremium availability and current product term bounds before submission.
Registration uses the provider's existing contacts, NoInvoice for its separate invoice option and provider auto-renew false. This does not replace your customer's EmailaBiller invoice or authorise hidden future registrar charges. Missing/invalid contacts, unsupported terms or premium names require review.
Sync and management
A fresh exact domain read returns provider order/entity ID, state, expiry, nameservers and available privacy/lock flags. It checks that a returned domain name matches the requested record. Provider IDs come from the account read, never from the local inventory primary key. Accepted but unreadable registration remains pending for later synchronization.
Other actions retain the base module's declared support. The reviewed 1.3.1 compatibility path supports protected EPP requests after account confirmation; secrets stay out of normal refresh/audit output. It does not imply every installed registrar or newer source version has the same EPP capability.
Recovery
A transport failure after dispatch may follow an accepted billable request. Inspect the original ResellerClub account and synchronize before retrying. Do not change registrar, erase the durable purchase marker or enter somebody else's contact IDs to make registration pass. A local record or catalogue price is not proof of provider ownership or registry completion.