WebMoney

Wiki

XML-interfaces

Description of XML Interfaces

XML interfaces are basically text message interfaces that send data via HTTPS protocol (http over 128-bit SSL) to special certification web servers of the system. Data is sent in the XML format with help of special module for authentication of WebMoney Keeper key files or standard certificates (WM Keeper WebPro certificates).

Description of XML-interfaces for transfer WMZ and WME are resulted in special article.

Interfaces using WM Keeper WinPro (Classic) authentication are located at https://w3s.webmoney.ru/asp/XML*.asp. Interfaces using WM Keeper WebPro certificate authentication are located at https://w3s.wmtransfer.com/asp/XML*Cert.asp.

In case WM Keeper WinPro (Classic) authentication is used, the request submitted to the certification server passes a signature created in the same manner as for https interfaces. The signature is sent in the parameter: <sign>...</sign>
In case WM Keeper WebPro (Light) authentication is used, WM Keeper WebPro (Light) certificate is used when connecting to the server: https://w3s.wmtransfer.com. In this case the <sign>...</sign> parameter is not used.

Regardless of the authentication type, requests have similar format and differ only in the method of creation and transmission of signature. Below you will find samples of requests:

Structure of a request based on WM Keeper WinPro (Classic) authentication (signature is created using WMSigner)

<w3s.request>
  <reqn></reqn> - request number
  <wmid></wmid> - WMID  of the signer
  <sign></sign> - signature created using WMSigner
  <request_type>
    ... - request parameters
  </request_type>
</w3s.request>

Structure of a request based on WM Keeper WebPro certificate authentication (Parameters wmid and sign should not be used; WMID's certificate should be used to connect to the server). You will find more information on certificates at msdn.microsoft.com
<w3s.request>
  <reqn></reqn> - request number
  <request_type>
    ... - request parameters
  </request_type>
</w3s.request>

In responding to a request, the server determines the data that needs to be returned. The structure of a response does not depend on the authentication type. Below you will find a sample response structure:

<w3s.response>
  <reqn></reqn> - number of the request the server is responding to 
  <retval></retval> - error code: 0 - successfully performed 
  <retdesc></retdesc> - error description if retval != 0
  <response_type>
    ... - response parameters
  </response_type>
</w3s.response>

The following interfaces can be used by online businesses:

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 WinPro
  • 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
  • Interface X19 — Verifying personal information for the owner of a WM identifier
  • Interface_X20 — Making transactions through the merchant.webmoney service without leaving the seller’s site (resource, service, application)
  • Interface_X21 — Setting trust for merchant payments by SMS
  • Interface_X22 — Receiving the ticket of prerequest payment form at merchant.webmoney

See also:
XML-interfaces to top-up WMZ and WME
WebMoney root certificate
Merchant WebMoney Transfer