Heading
Letterheads shall contain From and Content-type fields.
| Field name |
Example of use |
| From |
your_contact_email@your_domain.ru |
| Content-type |
text/plain; charset=koi8-r |
Ready heading example:
From: your_contact_email@your_domain.ru
Content-type: text/plain; charset=koi8-r
|
Authorization block
The email body begins with the authorization block.
| Field name |
Value |
Required or optional |
| action |
NEW | PROLONG | UPDATE |
Yes |
| pay-type |
real | bonus | real,bonus | bonus,real |
No |
| agreement |
YOUR_AGREEMENT |
Yes |
| password |
YOUR_PASSWORD |
Yes |
|
An example of a ready authorization block:
action: NEW
pay-type: real,bonus
agreement: RP/01/00
password: hJk4Gds
The pay-type field determines the funds withdrawal option.
Possible pay-type field options (separated by commas with a random space number):
real means the funds are withdrawn from the personal account (default);
bonus means the funds are withdrawn from the bonus account;
real,bonus means an attempt is made at first to withdraw from the personal account and, if the funds are short, they are withdrawn from the bonus account; and
bonus,real means an attempt is made at first to withdraw from the bonus account and, if the funds are short, they are withdrawn from the personal account.
The access password
(password field) to the email interface does not match the web interface access password.
It has to be set separately in the partner's interface "Access rights" section.
|
Template block
The template block follows the authorization block. It can contain the template of a person, entity and/or domain subject to the operation performed. The number of email templates is not limited. The block fields are divided into required and optional ones. The field may also be multi-line and single-line ones. A single-line field is the one which can only have one single-line value (for example, a person's nic_hdl). Multi-line fields are the ones which can have several single-line values (a person or entity's phone or email field) or one multi-line value (a person or entity's p-addr). Regular expressions to be met are provided for each field (the Cyrillic character codes are provided for the KOI8-R coding). For more information on the regular expressions, please, see
http://regexp.ru
[#PERSON TEMPLATE]#
Data template for a Registrant individual
| Field |
Description |
Regular expression |
Required or optional |
Multi-line feature |
Editing option |
| nic-hdl |
Person's nic_hdl in the registrar's DB |
^[0-9A-Z_]+-GPT$ |
Yes
(PK) |
No |
No |
| isprotected |
Whois privacy flag. If equals 1, the Whois service field will have the Private Person value |
^[01]$ |
No |
No |
|
| person |
Surname First name Patronymic (Roman alphabet) in the format "First name P Surname" |
^[\-a-zA-Z_ ]+$ |
Yes |
No |
No |
| person-r |
Surname First name Patronymic (Cyrillic alphabet) in the format "Surname First name Patronymic" |
^[ \-a-zA-Z\xC0-\xFF\xA3\xB3]+$ |
Yes |
No |
No |
| passport |
Passport series and number, issue details |
^[A-Za-z 0-9\xC0-\xFF\xA3\xB3.,;:"%$#@\/!*\-+]+$ |
Yes |
Yes |
No |
| birth-date |
Date of birth in the format DD.MM.YYYY |
^\d\.\d\.\d$ |
Yes |
No |
No |
| p-addr |
Domain Registrant's postal address |
^[ 0-9a-zA-Z\xC0-\xFF\xA3\xB3.,;:"%$#@\/!*\-+()]+$ |
Yes |
Yes |
|
| phone |
Domain Registrant's phone(s) |
^\+[0-9]+ [0-9]+ [0-9]+$ |
Yes |
Yes |
|
| fax-no |
Fax(es) |
^\+[0-9]+ [0-9]+ [0-9]+$ |
No |
Yes |
|
| e-mail |
Domain Registrant's email address |
^[\w|\.|\-]+@[\w|\.|\-]+\.\w{2,4}$ |
Yes |
Yes |
|
| passwd |
Registrar's web interface access password |
- |
No |
No |
|
| code |
INN (Tax Payer's Identification Number) |
^[\d+]{8,12}$ |
No |
No |
|
| isresident |
Is the Registrant a Russian Federation resident. The default setting is 1. |
^[01]$ |
No |
No |
|
[#ORGANIZATION TEMPLATE]#
Data template for a Registrant entity
| Field |
Description |
Regular expression |
Required or optional |
Multi-line feature |
Editing option |
| nic-hdl |
Nic_hdl in the registrar's DB |
^[0-9A-Z_]+-ORG-GPT$ |
yes
(PK) |
No |
No |
| org |
Entity's name in Latin letters |
^[\x20-\x7E]+$ |
Yes |
No |
No |
| org-r |
Entity's name in Russian |
^[ 0-9A-Z\xC0-\xFF\xA3\xB3.,;:"%$#@\/!*\-+()]+$ |
Yes |
No |
No |
| address-r |
Entity's legal address |
^[ 0-9a-zA-Z\xC0-\xFF\xA3\xB3.,;:"%$#@\/!*\-+()]+$ |
Yes |
Yes |
No |
| p-addr |
Entity's postal address |
^[ 0-9a-zA-Z\xC0-\xFF\xA3\xB3.,;:"%$#@\/!*\-+()]+$ |
Yes |
Yes |
|
| code |
INN (Tax Payer's Identification Number) |
^\d{5,12}$ |
Yes |
No |
No |
| phone |
Contact phone(s) |
^\+[0-9]+ [0-9]+ [0-9]+$ |
Yes |
Yes |
|
| fax-no |
Fax number(s) |
^\+[0-9]+ [0-9]+ [0-9]+$ |
No |
Yes |
|
| e-mail |
Contact e-mail(s) |
^[\w|\.|\-]+@[\w|\.|\-]+\.\w{2,4}$ |
Yes |
Yes |
|
| bank |
Name of bank |
^[ 0-9\xC0-\xFF\xA3\xB3.,;:"%$#@\/!*\-+()]+$ |
No |
Yes |
|
| ras_schet |
Entity's account |
^\d$ |
No |
No |
|
| kor_schet |
Correspondent account |
^\d$ |
No |
No |
|
| bik |
BIK |
^\d$ |
No |
No |
|
| okpo |
OKPO |
^[\d ,]+$ |
No |
No |
|
| okonh |
OKONH |
^[\d ,]+$ |
No |
Yes |
|
| kpp |
KPP |
^[\d ,]+$ |
No |
No |
|
| okved |
OKVED |
^[\d ,.]+$ |
No |
Yes |
|
| passwd |
Registrar's web interface access password |
^[ \x20-\x7E]{6,}$ |
No |
No |
|
| director |
Name of Director |
^[ 0-9a-zA-Z\xC0-\xFF\xA3\xB3.,;:"%$#@\/!*\-+]+$ |
No |
No |
|
| isresident |
Is the Registrant a Russian Federation resident. The default setting is 1. |
^[01]$ |
No |
No |
|
[#DOMAIN TEMPLATE]#
Domain data template
| Field |
Description |
Regular expression |
Required or optional |
Multi-line feature |
Editing option |
| domain |
Full domain name in RU TLD (in both upper and lower cases) |
^[0-9a-zA-Z][0-9a-zA-Z-]{0,61}[0-9a-zA-Z]\.[rRsS][uU]$ |
Yes
(PK) |
No |
No |
| admin-o |
Registrant's nic-hdl in the Registrar's database |
^[0-9a-zA-Z_]+(-ORG)?-GPT$ |
Yes |
No |
No |
| nserver |
Domain delegation DNS servers |
^\s*$|^[0-9a-zA-Z.-]+( +[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3})?$ |
No |
Yes |
Yes |
| descr |
Domain description |
^[\x20-\x26\x28-\x7E]+$ |
No |
Yes |
Yes |
The template block is required to be ended with the line
[#TEMPLATES END]#