CN114581088A - Aggregated payment method, device and system for SaaS (software as a service) system - Google Patents
Aggregated payment method, device and system for SaaS (software as a service) system Download PDFInfo
- Publication number
- CN114581088A CN114581088A CN202210481722.8A CN202210481722A CN114581088A CN 114581088 A CN114581088 A CN 114581088A CN 202210481722 A CN202210481722 A CN 202210481722A CN 114581088 A CN114581088 A CN 114581088A
- Authority
- CN
- China
- Prior art keywords
- payment
- order
- information
- user
- party
- 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; 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/38—Payment protocols; Details thereof
- G06Q20/389—Keeping log of transactions for guaranteeing non-repudiation of a transaction
-
- 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/02—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
- G06Q20/023—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP] the neutral party being a clearing house
-
- 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/02—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
- G06Q20/027—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP] involving a payment switch or gateway
-
- 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/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3821—Electronic credentials
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Accounting & Taxation (AREA)
- Strategic Management (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Finance (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The application discloses and provides an aggregation payment method, device and system for a software as a service (SaaS) system, wherein the method comprises the following steps: receiving a user order payment request, wherein the user order comprises a payment type and a user order identifier; determining a third party payment system gateway corresponding to the payment type; generating payment order information by a third party payment system gateway according to a user order, wherein the payment order information comprises a payment order identifier, payment order flow and payment service information; establishing a payment order by a third party payment system gateway according to the payment order information; if the payment order is successfully established, establishing an association relation between the user order identification and the payment order identification; generating a payment link according to the incidence relation and the payment order information, wherein the payment link is used for entering a third party payment system; the payment link is sent to the user terminal, so that the problems that in the prior art, more and more operators use the SaaS system, and various integration problems exist among different payment systems are solved.
Description
Technical Field
The invention relates to the technical field of aggregated payment for a software as a service (SaaS) system, in particular to an aggregated payment method, device and system for a SaaS system.
Background
In recent years, the SaaS system is rapidly developed, and more enterprises advance to the military SaaS system architecture. In order to increase enterprise income or maintain long-term operation of a system of the SaaS platform operator, a series of value-added services such as purchasing goods, user privileges and the like are created, operators from different countries usually adopt different payment systems to perform online transactions such as paypal which is widely applied globally, popular payment treasures and Wechat in China, and as the operators increase, the following technical problems of the existing SaaS system are always not solved:
firstly, operators in different countries need the SaaS system to access at least one local payment system, and for the SaaS system, how to access and publish the local payment system to the SaaS system does not affect the normal service of the existing operator.
Secondly, due to different local payment service processing logics in different countries, after the user successfully pays, corresponding processing or related transaction data storage is difficult to achieve, such as how to deliver goods to the user after receiving payment, how to store transaction records in multiple countries, and how to associate each paid flow with order transactions of the SaaS system.
Thirdly, the existing aggregation payment technology lacks a powerful information security protection scheme, so that privacy information such as a user name, a password and a payment password paid by a consumer through an aggregation payment system is leaked, and hidden dangers are brought to the safety of lives and properties of the consumer.
Disclosure of Invention
Therefore, the technical problem to be solved by the present invention is to overcome the various integration problems existing among different payment systems due to the increasing use of SaaS systems by operators in the prior art, a distributed gateway order Id is generated for each user order through a payment gateway, and a deduction record and a running bill of each payment gateway are associated with the user order through the gateway order Id, so that all information of the user order, including information paid by a third party and system information per se, can be queried according to the gateway order Id.
In order to solve the above technical problem, the embodiments of the present disclosure at least provide an aggregated payment method, apparatus, and system for a SaaS system.
In a first aspect, an embodiment disclosed in the present invention provides an aggregated payment method for a SaaS system, including:
receiving a payment request of a user order, wherein the user order comprises a payment type and a user order identifier;
determining a third party payment system gateway corresponding to the payment type;
generating payment order information by the third party payment system gateway according to the user order, wherein the payment order information comprises a payment order identifier, a payment order flow and payment service information;
creating a payment order by the third party payment system gateway according to the payment order information;
if the payment order is successfully established, establishing an association relationship between the user order identification and the payment order identification;
generating a payment link according to the incidence relation and the payment order information, wherein the payment link is used for entering the third-party payment system;
and sending the payment link to the user terminal.
Optionally, the user order further includes commodity information and user information, and the method further includes: obtaining payment state information called back by the third-party payment system gateway, wherein the payment state information comprises payment success, payment failure and payment cancellation; and if the payment state information recalled back by the third-party payment system gateway is successful in payment, binding the user information and the commodity information.
Optionally, the user order further includes operator information, and the binding the user information and the commodity information includes: determining a user order identification associated with the payment order identification; inquiring the commodity information, the user information and the operator information corresponding to the user order identification; determining a commodity database corresponding to the operator information; determining a specified commodity from the commodity database according to the commodity information; and binding the specified commodity with the user.
Optionally, the method further comprises: and updating the order state of the user order according to the payment state information.
Optionally, the user order state information in the user order payment request is unpaid, and the updating the payment state of the user order according to the payment state information includes: when the payment order is successfully established, modifying the order state of the user order into unpaid state; when the payment order is failed to be established, modifying the order state of the user order into a payment error; and when the payment state information recalled by the third-party payment system gateway is successful in payment, failed in payment and cancelled in payment, synchronously modifying the order states of the user order into successful in payment, failed in payment and cancelled in payment.
In a second aspect, an embodiment of the present disclosure further provides an aggregated payment apparatus for a SaaS system, including:
the order request receiving unit is used for receiving a payment request of a user order, and the user order comprises a payment type and a user order identifier;
the gateway determining unit is used for determining a third party payment system gateway corresponding to the payment type;
the payment order information generating unit is used for generating payment order information by the third-party payment system gateway according to the user order, wherein the payment order information comprises a payment order identifier, a payment order flow and payment service information;
the payment order creating unit is used for creating a payment order by the third party payment system gateway according to the payment order information;
the identification association unit is used for establishing an association relationship between the user order identification and the payment order identification if the payment order is successfully established;
the payment link generation unit is used for generating a payment link according to the incidence relation and the payment order information, and the payment link is used for entering the third-party payment system;
and the payment link sending unit is used for sending the payment link to the user terminal.
Optionally, the user order further includes commodity information and user information, and the apparatus further includes: the payment state acquisition unit is used for acquiring payment state information called back by the third-party payment system gateway, wherein the payment state information comprises payment success, payment failure and payment cancellation; and the commodity binding unit is used for binding the user information and the commodity information if the payment state information recalled by the third-party payment system gateway is successful in payment.
In a third aspect, an embodiment of the present disclosure further provides an aggregated payment system for a SaaS system, including:
the SaaS service module is used for receiving a user order payment request, wherein the user order comprises a payment type and a user order identifier, determining a third-party payment system gateway corresponding to the payment type, sending a gateway payment request to the aggregation payment module, receiving an incidence relation between the user order identifier and the payment order identifier sent by the aggregation payment module and payment order information, generating a payment link according to the incidence relation and the payment order information, wherein the payment link is used for entering the third-party payment system and sending the payment link to the user terminal, and the gateway payment request comprises the user order identifier;
and the aggregation payment module is used for receiving the gateway payment request, generating payment order information by the third-party payment system gateway according to the user order, creating a payment order by the third-party payment system gateway according to the payment order information, if the payment order is successfully created, establishing an association relation between the user order identifier and the payment order identifier, and sending the association relation and the payment order information to the SaaS service module, wherein the payment order information comprises a payment order identifier, a payment order flow and payment service information.
In a fourth aspect, an embodiment of the present disclosure further provides a computer device, including: a processor, a memory and a bus, the memory storing machine-readable instructions executable by the processor, the processor and the memory communicating via the bus when the computer device is running, the machine-readable instructions when executed by the processor performing the steps of the first aspect described above, or any possible implementation of the first aspect.
In a fifth aspect, the disclosed embodiments of the present invention further provide a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and the computer program is executed by a processor to perform the steps in the first aspect or any possible implementation manner of the first aspect.
The technical scheme provided by the embodiment of the invention has the following beneficial effects:
by using a policy design mode and a distribution process, each payment gateway has a unique code as a representative, a distributed Id is generated by a system for placing an order each time as an order number to process idempotent (all association relations, payment states and associated operators are all controlled by the Id), and a deduction record and a running bill of each payment gateway are associated with the order Id, that is, in a SaaS system, all running water (information of third-party payment and system information) of the order can be inquired according to the order Id.
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
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings can be obtained by those skilled in the art without creative efforts.
Fig. 1 shows a flowchart of an aggregated payment method for a SaaS system according to an embodiment of the present disclosure;
fig. 2 shows a flowchart of another aggregate payment method for a SaaS system according to an embodiment of the disclosure;
FIG. 3 shows a flowchart of step S209 of FIG. 2;
fig. 4 is a schematic structural diagram illustrating an aggregated payment apparatus for a SaaS system according to an embodiment of the present disclosure;
fig. 5 and fig. 6 are schematic structural diagrams illustrating an aggregated payment system for a SaaS system according to an embodiment of the present disclosure;
fig. 7 shows a schematic structural diagram of a computer device according to an embodiment of the present disclosure.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the invention, as detailed in the appended claims.
Example 1
As shown in fig. 1, a flowchart of an aggregated payment method for a SaaS system according to an embodiment of the present disclosure includes:
s11: receiving a user order payment request, wherein the user order comprises a payment type and a user order identifier;
s12: determining a third party payment system gateway corresponding to the payment type;
s13: generating payment order information by a third party payment system gateway according to a user order, wherein the payment order information comprises a payment order identifier, payment order flow and payment service information;
s14: establishing a payment order by a third party payment system gateway according to the payment order information;
s15: if the payment order is successfully established, establishing an association relation between the user order identification and the payment order identification;
s16: generating a payment link according to the incidence relation and the payment order information, wherein the payment link is used for entering a third party payment system;
s17: and sending the payment link to the user terminal.
It can be understood that, in the technical solution provided in this embodiment, a distributed gateway order Id is generated for each user order through the payment gateway, and the deduction record and the running bill of each payment gateway are associated with the user order through the gateway order Id, and all information of the user order, including the information of third party payment and the own system information, can be queried according to the gateway order Id.
Example 2
As shown in fig. 2, a flowchart of another aggregate payment method for a SaaS system according to an embodiment of the present disclosure includes:
s201: receiving a user order payment request, wherein the user order comprises commodity information, user information, a payment type and a user order identifier;
in specific practice, a user selects a payment mode, commodity information and the like at a user terminal to request SaaS service, and the user terminal may be an internet device, such as a mobile phone, a tablet, a television, a set-top box and the like.
S202: determining a third party payment system gateway corresponding to the payment type;
and the application layer of the SaaS system processes the data request aggregate payment service by judging the payment service layer corresponding to the request URL route.
S203: generating payment order information by a third party payment system gateway according to a user order, wherein the payment order information comprises a payment order identifier, payment order flow and payment service information;
s204: establishing a payment order by a third party payment system gateway according to the payment order information;
and the third party payment system gateway creates a payment order according to the payment order information, and the order state is 'unpaid'.
S205: if the payment order is successfully established, establishing an incidence relation between a user order identification and a payment order identification;
if the payment order is not established successfully, the order state is modified to be 'payment error', and if the payment order is established successfully, the order state is not changed and still is 'unpaid'.
S206: generating a payment link according to the incidence relation and the payment order information, wherein the payment link is used for entering a third party payment system;
s207: sending a payment link to a user terminal;
s208: obtaining payment state information called back by a third-party payment system gateway, wherein the payment state information comprises payment success, payment failure and payment cancellation, and if the payment state information called back by the third-party payment system gateway is payment success, executing the step S209;
s209: and binding the user information and the commodity information.
S210: and updating the order state of the user order according to the payment state information.
All information and data related to payment are encrypted in all links, a user terminal decrypts the data to skip a payment interface, and in the step, the SaaS system creates an 'ATM' machine for a user, all payment operations of the user are completed in a third-party payment system, and information leakage risks in the payment process are effectively reduced. The user inputs bank information through a payment page rendered by the user terminal, or jumps to app payment (WeChat app, Paibao app) to pay.
In a specific practice, the user order further includes operator information, and as shown in fig. 3, binding the user information and the commodity information includes:
s2091: determining a user order identification associated with the payment order identification;
s2092: inquiring commodity information, user information and operator information corresponding to the user order identification;
s2093: determining a commodity database corresponding to operator information;
s2094: determining a specified commodity from a commodity database according to the commodity information;
s2095: and binding the specified commodity with the user.
In a specific practice, the step of updating the payment status of the user order according to the payment status information includes:
when the payment order is successfully created, the order state of the user order is modified to be 'unpaid';
when the payment order is failed to be created, the order state of the user order is modified to be 'payment error';
and when the payment state information recalled by the third-party payment system gateway is payment success, payment failure and payment cancellation, synchronously modifying the order states of the user orders into payment success, payment failure and payment cancellation.
It can be understood that, in the technical solution provided in this embodiment, at the level of the system architecture, the payment function is split and separated from the system service, so that what is done with the payment function is what is done with the payment function, and adding a payment gateway does not affect the online service, and does not affect other operators. By using a policy design mode and a distribution process, each payment gateway has a unique code as a representative, a distributed Id is generated by a system for placing an order each time as an order number to process idempotent (all association relations, payment states and associated operators are all controlled by the Id), and a deduction record and a running bill of each payment gateway are associated with the order Id, that is, in a SaaS system, all running water (information of third-party payment and system information) of the order can be inquired according to the order Id. For the third point of security processing, the user payment is not associated with the SaaS system with account, password and bank card number, and the system itself will not record the user private information, and all submissions are interacted with the payment gateway by the user, for example (the SaaS system makes an "ATM" cash dispenser, and the user inputs account private information, and the bank processes account transfer and payment). The technical scheme solves the problems of multi-terminal payment, multi-country payment gateways and multi-operator payment of the SaaS system, enables basic services and payment service architectures to be completely separated, can carry out gray scale release, supports online updating of the payment system, solves the problems of user account information leakage and payment safety, and enables a user to skip a platform to directly interact with a bank (payment gateway).
Example 3
As shown in fig. 4, an embodiment of the present invention further provides an aggregation payment apparatus for a SaaS system, including:
an obtaining module 41, an order request receiving unit, configured to receive a user order payment request, where the user order includes a payment type and a user order identifier;
a gateway determining unit 42, configured to determine a third party payment system gateway corresponding to the payment type;
a payment order information generating unit 43, configured to generate, by the third party payment system gateway, payment order information according to the user order, where the payment order information includes a payment order identifier, a payment order flow and payment service information;
a payment order creating unit 44, configured to create, by the third party payment system gateway, a payment order according to the payment order information;
an identifier associating unit 45, configured to establish an association relationship between the user order identifier and the payment order identifier if the payment order is successfully created;
a payment link generating unit 46, configured to generate a payment link according to the association relationship and the payment order information, where the payment link is used to enter the third party payment system;
a payment link sending unit 47, configured to send the payment link to the user terminal.
In a specific practice, the user order further includes commodity information and user information, as shown in a dotted line in fig. 4, the apparatus further includes:
a payment status obtaining unit 48, configured to obtain payment status information that is called back by the third-party payment system gateway, where the payment status information includes payment success, payment failure, and payment cancellation;
and a commodity binding unit 49, configured to bind the user information and the commodity information if the payment state information recalled by the third-party payment system gateway is successful in payment.
It can be understood that, in the technical solution provided in this embodiment, at the level of the system architecture, the payment function is split and separated from the system service, so that what is done with the payment function is what is done with the payment function, and adding a payment gateway does not affect the online service, and does not affect other operators. By using a policy design mode and a distribution process, each payment gateway has a unique code as a representative, a distributed Id is generated by a system for placing an order each time as an order number to process idempotent (all association relations, payment states and associated operators are all controlled by the Id), and a deduction record and a running bill of each payment gateway are associated with the order Id, that is, in a SaaS system, all running water (information of third-party payment and system information) of the order can be inquired according to the order Id. For the third point of security processing, the user payment is not associated with the SaaS system with account, password and bank card number, and the system itself will not record the user private information, and all submissions are interacted with the payment gateway by the user, for example (the SaaS system makes an "ATM" cash dispenser, and the user inputs account private information, and the bank processes account transfer and payment).
Example 4
As shown in fig. 5 and fig. 6, an embodiment of the present invention further provides an aggregated payment system for a SaaS system, including:
the SaaS service module 51 is configured to receive a user order payment request, where the user order includes a payment type and a user order identifier, determine a third-party payment system gateway corresponding to the payment type, send a gateway payment request to an aggregation payment module, receive an association relationship between the user order identifier and the payment order identifier and payment order information sent by the aggregation payment module, generate a payment link according to the association relationship and the payment order information, where the payment link is used to enter the third-party payment system and send the payment link to the user terminal, and the gateway payment request includes the user order identifier;
the aggregate payment module 52 receives the gateway payment request, generates payment order information according to the user order by the third-party payment system gateway, creates a payment order according to the payment order information by the third-party payment system gateway, establishes an association relationship between the user order identifier and the payment order identifier if the payment order is successfully created, and sends the association relationship and the payment order information to the SaaS service module, wherein the payment order information includes a payment order identifier, a payment order flow and payment service information
It can be understood that, in the technical solution provided in this embodiment, at the level of the system architecture, the payment function is split and separated from the system service, so that what is done with the payment function is what is done with the payment function, and adding a payment gateway does not affect the online service, and does not affect other operators. By using a policy design mode and a distribution process, each payment gateway has a unique code as a representative, a distributed Id is generated by a system for placing an order each time as an order number to process idempotent (all association relations, payment states and associated operators are all controlled by the Id), and a deduction record and a running bill of each payment gateway are associated with the order Id, that is, in a SaaS system, all running water (information of third-party payment and system information) of the order can be inquired according to the order Id. For the third point of security processing, the user payment is not associated with the SaaS system with account, password and bank card number, and the system itself will not record the user private information, and all submissions are interacted with the payment gateway by the user, for example (the SaaS system makes an "ATM" cash dispenser, and the user inputs account private information, and the bank processes account transfer and payment).
Example 5
Based on the same technical concept, an embodiment of the present application further provides a computer device, which includes a memory 1 and a processor 2, as shown in fig. 7, where the memory 1 stores a computer program, and the processor 2 implements the aggregate payment method for the SaaS system according to any one of the foregoing items when executing the computer program.
The memory 1 includes at least one type of readable storage medium, which includes a flash memory, a hard disk, a multimedia card, a card type memory (e.g., SD or DX memory, etc.), a magnetic memory, a magnetic disk, an optical disk, and the like. The memory 1 may in some embodiments be an internal storage unit of the OTT video traffic monitoring system, e.g. a hard disk. The memory 1 may also be an external storage device of the OTT video service monitoring system in other embodiments, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like. Further, the memory 1 may also include both an internal storage unit and an external storage device of the OTT video service monitoring system. The memory 1 may be used to store not only application software installed in the OTT video service monitoring system and various data, such as codes of OTT video service monitoring programs, but also temporarily store data that has been output or is to be output.
The processor 2 may be a Central Processing Unit (CPU), a controller, a microcontroller, a microprocessor or other data Processing chip in some embodiments, and is used to run program codes stored in the memory 1 or process data, for example, execute an OTT video service monitoring program.
It can be understood that, in the technical solution provided in this embodiment, at the level of the system architecture, the payment function is split and separated from the system service, so that what is done with the payment function is what is done with the payment function, and adding a payment gateway does not affect the online service, and does not affect other operators. By using a policy design mode and a distribution process, each payment gateway has a unique code as a representative, a distributed Id is generated by a system for placing an order each time as an order number to process idempotent (all association relations, payment states and associated operators are all controlled by the Id), and a deduction record and a running bill of each payment gateway are associated with the order Id, that is, in a SaaS system, all running water (information of third-party payment and system information) of the order can be inquired according to the order Id. For the security processing at the third point, the user payment is not associated with the account, password and bank card number of the SaaS system, and the private information of the user will not be recorded by the system per se, and all submissions are interacted with the payment gateway by the user, for example (the SaaS system makes an 'ATM' cash dispenser, the user inputs the account private information per se, and the bank processes the account transfer and payment).
The disclosed embodiments of the present invention further provide a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the steps of the aggregated payment method for the SaaS system described in the above method embodiments are executed. The storage medium may be a volatile or non-volatile computer-readable storage medium.
The computer program product for the aggregated payment method for the SaaS system provided by the embodiments of the present disclosure includes a computer-readable storage medium storing a program code, where instructions included in the program code may be used to execute steps of the aggregated payment method for the SaaS system described in the above method embodiments, which may be specifically referred to in the above method embodiments and are not described herein again.
The embodiments disclosed herein also provide a computer program, which when executed by a processor implements any one of the methods of the preceding embodiments. The computer program product may be embodied in hardware, software or a combination thereof. In an alternative embodiment, the computer program product is embodied in a computer storage medium, and in another alternative embodiment, the computer program product is embodied in a Software product, such as a Software Development Kit (SDK), or the like.
It is understood that the same or similar parts in the above embodiments may be mutually referred to, and the same or similar parts in other embodiments may be referred to for the content which is not described in detail in some embodiments.
It should be noted that the terms "first," "second," and the like in the description of the present invention are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. Further, in the description of the present invention, the meaning of "a plurality" means at least two unless otherwise specified.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and alternate implementations are included within the scope of the preferred embodiment of the present invention in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present invention.
It should be understood that portions of the present invention may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, various steps or methods may be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.
It will be understood by those skilled in the art that all or part of the steps carried by the method for implementing the above embodiments may be implemented by hardware related to instructions of a program, which may be stored in a computer readable storage medium, and when the program is executed, the program includes one or a combination of the steps of the method embodiments.
In addition, functional units in the embodiments of the present invention may be integrated into one processing module, or each unit may exist alone physically, or two or more units are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The integrated module, if implemented in the form of a software functional module and sold or used as a separate product, may also be stored in a computer-readable storage medium.
The storage medium mentioned above may be a read-only memory, a magnetic or optical disk, etc.
In the description herein, references to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the invention. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
Although embodiments of the present invention have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present invention, and that variations, modifications, substitutions and alterations can be made to the above embodiments by those of ordinary skill in the art within the scope of the present invention.
Claims (10)
1. An aggregated payment method for a SaaS system, comprising:
receiving a payment request of a user order, wherein the user order comprises a payment type and a user order identifier;
determining a third party payment system gateway corresponding to the payment type;
generating payment order information by the third party payment system gateway according to the user order, wherein the payment order information comprises a payment order identifier, a payment order flow and payment service information;
creating a payment order by the third party payment system gateway according to the payment order information;
if the payment order is successfully established, establishing an association relationship between the user order identification and the payment order identification;
generating a payment link according to the incidence relation and the payment order information, wherein the payment link is used for entering the third-party payment system;
and sending the payment link to the user terminal.
2. The aggregated payment method for a SaaS system according to claim 1, wherein the user order further comprises commodity information and user information, the method further comprising:
obtaining payment state information called back by the third-party payment system gateway, wherein the payment state information comprises payment success, payment failure and payment cancellation;
and if the payment state information recalled back by the third-party payment system gateway is successful in payment, binding the user information and the commodity information.
3. The aggregated payment method for a SaaS system according to claim 2, wherein the user order further includes operator information, and the binding the user information and the commodity information includes:
determining a user order identification associated with the payment order identification;
inquiring the commodity information, the user information and the operator information corresponding to the user order identification;
determining a commodity database corresponding to the operator information;
determining a specified commodity from the commodity database according to the commodity information;
and binding the specified commodity with the user.
4. The aggregated payment method for a SaaS system according to claim 3, further comprising:
and updating the order state of the user order according to the payment state information.
5. The aggregated payment method for a SaaS system according to claim 4, wherein the user order state information in the user order payment request is unpaid, and the updating the payment state of the user order according to the payment state information comprises:
when the payment order is successfully established, modifying the order state of the user order into unpaid payment;
when the payment order is failed to be established, modifying the order state of the user order into a payment error;
and when the payment state information recalled by the third-party payment system gateway is successful in payment, failed in payment and cancelled in payment, synchronously modifying the order states of the user order into successful in payment, failed in payment and cancelled in payment.
6. An aggregated payment device for a SaaS system, comprising:
the order request receiving unit is used for receiving a payment request of a user order, and the user order comprises a payment type and a user order identifier;
the gateway determining unit is used for determining a third party payment system gateway corresponding to the payment type;
the payment order information generating unit is used for generating payment order information by the third-party payment system gateway according to the user order, wherein the payment order information comprises a payment order identifier, a payment order flow and payment service information;
the payment order creating unit is used for creating a payment order by the third party payment system gateway according to the payment order information;
the identification association unit is used for establishing an association relationship between the user order identification and the payment order identification if the payment order is successfully established;
the payment link generation unit is used for generating a payment link according to the incidence relation and the payment order information, and the payment link is used for entering the third-party payment system;
and the payment link sending unit is used for sending the payment link to the user terminal.
7. The aggregated payment apparatus for a SaaS system according to claim 6, wherein the user order further includes commodity information and user information, the apparatus further comprising:
the payment state acquisition unit is used for acquiring payment state information called back by the third-party payment system gateway, wherein the payment state information comprises payment success, payment failure and payment cancellation;
and the commodity binding unit is used for binding the user information and the commodity information if the payment state information recalled back by the third-party payment system gateway is successful in payment.
8. An aggregated payment system for a SaaS system, comprising:
the SaaS service module is used for receiving a user order payment request, wherein the user order comprises a payment type and a user order identifier, determining a third-party payment system gateway corresponding to the payment type, sending a gateway payment request to the aggregation payment module, receiving an incidence relation between the user order identifier and the payment order identifier sent by the aggregation payment module and payment order information, generating a payment link according to the incidence relation and the payment order information, wherein the payment link is used for entering the third-party payment system and sending the payment link to a user terminal, and the gateway payment request comprises the user order identifier;
and the aggregation payment module is used for receiving the gateway payment request, generating payment order information by the third-party payment system gateway according to the user order, creating a payment order by the third-party payment system gateway according to the payment order information, if the payment order is successfully created, establishing an association relation between the user order identifier and the payment order identifier, and sending the association relation and the payment order information to the SaaS service module, wherein the payment order information comprises a payment order identifier, a payment order flow and payment service information.
9. A computer device, comprising: a processor, a memory and a bus, the memory storing machine-readable instructions executable by the processor, the processor and the memory communicating over the bus when a computer device is run, the machine-readable instructions when executed by the processor performing the aggregated payment method for a SaaS system of any of claims 1 to 5.
10. A computer-readable storage medium, having stored thereon a computer program which, when executed by a processor, performs the aggregated payment method for a SaaS system as claimed in any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210481722.8A CN114581088A (en) | 2022-05-05 | 2022-05-05 | Aggregated payment method, device and system for SaaS (software as a service) system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210481722.8A CN114581088A (en) | 2022-05-05 | 2022-05-05 | Aggregated payment method, device and system for SaaS (software as a service) system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114581088A true CN114581088A (en) | 2022-06-03 |
Family
ID=81778457
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210481722.8A Pending CN114581088A (en) | 2022-05-05 | 2022-05-05 | Aggregated payment method, device and system for SaaS (software as a service) system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114581088A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116012013A (en) * | 2022-12-16 | 2023-04-25 | 广州市瑞立德信息***有限公司 | System, method and storage medium for preventing repeated payment of integrated ticket box |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107730366A (en) * | 2017-10-30 | 2018-02-23 | 江西博瑞彤芸科技有限公司 | A kind of information processing method of pay invoice management |
| CN112116438A (en) * | 2020-07-31 | 2020-12-22 | 福建亿能达信息技术股份有限公司 | Multi-channel payment integration method, platform, equipment and medium |
-
2022
- 2022-05-05 CN CN202210481722.8A patent/CN114581088A/en active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107730366A (en) * | 2017-10-30 | 2018-02-23 | 江西博瑞彤芸科技有限公司 | A kind of information processing method of pay invoice management |
| CN112116438A (en) * | 2020-07-31 | 2020-12-22 | 福建亿能达信息技术股份有限公司 | Multi-channel payment integration method, platform, equipment and medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116012013A (en) * | 2022-12-16 | 2023-04-25 | 广州市瑞立德信息***有限公司 | System, method and storage medium for preventing repeated payment of integrated ticket box |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11687914B2 (en) | Processing mobile payments when disconnected from payment servers | |
| CN109064334B (en) | Intelligent contract accounting method, computer device and readable storage medium | |
| TWI640937B (en) | Online payment method and equipment | |
| US20080147552A1 (en) | Electronic payment processing system | |
| CN105447734B (en) | Order information processing method and system | |
| US20090037294A1 (en) | Mobile communication device transaction control systems | |
| CN105046482A (en) | Mobile terminal payment method, device, and system | |
| CN110910230A (en) | Accounting method, accounting system and storage medium | |
| US20200279261A1 (en) | Blockchain-based reconciliation system, method, and apparatus and electronic device | |
| CN113554509B (en) | Processing method, device, medium and electronic equipment for online payment service | |
| CN112184240A (en) | Refund request processing method and device | |
| CN112348326A (en) | Bank business processing method and system | |
| CN114693296A (en) | Coupon management method and device, electronic equipment and storage medium | |
| CN110599133B (en) | Data processing method, device and storage medium based on blockchain network | |
| CN114581088A (en) | Aggregated payment method, device and system for SaaS (software as a service) system | |
| CN110874728A (en) | Online payment system, online payment method, device, medium and server | |
| CN106034148B (en) | Rapid information interaction method, local server, remote server and system | |
| CN110336872B (en) | Method, device and system for acquiring third-party data | |
| CN105354190A (en) | Numerical information transfer method and apparatus | |
| CN105787736A (en) | Data business processing method and device | |
| KR102107454B1 (en) | System for multiplication of financial payment networks, method for financial services using the same and computer program for the same | |
| JP7195016B2 (en) | Transaction processing method, system and program | |
| CN108765138B (en) | Object and fund transfer method and device | |
| CN112669028A (en) | Bill management method and device, computer equipment and computer-readable storage medium | |
| CN113379523A (en) | Bill generation method, device, medium and electronic equipment |
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 |
Application publication date: 20220603 |
|
| RJ01 | Rejection of invention patent application after publication |