Electronic cheque-based payment system
Patent Information
- Application Number
- LAP321
- Authority / Receiving Office
- LA · LA
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2011-12-30
- Filing Date
- 2012-12-28
- Publication Date
- 2025-12-12
AI Technical Summary
Existing electronic payment systems lack security and transparency in mutual settlements, with issues such as unsecured checks, incomplete transaction documentation, and complex check circulation processes, which hinder real-time and secure electronic mutual settlements.
A multifunctional electronic system for managing electronic checks, utilizing a server and client computer setup with encryption and digital signatures for secure communication, user authorization, data synchronization, and a comprehensive check circulation process, including issuance, payment, and verification, ensuring all transactions are recorded and verified in real-time.
The system enhances security and transparency in electronic mutual settlements by providing a complete documentary base for transactions, ensuring secure and real-time operations through technical means and methods for accounting, authentication, and full-cycle electronic check management.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
[0001] ELECTRONIC CHECK SETTLEMENT SYSTEM AND METHODS OF ISSUE, TRANSFER, PAYMENT AND VERIFICATION
[0002] ELECTRONIC CHECKS.
[0003] Field of technology
[0004] The invention relates to information technology, specifically electronic systems and methods for handling monetary funds, and can be used to resolve real-time settlements between participants in an electronic payment system. The cash equivalent in the present invention is electronic bank checks made payable to bearer, which comply with banking regulations and current legislation.
[0005] State of the art
[0006] Electronic payment systems that utilize electronic checks for settlement purposes are well known. One such system is CyberCheck, which utilizes electronic checks as a means of payment for goods and services. In this system, checks are used solely for payment transactions and are generated only after they are signed by users. This does not ensure full circulation of funds, significantly limiting the capabilities of the settlement system and creating the potential for the issuance of unsecured checks.
[0007] Another well-known system is NetChex, which is a quasi-electronic payment system. In this system, only the customer's check issuance instruction is received electronically, while the check is sent to the service / product provider in paper form, which also limits the capabilities of the payment system and significantly complicates the check handling process.
[0008] Paymer digital checks are also used for settlements. With this system, check information is stored in documented form on paper as it circulates, and check transactions between system users are possible both electronically and using paper media. However, checks are not linked to a specific owner, which creates the problem of "joint ownership." by check. Obviously, this system does not eliminate risks in electronic settlements and does not ensure transparency of all transactions with electronic checks. Disclosure of the invention
[0009] The objective of the present invention is to provide an electronic monetary system that serves for electronic settlements between its participants in real time using electronic analogues of bank checks, providing its participants with a high level of security and the ability to obtain a complete legally significant documentary base for all transactions carried out by participants in the system.
[0010] The technical result achieved by the invention is the creation of a multifunctional system for the electronic circulation of checks, as well as an increase in the security of mutual settlements using electronic checks, ensured both by technical means and methods for recording electronic checks, verifying the authenticity of electronic checks, authenticating system participants, and by ensuring a full cycle of circulation of electronic checks, including methods for issuing, paying for electronic checks, and performing transfers of electronic checks.
[0011] In order to achieve the above technical result, an electronic system for settlement by electronic checks is used, containing at least one server computer device for processing and storing data, including a server application and at least one client computer device for processing data, including software and hardware client modules, designed to provide the ability to connect the client computer device to the server via Internet communication channels and to protect the communication channels by software and hardware of the server and client modules using encryption and an electronic digital signature.At the same time, the declared electronic system for settlements with electronic checks differs from the prototype in that the client and server applications contain, at a minimum, interconnected user authorization blocks in the system, a block for updating and synchronizing data of the client and server applications, and also contain a block for entering parameters for performing transfers and storage. information on payments of the client application, connected by software and hardware with the blocks for checking the parameters of transfers of electronic checks, connected with the block for authorization and verification of user parameters and the block for registering and executing transfers of electronic checks of the server application, connected by feedback channels with the blocks for managing electronic checks, crediting the check, commission and sending notifications to the user in real time, connected with the block for updating and synchronizing data of the client application, as well as the inclusion in the client application of an electronic signature block, connected by software and hardware with the block for generating and storing digital documentation of the server application, connected with the block for registering and executing transfers of electronic checks,wherein the control unit for electronic checks of the server application is implemented in a software and hardware manner via feedback channels with interconnected units for registering operations with electronic checks in the register and issuing electronic checks, connected to the electronic check signature unit.
[0012] In this case, the client application blocks are grouped into modules by categories corresponding to the user status determined by the authorization block of the client and server applications, with the ability to pre-set a set of check handling parameters for each category.
[0013] In particular, the system provides for three categories of users - the initial one, with a minimum set of parameters for handling checks (in the system operating mode, when the transfer of electronic checks of the standard category of users, as well as the bank, is carried out through a dealer (broker) - the initial category is used exclusively for registration and sending an application to change the status (user category)); standard - requiring the provision of additional information about the participant and allowing the participant to present checks for payment to the bank and select the paying bank for their checks; and extended - having the widest range of functional capabilities, intended for the work of the Issuer, Partner banks and Dealers (Brokers) of the system with the ability to generate an additional set of check circulation parameters for each category. At the same time, to participate in the system as For a legal entity, the client must have a standard or extended category, which can only be obtained by completing the appropriate status change procedure, which guarantees that all necessary checks of the organization have been carried out.
[0014] The technical result is also achieved by proposing methods of payment, issuance, transfer and verification of electronic checks using the above-mentioned payment system.
[0015] The method for performing transfers of electronic checks, which includes the stage of entering user data and his authorization in the system, as well as entering the transfer parameters, differs in that it allows for the transfer of a check in real time in accordance with the restrictions presented in the method of accounting for electronic checks and includes the following stages: authorization in the System; obtaining account data; entering the parameters for the transfer of an electronic check; checking the parameters of an electronic check; registering a request for the transfer of an electronic check; the operation of exchanging the sender's check for several checks (a transfer check, a commission check, a new balance check), which includes the presentation of checks for payment, payment and the issuance of new checks; crediting the electronic commission check to the Operator's account or, in the operating mode of the system when transferring electronic checks of the standard category of users, as well as a bank through a dealer (broker), to the account of the Dealer (Broker);Crediting an electronic check to the Recipient's account; the exchange of the Recipient's checks for one check (if the Recipient has a balance in their account), which includes presenting the checks for payment (including through collection), payment, and issuing new checks; completing the transfer, accompanied by the creation and signing of electronic documents, and informing the participants of the transfer. This method of transferring electronic checks is accompanied by the creation of all necessary legally binding documents, and all completed actions are reflected in the Check Movement Register.
[0016] The method for issuing electronic checks presented in the invention allows for the issuance of electronic checks only after several categories of users have completed mandatory steps. The issuance method includes the mandatory steps of the issuer generating a check issuance request, the bank verifying the receipt of funds into the issuer's bank account, and Act as collateral for this check, and ensure that it complies with the request parameters and the bank confirms the issuance of the electronic check. Independent issuance by only one participant is not possible. The issuance is accompanied by the creation of legally binding documents and the recording of transactions in the Check Movement Register.
[0017] The electronic check payment method also involves several steps and requires the mandatory participation of several categories of users. This method includes the following steps: the client submits a check payment request to the bank; the bank verifies the details specified in the request and the ability to pay the check; the bank sends the client an invoice for check crediting; the client transfers the check presented for payment to the bank by paying the invoice; the bank sends a request for check verification to the issuer; the issuer verifies the check presented for payment; the issuer confirms the request by sending a verification notification; and the check is paid.
[0018] Brief description of the drawings
[0019] Fig. 1 Schematic representation of a System using methods according to the invention.
[0020] Fig. 2 The main blocks included in the client application.
[0021] Fig. 3. The main blocks that make up the server application.
[0022] Fig. 4. Diagram of the main sections of the client application database.
[0023] Fig. 5. Diagram of the main sections of the server application database
[0024] Fig. 6. Diagram of interaction of blocks when transferring an electronic check.
[0025] Fig. 7 Block diagram of the operating algorithm of the client block K5 for entering parameters and performing transfers.
[0026] Fig. 8 Block diagram of the procedure for carrying out the operation of the server block S5 for registering and transferring electronic checks.
[0027] Fig.9 Block diagram of the procedure for exchanging (combining) electronic checks of the server block S7 for managing electronic checks.
[0028] Fig. 10. Diagram of interaction of blocks during the procedure of issuing an electronic check.
[0029] Fig. 11. Diagram of interaction of blocks during the procedure of payment of an electronic check. Fig. 12. Diagram of interaction of blocks during the electronic check verification procedure.
[0030] The following symbols are used in the above illustrative diagrams:
[0031] K1 - client registration unit in the system (KB R)
[0032] K2 - client authorization block in the system (KB A)
[0033] KZ - client block for updating data, synchronizing the database of client and server applications (KB ODS)
[0034] K4 - client-server interaction block (CSIB)
[0035] K5 - client block for inputting parameters and performing transfers (KB VDVP)
[0036] KB - client block for data entry, sending invoices for check crediting (KB VDOS)
[0037] K7 - client block for data entry, sending requests for purchase and sale of electronic checks (KB OZPPEC)
[0038] K8 - client block for data entry, sending applications for payment of electronic checks (KB OZOEC)
[0039] K9 - client block for processing received electronic check transfers (KB OPPECH)
[0040] K10 - client block for processing received invoices for crediting checks (KB OPSZCh)
[0041] K11 - client unit for electronic signature of digital documentation (KB CP) K11 (Issuer) - client unit for data entry, sending requests for the issue of electronic checks (KBE OZVECh)
[0042] K 12 (Issuer) - client block for processing received requests for verification of electronic checks (KBE OPZVFECh)
[0043] K13 (Bank) - client block for processing received requests for issuing electronic checks (KBB OPZVECH)
[0044] K 14 (Bank) - client block for processing received applications for payment of electronic checks (KBB OPZOEC)
[0045] K 15 (Bank) - client block for data entry, sending requests for verification of electronic checks (KBB VDOZVFECH) K 16 (Issuer) - client block for processing received applications for the purchase of electronic checks (BE OPZPECH)
[0046] 16 (Dealer) - client block for processing received applications for the purchase of electronic checks (KBD OPZPECH)
[0047] K17 (Dealer) - client block for processing received applications for the sale of electronic checks (KBD OPZPREC)
[0048] 51 - server unit for registration and management of user accounts (SB RUUZP)
[0049] 52 - server block for authorization and verification of user parameters (SB APPP)
[0050] 53 - server block for updating data, synchronizing the database of client and server applications (SB ODS)
[0051] 54 - server unit for checking the parameters of electronic check transfers (SB PPPECH)
[0052] S5 - server unit for registration and execution of electronic check transfers
[0053] (SB RVPEC)
[0054] 55 - server block for managing user accounts (SB UUSP)
[0055] 56 - server block for registration of applications, requests, and invoices for crediting checks (SB RZZSZEC)
[0056] S7 - server control unit for electronic checks (SB UECh)
[0057] 58 - server unit for registering transactions with electronic checks in the register (SB ROECHR)
[0058] 59 - server unit for generating digital documentation (SB GCD)
[0059] S10 - server unit for sending online notifications (SB OOU)
[0060] S 11 - server unit for issuing electronic checks (SB VECh)
[0061] 512 - server unit for signature of electronic checks (SB PEC)
[0062] 513 - server unit for processing and executing applications and requests (SB OIZZ)
[0063] 514 - server block for writing off electronic checks (SB SEC)
[0064] Implementation of the invention
[0065] The present invention is aimed at providing a system of mutual settlements with electronic checks (hereinafter referred to as the System) between organizations and / or individuals in real time. Technically, the implementation of this System can At least one server computer device for processing and storing data, a server application included therein, and client computer devices for processing data, each with its own client applications, which facilitate interaction between the client devices and the server. Interaction between the client devices and the server is accomplished via the Internet, over secure communication channels. Security of the communication channels is ensured by the server and client applications using encryption algorithms and electronic digital signatures.
[0066] The methods presented in the present invention are expressed in corresponding operating algorithms for server and client computing devices. The devices' operation conforms to these algorithms by executing a sequence of software instructions presented in the server and client applications. The architecture of a server device, or set of devices, should be based on the use of one or more computers connected by a local area network and, at a minimum, should include the following modules: a database management system, a web server (a module that enables interaction with client applications via the internet), an application server (a module that implements the application's core logic and enables interaction with the DBMS), and an online messaging module (ensuring instant notification of users about events in the System).
[0067] The client device architecture can be based on the following possible client application solutions: a separate client application with its own user interface (described further in the document); a client application in the form of an embedded module in a standard Internet resource browser (web browser) with its own user interface displayed in the web browser (has the same basic blocks and interaction schemes as described further in the document); in the form of a thin client based on a web browser with the transfer of information processing and user interface generation blocks to the server. In thin client mode, only user input is processed on the client device. The web browser interface includes electronic signatures of digital documents, data encryption, data transmission to the server, data reception from the server, decryption, and output to the web browser user interface. Moreover, if the client application is implemented as an embedded module or thin client, the client device and the entire System as a whole have the same functionality as the System when using a client device based on a separate client application with its own interface.
[0068] The described System does not limit the possible implementations of this invention.
[0069] The structure of the client and server applications as functional blocks is shown in Figs. 2 and 3. In the described implementation of the System, the client application has several operating modes, which are determined by the status of the user logged into the System. Additional blocks are allocated for Issuer, Bank, and Dealer (Broker) modes. The remaining blocks can be accessed in any operating mode (possible limitations are determined by the specific implementation of the System). Implementations are possible in which there is not one, but several client applications, each with a corresponding set of blocks available.
[0070] Categories of Participants
[0071] It is assumed that there are three main types of statuses in the System
[0072] Participants.
[0073] Participants are defined as users (legal entities or individuals) whose information is stored electronically in the System's database and who interact with the System using client computing devices. A Participant's status determines a set of rights granted to them, which grants them the ability to execute certain algorithms in the System and access a certain amount of information stored in the System.
[0074] Initial status is a Participant level with a limited set of System capabilities and does not require the provision of documents to confirm the information entered by the user during registration. At the initial level, registration is only possible as an individual. A legal entity may Register in the System only when upgrading from the Basic to the Standard level. However, in the system's operating mode, when electronic check transfers for users with a Standard status, as well as for the bank, are processed through a dealer (broker), the Basic category is used exclusively for registration and submitting requests to change status (user category).
[0075] Standard status is a level intended for authorized System Participants, whether individuals or legal entities. To obtain this status, a Participant must provide additional personal information and a number of supporting documents. This status allows Participants to present checks for payment to the Bank and select the paying bank for their checks.
[0076] Extended status is a level intended for the work of the Issuer, Partner Banks and Dealers (Brokers) of the System.
[0077] To ensure the operability of the methods presented in the invention, the following Participants must be registered in the System:
[0078] · Issuer - an organization on whose behalf electronic checks are issued;
[0079] • Operator – the owner of the rights to the System, ensuring its functioning;
[0080] • at least one Bank - a partner bank, in the Issuer’s current account where there are funds that serve as collateral for the issued checks;
[0081] • at least one Dealer (Broker) - a legal entity that carries out on an ongoing basis transactions for the purchase and sale of electronic checks with Participants and the purchase of checks from the Issuer.
[0082] Participants registered as a Bank or Dealer (Broker) can also act as clients and use the standard functionality of the system.
[0083] An approximate diagram of such a System is shown in Fig. 1.
[0084] To acquire the appropriate status and gain access to the System, a Participant must complete registration, which consists of a varying number of steps depending on the requested status. The first step of registration in the System is completed using the client application and includes entering the participant's personal data, configuring security settings, reviewing the offer agreement, and generating electronic keys for the ASP. (analogous to a handwritten signature). As a result of the first stage of registration, the Participant is assigned a unique registration number, a public key for ASP verification is registered in their name on the System server, and the Participant's data is recorded in the System database.
[0085] As a result of the first stage of registration, the user is assigned
[0086] Initial Status. To obtain Standard or Extended Status, a Participant submits an electronic application through the System, specifying the category (individual / legal entity) and entering all the requested information. To confirm the entered information, the Participant provides duly certified copies of documents. Only after successfully completing the document verification stage and, if necessary, concluding additional agreements (for the Bank, Dealer (Broker), or Issuer) is the Participant assigned the requested status and granted the corresponding set of rights in the System.
[0087] Participants of any status in the System can open an unlimited number of current accounts denominated in currencies supported by the System. Participants with a status higher than Initial have the option to choose the bank that will act as the payer for a check equal to the current account balance. When an account is opened, it is assigned a unique number in the System, which can be used to uniquely identify the Participant.
[0088] Electronic checks
[0089] Electronic checks are the equivalent of cash in the System. An electronic check is a paperless bearer check and contains the following mandatory details:
[0090] • check number – unique check identifier,
[0091] • the name “check” included in the text of the document and expressed in the language of the country in which the document was drawn up;
[0092] • a demand to pay a certain amount (check denomination);
[0093] · name of the paying bank;
[0094] • indication of the account from which the payment should be made;
[0095] • indication of the payment currency; • indication of the date and place of issue of the check;
[0096] • signature of the Issuer (drawer).
[0097] The paperless form of checks is recognized as legal, and a check drawn up in this form is a valid payment instrument in accordance with the Bank of Russia Regulation "On Non-cash Settlements in the Russian Federation," which determines the specifics of the methods of working with electronic checks described below.
[0098] An electronic check is represented as a record in the database. The electronic check's signature is represented as a CSA (analogous to a handwritten signature), obtained by cryptographically transforming the check's details using the Issuer's private key. This signature protects the electronic check from counterfeiting, allows for the identification of the drawer, and ensures the integrity of the information in the electronic check.
[0099] Electronic checks are recorded in Participants' accounts (check accounts). After check exchange transactions are completed, only one check, equal to the account balance, can be linked to a single standard client account in the System. Specialized accounts, which can hold multiple electronic checks simultaneously, are used to record checks presented to the bank for payment.
[0100] Electronic checks are characterized by the following condition:
[0101] • Check in circulation – a valid check in the possession of one of the Participants of the system;
[0102] • The check is presented for payment (to the paying bank);
[0103] • The check is presented for payment via collection;
[0104] · The check has been paid.
[0105] Changes in the status of an electronic check or a change in check ownership can occur as a result of certain transactions, such as check issuance, check transfer, check presentation for payment, check collection, check payment, and collection. All transactions with electronic checks are recorded in the Check Movement Register and are accompanied by the generation of legally binding documents certified by the respective parties' ASPs. Electronic checks have a limited validity period, after which they are automatically exchanged for equivalent checks with a new number and issue date.
[0106] Method for performing electronic check transfers
[0107] The presented method for transferring electronic checks consists of a specific sequence of key process steps, some of which are mandatory and some of which are optional. The mandatory nature of the steps is determined by the fulfillment of certain conditions, as described in the algorithms presented below. The implementation details of the algorithms, such as the programming language and the architecture of the software implementing the method, are not limited by this invention.
[0108] The method assumes that the Participant's computer device is configured in such a way that it allows the execution of software instructions of the client application implementing the presented method and interaction with the server computer device via the Internet.
[0109] The transfer process begins when the user launches the client application, which initializes the K2 client authorization block in the System. During this block, the Participant's account must be verified and the appropriate rights granted. To perform these operations, the K2 client block, via the K4 server interaction block, communicates with the S2 server authorization block and verifies user parameters. Upon receiving the command and necessary data, the K4 block generates a request in the required format, encrypts and signs the request, establishes a connection with the server, transmits the request (via a secure internet connection), and processes the response. It is understood that all client-server interactions occur through the K4 block, and it will not be mentioned further.
[0110] The implementation of the client and server authorization block is not the subject of this invention and may include various combinations of well-known methods of user authentication and authorization. Mandatory for these blocks is the verification of the Participant's account, the availability and correctness of the electronic key storage, which will subsequently be used to create a handwritten signature (HSA) for requests and electronic documents, and the receipt of information about the Participant's status and corresponding rights. Based on the Participant's status, the Participant's ability to perform actions not provided for their status is blocked. This blocking occurs both at the client application level (lack of an appropriate user interface, execution of verification algorithms in the client application) and at the server application level (the server blocks included in it access the S2 block when processing each received request to verify the status and other user parameters).
[0111] Successful completion of the authorization block guarantees that the Participant has not been deleted or blocked, and that his private electronic key corresponds to the public key registered in the System.
[0112] Successful execution of the authorization block is a prerequisite for proceeding to the next block (KZ update block), synchronizing client and server application data. The client KZ block communicates with the server S3 update block, synchronizing client and server application data. During the execution of the KZ and S3 blocks, information about the current status of the Participant's account balances, received transfers, and check deposit accounts is obtained. Depending on the Participant's status, the corresponding types of applications and requests are received, and their statuses are updated. Execution of these blocks must guarantee the Participant's access to information on all sent and received transfers, check deposit accounts, applications, requests, and other information (e.g., by synchronizing the Participant's client application database with the server database). Methods for implementing these blocks are generally known and are not the subject of this invention.As an example of the implementation of the System, a variant is considered where the information received from the server is stored in a local database, the diagram of which is shown in Fig. 4. After successful completion of the KZ block, the application displays the received information in the user interface, including information about all of the client's accounts: account number, account name, active account balance, electronic check number linked to the account, bank details associated with the account, etc. The volume of information received and displayed is determined by the System implementation option.
[0113] Successful execution of the S3 server block and the K3 client block for updating and synchronizing data between the client and server applications is a prerequisite for moving to the K5 block for entering parameters and performing transfers.
[0114] To initialize this block, the Participant selects the appropriate section in the user interface of the client application.
[0115] Block K5 allows the user to enter the required initial data for an electronic check transfer. This block can provide various options for entering transfer parameters: direct parameter entry (entering the recipient's account number, the check amount to be received or the check amount to be written off, and the payment purpose), selecting parameter options from lists of possible values (selecting from a list of the sender's open accounts, selecting the recipient's account number from the correspondent directory), and generating a transfer based on a received check deposit invoice or a specific type of request (e.g., a request to purchase an electronic check). The latter option is based on the use of information obtained during the K3 update block, synchronizing data between the client and server applications, and storing it in the application in a manner appropriate to the specific implementation of the System (in the RAM or ROM of the computer device).The method for entering transfer parameters may include automatic validation performed during the parameter entry process, prompting the user to immediately notify them of any errors. The method may include automatic calculation of the transfer fee when the application receives the transfer amount. The fee calculation may be performed by the module based on local application data (stored in RAM or a database, loaded, etc.). For example, when retrieving account data) or based on a commission rate downloaded from the server via a separate request. This feature can be used to implement more complex commission settings, such as making the commission rate dependent on the Participant's status in a group (in this case, determining the commission requires data on both the sender and recipient of the transfer), the ability to set an individual commission for the Participant, etc. After calculating the commission, the module informs the user of the commission amount charged for the transfer and the amount to be debited (or the amount to be received, depending on the parameter entered).
[0116] An example of the algorithm for the operation of block K5 for inputting parameters and performing transfers is shown in Fig. 7.
[0117] It is possible to implement implementations in which, during the process of entering transfer parameters based on the recipient's account number, information about the transfer recipient will be downloaded from the server and displayed to the Participant in order to minimize the risk of entering incorrect data.
[0118] The method may include a preliminary transfer parameter check step, during which the K5 unit generates an electronic data verification request and transmits it to the S4 server unit for verifying electronic check transfer parameters. The request includes the account numbers of the sender and recipient, the amount, and the transfer currency. During these checks, the S4 unit determines whether the transfer can be executed with the specified parameters. Server unit S2 is then called, performing the necessary checks on both the sender (including checking the ASP request) and the recipient (including checking the availability of the recipient's account).Data about the electronic check held in the transfer sender's account is retrieved from the database, the check denomination is compared with the amount to be debited (implementations are possible that allow blocking of a specific amount in the account, in which case the amount to be debited is compared with the available active balance), and other checks are performed as required by the specific System implementation. Checks are performed by verifying information stored in the System database, checking account settings in the database, and executing digital signature verification algorithms. The client block K5 for entering parameters and executing transfers receives information about the verification results from the S4 block and displays either a message about the error or a window with information about the transfer, which the client must reconfirm. At this stage, the module can display any transfer data (amounts, name, recipient's TIN, etc.) consistent with the method's implementation.
[0119] Having received confirmation of the transaction from the Participant, the K5 block generates an electronic request to execute the transfer, containing the account number for debiting, the account number for crediting the check, the amount, the transfer currency, the purpose of the payment, and transmits it to the S5 server block for registering and executing transfers of electronic checks.
[0120] Upon receiving a transfer request, the S5 unit performs the transfer registration procedure. During this procedure, to verify the incoming request, a transition is made to the S4 unit for verifying the parameters of electronic check transfers (all incoming data is transferred). Upon successful completion, the transfer information is recorded in the System database, and the commission is calculated and recorded. If the S4 unit returns an error, the transfer is not registered, and an erroneous transfer result (e.g., the operation status or error code) is returned to the K5 client unit.
[0121] At the stage of sending and registering a transfer request, the digital documentation generation and storage unit (S9) can be executed. This method involves integrating this unit into either the server or client application. As a result of this unit's execution (in this case, the transfer request generation procedure), a separate electronic document (e.g., in PDF format) is generated, containing all the details of the electronic check transfer request and, via the client-side digital signature unit (K 17), confirming the Participant's ASP. This method allows for various storage options for this document; for example, the document can be transferred to the server, stored along with the ASP and other information in the application database, and then made available to all interested parties via specialized services of the server application. If the document was generated on the server, the digital documentation electronic signature unit (K 17) must implement the procedure for downloading electronic documents from the server.
[0122] After successfully recording the transfer in the server database, block S5 executes the transaction procedure. An example of the algorithm for executing this procedure is shown in Fig. 8. The input parameters for this procedure are all received information about the transfer being performed.
[0123] Block S5 for registering and executing electronic check transfers receives data from the System database about the electronic check in the transfer sender’s account and the commission amount (sections “Information about user accounts”, “Information about electronic checks”, “Information about electronic check transfers”).
[0124] If the denomination of the balance on the sender's account matches the transfer amount and no transfer fee is charged, the electronic check is transferred from the sender's account directly to the recipient's account.
[0125] To transmit a check, the S5 block initiates execution of the S7 server block for managing electronic checks. This calls the electronic check transmission procedure, which receives the following inputs: the electronic check number, the sender's account number, and the recipient's account number. When the procedure is executed, information is modified in the "User Account Information" section of the database: the check information is deleted from the sender's account, the recipient's account record is updated with the new check balance number, and the check holder information is updated in the "Electronic Check Information" section.
[0126] This procedure initiates execution of block S8 for registering transactions with electronic checks in the Register. The input parameters when calling the procedure for recording a check transfer operation in the Register are: the electronic check number, the account number of the transfer sender, the account number of the transfer recipient, and the operation type ("check transfer"). Possible operation types in the Check Movement Register are: "check issue", "check transfer", "presentation of a check for payment", "presentation of a check for payment via collection", "check payment", "collection". Based on the input parameters, block S8 retrieves the necessary data from the database, in The "Electronic Check Movement Register" section of the database records entries containing at least the following information: number, date, time of the transaction, amount, currency, number of the check being transferred, account numbers of the sender and recipient of the transfer, transaction type, and account balance data. Once the transaction is successfully recorded in the Check Movement Register, the S7 block's electronic check transfer procedure is complete.
[0127] In a similar situation, where the entire denomination of the check must be transferred to the recipient, it is possible to first transfer the electronic check to the Operator, who then transfers the check to the recipient. The check transfer (as with all subsequent references) is carried out within the framework of the electronic check transfer procedure described above in the S7 electronic check management server unit.
[0128] If the specified condition is not met (the full denomination of the check must not be transferred to the recipient), block S5 calls the electronic check exchange procedure of block S7 of the electronic check management system. As input to this procedure, block S5 passes the following: the number of the electronic check whose denomination equals the balance in the sender's account, the denominations of the electronic checks to be exchanged, equal to the transfer amount, and the amount of the transfer fee.
[0129] As part of the procedure for exchanging an electronic check of the S7 block, the sender's electronic check is transferred to the System Operator (the procedure for transferring an electronic check of the S7 server block for managing electronic checks is carried out, the input to which is the number of the electronic check, the account number of the sender of the transfer, and the account number of the Operator).
[0130] The Operator presents the received electronic check for payment to the Paying Bank. The electronic check is presented for payment by executing the check presentation for payment procedure of the S7 electronic check management unit. The following information is passed to the input: the electronic check number, bank information (registration number), and the account number from which the check is presented (the Operator's account). During this procedure, the number of the specialized bank account to which the check will be transferred is determined. The check is then transferred in the same way as the standard check transfer procedure. The difference is that the electronic check status in the System Database changes to "presented for payment" (section "Information about electronic checks"). (checks) and indicating in the Check Movement Register the operation type "presentation of check for payment" or "presentation of check for payment via collection" when executing block S8 of the registration of transactions with electronic checks in the Register. The operation type "presentation of check for payment via collection" is used if the bank to which the electronic check is presented for payment and the paying bank for this check do not match.
[0131] After the check presentation procedure is successfully completed, since the bank to which the electronic check is presented for payment and the paying bank for this check are the same, the check write-off procedure of the S7 electronic check management block is called, with the electronic check number as input. As part of this procedure, the information about the paid check is updated in the "Information on Electronic Checks" section, and the execution of the S8 block for registering electronic check transactions in the Register is called. As part of the check write-off procedure, a record is added to the "Electronic Check Movement Register" section of the database containing the following: number, date, time of the transaction, amount, currency, check number being written off, the number of the accounting account to which the check was written off, the type of transaction, and the balance information on this accounting account.The procedure for writing off an electronic check is possible only when the check is paid and real monetary funds equal to the denomination of the check are transferred to its bearer, or when the funds released upon payment of the check are offset against the purchase of new electronic checks from the System Issuer by the person who presented the check for payment.
[0132] After the transaction has been successfully recorded in the Check Movement Register, the procedure for writing off the electronic check from the S7 block is completed.
[0133] Using the funds received (released), the Operator purchases new checks of the required denominations from the Issuer:
[0134] o Check for the transfer amount.
[0135] o Check for the commission amount (may be equal to 0, then the check is not issued), o Check for the balance amount (the balance may be equal to 0, then the check is not issued).
[0136] To do this, block S7, as part of the electronic check exchange procedure, sequentially calls block S11 for issuing electronic checks for each of the specified checks. Data on the details of the new check is passed to this block as input. Checks, which, at a minimum, include: denomination, check currency, and information about the paying bank. The paying bank for the check submitted for exchange is indicated as the payer for new checks.
[0137] When executing block S 11, the necessary information for specifying all the check details is retrieved from the system database, execution of block S12 for signing electronic checks is called (within the framework of which, by executing electronic digital signature algorithms, a signature of the check on behalf of the Issuer is created), a record of the new electronic check is created in the “Information on electronic checks” section of the database.
[0138] When issuing an electronic check, block S11 triggers the check issuance recording procedure of block S8, which registers electronic check transactions in the Register. The input parameters for calling this procedure are the electronic check number, the number of the accounting account to which the issued check will be assigned (the Issuer's accounting account), and the transaction type ("check issuance"). This procedure adds a record to the "Electronic Check Movement Register" database section containing the following: number, date, time of the transaction, amount, currency, issued check number, transaction type, the number of the accounting account to which the issued check will be assigned, and the balance information on this accounting account. After the operation is successfully recorded in the Check Movement Register, the operation of block SI 1, which issues electronic checks for the check for which the block was called, is terminated.
[0139] After successful completion of the work of block S 11, the issued checks are transferred to the Operator (in accordance with the procedure for transferring an electronic check of block S7 for managing electronic checks).
[0140] If the balance check was successfully issued, the Operator transfers the check to the transfer sender. Once this action is successfully completed, the electronic check exchange procedure for the transfer sender's check is complete.
[0141] As part of the S5 block transaction process, the operator transfers a check for the transfer amount to the recipient's account. From the database (section "Information on user accounts"), the S5 block retrieves information about the recipient's account balance and account settings. If the recipient's account has a check balance, or a bank is specified in the account settings, Different from the bank paying the transfer check, block S5 calls the electronic check exchange (combination) procedure of block S7 of the electronic check management system (Fig. 9). As part of this procedure, electronic checks (checks) are transferred from the recipient's account to the System Operator's account.
[0142] The operator presents the received electronic checks (checks) for payment to the bank designated as the payer on the recipient's "balance check," or to the bank specified in the account settings if there is no balance. In addition to the above, other methods are available for determining the bank that will act as the payer on the recipient's new check. For example, instead of using the account settings and the current balance check data, the payer bank can be selected based on a higher-denomination electronic check.
[0143] Presentation of checks for payment to the Bank is carried out within the framework of the procedure for presenting a check for payment in the S7 electronic check management unit.
[0144] Presentation of a check for payment to a bank other than the bank designated as the payer for the check occurs in accordance with the check presentation for collection procedure. This procedure ensures the availability of sufficient funds in the Issuer's current accounts with Partner Banks to serve as collateral for the checks issued by the Issuer.
[0145] For an electronic check presented for payment to the paying bank (in the described implementation, a check for the balance from the transfer recipient's account), the standard check write-off procedure of the S7 electronic check management unit is called.
[0146] Using the released funds, the Operator purchases a new check from the Issuer, the denomination of which will be the sum of the denominations of the checks presented for exchange (or equal to the denomination of the check presented for exchange for a check from another paying bank).
[0147] To do this, block S7, as part of the electronic check exchange (consolidation) procedure, calls block S11 for issuing electronic checks, passing it the denomination, check currency (equal to the currency of the checks being combined), and information about the paying bank. The payer for the new check will be the bank that paid the checks presented for exchange. The issuer transfers the issued check to the System Operator. The Operator transfers the new check to the recipient. Once these steps are successfully completed, the electronic check exchange (consolidation) procedure is complete.
[0148] Implementations are possible in which the recipient's checks are not exchanged, and any number of electronic checks are maintained in the recipient's account. For example, in the described implementation, the electronic check exchange procedure is not performed if the transfer is carried out through check presentation for payment and the check is deposited into a specialized bank account.
[0149] If a commission is charged for the transfer, block S5 triggers block S13 to credit the commission check. In the described implementation, if there is a balance check in the Operator's account or a bank other than the paying bank for the commission check is specified in the Operator's account settings, block S13 also initiates the electronic check exchange (consolidation) procedure of block S7 for managing electronic checks. During this procedure, a new check must be credited to the Operator's account, including the commission amount for the completed transfer. The procedure for exchanging the Operator's electronic checks is similar to exchanging the recipient's checks, with the exception of check transfers to the Operator and receipt of a check from the System Operator. It is also important to note that if the check transfer is carried out through a dealer (broker), then in block S13 the commission is charged not to the Operator, but to the Dealer (Broker) acting as an intermediary in the transfer.Check exchange transactions are always carried out through the Operator, regardless of the recipient of the commission.
[0150] When performing the S5 registration and electronic check transfer procedure, the S9 digital documentation generation and storage block is called. This block generates digital reporting documentation based on incoming transfer parameters for the purpose of signing by the ASP Participants and enabling subsequent printing.
[0151] In the described implementation, during execution of block S9, an Electronic Receipt Acceptance Certificate, a Certificate of Services Rendered, and an Invoice are generated. Documents are signed by the respective parties through execution of block K 17, an electronic signature for digital documentation. After the transfer is successfully completed and the required documentation is generated, block S5 initiates block S10 for sending online notifications. This block receives information about the transfer recipient and the type of message being sent. Execution of this block triggers the client block K3 for updating and synchronizing client and server application data. After receiving information about the transfer, block K17 for electronic signature of digital documentation can be called to sign the Receipt Acceptance Certificate by the transfer recipient.
[0152] Upon completion of the S5 block for registering and executing electronic check transfers, a message with the operation result is generated and transmitted to the client block K5 for entering parameters, executing transfers, and storing payment information in the transfer sender's application. Implementations (application operating modes) are possible in which the S5 block's operation procedure for registering and executing electronic check transfers is performed offline. This means that after the transfer registration procedure is successfully completed, the transfer sender (K5 block) is immediately notified that the transfer has been accepted by the System, and the transaction execution procedure is performed later.
[0153] Upon receiving a message about the completion of the operation, block K5 for entering parameters, executing transfers and storing information about the sender's payments displays information about the result of the transfer to the user, calls the execution of block K3 for updating, synchronizing the data of the client and server applications, upon completion of which the information about the current balance of the user's accounts is updated.
[0154] Method of issuing electronic checks
[0155] Below is a method for issuing electronic checks used in situations other than the automatic exchange of electronic checks during transfers. This method is designed to ensure the security of the process of placing new checks into circulation, issued not by paying for other electronic checks, but by actual funds deposited into the issuer's account, for example, when checks are purchased by a dealer (broker). The electronic receipt issuance process begins when the user, using the Issuer account, launches the client application. This initiates the K2 client block for authorization in the System. After completion, the K3 block for updating and synchronizing client and server application data is launched. Successful completion of the K2 and K3 blocks is a prerequisite for proceeding to the K1 block for data entry and sending requests for electronic receipt issuance. To initialize this block, the Issuer selects the appropriate section in the client application's user interface.
[0156] Block K11 allows the user to enter the required initial data to generate a request for issuing an electronic check. This block can provide various options for entering request parameters: direct parameter entry, selecting parameter options from a list of possible values (selecting from a list of paying banks), or generating a request based on a check purchase order received from a dealer (broker).
[0157] The mandatory parameters of an electronic check issuance request are: Issuer details (registration number, name, etc.), denomination, currency of the check being issued, payer bank, Issuer's bank account number to which payment for the check will be credited, and information about the check purchaser and payer (name, TIN, registration number, purchase order details, and the buyer's account for check crediting). After the Issuer correctly completes all required request parameters, Block K11 generates a check issuance request as an electronic document certified by the Issuer's ASP. Block K11 transmits the request to Server Block S6, which registers check crediting requests, inquiries, and accounts.
[0158] Block S6 performs the check issuance request parameter validation procedure, and server block S2 is called to perform the necessary checks on both the sender (including the request's ASP verification) and the recipient. If all checks are successful, the request is registered on the server. Records are entered into the "Information on Requests, Queries, and Accounts for Check Crediting" section of the database. A message about the new request is sent to the recipient (the paying bank for the check being issued) via block S10 for sending online notifications. When logging into the Bank's System or receiving an online notification, the KZ block (updates, synchronization of client and server application data) of the Bank's client application, through interaction with the S3 block, downloads a request from the server to issue an electronic check.
[0159] In this case, the S3 server block for updating data and synchronizing the database of the client and server applications checks that the request is being downloaded by the recipient specified in the request with the “Bank” status.
[0160] After the request is successfully received, the Bank's K13 application client module is called to process received requests for electronic check issuance. The K13 module displays information about the check issuance request in the user interface and provides the Bank with the option to reject or approve the request.
[0161] Upon receiving the request, the Bank verifies that payment for the check being issued has been received from the payer specified in the electronic check issuance request and compares the details in the Issuer's request (e.g., check denomination, currency, check purchase order amount, payer details) with the details in the Issuer's account statement. If funds for the check purchase have been received in the Issuer's account, the Bank confirms the Issuer's Request through the client application. At the same time, the K13 block for processing received requests for electronic check issuance generates an electronic confirmation of the request and transmits it to the S13 server block for processing and executing applications and requests.
[0162] During the electronic check issuance request confirmation procedure, block S13 retrieves information about the check issuance request being confirmed from the database, performs the necessary checks (including calling block K2 to verify the Bank's account), and, upon successful completion, executes block S11 for issuing electronic checks. This block receives the new check details obtained from the issuance request, including the denomination, currency, and details of the paying bank. Block S11 is described above (see Method for Executing Electronic Check Transfers).
[0163] After the successful completion of the work of block S 11, block S13, during the procedure of confirming the application for the issue of an electronic check, calls the execution of block S5 for the registration and execution of transfers of electronic checks (transfer registration procedure) for the purpose of automatically creating and executing the transfer of the issued The check is transferred from the Issuer's account to the Check Purchaser's account. The S5 block's transfer registration procedure receives the electronic check issuance request data retrieved from the database: the recipient's account number, denomination, check currency, etc.
[0164] After the S5 block transfer registration procedure is completed, the S5 block operation procedure is carried out (in accordance with the above procedure).
[0165] Block S13 transmits the successful result of request processing to the client block of the Bank's K13 application, which records the updated status of the processed request for check issuance, and also, via block S10, to the client application of the sender of the request for check issuance (Issuer) (block S3 for updating data, synchronizing the database of the client and server applications, which updates and displays to the Issuer the updated status of the request and information about the automatic transfer of the check to the buyer).
[0166] Electronic check payment method
[0167] Below is a payment method for electronic checks used when presenting electronic checks to a bank to receive actual cash deposited into the bearer's bank account. This method is designed to ensure the security of the check payment process for both the check bearer and the bank processing the payment.
[0168] The process of presenting an electronic check for payment begins when the user launches the client application. This initializes the client block K2 for authorization in the System. Once completed, the K3 block for updating and synchronizing client and server application data is launched. Successful completion of the K2 and K3 blocks is a prerequisite for proceeding to the K8 block for data entry and submitting electronic check payment requests. Block K8 may be available to different user categories (for example, only legal entities with a status in the System higher than Initial).
[0169] To initialize this block, the System Participant selects the corresponding section in the user interface of the client application.
[0170] Block K8 provides the user with the ability to enter the required initial data for generating an application for payment of an electronic check, such as: the account from which the check will be debited, the denomination of the check, bank details Payment details. Based on the user's input, Block 8 determines the bank that will be the payer for the Participant's electronic check.
[0171] After the required application details are correctly filled in, the K8 unit generates an electronic check payment request as an electronic document certified by the user's ASP. The K8 unit forwards the request to the S6 server unit for registering applications, requests, and invoices for check crediting.
[0172] Block S6 performs the procedure for checking the parameters of the application for payment of an electronic check, the execution of server block S2 is called, during which the necessary checks are carried out for both the sender (including checking the ASP request) and the recipient of the request, performs a check of the correctness of the client's bank details for crediting the payment (including according to the current directory of banks by BIC), sufficiency of funds in the sender's account and other checks necessary for the correct execution of the operation.
[0173] If all checks are successfully completed, the request is registered on the server. Records are added to the database in the "Information on Requests, Requests, and Accounts for Check Crediting" section. A notification about the new request is sent to the recipient (paying bank) via the S10 online notification block.
[0174] Upon logging into the Bank's System or receiving an online notification, the KZ (client and server application data update and synchronization) block of the Bank's client application interacts with the S3 block to download the electronic check payment request from the server. The S3 server block, which updates the client and server application databases and synchronizes them, verifies that the request is being downloaded by the recipient specified in the request, with the "Bank" status.
[0175] After the request is successfully received, the Bank's K14 application client module is called to process received electronic check payment requests. The K14 module displays the electronic check payment request details in the user interface and provides the Bank with the option to reject or approve the request.
[0176] Upon receiving the application, the Bank verifies the accuracy of the application parameters and the availability of the required amount of funds in the Issuer's current account. The application is confirmed by an invoice issued through the System for check deposit. The Bank issues an invoice through the Kb client data entry block, sending invoices for check crediting. During this block, an invoice is generated, the parameters of which are determined based on the check payment request and partially completed by the Bank. The Bank specifies the details of its current account designated for checks presented for payment. The invoice is based on the check payment request number and the bank details of the check bearer for payment.
[0177] After the account details are correctly entered, the Kb unit generates an invoice for check deposit as an electronic document certified by the user's ASP. The Kb unit transmits the invoice to the S6 server unit for registering applications, requests, and invoices for check deposits.
[0178] Block S6 performs the procedure for checking the account parameters for check crediting. Server block S2 is called, during which the necessary checks are performed on both the sender (including the request's ASP verification) and the recipient. If all checks are successful, the invoice is registered on the server. Records are added to the "Information on applications, requests, and invoices for check crediting" section of the database. A message about the new invoice is sent to the recipient via block S10 for sending online notifications.
[0179] •After successful invoice issuance, the client block of Bank K14, which processes received requests for payment of electronic checks, updates the status of the request. To do this, a corresponding notification is sent to the server block S13, which processes and executes requests and queries. During this process, the new status of the request is recorded in the server database and a notification is sent to the sender.
[0180] If the Request cannot be satisfied (the check presenter has failed the required checks), the Bank selects the "Reject Request" option and specifies the reason for the rejection. At this point, Block K14, which processes received requests for electronic check payment, sends a command to Server Block S13, which processes and executes requests (the payment rejection procedure of Block S13 is called). During this procedure, information about the rejected request is retrieved from the database, the necessary checks are performed, and Block S9, which generates digital documentation, is called (the procedure for generating a Notification of Check Rejection). This procedure receives the information received from the check payment request regarding the client, bank, denomination, and currency of the check being paid, as well as the reason for refusal. The document is signed by the Bank's ASP through the execution of the K17 electronic signature block. Block S13 notifies the client of any changes to the status of their submitted request.
[0181] After receiving the specified Check Deposit Account, the Participant makes a bank transfer to the designated designated account in the System. The transfer is executed in accordance with the electronic check transfer method described above.
[0182] Upon receiving the transfer (block K9 for processing received electronic check transfers), the bank verifies that the check bearer details, order number, and other transfer parameters specified in the payment details match the parameters of the confirmed check payment request and initiates the verification procedure for the received electronic check. The electronic check verification procedure is described below.
[0183] Only after receiving a Notification of Check Verification from the Issuer and changing the status of the Verification Request in the System to “confirmed” does the bank pay the check by transferring funds to the Participant’s current account (or, if the Participant is a credit institution, to its correspondent account) and writes off the check.
[0184] The process of writing off an electronic check occurs when the corresponding option is selected in the Bank's application user interface. This triggers the execution of block 18 for writing off electronic checks. Block K18, based on a confirmed verification request, generates an electronic check write-off request containing the verification request number, verifies it with the Bank's ASP, and sends it to server block S14 for writing off electronic checks. Block K18 may additionally include the Bank entering payment order parameters, based on which the actual funds are transferred to the check bearer.
[0185] The S14 server block for writing off electronic checks performs the verification stage, during which information about the confirmed request for check verification is retrieved from the database, and the K2 block is called to verify the account. The bank, upon request, verifies the electronic check being written off. After all checks are successfully completed, block S14 writes off the check, and the corresponding changes are entered into the "Electronic Check Information" section of the database (the electronic check status and other required parameters are changed).
[0186] When writing off an electronic check, block S14 triggers the check write-off operation recording procedure in block S8, which registers electronic check transactions in the Register. The input parameters for calling this procedure are the electronic check number, the account number where the check was written off, and the transaction type ("check write-off (paid)"). This procedure creates a record in the "Electronic Check Movement Register" database section containing the number, date, time of the transaction, amount, currency, check number being written off, transaction type, account number where the check was written off, and the balance on that account.
[0187] After successfully recording the transaction in the Check Movement Register, block S14 updates the status of the check payment request and the verification request (to "check payment completed"). The corresponding notifications are sent to System participants via block S10.
[0188] Method of verification of electronic checks
[0189] The electronic check verification method enables the Bank to verify the authenticity of the check presented for payment and is a mandatory step prior to check payment.
[0190] The verification process begins when the Bank, having received a transfer of an electronic check to a specialized account with information about the check payment request specified in the payment purpose, generates a Request for Verification of the Electronic Check Presented for Payment.
[0191] When the bank selects the "Verification Request" option, block K15 initiates data entry and sends requests for electronic check verification. Block K15 allows the bank to automatically populate the request parameters based on the received transfer. The verification request contains information about the electronic check and the person presenting the check for payment. The completed request in the form of an electronic document is certified by the bank's ASP by block K15 and sent to the server block S6 for registering applications, requests, and invoices for crediting checks.
[0192] Block S6 performs the procedure for checking the parameters of the request for verification of the electronic check, which includes an automatic check of the details of the electronic check, during which the ASP of the check is checked (an algorithm for checking the electronic digital signature is performed using the Issuer's public key and the record of the check in the database, which guarantees the immutability of all details of the electronic check), the current state of the electronic check, the account of the request sender (the execution of server block S2 is called).
[0193] If all checks are successful, block S6 determines the Issuer's registration number and saves the request on the server. Records are entered into the database in the "Information on applications, requests, and invoices for check deposits" section. A message about the new request is sent to the recipient (Issuer) via block S10 for sending online notifications.
[0194] Upon logging into the Issuer System or receiving an online notification, the Issuer's client application's KZ (client and server application data update and synchronization) block downloads an electronic receipt verification request from the server via interaction with the S3 block. The S3 server block, which updates the client and server application databases and synchronizes them, verifies that the request is being downloaded by the recipient specified in the request, with the "Issuer" status.
[0195] Upon successful receipt of the request, the Issuer's K12 client application is called to process the received requests for electronic check verification. K12 displays information about the electronic check verification request in the user interface and provides the Issuer with the option to reject or approve the request.
[0196] The Issuer, upon receiving a Verification Request, tracks the history of the electronic check using the Check Movement Register, verifies the correctness of the check details (the System provides the ability to view the electronic check in graphical form), and the accuracy of the information about the check bearer. If all checks are completed successfully, the Issuer confirms the Check Verification Request.
[0197] Block K12, which processes received electronic check payment requests, sends a request to server block S13, which processes and executes requests (the procedure for confirming a check verification request in block S13 is called). During this procedure, information about the request being confirmed is retrieved from the database, the necessary checks are performed, and block S9, which generates a digital documentation (the procedure for generating an Electronic Check Verification Notification), is called. The electronic check information received from the verification request is fed to this procedure. The document is signed by block K17, which electronically signs digital documentation, through the Issuer's ASP. Block S13 notifies the Bank of any changes to the status of the request it submitted.
[0198] If the Request cannot be confirmed, the Issuer selects the "Reject Request" option and specifies the reason for the rejection. The request is rejected in the same way as a bank rejects a check payment request.
Claims
CLAUSES OF THE INVENTION 1. An electronic system for settlement by electronic checks, containing at least one server computer device for processing and storing data, a server application included in its composition, and client computer devices for processing data, including software and hardware client modules that ensure the interaction of client computer devices with the server, with the provision of the possibility of connecting client computer devices with the server computer device via Internet communication channels and the possibility of protecting communication channels by software and hardware of the server and client modules using encryption and an electronic digital signature, characterized in that the client and server applications contain, at least, user authorization blocks in the system, interconnected with each other, a block for updating and synchronizing data of the client and server applications,and also contain a block for entering parameters for executing transfers and storing information about payments of the client application, connected by software and hardware with blocks for checking parameters of transfers of electronic checks, connected with the block for authorization and verification of user parameters and the block for registering and executing transfers of electronic checks of the server application, connected by feedback channels with blocks for managing electronic checks, crediting a commission check and sending notifications to the user in real time, connected with the block for updating and synchronizing data of the client application, as well as the inclusion in the client application of an electronic signature block, connected by software and hardware with the block for generating and storing digital documentation of the server application, connected with the side of registering and executing transfers of electronic checks,wherein the control unit for electronic checks of the server application is implemented in a software and hardware manner via feedback channels with interconnected units for registering operations with electronic checks in the register and issuing electronic checks, connected to the electronic check signature unit.
2. An electronic system according to paragraph 1, characterized in that the blocks of the client application are grouped into modules by categories corresponding to the status of the user determined by the authorization block of the client and server applications, with the provision of the ability to pre-set a set of check circulation parameters for each category.
3. The electronic system according to paragraph 2, characterized in that the blocks of the client application are implemented as grouped modules in three categories, including an initial level, with a minimum set of parameters for handling checks, a standard level, with the ability to present checks for payment to the bank and select the paying bank for one's checks, and an extended level, with the ability to generate an additional set of parameters for handling checks for the work of the Issuer, Partner banks and Dealers (Brokers) of the system.
4. An electronic system for settlement by electronic checks according to paragraph 1 or 2, characterized in that the client device includes a separate client application with its own user interface and / or a client application in the form of an embedded module in a standard Internet resource browser with its own user interface displayed in a web browser and / or a client application implemented in the form of a thin client based on a web browser with the ability to transfer information processing blocks and generate a user interface to the server.
5. An electronic system for settlement by electronic checks according to paragraph 1 or 2, or 4, characterized in that the client device containing the user application in thin client mode is designed to provide the ability to process data input in the user interface of the web browser, electronic signature of digital documentation, data encryption, data transmission to the server, data reception from the server, decryption, and output to the user interface of the web browser.
6. A method for transferring electronic checks in an electronic check settlement system comprising a server computer device for processing and storing data, an information display device and a server application included therein, and client computer processing devices containing an information display device and client applications connected via wireless and / or internet communication channels, characterized in that it includes the following sequential stages: authorization of a participant in the system; receipt of account data; input of electronic check transfer parameters; verification of electronic check parameters; registration of a request for transfer of an electronic check; execution of an operation of exchanging the sender's check into several checks, including a transfer check, a commission check, a balance check; presentation of checks for payment, payment and issuance of new checks;crediting the commission electronic check to the system operator's account and / or to the Dealer's (broker's) account when transferring electronic checks of the standard category of users, as well as the bank through the dealer (broker); crediting the electronic check to the participant's account; completing the transfer, accompanied by the creation and signing of electronic documents, informing the participants about the completion of the transfer.
7. The method according to paragraph 6, characterized in that it additionally includes the operation of exchanging the recipient’s checks for one check, carried out after the stage of crediting the electronic check to the participant’s account, including the presentation of checks for payment, including through collection, payment and the issuance of new checks.
8. The method according to paragraph 6, characterized in that the authorization of a participant in the system includes the launch by the user of the client application, during which the client authorization block is initialized and the entry of credentials and their transmission through the K4 block of interaction with the server, via the Internet over a secure communication channel, to the server block S2 of authorization and verification of user parameters, where the participant's account, the availability and correctness of the electronic key storage are verified, with the possibility of generating an analogue of a handwritten signature (AHS) of requests and electronic documents, confirming the status and corresponding rights of the participant, synchronizing the data of the client and server applications, with the possibility of outputting to the terminal of the client and server applications information on the current state of the participant's accounting accounts, received transfers,accounts for crediting checks and initialize the block for entering parameters for executing transfers in the client application.
9. The method according to paragraph 8, characterized in that the entry and verification of the account, and the granting of rights corresponding to the account category are carried out during the initialization of the client authorization block.
10. The method according to paragraph 6, characterized in that after successful completion of the authorization stage, the server application of the information update module displays at least the accounting information in the user interface, including information about all of the participant’s accounting accounts: number, name of the accounting account, active balance on the account, number of the electronic check linked to the account, data of the bank associated with the account, etc.
11. The method according to paragraph 6, characterized in that the input of transfer parameters and the execution of the transfer are carried out in stages during the initialization of the block 5 for inputting parameters, executing transfers, which is carried out by forced selection of the corresponding section in the user interface of the client application; the required initial data for the transfer of an electronic check, preset in the system for each category of participants, are entered; the transfer is generated on the basis of the received invoice for crediting checks or an application of a certain type.
12. The method according to paragraph 6, characterized in that the input of the transfer parameters includes automatic validation performed during the process of inputting the parameters, with the simultaneous generation of an error message and its transmission to the client application and the participant’s computer device.
13. The method according to paragraph 6, characterized in that it includes automatic calculation of the amount of the commission charged for the transfer, in the process of receiving by the application data on the amount of the transfer, which is carried out by a software and hardware method by the server application with the simultaneous generation of a message and its transmission to the client application and the client computer device.
14. The method according to paragraph 13, characterized in that the commission calculation is performed by the module based on local application data stored in RAM and / or loaded, for example, during the account data acquisition stage and / or based on the commission rate preset in the server computer device's memory. The module is updated and transmitted from the server via a separate request from the client application, and generates a report on the commission amount charged for the transfer and the amount to be debited (or the amount to be received, depending on the parameter being filled in), which is transmitted to the K5 unit of the client application.
15. The method according to paragraph 6, characterized in that it additionally includes a stage of preliminary verification of the parameters of the transfer, during which, using block K5, an electronic request for data verification is generated and transmitted to server block S4 for verification of parameters of transfers of electronic checks, block S4 during the checks determines whether it is possible to carry out a transfer with the specified parameters and, in the event of receiving a positive response, causes the execution of server block S2, during which the necessary checks are carried out on the authenticity of the sender, at least a check of the ASP of the request, and the recipient of the transfer, at least a check of the availability of the recipient's account, and performs extraction from the DB of data on the electronic check available in the account of the sender of the transfer, a comparison of the denomination of the check with the amount to be written off and other checks provided for by the features of a specific implementation of the System.
16. The method according to paragraph 15, characterized in that a separate amount in the account is additionally blocked, and the amount to be written off is compared with the amount of the available active balance.
17. The method according to paragraph .15, characterized in that at the stage of registering a request for a transfer and recording it in the system database, the commission amount is calculated and recorded.
18. The method according to paragraph 15, characterized in that at the stage of sending and registering the request for the execution of the transfer, the digital documentation generation and storage unit S9 is additionally initialized, ensuring the possibility of generating an electronic document in a format suitable for printing on paper, which contains all the details of the application for the transfer of an electronic check and is confirmed by the Participant's ASP through the client unit of the electronic signature of the digital documentation (K 17).
19. The method according to paragraph 18, characterized in that the electronic document in a format suitable for printing on paper is transferred to the database on the server and stored together with the ASP and other information in the application database. 20 The method according to paragraph 4, characterized in that at the stage of executing the transfer, the S5 block for registering and executing transfers of electronic checks receives from the System database data on the electronic check in the account of the sender of the transfer and the amount of the commission and compares the denomination of the check balance in the account of the sender with the transfer amount; if the compared values coincide, the electronic check is transferred from the sender's account to the account of the recipient.
21. The method according to claim 20, characterized in that, in order to transfer a check, block S5 initiates the execution of server block S7 for managing electronic checks, wherein data on at least the number of the electronic check, the number of the account of the sender of the transfer, the number of the account of the recipient of the transfer are transmitted to the input, and when confirming the execution of the transfer, block S7 changes the information in the DB, wherein information on the check is deleted from the account of the sender of the transfer, data on the number of the new check of the balance is entered into the record of the account of the recipient and information on the check holder is changed, at the same time, information is transmitted to block S8 and the registration by block S8 of operations with electronic checks in the Register is carried out and then information on the successful completion of the transfer is generated and transmitted to block S7.
22. The method according to paragraph 20, characterized in that the electronic check is first transmitted To the Operator, and the Operator transfers the check to the recipient of the transfer. 23 The method according to paragraph 20, characterized in that, when requesting a transfer, the recipient is not given the entire denomination of the check, block S5 calls the procedure for exchanging the electronic check of block S7 of the electronic check management, whereby, at the input of this procedure, block S5 transmits: the number of the electronic check, the denomination of which is the balance on the sender's account, the denominations of the electronic checks for which the exchange must be made, equal to the amount of the transfer and the amount of the commission charged for the transfer.
24. Method according to paragraph23 characterized in that, when exchanging an electronic check, the S7 unit transfers the sender's electronic check to the System Operator, wherein the Operator presents the received electronic check for payment to the Payer Bank, and the presentation of the electronic check for payment is carried out by performing the procedure for presenting a check for payment of the S7 electronic check management unit, to the input of which at least the following are transmitted: the number of the electronic check, information about the bank, the number of the account from which the check is presented, and after the successful completion of the procedure for presenting a check for payment, the check write-off procedure is carried out by calling the S7 electronic check management unit, to the input of which the number of the electronic check is transmitted, the information about the paid check is changed and the registration and recording of the operation with electronic checks in the register is carried out by initializing the S8 unit and the operation of writing off the electronic check is completed by transmitting a control signal to the S7 unit.
25. The method according to paragraph 24, characterized in that block S7, within the framework of the procedure for exchanging an electronic check, sequentially calls for the execution of block S11 for issuing electronic checks for each of the said checks, wherein data on the details of the new check are transmitted to the input of this block, which, at least, include: the denomination, the currency of the check, information about the Payer Bank, with the provision of the possibility for the Operator to acquire from the Issuer new checks for the amount of the transfer and / or checks for the amount of the commission and / or checks for the balance of the required denominations.
26. The method according to paragraph 25, characterized in that when executing block S11, the necessary information for specifying the check details is extracted from the system database, execution of block S12 for signing electronic checks is called, and a record of the new electronic check is created in the database.
27. The method according to paragraph 24, characterized in that when issuing an electronic check, block S11 causes the execution of the procedure for recording the check issuance operation of block S8 for registering operations with electronic checks in the Register, and after the operation is successfully recorded in the Register, the work of block S11 for issuing electronic checks for the check is completed and the issued checks are transferred to the Operator in accordance with the procedure for transferring an electronic check of block S7 for managing electronic checks, and the Operator transfers the balance check to the sender of the transfer.
28. The method according to paragraph 24, characterized in that within the framework of the procedure for carrying out the operation of block S5, the operator transfers a check for the amount of the transfer to the recipient's current account; wherein block S5 retrieves information about the balance on the recipient's current account and the account settings, wherein if there is a balance on the recipient's current account of the check and / or a bank other than the paying bank for the transfer check is specified in the account parameters, block S5 calls the procedure for exchanging and / or combining electronic checks of block S7 of the electronic check management, wherein the electronic checks from the recipient's account are transferred to the account of the System Operator, and the Operator presents the received electronic checks (check) for payment to the bank declared as the payer for the "balance check" of the transfer recipient, or to the Bank specified in the account settings, if there is no balance and for the electronic check presented for payment to the paying bank, the procedure for writing off the check of block S7 of the electronic check management is called,Upon completion of which the Operator acquires from the Issuer a new check, the denomination of which will be the sum of the denominations of the checks presented for exchange and / or equal to the denomination of the check presented for exchange for a check of another paying bank; block S7, as part of the procedure for exchanging (combining) electronic checks, calls the execution of block S11 for issuing electronic checks and determines that the payer for the new check will be the bank that executed the payment for the checks presented for exchange; the Issuer transfers the issued check to the System Operator, and the Operator transfers the new check to the recipient of the transfer; after successful completion of these actions, the procedure for exchanging and / or combining electronic checks is completed.
29. The method according to any of paragraphs 24, 25, 26, 27, or 28, characterized in that, when performing the procedure for conducting the operation of block S5 for registering and transferring electronic checks, block S9 for generating and storing digital documentation is executed, and digital reporting documentation is generated. This ensures the possibility of signing it by the ASP Participants and subsequent printing.
30. The method according to paragraph 29, characterized in that when executing block S9, a digital image of the Electronic Receipt Acceptance Certificate, the Certificate of Services Rendered, and the Invoice is generated, which are transmitted to the input of block K17 for the electronic signature of digital documentation, ensuring the possibility of signing the ASP by the relevant parties.
31. The method according to paragraph 30, characterized in that after the successful execution of the transfer and the generation of the required documentation, block S5 initiates the execution of block S10 for sending online notifications; information about the recipient of the transfer, the type of the message being sent is transmitted to the input of S10, while S 10 causes the execution of the client block K3 for updating, synchronizing the data of the client and server applications, while block S5 simultaneously transmits information to block K5, which stores information about the payments of the sender of the transfer.
32. A method for issuing electronic checks in an electronic check settlement system comprising a server computer device for processing and storing data, an information display device and a server application included therein, and client computer processing devices containing an information display device and client applications connected via wireless and / or internet communication channels, characterized in that it includes at least the mandatory stages of generating a request for the issuance of a check by the issuer, checking by the bank the receipt of funds to the issuer's settlement account, which are security for this check, for compliance with the parameters of the request and confirmation by the bank of the issuance of the electronic check, with the ability to generate legally significant documents and reflect transactions in the check movement register generated and stored on the system server.
33. The method according to paragraph 32, characterized in that it includes the launch by the user with the Issuer account of the client application on the client computer device and the authorization of the client in the system, wherein, sequentially, upon entering the account data, the client blocks K2 of authorization in the System and KZ of updating, synchronizing the data of the client and server applications are initialized, which, through communication channels with the server, transmit the account data to the corresponding server blocks S1 of authorization and S2 of the data synchronization block, where a comparison of the entered credentials is carried out with the data of the server database,and upon completion of the account data processing, a control signal is transmitted to blocks K2 and K3 to block or allow account access to system applications and the account status data is updated with the ability to display the result on the client information display device; upon confirmation of authorization, block K3 transmits the account data to block K11 for entering data and sending requests for issuing electronic checks, which generates a client application with an interface corresponding to the check issuance operation and enters the data of the request for issuing an electronic check, on the basis of which block K11 generates a request for issuing a check in the form of an electronic document certified by the Issuer's ASP and transmits the request to server block S6 for registering applications for crediting checks, which performs the procedure for checking the parameters of the request for issuing a check, generates an authorization request and initializes the execution of server block S2,during which the necessary checks of the sender's accounts (including checking the ASP request) and the recipient of the request are carried out, and if the check of all data is positive, S2 generates a confirmation message about passing the check on S6 and the request is registered on the server, and the request data is entered into the DB, while the Paying Bank for the check being issued is sent a message about the presence of a new request to the bank's KZ block via the S10 online notification sending block, and the bank's KZ block, by sending a request with the Bank's identification data to S3, loads the data of the request for the issue of an electronic check after confirmation of the Bank's authorization in the system carried out by blocks S2 and S3 on the basis of the request, and transmits the data about the request to the Bank's client block K13 for processing received requests for the issue of electronic checks, with the ability to display information about the request for the issue of a check in the user interface and make a choice to accept or reject the request,wherein the Bank's K13 block checks for the presence of payment for the check being issued, received from the payer specified in the request for the issuance of an electronic check, and compares the data in the Issuer's request with the data from the Issuer's account statement received from S3, and in the event of receipt of funds for the purchase of the check on the Issuer's account, the Bank's K13 block generates an electronic confirmation of the request and transfers it to the S13 server block for processing and executing applications, which extracts information about the confirmed request for the issuance of a check from the DB, performs the necessary checks of the Bank's account and, after their successful completion, transfers the data about the issuance of the check to the S 11 block for issuing electronic checks, which initializes the S5 block for registering and executing transfers of electronic checks, which generates an electronic check and transfers the issued check from the Issuer's account to the account of the Buyer of the check,with the formation of a report on the execution of the operation and its forwarding to block S11 with its subsequent transmission to S10 via S13 with the possibility of forming a message about the completed operation to the Bank's and the Issuer's K3 blocks, wherein block S13 transmits data on the issuance of the check to the Bank's K13 block, which records the updated status of the processed request for the issuance of the check, and block S10 updates the Issuer's account data, with the possibility of simultaneously displaying on the Issuer's information display device the updated status of the request and information on the automatic transfer of the check to the buyer.
34. The method according to paragraph 33, characterized in that the parameters of the request data for issuing an electronic check include, at least, data on the check details, which include: denomination, check currency, information on the Payer Bank.
35. A method for paying for electronic checks in an electronic check settlement system containing a server computer device for processing and storing data, an information display device and a server application included in its composition, client computer processing devices containing an information display device and client applications connected via wireless and / or Internet communication channels, characterized in that it includes the launch of the client application by the user, during which the client block K2 of authorization in the System is initialized, after the execution of which the block K3 of updating, synchronizing the data of the client and server applications is launched, upon successful execution of which the block 8 of data input is initialized, sending applications for payment of electronic checks and entering the required initial data for the formation of an application for payment of an electronic check, wherein the block K8 determines the bank that is the payer for the electronic check of the Participant on the basis of the input data,generates an application for payment of an electronic check in the form of an electronic document certified by the user's ASP and transmits the application to the server block S6 for registration of applications, requests, and invoices for crediting checks, which, through block S2, verifies the data by comparing them with the data stored in the system's DB, and in case of a positive result of the verification, the application is registered on the server, and the records are entered into the DB, while the Recipient (Payer Bank) is sent a message about the presence of a new application through block S 10 for sending online notifications; the Bank, through interaction with block S3, downloads the application for payment of the electronic check from the server, while the server block S3 for updating data, synchronizing the DB of the client and server applications performs the verification,that the request has been uploaded by the recipient specified in the request with the "Bank" status; upon successful receipt of the request, a call is made to the client block of the Bank's K 14 application for processing received applications for payment of electronic checks, which generates and displays in the user interface information about the application for payment of the electronic check and provides the Bank with the option to reject or confirm the application; the Bank checks the correctness of the Application parameters, the availability of the required amount of funds in the Issuer's current account and, in case of a successful check, generates, through the System, an invoice for crediting the check by executing the client block Kb for data entry, sending invoices for crediting checks, which generates an invoice for crediting the check in the form of an electronic document certified by the user's ASP, and transfers the invoice to the server block S6 for registering applications, requests,accounts for crediting checks; block S6 performs the procedure for checking the account parameters for crediting a check via server block S2 and registers the account on the server in the system database if the checks are successful, and generates a message to the Recipient via block S10 for sending online notifications about the existence of a new account; upon receiving the system message, the client block of the Bank's application K 14 for processing received applications for payment of electronic checks updates the status of the application; the participant, having received the specified Account for crediting a check, makes a transfer to the bank to the specified current account in the System, while upon receiving the transfer via block K9 for processing received transfers of electronic checks, a check is made of the payment details and other parameters of the transfer, comparing them with the parameters of the confirmed application for payment of the check stored in the database,and the verification procedure for the received electronic check is initiated; after receiving a check verification notification from the Issuer and changing the status of the Verification Request in the System to "confirmed", the bank pays the check by transferring funds to the Participant's current account and writes off the check.
36. The method according to paragraph 35, characterized in that, if the Application cannot be satisfied and / or the check bearer has not passed the necessary checks, the Bank selects the “Reject Application” option and indicates the reason for the refusal, wherein block K 14 for processing received applications for payment of electronic checks sends a command to server block S13 for processing and executing applications, requests and calls the procedure for refusing payment of block S13, during the execution of this procedure, information about the rejected application is extracted from the DB, the necessary checks are performed and block S9 for generating digital documentation is called, ensuring the possibility of generating a Notification of refusal to pay the check and, by executing block K 17, an electronic signature of the digital documentation of the ASP Bank is carried out, wherein block S 13 notifies the client about a change in the status of the application sent by him.
37. The method according to paragraph 35, 36, characterized in that the process of writing off an electronic check is carried out by selecting the corresponding option in the user interface of the Bank's application, while calling the execution of block K18 for writing off electronic checks, which, on the basis of a confirmed verification request, generates an electronic request for writing off an electronic check containing the verification request number, certifies it with the Bank's ASP and sends it to the server block S14 for writing off electronic checks, which, after performing the verification stage, during which information about the confirmed request for verification of the check is extracted from the DB, calls block K2 to check the Bank's account, the ASP request, and also verifies the electronic check being written off, writes off the check, and the corresponding changes are entered into the DB and, through block S14, records and registers the write-off operation in the register, after which block S 14 updates the status of the request for payment of the check,verification request (for “check payment completed”) and the corresponding notifications are sent to the System participants via block S 10.
38. A method for verifying electronic checks in an electronic check settlement system comprising a server computer device for processing and storing data, an information display device and a server application included therein, and client computer processing devices containing an information display device and client applications connected via wireless and / or Internet communication channels, characterized in that it is launched upon receipt by the Bank of an electronic check transfer to a specialized account with information about the check payment request indicated in the payment purpose, while a Request for Verification of the Electronic Check presented for payment is generated, while initiating the execution of block K15 for data entry, sending requests for verification of electronic checks; block K15 provides the Bank with the ability to automatically fill in the request parameters based on the received transfer,In this case, the request in the form of an electronic document is certified by the K15 block of the bank's ASP and sent to the server block S6 for registering applications, requests, and invoices for crediting checks, which performs the procedure for checking the parameters of the request for verification of an electronic check, and in the case of successful completion of all checks, determines the registration number of the Issuer and saves the request on the server, in the system's DB, while a message about the presence of a new request is sent to the recipient (Issuer) via the S10 block of sending online notifications; the Issuer, through interaction with the S3 block, downloads the request for verification of an electronic check from the server, while the server block S3 for updating data, synchronizing the DB of the client and server applications checks that the request is being downloaded by the recipient specified in the request with the "Issuer" status, and after successful receipt of the request, a call is made to the client block of the Issuer's application K12 for processing the received requests for verification of electronic checks,which displays information about the electronic check verification request in the user interface and provides the Issuer with the option to reject or confirm the request. If all checks are successful, the Issuer confirms the Check Verification Request. Block K12 for processing received applications for payment of electronic checks sends a request to the server block S13 for processing and executing applications and requests and calls the procedure for confirming the check verification request of block S13. During the execution of this procedure, information about the confirmed request is retrieved from the database, the necessary checks are performed and block S9 for generating digital documentation is called, ensuring the possibility of generating a Notification of Electronic Check Verification. The document is signed by the Issuer's ASP through the execution of block K 17 for the electronic signature of digital documentation. Block S 13 notifies the Bank of a change in the status of the application sent by it.
