Publishing should not require assembling five unrelated vendors
A usable business website needs more than pages: it needs a name, correct DNS, a valid certificate, resilient hosting and a payment connection the owner can test.
i3nb brings those stages into the tenant-site workflow while retaining the host’s choice. Search and register a supported domain, connect an existing one, or start with a platform subdomain before moving to the final branded address.
Domain registration
Search supported extensions, see term pricing, register for one or more years and manage renewal status from the site workflow.
Bring your own domain
Attach an existing name using a generated verification record rather than transferring ownership just to publish the site.
Managed HTTPS hosting
Verified domains enter managed certificate and load-balancer provisioning with status, health and recovery state visible.
Payment gateway setup
Store encrypted live and sandbox credentials, test them against the provider, and activate Stripe, PayPal or Square on an eligible custom domain.
Register a name or connect the one the business already owns
The domain flow supports both paths because brand ownership and hosting ownership do not have to be the same thing.
Search and transparent term choice.
Look up availability, review the supported top-level domain and select a registration term from one to ten years.
Identity and payment controls.
Registration follows the required identity, plan-credit and payment checks before an order is submitted to the registrar.
Renewal management.
Expiration and automatic-renewal state remain visible instead of being buried in a separate registrar account.
Existing-domain verification.
A host can prove control with the instructed TXT or DNS authorization record and retain the domain at the current registrar.
DNS and certificates become a trackable publishing process
Custom-domain setup is asynchronous in the real world. i3nb keeps the states explicit so a host knows whether the next step is DNS, certificate issuance or traffic activation.
Generated DNS instructions.
The exact verification or authorization record is presented for the domain rather than relying on generic help text.
Managed certificate.
After domain control is proven, Google-managed certificate resources provide HTTPS without the host renewing certificate files manually.
Shared hosting infrastructure.
The site is attached to the managed load-balancing and certificate infrastructure instead of a one-off server.
Health and recovery.
Provisioning status and retry/recovery paths make incomplete setup visible and actionable.
Payment credentials remain private to the tenant site
Direct booking only becomes credible when the gateway can be configured, tested and separated between sandbox and live use.
Three supported gateways.
Connect Stripe, PayPal or Square according to the host’s provider and market.
Encrypted credentials.
Stored keys and secrets are encrypted and remain scoped to the tenant site rather than exposed in public site configuration.
Provider-level test.
The setup verifies credentials against the relevant provider API before the host relies on them.
Custom-domain boundary.
Payment collection is intentionally enabled on verified custom domains, not on temporary platform subdomains.
How it works
- Choose or connect the domain. Register a supported name or attach an existing domain to the tenant site.
- Complete DNS verification. Publish the exact generated record and let i3nb confirm domain control.
- Provision HTTPS and traffic. The verified domain advances through certificate and managed-hosting states.
- Test the payment gateway. Save encrypted sandbox or live credentials, verify the provider connection and enable eligible checkout.
Questions
Do I have to transfer my existing domain to i3nb?
No. You can keep it at its current registrar and prove control by adding the generated DNS verification or authorization record.
Does i3nb provide HTTPS for a connected domain?
Yes. Once ownership and DNS are correctly configured, the domain enters managed certificate provisioning and the tenant-site hosting workflow.
Which payment gateways can be configured?
Stripe, PayPal and Square credentials can be stored encrypted in live or sandbox mode and tested against the provider for an eligible custom-domain site.