Authorization Code (a.k.a. Domain Secret) of the domain name that you want to transfer.
The Authorization Code would be required to transfer a domain name of any of the following TLDs (extensions):
.AU
.BIZ
.BZ
.CA
.CC
.CO
.COM
.COOP
.DE
.EU
.IN (including only these Third Level .IN Domains: .CO.IN, .NET.IN, .ORG.IN, .GEN.IN, .FIRM.IN, .IND.IN)
.INFO
.MN
.MOBI
.NAME
.NET
.NL
.NZ
.ORG
.TV
.US
.WS
.XXX
You may fetch the auth-code from your customer and provide it while placing the Transfer Order. Alternatively, you may initially place the Transfer Order without the auth-code. The Administrative Contact can provide it at the time of approving the Transfer Authorization email received from .
It is recommended that you adopt the second option since it leaves out the requirement for an auth-code at the time of placing the Transfer Order and the customer would be more willing to submit it at a later stage.
Domain Name Extensions for which the Authorization Code needs to be compulsorily provided at this stage:
.EU, .NZ, .RU and .UK domain names do not have an Administrative Contact associated with them. You need to pass the value of admin-contact-id as -1 for these domain names.
The Technical Contact associated with a .EU domain name cannot be modified while .NZ, .RU and .UK domain names do not have a Technical Contact associated with them. You need to pass the value of tech-contact-id as -1 for these domain names.
The Billing Contact associated with a .EU domain name cannot be modified while .AT, .BERLIN, .CA, .NL, .NZ, .RU and .UK domain names do not have a Billing Contact associated with them. You need to pass the value of billing-contact-id as -1 for these domain names.
Mapping value of the extra details required to transfer a domain name. This together with attr-name shall contain the extra details.
To transfer a .ASIA domain name:
cedcontactid: For a .ASIA domain name, 'Charter Eligibility Declaration Contact ID' is mandatory. This parameter represents the CED
Contact ID. You may select any one of the Admin, Technical, Billing or Registrant Contacts as a value for this parameter.
Description of the Domain Transfer Action (actiontypedesc)
Action ID of the Domain Transfer Action (eaqid)
Domain Transfer Action Status (actionstatus)
Description of the Domain Transfer Action Status (actionstatusdesc)
Invoice ID of the Domain Transfer Invoice (invoiceid)
Selling Currency of the Reseller (sellingcurrencysymbol)
Selling Curreny Amount (sellingamount)
Customer ID associated with the Domain Name Order (customerid)
Privacy Protection Details (privacydetails)
Domain Name (description)
Order ID of the Domain Registration Order (entityid)
Action Type (actiontype)
Description of the Privacy Protection Purchase Action (actiontypedesc)
Action ID of the Privacy Protection Purchase Action (eaqid)
Privacy Protection Purchase Action Status (actionstatus)
Description of the Privacy Protection Purchase Action Status (actionstatusdesc)
Invoice ID of the Privacy Protection Purchase Invoice (invoiceid)
Selling Currency of the Reseller (sellingcurrencysymbol)
Transaction Amount in the Selling Currency (sellingamount)
Unutilized Transaction Amount in the Selling Currency (unutilisedsellingamount)
Customer ID associated with the Domain Registration Order (customerid)
Note
invoiceid, sellingcurrencysymbol, sellingamount and customerid will not be returned if invoice-option is set to NoInvoice.
In case of an error, a status key with value as ERROR alongwith an error message will be returned. However, if the transfer action is waiting on user input or registry response, the value No Error will be returned.
VAT (Value Added Tax) is a tax levied on goods and services sold in Russia.
How does this affect me?
If VAT for Russia is enabled, the invoices generated for customers who are charged VAT for Russia will be updated to include VAT (20.00% w.e.f September 01, 2019).
How do I add my VAT ID?
You can add your VAT ID after you start charging VAT for Russia. Learn how.
The following method must be used if the customer requests to re-send the authorization email to disable the GDPR Protection setting (e.g., in situations where the Registrant contact may not have received the initial email).
