Self-coding account collection method and device, equipment, storage medium and product
By generating enterprise payment codes bound to customers and establishing mapping relationships, the problem that corporate customers cannot personalize their accounts in bank collection business is solved, reducing learning costs and improving collection efficiency.
Patent Information
- Application Number
- CN202411293022.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-14
- Publication Date
- 2025-01-14
AI Technical Summary
In the bank's collection business, accounts opened based on rules cannot be personalized, resulting in increased customer learning costs.
By obtaining corporate account data, generating corporate payment codes bound to customers, and establishing a mapping relationship between corporate account data and payment codes, personalized payments for customers are realized and dependence on bank rules is reduced.
It reduces the cost of customers learning and understanding the collection account, simplifies the payment process, improves collection efficiency, and reduces manpower and reconciliation workload.
Smart Images
Figure CN119313324A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of data processing technology, and in particular to a self-encoding account payment collection method, device, equipment, storage medium and computer program product. Background Art
[0002] At present, corporate customers generally use two types of accounts in the bank's collection business. One is a current settlement account, and the other is an account under the settlement account and opened based on certain rules. These accounts do not have actual balances, but the bank provides services that can be used to identify payers. These accounts also have balances and transaction services. These two accounts must meet certain internal bank rules, and customers cannot personalize the payment account, which means that a large number of customers need to understand the collection account in detail, increasing the customer's learning cost.
[0003] Therefore, how to realize personalized coding of payment accounts to reduce customers' learning costs is a problem that needs to be solved urgently.
[0004] The above contents are only used to assist in understanding the technical solution of the present application and do not constitute an admission that the above contents are prior art. Summary of the invention
[0005] The main purpose of this application is to provide a self-coding account collection method, device, equipment, storage medium and computer program product, aiming to solve the technical problem in related technologies that accounts opened based on certain rules must meet certain internal rules of the bank, and customers cannot personalize the payment accounts, which increases the learning cost of customers.
[0006] To achieve the above purpose, the present application proposes a self-coding account payment method, which includes:
[0007] Obtain enterprise account data;
[0008] Based on the enterprise account data, a plurality of enterprise payment codes are generated, wherein any enterprise payment code is bound to a corresponding customer;
[0009] A mapping relationship is established between the enterprise account data and each of the enterprise payment codes, and payment is collected from each of the customers using the enterprise payment code.
[0010] In one embodiment, the step of generating a plurality of enterprise payment codes based on the enterprise account data comprises:
[0011] Obtain customer coding quantity and coding requirements;
[0012] Based on the coding requirement and the corporate account data, a corporate payment code corresponding to the customer coding quantity is generated.
[0013] In one embodiment, before the step of establishing a mapping relationship between the enterprise account data and each of the enterprise payment codes, the step further includes:
[0014] Evenly distribute each of the enterprise payment codes to multiple customers;
[0015] Bind each of the customers with the corresponding allocated enterprise payment code to obtain a plurality of binding relationship data, and store the binding relationship data in a preset payment database.
[0016] In one embodiment, after the step of collecting payment from each of the customers using the enterprise payment code, the method further includes:
[0017] Extracting payment data from each of the enterprise payment codes;
[0018] Based on the mapping relationship, each payment data is transmitted to the enterprise account data to collect statistics on the payment data of each customer.
[0019] In one embodiment, the step of collecting payment from each of the customers using the enterprise payment code includes:
[0020] determining the payment pattern of each of said customers;
[0021] When it is determined that the payment mode is a code scanning mode, displaying a payment code to the customer, and receiving payment data fed back by the customer through the payment code;
[0022] In the case where it is determined that the payment mode is a transfer mode, opening the transfer authority of the customer and receiving the transfer data of the customer paying the enterprise payment code;
[0023] In the case where it is determined that the payment mode is the gesture scanning payment mode, detecting a gesture image of the customer;
[0024] When the gesture image meets a preset image standard, a preset amount of payment data is deducted from the customer's account.
[0025] In one embodiment, the step of collecting payment from each of the customers using the enterprise payment code further includes:
[0026] Sending a payment request to each of the customers through the enterprise payment code;
[0027] Receiving a payment instruction sent by the customer based on the payment request, and determining whether the payment amount in the payment instruction is less than a preset threshold;
[0028] When it is determined that the payment amount is less than a preset threshold, the account of each of the customers is deducted, and the deduction amount is recorded in the enterprise payment code.
[0029] In addition, to achieve the above purpose, the present application also proposes a self-coding account payment collection device, the self-coding account payment collection device comprising:
[0030] The acquisition module is used to obtain enterprise account data;
[0031] A generating module, configured to generate a plurality of enterprise payment codes based on the enterprise account data, wherein any enterprise payment code is bound to a corresponding customer;
[0032] The payment collection module is used to establish a mapping relationship between the enterprise account data and each of the enterprise payment codes, and to collect payment from each of the customers using the enterprise payment code.
[0033] In addition, to achieve the above-mentioned purpose, the present application also proposes a self-encoding account payment collection device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, and the computer program is configured to implement the steps of the self-encoding account payment collection method as described above.
[0034] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, which is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by the processor, the steps of the self-encoding account collection method described above are implemented.
[0035] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, it implements the steps of the self-encoding account payment collection method as described above.
[0036] The present application proposes a self-coding account payment collection method, device, equipment, storage medium and computer program product. The present application obtains corporate account data and generates the required corporate payment code based on the corporate account data, wherein any corporate payment code is bound to the corresponding customer, and a mapping relationship is established between the corporate account data and each corporate payment code to collect payment from each customer through each corporate payment code. The actual payment data and payment status of each customer can be determined and counted in the corporate account data. The corporate payment code used for collection does not need to meet the rules stipulated by the bank, and supports customers to personalize the coding of payment accounts, so that customers do not need to spend time learning or understanding the collection account number. BRIEF DESCRIPTION OF THE DRAWINGS
[0037] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.
[0038] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.
[0039] Figure 1 A flowchart of the first embodiment of the method for collecting payment from a self-coding account is provided for this application;
[0040] Figure 2 A flowchart of the second embodiment of the self-coding account payment method for this application;
[0041] Figure 3 This is a schematic diagram of the overall process involved in the self-coding account payment method for this application;
[0042] Figure 4 This is a schematic diagram of the module structure of the self-coding account payment collection device according to an embodiment of the present application;
[0043] Figure 5 This is a schematic diagram of the device structure of the hardware operating environment involved in the self-coding account payment collection method in the embodiment of the present application.
[0044] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION
[0045] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.
[0046] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.
[0047] The main solutions of the embodiments of this application are:
[0048] Obtain enterprise account data;
[0049] Based on the enterprise account data, a plurality of enterprise payment codes are generated, wherein any enterprise payment code is bound to a corresponding customer;
[0050] A mapping relationship is established between the enterprise account data and each of the enterprise payment codes, and payment is collected from each of the customers using the enterprise payment code.
[0051] Because in the relevant technology, the accounts are opened under the settlement account and based on certain rules. These accounts do not have actual balances, but the bank provides services that can be used to identify payers. These accounts also have balances and transaction services. These two types of accounts must meet certain internal rules of the bank. Customers cannot personalize the payment account, which requires a large number of customers to understand the collection account in detail, increasing the learning cost of customers.
[0052] The present application proposes a self-coding account payment collection method, device, equipment, storage medium and computer program product. The present application obtains corporate account data and generates the required corporate payment code based on the corporate account data, wherein any corporate payment code is bound to the corresponding customer, and a mapping relationship is established between the corporate account data and each corporate payment code to collect payment from each customer through each corporate payment code. The actual payment data and payment status of each customer can be determined and counted in the corporate account data. The corporate payment code used for collection does not need to meet the rules stipulated by the bank, and supports customers to personalize the coding of payment accounts, so that customers do not need to spend time learning or understanding the collection account number.
[0053] It should be noted that the execution subject of this embodiment can be a computing service device with data processing, network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or an electronic device capable of realizing the above functions, a self-coding account payment collection device, etc. The following takes the self-coding account payment collection device as an example to illustrate this embodiment and the following embodiments.
[0054] Based on this, the present application embodiment provides a self-coding account payment method, referring to Figure 1 , Figure 1 This is a flow chart of the first embodiment of the self-coding account payment collection method of the present application.
[0055] In this embodiment, the self-coding account payment method includes steps S10 to S30:
[0056] Step S10, obtaining enterprise account data;
[0057] It should be noted that the method involved in this application is applied to business collection scenarios of some large enterprises from customers. The enterprise account data is the total account data when large enterprises collect payments from customers. The enterprise account data includes but is not limited to the enterprise account ID, payment method, amount of collection, etc., and is not specifically limited.
[0058] It should be noted that corporate accounts are used to connect with the banking system. For example, when power grid companies collect electricity bills on a regular basis, they aggregate the payment data of each customer, and then reconcile and summarize the corporate accounts. Finally, they connect with the banking system to verify whether the funds correspond to the bank's internal accounts, and then complete the collection of payments for each customer.
[0059] Step S20, generating multiple enterprise payment codes based on the enterprise account data, wherein any enterprise payment code is bound to a corresponding customer;
[0060] It should be noted that the enterprise payment code can be a combination of letters and numbers, or it can be pure numbers. For example, the enterprise payment code can be 0001, A002, etc., without specific limitation.
[0061] It should be noted that the corporate payment code can be a corporate code generated by the company based on customer needs. In order to facilitate customer memory, the corporate payment code does not need to be set according to the bank's rules. The coding method is not limited and can be customized. Among them, the corporate payment code will not actually store funds and is mainly used to assist customers in classified accounting.
[0062] It should be noted that each customer is assigned a corresponding corporate payment code. When recording the customer's payment data, the payment status and amount of each customer can be determined through the data recorded by each corporate payment code. When a customer collects payment through a corporate payment code, each corporate payment code has established a binding relationship with the customer to ensure that there is an association between the two.
[0063] In a feasible implementation manner, the step S20 of generating a plurality of enterprise payment codes based on the enterprise account data includes:
[0064] Obtain customer coding quantity and coding requirements;
[0065] It should be noted that the number of customer codes corresponds to the number of customers who need to pay. For example, if the number of customers who need to pay is 100, the number of customer codes is also 100.
[0066] It should be noted that the coding requirement can be a coding requirement for personalized coding. For customers, if the account code has too many characters, it will cost more to learn. Some customers will choose to make the code as short as possible, or personalize the payment account according to their own memory method.
[0067] Based on the coding requirement and the corporate account data, a corporate payment code corresponding to the customer coding quantity is generated.
[0068] It should be noted that after determining the coding requirements, an enterprise payment code corresponding to the customer coding number is generated. After the enterprise payment code is generated, a mapping relationship is established with the enterprise account data, and the enterprise payment code is set.
[0069] It should be noted that in the process of generating corporate payment codes, there are two ways: one is to import the existing collection numbers into the China Merchants Bank system at one time to realize the collection of payment codes; the other is to complete the opening, change and account closing of collection codes in real time during the company's daily business operations.
[0070] Step S30, establishing a mapping relationship between the enterprise account data and each of the enterprise payment codes, and collecting payment from each of the customers using the enterprise payment code.
[0071] It should be noted that after the enterprise payment code is generated, a mapping relationship between the enterprise account data and each enterprise payment code is established to form a payment relationship between the enterprise account and each customer / settlement customer, which facilitates the subsequent statistics of the number of collections.
[0072] It should be noted that after the mapping relationship between the corporate account data and each corporate payment code is established, the payment made by the customer is received through the corporate payment code. After each corporate payment code records the specific payment amount of each customer, the payment data of the customer in each corporate payment code is obtained through the mapping relationship through the corporate account data, and statistics are made on it. After the account is reconciled with the bank system, the payment collection business for the customer can be completed.
[0073] In a feasible implementation manner, before the step S30 of establishing a mapping relationship between the enterprise account data and each of the enterprise payment codes, the step further includes:
[0074] Evenly distribute each of the enterprise payment codes to multiple customers;
[0075] It should be noted that before establishing a mapping relationship between corporate account data and corporate payment codes, it is necessary to bind customers to each corporate payment code.
[0076] It should be noted that the uniform distribution method can be: the corporate payment code generated according to customer needs is distributed to the corresponding customers, and the randomly generated corporate payment code is distributed to other customers who do not have coding requirements.
[0077] Bind each of the customers with the corresponding allocated enterprise payment code to obtain a plurality of binding relationship data, and store the binding relationship data in a preset payment database.
[0078] It should be noted that the process of binding the corporate payment code with each customer can be to establish association information between the customer and the corporate payment code. After the binding is completed, binding data is set between each corporate payment code and the customer, and the binding relationship data is stored in the preset payment database for subsequent call-up during payment reconciliation, thereby determining the payment status of each customer.
[0079] In a feasible implementation manner, after the step S30 of collecting payment from each customer using the enterprise payment code, the method further includes:
[0080] Extracting payment data from each of the enterprise payment codes;
[0081] It should be noted that after collecting payments from each customer, the specific amount paid by each customer, that is, the payment data, will be stored in the enterprise payment code.
[0082] It should be noted that the payment data can be 1000, 5000, etc., without specific limitation.
[0083] Based on the mapping relationship, each payment data is transmitted to the enterprise account data to collect statistics on the payment data of each customer.
[0084] It should be noted that before this, a mapping relationship has been established between the corporate account data and each corporate payment code. Therefore, the corporate account data can use this mapping relationship to count the payment data in each corporate payment code, and then through the connection between its own system and the bank system, it can know in real time which customer's payment has arrived and how much has arrived. For enterprises, on the one hand, it can reduce the business volume at the counter and save a lot of manpower. On the other hand, the arrival information can be known in real time, identifying which customer has completed the payment and how much has been paid, reducing a lot of reconciliation work, and can also combine the data to make targeted reminders and collections.
[0085] The present application proposes a self-coding account payment collection method, device, equipment, storage medium and computer program product. The present application obtains corporate account data and generates the required corporate payment code based on the corporate account data, wherein any corporate payment code is bound to the corresponding customer, and a mapping relationship is established between the corporate account data and each corporate payment code to collect payment from each customer through each corporate payment code. The actual payment data and payment status of each customer can be determined and counted in the corporate account data. The corporate payment code used for collection does not need to meet the rules stipulated by the bank, and supports customers to personalize the coding of payment accounts, so that customers do not need to spend time learning or understanding the collection account number.
[0086] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as those in the above-mentioned embodiment 1 can be referred to the above introduction, and will not be repeated in the following. Figure 2 The step S30 of collecting payment from each customer using the enterprise payment code comprises steps S31 to S35:
[0087] Step S31, determining the payment mode of each customer;
[0088] It should be noted that when collecting payments from customers through various corporate payment codes, the corresponding payment method is executed according to the customer's different payment modes. The payment mode can be a code scanning mode, a transfer mode, a facial payment mode, a password payment mode, etc., without specific limitation.
[0089] Step S32, when it is determined that the payment mode is a code scanning mode, displaying a payment code to the customer, and receiving payment data fed back by the customer through the payment code;
[0090] It should be noted that when the payment mode is determined to be the code scanning mode, the payment code corresponding to the corporate account is displayed to the customer and displayed on the customer's mobile terminal or computer terminal. After receiving the payment code, the customer can scan the code to pay the fee and feedback the payment data to the corporate account through his own terminal.
[0091] Step S33, when it is determined that the payment mode is a transfer mode, opening the transfer authority of the customer and receiving the transfer data of the customer paying the enterprise payment code;
[0092] It should be noted that when the customer's payment mode is a transfer mode, the customer is required to transfer money to the enterprise payment code. At this time, the customer's transfer authority can be opened so that the customer can make payments to the enterprise payment code, and then receive the transfer data of the customer's payment to the enterprise payment code.
[0093] Step S34, when it is determined that the payment mode is the gesture scanning payment mode, detecting the gesture image of the customer;
[0094] It should be noted that the gesture scanning payment mode is different from facial payment. Gesture scanning payment is to make payment by detecting the customer's gesture image after confirming the customer's identity.
[0095] It should be noted that the gesture image can be two fingers crossed, three fingers together, etc., without specific limitation.
[0096] Step S35, when the gesture image meets the preset image standard, deducting a preset amount of payment data from the customer's account.
[0097] It should be noted that the preset image standard may be an image standard for payment. For example, when the preset image standard is two fingers crossed, when the customer's gesture image is detected as two fingers crossed, it is determined that the customer can pay the enterprise payment code. However, when the customer's gesture image is detected as three fingers together, the preset image standard is not met and payment cannot be made.
[0098] It should be noted that when it is determined that the gesture image meets the preset image standard, the fee to be paid is deducted from the customer's account, wherein the preset amount may be 2000 / 4000, etc., and is not specifically limited.
[0099] In a feasible implementation manner, the step S30 of collecting payment from each of the customers using the enterprise payment code further includes:
[0100] Sending a payment request to each of the customers through the enterprise payment code;
[0101] It should be noted that when it is necessary to collect payments from customers on a regular basis, a payment request can be sent to each customer to remind the customer to pay the fees. The payment request can be displayed on the terminal interface where the customer is located in the form of a payment reminder.
[0102] Receiving a payment instruction sent by the customer based on the payment request, and determining whether the payment amount in the payment instruction is less than a preset threshold;
[0103] It should be noted that the payment instruction received from the customer includes the payment amount, payment method, etc., and whether the payment amount meets the requirements is determined to determine whether to deduct the account.
[0104] It should be noted that the preset threshold can be 500, 2000, etc., and there is no specific limitation. When making a payment, the preset threshold is set mainly to avoid users from accidentally touching the threshold and making overpayments.
[0105] When it is determined that the payment amount is less than a preset threshold, the account of each of the customers is deducted, and the deduction amount is recorded in the enterprise payment code.
[0106] It should be noted that when the payment amount is less than the preset threshold, the money will be deducted from each customer's account, and the deduction amount will be recorded in the enterprise payment code for subsequent account verification.
[0107] In this embodiment, payment is collected from customers through a variety of payment methods, which greatly simplifies the customer's payment process, improves collection efficiency, and saves manpower.
[0108] For example, in order to help understand the implementation process of the self-coding account payment method obtained by combining this embodiment with the above-mentioned embodiment 1, please refer to Figure 3 , Figure 3 A brief flowchart of a self-coding account payment method is provided, specifically:
[0109] Taking the power grid enterprise as an example, the current settlement account established is the enterprise account, in which each power grid collection account corresponds to the enterprise payment code, which can be used for transactions, automatic distinguishing accounting, etc. The payer corresponds to multiple customers, and the way for customers to remit money to the account can be public remittance, personal remittance, peer remittance, inter-bank remittance, etc. Among them, the power grid collection number will not actually store funds, but only assist customers in classified accounting, bind each payer with the power grid collection number, and establish a mapping relationship between the current settlement account and each power grid collection number for subsequent reconciliation, statistics, etc. Large enterprises can know in real time which customer's payment has been received and how much has been received through the docking of their own systems with the bank system. For enterprises, on the one hand, it can reduce the business volume at the counter and save a lot of manpower, and on the other hand, the arrival information is known in real time, identifying which customer has completed the payment and how much has been paid, reducing a lot of reconciliation work, and can also combine data to make targeted reminders and collections.
[0110] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the self-encoding account payment method of the present application. More simple transformations based on this technical concept are all within the scope of protection of the present application.
[0111] This application also provides a self-coding account payment device, please refer to Figure 4 , the self-coding account payment collection device comprises:
[0112] An acquisition module 10, used to acquire enterprise account data;
[0113] A generating module 20, configured to generate a plurality of enterprise payment codes based on the enterprise account data, wherein any enterprise payment code is bound to a corresponding customer;
[0114] The payment collection module 30 is used to establish a mapping relationship between the enterprise account data and each of the enterprise payment codes, and to collect payment from each of the customers using the enterprise payment code.
[0115] Optionally, the generating module includes:
[0116] An acquisition unit, used to acquire the number of customer codes and coding requirements;
[0117] A generating unit is used to generate an enterprise payment code corresponding to the number of customer codes based on the coding requirement and the enterprise account data.
[0118] Optionally, the device further comprises:
[0119] A distribution module, used for evenly distributing each of the enterprise payment codes to multiple customers;
[0120] The binding module is used to bind each of the customers with the corresponding allocated enterprise payment code to obtain a plurality of binding relationship data, and store the binding relationship data in a preset payment database.
[0121] Optionally, the device further comprises:
[0122] An extraction module, used for extracting payment data from each of the enterprise payment codes;
[0123] A transmission module is used to transmit each of the payment data to the enterprise account data based on the mapping relationship, so as to collect statistics on the payment data of each of the customers.
[0124] Optionally, the payment collection module includes:
[0125] A determination unit, used to determine a payment mode of each of the customers;
[0126] A display unit, configured to display a payment code to the customer and receive payment data fed back by the customer through the payment code when the payment mode is determined to be a code scanning mode;
[0127] A receiving unit, configured to, when determining that the payment mode is a transfer mode, open the transfer authority of the customer and receive transfer data of the customer paying the enterprise payment code;
[0128] a detection unit, configured to detect a gesture image of the customer when determining that the payment mode is a gesture scanning payment mode;
[0129] The deduction unit is used to deduct a preset amount of payment data from the customer's account when the gesture image meets a preset image standard.
[0130] Optionally, the payment module further includes:
[0131] A sending unit, used for sending a payment request to each of the customers through the enterprise payment code;
[0132] A determination unit, configured to receive a payment instruction sent by the customer based on the payment request, and determine whether a payment amount in the payment instruction is less than a preset threshold;
[0133] The recording unit is used to deduct money from the account of each of the customers when it is determined that the payment amount is less than a preset threshold, and record the deduction amount in the enterprise payment code.
[0134] The self-coding account payment collection device provided by the present application adopts the self-coding account payment collection method in the above embodiment, which can solve the technical problem of self-coding account payment collection. Compared with the prior art, the beneficial effects of the self-coding account payment collection device provided by the present application are the same as the beneficial effects of the self-coding account payment collection method provided by the above embodiment, and other technical features in the self-coding account payment collection device are the same as the features disclosed in the above embodiment method, which will not be repeated here.
[0135] The present application provides a self-encoding account payment collection device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the self-encoding account payment collection method in the above-mentioned embodiment one.
[0136] Reference below Figure 5 , which shows a schematic diagram of the structure of a self-coding account payment collection device suitable for implementing the embodiment of the present application. The self-coding account payment collection device in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 5 The self-encoding account payment device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.
[0137] like Figure 5As shown, the self-coding account payment collection device may include a processing device 1001 (e.g., a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 1002 or a program loaded from a storage device 1003 to a random access memory (RAM: Random Access Memory) 1004. Various programs and data required for the operation of the self-coding account payment collection device are also stored in the RAM 1004. The processing device 1001, the ROM 1002, and the RAM 1004 are connected to each other via a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to the I / O interface 1006: input devices 1007 including, for example, a touch screen, a touchpad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; output devices 1008 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; storage devices 1003 including, for example, a magnetic tape, a hard disk, etc.; and communication devices 1009. The communication device 1009 can allow the self-encoding account payment collection device to communicate wirelessly or wired with other devices to exchange data. Although the figure shows a self-encoding account payment collection device with various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems may be implemented or have alternatively.
[0138] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.
[0139] The self-coding account payment collection device provided by the present application adopts the self-coding account payment collection method in the above embodiment, which can solve the technical problem of self-coding account payment collection. Compared with the prior art, the beneficial effects of the self-coding account payment collection device provided by the present application are the same as the beneficial effects of the self-coding account payment collection method provided by the above embodiment, and the other technical features in the self-coding account payment collection device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.
[0140] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.
[0141] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.
[0142] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, and the computer-readable program instructions are used to execute the self-encoding account payment collection method in the above-mentioned embodiment.
[0143] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination of the above.
[0144] The computer-readable storage medium may be included in the self-encoding account payment receiving device; or may exist independently without being assembled into the self-encoding account payment receiving device.
[0145] The computer-readable storage medium carries one or more programs. When the one or more programs are executed by the self-encoding account payment collection device, the self-encoding account payment collection device:
[0146] Obtain enterprise account data;
[0147] Based on the enterprise account data, a plurality of enterprise payment codes are generated, wherein any enterprise payment code is bound to a corresponding customer;
[0148] A mapping relationship is established between the enterprise account data and each of the enterprise payment codes, and payment is collected from each of the customers using the enterprise payment code.
[0149] Computer program code for performing the operations of the present application may be written in one or more programming languages or a combination thereof, including object-oriented programming languages such as Java, Smalltalk, C++, and conventional procedural programming languages such as "C" or similar programming languages. The program code may be executed entirely on the client computer, partially on the client computer, as a separate software package, partially on the client computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the client computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).
[0150] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.
[0151] The modules involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the module does not constitute a limitation on the unit itself in some cases.
[0152] The readable storage medium provided in this application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned self-coding account payment collection method, and can solve the technical problem of self-coding account payment collection. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as the beneficial effects of the self-coding account payment collection method provided in the above-mentioned embodiment, and will not be repeated here.
[0153] The present application also provides a computer program product, including a computer program, which implements the steps of the self-encoding account payment collection method as described above when executed by a processor.
[0154] The computer program product provided by this application can solve the technical problem of self-coding account collection. Compared with the prior art, the beneficial effects of the computer program product provided by this application are the same as the beneficial effects of the self-coding account collection method provided by the above embodiment, which will not be repeated here.
[0155] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.
Claims
1. A self-coding account payment method, characterized in that: The method comprises: Obtain enterprise account data; Based on the enterprise account data, a plurality of enterprise payment codes are generated, wherein any enterprise payment code is bound to a corresponding customer; A mapping relationship is established between the enterprise account data and each of the enterprise payment codes, and payment is collected from each of the customers using the enterprise payment code.
2. The method according to claim 1, characterized in that The step of generating a plurality of enterprise payment codes based on the enterprise account data comprises: Obtain customer coding quantity and coding requirements; Based on the coding requirement and the corporate account data, a corporate payment code corresponding to the customer coding quantity is generated.
3. The method according to claim 2, characterized in that Before the step of establishing a mapping relationship between the enterprise account data and each of the enterprise payment codes, the method further includes: Evenly distribute each of the enterprise payment codes to multiple customers; Bind each of the customers with the corresponding allocated enterprise payment code to obtain a plurality of binding relationship data, and store the binding relationship data in a preset payment database.
4. The method according to claim 1, characterized in that After the step of collecting payment from each of the customers using the enterprise payment code, the method further includes: Extracting payment data from each of the enterprise payment codes; Based on the mapping relationship, each payment data is transmitted to the enterprise account data to collect statistics on the payment data of each customer.
5. The method according to claim 1, characterized in that The step of collecting payment from each of the customers using the enterprise payment code comprises: determining the payment pattern of each of said customers; When it is determined that the payment mode is a code scanning mode, displaying a payment code to the customer, and receiving payment data fed back by the customer through the payment code; In the case where it is determined that the payment mode is a transfer mode, opening the transfer authority of the customer and receiving the transfer data of the customer paying the enterprise payment code; In the case where it is determined that the payment mode is the gesture scanning payment mode, detecting a gesture image of the customer; When the gesture image meets a preset image standard, a preset amount of payment data is deducted from the customer's account.
6. The method according to claim 1, characterized in that The step of collecting payment from each of the customers using the enterprise payment code also includes: Sending a payment request to each of the customers through the enterprise payment code; Receiving a payment instruction sent by the customer based on the payment request, and determining whether the payment amount in the payment instruction is less than a preset threshold; When it is determined that the payment amount is less than a preset threshold, the account of each of the customers is deducted, and the deduction amount is recorded in the enterprise payment code.
7. A self-coding account payment device, characterized in that: The device comprises: The acquisition module is used to obtain enterprise account data; A generating module, configured to generate a plurality of enterprise payment codes based on the enterprise account data, wherein any enterprise payment code is bound to a corresponding customer; The payment collection module is used to establish a mapping relationship between the enterprise account data and each of the enterprise payment codes, and to collect payment from each of the customers using the enterprise payment code.
8. A self-coding account payment device, characterized in that: The device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the self-encoding account payment collection method according to any one of claims 1 to 6.
9. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the self-encoding account payment collection method as described in any one of claims 1 to 6 are implemented.
10. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the steps of the self-encoding account payment collection method according to any one of claims 1 to 6 are implemented.