# OpenProvider Module

https://docs.wisecp.com/en/openprovider-module

Connect OpenProvider to WISECP to handle domain sales and keep provider settings accessible from each customer’s service record.

## Opening the Screen

Open **Products → Domains → Domain Name Registrars → All Modules → OpenProvider**: `{admin}/module/registrars?module=OpenProvider`.

## What Is on the Screen

**Module Settings** holds credentials, nameservers and costs. **Import** lists existing provider domains; **Import Extensions** lists extension prices.

### Prepare the provider account

1. Open your Openprovider reseller account and complete the provider’s account requirements. Keep funds available for domain purchases.
2. Under **Account → Account Overview**, open the username and click **Edit**.
3. Select **API access Enabled** and click **Update contact**. Allow the WISECP server’s outgoing IP if you restrict API access.
4. Keep that user’s username and normal password. The module obtains its access token automatically. See [enabling API access](https://support.openprovider.eu/hc/en-us/articles/360015453220-How-to-enable-API-access).

## Settings

- ****API Username****: Required; initially empty. Enter the username whose API access you enabled.
- ****API Password****: Required; initially empty. Enter that user’s password, not a password hash or manually generated token.
- ****Test Mode****: Off by default. In this module version, selecting it does not change the live API address. Do not use it as sandbox protection.
- ****Default Nameservers****: Four initially empty, optional entries. The first two carry required markers. Without both, service defaults use system nameservers.
- ****Automatic Cost Updates****: Off by default. Enables scheduled provider cost updates.
- ****Cost Currency****: Match the provider’s reseller price currency. Check the installation’s initial selection before importing or updating costs.

## Tasks

### Connect without purchasing

1. In **Module Settings**, enter the live API user and password. Keep **Test Mode** off.
2. Click **Test Connection** beside **Save Changes**. The check signs in and requests the domain list.
3. On success, click **Save Changes**. The test alone does not retain settings.
4. If access fails, check API permission, password and IP restrictions at Openprovider. No separate WISECP server record is required.

### Import extensions and existing domains

1. After verifying currency, open **Import Extensions**. Select extensions and click the tab’s **Import** button.
2. Check registrar assignments and sale prices under **Products → Domains**. Import can update existing extensions using your profit rate.
3. For domains already at Openprovider, open **Import**. Assign customers, review dates and click **Import**.
4. Verify the service customer, provider and expiry. Import adds a local service without purchasing or transferring the domain.

### Register, transfer and renew

Assign the sold extension to OpenProvider and complete its WHOIS contacts and nameservers. The module creates owner, administrative, technical and billing contacts before submitting registration. Transfers require the losing registrar’s unlock and EPP code and remain pending until completion. Renewal sends the selected years to the provider.

Registration follows the Openprovider account’s default auto-renew policy. Coordinate this with WISECP billing. Inspect provider orders and expiry before retrying an uncertain purchase. For extensions requiring extra eligibility data, confirm that the current module supplies it before offering sales.

### Manage a domain

Open a domain under **Orders → Services**. **DNS** provides nameserver changes, child nameserver add/edit/delete and provider DNS records. The listed types are A, AAAA, CAA, CNAME, MX, SPF, SRV, TXT, NS, TLSA, SSHFP and SOA.

Opening DNS records can create a missing Openprovider DNS zone automatically. Use the provider’s authoritative nameservers for records to affect resolution. Review zone charges before opening this section.

**WHOIS** manages the four contact types and eligible privacy. **Transfer** manages locking; **Get Auth (EPP) Code** retrieves the provider’s code. Status and expiry synchronization are supported.

Customers manage their own domain through service details, subject to permissions and addons. DNS management and privacy may require an active addon. This module does not provide DNSSEC, web/email forwarding or redemption restore, even where the provider offers them separately.

## Things to Watch

> **The test switch does not isolate purchases**
> 
> The current WISECP module always uses the live Openprovider API address. Do not place test registrations, transfers or renewals with this switch enabled. A successful connection check proves access only.

> **Provider sandbox is separate**
> 
> [Openprovider’s sandbox](https://support.openprovider.eu/hc/en-us/articles/8095671860114-Sandbox-Testing-Environment) requires a separate account and API address. It does not support transfers. Use it directly for provider tests; this module has no sandbox-address field.

> **Review operating costs**
> 
> Privacy follows the WISECP addon and provider eligibility. Check provider fees, account auto-renew, scheduled cost updates and sale margins regularly.

## Privileges

**Domain Name Registrars** is required for setup. Service operations require the appropriate service permissions.

## Related Guides

- [Registrar Modules](https://docs.wisecp.com/en/registrar-modules)
- [Domain Extensions](https://docs.wisecp.com/en/domain-extensions-and-pricing)
- [Service DNS Management](https://docs.wisecp.com/en/service-dns-management)
- [Service WHOIS Records](https://docs.wisecp.com/en/service-whois-records)
- [Service Transfer](https://docs.wisecp.com/en/service-transfer)