CN109947994B - Payment process processing method, device, medium and electronic equipment - Google Patents
Payment process processing method, device, medium and electronic equipment Download PDFInfo
- Publication number
- CN109947994B CN109947994B CN201810914348.XA CN201810914348A CN109947994B CN 109947994 B CN109947994 B CN 109947994B CN 201810914348 A CN201810914348 A CN 201810914348A CN 109947994 B CN109947994 B CN 109947994B
- Authority
- CN
- China
- Prior art keywords
- payment
- response message
- field
- target field
- request message
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/80—Information retrieval; Database structures therefor; File system structures therefor of semi-structured data, e.g. markup language structured data such as SGML, XML or HTML
- G06F16/84—Mapping; Conversion
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Accounting & Taxation (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Finance (AREA)
- General Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the invention provides a payment process processing method, a payment process processing device, a computer readable medium and electronic equipment, wherein the payment process processing method comprises the following steps: receiving payment request parameters; calling a request message template, mapping fields of the payment request parameters, and generating a payment request message; calling a payment channel interface to obtain a payment response message according to the payment request message; and calling a response message template, carrying out field mapping on the payment response message, and generating a mapped payment response message so as to complete the processing of the payment process. The technical scheme of the embodiment of the invention avoids the repeated development of interfaces of different payment channels through the field mapping between the message template and the relevant parameters of the actual payment process, so that the payment processes of different payment channels can be managed and maintained in a centralized manner, and meanwhile, the flexibility of aggregated payment is improved.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a payment process processing method, a payment process processing device, a payment process processing medium and electronic equipment.
Background
With the development of scientific technology and the increase of the demand of people for payment convenience, the internet payment channel is more and more popular with users. However, due to the increase of the variety of internet payment channels, certain inconvenience is brought to consumers and merchants. For example, if a user in an off-line store wants to include various internet payment channels, a two-dimensional code mobile consumer corresponding to each internet payment channel needs to be provided for code scanning payment, and meanwhile, the terminal of a store owner needs to be provided with collection software of each internet payment channel prop. Thus, to satisfy the consumer payment experience and merchant checkout convenience, aggregated payment is generated. Aggregation payment aggregates multiple payment channel modes into one payment mode.
In the prior art, a manner of aggregating a plurality of payment channels by aggregating payment is as follows: different payment channels are provided with different docking interfaces, and for the same payment task, the docking interfaces of different payment channels use different program codes. Meanwhile, for the newly added payment channel, program codes need to be redeveloped for each payment task.
However, the prior art approach of aggregating payments to aggregate multiple payment channels is tedious in development and maintenance tasks.
It is to be noted that the information disclosed in the above background section is only for enhancement of understanding of the background of the present invention and therefore may include information that does not constitute prior art known to a person of ordinary skill in the art.
Disclosure of Invention
Embodiments of the present invention provide a payment process processing method, a payment process processing apparatus, a computer-readable medium, and an electronic device, so as to overcome, at least to a certain extent, the problem of complex development and maintenance tasks in a manner of aggregating payment and aggregating multiple payment channels in the prior art.
Additional features and advantages of the invention will be set forth in the detailed description which follows, and in part will be obvious from the description, or may be learned by practice of the invention.
According to a first aspect of the embodiments of the present invention, there is provided a method for processing a payment process, including:
receiving payment request parameters;
calling a request message template, mapping fields of the payment request parameters, and generating a payment request message;
calling a payment channel interface to obtain a payment response message according to the payment request message;
and calling a response message template, carrying out field mapping on the payment response message, and generating a mapped payment response message so as to complete the processing of the payment process.
In some embodiments of the present invention, invoking a request message template, performing field mapping of the payment request parameter, and generating a payment request message includes:
acquiring a field to be mapped in the request message template as a first target field;
acquiring a field corresponding to the first target field in the payment request parameter as a second target field;
and converting the attribute of the second target field into the attribute of the first target field to generate the payment request message.
In some embodiments of the invention, the request message template is in a first programming language format;
before converting the attribute of the second target field into the attribute of the first target field, the method further comprises:
converting the second target field to the first programming language format.
In some embodiments of the present invention, invoking a response packet template, performing field mapping on the payment response packet, and generating a mapped payment response packet includes:
acquiring a field to be mapped in the response message template as a third target field;
acquiring a field corresponding to the third target field in the payment response message as a fourth target field;
and converting the attribute of the fourth target field into the attribute of the third target field to generate the mapped payment response message.
In some embodiments of the invention, the payment request parameter is an object of a second programming language;
after converting the attribute of the fourth target field into the attribute of the third target field, the method further comprises:
and analyzing the mapped payment response message to obtain the object of the second programming language.
In some embodiments of the present invention, the mapped payment response message is in an XML format, and the second programming language format is a Java Bean;
analyzing the mapped payment response message to obtain the object of the second programming language, including:
and the payment request parameter is an object of Java Bean, and the mapped payment response message is analyzed through JAXB to obtain the object of the second programming language.
In some embodiments of the present invention, before invoking the request message template, the method further includes:
and adding the request message template into a configuration file.
In some embodiments of the present invention, invoking a request message template, performing field mapping of the payment request parameter, and generating a payment request message includes:
when the payment request parameters are received, calling the configuration file;
and based on the configuration file, realizing field mapping of the payment request parameters through a template engine library, and generating a payment request message.
In some embodiments of the present invention, before invoking the response packet template, the method further includes:
and adding the response message template into a configuration file.
In some embodiments of the present invention, invoking a response message template, performing field mapping on the payment response message, and generating a mapped payment response message includes:
when the payment response message is received, calling the configuration file;
and based on the configuration file, realizing field mapping of the payment response message through a template engine library, and generating the mapped payment response message.
In some embodiments of the present invention, the payment request parameters include M types of payment request parameters, each type of payment request parameter corresponds to a payment channel, where M is a positive integer.
According to a second aspect of the embodiments of the present invention, there is provided a processing apparatus for a payment process, including:
a receiving module for receiving payment request parameters;
the first mapping module is used for calling a request message template, carrying out field mapping on the payment request parameters and generating a payment request message;
the calling module is used for calling a payment channel interface to acquire a payment response message according to the payment request message;
and the second mapping module is used for calling a response message template, carrying out field mapping on the payment response message and generating a mapped payment response message so as to finish the processing of the payment process.
According to a third aspect of embodiments of the present invention, there is provided a computer readable medium having stored thereon a computer program which, when executed by a processor, implements the method of processing a payment process as described in the first aspect of the embodiments above.
According to a fourth aspect of an embodiment of the present invention, there is provided an electronic apparatus including: one or more processors; storage means for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to implement a method of processing a payment process as described in the first aspect of the embodiments above.
The technical scheme provided by the embodiment of the invention has the following beneficial effects:
in the technical solutions provided by some embodiments of the present invention, a payment request message for calling a payment channel interface is generated by calling a request message template and performing field mapping on a payment request parameter; and after the payment response message is acquired according to the payment request message, calling a response message template, and further performing field mapping on the payment response message, thereby completing the processing of the payment process corresponding to the payment request parameter. According to the payment process processing method provided by the embodiment of the invention, through field mapping between the message template and the relevant parameters of the actual payment process, repeated development of interfaces of different payment channels is avoided, so that the payment processes of different payment channels can be managed and maintained in a centralized manner, and meanwhile, the flexibility of aggregated payment is improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention, as claimed.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention. It is obvious that the drawings in the following description are only some embodiments of the invention, and that for a person skilled in the art, other drawings can be derived from them without inventive effort. In the drawings:
FIG. 1 shows a flow diagram of a processing method of a payment process according to an embodiment of the invention;
FIG. 2 shows a block diagram of a processing method of a payment process according to an embodiment of the invention;
FIG. 3 is a flowchart illustrating a method for generating a payment request message by field mapping according to an embodiment of the invention;
FIG. 4 is a flowchart illustrating a method of generating a payment request message via field mapping according to another embodiment of the invention;
FIG. 5 is a flowchart illustrating a method for field mapping a payment response packet according to an embodiment of the invention;
FIG. 6 is a flowchart illustrating a method for field mapping a payment response packet according to another embodiment of the invention;
FIG. 7 shows a flow diagram of a method of processing a payment process according to another embodiment of the invention;
fig. 8 shows a schematic configuration of a processing means of a payment process according to an embodiment of the invention;
FIG. 9 illustrates a schematic structural diagram of a computer system suitable for use with the electronic device to implement an embodiment of the invention.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art.
Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to provide a thorough understanding of embodiments of the invention. One skilled in the relevant art will recognize, however, that the invention may be practiced without one or more of the specific details, or with other methods, components, devices, steps, and so forth. In other instances, well-known methods, devices, implementations or operations have not been shown or described in detail to avoid obscuring aspects of the invention.
The block diagrams shown in the figures are functional entities only and do not necessarily correspond to physically separate entities. I.e. these functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor means and/or microcontroller means.
The flowcharts shown in the figures are illustrative only and do not necessarily include all of the contents and operations/steps, nor do they necessarily have to be performed in the order described. For example, some operations/steps may be decomposed, and some operations/steps may be combined or partially combined, so that the actual execution sequence may be changed according to the actual situation.
In the aggregated payment, for the same payment task, such as a unified ordering task, the codes in the interfaces of different payment channels are different in the message format of the request message/response and the field name in the message, and the codes in other parts are the same. In the prior art, codes are re-developed through interfaces corresponding to payment channels. However, the prior art approach of aggregating payments to aggregate multiple payment channels is tedious in development and maintenance tasks.
Fig. 1 shows a flow diagram of a processing method of a payment process according to an embodiment of the present invention, which overcomes at least to some extent the problem of the tedious development and maintenance task in the prior art approach of aggregating payments into a plurality of payment channels. Referring to fig. 1, the method includes:
step S101, receiving payment request parameters;
step S102, calling a request message template, carrying out field mapping on the payment request parameters, and generating a payment request message;
step S103, calling a payment channel interface to obtain a payment response message according to the payment request message;
and step S104, calling a response message template, mapping the field of the payment response message, and generating a mapped payment response message so as to complete the processing of the payment process.
In the technical solution provided in the embodiment shown in fig. 1, a payment request message for calling a payment channel interface is generated by calling a request message template and performing field mapping on a payment request parameter; and after the payment response message is acquired according to the payment request message, calling a response message template, and further performing field mapping on the payment response message, thereby completing the processing of the payment process corresponding to the payment request parameter. According to the payment process processing method provided by the embodiment of the invention, through field mapping between the message template and the relevant parameters of the actual payment process, repeated development of interfaces of different payment channels is avoided, so that the payment processes of different payment channels can be managed and maintained in a centralized manner, and meanwhile, the flexibility of aggregated payment is improved.
Fig. 2 shows a frame schematic diagram of a processing method of a payment process according to an embodiment of the present invention, and a specific implementation manner of each step in fig. 1 is described in detail below with reference to fig. 2:
referring to fig. 2, in an exemplary embodiment, the payment request parameter 21 received in step S101 includes M types of payment request parameters, where each type of payment request parameter 21 corresponds to a payment channel, and M is a positive integer. When M is greater than or equal to 2, the codes of the interfaces of different payment channels in M are different in message format of request message/response, field name in message, and the like, and the codes of other parts are the same.
In an exemplary embodiment, in step S102, a request message template is called, field mapping of the payment request parameter is performed, and a payment request message is generated.
Fig. 3 is a flowchart illustrating a method for generating a payment request message through field mapping according to an embodiment of the present invention, and referring to fig. 3, the method includes:
step S301, adding the request message template into a configuration file.
Step S302, when the payment request parameters are received, the configuration file is called;
step S303, based on the configuration file, the field mapping of the payment request parameter is realized through a template engine library, and a payment request message is generated.
With continued reference to fig. 2, by storing the request message template 221 in the unified configuration file 22, when each payment channel executes the program of its own interface, it can call the configuration file 22 to obtain the request message template 221. Further, based on the configuration file, a unified message generation tool (e.g., a template engine library) is used to implement field mapping 222 on the payment request parameters 21, so as to generate a payment request message 23. The request message template 221 is centrally managed by the configuration center, which is beneficial to conveniently calling the request message template and is beneficial to the light weight of the whole program.
Illustratively, the template engine library may be Stringtemplate.
Fig. 4 is a flowchart illustrating a method for generating a payment request message through field mapping according to another embodiment of the present invention, and referring to fig. 4, the method includes:
step S401, acquiring a field to be mapped in the request message template as a first target field;
step S402, acquiring a field corresponding to the first target field in the payment request parameter as a second target field;
step S403, converting the attribute of the second target field into the attribute of the first target field to generate the payment request packet.
The following code example briefly describes the flow of the method for generating a payment request message through field mapping shown in fig. 4:
the output is: < xml > < payID > $123456 $/xml >
Here, "< xml > < payID > $ payID > </xml >" is the request message template in step S301, the attribute of the first target field may be represented by "$ payID $" in the request message template, and "123456" may be represented by the attribute of the second target field corresponding to the first target field obtained from the payment request parameter. Converting the attribute of the second target field into the attribute of the first target field to generate the payment request message: < xml > < payID > $123456 $/xml >.
In an exemplary embodiment, if the request message template is in the first programming language format, the second target field is converted into the first programming language format before step S403. That is to say, in the process of invoking the request message template to perform the field mapping of the payment request parameter to generate the payment request message, the method provided by the present application not only includes the conversion of the corresponding field attribute, but also needs to unify the format of the programming language of the corresponding field in the request message parameter into the format of the programming language of the request message template. So as to facilitate the execution and management of the generated message requesting payment.
With continued reference to fig. 2, in an exemplary embodiment, after obtaining the payment request message based on the method provided in fig. 3 and/or fig. 4, in step S103, a bottom layer payment channel interface is called through an HTTPS/JSF protocol, so that the interface of the payment channel returns a response message 24 according to the request message.
In an exemplary embodiment, in step S104, a response message template is called, field mapping of the payment response parameter is performed, and a mapped payment request message is generated.
Fig. 5 is a schematic flowchart illustrating a method for field mapping a payment response packet according to an embodiment of the present invention, and referring to fig. 5, the method includes:
step S501, add the request message template to a configuration file.
Step S502, when the payment response message is received, the configuration file is called;
step S503, based on the configuration file, the field mapping of the payment response message is realized through a template engine library, and the mapped payment response message is generated.
With continued reference to fig. 2, by storing the response message template 223 in the unified configuration file 22, when each payment channel executes the program of its own interface, it can call the configuration file 22 to obtain the response message template 223. Further, based on the configuration file 22, a field mapping of the payment response message 24 is implemented by a unified message generation tool (e.g., a template engine library), and a mapped payment response message 25 is generated. The response message template 223 is centrally managed by the configuration center, which is beneficial to conveniently calling the response message template 223 and is beneficial to the whole light weight of the program.
Illustratively, the template engine library may be StringTemplate.
Fig. 6 is a flowchart illustrating a method for field mapping a payment response packet according to another embodiment of the present invention, and referring to fig. 6, the method includes:
step S601, acquiring a field to be mapped in the response message template as a third target field;
step S602, a field corresponding to the third target field is obtained in the payment response message and is a fourth target field;
step S603, converting the attribute of the fourth target field into the attribute of the third target field to generate the mapped payment response packet.
The specific implementation process of each step in the embodiment shown in fig. 6 is similar to the specific implementation manner of each step in the embodiment shown in fig. 4, and reference may be specifically made to the embodiment shown in fig. 4, which is not described herein again.
In an exemplary embodiment, if the payment request parameter is an object in the second programming language, after step S603, the mapped payment response packet is parsed to obtain the object in the second programming language. That is, the method provided by the present application, in the processing of the payment process, not only includes the conversion of the corresponding field attribute, but also needs to analyze the payment response message into the programming language format consistent with the payment request parameter. So as to facilitate the use of the mapped payment response message in the payment process.
Fig. 7 shows a flow diagram of a processing method of a payment process according to another embodiment of the invention. Referring to fig. 7, the method includes:
step S701, receiving payment request parameters;
step S702, acquiring a field to be mapped in the request message template as a first target field;
step S703, acquiring a field corresponding to the first target field in the payment request parameter as a second target field;
step S704, the request message template is in an XML format, and the second target field is converted into the XML format;
step S705, converting the attribute of the second target field into the attribute of the first target field to generate a payment request message in an XML format;
step S706, according to the payment request message in the XML format, calling a payment channel interface to obtain a payment response message in the XML format;
step S707, acquiring a field to be mapped in the response message template as a third target field;
step S708, a field corresponding to the third target field is acquired in the XML-formatted payment response message as a fourth target field;
step S709, converting the attribute of the fourth target field into the attribute of the third target field to generate the mapped payment response packet, where the mapped payment response packet is in an XML format;
and step S710, the payment request parameter is an object of the Java Bean, and the mapped payment response message is analyzed through JAXB to obtain the object of the Java Bean.
In an exemplary embodiment, the specific implementation manner of step S701 is the same as that of step S101, and is not described herein again.
In the exemplary embodiment, steps S702 to S705 are a specific implementation manner of step S102. Step S702-step S705 are also a concrete representation of the embodiment shown in fig. 3.
Specifically, in step S704, if the request packet template is in an XML format, the second target field is converted into the XML format. Further, in step S705, a payment request message in XML format is generated. In the method provided by the application, in the process of calling the request message template to map the fields of the payment request parameters to generate the payment request message, the conversion of the attributes of the corresponding fields is included, and the formats of the programming languages of the corresponding fields in the request message parameters need to be unified into the format of the programming language of the request message template. So as to facilitate the execution and management of the generated message requesting payment.
In an exemplary embodiment, in step S706, according to the payment request message in the XML format, a payment channel interface is invoked to obtain a payment response message in the XML format.
In an exemplary embodiment, steps S707-S710 are a specific implementation of step S103. Step S707-step S710 are also a concrete expression of the embodiment shown in fig. 5.
Specifically, in step S709, the obtained mapped payment response packet is also in the XML format. Meanwhile, if the payment request parameter is an object of the Java Bean, after step S709, analyzing the mapped payment response message of the XML through JAXB to obtain the object of the Java Bean. That is to say, in the method provided by the present application, the processing of the payment process includes not only the conversion of the corresponding field attribute, but also the parsing of the payment response message into the programming language format consistent with the payment request parameter. So as to facilitate the use of the mapped payment response message in the payment process.
Embodiments of the apparatus of the present invention are described below, which may be used to perform the above-described payment processing methods of the present invention.
Fig. 8 shows a schematic configuration of a processing device of a payment process according to an embodiment of the invention. The processing device 800 for the payment process includes: a receiving module 801, a first mapping module 802, a calling module 803, and a second mapping module 804.
Wherein, the receiving module 801 is configured to receive a payment request parameter; the first mapping module 802 is configured to invoke a request message template, perform field mapping on the payment request parameter, and generate a payment request message; the calling module 803 is configured to call a payment channel interface to obtain a payment response message according to the payment request message; the second mapping module 804 is configured to invoke a response message template, perform field mapping on the payment response message, and generate a mapped payment response message, so as to complete processing of the payment process.
In an exemplary embodiment, the first mapping module 802 includes: an acquisition unit and a conversion unit.
The acquiring unit is used for acquiring a field to be mapped in the request message template as a first target field; the acquisition unit is further used for acquiring a field corresponding to the first target field in the payment request parameter as a second target field; the conversion unit is used for converting the attribute of the second target field into the attribute of the first target field so as to generate the payment request message.
In an exemplary embodiment, the request message template is in a first programming language format; the conversion unit is further configured to convert the second target field into the first programming language format.
In an exemplary embodiment, the second mapping module 804 includes: an acquisition unit and a conversion unit.
The acquiring unit is used for acquiring a field to be mapped in the response message template as a third target field; the acquisition unit is further configured to acquire a field corresponding to the third target field as a fourth target field in the payment response message; and the conversion unit is used for converting the attribute of the fourth target field into the attribute of the third target field so as to generate the mapped payment response message.
In an exemplary embodiment, the second mapping module 804 further includes: and an analysis unit. The payment request parameter is an object of a second programming language, and the analysis unit is used for analyzing the mapped payment response message and acquiring the object of the second programming language.
In an exemplary embodiment, the mapped payment response message is in an XML format, and the second programming language format is a Java Bean; the parsing unit is specifically configured to parse the mapped payment response packet to obtain an object of the second programming language, and includes:
and the payment request parameter is an object of Java Bean, and the mapped payment response message is analyzed through JAXB to obtain the object of the second programming language.
In an exemplary embodiment, the processing device 800 of the payment process further comprises: a first adding module. The first adding module is used for adding the request message template into a configuration file.
In an exemplary embodiment, the first mapping module 802 includes: a calling unit and a mapping unit.
The calling unit is used for calling the configuration file when receiving the payment request parameter; and the mapping unit is used for realizing field mapping of the payment request parameters through a template engine library based on the configuration file and generating a payment request message.
In an exemplary embodiment, the processing device 800 of the payment process further comprises: and a second adding module. And the second adding module is used for adding the response message template into a configuration file.
In an exemplary embodiment, the second mapping module 804 includes: a calling unit and a mapping unit.
The calling unit is used for calling the configuration file when receiving the payment response message; and the mapping unit is used for realizing field mapping of the payment response message through a template engine library based on the configuration file and generating the mapped payment response message.
In an exemplary embodiment, the payment request parameters include M types of payment request parameters, and each type of payment request parameter corresponds to one payment channel, where M is a positive integer.
For details which are not disclosed in the embodiments of the apparatus of the present invention, reference is made to the above-described embodiments of the processing method of the payment process of the present invention for the details which are not disclosed in the embodiments of the apparatus of the present invention, since the respective functional modules of the processing apparatus of the payment process of the present invention correspond to the steps of the above-described exemplary embodiments of the processing method of the payment process.
Referring now to FIG. 9, shown is a block diagram of a computer system 900 suitable for use in implementing an electronic device of an embodiment of the present invention. The computer system 900 of the electronic device shown in fig. 9 is only an example, and should not bring any limitations to the function and the scope of the use of the embodiments of the present invention.
As shown in fig. 9, the computer system 900 includes a Central Processing Unit (CPU) 901 that can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM) 902 or a program loaded from a storage section 908 into a Random Access Memory (RAM) 903. In the RAM 903, various programs and data necessary for system operation are also stored. The CPU 901, ROM 902, and RAM 903 are connected to each other via a bus 904. An input/output (I/O) interface 905 is also connected to bus 904.
The following components are connected to the I/O interface 905: an input portion 906 including a keyboard, a mouse, and the like; an output section 907 including components such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 908 including a hard disk and the like; and a communication section 909 including a network interface card such as a LAN card, a modem, or the like. The communication section 909 performs communication processing via a network such as the internet. The drive 910 is also connected to the I/O interface 905 as necessary. A removable medium 911 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 910 as necessary, so that a computer program read out therefrom is mounted into the storage section 908 as necessary.
In particular, according to an embodiment of the present invention, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the invention include a computer program product comprising a computer program embodied on a computer-readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication section 909 and/or installed from the removable medium 911. The above-described functions defined in the system of the present application are executed when the computer program is executed by a Central Processing Unit (CPU) 901.
It should be noted that the computer readable medium shown in the present invention can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, 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 disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present invention, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units described in the embodiments of the present invention may be implemented by software, or may be implemented by hardware, and the described units may also be disposed in a processor. Wherein the names of the elements do not in some way constitute a limitation on the elements themselves.
As another aspect, the present application also provides a computer-readable medium, which may be contained in the electronic device described in the above embodiments; or may exist separately without being assembled into the electronic device. The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to implement the processing method of the payment process as described in the above embodiments.
For example, the electronic device may implement the following as shown in fig. 1: step S101, receiving payment request parameters; step S101, calling a request message template, mapping fields of the payment request parameters, and generating a payment request message; step S103, calling a payment channel interface to obtain a payment response message according to the payment request message; and step S104, calling a response message template, mapping the field of the payment response message, and generating a mapped payment response message so as to complete the processing of the payment process.
As another example, the electronic device may implement the steps shown in fig. 7.
It should be noted that although in the above detailed description several modules or units of the device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functions of two or more modules or units described above may be embodied in one module or unit according to an embodiment of the invention. Conversely, the features and functions of one module or unit described above may be further divided into embodiments by a plurality of modules or units.
Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiment of the present invention can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, a touch terminal, or a network device, etc.) to execute the method according to the embodiment of the present invention.
Other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the invention and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the invention being indicated by the following claims.
It will be understood that the invention is not limited to the precise arrangements that have been described above and shown in the drawings, and that various modifications and changes can be made without departing from the scope thereof. The scope of the invention is limited only by the appended claims.
Claims (12)
1. A method of processing a payment process, comprising:
receiving payment request parameters;
calling a request message template, mapping fields of the payment request parameters, and generating a payment request message;
calling a payment channel interface to obtain a payment response message according to the payment request message;
calling a response message template, carrying out field mapping on the payment response message, and generating a mapped payment response message to complete the processing of the payment process;
the calling of the request message template to perform field mapping of the payment request parameters and generate the payment request message comprises the following steps:
acquiring a field to be mapped in the request message template as a first target field;
acquiring a field corresponding to the first target field in the payment request parameter as a second target field;
converting the attribute of the second target field into the attribute of the first target field to generate the payment request message;
the request message template is in a first programming language format;
before converting the attribute of the second target field into the attribute of the first target field, the method further comprises:
converting the second target field to the first programming language format.
2. The method of claim 1, wherein invoking a response message template to perform field mapping of the payment response message and generate a mapped payment response message comprises:
acquiring a field to be mapped in the response message template as a third target field;
acquiring a field corresponding to the third target field in the payment response message as a fourth target field;
and converting the attribute of the fourth target field into the attribute of the third target field to generate the mapped payment response message.
3. The method of claim 2, wherein the payment request parameter is an object in a second programming language;
after converting the attribute of the fourth target field into the attribute of the third target field, the method further comprises:
and analyzing the mapped payment response message to obtain the object of the second programming language.
4. The method of claim 3, wherein the mapped payment response message is in XML format and the second programming language format is Java Bean;
analyzing the mapped payment response message to obtain the object of the second programming language, wherein the method comprises the following steps:
and the payment request parameter is an object of Java Bean, and the mapped payment response message is analyzed through JAXB to obtain an object of the second programming language.
5. The method according to any one of claims 1 to 4, further comprising, before invoking the request message template:
and adding the request message template into a configuration file.
6. The method of claim 5, wherein invoking a request message template to perform field mapping of the payment request parameters to generate a payment request message comprises:
when the payment request parameters are received, calling the configuration file;
and based on the configuration file, realizing field mapping of the payment request parameters through a template engine library, and generating a payment request message.
7. The method according to any one of claims 1 to 4, further comprising, before invoking the response message template:
and adding the response message template into a configuration file.
8. The method of claim 7, wherein invoking a response message template to perform field mapping of the payment response message and generate a mapped payment response message comprises:
when the payment response message is received, calling the configuration file;
and based on the configuration file, realizing field mapping of the payment response message through a template engine library, and generating the mapped payment response message.
9. The method of any one of claims 1 to 4, wherein the payment request parameters include M types of payment request parameters, each type of payment request parameter corresponding to a payment channel, wherein M is a positive integer.
10. A payment process processing apparatus, comprising:
a receiving module for receiving payment request parameters;
the first mapping module is used for calling a request message template, carrying out field mapping on the payment request parameters and generating a payment request message;
the calling module is used for calling a payment channel interface to acquire a payment response message according to the payment request message;
the second mapping module is used for calling a response message template, carrying out field mapping on the payment response message and generating a mapped payment response message so as to complete the processing of the payment process;
the calling of the request message template to perform field mapping of the payment request parameters and generate the payment request message comprises the following steps:
acquiring a field to be mapped in the request message template as a first target field;
acquiring a field corresponding to the first target field in the payment request parameter as a second target field;
converting the attribute of the second target field into the attribute of the first target field to generate the payment request message;
the request message template is in a first programming language format;
before converting the attribute of the second target field into the attribute of the first target field, the method further comprises:
converting the second target field to the first programming language format.
11. A computer-readable medium, on which a computer program is stored, which program, when being executed by a processor, carries out a method of processing a payment process according to any one of claims 1 to 9.
12. An electronic device, comprising:
one or more processors;
storage means for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to implement a method of processing a payment process as claimed in any one of claims 1 to 9.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810914348.XA CN109947994B (en) | 2018-08-10 | 2018-08-10 | Payment process processing method, device, medium and electronic equipment |
| PCT/CN2019/099502 WO2020029971A1 (en) | 2018-08-10 | 2019-08-06 | Processing method and device for payment process, medium and electronic device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810914348.XA CN109947994B (en) | 2018-08-10 | 2018-08-10 | Payment process processing method, device, medium and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109947994A CN109947994A (en) | 2019-06-28 |
| CN109947994B true CN109947994B (en) | 2022-12-27 |
Family
ID=67005784
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810914348.XA Active CN109947994B (en) | 2018-08-10 | 2018-08-10 | Payment process processing method, device, medium and electronic equipment |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN109947994B (en) |
| WO (1) | WO2020029971A1 (en) |
Families Citing this family (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109947994B (en) * | 2018-08-10 | 2022-12-27 | 京东科技控股股份有限公司 | Payment process processing method, device, medium and electronic equipment |
| WO2021003607A1 (en) * | 2019-07-05 | 2021-01-14 | 深圳海付移通科技有限公司 | Aggregate payment method and related devices |
| CN111091358B (en) * | 2019-12-16 | 2024-04-16 | 中国建设银行股份有限公司 | Unified processing method and system for multiple payment channels |
| CN111324780A (en) * | 2020-02-28 | 2020-06-23 | 北京三快在线科技有限公司 | Storage method, transmission method, device and storage medium of product data |
| CN111324612A (en) * | 2020-02-28 | 2020-06-23 | 北京三快在线科技有限公司 | Storage method, system, device, equipment and storage medium of order information |
| CN111369252A (en) * | 2020-03-10 | 2020-07-03 | 北京意锐新创科技有限公司 | Account checking method and device suitable for payment equipment |
| CN111695328B (en) * | 2020-06-16 | 2023-01-24 | 深圳前海微众银行股份有限公司 | Method, device, equipment and storage medium for generating simulation test message |
| CN112037002B (en) * | 2020-09-03 | 2024-04-23 | 中国银行股份有限公司 | Defragmentation message processing method and defragmentation message processing system based on distributed payment system |
| CN112419004B (en) * | 2020-12-07 | 2024-02-02 | 恩亿科(北京)数据科技有限公司 | Method, system, equipment and storage medium for configurable access of all-channel order |
| CN115964028B (en) * | 2021-10-12 | 2023-11-03 | 讯联数据(无锡)有限公司 | Rapid access method and system for third party payment interface |
| CN114070886A (en) * | 2021-11-17 | 2022-02-18 | 深圳壹账通智能科技有限公司 | Message conversion method, device, equipment and medium |
| CN114500690B (en) * | 2022-02-15 | 2023-08-18 | 平安科技（深圳）有限公司 | Interface data processing method and device, electronic equipment and storage medium |
| CN114900549A (en) * | 2022-05-06 | 2022-08-12 | 建信金融科技有限责任公司 | Message sending method and device, electronic equipment and storage medium |
| CN115242872B (en) * | 2022-06-24 | 2024-02-02 | 平安银行股份有限公司 | Data processing method, device, computer equipment and readable storage medium |
| CN115103034A (en) * | 2022-06-27 | 2022-09-23 | 京东科技信息技术有限公司 | Message protocol conversion method and device |
| CN117556801A (en) * | 2023-11-30 | 2024-02-13 | 中科世通亨奇(北京)科技有限公司 | Method, system, storage medium and electronic device for generating request message |
| CN117435174B (en) * | 2023-12-11 | 2024-04-09 | 江西曼荼罗软件有限公司 | Payment expansion method and system |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105741088A (en) * | 2016-01-27 | 2016-07-06 | 广州唯品会信息科技有限公司 | Routing matching payment method and device |
| CN105741093A (en) * | 2016-01-25 | 2016-07-06 | 网易（杭州）网络有限公司 | Payment method, device and system of mobile application |
| WO2016115329A1 (en) * | 2015-01-16 | 2016-07-21 | Van De Wetering Stephen James | Methods and systems for a personal data sharing app |
| CN106296142A (en) * | 2015-06-12 | 2017-01-04 | 深圳云游四海信息科技有限公司 | A kind of method and system of pay this extra Channel Selection |
| CN107153961A (en) * | 2017-05-18 | 2017-09-12 | 努比亚技术有限公司 | A kind of method of payment, paying server, trading server and readable storage medium storing program for executing |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100211499A1 (en) * | 2009-02-13 | 2010-08-19 | Bank Of America Corporation | Systems, methods and computer program products for optimizing routing of financial payments |
| CN105427101A (en) * | 2015-11-19 | 2016-03-23 | 成都连银信息技术有限公司 | Unified payment access gateway supporting multiple payment channels |
| CN105654279A (en) * | 2016-01-27 | 2016-06-08 | 广州唯品会信息科技有限公司 | Payment platform management method and device |
| CN108022087A (en) * | 2017-11-22 | 2018-05-11 | 深圳市牛鼎丰科技有限公司 | payment data processing method, device, storage medium and computer equipment |
| CN108183958A (en) * | 2017-12-29 | 2018-06-19 | 银联商务股份有限公司 | Message transmitting method, device and payment system |
| CN109947994B (en) * | 2018-08-10 | 2022-12-27 | 京东科技控股股份有限公司 | Payment process processing method, device, medium and electronic equipment |
-
2018
- 2018-08-10 CN CN201810914348.XA patent/CN109947994B/en active Active
-
2019
- 2019-08-06 WO PCT/CN2019/099502 patent/WO2020029971A1/en active Application Filing
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2016115329A1 (en) * | 2015-01-16 | 2016-07-21 | Van De Wetering Stephen James | Methods and systems for a personal data sharing app |
| CN106296142A (en) * | 2015-06-12 | 2017-01-04 | 深圳云游四海信息科技有限公司 | A kind of method and system of pay this extra Channel Selection |
| CN105741093A (en) * | 2016-01-25 | 2016-07-06 | 网易（杭州）网络有限公司 | Payment method, device and system of mobile application |
| CN105741088A (en) * | 2016-01-27 | 2016-07-06 | 广州唯品会信息科技有限公司 | Routing matching payment method and device |
| CN107153961A (en) * | 2017-05-18 | 2017-09-12 | 努比亚技术有限公司 | A kind of method of payment, paying server, trading server and readable storage medium storing program for executing |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2020029971A1 (en) | 2020-02-13 |
| CN109947994A (en) | 2019-06-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109947994B (en) | Payment process processing method, device, medium and electronic equipment | |
| CN110895471A (en) | Installation package generation method, device, medium and electronic equipment | |
| CN111367516B (en) | Application interface generation method and device and electronic equipment | |
| CN110134427A (en) | A kind of method and apparatus generating code file | |
| CN110109983B (en) | Method and device for operating Redis database | |
| CN116414370A (en) | Platform construction method and device based on low codes, medium and electronic equipment | |
| CN110807056A (en) | Excel-based report processing method, Excel-based report processing device, Excel-based report processing medium and electronic equipment | |
| CN116781586A (en) | gRPC flow analysis method, device, equipment and medium | |
| CN113536748A (en) | Method and device for generating chart data | |
| CN113094561B (en) | Webpage generating method, webpage generating device, electronic equipment and storage medium | |
| CN113760240B (en) | Method and device for generating data model | |
| CN115391343A (en) | Bill data processing method and device, electronic equipment and storage medium | |
| CN115145652A (en) | Method, device, equipment and medium for creating data processing task | |
| CN110764768A (en) | Method and device for mutual conversion between model object and JSON object | |
| CN111414161B (en) | Method, device, medium and electronic equipment for generating IDL file | |
| CN111062682B (en) | Work order processing method and device | |
| CN112596729A (en) | Target application interface generation method and device, readable medium and electronic equipment | |
| CN109669720B (en) | Chain type asynchronous request processing method and device based on Promise and electronic equipment | |
| CN112363716A (en) | Method, system and device for dynamically assembling evaluation model | |
| CN112507676A (en) | Energy report generation method and device, electronic equipment and computer readable medium | |
| CN111078230A (en) | Code generation method and device | |
| CN112825107B (en) | Method and device for generating chart | |
| CN111401825B (en) | Instantiation method and device | |
| CN112688863B (en) | Gateway data processing method and device and electronic equipment | |
| CN113011138B (en) | Information processing method, information processing device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: Room 221, 2nd floor, Block C, 18 Kechuang 11th Street, Beijing Economic and Technological Development Zone, 100176 Applicant after: JINGDONG DIGITAL TECHNOLOGY HOLDINGS Co.,Ltd. Address before: Room 221, 2nd floor, Block C, 18 Kechuang 11th Street, Beijing Economic and Technological Development Zone, 100176 Applicant before: BEIJING JINGDONG FINANCIAL TECHNOLOGY HOLDING Co.,Ltd. |
|
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Address after: Room 221, 2 / F, block C, 18 Kechuang 11th Street, Daxing District, Beijing, 100176 Applicant after: Jingdong Technology Holding Co.,Ltd. Address before: Room 221, 2 / F, block C, 18 Kechuang 11th Street, Daxing District, Beijing, 100176 Applicant before: Jingdong Digital Technology Holding Co.,Ltd. Address after: Room 221, 2 / F, block C, 18 Kechuang 11th Street, Daxing District, Beijing, 100176 Applicant after: Jingdong Digital Technology Holding Co.,Ltd. Address before: Room 221, 2 / F, block C, 18 Kechuang 11th Street, Beijing Economic and Technological Development Zone, 100176 Applicant before: JINGDONG DIGITAL TECHNOLOGY HOLDINGS Co.,Ltd. |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |