nour.net.sa

Goal: to clarify questions regarding scope of work and requirements:

Request:

We want to upgrade existing services from nour.net.sa (provider), we want to work with UX of the portal and also extend functionality.

Questions:

• could we obtain access to existing customer panel? We were not able to break throw SMS verification limited to Saudi phone number.
  • Should Provider work only with Saudi citizens, or it should be international service?

  Provider oriented on local citizens and primary goal is to sell local country specific domains.

• the main service that we should provide is domain registration?
  • does SA zone registrar provides some test or stage environment to test EPP integration with them?

• Could we obtain access to existing admin panel?
  • We need to understand how you want to work with prices
  • Also we need to understand, is your current billing solution based on WHMCS or something similar, or you have some requirements that could not be covered by them, and we have to build all from scratch? From what we see, there is a very strict KYC requirements plus custom payment solution

• Do we need to support recurrent payments? HyperPay supports it, but Sadad — seems to be missing that feature. https://dg-cash.com/contact/

• In requirements we see: “Ensure seamless bundling of services during domain registration”. Does that means that we should have some interop with other service portals to sell them together? How it should behave, would be great to have better explanation

• we will need help to integrate with Nafath. Nafath is a government based SSO in SA, that allows to identify any citizen. Like E-passport. We will need some accounts to testing it, because we are not citizens of country.

• providing NS services is also part of our portal, what existing solution used to manage NS server settings?

• What should we do with existing customers? Should we migrate existing accounts? Should we migrate purchase history, existing products, etc? If yes — then we would need some documentation on existing system. Have you any?

• Have you any docs on existing system? It would be nice to get some product and tech docs, if they are exist

• Is providing email services also part of the portal? Should we manage dkim, dmarc etc from our side?

PreEstimation

The solution architecture for the revamp of the NourNet eServices portal can be divided into the following key components:

User Registration and Authentication

There are two options:

• Implement integrated Single Sign-On (SSO) across all products using tools like Keycloak or AuthKit for robust security and scalability. Keycloak is widely supported and can cater to extended integration needs.
• Alternatively, for solutions focusing solely on the portal, consider lightweight authentication platforms like Better Auth

KYC Process Management

• Client-Side: Handle user verification procedures partially with existing third party providers. Collaborate closely with providers to document and manage the KYC data, including handling NIC (Network Information Center) data.
• Admin-Side: Develop a secure admin panel for KYC status monitoring and document exchange. This ensures compliance and efficiency, allowing the management of multiple NIC handles under a single user account. From regulatory side we have to make KYC for every new handle, not only for initial registration.

Domain Shop Functionality

• Develop a streamlined process where users can search for domain availability, select additional services, and complete purchases with ease.

Payment System Integration

• Implement both real-time credit card processing and delayed invoice-based payment models. It includers integration with local services like Hyper Pay and Sadad to ensure comprehensive coverage.

EPP Integration

• Conduct thorough testing with the Saudi NIC EPP (Extensible Provisioning Protocol) system. Be prepared to adapt to any inconsistencies or deviations in protocol standards through close interaction with testing environments. If now testing environment present — it could cause big delays in implementation.

CRM Integration

• Export customer data to a CRM solution for holistic customer management and analytics. If no preferred CRM exists, consider starting with Hubspot for its user-friendly features and integration capabilities. CRM will be a master data storage that collects customer data from all yours products.

Upselling and Cross-Selling Features

• Implement recommendation systems and pop-ups to promote related services. Define a flexible integration system to accommodate future partnerships and offerings.

Estimations:

• Registration: SSO, up to one month.
• Registration: without SSO, up to two weeks
• KYC process (client side): near one month
• KYC process (admin side): few weeks
• Shop functionality: up to month
• Payment system integration: up to month
• EPP integration: up to two month
• CRM integration: few weeks
• Up sale functionality: month or two

Estimation, $

Cover letter

The KYC process should be discussed with the registrar. According to the documentation, they require full KYC for each NIC handle. However, there may be instances where this requirement can be bypassed. This has a significant impact on the user flow, and it needs to be clarified before coding begins, during the BA phase.

Additionally, if there is no test environment or test mode for the EPP provided by the registrar, we might need to allocate extra resources to purchase or transfer some real domains for development purposes and also an extra time.

Regarding DNSSEC, it is supported by the registrar. However, we will exclude it from the current estimation because we need to complete the EPP integration first. Implementing DNSSEC will be a subsequent step for product improvement.