Disclosure of Invention
Aiming at the technical problems, the embodiment of the specification provides a payment method, a payment system, a payment device, a payment terminal and a payment server, wherein the technical scheme is as follows:
according to a first aspect of embodiments of the present description, there is provided a payment method, applied to a payment system,
the payment system comprises a client and a server, and the method comprises the following steps:
the client acquires the identification and the transaction amount of the collection entity through a specified code scanning payment mode, and sends the identification and the transaction amount of the collection entity to the server;
the server generates a virtual bank card number according to a bank card number naming rule of the signed bank entity;
The server generates a payment transaction bill and sends the payment transaction bill to a banking entity to which the virtual bank card number belongs, wherein the payment transaction bill at least comprises the virtual bank card number, the identification of the receiving entity and the transaction amount, so that the banking entity pays transaction funds to the receiving entity according to the transaction amount.
According to a second aspect of embodiments of the present description, there is provided a payment method,
applied to a client, the method comprises the following steps:
and acquiring the identification and the transaction amount of the receiving entity in a specified code scanning payment mode, and transmitting the identification and the transaction amount of the receiving entity to the server.
According to a third aspect of embodiments of the present disclosure, there is provided a payment method, applied to a server, the method including:
receiving an identification and transaction amount of a collection entity sent by a client;
generating a virtual bank card number according to a bank card number naming rule of the contracted bank entity;
generating a payment transaction bill and sending the payment transaction bill to a banking entity to which the virtual bank card number belongs, wherein the payment transaction bill at least comprises the virtual bank card number, the identification of the receiving entity and the transaction amount, so that the banking entity pays transaction funds to the receiving entity according to the transaction amount.
According to a fourth aspect of embodiments of the present disclosure, there is provided a payment system, including a client, a server;
the client is used for acquiring the identification and the transaction amount of the collection entity in a specified code scanning payment mode and sending the identification and the transaction amount of the collection entity to the server;
the server is used for generating a virtual bank card number according to the bank card number naming rule of the contracted bank entity;
the server is further configured to generate a payment transaction bill, and send the payment transaction bill to a banking entity to which the virtual bank card number belongs, where the payment transaction bill at least includes the virtual bank card number, an identifier of the receiving entity, and the transaction amount, so that the banking entity pays transaction funds to the receiving entity according to the transaction amount.
According to a fifth aspect of embodiments of the present specification, there is provided a payment device for use with a client, the device comprising:
the acquisition module is used for acquiring the identification and transaction amount of the collection entity in a specified code scanning payment mode;
and the sending module is used for sending the identification of the collection entity and the transaction amount to the server.
According to a sixth aspect of embodiments of the present disclosure, there is provided a payment device, applied to a server, the device including:
the receiving module is used for receiving the identification of the collection entity and the transaction amount sent by the client;
the card number generation module is used for generating a virtual bank card number according to a bank card number naming rule of the contracted bank entity;
the bill generation module is used for generating a payment transaction bill and sending the payment transaction bill to a banking entity to which the virtual bank card number belongs, wherein the payment transaction bill at least comprises the virtual bank card number, the identification of the receiving entity and the transaction amount, so that the banking entity pays transaction funds to the receiving entity according to the transaction amount.
According to a seventh aspect of the embodiments of the present specification, there is provided a terminal comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the payment method provided by the embodiments of the present specification when executing the program.
According to an eighth aspect of the embodiments of the present specification, there is provided a service server comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the payment method provided by the embodiments of the present specification when executing the program.
According to the technical scheme provided by the embodiment of the specification, the identification and the transaction amount of the collection entity are obtained through a client through a specified code scanning payment mode, and the identification and the transaction amount of the collection entity are sent to a server; the server generates a virtual bank card number according to the bank card number naming rule of the contracted bank entity; the server generates a payment transaction bill and sends the payment transaction bill to a banking entity to which the virtual bank card number belongs, wherein the payment transaction bill at least comprises the virtual bank card number, the identification of a receiving entity and transaction amount, so that the banking entity pays transaction funds to the receiving entity according to the transaction amount, the popularization of mobile payment business can be realized on the premise of not changing the existing funds settlement flow formulated for card swiping payment, and the user experience is improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the embodiments of the disclosure.
Further, not all of the effects described above need be achieved in any of the embodiments of the present specification.
Detailed Description
In order for those skilled in the art to better understand the technical solutions in the embodiments of the present specification, the technical solutions in the embodiments of the present specification will be described in detail below with reference to the drawings in the embodiments of the present specification, and it is apparent that the described embodiments are only some embodiments of the present specification, not all embodiments. All other embodiments obtained by a person skilled in the art based on the embodiments in the present specification shall fall within the scope of protection.
With the development of internet technology, domestic users are increasingly inclined to pay using a payment type application, such as a payment treasury, installed on a mobile terminal, when consuming, such as supermarket shopping settlement, or restaurant ticket settlement, wherein the payment type application is an application developed by a special payment institution. Through the payment mode, the problems of complex operation and lower efficiency caused by traditional cash payment and card swiping payment can be solved, and the user experience is improved.
However, currently, in one type of scenario, with the development of economic globalization, more and more payment institutions intend to develop mobile payment services, such as code-scanning payment services, overseas. However, for areas where the card organization is developed, such as the european and american areas, people are generally used to make swipe payments using bank cards, such as credit cards, and for such swipe payment methods, the existing settlement procedure is: after the user swipes the card and consumes, the bank entity performs fund settlement to the collection entity (such as a merchant entity or a bill receiving mechanism cooperated with the merchant entity) according to a preset settlement period, such as a T+1 settlement period, and meanwhile, the bank entity can deduct corresponding amount from the user bank card.
For this scenario, the difficulty of the payment mechanism to develop mobile payment business overseas is: the intervention of the payment mechanism involves the modification of the existing fund settlement process, and the fund settlement process involves more mechanisms, so that the modification is more difficult.
Based on this, the embodiment of the present specification provides a payment method to realize popularization of mobile payment service without changing the existing funds settlement flow formulated for swipe payment. The method is described as follows:
referring first to fig. 1, an application scenario schematic diagram for implementing a payment method according to an exemplary embodiment of the present disclosure is provided, where fig. 1 includes a payment system 110 and a banking entity 120, and the payment system 110 may include: a payer terminal 111, a server 112, and a payee terminal 113.
The payer terminal 111 has installed thereon a payer client having a payment function, such as a payment instrument APP, and the payee terminal 113 may be a payee entity (not shown in fig. 1), such as a terminal of a store, supermarket, hotel, etc., on which a payee client having a payee function is installed. It should be noted that, the payer terminal 111 illustrated in fig. 1 is only an example of a mobile phone, and in practical application, the payer terminal 111 may also be a PAD, a tablet computer, or the like, which is not limited in this embodiment of the present disclosure.
The server 112 is a server corresponding to the payer client and the payee client, that is, the payer client and the payee client can both communicate with the server 112, it should be noted that the server 112 illustrated in fig. 1 only uses one server as an example, and in practical application, the server 112 may be a server cluster, which is not limited in this embodiment of the present disclosure.
Based on the application scenario illustrated in fig. 1, taking the case that the user (not shown in fig. 1) consumes in the cash-collecting entity as an example, the payment method provided in the embodiment of the present disclosure may be applied to implement payment, and as follows, the following embodiment is provided to describe the payment method provided in the present disclosure in detail:
embodiment one:
referring to fig. 2, a flowchart of an embodiment of a payment method according to an exemplary embodiment of the present disclosure may be applied to the payment system 110 illustrated in fig. 1, and includes the following steps:
step 202: the client acquires the identification and the transaction amount of the receiving entity through a specified code scanning payment mode, and sends the identification and the transaction amount of the receiving entity to the server.
Firstly, the client described in this step is a generic term of the payer client and the payee client, and interaction can be performed between the payer client and the payee client by a specified code scanning payment method, so as to obtain the identification and transaction amount of the payee entity.
In one embodiment, the payee entity may have a code scanning device (not shown in FIG. 1), such as a code scanning gun, which may be coupled to payee terminal 113 for scanning the payment code presented by the payer client. Based on this, the user can activate the payer client upon payment through the payer terminal 111, and operate the payer client to display the payment code. The clerk in the receiving entity can operate the code scanning equipment to scan the payment code, and if the code scanning is successful, the payment is successful. After the code scanning is successful, the payer client may send the identification of the payee entity and the transaction amount of the payment to the server 112.
In another embodiment, a two-dimensional code of collection may be laid in the collection entity, where the two-dimensional code of collection may carry an identifier of the collection entity, and then, when the user makes a payment through the payer terminal 111, the user may start the payer client and operate the payer client to scan the two-dimensional code of collection laid in the collection entity, after the code scanning is successful, the payment client may display a collection interface, and the user may input a corresponding amount on the collection interface and click "confirm payment", which means that the payment is successful. Thus, through this process, the payer client can obtain the identity of the payee entity and the transaction amount paid this time, and then the payer client can send the identity of the payee entity and the transaction amount to the server 112.
Step 204: and the server generates a virtual bank card number according to the bank card number naming rule of the contracted bank entity.
In the embodiment of the present disclosure, the payment system 110 may sign up with a partner banking entity, such as the banking entity 120, where "sign up" means that after the user makes a payment to the receiving entity through the payment system 110, the signed up banking entity performs a fund settlement to the receiving entity. Therefore, the existing fund settlement flow established for card swiping consumption between the banking entity and the collecting entity can not be changed through the processing.
In an embodiment, after receiving the identification of the receiving entity and the transaction amount corresponding to a transaction, the server 112 may automatically generate a virtual bank card number according to the bank card naming rule of the contracted bank entity, for example, the bank entity 120.
In another embodiment, in the step 202, the user may select a payment manner while operating the payment client to display the payment code, for example, as shown in fig. 3, the user selects the payment manner of "virtual bank card transaction", and then the payment code displayed by the payment client may carry an indication message for indicating that the virtual bank card transaction is performed, and then by scanning the payment code, the payee client may acquire the indication message and send the indication message to the server together. After receiving the indication message, the server can trigger to generate a virtual bank card number.
It will be appreciated by those skilled in the art that the naming rules of the bank card numbers of different banking entities are different, so that the banking entity to which the bank card number belongs can be identified by the bank card number.
In addition, it should be noted that the payment system 110 may correspond to at least one contracted banking entity, which is not limited in this embodiment of the present disclosure. In the case that the payment system 110 corresponds to more than two contracted banking entities, the server 112 may select one banking entity from the more than two contracted banking entities, and generate the virtual bank card number according to the bank card number naming rule of the selected banking entity.
In an alternative implementation, the server 112 may randomly select one of the two or more contracted banking entities; in another alternative implementation, the server 112 may select one of the two or more contracted banking entities according to a usage habit preset by the user. Those skilled in the art will appreciate that the above two alternative implementations are merely examples, and that in practical applications, there may be other implementations of selecting one of two or more contracted banking entities, and the embodiments of the present disclosure are not limited thereto.
It should be further noted that, for the same user, when the user uses the client of the payer to pay at different times, different places and different scenes, the virtual bank card number generated by the server 112 may be different each time.
Step 206: the server generates a payment transaction bill and sends the payment transaction bill to a banking entity to which the virtual bank card number belongs, wherein the payment transaction bill at least comprises the virtual bank card number, an identification of a receiving entity and transaction amount, so that the banking entity pays transaction funds to the receiving entity according to the transaction amount.
In the embodiment of the present disclosure, the server 112 may generate a payment transaction bill, where the payment transaction bill includes at least the virtual bank card number, the identification of the receiving entity, and the transaction amount. Subsequently, the server 112 may push the payment transaction bill to the banking entity to which the virtual bank card number belongs according to a settlement period agreed with the banking entity to which the virtual bank card number belongs, for example, a t+1 settlement period, so that the banking entity pays the transaction funds to the receiving entity according to the transaction amount in the payment transaction bill.
As can be seen from the description in the above steps 204 and 206, the process that the server 112 generates a virtual bank card number, and then the bank entity to which the virtual bank card number belongs pays the amount of the user to the receiving entity can be colloquially understood that the server 112 temporarily applies the user for a "credit card" to the bank entity, and then the bank entity to which the "credit card" belongs pays the amount of the user to the receiving entity.
Based on this, in the embodiment of the present disclosure, the server 112 may pay the transaction funds to the banking entity to which the virtual bank card number belongs according to the transaction amount, and deduct the transaction amount from the user account according to the account information of the user account currently logged in on the payer client. This process can be colloquially understood as the "user performs credit card repayment".
In an embodiment, the payment code displayed by the payer client may further carry account information of the user account currently logged in on the payer client, and then, after the payee client scans the payment code displayed by the payer client based on the user operation, the payee client may acquire the account information, and then, the payee client may send the account information to the server 112.
In another embodiment, if the payer client performs payment by scanning the two-dimensional code, the account information of the user account may be sent to the server 112 by the payer client after the payment operation is completed.
According to the technical scheme provided by the embodiment of the specification, the identification and the transaction amount of the collection entity are obtained through a client through a specified code scanning payment mode, and the identification and the transaction amount of the collection entity are sent to a server; the server generates a virtual bank card number according to the bank card number naming rule of the contracted bank entity; the server generates a payment transaction bill and sends the payment transaction bill to a banking entity to which the virtual bank card number belongs, wherein the payment transaction bill at least comprises the virtual bank card number, the identification of a receiving entity and transaction amount, so that the banking entity pays transaction funds to the receiving entity according to the transaction amount, the popularization of mobile payment business can be realized on the premise of not changing the existing funds settlement flow formulated for card swiping payment, and the user experience is improved.
Thus, the description of the first embodiment is completed.
Embodiment two:
referring to fig. 4, a flowchart of an embodiment of another payment method provided for an exemplary embodiment of the present disclosure may be applied to a client (including a payer client and a payee client) in the payment system 110 illustrated in fig. 1, and includes the following steps:
step 402: the identification and the transaction amount of the collection entity are obtained through a specified code scanning payment mode, and the identification and the transaction amount of the collection entity are sent to a server.
According to the technical scheme provided by the embodiment of the specification, the client acquires the identification and the transaction amount of the receiving entity through the specified code scanning payment mode, and sends the identification and the transaction amount of the receiving entity to the server, so that the popularization of mobile payment service can be realized on the premise that the existing fund settlement flow formulated for card swiping payment is not changed, and the user experience is improved.
Thus, the description of the second embodiment is completed.
Embodiment III:
referring to fig. 5, a flowchart of an embodiment of a payment method according to an exemplary embodiment of the present disclosure may be applied to the server 112 illustrated in fig. 1, and includes the following steps:
Step 502: and receiving the identification of the receiving entity and the transaction amount sent by the client.
Step 504: and generating a virtual bank card number according to the bank card number naming rule of the contracted bank entity.
Step 506: and generating a payment transaction bill and sending the payment transaction bill to a banking entity to which the virtual bank card number belongs, wherein the payment transaction bill at least comprises the virtual bank card number, the identification of the receiving entity and the transaction amount, so that the banking entity pays transaction funds to the receiving entity according to the transaction amount.
According to the technical scheme provided by the embodiment of the specification, the identification of the collection entity and the transaction amount sent by the client are received; generating a virtual bank card number according to a bank card number naming rule of the contracted bank entity; generating a payment transaction bill and sending the payment transaction bill to a banking entity to which the virtual bank card number belongs, wherein the payment transaction bill at least comprises the virtual bank card number, the identification of a receiving entity and transaction amount, so that the banking entity pays transaction funds to the receiving entity according to the transaction amount, the popularization of mobile payment service can be realized on the premise of not changing the existing funds settlement flow formulated for card swiping payment, and the user experience is improved.
Thus, the description of the third embodiment is completed.
Corresponding to the above-mentioned method embodiment illustrated in fig. 2, the present embodiment further provides a payment system, please refer to fig. 6, which is an architecture diagram of the payment system provided in an exemplary embodiment of the present disclosure, the payment system includes: client 61, server 62.
The client 61 is configured to obtain an identifier of a receiving entity and a transaction amount through a specified code scanning payment manner, and send the identifier of the receiving entity and the transaction amount to the server;
the server 62 is configured to generate a virtual bank card number according to a bank card number naming rule of a signed bank entity;
the server 62 is further configured to generate a payment transaction bill, and send the payment transaction bill to a banking entity to which the virtual bank card number belongs, where the payment transaction bill at least includes the virtual bank card number, an identifier of the receiving entity, and the transaction amount, so that the banking entity pays the transaction funds to the receiving entity according to the transaction amount.
In one embodiment, the clients 61 include a payer client 611, a payee client 612; wherein,,
A payer client 611 for displaying a payment code based on a user operation;
the payee client 612 is configured to scan the payment code based on user operation, and send the identifier of the payee entity and the transaction amount to the server after the payment code is scanned successfully.
In an embodiment, the payer client 611 is further configured to scan the specified two-dimensional code for receipt, and display a payment interface after the code scanning is successful, where the two-dimensional code for receipt carries an identifier of a receiving entity to which the two-dimensional code for receipt belongs;
the payer client 611 is further configured to receive a transaction amount input by the user through the payment interface;
the payer client 611 is further configured to send the identification of the payee entity and the transaction amount to the server. In one embodiment, the payment code further carries an indication message for indicating to take a virtual bank card transaction mode;
the payee client 612 is further configured to obtain the indication message after scanning the payment code based on user operation, and send the indication message to the server;
the server 62 is configured to receive the indication message sent by the payee client, and generate a virtual bank card number according to a bank card number naming rule of the signed bank entity based on the indication message.
In an embodiment, the payment code also carries account information of the user account currently logged in on the payer client 611;
the payee client 612 is further configured to obtain account information of the user account after scanning the payment code based on user operation;
the payee client 612 is further configured to send account information of the user account to the server.
In an embodiment, the payment client 611 is further configured to send account information of the locally currently logged-in user account to the server.
In an embodiment, the server 62 is further configured to deduct the transaction amount from the currently logged-in user account on the payer client 611 according to the account information.
Corresponding to the above-mentioned method embodiment illustrated in fig. 4, the present embodiment further provides a payment device, which may be applied to a client, please refer to fig. 7, for an embodiment block diagram of a payment device provided in an exemplary embodiment of the present disclosure, the device includes: an acquisition module 71 and a transmission module 72.
The acquiring module 71 may be configured to acquire an identifier of a receiving entity and a transaction amount in a specified code scanning payment manner;
The sending module 72 may be configured to send the identification of the receiving entity and the transaction amount to the server.
It should be understood that, the acquiring module 71 and the transmitting module 72 may be configured in the apparatus as two modules with independent functions, as shown in fig. 7, or may be configured in the apparatus separately and separately, and therefore, the configuration shown in fig. 7 should not be construed as limiting the embodiment of the present disclosure.
In response to the above-described method embodiment illustrated in fig. 5, the embodiment of the present disclosure further provides another payment device, which may be applied to a server, please refer to fig. 8, which is a block diagram of an embodiment of another payment device provided in an exemplary embodiment of the present disclosure, where the device includes: a receiving module 81, a card number generating module 82, and a bill generating module 83.
The receiving module 81 may be configured to receive an identifier of a receiving entity and a transaction amount sent by the client;
the card number generation module 82 may be configured to generate a virtual bank card number according to a bank card number naming rule of a contracted banking entity;
the bill generating module 83 is configured to generate a payment transaction bill, and send the payment transaction bill to a banking entity to which the virtual bank card number belongs, where the payment transaction bill at least includes the virtual bank card number, an identifier of the receiving entity, and the transaction amount, so that the banking entity pays transaction funds to the receiving entity according to the transaction amount.
It should be understood that, as three modules with independent functions, the receiving module 81, the card number generating module 82, and the bill generating module 83 may be configured in the apparatus at the same time as shown in fig. 8, or may be configured in the apparatus separately, so the configuration shown in fig. 8 should not be construed as limiting the embodiment of the present disclosure.
In addition, the implementation process of the functions and roles of each module in the apparatus shown in fig. 7 and fig. 8 is specifically shown in the implementation process of the corresponding steps in the method, and will not be repeated here.
The embodiment of the specification also provides a terminal, which at least comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the processor executes the program to realize the payment method. The method at least comprises the following steps: and acquiring the identification and the transaction amount of the receiving entity in a specified code scanning payment mode, and sending the identification and the transaction amount of the receiving entity to a server.
The embodiment of the specification also provides a service server, which at least comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the processor executes the program to realize the payment method. The method at least comprises the following steps: receiving an identification and transaction amount of a collection entity sent by a client; generating a virtual bank card number according to a bank card number naming rule of the contracted bank entity; generating a payment transaction bill and sending the payment transaction bill to a banking entity to which the virtual bank card number belongs, wherein the payment transaction bill at least comprises the virtual bank card number, the identification of the receiving entity and the transaction amount, so that the banking entity pays transaction funds to the receiving entity according to the transaction amount.
Fig. 9 is a schematic diagram of a more specific hardware structure of a terminal according to an embodiment of the present disclosure, where the terminal may include: a processor 910, a memory 920, an input/output interface 930, a communication interface 940, and a bus 950. Wherein processor 910, memory 920, input/output interface 930, and communication interface 940 implement communication connections among each other within the device via a bus 950.
The processor 910 may be implemented by a general-purpose CPU (Central Processing Unit ), a microprocessor, an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), or one or more integrated circuits, etc. for executing relevant programs to implement the technical solutions provided in the embodiments of the present disclosure.
The Memory 920 may be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory ), static storage device, dynamic storage device, or the like. Memory 920 may store an operating system and other application programs, and when the embodiments of the present specification are implemented in software or firmware, the associated program code is stored in memory 920 and executed by processor 910.
The input/output interface 930 is used to connect with input/output modules to achieve information input and output. The input/output module may be configured as a component in a device (not shown) or may be external to the device to provide corresponding functionality. Wherein the input devices may include a keyboard, mouse, touch screen, microphone, various types of sensors, etc., and the output devices may include a display, speaker, vibrator, indicator lights, etc.
The communication interface 940 is used to connect a communication module (not shown in the figure) to enable communication interaction between the present device and other devices. The communication module may implement communication through a wired manner (such as USB, network cable, etc.), or may implement communication through a wireless manner (such as mobile network, WIFI, bluetooth, etc.).
Bus 950 includes a path for transferring information between components of the device (e.g., processor 910, memory 920, input/output interface 930, and communication interface 940).
It should be noted that although the above device only shows the processor 910, the memory 920, the input/output interface 930, the communication interface 940, and the bus 950, in the implementation, the device may include other components necessary to achieve normal operation. Furthermore, it will be understood by those skilled in the art that the above-described apparatus may include only the components necessary to implement the embodiments of the present description, and not all the components shown in the drawings.
Fig. 10 is a schematic diagram of a more specific hardware architecture of a service server according to an embodiment of the present disclosure, where the service server may include: a processor 1010, a memory 1020, an input/output interface 1030, a communication interface 1040, and a bus 1050. Wherein processor 1010, memory 1020, input/output interface 1030, and communication interface 1040 implement communication connections therebetween within the device via a bus 1050.
The processor 1010 may be implemented by a general-purpose CPU (Central Processing Unit ), microprocessor, application specific integrated circuit (Application Specific Integrated Circuit, ASIC), or one or more integrated circuits, etc. for executing relevant programs to implement the technical solutions provided in the embodiments of the present disclosure.
The Memory 1020 may be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory ), static storage device, dynamic storage device, or the like. Memory 1020 may store an operating system and other application programs, and when the embodiments of the present specification are implemented in software or firmware, the associated program code is stored in memory 1020 and executed by processor 1010.
The input/output interface 1030 is used to connect with an input/output module for inputting and outputting information. The input/output module may be configured as a component in a device (not shown) or may be external to the device to provide corresponding functionality. Wherein the input devices may include a keyboard, mouse, touch screen, microphone, various types of sensors, etc., and the output devices may include a display, speaker, vibrator, indicator lights, etc.
Communication interface 1040 is used to connect communication modules (not shown) to enable communication interactions of the present device with other devices. The communication module may implement communication through a wired manner (such as USB, network cable, etc.), or may implement communication through a wireless manner (such as mobile network, WIFI, bluetooth, etc.).
Bus 1050 includes a path for transferring information between components of the device (e.g., processor 1010, memory 1020, input/output interface 1030, and communication interface 1040).
It should be noted that although the above-described device only shows processor 1010, memory 1020, input/output interface 1030, communication interface 1040, and bus 1050, in an implementation, the device may include other components necessary to achieve proper operation. Furthermore, it will be understood by those skilled in the art that the above-described apparatus may include only the components necessary to implement the embodiments of the present description, and not all the components shown in the drawings.
The present description also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the foregoing payment method. The method at least comprises the following steps: and acquiring the identification and the transaction amount of the receiving entity in a specified code scanning payment mode, and sending the identification and the transaction amount of the receiving entity to a server.
The present description also provides another computer-readable storage medium, on which a computer program is stored which, when executed by a processor, implements the aforementioned payment method. The method at least comprises the following steps: receiving an identification and transaction amount of a collection entity sent by a client; generating a virtual bank card number according to a bank card number naming rule of the contracted bank entity; generating a payment transaction bill and sending the payment transaction bill to a banking entity to which the virtual bank card number belongs, wherein the payment transaction bill at least comprises the virtual bank card number, the identification of the receiving entity and the transaction amount, so that the banking entity pays transaction funds to the receiving entity according to the transaction amount.
Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.
From the foregoing description of embodiments, it will be apparent to those skilled in the art that the present embodiments may be implemented in software plus a necessary general purpose hardware platform. Based on such understanding, the technical solutions of the embodiments of the present specification may be embodied in essence or what contributes to the prior art in the form of a software product, which may be stored in a storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method described in the embodiments or some parts of the embodiments of the present specification.
The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. A typical implementation device is a computer, which may be in the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or a combination of any of these devices.
In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for the device embodiments, since they are substantially similar to the method embodiments, the description is relatively simple, and reference is made to the description of the method embodiments for relevant points. The apparatus embodiments described above are merely illustrative, in which the modules illustrated as separate components may or may not be physically separate, and the functions of the modules may be implemented in the same piece or pieces of software and/or hardware when implementing the embodiments of the present disclosure. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art will understand and implement the present invention without undue burden.
The foregoing is merely a specific implementation of the embodiments of this disclosure, and it should be noted that, for a person skilled in the art, several improvements and modifications may be made without departing from the principles of the embodiments of this disclosure, and these improvements and modifications should also be considered as protective scope of the embodiments of this disclosure.