WMTransfer Wiki

WebMoney Keeper Mini password reminder

Wed, 18 Nov 2009 13:52:35 Z

Please follow the steps below should you forget your WebMoney Keeper Mini access password:

Go to https://mini.wmtransfer.com/ and click the ‘Forgot your password’ link to continue to a password reminder page.

Type your e – mail, WMID or phone number that you provided during the registration and select the method to receive password reminder instructions (via e – mail, phone or WM Keeper), type the code you see in the picture and confirm the operation by clicking «OK».

A link to the password reminder page will be sent to you via e – mail, phone or WM Keeper. Follow the link and choose a new password to your WebMoney Keeper Mini.

This article in other languages: Русский

WM Keeper Mini

Wed, 18 Nov 2009 13:36:00 Z

WM Keeper Mini

What is it?

It is another WebMoney Keeper software, not so powerful as Classic or Light, but very user-friendly and easy to use in most cases.
It is deployed as a light site supporting main WebMoney Transfer account management functions.

Who is it designed for?

It is for those:

who already have WebMoney account and who want to be able to manage it without using WebMoney Keeper Classic or Light;
who want to enhance their mobility (only login and password are required to enter WebMoney Keeper Mini);
who want to simplify WebMoney use and improve its use-friendliness.

What does it allow to do?

to enter the account using the login and the password;
to work with mobile devices enhancing convenience;
to see the purse balance;
to add the purse funds with WM card (Paymer check);
to transfer WM;
to issue and pay invoices;
to see the last operations;
to enhance convenience when paying for services (mobile communications, Internet, etc.);
to enhance convenience when buying digital products in stores that use digiseller.ru;
to transfer WM to WebMoney ATM card.

How secure is it?

WebMoney Keeper Tiny will help you securely manage only the purses you enable in this software.

Note: You can set a (daily, weekly, or monthly) limit for the trusted purse, i.e., the maximum sum you can transfer from it during the specified time interval.

Service website: https://mini.webmoney.ru/ https://mini.wmtransfer.com

Category: System services, WM Keeper Mini

This article in other languages: Русский

Formal passport

Tue, 10 Nov 2009 16:55:21 Z

A formal passport is issued free of charge to a WebMoney Transfer member at the Verification Center Website after such user enters his / her personal (passport) data. Data specified by the user are not verified. The formal passport holder is provided access to Banking WebMoney Transfer service allowing:

to add funds by bank wire;
using a Ukash Voucher

This article in other languages: Русский

WM_Keeper_Classic_history

Mon, 19 Oct 2009 14:10:00 Z

WebMoney Keeper Classic History

WebMoney Keeper Classic 3.8.0.0, released September 29, 2009 29/09/2009

Some of the new features in WebMoney Keeper Classic 3.8.0.0 include:

Advanced layout of dialogue boxes

There are special informative components located at the top of a dialogue box, including:

Dialogue box icon
Dialogue box title
Dialogue box short description
There can also be an icon linking to an article in wiki or an extra menu button

New REGISTRATION wizard

Signing up process has become much simpler
During the registration users get signed up for www.enum.ru and connected to the E-num Storage

New SIGN IN dialogue box

All sign-in options are available from one window

Now you needn’t switch from window to window to select a sign-in option you want to use
A new sign-in option for E-num – response value is sent via SMS
If you make a mistake when signing in (type a wrong password, etc), the special wizard will guide you through the process

WebMoney Keeper main window

Total balance is now displayed at the top of the window
Full and reduced (only the contact list is displayed) view mode
New events are indicated in the status bar

FIND A CONTACT dialogue box

Lets to search contacts by their name in the contacts list

SEND WEBMONEY dialogue box

Click on the Total Amount and Commission line to copy this information to the clipboard

ENTERING THE SITE SECURE AREA window

The scroll wheel can be used to make this window transparent – just scroll the wheel up or down to change the transparency
Transparency settings will be remembered
You can change the size of this window (size settings will be remembered)

Chat window

Much more messages can be uploaded to the chat window
If an authorized contact sends an authorization request this request will be processed correctly
fixed: now you can select the text in the tab even when a new message is blinking in another tab
fixed: coding errors

Integration with Files.WebMoney

Drag&Drop is now supported
If you drag and drop a file into a chat or contact, the Send Files dialogue box will open to send files to a particular contact

If you drag and drop a file into the main menu, it will open the Send Files dialogue box to send files to your personal storage at Files.WebMoney

E-NUM

Software to sign in by fingerprints was updated

Advancements in build 3066, released 9.10.09

WMID can be again copied to the clipboard by a single click

Click here or press Alt+C to copy your WMID to the clipboard

Important notice!

If your key file is saved in ruToken, please do not install this version, because it doesn’t support this login option
You can receive a response value no more than thrice a day. Then you will receive an error message.

WM Keeper Classic

Mon, 19 Oct 2009 13:17:44 Z

WM Keeper Classic is one of the possible methods for managing WM-purses and working with the WebMoney Transfer system. This application is implemented as a client software program and is installed on user’s computer.

System information
WM Keeper Classic supports Windows 2000, Windows XP, Windows 2003 and Windows Vista operating systems. Internet Explorer version 6.0 and higher must be installed in the system. When working with Russian version of the software, the user must use either Russian edition of the corresponding operating system or localized English version. In other cases, it is recommended to use English version of WM Keeper Classic.
WM Keeper Classic installer also includes a plug-in for the web browser – WebMoney Advisor.

Download: Russian version | English version

Launch WM Keeper Classic (it must be already installed on your computer).

It is recommended to read the Checking security settings article.
More information about using the software

Category: WM Keeper Classic

This article in other languages: Русский

WebMoney Keeper Mobile financial restrictions

Fri, 02 Oct 2009 14:21:59 Z

WM Keeper Mobile users with passports lower than initial and only with WM-purses received after registering with WM Keeper Mobile have the following financial restrictions imposed:

Maximum amount on all purses cannot exceed 5000 WMR (or in any other currency at the rate of Central Bank). If, as a result of funds transfer to a purse, the maximum amount is exceeded on purses, then it will be impossible to complete such a transaction.

The maximum amount of one transaction from one purse is 1000 WMR (or in any other currency at the rate of Central Bank of Russian Federation at the day of payment). There are no financial restrictions for transactions in the telepay.wmtransfer.com service (including services provided by WM Keeper Mobile application).

The table below lists financial restrictions for transactions for certain time periods:

WM currency	monthly limit	weekly	daily	per day
WMR	30000	15000	5000	5000
WMZ	1000	500	200	200
WME	750	375	140	140
WMU	8000	4000	1500	1500
WMB	600000	300000	100000	100000
WMY	300000	150000	50000	50000
WMG	300	150	50	50

WM Keeper Classic, Keeper Light, Keeper Mini purses or purses added to operation modes via Keeper Mobile do not have the financial restrictions specified above.

To avoid financial restrictions you must obtain initial or higher passport or change operation mode to WM Keeper Classic.

Category: WM Keeper Mobile

This article in other languages: Русский

Renewing personal certificate

Fri, 02 Oct 2009 10:58:43 Z

WM Keeper Light personal certificate must be renewed once in a year.

WM Keeper Light will notify you about the necessity to renew your certificate by a message on the “Purses” page approximately a month before the current certificate expires.

If you failed to renew your certificate before the current certificate has expired, then you must contact our Technical Support.

The procedure for renewing your certificate is the same as for obtaining a certificate when registering with WM Keeper Light. Let’s follow this procedure step-by-step on the example of Firefox browser.

Login to your WM Keeper Light and go to the “Purses” page. In the notification about certificate renewal find the link www.wmcert.com and click it.

In the opened window enter your e-mail address. This can be the e-mail you specified when registering with WM Keeper Light or any other e-mail. Your new certificate will be the certificate for the specified e-mail address and you will be able to sign your messages with it.
Then press the “Register” button.

If the opened page is the same as the one showed below, it means your certificate has been generated and you must install it to the browser’s storage. To do so, click the “Install certificate” link.

If the certificate is installed, the system will pop up the following message:

You can also save the certificate to local disk by right-clicking the specified link and selecting the “Save as…” menu option.
Then close the message and click the “Launch” button and confirm that you want to install the certificate.

Remove the old certificate from the storage. To do so, go to browser settings > menu “Tools→ Options”, section “Advanced”, switch to the “Encryption” tab, press the “View Certificates” button, select the old certificate and click the “Remove” button.

Close the Options window and click the “Launch” button.

Restart your browser and login to WM Keeper Light – light.wmtransfer.com

If the certificate generated by the server has not been installed to the browser’s storage, you can complete the installation manually – the certificate registered and signed on the server (the file with .cer extension) can be sent to your e-mail address. For some browsers (Internet Explorer, Opera) it is enough just to import the certificate received by e-mail to the storage. In the Firefox browser the installation procedure is more complex.

Right after you renew the certificate create backup copy on portable information storage. To do so, in the Firefox browser open certificate manager – menu “Tools-Options”, “Advanced” section, switch to the “Encryption” tab, click the “View Certificates” button, select the certificate on the “Your certificates” tab and click the “Save copy…” and select where you want to save it and specify the password.

What to do if the certificate has expired?

If you failed to renew your certificate due to whatever reasons before it expired and if you need access to your WMID, then you need to send from your e-mail (the one you specified during the registration) the number of your WMID and certificate file with private key in format <file name>.PFX (*.P12) with the password to the file to wmlight@wmtransfer.com.

Within five working days we will send you the link for restoring the certificate and password.

If you send the message from another e-mail (not the one you specified during the registration), then you must specify the reasons for changing your e-mail and specify the password, entered when registering in the system.

If you have already renewed the certificate, but you have lost the certificate, then you must follow the procedure for restoring the certificate.

Interface X17

Tue, 22 Sep 2009 17:23:50 Z

Interface X17. Operations with arbitration contracts.

This interface is available only to registered clients. To get access to this interface send via internal mail a message to WMID 941977853154 (Technical support) containing short information about your project, URL of your web-site, IP-address from which requests will be sent, purpose and method the interface will be used. The Keeper signing requests must have Personal (or higher) passport.

This interface allows automatically creating and publishing on the web-site of the arbitration service special text documents – contracts, and also checking whether these contracts were accepted by authorized users.

Creating contracts

Requests using WM Keeper Classic authorization should be sent to – Coming soon…
Method – POST
Request format:

<contract.request>
	<sign_wmid></sign_wmid>
	<name></name>
	<ctype></ctype>
	<text></text>
	<sign></sign>
		<accesslist>
        		<wmid></wmid>
	        	<wmid></wmid>
        	</accesslist>
</contract.request>

Request parameters:

name	purpose	comments
sign_wmid	Signer’s WMID	He/she is the contract author
name	Contract name	short (not more than 255 characters) contract name
ctype	Contract type	ctype=1 – contract type with open access, ctype=2 – contract with restricted access
text	Text of contract	Document text itself
sign	Request signature	Takes the following parameters: wmid & Len(name) & ctype
accesslist	List of users WMIDs authorized to accept the given contract	for contracts with restricted access contract.request\ctype=2 it is MANDATORY to specify the list of authorized users. It will be impossible to change this list after the contract is published. For contracts with open access there is no necessity to specify contract.request\accesslist, you can find more information about contract types here
accesslist\wmid	WMID	WMID of the user who is authorized to accept this contract

Response format:

<contract.response>
	<retval></retval>
	<retdesc></retdesc>
	<contractid></contractid>
</contract.response>

Response parameters:

name	purpose	comments
retval	Execution code	0 – request successful, other values indicate that error(s) occurred during request
retdesc	Description of execution code
contractid	Number of the created contract	If retval=0 this tag will contain the number of the created contract

Information about contract acceptances

Requests using WM Keeper Classic authorization should be sent to – Coming soon…
Method – POST
Request format:

<contract.request>
	<wmid></wmid>
	<contractid></contractid>
	<mode>acceptdate</mode>
	<sign></sign>
</contract.request>

Request parameters:

name	purpose	comments
wmid	Signer’s WMID	He/she is the contract author
contractid	Contract number
mode	Request type	To get information about acceptors you must always specify mode=acceptdate
sign	Request signature	Takes the following parameters: contractid + mode

Response format:

<contract.response>
	<retval></retval>
	<retdesc></retdesc>
		<contractinfo>
			<row contractid="" wmid="" acceptdate=""/>
			<row contractid="" wmid="" acceptdate=""/>
		</contractinfo>
</contract.response>

Response parameters:

name	purpose	comments
retval	Execution code	0 – request successful, other values mean there were errors during request
retdesc	Description of execution code
contractinfo	Information about acceptors
contractinfo\row	Information about one acceptor
contractinfo\row\@contractid	Contract number
contractinfo\row\@wmid	Acceptor’s WMID
contractinfo\row\@acceptdate	Date and time of acceptance	for example 2005-11-29T12:00:39.077, if there is no acceptance date, then this user hasn’t accepted this contract

Interface X18

Tue, 22 Sep 2009 17:17:45 Z

Interface X18. Getting transaction details via merchant.wmtransfer.com.

This interface is available only to registered clients who use merchant.wmtransfer.com service.

This interface allows the user to automatically get information about payment status and whether the payment was made or not by using payment number (lmi_payment_no in terms of merchant.wmtransfer.com). If the payment was made then the user will be able to get payment details. Interface X18 does not only have strict WMSigner but also simple (MD5 or passing secret_key via https) authentication which allows integrating this interface easily and securely and using it for searching payments.

Requests should be sent to – https://merchant.webmoney.ru/conf/xml/XMLTransGet.asp
Method – POST
Request format:

<merchant.request>
	<wmid></wmid>
	<lmi_payee_purse></lmi_payee_purse>
	<lmi_payment_no></lmi_payment_no>
	<sign></sign>
	<md5></md5>
	<secret_key></secret_key>
</merchant.request>

Request parameters:

name	purpose	comments
wmid	WM-identifier of the recipient or signature	WMID of the user who owns the purse, to which lmi_payment_no payment was received via merchant.wmtransfer.com or WMID of the user who signed the request using WMSigner authentication method. Keep in mind that if the owner of that WMID does not own the purse, which received the payment, must be trusted to view transaction details for this purse.
lmi_payee_purse	WM purse of payment recipient	Purse number to which lmi_payment_no payment was received and which status needs to be defined.
lmi_payment_no	payment number	The number of the payment, which was generated by the service, web-site, other service, internet shop, etc and was transferred to the merchant.wmtransfer.com service as a payment in a hidden lmi_payment_no field. Pay attention that if the lmi_payee_purse purse is not configured in the merchant.wmtransfer.com service to receive only unique lmi_payment_no then there might be situations when the merchant through his/her fault might generate for different purchases or even purchasers one and the same lmi_payment_no. In such cases the service will register two payments with one and the same number, and this case the interface will retrieve ONLY one transaction – the last one.
sign	Request signature	The request is signed with WM-identifier keys using the WMSigner method and takes the following parameters: wmid & lmi_payee_purse & lmi_payment_no. Keep in mind that if the owner of WM-identifier does not own the lmi_payee_purse, then this WMID must be trusted at security.wmtransfer.com to view transaction details for the lmi_payee_purse. In cases when this authentication method is used, md5 and secret_key parameters must be left empty or omitted.
md5	Request signature	The request is signed using the MD5 method and takes the following parameters: wmid & lmi_payee_purse & lmi_payment_no & secret_key. If the user uses this method for authenticating the request, sign and secret_key parameters must be left empty or omitted. Bear in mind that when generating the string, to which md5 algorithm will be applied, the value of secret key from the purse settings in the merchant.wmtransfer.com service is used as secret_key. The request itself must pass ONLY the result of the algorithm work in MD5 parameter and secret_key parameter must be left empty!!!
secret_key	Secret key	This parameter passes the value of the secret key specified in the lmi_payee_purse settings in the merchant.wmtransfer.com service. Keep in mind that, when using this method, https connection authentication check (validity and ownership of the root certificate of https://merchant.wmtransfer.com, etc) will be your responsibility to avoid DNS substitution, etc. If you use this method for authenticating the request, sign and md5 parameters must be left empty or omitted.

Response format:

<?xml version="1.0"?>
<merchant.response>
	<operation wmtransid="" wminvoiceid="">
		<operdate></operdate>
		<purpose></purpose>
		<pursefrom></pursefrom>
		<capitallerflag></capitallerflag>
		<enumflag></enumflag>
		<IPAddress></IPAddress>
		<telepat_phone></telepat_phone>
		<paymer_number></paymer_number>
		<paymer_email></paymer_email>
		<cashier_number></cashier_number>
		<cashier_date></cashier_date>
		<cashier_amount></cashier_amount>
	</operation> 
	<retval>0</retval> 
	<retdesc></retdesc> 
</merchant.response>

Response parameters:

name	purpose	description
wmtransid	WM transaction ID	Unique transaction number in WebMoney Transfer.
wminvoiceid	WM invoice ID	Unique invoice number in WebMoney Transfer.
amount	Amount	The amount of WebMoney units transferred in this transaction to the merchant.
operdate	Operation date	Server date of the transaction in WebMoney Transfer.
purpose	Comment	The payment purpose as submitted to the merchant.wmtransfer.com service in the lmi_payment_desc field.
pursefrom	Purchaser’s purse	WM purse of the payer. Pay attention that when paying via terminals or ATMs, or Paymer check or WM card the purse of the corresponding gateway or Paymer service will be passed as Payer’s purse.
capitallerflag	Payment parameter	If the flag is set to 1 – it means that Payer used the purse of the Capitaller service and not his/her own purse for the payment; if set to 0 – Payer used his/her own purse for the payment.
enumflag	Payment parameter	If this flag is set to 1 – it means that the payment was made by the user who auhorized via E-num.ru service.
IPAddress	Payment parameter	The IP-address of the user who made the payment.
telepat_phone	Payment parameter	The phone number of the payer, if the payment was made via WM Keeper Mobile service.
paymer_number	Payment parameter	The number of the check or payer’s WM-card if the payment was made by means of Paymer check or WM-card.
paymer_email	Payment parameter	Payer’s e-mail address, which he/she specified when paying by means of Paymer check or WM-card.
cashier_number	Payment parameter	The number of the payment, if payer paid via a terminal, ATM or post office.
cashier_date	Payment parameter	The date of the payment, if it was made via a terminal, ATM or post office.
cashier_amount	Payment parameter	The amount of the payment, if it was made via a terminal, ATM or post office.
retval	Execution code	0 – request successful, other values mean there were errors during request.
retdesc	Description of execution code

Adding WM Keeper Classic to WM Keeper Mini

Tue, 22 Sep 2009 17:14:27 Z

If you want to manage your WMID registered in WM Keeper Mini via WM Keeper Classic, you can do this by changing the main operation mode at the Security WebMoney. Keep in mind that after you switch to WM Keeper Classic it will be the main application for managing your purses. That is why when you enter the protected zone of WebMoney Transfer web-sites and make transactions via the Merchant WebMoney Transfer service of automatic payments you must select exactly WM Keeper Classic, and correspondingly you must have all data required for accessing this application (for more details see Launching WM Keeper Classic).

You can change the method for managing your purses under the following conditions:

your WMID has formal or higher passport (for more details see Passports description)
the contact phone number specified in the passport is verified by the Verification center (the link for verifying the phone number)

Go to Operation modes page, select WM Keeper Mini login and specify your login and password (or use E-num authorization for this). Click “Add” in the CLASSIC box.

Specify new password and confirm it in the corresponding fields. You will use this password for launching WM Keeper Classic.

Download Key file for your WMID using the suggested link. Access code for this key file will be the same as the login password you have specified in the previous step. Pay attention that, as opposed to the usual system for storing keys, access code coincides with the WM Keeper Classic login password.

Make sure you click the “Continue” button for the system to register your new keys!

After you successfully finish changing the operation mode, the instructions for launching and using WM Keeper Classic will be displayed.
For security reasons, after you successfully login to WM Keeper Classic, go to Settings and change login password, change keys and save new key file.

You will still be able to manage your purses via WM Keeper Mini. WebMoney Keeper Mini financial restrictions for your purses will be removed.

See also:
Operation modes

Category: WM Keeper Mini, WM Keeper Classic, Security

This article in other languages: Русский

Adding WM Keeper Classic to WM Keeper Mobile

Tue, 22 Sep 2009 17:12:30 Z

If you have started using WebMoney via Telepat and manage your purses via WM Keeper Mobile, then you cannot use all the possibilities that WebMoney Transfer provides and which are available in WM Keeper Classic. Using WM Keeper Classic you can:

have several purses of one type of Title units;
store more than 5000 WMR on your purses without any WebMoney Keeper Mobile financial restrictions;
significantly increase security level of your transactions;
have secure communication with other WebMoney Transfer users;
use different WebMoney Transfer system services to the full extent (including adding/withdrawing funds via bank transactions, on-line currency exchange and many others).

To add WM Keeper Classic operation mode to your purses and at the same time keep the possibility to manage them via WM Keeper Mobile go to Security service web-site and perform the following actions:

Start authorization process by clicking the Login link.

In the appeared window select the Mobile tab, enter the phone number and PIN-code, you use in WM Keeper Mobile and click the “Login” button.

Go to Operation modes section. On the opened page you will see current operation mode for your WMID purses. The activated possibilities have a “green light”. To manage your purses via WM Keeper Classic you need to click the “Add” button in the corresponding section.

If your passport level is lower than formal, then go to the procedure for getting it. Also, do not forget to verify your contact phone number.

After you get formal passport, go to “Operation modes” section again and repeat step 3.

Then set the password for the first login to WM Keeper Classic and accessing the key file. Keep in mind that this password must be temporary because after you finish installing and initializing WM Keeper Classic on your computer you must change this password and also generate a new key file.

After you specify the password click the “Change operation mode” button.

Click the “Download keys…” link and save key file to your computer. This file looks like <Your WMID>_<access code>.kmw. Then click the “Continue” button.

Install and initialize WM Keeper Classic on your computer.

To do so, follow the steps below:

Download WM Keeper Classic installation file.
Install and launch it, specify your WMID and access code. Select the Initialize mode.
Then specify that you have key file and are ready to initialize the application.
Browse the location of the key file and enter the password you got in step 2 as the access code. In this case the access code for key file is the same as the login password for WM Keeper Classic. After initialization, do not forget to change the password and code (make them different).
Allow the application create purse file automatically.
After you connect WM Keeper Classic to the server (‘Online’ mode) we recommend changing the keys (key file and access code for it) and also login password for WM Keeper Classic since you received them via the Internet.

Without a delay follow the recommendations for WebMoney Keeper Classic secure operation.

Personal authentication hardware

Tue, 22 Sep 2009 17:07:45 Z

To increase security for working with your purses and WebMoney Transfer services we recommend using the following personal authentication hardware:

Fingerprint reader;
eToken PRO USB authentication token;
Rutoken USB authentication token.

Fingerprint reader is a high-frequency scanner that generates unique sequence of numbers on the basis of unique image of dermal ridges of human finger skin and uses that sequence to identify the user. The fingerprint reader is used in WebMoney Transfer system in E-num authorization. Some modern notebooks, keyboards and mice are equipped with fingerprint readers. They are produced as separate USB devices. E-num supports a great number of fingerprint readers.

eToken PRO and Rutoken USB authentication tokens represent secure devices designed for authenticating the user in the network or local computer, protecting e-mail communication, providing secure remote access to information resources and also for providing secure storage for personal data such as electronic digital signature, WM Keeper Light personal certificate, WM Keeper Classic key files. You can read the description of USB authentication tokens on manufacturers’ web-sites eToken PRO and Rutoken.

The following instructions will help you install and configure the devices mentioned above for working in WebMoney Transfer.

Using fingerprint reader for Enum-authorization?
How to store WM Keeper Classic access code on eToken
How to store WM Keeper Classic access code on ruToken
Using eToken for storing WM Keeper Light certificates?
Using Rutoken for storing WM Keeper Light certificates?

Personal certificate

Fri, 18 Sep 2009 15:46:04 Z

Personal (private, client) digital certificate in WMT system is designed for protecting, identifying and transmitting data during internet connections in WM Keeper Light.

Authentication is ensured by applying a privacy key, generated on user’s computer during the registration process. It is stored only with the owner of WM Keeper Light personal digital certificate and is never passed via the network.

Personal digital certificate authenticates the owner of WM-identifier on sites of WMT services and also on other sites where WMT authentication system is installed.

Installation of personal certificate is part of the WM Keeper Light registration process and can be completed in any browser.

Also, it is possible to obtain client certificate after the registration process via E-Num.

Personal certificate is valid for one year, after this period expires the user has to renew (prolong) it. To do so, on www.wmcert.com web-site the user has to perform the same actions for obtaining and installing the certificate, specified above in the instructions for registering WM Keeper Light in different browsers.

The process of installing personal certificate consists of three steps:

Generating a privacy key and a request for certificate (public key) on user’s computer;
Registering and signing the certificate on WMT server;
Obtaining the certificate and installing it in the browser.

In case when the certificate generated by the server was not saved to browser’s storage due to any reasons, then the user can complete the registration process independently, – the certificate registered and signed on the server (file with .cer extension) can be sent to user’s e-mail. For some browsers (Internet Explorer, Opera) it is enough just to import the certificate received by mail to browser’s storage. For Firefox installation procedure is more complex.

Immediately after the registration (renewal) process the certificate and privacy key are stored in so-called exporting mode, which allows creating their replicas. It is unsafe to store the privacy key in the storage for a long time, so after installing personal certificate the user is required to perform the following:

Create backup copy of the certificate (see Keeper Light key export) on reliable removable data storage;
Delete the certificate from the storage;
Install the certificate to the storage from the backup copy by disabling the option allowing export of privacy key (see Keeper Light key import). In IE it is better to enable advanced certificate protection mode.
To increase the security of WM Keeper Light operation it is recommended to install the certificate on secure device like eToken or RuToken.

Category: WM Keeper Light

This article in other languages: Русский

Geo service interfaces

Fri, 11 Sep 2009 09:16:52 Z

GEOWM.INPUTXML Service

This interface allows automatic uploading to WebMoney GeoService server the list of user WM-objects of certain type.

XML file format for GEOWM.INPUTXML service:

The example below describes one user object (exchange agency):

<?xml version="1.0" encoding="windows-1251"?>
<wmobjects>
 <row 
  sid="30482" 
  citid="12918" 
  name="Association &quot;WMEXPRESS&quot; in Moscow" 
  wmid="477230148314" 
  web="http://wmmoscow.com/" 
  email="" 
  type="1" 
  addr="17 Bolshaya Ordynka" 
  worktime="Monday - Friday, from 10:30 till 19:00" 
  phone="(901)530xxx1, (901)530xxx2" 
  mid="16" 
  mid2="0" 
  dopinfo="exchanging WM*, EGOLD, Yandex.Money. Adding and withdrawing WebMoney in Moscow. Cashless adding and withdrawing WebMoney and E-Gold"
  help="" 
  lng=""
  lat="" 
  direction="3" 
  lang="ru-RU"
  />
</wmobjects>

Requirements to GEOWM.INPUTXML file:

The file must begin with <wmobjects> opening tag and end with the </wmobjects> tag.
One <row /> tag is a string containing data about one object.
The file must be saved in windows-1251 encoding.
All objects must be geographically binded to WebMoney GeoService geodata database, i.e. each object must have a unique number (ID) of the place (city) where it is located.
The following masking must be applied to all unallowed symbols:
Double quotes <"> must be replaced with "
Greater than sign “>” must be replaced with >
Less than sign “<” must be replaced with <

Attribute name XML	Mandatory	Parameter description
wmobjects/row/@sid	Mandatory	Unique number of the location or unique identifier of ATM (kiosk_id).
wmobjects/row/@citid	Mandatory	City number (ID), where the object is located. You can find the list of city IDs here
wmobjects/row/@name	Mandatory	Object name
wmobjects/row/@type	Mandatory	Object type (6 – WM cards selling points, 7 – points for adding funds by depositing cash, other must be conformed with the service administrator (geosupport@webmoney.ru)
wmobjects/row/@lang	Mandatory	Language (CultureInfo)
wmobjects/row/@direction	Mandatory	Type of service (1-adding, 2-withdrawing, 3-adding/withdrawing)
wmobjects/row/@country	Optional	Country
wmobjects/row/@region	Optional	Region
wmobjects/row/@city	Optional	City
wmobjects/row/@wmid	Optional	WM-identifier
wmobjects/row/@web	Optional	Web-site URL
wmobjects/row/@email	Optional	E-mail
wmobjects/row/@mid	Mandatory for objects located in Moscow and St. Petersbourgh	Number (ID) of the closest metro station (1). Only for Moscow and St. Petersbourgh You can find the list of metro stations IDs here
wmobjects/row/@mid2	Optional	Number (ID) of the closest metro station (2). Only for Moscow and St. Petersbourgh You can find the list of metro stations IDs here
wmobjects/row/@dopinfo	Optional	Additional information
wmobjects/row/@phone	Optional	Contact phone number
wmobjects/row/@addr	Optional	Address
wmobjects/row/@worktime	Optional	Working hours
wmobjects/row/@tarif	Optional	Rates
wmobjects/row/@proezd	Optional	Location map (URL)
wmobjects/row/@srok	Optional	Adding term
wmobjects/row/@help	Optional	Instructions (URL)
wmobjects/row/@lng	Optional	Longitude
wmobjects/row/@lat	Optional	Latitude

Each XML batch must not exceed 200 (maximum) strings in one data set. To update the data, having greater number of strings in one set, the web-site update service calls the registered URL several times, with different FirstId parameters, specifying maximum SID of the previous data set. For correct operation of the update system, each data set batch (200 strings) must have LastID specified. LastId is the ID of the last string in one data set.

Its format is described below:


    http://yoursite.com/yourservice/dataxml?fisrtid=0 (lastid=200)
    http://yoursite.com/yourservice/dataxml?fisrtid=200 (lastid=400)
    http://yoursite.com/yourservice/dataxml?fisrtid=400 (lastid=600)
    .
    .
    .
    http://yoursite.com/yourservice/dataxml?fisrtid=1000 (lastid=1200)
    http://yoursite.com/yourservice/dataxml?fisrtid=1200 (lastid=1200 not greater than 1200 or -1, data is out of range)

Attribute name XML	Mandatory	Parameter description
wmobjects/lastid/@value	Mandatory, if the total volume of data exceeds 200 strings	ID of the last record in the data set

A sample of GEOWM.INPUTXML for banks and payment systems, accepting rubles in cash for depositing to R-purses in WebMoney Transfer:

<?xml version="1.0" encoding="windows-1251"?>
<wmobjects>

	<row 
	sid="1000" 
	citid="12918" 
	name="X-System payment terminal" 
	web="http://www.x-system.ru/" 
	email="support@x-system.ru"
	mid="117" 
	addr="11-28 Kvesisskaya str." 
	srok="immediately" 
	tarif="2.5% from transaction sum" 
	worktime="24 hours" 
	help="http://www.webmoney.ru/wmintrans6.shtml" 
	dopinfo="Adding funds to R-purse by depositing cash" 
	direction="1" 
	type="7"/>
	
	<row 
	sid="1001" 
	citid="28610" 
	name="X-System payment terminal"  
	web="http://www.x-system.ru/"  
	email="support@x-system.ru" 
	mid="1001" 
	addr="2-23 Kolontai str" 
	srok="immediately" 
	tarif="2.5% from transaction sum" 
	worktime="24 hours" 
	help="http://www.webmoney.ru/wmintrans6.shtml" 
	dopinfo="Adding funds to R-purse by depositing cash"  
	direction="1" 
	type="7"/>
	
        .
        .
        .

	<row 
	sid="1200"
	citid="12918" 
	name="X-System payment terminal" 
	web="http://www.x-system.ru/" 
	email="support@x-system.ru" 
	mid="13" 
	addr="22, Rimsky-Korsakov str" 
	srok="from 9-00 till 22-00" 
	tarif="2.5% from transaction sum" 
	worktime="24 hours" 
	help="http://www.webmoney.ru/wmintrans6.shtml" 
	dopinfo="Adding funds to R-purse by depositing cash"  
	direction="1" 
	type="7"/>

        <lastid value="-1" />
        <!-- end of data -->
			
</wmobjects>

GEOWM.OUTPUTXML web-service

This interface allows retrieving from geodata database:

List of countries
List of regions (for a specific country)
City list (for a specific region)
List of metro stations (for Moscow and St. Petersbourgh)

Web-service URL and available methods:

https://geo.webmoney.ru/find/GeoSearchService.asmx

Main methods

GetCountryList
Returns the list of countries
GetRegionList
Returns the list of regions. Counry ID is set.
GetCityList
Returns the list of cities and towns. Region ID is set. If hasCoords=1 geographical coordinates are returned, if hasCoords=0 – then not.
GetNearestMetro
Returns the list of metro stations, sorted by remoteness from the specified coordinates. Geo-coordinates are set.
GetNearestMetro2
Returns the list of metro stations, sorted by remoteness from the address. City ID and address are specified.
GetNearestMetro3
Returns the list of metro stations, sorted by remoteness from the address. City ID and address are specified. The city is set as a string, not as ID.

Additional methods

AddressGeoCoding
Geocodes the address, by processing it with the ParseAddress method in advance. Returns geographical coordinates. It is similar to GeoCoding, but it is advised to user AddressGeoCoding, if the address is not structured.
AddressGeoCoding2
Geocodes the address, by processing it with the ParseAddress method in advance. Returns geographical coordinates. It is similar to GeoCoding, but it is advised to user AddressGeoCoding, if the address is not structured.
AddressGeoCodingY
Geocodes the address, by processing it with Yandex geocoder. Returns geographical coordinates. Address contains structured address.
AddressGeoCodingY2
Geocodes the address, by processing it with Yandex geocoder. Returns geographical coordinates. Address contains structured address. City is set as a string, and not as ID
AddressParsingY
Structures the address with Yandex geocoder. Returns structured address.
AddressParsingY2
Structures the address with Yandex geocoder. Returns structured address. The city is specified as a string, not as ID.

In order to user the service, the user must go through the registration procedure. After the registration process you will GUID (unique user’s identifier) and password. Each method of this web-service accepts two additional parameters – GUID and password.

You can find more detailed information on this page offering help for a user of this interface.

GEOWM-Locator search interface

This interface allows making geographical binding of any resources (offices and subsidiaries, objects of storage or agent network, etc), i.e. everything that can be later displayed on a map. The main task of this interface is provide access to unique for WebMoney Transfer system geodata database, and by using which it is possible to display “geographically binded” objects by means of WebMoney GeoService without earlier processing.

You can find more detailed information on page with help services of this service.

Category: XML-Interfaces

This article in other languages: Русский

XML-interfaces

Fri, 11 Sep 2009 07:12:24 Z

XML-Interfaces

Interface X1 — Sending Invoice from merchant to customer
Interface X2 — Transferring funds from one purse to another
Interface X3 — Receiving the History of Transactions; checking Transaction status
Interface X4 — Receiving the history of issued invoices. Verifying whether invoices were paid
Interface X5 — Completing a code-protected transaction. Entering a protection code
Interface X6 — Sending message to random WM-identifier via internal mail
Interface X7 — Verifying client’s handwritten signature – owner of WM Keeper Classic
Interface X8 — Retrieving information about purse ownership. Searching for system user by his/her identifier or purse
Interface X9 — Retrieving information about purse balance
Interface X10 — Retrieving list of invoices for payment
Interface X11 — Retrieving information from client’s passport by WM-identifier
Interface X12 — Importing statement of a purse into a 1C document
Interface X13 — Recalling incomplete protected transaction
Interface X14 — Fee-free refund
Interface X15 — Viewing and changing settings of “by trust” management
Interface X16 — Creating a purse
Interface X17 — Operations with arbitration contracts
Interface X18 — Getting transaction details via merchant.webmoney

Category: XML-Interfaces

This article in other languages: Русский