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 Light certificates).

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

In case WM Keeper 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 Light authentication is used, WM Keeper 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:

1. Structure of a request based on WM Keeper 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>
2. Structure of a request based on WM Keeper Light 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:

The following interfaces can be used by online businesses:

• Purpose and description of WMSigner module
• Purpose and description of WebMoney HTTPS interfaces
• Interface X1. Sending invoices from one WMID to another
• Interface X2. Sending 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 messages to arbitrary WMID via secure WM Keeper messenger
• Interface X7. Validation of signature made with WM Keeper Classic keys
• Interface X8. Collecting information on a WM purse belonging to a WMID. Finding a user by his WMID or WM purse
• Interface X9. Receiving balance statement
• Interface X10. Receiving the listing of incoming payable invoices
• Interface X11. Collecting information from client's WM passport by his WMID
• Interface X12. Importing purse statement into 1C- software 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
• Program access to the XML interfaces from PHP scripts using CURL extension

WebMoney root certificate in the PEM format (to be used with CURL library)