Method and device for generating payment code
The method enhances payment codes by incorporating merchant and user-specific data, addressing the limitation of existing codes to convey only basic payment information, thereby improving user experience and flexibility.
Patent Information
- Application Number
- JP2023543427
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2021-01-19
- Filing Date
- 2021-08-20
- Publication Date
- 2024-11-07
- Estimated Expiration
- 2041-08-20
AI Technical Summary
Existing payment codes lack the ability to convey additional information beyond basic payment details, such as merchant or user-specific information, limiting their functionality.
A method and apparatus for generating payment codes that include additional information by obtaining and integrating merchant or user-specific data, such as risk information, complaint history, and account status, into the payment code generation process.
Enables the display of enhanced information on payment codes, increasing their flexibility and improving user experience by providing valuable insights to both merchants and users.
Smart Images

Figure 0007579456000004 
Figure 0007579456000005 
Figure 0007579456000006
Abstract
Description
[Technical field]
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority from a Chinese patent application filed with the China Patent Office on January 19, 2021, bearing application number 202110069523.1, and entitled "Method and apparatus for generating payment codes," the entire disclosure of which is incorporated herein by reference.
[0002] FIELD OF THE DISCLOSURE The present invention relates to the field of computer technology, and more particularly to a method and apparatus for generating a payment code. [Background technology]
[0003] Payment codes are used as a means of payment in online payment software. For example, at places of consumption such as convenience stores, shops, and restaurants, when a user shows his / her mobile phone at checkout, the merchant can use an infrared barcode scanner to scan the one-dimensional barcode displayed on the user's mobile phone and start the checkout. When switching to a QR code, the other party can scan it using a mobile phone or special device to start the transaction.
[0004] In existing code scanning processes, the displayed code (QR Code) usually carries the required payment account information (scanned) or order information (main scan), i.e., the payment code has a single function since it only carries payment information. The color and background color of the payment code are fixed, and no further information about the merchant or personal account can be obtained from the payment code. Summary of the Invention [Problem to be solved by the invention]
[0005] SUMMARY OF THE PRESENT EMBODIMENTS The present invention provides a method and apparatus for generating a payment code to solve the problem that additional information cannot be provided due to insufficient information in the payment code. [Means for solving the problem]
[0006] The technical solutions provided in the present invention are as follows:
[0007] In one aspect, a method for generating a payment code provided by an embodiment of the present invention includes: receiving a payment code generation request including an identifier of a payment-related object transmitted from a terminal; obtaining payment information of the payment-related object and an associated feature identifier of the payment-related object based on the identifier of the payment-related object; determining ancillary information of the payment-related object based on an ancillary feature identifier of the payment-related object; A payment code generation response is generated based on the payment information and auxiliary information of the payment-related object, and the payment code generation response is sent to the terminal, causing the terminal to generate a payment code based on the payment code generation response.
[0008] Optionally, the identifier of the payment-related object is a merchant identifier, and the associated feature identifier of the payment-related object includes at least a system preset feature identifier; The step of obtaining payment information of the payment-related object and an associated feature identifier of the payment-related object based on the identifier of the payment-related object includes: sending a first payment code information acquisition request to a merchant management server based on the merchant identifier; receiving a first payment code information acquisition response including payment information corresponding to the merchant identifier transmitted from the merchant management server; and determining a corresponding system preset feature identifier based on the merchant identifier.
[0009] Optionally, the identifier of the payment-related object is a user identifier, and the associated feature identifier of the payment-related object includes a system preset feature identifier and a custom feature identifier; The step of obtaining payment information of the payment-related object and an associated feature identifier of the payment-related object based on the identifier of the payment-related object includes: sending a second payment code information acquisition request to a user management server based on the user identifier; acquiring a second payment code information acquisition response transmitted from the user management server; determining a corresponding system preset feature identifier based on the user identifier; The second payment code information acquisition response includes payment information and a custom feature identifier corresponding to the user identifier, and the custom feature identifier corresponding to the user identifier is determined according to a user's operation on a configuration interface of a terminal.
[0010] Optionally, the step of determining ancillary information of the payment-related object based on an ancillary feature identifier of the payment-related object further comprises: receiving attribute characteristic information of the payment-related object transmitted from an information management server corresponding to the payment-related object; storing the ancillary feature information; and converting the ancillary feature information into the ancillary information.
[0011] Optionally, before receiving the attribute characteristic information of the payment-related object transmitted from the information management server corresponding to the payment-related object, further, generating a request for obtaining characteristic information based on the associated characteristic identifier of the payment-related object; transmitting the characteristic information acquisition request to the information management server; The step of receiving attribute characteristic information of the payment-related object transmitted from an information management server corresponding to the payment-related object includes: The method includes a step of receiving a characteristic information acquisition response including auxiliary characteristic information of the payment-related object transmitted from the information management server.
[0012] Optionally, the step of converting the ancillary feature information into the ancillary information comprises: determining a corresponding information attachment rule according to the attached feature identifier of the payment-related object; The method includes a step of comparing the auxiliary characteristic information with the information attachment rules to obtain auxiliary information.
[0013] In another aspect, a method for generating a payment code provided by an embodiment of the present invention includes: generating a payment code generation request in response to a payment code generation operation triggered on the payment interface, the payment code generation request including an identifier of a payment-related object; transmitting the payment code generation request to a payment code server, so that the payment code server determines payment information and auxiliary information of a payment-related object based on the payment code generation request; receiving a payment code generation response including the payment information and auxiliary information of the payment-related object transmitted from the payment code server; The method includes a step of generating and displaying a payment code based on the payment information and the auxiliary information.
[0014] Optionally, the identifier of the payment-related object is a user identifier, and the attached information is determined by the payment code server based on a system preset feature identifier and a custom feature identifier; The method further comprises: displaying a configuration interface corresponding to the user identifier; retrieving a custom feature identifier corresponding to the user identifier in response to a user action triggered on a configuration interface; and sending a custom feature identifier corresponding to the user identifier to a user management server. Optionally, the step of generating a payment code based on the payment information and the auxiliary information includes: determining target ancillary information based on a priority corresponding to the ancillary information; determining a target generated code style corresponding to the target auxiliary information according to a correspondence relationship between the auxiliary information and the payment code style; generating a payment code based on the payment information, and displaying the payment code according to the target generated code style.
[0015] In another aspect, a payment code generating device provided by an embodiment of the present invention comprises: A first transceiver unit configured to receive a payment code generation request including an identifier of a payment-related object sent from a terminal; an acquiring unit configured to acquire payment information of the payment-related object and an associated feature identifier of the payment-related object based on the identifier of the payment-related object; a determining unit configured to determine ancillary information of the payment-related object based on an ancillary feature identifier of the payment-related object; a generating unit configured to generate a payment code generation response based on the payment information and ancillary information of the payment-related object; The first transceiver unit is further configured to send the payment code generation response to the terminal, thereby causing the terminal to generate a payment code based on the payment code generation response.
[0016] Optionally, the identifier of the payment-related object is a merchant identifier, and the associated feature identifier of the payment-related object includes at least a system preset feature identifier; The acquisition unit specifically includes: Sending a first payment code information acquisition request to a merchant management server based on the merchant identifier; receiving a first payment code information acquisition response including payment information corresponding to the merchant identifier transmitted from the merchant management server; Based on the merchant identifier, a corresponding system preset feature identifier is determined.
[0017] Optionally, the identifier of the payment-related object is a user identifier, and the associated feature identifier of the payment-related object includes a system preset feature identifier and a custom feature identifier; The acquisition unit specifically includes: Sending a second payment code information acquisition request to a user management server based on the user identifier; Obtain a second payment code information acquisition response sent from the user management server, the second payment code information acquisition response including payment information and a custom feature identifier corresponding to the user identifier, and the custom feature identifier corresponding to the user identifier is determined according to a user's operation on a configuration interface of a terminal; A corresponding system preset feature identifier is determined based on the user identifier.
[0018] Optionally, the determining unit specifically: receiving attribute characteristic information of the payment-related object transmitted from an information management server corresponding to the payment-related object; The auxiliary feature information is stored, and the auxiliary feature information is converted into the auxiliary information.
[0019] Optionally, the determining unit specifically: Generate a request for obtaining characteristic information based on the associated characteristic identifier of the payment-related object; Sending the characteristic information acquisition request to the information management server; A characteristic information acquisition response including auxiliary characteristic information of the payment-related object transmitted from the information management server is received.
[0020] Optionally, the determining unit specifically: Determine a corresponding information attachment rule according to the attached feature identifier of the payment-related object; The auxiliary feature information is compared with the information auxiliary rules to obtain auxiliary information.
[0021] In another aspect, a payment code generating device provided by an embodiment of the present invention comprises: a response unit configured to generate a payment code generation request in response to a payment code generation operation triggered on the payment interface, the payment code generation request including an identifier of the payment-related object; a second transceiver unit for transmitting the payment code generation request to a payment code server, so that the payment code server determines payment information and additional information of a payment-related object based on the payment code generation request, and receiving a payment code generation response including the payment information and additional information of the payment-related object transmitted from the payment code server; and a generating unit configured to generate and display a payment code based on the payment information and the ancillary information.
[0022] Optionally, the identifier of the payment-related object is a user identifier, and the attached information is determined by the payment code server based on a system preset feature identifier and a custom feature identifier; The response unit specifically displays a configuration interface corresponding to the user identifier, and responds to a user's operation triggered on the configuration interface to obtain a custom feature identifier corresponding to the user identifier; The second transceiver unit further sends a custom feature identifier corresponding to the user identifier to a user management server, so that the payment code server obtains the custom feature identifier from the user management server.
[0023] Optionally, the generating unit comprises: determining target ancillary information based on a priority order corresponding to the ancillary information; Determine a target generated code style corresponding to the target auxiliary information according to a correspondence relationship between the auxiliary information and the payment code style; The device is configured to generate a payment code based on the payment information and display the payment code according to a code style generated by the target.
[0024] In another aspect, an electronic device provided by an embodiment of the present invention comprises: a memory configured to store executable instructions; and a processor configured to read and execute executable instructions stored in the memory to perform the method described in any of the above embodiments.
[0025] In another aspect, an embodiment of the present invention provides a computer-readable storage medium, the instructions of which, when executed by a processor, cause the processor to perform a method as described in any of the above embodiments.
[0026] In another aspect, an embodiment of the present invention provides a computer program product comprising a computer program stored on a computer readable storage medium, said computer program comprising program instructions that, when executed by a computer, cause the computer to perform the steps of the method described in any of the above embodiments. Effect of the Invention
[0027] In an embodiment of the present invention, the terminal sends a payment code generation request to the server after receiving a user operation. The payment code generation request includes an identifier of a payment-related object, where the payment-related object can be a user or a merchant. After the server receives the payment code generation request, the server obtains payment information of the payment-related object and an associated feature identifier of the payment-related object according to the identifier of the payment-related object, and determines the associated information of the payment-related object according to the associated feature identifier of the payment-related object. The server generates a payment code generation response according to the payment information and the associated information of the payment-related object, sends the payment code generation response to the terminal, and lets the terminal generate a payment code according to the payment information and the associated information in the payment code generation response. In an embodiment of the present invention, in addition to displaying basic payment information through the payment code, the payment code can also be used to prompt the associated information of the payment-related object, such as merchant risk information, merchant complaint information, user credit information, and user account fund status. This allows the merchant or user to obtain more valuable information from the payment code, enhances the flexibility of using the payment code, and improves the user experience. [Brief description of the drawings]
[0028] [Figure 1] FIG. 2 is a schematic diagram of an application architecture of a method for generating a payment code in an embodiment of the present invention. [Diagram 2] FIG. 11 is a schematic diagram of another application architecture of the method for generating a payment code in an embodiment of the present invention. [Diagram 3] 4 is a schematic flowchart of generating a server-side payment code in an embodiment of the present invention. [Figure 4] FIG. 2 is a schematic diagram of a display mode of a payment code in an embodiment of the present invention. [Diagram 5] 10 is a schematic flowchart illustrating generation of a terminal-side payment code according to an embodiment of the present invention. [Figure 6]FIG. 1 is a schematic diagram of a system architecture in an embodiment of the present invention. [Figure 7] FIG. 2 is a schematic diagram of the logical architecture of a server in an embodiment of the present invention. [Figure 8] FIG. 2 is a schematic diagram of the logical architecture of a terminal in an embodiment of the present invention; [Figure 9] FIG. 2 is a schematic diagram of the physical architecture of a computer device according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0029] In order to clarify the purpose, technical solution and advantages of the embodiments of the present invention, the technical solution of the embodiments of the present invention will be described clearly and completely below with reference to the drawings of the embodiments of the present invention. It is obvious that the described embodiments are only some of the embodiments of the present invention, and do not include all the embodiments. Based on the embodiments of the present invention, other embodiments obtained by those skilled in the art without creative work are all within the scope of protection of the present invention.
[0030] In one embodiment, the process of generating a payment code via a terminal can be applied to various application scenarios. Referring to FIG. 1, a schematic diagram of the application architecture of the method for generating a payment code in an embodiment of the present invention includes a server 100 and a terminal 200.
[0031] The terminal device 200 may be a mobile or stationary electronic device. For example, it may be a mobile phone, a tablet computer, a laptop computer, a desktop computer, various wearable devices, a smart TV, an in-vehicle device, or other electronic devices capable of implementing the above functions. The terminal device 200 includes a code generating device capable of generating a payment code according to payment information. The terminal device 200 may display an interface to a user via a display screen and receive a user operation on the interface. The terminal device 200 generates a request message based on a user operation, transmits the request message to the server 100, receives feedback from the server 100, and then displays the result to the user via a display screen.
[0032] The terminal device 200 and the server 100 may be connected via the Internet to realize intercommunication. Optionally, the Internet uses standard communication technologies and / or protocols. The Internet is typically the Internet, but any network may be used, including, but not limited to, any combination of Local Area Network (LAN), Metropolitan Area Network (MAN), Wide Area Network (WAN), mobile, wired or wireless networks, private networks, or virtual private networks. In some embodiments, data exchanged over the network is represented by technologies and / or formats including HyperText Mark-up Language (HTML), Extensible Markup Language (XML), and the like. Additionally, all or part of the link may be encrypted using conventional encryption technologies such as Secure Socket Layer (SSL), Transport Layer Security (TLS), Virtual Private Network (VPN), Internet Protocol Security (IPSec), and the like. In some other embodiments, custom and / or proprietary data communication technologies may be used instead of or in addition to the data communication technologies listed above.
[0033] The server 100 can provide various network services to the terminal device 200. The server 100 can use cloud computing technology to process information. The server 100 may be an independent physical server, a server cluster consisting of multiple physical servers, a distributed system, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, big data and artificial intelligence platforms. The terminal may be, but is not limited to, a smartphone, a tablet computer, a laptop computer, a desktop computer, a smart speaker, a smart watch, etc. The terminal and the server can be directly or indirectly connected via wired or wireless communication, which is not limited to the present invention.
[0034] For example, the server 100 may include a processor 110 (Central Processing Unit, CPU), a memory 120, an input device 130, and an output device 140. The input device 130 may include a keyboard, a mouse, a touch screen, etc. The output device 140 may include a display device such as a Liquid Crystal Display (LCD) or a Cathode Ray Tube (CRT).
[0035] The memory 120 includes a read only memory (ROM) and a random access memory (RAM), and can provide program instructions and data stored in the memory 120 to the processor 110. In the embodiment of the present invention, the memory 120 can be used to store a program of the method for generating a payment code in the embodiment of the present invention. Furthermore, the memory 120 in the embodiment of the present invention can be used to store all the information of related accounts.
[0036] The processor 110 calls program instructions stored in the memory 120, and the processor 110 is configured to perform steps of any method for generating a payment code in an embodiment of the present invention according to the retrieved program instructions.
[0037] In another application scenario of an embodiment of the present application, referring to FIG. 2, is a schematic diagram of another application architecture of the method for generating a payment code in an embodiment of the present application. The system architecture for generating a payment code includes a payment code server 201, a terminal 202, and an information management server 203. The terminal 202 can establish a connection with the payment code server 201 through a network 204 (such as a wired network or a wireless network), and the payment code server 201 can establish a connection with the information management server 203 through the network 204 (such as a wired network or a wireless network). Here, the information management server 203 may be an information management server in an external risk management system, such as a risk management system, a credit reporting system, an account management system, etc. The information management server 203 stores associated characteristic information about a user or a merchant. The associated characteristic information includes personal credit report information, merchant credit and evaluation information, personnel and economic investigation information, account balance information, etc. The payment code server 201 can obtain the above-mentioned attached characteristic information by sending a characteristic information acquisition request to the information management server 203, or the information management server 203 can actively push the attached characteristic information to the payment code server 201.
[0038] Some scenarios in which embodiments of the present invention may be applied are described below in combination with the above mentioned system architecture.
[0039] Personal consumption scenario: A user clicks on "payment code" on the terminal's app. The terminal generates a payment code generation request and sends the payment code generation request to the server. After receiving the payment code generation response, the terminal generates a payment code according to the payment information and determines the style of the payment code according to the attached information. The terminal displays the payment code according to the style. After seeing the code of a certain style, the user can know whether the accumulated consumption of the account is high, whether the credit card has been repaid on time, and other information. By scanning the merchant's "payment order code", it can check whether the merchant has any negative comments.
[0040] Principal-to-principal transfer scenario: When checking the recipient's "receipt code," the sender can check from the style of the code whether the recipient is registered as a specific person in the credit reporting system to avoid financial risks.
[0041] Epidemic prevention scenario: When a user is asked to display a health code, a payment code can be displayed on the terminal. The display mode of the payment code can be determined by the ancillary information, so like the health code, it is possible to determine whether the epidemic prevention standard is met according to the display mode of green, yellow, or red. This provides the effect of one code being used for multiple purposes.
[0042] Economic research scenario: After the user presents the "payment code", both the cashier and the cash register system can quickly identify and report according to the display of the payment code. In order to achieve the concealment effect, the display mode of the payment code in this scenario can also be set to normal, but the cash register system can read out the concealment information from the scanning result of the payment code and present the concealment information to the cashier.
[0043] In addition, the application architecture diagram in the embodiment of the present invention is intended to more clearly explain the technical solution in the embodiment of the present invention, and does not constitute a limitation of the technical solution provided by the embodiment of the present invention. In addition, the present invention is not limited to the above business application scenario, and the technical solution provided by the embodiment of the present invention can be applied to similar problems in other application architectures and business application scenarios.
[0044] Based on the above design concept, and referring to FIG. 3, the detailed process of generating a payment code on the server side in the embodiment of the present invention is as follows:
[0045] Step 301: The payment code server receives a payment code generation request including an identifier of a payment-related object sent from a terminal.
[0046] Step 302: The payment code server obtains the payment information of the payment-related object and the associated feature identifier of the payment-related object according to the identifier of the payment-related object.
[0047] Step 303: The payment code server determines auxiliary information of the payment-related object according to the auxiliary feature identifier of the payment-related object.
[0048] Step 304: The payment code server generates a payment code generation response based on the payment information and auxiliary information of the payment-related object, and sends the payment code generation response to the terminal, thereby causing the terminal to generate a payment code based on the payment code generation response.
[0049] In an embodiment of the present invention, after the terminal receives a user operation, it sends a payment code generation request to the payment code server. The payment code generation request includes an identifier of a payment-related object, where the payment-related object can be a user or a merchant. After the payment code server receives the payment code generation request, it obtains the payment information of the payment-related object and the associated feature identifier of the payment-related object according to the identifier of the payment-related object, and determines the associated information of the payment-related object according to the associated feature identifier of the payment-related object. The payment code server generates a payment code generation response according to the payment information and the associated information of the payment-related object, sends the payment code generation response to the terminal, and lets the terminal generate a payment code according to the payment information and the associated information in the payment code generation response. In an embodiment of the present invention, in addition to displaying basic payment information through the payment code, the payment code can also be used to prompt the associated information of the payment-related object, such as merchant risk information, merchant complaint information, user credit information, and user account fund status. This allows the merchant or user to obtain more valuable information from the payment code, increase the flexibility of the use of the payment code, and improve the user experience.
[0050] The payment code in the embodiment of the present invention can be applied to different modes, including a main scan mode and a scan mode. Here, in the main scan mode, the merchant presents the payment code to the user, and the color and shape of the payment code displayed by the merchant can prompt the user whether the merchant is a high-risk merchant or a merchant with a high complaint rate. In the scan mode, the user displays the payment code to the merchant, and the user can use different color and shape payment code display methods to display account balance status, credit card repayment information, whether the monthly cumulative consumption is excessive, and other information. For risk accounts or special accounts, the system-defined reserved color takes precedence over the user-defined settings.
[0051] There are two code scanning modes:
[0052] In the main scan mode, the identifier of the payment related object is a merchant identifier, and the associated feature identifier of the payment related object includes a system preset feature identifier.
[0053] Next, the step of the payment code server acquiring payment information of the payment-related object and an associated feature identifier of the payment-related object based on the identifier of the payment-related object includes: sending a first payment code information acquisition request to a merchant management server based on the merchant identifier; receiving a first payment code information acquisition response including payment information corresponding to the merchant identifier transmitted from the merchant management server; and determining a corresponding system preset feature identifier based on the merchant identifier.
[0054] In one embodiment, after receiving the payment code generation request sent from the terminal, the server determines that the current payment code is the main scan mode according to the merchant identifier in the payment code generation request. Then, it is necessary to obtain the payment information of the merchant from the merchant management server corresponding to the merchant. Since the payment information of the merchant is uniformly stored and managed by the merchant management server, the payment code server can send a first payment code information acquisition request to the merchant management server. Then, the merchant management server obtains the corresponding payment information based on the merchant identifier and generates a first payment code information acquisition response. After receiving the first payment code information acquisition response sent from the merchant management server, the payment code server can obtain the payment information corresponding to the merchant from the first payment code information acquisition response.
[0055] Furthermore, since the relevant characteristics of a merchant are generally uniformly defined by the system, the payment code server can directly obtain the preset characteristic identifier of the corresponding system according to the merchant identifier.
[0056] For example, the payment code server sends a first payment code information acquisition request to the merchant management server. The first payment code information acquisition request includes the merchant ID to acquire account information of the merchant ID. The merchant management server returns the default or designated account of the merchant ID through the first payment code information acquisition response. After acquiring the account, the payment code server sends the default or designated account to a terminal. Then, the terminal generates a payment code based on the default or designated account. At the same time, the payment code server further determines a preset characteristic identifier (i.e., a payment code generation parameter of the merchant) of the corresponding system based on the merchant ID. The payment code generation parameter here is uniformly defined by the system. The payment code server collects auxiliary information from an external system based on the payment code generation parameter.
[0057] In the scan mode, the identifier of the payment related object is a user identifier, and the associated feature identifiers of the payment related object include system preset feature identifiers and custom feature identifiers.
[0058] Next, the step of the payment code server acquiring payment information of the payment-related object and an associated feature identifier of the payment-related object based on the identifier of the payment-related object, sending a second payment code information acquisition request to a user management server based on the user identifier; acquiring a second payment code information acquisition response transmitted from the user management server; and determining a corresponding system preset feature identifier based on the user identifier.
[0059] The second payment code information acquisition response includes payment information and a custom feature identifier corresponding to the user identifier, and the custom feature identifier corresponding to the user identifier is determined according to a user's operation on a configuration interface of a terminal.
[0060] In one embodiment, after receiving the payment code generation request sent from the terminal, the server needs to determine that the current payment code is in scan mode based on the user identifier, and obtain the user's payment information from the user management server corresponding to the user. Since the user's payment information is uniformly stored and managed by the user management server, the payment code server can send a second payment code information acquisition request to the user management server. The user management server obtains corresponding payment information based on the user identifier, and generates a second payment code information acquisition response. After receiving the second payment code information acquisition response sent from the user management server, the payment code server may obtain the payment information corresponding to the user from the second payment code information acquisition response.
[0061] In another aspect, unlike the merchant's accessory features defined by the system, the user's accessory features can also be customized by the user, so that the payment code server not only directly obtains the corresponding system's preset feature identifier according to the user identifier, but also obtains the user's custom feature identifier through a second payment code information acquisition request.
[0062] For example, the payment code server sends a second payment code information acquisition request including a user ID to the user management server to acquire account information of the user ID. The user management server returns the default or specified card number of the user ID through the second payment code information acquisition response. After acquiring the card number, the payment code server sends the card number to the terminal. Then, the terminal can generate a payment code based on the card number. At the same time, the second payment code information acquisition response further includes a custom feature identifier. The custom feature identifier corresponding to the user identifier is determined according to the user's operation on the configuration interface of the terminal. That is, the user performs an operation on the configuration interface of the terminal in advance, and the terminal determines the user's custom feature according to the user's operation and sends the custom feature identifier to the user management server. In this way, when the user management server receives the second payment code information acquisition request, it can add the custom feature identifier of the user to the second payment code information acquisition response and send it to the payment code server. Therefore, by sending the second payment code information acquisition request, the payment code server can acquire both the payment information and the custom feature identifier.
[0063] In addition, the user's attached feature identifier also includes the system's preset feature identifier. The payment code server determines the corresponding system's preset feature identifier (i.e., the user's payment code generation parameter) based on the user ID. The payment code generation parameter is uniformly defined by the system. The payment code server collects the user's attached information from the external system based on the payment code generation parameter.
[0064] For example, in a payment APP, a user will usually bind multiple card numbers or payment accounts, so the payment code can be set for all accounts of the user or for one account of the user. Table 1 shows the settings of the additional features of all accounts of the user. One prompt item corresponds to one additional feature. The features with the note "uniformly defined by the system" are system preset features, and the features with the note "defined by the user" are user custom features.
[0065] [Table 1]
[0066] Table 2 shows the user's single account custom feature settings. Features marked with "Uniformly defined by the system" are system preset features, and features marked with "User defined" are user custom features.
[0067] [Table 2]
[0068] The settlement code setting for all accounts has a higher priority than the settlement code setting for a single account. The system preset features defined uniformly by the system have a higher priority than the user custom features. Different feature prompt item numbers are assigned to prompt items by the system, and the numbers are globally unique.
[0069] In addition, one payment code display style is set corresponding to each prompt item in Table 1 or 2, and its attributes may include code color, shape, center image, frame, background color, etc., and the attributes can be extended. The payment code display style is as shown in Figure 4.
[0070] The payment code display style defined uniformly in the system cannot be changed by users, but users can set their own customized payment code display style. To facilitate user identification, the central screen of the payment code in Figure 4 can be defined as various common warning screens, similar to the warning screens on the dashboard of a car. The code shape can be square, circular, etc., and the border can be defined as whether it is displayed or not, and the displayed color. The payment code display style supports user personalization and improves the user experience.
[0071] The auxiliary feature information in the embodiment of the present invention may be collected in advance and then stored in the payment code server, or may be collected in real time after the payment code server receives a request sent from the terminal. Preferably, in order to reduce the time consumed in the payment code generation process, the payment code server stores the collected information in a cache such as Redis in the form of key-values.
[0072] Furthermore, in an embodiment of the present invention, the manner in which the settlement code server obtains the ancillary information includes active pull and passive push, and both pull and push can include batch and real-time manner.
[0073] Here, in the case of passive push, the step of determining the auxiliary information of the payment-related object based on the auxiliary feature identifier of the payment-related object by the payment code server includes: receiving attribute characteristic information of the payment-related object transmitted from an information management server corresponding to the payment-related object; storing the ancillary feature information; and converting the ancillary feature information into the ancillary information.
[0074] In one embodiment, information such as personal credit information, commercial credit, and evaluation, which is updated infrequently and has high risk, can be obtained by pushing in bulk from an external system. The HTTP message may take effect immediately or may be loaded in the form of a file and take effect periodically. Information with high timeliness requirements, such as merchant risk and the risk of illegal transfer of funds from an account, can be pushed in real time by the external risk management system and immediately received by the settlement code server to take effect.
[0075] In the active pull mode, before receiving the attached characteristic information of the payment-related object transmitted from the information management server corresponding to the payment-related object, the payment code server further Generate a request for obtaining characteristic information based on the associated characteristic identifier of the payment-related object; The characteristic information acquisition request is transmitted to the information management server.
[0076] The step of receiving, by the payment code server, the attribute characteristic information of the payment-related object transmitted from the information management server corresponding to the payment-related object, specifically includes: The method includes a step of receiving a characteristic information acquisition response including auxiliary characteristic information of the payment-related object transmitted from the information management server.
[0077] In one embodiment, the payment code server can periodically batch-query and pull information from the bank or institution on whether the credit card bill has been paid, depending on the credit card billing period. If information such as the user's account balance is missing, the payment code server can query the bank or institution when the code is generated to obtain real-time balance information.
[0078] The payment code server may also store information such as local statistics, ie cumulative reminders of consumption within a cycle.
[0079] In addition, the payment code server needs to process the collected original information and convert it into a data format that can be read directly. Then, the step of converting the postponed auxiliary characteristic information into the auxiliary information includes: determining a corresponding information attachment rule according to the attached feature identifier of the payment-related object; The method includes a step of comparing the auxiliary characteristic information with the information attachment rules to obtain auxiliary information.
[0080] In one embodiment, the payment code server can obtain the additional feature information from the external network system server in advance and cache the additional feature information. After receiving the payment code generation request sent from the terminal, the payment code server queries the additional feature information in the cache according to the user ID and the additional feature identifier in the request, and determines the corresponding information attachment rule, such as the configuration information of the payment code items shown in Table 1 or Table 2. Based on the configuration information, the additional feature information is calculated according to the judgment condition, and a calculation result of YES or NO is obtained. After all the prompt items are calculated, they are incorporated into the overall structure as additional information.
[0081] Then, the payment code server assembles the payment information and the auxiliary information into a response message according to the user settings, and sends it back to the terminal. The payment code server fills in the display requirements according to the user settings, fills in the response message with the numbers of each prompt item and the corresponding payment code style, and completes the basic information for generating the payment code, and then returns the response message to the terminal.
[0082] The display requirements written in the response message can be divided into the following cases: (1) displaying the payment codes in one style, that is, displaying the payment codes according to the prompt items with higher priority, and (2) scrolling and presenting all payment codes that meet the conditions in the order of priority.
[0083] As shown in FIG. 5, the detailed process of generating a payment code on the terminal side based on the above-mentioned terminal operation process in the embodiment of the present invention is as follows.
[0084] Step 501: The terminal generates a payment code generation request including an identifier of a payment-related object in response to a payment code generation operation triggered on a payment interface.
[0085] Step 502: The terminal transmits the payment code generation request to the payment code server, thereby causing the payment code server to determine payment information and auxiliary information of a payment-related object based on the payment code generation request.
[0086] Step 503: The terminal receives a payment code generation response including the payment information and auxiliary information of the payment-related object transmitted from the payment code server.
[0087] Step 504: The terminal generates and displays a payment code based on the payment information and the auxiliary information.
[0088] In one embodiment, the terminal sends a payment code generation request to the server after receiving a user operation. The payment code generation request includes an identifier of a payment-related object, where the payment-related object can be a user or a merchant. After the server receives the payment code generation request, the server obtains payment information of the payment-related object and an associated feature identifier of the payment-related object based on the identifier of the payment-related object, and determines the associated information of the payment-related object based on the associated feature identifier of the payment-related object. The server generates a payment code generation response based on the payment information and the associated information of the payment-related object, sends the payment code generation response to the terminal, and lets the terminal generate a payment code based on the payment information and the associated information in the payment code generation response. In an embodiment of the present invention, in addition to displaying basic payment information through the payment code, the payment code can also be used to prompt the associated information of the payment-related object, such as merchant risk information, merchant complaint information, user credit information, and user account fund status. This allows the merchant or user to obtain more valuable information from the payment code, increase the flexibility of the use of the payment code, and improve the user experience.
[0089] Further, the identifier of the payment-related object is a user identifier, and the ancillary information is determined by the payment code server based on a system's preset feature identifiers and custom feature identifiers.
[0090] and before the terminal generates a payment code generation request in response to a payment code generation operation triggered on the payment interface, the payment code generation request including an identifier of a payment-related object, further comprising: The terminal displays a configuration interface corresponding to the user identifier; The terminal obtains a custom feature identifier corresponding to the user identifier in response to a user operation triggered on a configuration interface; The terminal transmits a custom feature identifier corresponding to the user identifier to a user management server, so that the payment code server obtains the custom feature identifier from the user management server.
[0091] In one embodiment, not only the system preset features for the user's attached features are directly determined by the system, but also the custom features corresponding to the user subset can be preset by the user. The custom feature identifier corresponding to the user identifier is determined according to the user's operation on the configuration interface of the terminal. That is, the user performs an operation on the configuration interface of the terminal in advance, and the terminal determines the user's custom features according to the user's operation and sends the custom feature identifier to the user management server. In this way, when the user management server receives the second payment code information acquisition request, it can add the custom feature identifier of the user to the second payment code information acquisition response and send it to the payment code server. Therefore, by sending the second payment code information acquisition request, the payment code server can obtain both the payment information and the custom feature identifier.
[0092] Therefore, the payment code server can not only directly obtain the preset feature identifier of the corresponding system based on the user identifier, but also obtain the user's custom feature identifier through the second payment code information acquisition request.
[0093] Furthermore, the step of generating a payment code based on the payment information and the auxiliary information includes: determining target ancillary information based on a priority corresponding to the ancillary information; determining a target generated code style corresponding to the target auxiliary information according to a correspondence relationship between the auxiliary information and the payment code style; generating a payment code based on the payment information, and displaying the payment code according to the target generated code style.
[0094] In one embodiment, a code generator is provided in the terminal, and the code generator generates a payment code in a target generation code style from the information in the received response message according to the definition of the interface specification. The payment code server provides the code generator with an SDK development kit to quickly integrate various types of terminals.
[0095] Here, the code generation interface specification has various definitions such as fixed field format, TLV format, etc. An embodiment of the present invention is illustrated by the TLV format shown in Table 3.
[0096] [Table 3]
[0097] With reference to the system architecture shown in Figure 6, the following uses a specific application scenario to further describe the interactive process between the terminal and the server in the above embodiment. A code generating device is disposed in the terminal, and the payment code server includes a payment code service device, an information conversion device, and an information collection and storage device. The above process is as follows:
[0098] The code generating device initiates a code generation request to the payment code service device according to the user ID.
[0099] The payment code service device requests account information for a user ID from the user system, and the user system returns the default or specified account or card number for the user ID or a specified payment, as well as custom parameters for code generation predefined by the user.
[0100] The payment code service device requests auxiliary information for code generation from the information conversion device based on the custom parameters for code generation.
[0101] The information collection and storage device collects information on user-specified payment defaults or specified account or card numbers periodically or in real time in response to a request, and returns the information to the information conversion device.
[0102] The information conversion device converts and processes the collected auxiliary information for code generation according to custom parameters for user code generation, and notifies, for example, a credit card outstanding reminder and the generated code style, whether the monthly cumulative consumption is excessive, the generated code style, etc., and the priority number of these prompt information, and returns the above information to the payment code service device.
[0103] The payment code service device embeds the information necessary for code generation and the service information in an interface message and returns the message to the code generation device.
[0104] The code generation device determines whether there is prompt information that satisfies the conditions according to the priority of the auxiliary information, and if there is no prompt information that satisfies the conditions, generates a default code, and if there is, generates a code based on the code style (color, shape, etc.) generated according to the prompt information. Depending on the user's settings, it can present only the information with the highest priority, or it can present all prompt information that satisfies the conditions sequentially at a fixed time interval.
[0105] Based on the same inventive idea, referring to FIG. 7, based on the same inventive idea, an embodiment of the present invention provides a payment code generating device (eg, a server), including at least:
[0106] The payment code generating device includes: A first transceiver unit 701 configured to receive a payment code generation request including an identifier of a payment-related object sent from a terminal; an acquiring unit 702 configured to acquire payment information of the payment-related object and an associated feature identifier of the payment-related object based on the identifier of the payment-related object; A determining unit 703 configured to determine ancillary information of the payment-related object based on an ancillary feature identifier of the payment-related object; and a generating unit 704 configured to generate a payment code generation response based on the payment information and ancillary information of the payment-related object.
[0107] The first transceiver unit 701 further sends the payment code generation response to the terminal, thereby causing the terminal to generate a payment code according to the payment code generation response.
[0108] Optionally, the identifier of the payment-related object is a merchant identifier and the associated feature identifier of the payment-related object includes at least a system preset feature identifier.
[0109] The acquiring unit specifically sends a first payment code information acquiring request to a merchant management server according to the merchant identifier; receiving a first payment code information acquisition response including payment information corresponding to the merchant identifier transmitted from the merchant management server; Based on the merchant identifier, a corresponding system preset feature identifier is determined.
[0110] Optionally, the identifier of the payment-related object is a user identifier, and the associated feature identifiers of the payment-related object include a system pre-set feature identifier and a custom feature identifier.
[0111] Specifically, the acquiring unit sends a second payment code information acquiring request to a user management server based on the user identifier, and acquires a second payment code information acquiring response sent from the user management server.
[0112] The second payment code information acquisition response includes payment information and a custom feature identifier corresponding to the user identifier, and the custom feature identifier corresponding to the user identifier is determined according to a user's operation on a configuration interface of a terminal.
[0113] A corresponding system preset feature identifier is determined based on the user identifier.
[0114] Optionally, the determination unit specifically receives auxiliary feature information of the payment-related object sent from an information management server corresponding to the payment-related object, stores the auxiliary feature information, and converts the auxiliary feature information into the auxiliary information.
[0115] Optionally, the determination unit specifically generates a feature information acquisition request based on an associated feature identifier of the payment-related object, sends the feature information acquisition request to the information management server, and receives a feature information acquisition response including the associated feature information of the payment-related object sent from the information management server.
[0116] Optionally, the determining unit specifically determines a corresponding information attachment rule according to the attached feature identifier of the payment-related object, and compares the attached feature information with the information attachment rule to obtain attached information.
[0117] Based on the same inventive idea, as shown in FIG. 8, a payment code generating device (e.g., a terminal) provided in an embodiment of the present invention comprises: A response unit 801 configured to generate a payment code generation request including an identifier of a payment-related object in response to a payment code generation operation triggered on the payment interface; a second transceiver unit 802 for sending the payment code generation request to a payment code server, so that the payment code server determines payment information and auxiliary information of a payment-related object according to the payment code generation request; and a generating unit 803 configured to generate and display a payment code based on the payment information and the ancillary information.
[0118] The second transceiver unit 802 is configured to receive a payment code generation response sent from the payment code server, the payment code generation response including the payment information and auxiliary information of the payment-related object.
[0119] Optionally, the identifier of the payment-related object is a user identifier, and the associated information is determined by the payment code server based on a system's preset feature identifiers and custom feature identifiers.
[0120] The response unit 801 is specifically configured to display a configuration interface corresponding to the user identifier, respond to a user's operation triggered on the configuration interface, and obtain a custom feature identifier corresponding to the user identifier.
[0121] The second transceiver unit 802 further sends a custom feature identifier corresponding to the user identifier to a user management server, so that the payment code server obtains the custom feature identifier from the user management server.
[0122] Optionally, the generating unit 803 is determining target ancillary information based on a priority order corresponding to the ancillary information; Determine a target generated code style corresponding to the target auxiliary information according to a correspondence relationship between the auxiliary information and the payment code style; A payment code is generated based on the payment information, and the payment code is displayed according to a code style generated by the target.
[0123] Based on the same inventive idea, as shown in FIG. 9, an embodiment of the present invention further provides a computer device 1400. The computer device 1400 may be an electronic device such as a smartphone, a tablet computer, a laptop computer, or a PC. As shown in FIG. 9, the computer device 1400 includes a display unit 1440, a processor 1480, and a memory 1420. Here, the display unit 1440 includes a display panel 1441 configured to display information input by a user or information provided by a user and various object selection pages of the computer device 1400, etc. In an embodiment of the present invention, the display panel 1441 is mainly configured to display pages, shortcut windows, etc. of applications installed in the computer device 1400. Optionally, the display panel 1441 may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), etc. The computer device 1400 can execute any of the methods executed by a terminal or a processing server in the various embodiments described above.
[0124] The processor 1480 is configured to read a computer program and then execute a method defined by the computer program. For example, the processor 1480 reads a social application program, executes the application on the computer device 1400, and displays a page of the application on the display unit 1440. The processor 1480 may include one or more general-purpose processors, and may further include one or more digital signal processors (DSPs). The digital signal processor is configured to perform operations related to implementing the technical solutions provided by the embodiments of the present invention.
[0125] The memory 1420 generally includes an internal memory and an external memory, and the internal memory may be a random access memory (RAM), a read only memory (ROM), a cache (CACHE), etc. The external memory may be a hard disk, an optical disk, a USB disk, a floppy disk, a tape drive, etc. The memory 1420 is configured to store computer programs and other data, and the computer programs may include application programs corresponding to applications, etc., and the other data may include data generated after the execution of an operating system or an application program. Here, the data includes system data (e.g., operating system configuration parameters, etc.) and user data. In an embodiment of the present invention, program instructions are stored in the memory 1420, and the processor 1480 executes the program instructions stored in the memory 1420 to realize any method performed by the terminal or processing server described above.
[0126] Further, the computer device 1400 may further include a display unit 1440 configured to receive inputted numerical information, character information, or contact touch operation / non-contact gesture, and generate signal input related to user settings and function control of the computer device 1400. Specifically, in an embodiment of the present invention, the display unit 1440 may include a display panel 1441. The display panel 1441 is, for example, a touch screen that can collect a user's touch operation (e.g., an operation on or near the display panel 1441 using a finger, a stylus, or any suitable object or accessory) and drive a corresponding connected device according to a pre-set program. In addition, the display panel 1441 may include two parts: a touch detection device and a touch controller. The touch detection device detects the user's touch direction, detects a signal generated from the touch operation, and transmits the signal to the touch controller. The touch controller can receive touch information from the touch detection device, convert it into contact coordinates, transmit it to the processor 1480, and receive and execute instructions transmitted from the processor 1480.
[0127] Here, the display panel 1441 can be implemented in various types, such as resistive, capacitive, infrared, surface acoustic wave, etc. In addition to the display unit 1440, the computing device 1400 can also include an input unit 1430, which can include, but is not limited to, one or more of a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, etc. In FIG. 9, the input unit 1430 includes an image input device 1431 and another input device 1432 as an example.
[0128] In addition, the computing device 1400 may also include a power supply 1490 for supplying power to other modules, an audio circuit 1460, a near-field communication module 1470, and an RF circuit 1410. The computing device 1400 may also include one or more sensors 1450, such as an acceleration sensor, a light sensor, a pressure sensor, etc. The audio circuit 1460 specifically includes a speaker 1461 and a microphone 1462, etc. For example, a user can use voice control. When the user needs to be prompted, the computing device 1400 can collect the user's voice through the microphone 1462, control with the user's voice, and play the corresponding prompt tone through the speaker 1461.
[0129] Based on the same inventive idea, an embodiment of the present invention provides a computer-readable storage medium, which, when instructions in the computer-readable storage medium are executed by a processor, enables the processor to execute any method executed by the terminal or processing server in the embodiment.
[0130] Alternatively, the computer-readable medium may be a non-transitory computer-readable storage medium, for example, a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.
[0131] Based on the same inventive idea, an embodiment of the present invention provides a computer program product or a computer program, the computer program product or the computer program comprising computer instructions, the computer instructions being stored in a computer-readable storage medium, a processor of the computer device reading the computer instructions from the computer-readable storage medium, and the processor executing the computer instructions, thereby enabling the computer device to perform any of the methods performed by the terminal or the processing server in the above embodiments.
[0132] The program product may use any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable signal medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or apparatus, or any combination thereof. More specific examples of readable storage media (not an exhaustive list) include an electrical connection having one or more wires, a portable 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 thereof.
[0133] The program product of the embodiment of the present invention may be implemented on a portable compact disk read only memory (CD-ROM), contain program code, and be executed on a computing device. However, the program product of the present invention is not limited thereto. In this specification, a readable storage medium may be any tangible medium that contains or stores a program, where the program can be used by or in combination with an instruction execution system, device, or apparatus.
[0134] A readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with readable program code borne therein. Such a propagated data signal may be in many forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination thereof. A readable signal medium may be a readable medium other than a readable storage medium, where the readable medium may transmit, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device.
[0135] The program code contained in the readable medium may be transmitted via any suitable medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination thereof.
[0136] Based on the same inventive idea, an embodiment of the present invention provides a computer program product, the computer program product including a computer program stored on a computer-readable storage medium, the computer program including program instructions, which when executed by a computer, cause the computer to perform the steps of the method for generating a payment code.
[0137] Although the preferred embodiments of the present invention have been described above, those skilled in the art, once acquiring the basic creative concept, may make additional modifications and variations to these embodiments. Therefore, it is intended that the appended claims be construed to include the preferred embodiments as well as all modifications and variations that fall within the scope of the present invention.
[0138] It is apparent that those skilled in the art can make various modifications and variations to the present invention without departing from the spirit and scope of the present invention. Therefore, the present invention is intended to include these modifications and variations as long as they fall within the scope of the claims of the present invention and their equivalents. [Explanation of symbols]
[0139] 100 Servers 110 Processor 120 Memory 130 Input Device 140 Output Device 200 Terminal Equipment 701 First transmitting / receiving unit 702 Acquired Units 703 Decision Unit 704 Generator Unit 801 Response Unit 802 Second Transceiver Unit 803 Generator Unit 1410 RF circuit 1420 Memory 1430 Input section 1431 Input Device 1432 Other input devices 1440 display unit 1441 Display Panel 1450 Sensor 1460 Audio Circuit 1470 Near-field communication module 1480 Processor 1490 Power supply
Claims
1. A method for generating a payment code to be applied to a payment code server, comprising: receiving a payment code generation request including an identifier of a payment-related object transmitted from a terminal; obtaining payment information of the payment-related object and an associated feature identifier of the payment-related object based on the identifier of the payment-related object; determining ancillary information of the payment-related object based on an ancillary feature identifier of the payment-related object; generating a payment code generation response based on the payment information and auxiliary information of the payment-related object, and transmitting the payment code generation response to the terminal, thereby causing the terminal to generate a payment code based on the payment code generation response; the identifier of the payment-related object is a merchant identifier, and the associated feature identifier of the payment-related object includes at least a system preset feature identifier; The step of obtaining payment information of the payment-related object and an associated feature identifier of the payment-related object based on the identifier of the payment-related object includes: transmitting a first payment code information acquisition request to a merchant management server based on the merchant identifier; receiving a first payment code information acquisition response including payment information corresponding to the merchant identifier transmitted from the merchant management server; determining a preset feature identifier of a corresponding system based on the merchant identifier; or The identifier of the payment-related object is a user identifier, and the associated feature identifiers of the payment-related object include a system preset feature identifier and a custom feature identifier; The step of obtaining payment information of the payment-related object and an associated feature identifier of the payment-related object based on the identifier of the payment-related object includes: sending a second payment code information acquisition request to a user management server based on the user identifier; acquiring a second payment code information acquisition response transmitted from the user management server; determining a corresponding system preset feature identifier based on the user identifier; The second payment code information acquisition response includes payment information and a custom feature identifier corresponding to the user identifier, and the custom feature identifier corresponding to the user identifier is determined according to a user's operation on a configuration interface of a terminal.
2. determining additional information of the payment-related object based on an additional feature identifier of the payment-related object, receiving attribute characteristic information of the payment-related object transmitted from an information management server corresponding to the payment-related object; 2. The method for generating a payment code according to claim 1, further comprising the steps of: storing the auxiliary characteristic information; and converting the auxiliary characteristic information into the auxiliary information.
3. before receiving attribute characteristic information of the payment-related object transmitted from an information management server corresponding to the payment-related object; generating a request for obtaining characteristic information based on the associated characteristic identifier of the payment-related object; and transmitting the characteristic information acquisition request to the information management server, The step of receiving attribute characteristic information of the payment-related object transmitted from an information management server corresponding to the payment-related object includes: The method for generating a payment code according to claim 2, further comprising a step of receiving a characteristic information acquisition response including auxiliary characteristic information of the payment-related object transmitted from the information management server.
4. The step of converting the auxiliary feature information into the auxiliary information includes: determining a corresponding information attachment rule according to the attached feature identifier of the payment-related object; The method for generating a payment code according to claim 2, further comprising a step of comparing the auxiliary characteristic information with the information auxiliary rule to obtain auxiliary information.
5. A method for generating a payment code to be applied to a terminal, comprising: generating a payment code generation request in response to a payment code generation operation triggered on the payment interface, the payment code generation request including an identifier of a payment-related object; transmitting the payment code generation request to a payment code server, so that the payment code server determines payment information and auxiliary information of a payment-related object based on the payment code generation request; receiving a payment code generation response including the payment information and auxiliary information of the payment-related object transmitted from the payment code server; generating and displaying a payment code based on the payment information and the auxiliary information; The identifier of the payment-related object is a user identifier, and the attached information is determined by the payment code server based on a system preset feature identifier and a custom feature identifier; before generating a payment code generation request in response to a payment code generation operation triggered on the payment interface, the payment code generation request including an identifier of a payment-related object; displaying a configuration interface corresponding to the user identifier; retrieving a custom feature identifier corresponding to the user identifier in response to a user action triggered on a configuration interface; sending a custom feature identifier corresponding to the user identifier to a user management server; A method for generating a payment code, characterized in that the custom feature identifier is included in a second payment code information acquisition response and sent to the payment code server after the user management server receives a second payment code information acquisition request from the payment code server.
6. The step of generating a payment code based on the payment information and the auxiliary information includes: determining target ancillary information based on a priority corresponding to the ancillary information; determining a target generated code style corresponding to the target auxiliary information according to a correspondence relationship between the auxiliary information and the payment code style; 6. The method of claim 5, further comprising: generating a payment code based on the payment information; and displaying the payment code according to the target generated code style.
7. A payment code generation device applied to a payment code server, comprising: A first transceiver unit configured to receive a payment code generation request including an identifier of a payment-related object sent from a terminal; an acquiring unit configured to acquire payment information of the payment-related object and an associated feature identifier of the payment-related object based on the identifier of the payment-related object; a determining unit configured to determine ancillary information of the payment-related object based on an ancillary feature identifier of the payment-related object; a generating unit configured to generate a payment code generation response based on the payment information and ancillary information of the payment-related object; The first transceiver unit further transmits the payment code generation response to the terminal, thereby causing the terminal to generate a payment code based on the payment code generation response; the identifier of the payment-related object is a merchant identifier, and the associated feature identifier of the payment-related object includes at least a system preset feature identifier; The acquiring unit acquires payment information of the payment-related object and an associated feature identifier of the payment-related object based on the identifier of the payment-related object, Transmitting a first payment code information acquisition request to a merchant management server based on the merchant identifier; receiving a first payment code information acquisition response including payment information corresponding to the merchant identifier transmitted from the merchant management server; determining a corresponding system preset feature identifier based on the merchant identifier; or The identifier of the payment-related object is a user identifier, and the associated feature identifiers of the payment-related object include a system preset feature identifier and a custom feature identifier; The determining unit obtains payment information of the payment-related object and an associated feature identifier of the payment-related object based on the identifier of the payment-related object, Sending a second payment code information acquisition request to a user management server based on the user identifier; acquiring a second payment code information acquisition response transmitted from the user management server; determining a corresponding system preset feature identifier based on the user identifier; The second payment code information acquisition response includes payment information and a custom feature identifier corresponding to the user identifier, and the custom feature identifier corresponding to the user identifier is determined according to a user's operation on a configuration interface of a terminal.
8. A device for generating a payment code to be applied to a terminal, comprising: a response unit configured to generate a payment code generation request in response to a payment code generation operation triggered on the payment interface, the payment code generation request including an identifier of the payment-related object; a second transceiver unit configured to send the payment code generation request to a payment code server; a generating unit configured to generate and display a payment code based on the payment information and the ancillary information; The second transceiver unit is further configured to receive a payment code generation response including the payment information and auxiliary information of the payment-related object transmitted from the payment code server; The identifier of the payment-related object is a user identifier, and the attached information is determined by the payment code server based on a system preset feature identifier and a custom feature identifier; before the response unit generates a payment code generation request including an identifier of a payment-related object in response to a payment code generation operation triggered on the payment interface, the response unit displays a configuration interface corresponding to the user identifier; and The response unit responds to a user's operation triggered on a configuration interface to obtain a custom feature identifier corresponding to the user identifier; The second transceiver unit transmits a custom feature identifier corresponding to the user identifier to a user management server; A payment code generation device characterized in that the custom feature identifier is included in a second payment code information acquisition response and sent to the payment code server after the user management server receives a second payment code information acquisition request from the payment code server.
9. An electronic device applied to a payment code server, a memory configured to store executable instructions; and a processor configured to read and execute executable instructions stored in the memory to perform the method of any one of claims 1 to 4.
10. A computer-readable storage medium applied to a payment code server, comprising: A computer-readable storage medium, the instructions of which, when executed by a processor, cause the processor to perform the method of any one of claims 1 to 4.
11. A computer program product applied to a payment code server, comprising: The computer program product comprises a computer program stored on a computer-readable storage medium, the computer program comprising program instructions which, when executed by a computer, cause the computer to perform a method according to any one of claims 1 to 4.
Citation Information
Patent Citations
Payment code generation method and device
CN113159757A
Settlement support system, settlement support device, settlement support method, and program
JP2020166896A
Scan and pay method and apparatus for use with a mobile device
JP2020513622A
Transaction authorization based on transaction, time, and geolocation dependent optical machine-readable codes
US20200074442A1
Transaction mediation method
US20200193405A1
