Table of Contents

Standard Scheme

Description

This trading scheme can be used to place orders on multiple products at once. When placing an order, the partner must pass the unique order number and a list of order lines as input parameters. Each line needs to contain a part number of the ordered item, desired quantity, and order line number (which is also unique compared to all user's order lines in the MONT system). We recommend the following approach to generating order numbers: Assume an order has been placed in the partner's system for 2 products: abc-11111 and 6qr-00006. The system assigned a unique number to the order, for example KEYS-00004280. In this case, when the order is placed in the MONT system, the partner's number is used as it exists in the system (KEYS-00004280), and KEYS-00004280-N number is assigned to each line where N is order line sequential number.

ATTENTION!
When designing their proprietary system, the partner needs to remember that keys/links/files ordered via ESD cannot be returned and an order cannot be canceled after placement. Therefore, we recommend that you place an order in the MONT system only after the end users effects a payment. The need to follow this recommendation depends on the partner's business processes.

System operation procedure

  1. GetPriceChanges. The partner receives current prices. Learn more...
  2. GetMenu. The partner receives a list of product categories for their website data mart. Learn more...
  3. GetProduct. The partner downloads a description for each product.
  4. The buyer selects a product to be ordered on the partner's website.
  5. CheckLimits. The partner checks their available funds limit. Learn more...
  6. The partner checks product properties. If the product to be ordered does not require a license form to be filled out, proceed to step 10.
  7. GetUserInfoDescriptionFor. The partner receives license form fill out guidelines for the selected product.
  8. The buyer fills out the license form following the guidelines describing fields. Learn more..
  9. CheckEndUserInfo. The partner checks whether the license form is filled out correctly.
  10. AddOrder. The partner adds the order to the MONT system.
  11. GetOrder. The partner regularly requests the placed order until its status chances to Processed Successfully or Error.

Схема

Some partners who use cash registers ask to send them both the key and the product installation/activation guidelines to be printed on the receipt. Learn more...

Partner requirements

  • The partner shall be registered with the MONT system with a valid user name and password.
  • The partner shall have a list of product part numbers in the MONT system they intend to sell. At least one product shall be unlocked for sale.
  • The partner shall have all required contracts. Contract status is displayed by calling the CheckLimits method.
  • The partner shall have a sufficient funds limit to buy products.
  • If the partner uses receipts, the MONT system shall be configured to Prioritized Key Delivery when keys are immediately delivered in response to the request.

To specify signup details, contact your personal MONT manager or write to ESDTeam@mont.com

Integration procedure

Partner integration with MONT services comprises two steps:

  1. Development, debugging and testing in the test system
  2. Launch in the production system

Obtaining test access

All MONT services are available in both production and test (sandbox) environments. To ensure system integrity, partners can work in the sandbox only during the development stage. To obtain access (user name and password), send a message to webstore_support@mont.com with the subject 'Test access for auto-placement of orders'. The reply will contain test user name and password.

User name/password for auto-placement of orders is in no way connected with user name/password for placement of orders via web-interface (portal.mont.ru, eShop). A different user name is ALWAYS used for auto-connection.

Transfer to production platform

When the partner believes that integration is completed on their side and they are ready to switch to production mode, they need to test integration. Integration testing procedure is described for each module (and included in service description) and can sometimes be modified (for example, if the partner integrates with eKey, but will only buy keys for Microsoft Office). After testing is successfully completed, the partner is provided with a user name in the production system. To receive a user name, send a message to webstore_support@mont.com. If you have questions or something is out of order during or after integration, you can send a message to webstore_support@mont.com.

Download instruction classic_scheme.pdf

,