Domain resellers need to coordinate two processes: collecting the customer's payment and renewing the domain at the registrar. A paid invoice does not prove that renewal succeeded, and an unpaid invoice does not automatically stop registrar renewal. Use Openprovider for registrar management and PayRequest for customer billing and the portal, with an explicit check between them.
This guide gives new domain sellers a date checklist, an exception matrix and a fictional annual-service example. It describes a process you can configure and review, not a universal automatic renewal workflow.
Track four dates separately
A domain can have a customer invoice date, a payment deadline, a registrar renewal date and an expiration date. They do not necessarily fall on the same day.
Openprovider's official domain renewal guide discusses renewal and refers resellers to its renewal policies. Check the rules for the actual extension and account before deciding when to act.
| Date | Why you need it |
|---|---|
| Next customer billing | Know when the next payment obligation is created |
| Customer payment deadline | Leave time for reminders and manual follow-up |
| Registrar renewal event | Understand when an upstream purchase obligation may arise |
| Domain expiration | Monitor the end of the currently registered period |
Do not infer registrar dates from an old customer invoice. Use current provider information and record when it was checked. Registration, renewal and transfer prices also need separate review.
Keep one operational record per domain
Record the domain name, customer, subscription, registrar, currency, annual selling price, known renewal cost, payment status and the four dates. Assign a person responsible for resolving mismatches.
PayRequest connects domain registrations to customers and subscriptions. Its Openprovider margin functions include a workflow for renewal costs and reference prices. Any margin view still depends on complete, current cost information. A standard extension quote does not establish the cost of every premium domain or restoration.
Keep unknown costs marked as unknown. A blank cost is a reason to investigate, not a zero-cost domain. When reviewing contribution, use actual invoices where available and distinguish them from catalog indications.
Plan customer billing ahead of the registrar decision
Fictional schedule, not Openprovider policy: suppose the registrar renewal event you verified is 30 June. Your own process might invoice on 1 June, set a 10 June payment deadline and review unpaid accounts on 12 June.
Whether that schedule is suitable depends on the extension, the contract and the registrar configuration. It is not a recommendation to apply an automatic cutoff on those dates.
Before using any schedule, establish which action remains possible, its deadline and how you verify the result at the registrar. Explain the consequences of nonpayment or cancellation to the customer before renewal becomes urgent.
Use a payment-versus-registrar exception matrix
Payment and registrar state should be checked independently. The following matrix is a reseller decision aid; it is not a claim that every PayRequest account runs this as an automated state machine.
| Customer payment | Registrar state | Follow-up |
|---|---|---|
| Paid | Renewal confirmed | Verify the new period and close the renewal review |
| Paid | Renewal failed or unknown | Investigate the provider status and inform the customer; check before requesting payment again |
| Unpaid | Already renewed | Handle the receivable and record the incurred upstream cost |
| Unpaid | Not yet renewed | Follow the agreed policy and check which registrar actions remain available |
| Cancelled | Automatic renewal still enabled | Review the mismatch between customer agreement and registrar configuration in time |
This also helps distinguish two different support incidents: “the customer has not paid” and “the registrar action has not completed.” Each needs its own owner and evidence.
Price the second year before offering the first
A low introductory registration cost may not represent the renewal cost. Calculate the next period using the same currency and VAT basis across inputs. Use actual costs and state what is excluded.
Fictional example: annual domain revenue is €24, renewal purchase cost is €13 and payment processing costs €1. That leaves €10 before support, platform costs and other overhead. An hour spent resolving a payment problem can change the contribution substantially. These figures are not Openprovider rates or PayRequest fees.
For different customer agreements, see the separate domain reseller price-list guide. Do not silently rewrite the price of an accepted subscription simply because a new catalog price exists.
Make the customer view understandable
Give customers a recognizable place to find their domain service, subscription and invoices. Review the displayed service period and payment status. An invoice marked paid should not imply that an unconfirmed registrar operation has completed.
If a customer cancels, explain which service ends and what they need to arrange if they want to retain or transfer the domain. Cancelling a billing subscription is a different event from completing a transfer, deleting a domain or confirming that registrar auto-renewal is disabled.
A portal may reduce repeated information requests, but do not assume a fixed support saving without measurement. Track the questions your actual customers ask and improve the process from that evidence.
Start with one annual domain service
Choose one extension and write a clear renewal policy. Check the relationship between customer, domain, subscription and provider status. Then establish who reviews unpaid accounts and registrar exceptions before the critical dates.
Explore the Openprovider integration with PayRequest for the provider connection, and PayRequest Hosting Billing for the billing and customer environment around it.
Editorial note: prepared with AI assistance. Product code and sources were reviewed on 5 November 2026. Dates and figures are fictional examples. No renewals, collections or cancellations were performed for this article; the cover is an illustration.
