SAFE MOBILE PAYMENT PLATFORM

Abstract

The system which provides formation of fiscal data and its inspection for the payment methods wherein it comprises; Terminal (20) which is composed of devices used by the taxpayer/job site which will form the fiscal data related to receiving the payment and processing, and which determines the payment method, Fiscal module (27) which is present on the terminal (20) and which provides formation of fiscal information, carrying out of certificate and signature management, Basic sales application (23) which is present on the terminal (20) and which defines the product/division information so as to implement the sales transaction of the job site, and which forms the information related to the sales by using the data which it had defined during the sale, Terminal (20) software module in which all terminal software modules (24) are located, Authorization/approval hosts (30) which meets and feeds back the replies of the approval requests which the establishment giving the service must receive from its systems for payment transactions and added value services of the terminal (20), Central safe mobile payment platform (10) which provides fiscal certificate management related to the terminal (20) on which the sales has been performed, Back office software module (11) which is located on the safe mobile payment platform (10) and which provides face up for making customer and terminals (20) definitions to the system, which offers operator screens for monitoring the system and which provides preparation of awaited reports by receiving report demands, Fiscal data transmission module (12) which is located on the safe mobile payment platform (10) and which provides transmission of fiscal data to the Income Authority Official Corporation (40) with regulation approved content and timing via special integrators (41), Certificate management module (13) which is located on the safe mobile payment platform (10) and which performs certificate management belonging to terminals (20), Online message processing module (14) which is located on the safe mobile payment platform (10) and which meets the transactions starting from the terminal (20) to be done real time/online, which transmits to the respective sides and which receives their replies, which feeds back the replies to the terminal (20) and which records the information required for the transaction on server side.

Claims

1. A system which provides formation of fiscal data and inspection for the payment methods, the system comprising: a terminal which is composed of devices used by a taxpayer/job site which will form fiscal data related to receiving payment and processing, and which determines a payment method: a fiscal module which is present on the terminal and which provides formation of fiscal information, carrying out of certificate and signature management; a basic sales application which is present on the terminal and which defines product/division information so as to implement sales transaction of the job site, and which forms information related to the sales by using the data which it had defined during the sale; a terminal software module in which all terminal software modules are located; a crypto transactions module which carries out cryptographic functions such as receiving certificate/key, keeping, using, signing, coding, and verification; a workflow module which provides management of hierarchically all steps in sequence from the start to the conclusion of the sale; a user interface module which forms the entire screens of information, data input which the end user will see on the terminal; a host protocol module in which messaging protocols of authorization hosts are realized; authorization/approval hosts which meets and feeds back the replies of the approval requests which the establishment giving the service must receive from its systems for payment transactions and added value services of the terminal; a central safe mobile payment platform which provides fiscal certificate management related to the terminal on which the sales has been performed; a back office software module which is located on the safe mobile payment platform and which provides face up for making customer and terminals definitions to the system, which offers operator screens for monitoring the system and which provides preparation of awaited reports by receiving report demands; a fiscal data transmission module which is located on the safe mobile payment platform and which provides transmission of fiscal data to the income authority official corporation with regulation approved content and timing via special integrators; a certificate management module which is located on the safe mobile payment platform and which performs certificate management belonging to terminals, signature inspections and cryptography management to be performed by using certificates in transactions messages; an online message processing module which is located on the safe mobile payment platform and which meets the transactions starting from the terminal to be done real time/online, which transmits to the respective sides and which receives their replies, which feeds back the replies to the terminal and which records the information required for the transaction on server side.

2. The system according to claim 1, comprising the payment application which is prepared for the establishments that intervene with the payment or for the banks that accept payment by card, which sends the information about the payment transaction to the respective establishment and receives their approval, and which is located in the fiscal module.

3. The system according to claim 1, comprising the VAS application which meets special requirements for various lines of business, and which does not form financial/fiscal data in its own structure.

4. The system according to claim 1, comprising the hardware abstraction module which provides unchangeableness of the software at the upper level for different hardware, and which comprises the suitable software related to the differences of hardware.

5. The system according to claim 1, comprising the lower level layer composed of low level software modules, and which offer the infrastructure that the upper level applications such as operating system, device drivers and software libraries will use.

6. The system according to claim 1, comprising the hardware layer t26)-which forms the physical hardware of the user as terminal.

7. The system according to claim 1, comprising the payment host which communicates with the payment application and which is the server module of the parties that offer payment services.

8. The system according to claim 1, comprising the VAS host which communicates with VAS application and which is the server module of the parties that offer value added services.

9. A method which provides formation and inspection of fiscal data for the payment methods, comprising the process steps of: defining a job site which will use a safe mobile payment platform via a back office software module; implementing prerequisites by a certificate management module that are required for the operation of certificate production process for terminal/terminals that the job site will use, and for set-up of software modules that will work on the terminal; setting-up fiscal module and basic sales application which will work on the terminal; completing technical preliminary preparations that are required for safely inclusion of the fiscal module and basic sales application to the system, and for enabling sales transaction by using verification methods that have been determined at the certificate management module; configuring the fiscal module and the basic sales application; selecting products/amounts in tax segments in the fiscal module to do the sales transaction, and following formation of the fiscal activity implementation of the payment by the methods supported by the system; transmitting the fiscal data by the terminal software module momentarily to the safe mobile payment platform in routine intervals determined by the regulation or in line with the momentary requests of the regulator; transmitting the fiscal data from the safe mobile payment platform to the an income authority official corporation.

Description

THE FIGURES WHICH WILL AID FOR BETTER UNDERSTANDING OF THE INVENTION

[0027] FIG. 1 is the overall view of the system of the invention.

[0028] The drawings must certainly be scaled and details which are not required to understand the present invention can be neglected. Other than this, elements which are substantially identical, or which have at least substantially identical functions are designated with the same numbers.

EXPLANATION OF PART REFERENCES

[0029] 10. Safe mobile payment platform [0030] 11. Back office module [0031] 12. Fiscal data transmission module [0032] 13. Certificate management module [0033] 14. Online message processing module [0034] 20. Terminal [0035] 21. Payment applications [0036] 22. VAS applications [0037] 23. Basic sales applications [0038] 24. Terminal software module [0039] 24.1 Crypto transactions module [0040] 24.2 Workflow module [0041] 24.3 User interface module [0042] 24.4 Hardware abstraction module [0043] 24.5 Host protocol module [0044] 25. Lower level layer [0045] 26. Hardware layer [0046] 27. Fiscal module [0047] 30. Authorization hosts (approval hosts) [0048] 31. Payment host [0049] 32. VAS host [0050] 40. income Authority Official Corporation [0051] 41. Private integrator

DETAILED DESCRIPTION OF THE INVENTION

[0052] In this detailed description, preferred configurations of the invention are described aimed at only better understanding of the subject and without forming any limiting effects.

[0053] In the system and method of the invention, sales is being performed via terminal (20) and fiscal certificate management related to the terminal (20) on which sales has been performed is being performed on the application in the servers of central safe payment platform (10).

[0054] Terminal (20) is all kinds of devices such as telephone, tablet, computer, eft - pos which are used by the taxpayer (job site) who will receive the payment and will form the fiscal data related to the transaction. In other words, terminals (20) are utterly different pool of terminals far away from the safe mobile payment platform (10), working on hardware in various job sites. Payment method is being determined at the terminal (20), Payment method is a system solution which provides technical infrastructure to the payment of independent (Cash, actual or virtual payment with card, meal cheque, social help cheque, etc.) procurement of goods or services, which produces fiscal data related to the payment in a suitable manner to fiscal legislation, which transmits and stores it compatible with the regulation.

[0055] Fiscal module (27) located at the terminal (20) provides formation of fiscal information and performing certificate and signature management. According to the payment method determined at the terminal (20) authorization/approval is being received from the authorization hosts (30) which are related to payment applications (21) or VAS applications (22) that are located at the fiscal module (27). Payment application (21) is the terminal (20) application that sends the information about the payment transaction which is prepared for the establishment that is intervening with the payment or banks that accept (acquire) the payment with card to the respective establishment and receiving their approval, It is necessary to receive authorization for all transactions except for cash payments. Payment acceptance is being received from the bank for the card, from the respective meal card companies for the meal card, from the bank for the debit card, and from respective companies for the transportation card. Approval/authorization are being received from için l5 the respective payment host (31) for payment application (21), and from the VAS host (31) for the VAS application (22). (VAS: Value Added Services). VAS applications (22) are applications that meet the special requirements for various lines of business but that do not form financial I fiscal data in their own structure. (For example, a parking lot management application provides parking lot establishment to carry out their work by managing the information such as license plate number, parking time, subscription, reduction, exit time, parking location/unit, registration number of incumbent employee and kind of payment of parked vehicles; and a complete solution is provided at the same terminal (20) which has been provided with both work flow, and financial activity (payment) and also fiscal data management by means of the other modules on the terminal (20).)

[0056] The basic sales application (23) located at the terminal (20) is the user application module which defines the product/division information for implementing the sales transaction of the job site, and which forms the information related to the sales (such as which product, in which quantity, in which amount from which division is being sold) by using the data that it has defined during the sale.

[0057] Terminal software module (24) is the collective name for all terminal software modules developed to implement the invention.

[0058] Crypto transactions module (24.1) is the module which carries out cryptographic functions such as acquiring certificate I key, storing, using, signing, coding, and verification.

[0059] Workflow module (24.2) is the flow module which provides hierarchically the management of all steps in sequence from the start of the sales until the end of it. It makes decisions such as proceeding to the next stage or cutting off the transaction by requesting the respective module for the transaction whose turn has come and collecting result data and evaluating them.

[0060] User interface module (24.3) is the visual software layer for all screens such as information, data entry which the end user (job site and consumer) will see on the terminal (20)

[0061] Hardware abstraction module (24.4) is the intermediate layer software which provides unchangeableness of the software at the upper level for different hardware, and which comprises the suitable software related to the differences of hardware.

[0062] Host protocol module (24.5) is the software layer on which messaging protocols of the authorization hosts (30) are being realized.

[0063] Lower level layer (25) is low level software modules which offer the infrastructure that the upper level applications such as operating system, device drivers and software libraries will use.

[0064] Hardware layer (26) is the physical hardware of the user as the terminal (20).

[0065] Authorization hosts (approval hosts) (30) are server systems which meet approval requests that are required to be received from the systems of the respective establishment for the payment transactions and value added services of the terminal (20), and which feeds back the replies of the same.

[0066] Payment host (31) is the server module of the systems belonging to the sides that give payment services. And the VAS host (32) is the server module of the systems belonging to the sides that give value added services.

[0067] Fiscal certificate management related to the terminal (20) at which sales has been made is being done by the central safe mobile payment platform (10). In the back office software module (11) which is located at the safe mobile payment platform (10), face up is being provided for carrying out definitions of customer and terminals (20) to the system; operator screens are being offered for monitoring the system; and preparation of awaited reports is being provided by receiving report demands. That is to say, back office software module (11) is the module which comprises all components of the integration of the platform that are not real time, user screens on the server side.

[0068] In the fiscal data transmission module (12) located at the safe mobile payment platform (10) transmission of the fiscal data with regulation defined content and with timing to the Income Authority Official Corporation (40) via special integrators (41). Income Authority Official

[0069] Corporation (40) is the public systems that fiscal data must reach as per the requirements of the regulation. Presidency of Income Authority can be given as an example to the Income Authority Official Corporation (40). And the special integrator (41) is e-document system equity houses whose activity rules and liabilities have been determined by public regulation.

[0070] And in the certificate management module (13) which is located in the safe mobile payment platform (10) certificate management belonging to the terminals (20), signature checks to be done by using certificates in the transaction messages and cryptography management are being carried out. Also, in the certificate management module (13) certificate acquiring and utilization works such as transmission of fiscal data which the system is in need of, signing, verification, message coding are being carried out too.

[0071] The online message processing module (14) located at the safe mobile payment platform (10) is the software module which meets the transactions to be done real time/online starting from the terminal (20), transmits to the related parties and receives their replies, feeds back the replies to the terminal (20) and records the information required for the transaction on the server side,

[0072] The process steps implemented by the system of the invention are the following; [0073] defining the job site which will use the safe mobile payment platform (10) via back office software module (11), [0074] implementing prerequisites by the certificate management module (13) that are required for the operation of certificate production process for the terminal/terminals (20) that the job site will use, and for the set-up of software modules that will work on the terminal (20) (version definition, user and code definitions, single use verification definitions, etc.), [0075] setting-up fiscal module (27) and basic sales application (23) which will work on the terminal (20), [0076] completing technical preliminary preparations that are required for safely inclusion of fiscal module (27) and basic sales application (23) to the system, and for enabling sales transaction by using the verification methods that have been determined at the certificate management module (13), [0077] configurating the fiscal module (27) and the basic sales application (23), (cashier/user definitions, tax groups' definitions, product definitions, etc, are being implemented at this stage.) [0078] selecting products/amounts in tax segments in the fiscal module (27) to do the sales transaction, and following formation of the fiscal activity implementation of the payment by the methods supported by the system, (while in methods such as cash it is implemented between the seller and buyer, in the methods of payments with card or meal cheque technical messaging which will provide authorization online from the respective approval bodies is being used) and transfer of successful/unsuccessful (cancel/abort) fiscal data to gmö platform are implemented. [0079] transmitting the fiscal data by the terminal software module (24) momentarily to the safe mobile payment platform (10) in routine intervals determined by the regulation or in line with the momentary requests of the regulator (such as momentary transaction information, daily z-reports, weekly or monthly z-reports), [0080] transmitting the fiscal data from the safe mobile payment platform (10) to the income authority official corporation (40).