Reception of payment on a site
Actually, simple opening of a purse in EPS already allows to accept payments on the site. In fact it is possible to do(make) it manually, whether not so? Sit to itself all day and night and process orders in the Ñ-shop. Not so conveniently, unfortunately. Much more it is more pleasant to realize, that process of reception of payments on your site occurs(happens) automatically, without your participation. You sleep - money drip.
And all WebMoney gives a question of automation of all great value. Here in general it is much made for simplification of a life to web designers and developers. So, by means of the corresponding(meeting) elements ActiveX inserted on page, we can suggest to start to the user Keeper (and in case of its(his) consent to make automatically) and even to induce it it(him) to begin procedure of installation Keeper'а (if the program is not established(installed) yet).
As to reception of payments on a site then WebMoney gives 2 ways: use of the module autentifikatsii for an automatic extract of the account(invoice) and use of service Merchant).
The first variant - for inveterate developers. It(he) is considered already a little become outdated(out-of-date) owing to some complexity, however is used still enough often. Its(his) essence consists in an automatic extract of the account(invoice) to the buyer, and then - in check of a condition of its(his) payment. For this purpose it is necessary skachat and proinstalit on a server the special module autentifikatsii which problems(tasks) include formation ETSP of each operation. It allows to make operations in system only on behalf of the WM-identifier, with use of which confidential keys the module makes the signature. Installation under Unix can look(appear) so:
>chmod a+x ./compl.sh ./compl.sh
In the further for an automatic extract of the account(invoice), check of a condition of its(his) payment, and also machine translation of means from a purse on a purse it is necessary to use offered WebMoney simple enough and clear interfaces.
The given way, however, has two lacks. The first - high probability of failure or "error" in work of system, dependence on a condition of a connection to server WebMoney; the second - necessity to spread in the open kind on a server a file of keys kwm (it(he) is necessary for work of the module autentifikatsii), and also a special ini-file which should contain WMID, the password to it(him,them) and a way to keys on a server. The main and unique protective measure - to put(fold) all this kindly on a server as it is possible more deeply, for example to the address of type ./yUik3orl //9klv3adq/85hjklfr/
At such variant come across a file with keys can either the skilled shaman, or the full fool (to which, as is known, carries).
The second variant of reception of payments through WebMoney where is easier. For this purpose service Merchant serves. Here the scheme(plan) such: you transfer(transmit) server WebMoney the information on the order (number, the sum and so forth), the user passes(takes place) authorization (on server VebManej) then from its(his) account(invoice) the corresponding(meeting) sum is written off(copied), and the user perenapravlyaetsya back on a site.
by businesscrp.com
