For example, casino script installation program, that accepts JetSwap money and points and using this interface, can add a custom website for JetSwap Merchant payment processing system with all the necessary settings (to activate the possibility of receiving payments), register a new API-Interface for the payment of winnings, to save all data in the database, then turn off the automatic configuration interface for security user account. And all that user has to do - is to enter his/her username and temporary automation code (issued by our site) in the installer (and the data will not be saved, which enhances security, and automation code changes all the time).

• Interface functions

• Function 1. Adding new site for payment acception
• Function 2. Adding new API-interface
• Function 3. Disable User account Automatic Configuration interface

• Function 1. Adding new site for payment acception

Request form must have the following options:
Action: http://go.jetswap.net/api
Method: POST
Fields, transmitted in form:

Option	Required	Description
PAY_INTERFACE	Yes	Must be set to 4.
PAY_USER	Yes	Sellers JetSwap Username
PAY_TIME	Yes	Time of the transaction in UNIX_TIMESTAMP format. May deviate from server time not more than 10 minutes (server time is Moscow).
PAY_CODE	Yes	Control signature request (form described below)
fnc	Yes	Must be set to 1.
name	Yes	Your site name.
result	Yes	URL to send a message about the payment
success	Yes	Successful payment implementation URL.
successm	Yes	Success URL Send method: GET/POST
middle	Yes	Non-automatic payement execution URL
middlem	Yes	Middle URL Send method: GET/POST
fail	Yes	Error of payment URL
failm	Yes	Fail URL Send method: GET/POST
email	No	Seller's E-Mail for payment result
allowcurl	No	Allow using Success URL, Middle URL è Fail URL, transmitted in the payment request form 0/1
code	Yes	Code to validate the payment report (PAY_KEY)
ps	No	Enable payments for external payment systems 0/1

After processing the request, the server will respond:

Possible answer	Description
!ID	The operation was successful, ID of the registered site in JetSwap Merchant system (option PAY_SITE). For example, !123.
1	PAY_USER is not registered in the system.
2	Invalid PAY_CODE
3	PAY_TIME does not meet the requirements
?PARAMETER	One of the mandatory parameters is not specified or accepts invalid values. Instead PARAMETER will be displayed it's name, For example ?result.
5	Variable PAY_INTERFACE is incorrect or missing
6	Interface AutoConf is not activated for the user
Any Other	Internal server error

Electronic signature of the request ( PAY_CODE option)
To verify the authenticity of the request using an electronic signature, which is passed to the handler in variable PAY_CODE. It is formed using the md5 function:
PAY_CODE=md5("PAY_INTERFACE::PAY_USER::PAY_TIME::fnc::PAY_KEY")
where PAY_KEY - Automation code, obtained by activation of automatic interface configuration and other variables described above in this paragraph. The symbols "::" is not replaced and are separators of variables.

• Function 2. Adding new API-interface

This feature allows you to add a new API-Interface. Appointment of fields described briefly, a more detailed description can be found in API-interface manual. Form request must have the following parameters:
Action: http://go.jetswap.net/api
Method: POST
Fields, transmitted in form:

Option	Required	Description
PAY_INTERFACE	Yes	Must be set to 4.
PAY_USER	Yes	Seller's JetSwap username
PAY_TIME	Yes	Time of the transaction in UNIX_TIMESTAMP format. May deviate from server time not more than 10 minutes (server time is Moscow).
PAY_CODE	Yes	Control signature of request (formation described below)
fnc	Yes	Must be set to 2.
name	Yes	Interface name
ip	Íåò	Allowed IP-addresses
op	Yes	List of permitted operations. List Format: each operation can be set to 0 (forbidden) or 1 (allowed). List of permitted operations. List Format: each operation can be set to 0 (forbidden) or 1 (enabled). The sequence of operations: transfer of funds, transfer of points, balance check. For example, 001 - allows verification of the balance, 110 - allows the transfer of money and credit, and prohibits the verification of balance. Must be transferred to all three control number from 000 to 111.
code	Yes	The code that is used in formation of control signature of request to the interface.

After processing the request, the server will respond:

Possible answer	Description
!ID	The operation was successful, ID of the registered API-Interface (option PAY_API). For example,! 123.
1	PAY_USER is not registered in the system.
2	Invalid PAY_CODE
3	PAY_TIME does not meet the requirements
?PARAMETER	One of the mandatory parameters is not specified or accepts invalid values. Instead PARAMETER will be displayed it's name, For example ?result.
5	Variable PAY_INTERFACE is incorrect or missing
6	Interface AutoConf is not activated for the user
Any other	Internal server error

Electronic signature of the request ( PAY_CODE option)
To verify the authenticity of the request using an electronic signature, which is passed to the handler in variable PAY_CODE. It is formed using the md5 function:
PAY_CODE=md5("PAY_INTERFACE::PAY_USER::PAY_TIME::fnc::PAY_KEY")
where PAY_KEY - Automation code, obtained by activation of automatic interface configuration and other variables described above in this paragraph. The symbols "::" is not replaced and are separators of variables.

• Function 3. Disable AutoConf

This feature allows you to disable user account automatic configuration interface after all necessary action for the installation program. Typically, users do forget, so that better care for them. Form request must have the following parameters:
Action: http://go.jetswap.net/api
Method: POST
Fields, transmitted in form:

Option	Required	Description
PAY_INTERFACE	Yes	Must be set to 4.
PAY_USER	Yes	Seller JetSwap username
PAY_TIME	Yes	Time of the transaction in UNIX_TIMESTAMP format. May deviate from server time not more than 10 minutes (server time is Moscow).
PAY_CODE	Yes	Control signature of request (formation described below)
fnc	Yes	Must be set to 3

After processing the request, the server will respond:

Possible answer	Description
0	The operation was successful, the interface is disabled.
1	PAY_USER is not registered in the system.
2	Invalid PAY_CODE code
3	PAY_TIME does not meet the requirements
?PARAMETER	One of the mandatory parameters is not specified or accepts invalid values. Instead PARAMETER will be displayed it's name, For example ?result.
5	Variable PAY_INTERFACE is incorrect or missing
6	Interface AutoConf is not activated for the user
Any other	Internal server error

Electronic signature of the request ( PAY_CODE option)
To verify the authenticity of the request using an electronic signature, which is passed to the handler in variable PAY_CODE. It is formed using the md5 function:
PAY_CODE=md5("PAY_INTERFACE::PAY_USER::PAY_TIME::fnc::PAY_KEY")
where PAY_KEY - Automation code, obtained by activation of automatic interface configuration and other variables described above in this paragraph. The symbols "::" is not replaced and are separators of variables.