CN113723942A - Aggregated payment method, device, equipment and storage medium - Google Patents
Aggregated payment method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN113723942A CN113723942A CN202110868874.9A CN202110868874A CN113723942A CN 113723942 A CN113723942 A CN 113723942A CN 202110868874 A CN202110868874 A CN 202110868874A CN 113723942 A CN113723942 A CN 113723942A
- Authority
- CN
- China
- Prior art keywords
- payment
- order
- request
- transaction
- target
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; 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/085—Payment architectures involving remote charge determination or related payment systems
- G06Q20/0855—Payment architectures involving remote charge determination or related payment systems involving a third party
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; 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
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
Landscapes
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- Physics & Mathematics (AREA)
- Strategic Management (AREA)
- Theoretical Computer Science (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Marketing (AREA)
- Technology Law (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention relates to the technical field of finance, and discloses an aggregated payment method, device, equipment and storage medium. When a payment service calling request is received, matching target configuration information from a preset database, storing pre-aggregated configuration information of a plurality of third-party payment platforms in the preset database, then sending a transaction request to the target third-party payment platform corresponding to the payment service calling request according to the target configuration information, so that the target third-party payment platform feeds back an order payment result notification corresponding to the transaction request, and when the order payment result notification is received, feeding back an order state corresponding to the payment service calling request to a user according to the order payment result notification. Matching the target configuration information from the preset database, uniformly managing the configuration information of the accessed third-party payment platform, sending a transaction request to the target third-party payment platform, and then feeding back the order state to the user, thereby performing uniform service management on the payment mode provided by the third-party payment platform.
Description
Technical Field
The invention relates to the technical field of finance, in particular to an aggregated payment method, device, equipment and storage medium.
Background
With the coming of the information age and the continuous progress of the society, the daily life of people based on various information technologies changes day by day, and people are increasingly pursuing higher quality of life besides ensuring the basic daily life level. Nowadays, online shopping has penetrated the aspects of people's daily life, and as the carrier of online shopping, internet electricity merchant platform develops well-being, and payment function is as its indispensable part, and the realization has also various schemes. More and more people pursue more convenient electronic payment field modes such as payment treasure and WeChat, and although the electronic payment means brings certain convenience to life, certain development problems exist correspondingly.
Many enterprises and individuals often have single payment modes supported by products, which cannot meet the current-stage payment transaction market capacity, and meanwhile, the enterprises and individuals want to access a new payment mode into the original products, and the third-party payment mode has the following defects: 1. various third party payment interfaces are inconsistent in specification and inconsistent in safety mechanism, so that high cost and difficult maintenance are caused to the access of a service system; 2. different payment forms relate to different technologies, system platforms are different, and business systems need to be respectively butted against different platforms and technologies; 3. the systems of mobile platforms supported by mobile payment terminals are numerous and incompatible, often resulting in more time and cost for both enterprises and individuals to develop. The user also needs to download and use the payment terminal supporting the corresponding system according to the systems of different platforms, not only the operation process is complex, but also when the client needs to add or change the payment service, the payment service needs to be added or changed on each system, and the cost for developing and maintaining the payment functions of different systems is high.
The above is only for the purpose of assisting understanding of the technical aspects of the present invention, and does not represent an admission that the above is prior art.
Disclosure of Invention
The invention mainly aims to provide an aggregated payment method, an aggregated payment device, aggregated payment equipment and a storage medium, and aims to solve the technical problem that unified service management cannot be performed on a third-party payment mode in the prior art.
To achieve the above object, the present invention provides an aggregated payment method, including:
matching target configuration information from a preset database when a payment service calling request is received, wherein the preset database stores pre-aggregated configuration information of a plurality of third-party payment platforms;
sending a transaction request to a target third party payment platform corresponding to the payment service calling request according to the target configuration information so that the target third party payment platform feeds back an order payment result notice corresponding to the transaction request;
and when the order payment result notification is received, feeding back the order state corresponding to the payment service calling request to the user according to the order payment result notification.
Preferably, the step of sending a transaction request to a target third party payment platform corresponding to the payment service invocation request according to the target configuration information so that the target third party payment platform feeds back an order payment result notification corresponding to the transaction request specifically includes:
determining transaction flow according to transaction data in the payment service calling request;
creating a trade order according to the target configuration information and the trade flow, and generating a trade request according to the trade order;
and sending the transaction request to a target third party payment platform corresponding to the payment service calling request so that the target third party payment platform feeds back an order payment result notice corresponding to the transaction request.
Preferably, the step of sending the transaction request to a target third party payment platform corresponding to the payment service invocation request so that the target third party payment platform feeds back an order payment result notification corresponding to the transaction request specifically includes:
and sending the transaction request to a target third party payment platform corresponding to the payment service calling request, so that the target third party payment platform determines a corresponding service interface according to the transaction request, and feeds back an order payment result notice corresponding to the transaction request through the service interface.
Preferably, the step of feeding back the order state corresponding to the payment service invocation request to the user according to the order payment result notification when the order payment result notification is received specifically includes:
when the order payment result notification is received, determining a notification type corresponding to the order payment result notification according to a service interface corresponding to the transaction request;
when the notification type is a synchronous notification, feeding back an order state corresponding to the payment service calling request to a user according to the order payment result notification;
and when the notification type is asynchronous notification, determining the transaction order state corresponding to the transaction request according to the order payment result notification, and feeding back the order state corresponding to the payment service calling request to the user according to the transaction order state.
Preferably, when the notification type is an asynchronous notification, the step of determining the transaction order state corresponding to the transaction request according to the order payment result notification, and feeding back the order state corresponding to the payment service invocation request to the user according to the transaction order state specifically includes:
when the notification type is asynchronous, analyzing the order payment result notification into a notification message with a unified format, and performing security verification on the notification message;
when the security verification passes, determining the transaction order state corresponding to the transaction request according to the transaction amount in the notification message;
and feeding back the order state corresponding to the payment service calling request to the user according to the transaction order state.
Preferably, when receiving a payment service invocation request, the method further includes, before the step of matching target configuration information from a preset database, where configuration information of a plurality of third party payment platforms aggregated in advance is stored in the preset database:
monitoring the state of each service interface to obtain a monitoring result;
and when the monitoring result is abnormal, determining an abnormal interface, and sending out early warning according to the state of the abnormal interface.
Preferably, after the step of feeding back the order state corresponding to the payment service invocation request to the user according to the order payment result notification when the order payment result notification is received, the method further includes:
when receiving a refund request sent by a refund gateway, carrying out security verification on the refund gateway;
and when the safety verification is passed, responding to the refund request, and when the response result is that the refund is successful, updating the state of the order corresponding to the refund request.
In addition, to achieve the above object, the present invention also provides an aggregation payment apparatus, including:
the payment service calling module is used for calling a payment service to a payment service server according to the target configuration information, and the payment service calling request is sent to the payment service server through the payment service server;
the result notification module is used for sending a transaction request to a target third-party payment platform corresponding to the payment service calling request according to the target configuration information so that the target third-party payment platform feeds back an order payment result notification corresponding to the transaction request;
and the state feedback module is used for feeding back the order state corresponding to the payment service calling request to the user according to the order payment result notice when the order payment result notice is received.
In addition, to achieve the above object, the present invention further provides an aggregation payment apparatus, including: a memory, a processor, and an aggregate payment program stored on the memory and executable on the processor, the aggregate payment program configured to implement the steps of the aggregate payment method as described above.
Furthermore, to achieve the above object, the present invention also proposes a storage medium having stored thereon an aggregated payment program, which when executed by a processor implements the steps of the aggregated payment method as described above.
When a payment service calling request is received, target configuration information is matched from a preset database, pre-aggregated configuration information of a plurality of third-party payment platforms is stored in the preset database, then a transaction request is sent to the target third-party payment platform corresponding to the payment service calling request according to the target configuration information, so that the target third-party payment platform feeds back an order payment result notice corresponding to the transaction request, and when the order payment result notice is received, an order state corresponding to the payment service calling request is fed back to a user according to the order payment result notice. According to the invention, the target configuration information is matched from the preset database, so that the configuration information of the accessed third-party payment platform can be uniformly managed, the transaction request is sent to the target third-party payment platform according to the target configuration information, and then the order state is fed back to the user, so that the payment mode provided by the third-party payment platform is uniformly managed, and the user experience is improved.
Drawings
Fig. 1 is a schematic structural diagram of an aggregation payment device of a hardware operating environment according to an embodiment of the present invention;
FIG. 2 is a schematic flow chart diagram of a first embodiment of an aggregate payment method of the present invention;
FIG. 3 is a communication diagram of an aggregated payment method according to an embodiment of the present invention;
FIG. 4 is a schematic flow chart diagram of a second embodiment of the aggregate payment method of the present invention;
FIG. 5 is a schematic flow chart of a third embodiment of the aggregate payment method of the present invention;
fig. 6 is a block diagram of the aggregate payment device according to the first embodiment of the present invention.
The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
Referring to fig. 1, fig. 1 is a schematic structural diagram of an aggregation payment device in a hardware operating environment according to an embodiment of the present invention.
As shown in fig. 1, the aggregate payment device may include: a processor 1001, such as a Central Processing Unit (CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. Wherein a communication bus 1002 is used to enable connective communication between these components. The user interface 1003 may include a Display screen (Display), an input unit such as a Keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface, a wireless interface. The network interface 1004 may optionally include a standard wired interface, a Wireless interface (e.g., a Wireless-Fidelity (WI-FI) interface). The Memory 1005 may be a Random Access Memory (RAM) or a Non-Volatile Memory (NVM), such as a disk Memory. The memory 1005 may alternatively be a storage device separate from the processor 1001.
Those skilled in the art will appreciate that the configuration shown in fig. 1 does not constitute a limitation of the aggregate payment device and may include more or fewer components than shown, or some components may be combined, or a different arrangement of components.
As shown in fig. 1, a memory 1005, which is a kind of storage medium, may include therein an operating system, a network communication module, a user interface module, and an aggregation payment program.
In the aggregated payment device shown in fig. 1, the network interface 1004 is mainly used for data communication with a network server; the user interface 1003 is mainly used for data interaction with a user; the processor 1001 and the memory 1005 in the aggregated payment device of the present invention may be disposed in the aggregated payment device, and the aggregated payment device calls the aggregated payment program stored in the memory 1005 through the processor 1001 and executes the aggregated payment method provided by the embodiment of the present invention.
An embodiment of the present invention provides an aggregate payment method, and referring to fig. 2, fig. 2 is a schematic flow diagram of a first embodiment of the aggregate payment method according to the present invention.
In this embodiment, the aggregate payment method includes the following steps:
step S10: when a payment service calling request is received, matching target configuration information from a preset database, wherein the preset database stores pre-aggregated configuration information of a plurality of third-party payment platforms.
It should be noted that the execution main body of this embodiment may be aggregation payment equipment having network communication and program running functions, and the aggregation payment equipment may be a server or other equipment.
Further, referring to fig. 3, fig. 3 is a communication diagram of an embodiment of the aggregate payment method according to the present invention.
It should be understood that the configuration information refers to information that needs to be configured when accessing the third party payment platform, and may include a key, account information, payment channel information, service interface parameter information, and the like of each third party payment platform, which is not limited in this embodiment specifically.
It can be understood that, as shown in fig. 3, the payment service invocation request may be a request for payment issued by a user, and the third party payment platform selected by the user may be determined according to the payment service invocation request, so that the target configuration information corresponding to the selected third party payment platform is matched from the preset database.
In the specific implementation, a user can be inquired whether online payment or signed withholding payment is needed, if the online payment is needed, the online payment can be accessed in an http interface mode, and a server provides a uniform ordering interface and a uniform refund interface; if the payment is signed and withheld, the payment can be asynchronously accessed through a RabbitMQ message, and a server provides a signing and contracting interface. When multiple scenes are used, the flow of each payment channel is different, so that the payment interface is realized by using an abstract class, the redundancy of codes is reduced, various payment scenes are managed by using a payment class, and the invocation of various payment scenes is provided for upper-layer services by combining the annotation mode of a Springboot technology stack.
Further, before step S10, the method further includes: monitoring the state of each service interface to obtain a monitoring result; and when the monitoring result is abnormal, determining an abnormal interface, and sending out early warning according to the state of the abnormal interface.
It can be understood that, in the present embodiment, by monitoring the state of each service interface, a specific implementation manner may be implemented by a code, which is not described in detail in the present embodiment.
In a specific implementation, after the abnormal interface is determined, an early warning is sent to a developer, for example: and early warning is carried out in the modes of mails, short messages and the like, and after the early warning is seen by developers, the abnormal interface can be processed according to the state of the abnormal interface, so that the abnormal interface is recovered to be normal.
Step S20: and sending a transaction request to a target third party payment platform corresponding to the payment service calling request according to the target configuration information so that the target third party payment platform feeds back an order payment result notice corresponding to the transaction request.
It should be noted that, referring to fig. 3, the transaction request is sent from the server to the target third party payment platform, the order payment result notification is sent from the target third party payment platform to the server, and the order payment result notification corresponds to the transaction request.
It will be appreciated that the order payment result notification is received by the server.
Step S30: and when the order payment result notification is received, feeding back the order state corresponding to the payment service calling request to the user according to the order payment result notification.
In a specific implementation, the order payment result notification needs to be processed to obtain an order status, and to feed back to the user, for example: payment success, payment failure, etc., which the present embodiment does not specifically limit.
Further, after the step S30, the method further includes: when receiving a refund request sent by a refund gateway, carrying out security verification on the refund gateway; and when the safety verification is passed, responding to the refund request, and when the response result is that the refund is successful, updating the state of the order corresponding to the refund request.
It can be understood that the paid order actively cancelled by the user or the order needs to be cancelled due to various reasons such as insufficient inventory, incapability of delivery and the like needs to be refunded for the user, the refunding mode includes road refund, bank transfer, balance refund and the like, and the current mainstream is the road refund. The refund gateway can not be directly accessed by a user, the order has a refund application and approval process, generally, the refund gateway is called by the order management system under the control of the order management system to initiate a refund request, and therefore the server needs to make identity verification and safety precaution on the refund gateway.
It should be understood that the refund data of the order which is successfully refunded can be inquired through the inquiry interface of the third party payment platform, and the refund data is processed uniformly, the state of the refund list is updated, the order system is informed, and the like.
In the specific implementation, for all refund requests, the order payment state needs to be inquired first, and the inquiry interface for third-party payment is directly called to check the latest information such as the order state, refundable amount and the like. Then, checking the refund amount, and if the refund amount is full refund, only verifying that the refund amount is equal to the payment amount, and calling a refund interface to refund money; if the refund is partial refund, calculating the sum of the amount of the successfully refund and the sum of the amount of the successfully refund which is successfully applied but is not notified by the successful refund of the third-party payment platform, wherein the sum of the amount of the order payment subtracted by the sum of the amount of the two parts is the refundable amount; for the partial refund application processing, if the application is successful, the refund cannot be repeatedly applied for the refund in the processing.
In the embodiment, when a payment service calling request is received, target configuration information is matched from a preset database, pre-aggregated configuration information of a plurality of third-party payment platforms is stored in the preset database, then a transaction request is sent to the target third-party payment platform corresponding to the payment service calling request according to the target configuration information, so that the target third-party payment platform feeds back an order payment result notification corresponding to the transaction request, and when the order payment result notification is received, an order state corresponding to the payment service calling request is fed back to a user according to the order payment result notification. According to the embodiment, the configuration information of the accessed third-party payment platform can be uniformly managed by matching the target configuration information from the preset database, the transaction request is sent to the target third-party payment platform according to the target configuration information, and then the order state is fed back to the user, so that the payment mode provided by the third-party payment platform is uniformly service-managed, and the user experience is improved.
Referring to fig. 4, fig. 4 is a flowchart illustrating a second embodiment of the aggregate payment method according to the present invention.
Based on the first embodiment described above, in the present embodiment, the step S20 includes:
step S201: and determining transaction flow according to the transaction data in the payment service calling request.
It should be noted that various transaction data can be included in the transaction stream, such as: the transaction payment amount, the transaction refund amount, the transaction order number, and the like can be set according to the actual situation, and this embodiment is not particularly limited thereto.
Step S202: and creating a trade order according to the target configuration information and the trade flow, and generating a trade request according to the trade order.
It should be understood that the trade order may include trade streamlines and may also include other information, such as: the user name of the user, the name of the merchant, and the like may be set according to a transaction order provided by the third party transaction platform, which is not limited in this embodiment.
It can be understood that, in the embodiment, information in the transaction order corresponding to each third party payment platform may be inconsistent, and according to the target configuration information, information in the transaction order of the third party payment platform may be determined, and then the information in the transaction order is changed according to the transaction flow, so as to create the transaction order.
Step S203: and sending the transaction request to a target third party payment platform corresponding to the payment service calling request so that the target third party payment platform feeds back an order payment result notice corresponding to the transaction request.
Further, the step S203 specifically includes: and sending the transaction request to a target third party payment platform corresponding to the payment service calling request, so that the target third party payment platform determines a corresponding service interface according to the transaction request, and feeds back an order payment result notice corresponding to the transaction request through the service interface.
It should be noted that, the service interface may include: a subscription interface, a contract-release interface, a payment interface, a refund interface, a query interface, a callback interface, a reconciliation interface, etc., which is not specifically limited by the embodiment.
It can be understood that the transaction request includes the service information that the user needs to handle, such as: when the user sends a payment request, the corresponding service interface is a payment interface, and the same processing is performed on other service interfaces, which is not described in detail in this embodiment.
In this embodiment, a transaction flow is determined according to transaction data in the payment service invocation request, then a transaction order is created according to the target configuration information and the transaction flow, a transaction request is generated according to the transaction order, and then the transaction request is sent to a target third-party payment platform corresponding to the payment service invocation request, so that the target third-party payment platform feeds back an order payment result notification corresponding to the transaction request. According to the embodiment, the transaction request is generated according to the transaction order and then sent to the third-party payment platform, so that the transaction request contains all information required by the third-party payment platform, the order payment result notification can be accurately fed back to the server, and the order state is fed back to the user, so that the payment mode provided by the third-party payment platform is subjected to unified service management, and the user experience is improved.
Referring to fig. 5, fig. 5 is a schematic flow chart of a third embodiment of the aggregate payment method according to the present invention.
Based on the above embodiments, in the present embodiment, the step S30 includes:
step S301: when the order payment result notification is received, determining a notification type corresponding to the order payment result notification according to a service interface corresponding to the transaction request;
it should be noted that the notification types may include a synchronous notification and an asynchronous notification, and the synchronous notification may be directly fed back to the client for immediately notifying the order status; the asynchronous notification needs to be fed back to the server to prevent the information from being missed in sending and receiving. In order to ensure the safety in the transaction process, the asynchronous notification result is mainly used as the standard.
Step S302: when the notification type is a synchronous notification, feeding back an order state corresponding to the payment service calling request to a user according to the order payment result notification;
step S303: and when the notification type is asynchronous notification, determining the transaction order state corresponding to the transaction request according to the order payment result notification, and feeding back the order state corresponding to the payment service calling request to the user according to the transaction order state.
In a specific implementation, the order status needs to be determined jointly according to the notification type and the order payment result notification, for example: the notification type is synchronous notification, the order payment result notification is paid, and the order state is in payment confirmation; the notification type is asynchronous notification and the order payment result notification is payment success, and the order state is paid.
Further, the step S303 includes: when the notification type is asynchronous, analyzing the order payment result notification into a notification message with a unified format, and performing security verification on the notification message; when the security verification passes, determining the transaction order state corresponding to the transaction request according to the transaction amount in the notification message; and feeding back the order state corresponding to the payment service calling request to the user according to the transaction order state.
It can be understood that the server cannot repeat the receiving address of the order payment result notification fed back by the third-party payment platform, and the payment notification from which platform the order payment result notification is sent can be clearly known by determining a Uniform Resource Location (URL) of the order payment result notification. If only one public URL is provided for the accessed third party payment platform, and then the message format is analyzed to judge which payment mode comes from which platform, the mode is chaotic and uncontrollable.
It should be appreciated that upon receipt of the order payment result notification, it is first parsed into a uniform format, such as map, and then security verification is performed, for example: whether the signature is correct or not and whether the payment amount is consistent or not are verified, which is not specifically limited in this embodiment. When the payment amount is verified to be consistent, type conversion needs to be performed on the amount, for example, an int type, so that failure of amount verification due to accuracy problems is avoided, conversion types corresponding to different third-party payment platforms may not be consistent, and this embodiment does not specifically limit this.
In the specific implementation, for the order payment result notification passing the security verification, a correct receipt needs to be returned to the corresponding third-party payment platform immediately, so that after the notification is received, the notification is inserted into the payment success queue, the relative performance overhead is minimum and stable, the correct receipt can be provided for the third-party payment platform at the highest speed, and the third-party payment platform is not influenced by the service processing flow of the user. When an extreme situation is met, the server is abnormal or responds too slowly, the receipt of the server to the third-party payment platform is affected, and although a retransmission mechanism is arranged on part of the third-party payment platforms, the server responds successfully as soon as possible based on the consideration of performance and order account-finding efficiency. Therefore, if the server does not receive the successful response in case of exception, the data in the order payment result notice can be inserted into the exception handling queue, and the consuming process of the exception handling queue consumes the data at regular time until the consuming process receives the successful response of the server. When an abnormal interface is monitored, after early warning is given to a developer, timely query is carried out through XXJ-JOB, wherein XXL-JOB is a lightweight distributed task scheduling platform until a server can normally return a receipt.
In response to receipt of a specific third party payment platform, the server sets the channel to the confirm mode, once the channel enters the confirm mode, all messages posted on the channel are assigned a unique ID (starting with 1), and once the message is posted to all matching queues, the brooker sends a confirmation to the producer (containing the unique ID of the message), which makes the server know that the message has arrived correctly at the destination queue, i.e., the target third party payment platform.
In this embodiment, when an order payment result notification is received, a notification type corresponding to the order payment result notification is determined according to a service interface corresponding to the transaction request, when the notification type is a synchronous notification, an order state corresponding to the payment service invocation request is fed back to the user according to the order payment result notification, when the notification type is an asynchronous notification, a transaction order state corresponding to the transaction request is determined according to the order payment result notification, and an order state corresponding to the payment service invocation request is fed back to the user according to the transaction order state. According to the method and the device, the order state can be fed back to the user based on the notification type by judging whether the notification type corresponding to the order payment result notification is the synchronous notification or the asynchronous notification, so that the payment mode provided by the third-party payment platform is subjected to unified service management, and the user experience is improved.
Furthermore, an embodiment of the present invention further provides a storage medium, where an aggregated payment program is stored, and the aggregated payment program, when executed by a processor, implements the steps of the aggregated payment method as described above.
Referring to fig. 6, fig. 6 is a block diagram illustrating a configuration of a first embodiment of the aggregation payment device according to the present invention.
As shown in fig. 6, the aggregate payment apparatus provided in the embodiment of the present invention includes:
the payment service calling module 601 is configured to, when a payment service calling request is received, match target configuration information from a preset database, where configuration information of multiple pre-aggregated third-party payment platforms is stored in the preset database;
a result notification module 602, configured to send a transaction request to a target third-party payment platform corresponding to the payment service invocation request according to the target configuration information, so that the target third-party payment platform feeds back an order payment result notification corresponding to the transaction request;
and a state feedback module 603, configured to, when the order payment result notification is received, feed back, to the user, an order state corresponding to the payment service invocation request according to the order payment result notification.
Based on the above-mentioned first embodiment of the aggregated payment device of the present invention, a second embodiment of the aggregated payment device of the present invention is proposed.
In this embodiment, the result notification module 602 is further configured to determine a transaction flow according to the transaction data in the payment service invocation request; creating a trade order according to the target configuration information and the trade flow, and generating a trade request according to the trade order; and sending the transaction request to a target third party payment platform corresponding to the payment service calling request so that the target third party payment platform feeds back an order payment result notice corresponding to the transaction request.
Further, the result notification module 602 is further configured to send the transaction request to a target third party payment platform corresponding to the payment service invocation request, so that the target third party payment platform determines a corresponding service interface according to the transaction request, and feeds back an order payment result notification corresponding to the transaction request through the service interface.
Further, the state feedback module 603 is further configured to, when the order payment result notification is received, determine a notification type corresponding to the order payment result notification according to a service interface corresponding to the transaction request; when the notification type is a synchronous notification, feeding back an order state corresponding to the payment service calling request to a user according to the order payment result notification; and when the notification type is asynchronous notification, determining the transaction order state corresponding to the transaction request according to the order payment result notification, and feeding back the order state corresponding to the payment service calling request to the user according to the transaction order state.
Further, the state feedback module 603 is further configured to, when the notification type is an asynchronous notification, parse the order payment result notification into a notification message in a unified format, and perform security verification on the notification message; when the security verification passes, determining the transaction order state corresponding to the transaction request according to the transaction amount in the notification message; and feeding back the order state corresponding to the payment service calling request to the user according to the transaction order state.
Further, the aggregation payment device further includes a monitoring module 600, where the monitoring module 600 is configured to monitor the state of each service interface to obtain a monitoring result; and when the monitoring result is abnormal, determining an abnormal interface, and sending out early warning according to the state of the abnormal interface.
Further, the aggregated payment device further includes a refund module 604, where the refund module 604 is configured to perform security verification on the refund gateway when receiving a refund request sent by the refund gateway; and when the safety verification is passed, responding to the refund request, and when the response result is that the refund is successful, updating the state of the order corresponding to the refund request.
Other embodiments or specific implementation manners of the aggregation payment device of the present invention may refer to the above method embodiments, and are not described herein again.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or system. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or system that comprises the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., a rom/ram, a magnetic disk, an optical disk) and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present invention.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (10)
1. An aggregated payment method, comprising:
matching target configuration information from a preset database when a payment service calling request is received, wherein the preset database stores pre-aggregated configuration information of a plurality of third-party payment platforms;
sending a transaction request to a target third party payment platform corresponding to the payment service calling request according to the target configuration information so that the target third party payment platform feeds back an order payment result notice corresponding to the transaction request;
and when the order payment result notification is received, feeding back the order state corresponding to the payment service calling request to the user according to the order payment result notification.
2. The aggregated payment method according to claim 1, wherein the step of sending a transaction request to a target third party payment platform corresponding to the payment service invocation request according to the target configuration information, so that the target third party payment platform feeds back an order payment result notification corresponding to the transaction request specifically includes:
determining transaction flow according to transaction data in the payment service calling request;
creating a trade order according to the target configuration information and the trade flow, and generating a trade request according to the trade order;
and sending the transaction request to a target third party payment platform corresponding to the payment service calling request so that the target third party payment platform feeds back an order payment result notice corresponding to the transaction request.
3. The aggregated payment method according to claim 2, wherein the step of sending the transaction request to the target third party payment platform corresponding to the payment service invocation request so that the target third party payment platform feeds back an order payment result notification corresponding to the transaction request specifically includes:
and sending the transaction request to a target third party payment platform corresponding to the payment service calling request, so that the target third party payment platform determines a corresponding service interface according to the transaction request, and feeds back an order payment result notice corresponding to the transaction request through the service interface.
4. The aggregate payment method according to claim 3, wherein the step of feeding back the order status corresponding to the payment service invocation request to the user according to the order payment result notification when receiving the order payment result notification specifically comprises:
when the order payment result notification is received, determining a notification type corresponding to the order payment result notification according to a service interface corresponding to the transaction request;
when the notification type is a synchronous notification, feeding back an order state corresponding to the payment service calling request to a user according to the order payment result notification;
and when the notification type is asynchronous notification, determining the transaction order state corresponding to the transaction request according to the order payment result notification, and feeding back the order state corresponding to the payment service calling request to the user according to the transaction order state.
5. The aggregate payment method according to claim 4, wherein when the notification type is an asynchronous notification, the step of determining the transaction order status corresponding to the transaction request according to the order payment result notification, and feeding back the order status corresponding to the payment service invocation request to the user according to the transaction order status specifically comprises:
when the notification type is asynchronous, analyzing the order payment result notification into a notification message with a unified format, and performing security verification on the notification message;
when the security verification passes, determining the transaction order state corresponding to the transaction request according to the transaction amount in the notification message;
and feeding back the order state corresponding to the payment service calling request to the user according to the transaction order state.
6. The aggregated payment method according to any one of claims 1 to 5, wherein when receiving a payment service invocation request, matching target configuration information from a preset database, before the step of storing pre-aggregated configuration information of a plurality of third party payment platforms in the preset database, further comprises:
monitoring the state of each service interface to obtain a monitoring result;
and when the monitoring result is abnormal, determining an abnormal interface, and sending out early warning according to the state of the abnormal interface.
7. The aggregate payment method according to claim 6, wherein after the step of feeding back the order status corresponding to the payment service invocation request to the user according to the order payment result notification when the order payment result notification is received, the method further comprises:
when receiving a refund request sent by a refund gateway, carrying out security verification on the refund gateway;
and when the safety verification is passed, responding to the refund request, and when the response result is that the refund is successful, updating the state of the order corresponding to the refund request.
8. An aggregate payment device, comprising:
the payment service calling module is used for calling a payment service to a payment service server according to the target configuration information, and the payment service calling request is sent to the payment service server through the payment service server;
the result notification module is used for sending a transaction request to a target third-party payment platform corresponding to the payment service calling request according to the target configuration information so that the target third-party payment platform feeds back an order payment result notification corresponding to the transaction request;
and the state feedback module is used for feeding back the order state corresponding to the payment service calling request to the user according to the order payment result notice when the order payment result notice is received.
9. An aggregate payment device, the aggregate payment device comprising: a memory, a processor, and an aggregated payment program stored on the memory and executable on the processor, the aggregated payment program configured to implement the steps of the aggregated payment method as claimed in any one of claims 1 to 7.
10. A storage medium having stored thereon an aggregated payment program which, when executed by a processor, carries out the steps of the aggregated payment method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110868874.9A CN113723942A (en) | 2021-07-29 | 2021-07-29 | Aggregated payment method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110868874.9A CN113723942A (en) | 2021-07-29 | 2021-07-29 | Aggregated payment method, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113723942A true CN113723942A (en) | 2021-11-30 |
Family
ID=78674441
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110868874.9A Pending CN113723942A (en) | 2021-07-29 | 2021-07-29 | Aggregated payment method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113723942A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112231118A (en) * | 2020-10-16 | 2021-01-15 | 蜂助手股份有限公司 | Aggregated payment platform, system and method |
| CN114462992A (en) * | 2022-01-27 | 2022-05-10 | 中国工商银行股份有限公司 | Payment method, system and device |
| CN114565374A (en) * | 2022-02-28 | 2022-05-31 | 成都九洲电子信息系统股份有限公司 | Agricultural batch market charging system and method |
| CN117808477A (en) * | 2023-11-27 | 2024-04-02 | 中国民航信息网络股份有限公司 | Payment information processing method, system and equipment |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105373923A (en) * | 2015-11-13 | 2016-03-02 | 广东网金控股股份有限公司 | Unified payment method for investment and financing platform |
| CN105741092A (en) * | 2016-01-19 | 2016-07-06 | 四川长虹电器股份有限公司 | Unified payment method and unified payment system supporting multiple cloud services |
| CN108052398A (en) * | 2017-12-12 | 2018-05-18 | 苏州比可网络科技有限公司 | A kind of feedback method of order processing state and polymerization payment platform |
| CN108711045A (en) * | 2018-04-04 | 2018-10-26 | 首汽租赁有限责任公司 | A kind of cash register system and cash method |
| CN108734457A (en) * | 2018-04-04 | 2018-11-02 | 首汽租赁有限责任公司 | A kind of Withdrawing method unified under cash register system |
-
2021
- 2021-07-29 CN CN202110868874.9A patent/CN113723942A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105373923A (en) * | 2015-11-13 | 2016-03-02 | 广东网金控股股份有限公司 | Unified payment method for investment and financing platform |
| CN105741092A (en) * | 2016-01-19 | 2016-07-06 | 四川长虹电器股份有限公司 | Unified payment method and unified payment system supporting multiple cloud services |
| CN108052398A (en) * | 2017-12-12 | 2018-05-18 | 苏州比可网络科技有限公司 | A kind of feedback method of order processing state and polymerization payment platform |
| CN108711045A (en) * | 2018-04-04 | 2018-10-26 | 首汽租赁有限责任公司 | A kind of cash register system and cash method |
| CN108734457A (en) * | 2018-04-04 | 2018-11-02 | 首汽租赁有限责任公司 | A kind of Withdrawing method unified under cash register system |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112231118A (en) * | 2020-10-16 | 2021-01-15 | 蜂助手股份有限公司 | Aggregated payment platform, system and method |
| CN112231118B (en) * | 2020-10-16 | 2024-04-30 | 蜂助手股份有限公司 | Aggregate payment platform, system and method |
| CN114462992A (en) * | 2022-01-27 | 2022-05-10 | 中国工商银行股份有限公司 | Payment method, system and device |
| CN114565374A (en) * | 2022-02-28 | 2022-05-31 | 成都九洲电子信息系统股份有限公司 | Agricultural batch market charging system and method |
| CN117808477A (en) * | 2023-11-27 | 2024-04-02 | 中国民航信息网络股份有限公司 | Payment information processing method, system and equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113723942A (en) | Aggregated payment method, device, equipment and storage medium | |
| US8126967B2 (en) | Multiple aggregator support | |
| US8270951B2 (en) | Rule-based system and method for managing the provisioning of user applications on limited-resource and/or wireless devices | |
| CN113379523A (en) | Bill generation method, device, medium and electronic equipment | |
| CN112308552B (en) | Method and device for ordering medical insurance medicine | |
| CN101388096A (en) | Multi-platform data standardization processing method and system | |
| CN110213071B (en) | Data checking method, device, system, computer equipment and storage medium | |
| CN113179282A (en) | Method and device for merging account numbers and server | |
| CN112990902A (en) | Service processing method, device, computer equipment and storage medium | |
| CN111695985A (en) | System and method for processing voluntary deposit service of accumulation fund | |
| CN111311146A (en) | Information transmission method and system, communication system, computer readable storage medium | |
| CN113627835A (en) | Distribution management method and device | |
| CN113496395B (en) | Payment method and system | |
| CN111091439A (en) | Order association marketing campaign implementation method, system, equipment and storage medium | |
| CN111507594A (en) | Data processing method and equipment | |
| CN101784028A (en) | Method and system for ordering mobile terminal software business | |
| CN114971564A (en) | Service processing method and device, electronic equipment and computer readable medium | |
| CN112215592B (en) | Data processing method and system | |
| CN115544052A (en) | Data processing method and device | |
| CN111242337A (en) | Online reservation network point system for battery disassembly | |
| JP7458596B2 (en) | Information processing device, information processing program, and information processing method | |
| CN110753316A (en) | Information sending method and device, computer readable storage medium and electronic equipment | |
| US20070162913A1 (en) | System and method for triggering a process on an enterprise system | |
| US20240211873A1 (en) | Embedded shipping label management | |
| CN103390231A (en) | Payment system and method |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20211130 |