CN115018485B - Aggregate payment operation management platform and aggregate payment method - Google Patents

Aggregate payment operation management platform and aggregate payment method Download PDF

Info

Publication number
CN115018485B
CN115018485B CN202210631617.8A CN202210631617A CN115018485B CN 115018485 B CN115018485 B CN 115018485B CN 202210631617 A CN202210631617 A CN 202210631617A CN 115018485 B CN115018485 B CN 115018485B
Authority
CN
China
Prior art keywords
payment
merchant
platform
product
module
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202210631617.8A
Other languages
Chinese (zh)
Other versions
CN115018485A (en
Inventor
谭威强
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Easylink Payment Co ltd
Original Assignee
Easylink Payment Co ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Easylink Payment Co ltd filed Critical Easylink Payment Co ltd
Priority to CN202210631617.8A priority Critical patent/CN115018485B/en
Publication of CN115018485A publication Critical patent/CN115018485A/en
Application granted granted Critical
Publication of CN115018485B publication Critical patent/CN115018485B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

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/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; 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/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401—Transaction verification
    • 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
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange

Abstract

According to the aggregated payment operation management platform and the aggregated payment method, the merchant account opening management module in the platform can manage product information corresponding to products provided for merchants, and the merchant contract management module can manage contract information of the merchants, so that the instantaneity and the effectiveness of the product opened by the platform for the merchants and the contract information between the platform and the merchants are guaranteed, and verification can be performed when the merchants transact with the platform; the transaction inquiry module can inquire and manage transaction information of the merchant, the cash desk authority configuration module can conduct authority configuration on payment modes which can be used by the user when the merchant collects money to the user through the aggregated payment cash desk, and therefore transparency and legality of the transaction between the merchant and the user through the platform are further guaranteed.

Description

Aggregate payment operation management platform and aggregate payment method
Technical Field
The application relates to the technical field of mobile payment, in particular to an aggregate payment operation management platform and an aggregate payment method.
Background
At present, in the daily consumption process, a user often uses a third party payment platform such as a payment bank, weChat payment, beijing east payment, QQ wallet and the like to pay. In order to meet the diversified payment demands of users for payment by using various different types of third party payment platforms, merchants can be in butt joint with an aggregate payment operation management platform to realize an aggregate payment function.
For example, due to the diversification of service scenes, users not only have demands on the existing WeChat applet & public number payment and payment treasured code scanning payment, but also hope to use the payment functions of WeChat, payment treasured APP and the like, merchants can be in butt joint with the aggregate payment operation management platform, so that the aggregate payment function is realized. In the process, as a plurality of merchants are butted by the aggregate payment operation management platform, and certain differences exist between products and transaction authorities opened by each merchant, the management and maintenance difficulty of the aggregate payment operation management platform is high, and the cost is high.
Disclosure of Invention
The purpose of the application is to at least solve one of the technical defects, especially the technical defects of the prior art that the management and maintenance difficulty of the aggregate payment operation management platform is high and the cost is high.
The application provides an aggregate payment operation management platform, which comprises a merchant management module, a receipt application operation module and an aggregate payment cash register;
the merchant management module comprises a merchant account opening management module and a merchant contract management module;
the merchant account opening management module is used for managing product information corresponding to products provided for merchants;
the merchant contract management module is used for managing contract information of merchants;
the order receiving application operation module comprises a transaction inquiry module and a cash desk authority configuration module;
the transaction inquiry module is used for inquiring and managing transaction information of the merchant;
the cash register authority configuration module is used for performing authority configuration on a payment mode which can be used by a user when a merchant collects money to the user through an aggregate payment cash register;
the aggregate payment cash register is used for generating a corresponding payment link for the user to pay according to the payment request of the user.
Optionally, the process that the merchant account opening management module is used for managing the product information corresponding to the product provided to the merchant includes:
and adding, deleting or modifying the product enumeration value in the product list of the newly added contract function page.
Optionally, the process that the merchant account opening management module is used for managing the product information corresponding to the product provided to the merchant includes:
and adding, deleting or modifying the product enumeration value of the product field in the contract details of each contract.
Optionally, the process that the merchant contract management module is used for managing the contract information of the merchant includes:
and adding, deleting or modifying the product name in the contract of the merchant.
Optionally, the transaction inquiry module is used for inquiring and managing transaction information of the merchant, and comprises the following steps:
and adding, deleting or modifying the order sources of the merchants, wherein the order sources comprise an aggregate payment cash register.
Optionally, the cash register authority configuration module is configured to perform authority configuration on payment modes available to the user when the merchant collects money to the user through the aggregate payment cash register, and includes:
when the merchant collects money to the user through the aggregated payment cash desk, the user can use the use state of the payment mode to carry out authority management;
wherein the usage status includes deactivated and activated.
The application also provides an aggregate payment method applied to the aggregate payment cash register in the aggregate payment operation management platform according to any one of the above embodiments, the method comprising:
receiving a payment request sent by a merchant with transaction permission and an opened product, wherein the payment request comprises an order number and a corresponding payment mode;
and generating a payment link of the aggregate payment program running on a third party payment platform based on the order number and the corresponding payment mode, wherein the payment link is used for a user to access the corresponding aggregate payment program and pay to the merchant by using the third party payment platform.
Optionally, the receiving the payment request sent by the merchant with the transaction right and the opened product includes:
receiving a payment request sent by any merchant;
checking whether the merchant opens a product corresponding to the payment request and whether the merchant has transaction permission corresponding to the payment request;
and if the verification is passed, marking the payment request sent by the merchant as the payment request sent by the merchant with the transaction authority and the opened product.
Optionally, the generating a payment link of the aggregated payment procedure cash register running on the third party payment platform based on the order number and the corresponding payment mode includes:
converting the order number into a random character string;
and constructing a payment link of the aggregate payment program running on the third party payment platform by using the random character string and the payment mode corresponding to the order number.
Optionally, the converting the order number into a random string includes:
and converting the order number into a random character string according to the validity period of the order number and the preset character length.
From the above technical solutions, the embodiments of the present application have the following advantages:
according to the aggregated payment operation management platform and the aggregated payment method, when a merchant pays a user, the user can pay through the aggregated payment operation management platform, so that the investment cost of the merchant is greatly reduced; the platform comprises a merchant management module, a receipt application operation module and an aggregate payment cash desk, wherein the merchant management module comprises a merchant account opening management module and a merchant contract management module, the merchant account opening management module can manage product information corresponding to products provided for merchants, and the merchant contract management module can manage contract information of the merchants so as to ensure real-time performance and effectiveness of the products opened by the merchants and contract information between the platform and the merchants, and can verify the transaction between the merchants and the platform; the order receiving application operation module can also comprise a transaction inquiry module and a cash desk authority configuration module, wherein the transaction inquiry module can inquire and manage transaction information of a merchant, and the cash desk authority configuration module can carry out authority configuration on a payment mode which can be used by a user when the merchant collects money to the user through an aggregate payment cash desk, so that transparency and legitimacy of the transaction between the merchant and the user through a platform are further ensured, and management and maintenance difficulty of the aggregate payment operation management platform is effectively reduced; in addition, the aggregate payment cash desk can generate a corresponding payment link for the user to pay according to the payment request of the user, so that the flow management difficulty and the research and development cost of the merchant are effectively reduced.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic structural diagram of an aggregate payment operation management platform provided in an embodiment of the present application;
FIG. 2 is a display diagram of a merchant account opening management interface according to an embodiment of the present application;
FIG. 3 is a display view of a merchant contract management interface provided by an embodiment of the present application;
FIG. 4 is a page display diagram of a transaction query module provided in an embodiment of the present application;
FIG. 5 is a page display view of a transaction detail page of a transaction query module provided by an embodiment of the present application;
fig. 6 is a page display diagram of a cash register authority configuration module provided in an embodiment of the present application;
fig. 7 is a flow chart of an aggregate payment method according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.
At present, due to the diversification of service scenes, users have demands for the existing WeChat applet, public number payment and payment treasured code scanning payment, and hope to use the payment functions of WeChat, payment treasured APP and the like, merchants can be in butt joint with the aggregate payment operation management platform, so that the aggregate payment function is realized. In the process, as a plurality of merchants are butted by the aggregate payment operation management platform, and certain differences exist between products and transaction authorities opened by each merchant, the management and maintenance difficulty of the aggregate payment operation management platform is high, and the cost is high.
Based on this, the following technical scheme is proposed in the present application, see specifically below:
in one embodiment, as shown in fig. 1, fig. 1 is a schematic structural diagram of an aggregate payment operation management platform provided in an embodiment of the present application; the application provides an aggregated payment operation management platform, which can comprise a merchant management module, a receipt application operation module and an aggregated payment cash desk.
The merchant management module may include a merchant account opening management module and a merchant contract management module.
The merchant account opening management module is used for managing product information corresponding to products provided for merchants.
The merchant contract management module is used for managing contract information of merchants.
The order receiving application operation module can comprise a transaction inquiry module and a cash desk authority configuration module.
The transaction inquiry module is used for inquiring and managing transaction information of the merchant.
The cash register authority configuration module is used for performing authority configuration on payment modes which can be used by a user when the merchant collects money to the user through the aggregated payment cash register.
The aggregate payment cash register is used for generating a corresponding payment link for the user to pay according to the payment request of the user.
In this embodiment, as shown in fig. 1, the aggregate payment operation management platform may include an operation management background and an aggregate payment cash register, where the aggregate payment cash register is mainly responsible for directly interfacing with each merchant, for example, generating a corresponding payment link according to a payment request of a user for payment by the user, and the operation management background is mainly responsible for managing contract information, transaction authority and the like in the process of interfacing the aggregate payment cash register with each merchant, thereby forming a complete aggregate payment platform.
The operation management background can be divided into a plurality of management modules, such as a system management authority module, a reconciliation management module, a marketing management module, an operation support module and the like, wherein each module executes corresponding functions, such as the reconciliation management module is mainly responsible for managing the bill information, the marketing management module is mainly used for managing marketing content, and the operation support module is mainly used for managing operation content.
Further, the merchant management module and the acquirer application operation module in the application are mainly all sub-modules under the operation support module. The merchant management module can be divided into a merchant account opening management module and a merchant contract management module, wherein the merchant account opening management module is mainly responsible for managing product information corresponding to products provided for merchants, and the merchant contract management module is mainly responsible for managing contract information of the merchants; the order-receiving application operation module can be divided into a transaction inquiry module and a cash desk authority configuration module, wherein the transaction inquiry module is mainly responsible for inquiring and managing transaction information of merchants, and the cash desk authority configuration module is mainly responsible for performing authority configuration on payment modes which can be used by users when the merchants collect money to the users through an aggregate payment cash desk.
It can be understood that the aggregate payment operation management platform opens various products for each merchant, such as a "public number payment" product, a "applet payment" product, a "mobile phone WAP payment" product, etc., each product corresponds to one or more interfaces for the merchant to call, the aggregate payment operation management platform can view and update the content of each management module in the operation management background in real time so as to meet the service requirements, and the merchant can also open the corresponding product on the aggregate payment operation management platform according to the self and user requirements, contract with the platform, and the platform can also provide corresponding transaction rights for the products opened by the merchant. When the merchant invokes a certain interface to send a payment request to the aggregate payment cash register, the aggregate payment cash register can verify whether the payment request is legal or not according to the data stored in each module, if not, error information is directly returned, and if so, the payment operation is continued.
In the embodiment, when the merchant pays the user, the user can pay the user through the aggregated payment operation management platform, so that the investment cost of the merchant is greatly reduced; the platform comprises a merchant management module, a receipt application operation module and an aggregate payment cash desk, wherein the merchant management module comprises a merchant account opening management module and a merchant contract management module, the merchant account opening management module can manage and maintain product information corresponding to products provided for merchants, and the merchant contract management module can manage and maintain contract information of the merchants, so that the real-time performance and the validity of the products opened by the platform for the merchants and contract information between the platform and the merchants are ensured, and verification can be carried out when the merchants transact with the platform; the order receiving application operation module can also comprise a transaction inquiry module and a cash desk authority configuration module, wherein the transaction inquiry module can inquire and manage transaction information of a merchant, and the cash desk authority configuration module can carry out authority configuration on a payment mode which can be used by a user when the merchant collects money to the user through an aggregate payment cash desk, so that transparency and legitimacy of the transaction between the merchant and the user through a platform are further ensured, and management and maintenance difficulty of the aggregate payment operation management platform is effectively reduced; in addition, the aggregate payment cash desk can generate a corresponding payment link for the user to pay according to the payment request of the user, so that the flow management difficulty and the research and development cost of the merchant are effectively reduced.
In one embodiment, as shown in fig. 2, fig. 2 is a display diagram of a merchant account opening management interface provided in an embodiment of the present application; the process that the merchant account opening management module is used for managing the product information corresponding to the product provided to the merchant can comprise the following steps: and adding, deleting or modifying the product enumeration value in the product list of the newly added contract function page.
In this embodiment, the merchant account opening management module is mainly responsible for managing product information corresponding to products provided to merchants, including, but not limited to, managing product information of opened products, and managing product information of products to be opened. When a new contract is needed and a product type is needed to be added, deleted or modified, the product enumeration value in the original product list in the new contract can be added, deleted or modified, and the product list after the product enumeration value is added, deleted or modified is also applicable to the product list of the opened product.
The newly added product enumeration value may be "skip payment (third party payment platform)" or "main payment (third party payment platform)", etc., and may specifically be set according to the actual service requirement, which is not limited herein.
Further, the functional interface of the merchant account opening management module also displays different products opened by different merchants and different products opened by the same merchant, and each product opened by each merchant has a corresponding first party name, second party name, contract number, state, effective date, expiration date and the like. When a certain merchant sends a payment request to an aggregate payment cash desk, whether the sent payment request is legal or not can be checked according to the product number corresponding to the opened product in each contract number, the effective date, the expiration date and the like.
In one embodiment, the process of the merchant account opening management module for managing product information corresponding to products provided to the merchant may include: and adding, deleting or modifying the product enumeration value of the product field in the contract details of each contract.
In this embodiment, as shown in fig. 2, in the functional interface corresponding to the merchant account opening management module, not only the product opening and the new contract but also contract details corresponding to different contracts are displayed, and when the product enumeration value of the product field needs to be newly added, deleted or modified, the operation of adding, deleting or modifying the product enumeration value can be realized through the technical code.
In one embodiment, as shown in fig. 3, fig. 3 is a display diagram of a merchant contract management interface provided in an embodiment of the present application, where the process of managing contract information of a merchant by using the merchant contract management module may include: and adding, deleting or modifying the product name in the contract of the merchant.
In this embodiment, as shown in fig. 3, the merchant contract management module is configured to perform an operation of adding, deleting or modifying a product name in a merchant contract, for example, adding a product name of "skip payment (third party payment platform)", and may derive details of the checked contract by one key.
Further, the function interface corresponding to the merchant contract management module in the application also displays contract numbers, contract body numbers, application time, application serial numbers, effective dates, expiration dates, states and the like, a user can accurately search by inputting the corresponding contract numbers or contract body numbers or application serial numbers and the like, and the export function can export searched contract details in a key mode, so that the user can conveniently check the contract details.
In one embodiment, as shown in fig. 4 and 5, fig. 4 is a page display diagram of a transaction inquiry module provided in an embodiment of the present application, and fig. 5 is a page display diagram of a transaction detail page of the transaction inquiry module provided in an embodiment of the present application; the transaction inquiry module is used for inquiring and managing transaction information of merchants, and can comprise the following steps:
and adding, deleting or modifying the order sources of the merchants, wherein the order sources comprise an aggregate payment cash register.
In this embodiment, as shown in fig. 4, the transaction inquiry module includes an order source, details, etc., and the application may perform an operation of adding, deleting or modifying the order source of the merchant, and the order source includes, but is not limited to, an aggregate payment checkout counter, i.e. the PC checkout counter in fig. 4.
In addition, the functional interface of the transaction inquiry module also displays the merchant number, the merchant order number, the payment mode, the payment state, the payment result, the payment time confirmation and the like. The transaction inquiry module can inquire and derive the corresponding order state according to the merchant order number corresponding to the payment request.
Further, after clicking the "details" in the transaction inquiry module, a transaction detail page as shown in fig. 5 may be obtained, where the transaction detail page is set with a product number, an order total amount, a payment initiation time, a request time, refund times, an order source, a product name, and the like. When the merchant sends a payment request to the aggregate payment cash desk, namely the PC cash desk, the transaction inquiry module can also acquire the total amount of the order, the product name, the product number, the request time and the like contained in the payment request.
When a merchant sends a payment request to an aggregate payment cash register, the aggregate payment cash register can record detailed order information and modify the payment state, if the payment request is sent for the first time, the payment state is changed into to-be-paid, and after a corresponding payment link is issued, the payment state is changed into in-payment; after the clearing platform returns the corresponding payment result, the aggregate payment cash desk can modify the payment result and fill in and confirm the payment time, so as to record the complete payment process, thereby facilitating the subsequent order inquiry. And when other programs are requested later, the transaction information stored in the payment cash register can be aggregated for feedback.
In one embodiment, as shown in fig. 6, fig. 6 is a page display diagram of a cash register authority configuration module provided in an embodiment of the present application; the process of the cash register authority configuration module for performing authority configuration on a payment mode which can be used by a user when a merchant collects money to the user through an aggregate payment cash register can comprise the following steps:
when the merchant collects money to the user through the aggregated payment cash desk, the user can use the use state of the payment mode to carry out authority management;
wherein the usage status includes deactivated and activated.
In this embodiment, a tag number, a tag name and a use state corresponding to a payment manner of an opened product of each merchant are displayed in a functional interface of the cash register authority configuration module, wherein the tag number and the tag name may be the same, and the use state may include deactivation and activation, and the setting may be performed specifically according to a period of a contract of the merchant.
It can be understood that the merchant displaying the tag number and tag name opens corresponding products, and configures corresponding use states for the products, so that when the merchant sends a payment request to the aggregated payment cash register, the merchant can query the use states of the products corresponding to the payment request for verification.
In one embodiment, as shown in fig. 7, fig. 7 is a schematic flow chart of an aggregate payment method provided in the embodiment of the present application; the application also provides an aggregate payment method applied to the aggregate payment cash register in the aggregate payment operation management platform according to any one of the above embodiments, where the method may include:
s110: and receiving a payment request sent by a merchant with the transaction authority and the opened product.
S120: and generating a payment link of the aggregate payment program running on the third party payment platform based on the order number and the corresponding payment mode.
In this embodiment, after the aggregated payment cash register receives a payment request sent by a merchant that has an opened product and has transaction permission, a payment link of an aggregated payment program running on a third party payment platform can be generated based on an order number and a corresponding payment mode in the payment request, the payment link can be used for a user to access the corresponding aggregated payment program, and the aggregated payment program is used for calling the third party payment platform to pay to the merchant, in this process, transaction information between the merchant and the aggregated payment platform can be saved by the aggregated payment cash register for subsequent query and display, and in addition, the aggregated payment cash register can be checked by a merchant account opening management module, a merchant contract management module and a cash register permission configuration module when receiving the payment request sent by the merchant, so as to verify the validity of the current payment request, thereby further improving transaction security.
The aggregate payment program may be run on any third party payment platform, such as an applet, a public number, etc., without limitation.
Further, after the user makes a payment in the aggregate payment procedure, the third party payment platform can send a payment result to the clearing platform, and after the clearing platform receives the payment result, the third party payment platform sends the payment result to the aggregate payment cash register, or, after receiving the result, the aggregate payment cash register in the application can display the corresponding payment result in the aggregate payment procedure and the PC cash register.
In one embodiment, receiving the payment request sent by the merchant that has opened the product and has the transaction right in S110 may include:
s111: and receiving a payment request sent by any merchant.
S112: and checking whether the merchant opens a product corresponding to the payment request and whether the merchant has transaction permission corresponding to the payment request.
S113: and if the verification is passed, marking the payment request sent by the merchant as the payment request sent by the merchant with the transaction authority and the opened product.
In this embodiment, after the aggregated payment cash register receives a payment request sent by any merchant, the merchant can check whether the merchant opens a product corresponding to the payment request through the merchant account opening management module, and check whether the payment request sent by the merchant has transaction permission through the merchant contract management module and the cash register permission configuration module, if the payment request passes, the current merchant is indicated to have the product opened and the transaction permission is owned, at this time, the payment request sent by the merchant can be marked as the payment request sent by the merchant which has the transaction permission and has the product opened, and a payment link of the aggregated payment program running on the third party payment platform is generated based on an order number and a corresponding payment mode in the payment request, so that the merchant accesses a corresponding payment page through the payment link and then provides the user with payment.
In one embodiment, generating a payment link of the aggregated payment procedure cash register running on the third party payment platform based on the order number and the corresponding payment method in S120 may include:
s121: and converting the order number into a random character string.
S122: and constructing a payment link of the aggregate payment program running on the third party payment platform by using the random character string and the payment mode corresponding to the order number.
In this embodiment, when the aggregated payment cashier generates the payment link, the order number in the payment request may be converted into a random string, and the payment link of the aggregated payment program running on the third party payment platform may be constructed by using the random string and the payment mode corresponding to the order number.
The random character string is a globally unique random character string obtained by special conversion of the order number, and corresponds to the order number one by one, and different payment modes can influence parameters carried in the payment link. Specifically, the payment link generated by the aggregate payment checkout counter may be: the "aggregate paymate domain name/minipay/random string" may, of course, be modified as appropriate, and is not limited in this regard.
In one embodiment, the converting the order number into a random string in S121 may include:
and converting the order number into a random character string according to the validity period of the order number and the preset character length.
In this embodiment, when the order number is converted into the random character string, the preset character length and the validity period corresponding to the order number can be determined first, then the order number is converted into the random character string by using the validity period of the order number and the preset character length, and the generated payment link has a corresponding validity period, and once the order is overtime, the payment link overtime, so that the transaction security is ensured.
Further, the character length may be set according to the actual situation, for example, the character length may be formed by capital and lowercase letters and numerals, or may be formed by numerals and characters, and the length may be 8, 10, 18, etc., which is not limited thereto.
Finally, it is further noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus 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 apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
In the present specification, each embodiment is described in a progressive manner, and each embodiment focuses on the difference from other embodiments, and may be combined according to needs, and the same similar parts may be referred to each other.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims (8)

1. An aggregate payment operation management platform is characterized by comprising a merchant management module, a receipt application operation module and an aggregate payment cash register;
the merchant management module comprises a merchant account opening management module and a merchant contract management module;
the merchant account opening management module is used for managing product information corresponding to products provided for merchants;
the merchant contract management module is used for managing contract information of merchants;
the order receiving application operation module comprises a transaction inquiry module and a cash desk authority configuration module;
the transaction inquiry module is used for inquiring and managing transaction information of the merchant;
the cash register authority configuration module is used for performing authority configuration on a payment mode which can be used by a user when a merchant collects money to the user through an aggregate payment cash register;
the aggregated payment cash register is used for receiving a payment request sent by a merchant with transaction permission and an opened product, and generating a payment link of an aggregated payment program running on a third party payment platform for a user to pay based on an order number and a corresponding payment mode contained in the payment request;
the merchant account opening management module is used for managing product information corresponding to products provided for merchants, and comprises the following steps:
adding, deleting or modifying the product enumeration value in the product list of the newly added contract function page;
and/or adding, deleting or modifying the product enumeration value of the product field in the contract details of each contract.
2. The platform of claim 1, wherein the merchant contract management module is configured to manage contract information for a merchant, comprising:
and adding, deleting or modifying the product name in the contract of the merchant.
3. The platform of claim 1, wherein the transaction inquiry module is configured to inquire and manage transaction information of a merchant, and comprises:
and adding, deleting or modifying the order sources of the merchants, wherein the order sources comprise an aggregate payment cash register.
4. The platform of claim 1, wherein the cash register authority configuration module is configured to perform an authority configuration process for a payment manner available to a user when a merchant collects a payment to the user through an aggregated payment cash register, comprising:
when the merchant collects money to the user through the aggregated payment cash desk, the user can use the use state of the payment mode to carry out authority management;
wherein the usage status includes deactivated and activated.
5. An aggregated payment method applied to an aggregated payment cash desk in an aggregated payment operations management platform according to any of the preceding claims 1-4, characterized in that the method comprises:
receiving a payment request sent by a merchant with transaction permission and an opened product, wherein the payment request comprises an order number and a corresponding payment mode;
and generating a payment link of the aggregate payment program running on a third party payment platform based on the order number and the corresponding payment mode, wherein the payment link is used for a user to access the corresponding aggregate payment program and pay to the merchant by using the third party payment platform.
6. The method of claim 5, wherein receiving a payment request sent by a merchant that has opened a product and has transaction rights comprises:
receiving a payment request sent by any merchant;
checking whether the merchant opens a product corresponding to the payment request and whether the merchant has transaction permission corresponding to the payment request;
and if the verification is passed, marking the payment request sent by the merchant as the payment request sent by the merchant with the transaction authority and the opened product.
7. The method of claim 5, wherein generating a payment link for an aggregated payment procedure cash desk running on a third party paymate based on the order number and corresponding payment means comprises:
converting the order number into a random character string;
and constructing a payment link of the aggregate payment program running on the third party payment platform by using the random character string and the payment mode corresponding to the order number.
8. The method of claim 7, wherein said converting said order number into a random string comprises:
and converting the order number into a random character string according to the validity period of the order number and the preset character length.
CN202210631617.8A 2022-06-06 2022-06-06 Aggregate payment operation management platform and aggregate payment method Active CN115018485B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210631617.8A CN115018485B (en) 2022-06-06 2022-06-06 Aggregate payment operation management platform and aggregate payment method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210631617.8A CN115018485B (en) 2022-06-06 2022-06-06 Aggregate payment operation management platform and aggregate payment method

Publications (2)

Publication Number Publication Date
CN115018485A CN115018485A (en) 2022-09-06
CN115018485B true CN115018485B (en) 2023-06-09

Family

ID=83072621

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210631617.8A Active CN115018485B (en) 2022-06-06 2022-06-06 Aggregate payment operation management platform and aggregate payment method

Country Status (1)

Country Link
CN (1) CN115018485B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115689541A (en) * 2022-12-30 2023-02-03 北京锐融天下科技股份有限公司 Payment system transaction settlement bill generation method and system compatible with digital currency payment

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10304057B1 (en) * 2017-02-07 2019-05-28 Vagabond Vending, LLC Vending equipment for remote selection of items via a mobile device
CN111738706A (en) * 2020-06-23 2020-10-02 江苏苏宁银行股份有限公司 Aggregated payment system, method and equipment
CN113067879A (en) * 2021-03-26 2021-07-02 中国工商银行股份有限公司 Business service method and device based on multiple business service parties and financial system
US11055692B1 (en) * 2020-09-10 2021-07-06 Square, Inc. Application integration for contactless payments

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140089120A1 (en) * 2005-10-06 2014-03-27 C-Sam, Inc. Aggregating multiple transaction protocols for transacting between a plurality of distinct payment acquiring devices and a transaction acquirer
CN106779666A (en) * 2016-11-25 2017-05-31 武汉烽火信息服务有限公司 Polymerization payment platform and method of payment
CN107578224A (en) * 2017-09-13 2018-01-12 深圳前海乘势科技有限公司 The method and device that multi-platform polymerization is paid
CN108460586A (en) * 2018-02-10 2018-08-28 深圳壹账通智能科技有限公司 A kind of amount of money preferential measure, device, terminal device and the storage medium of polymerization payment
CN110555691A (en) * 2018-06-04 2019-12-10 上海硕诺信息科技有限公司 aggregated payment system
CN109829701A (en) * 2018-12-24 2019-05-31 北京航天智造科技发展有限公司 Electric business platform loose coupling on-line payment system
CN112966196A (en) * 2021-03-26 2021-06-15 深圳九星互动科技有限公司 Skip control method, device, system and medium for webpage aggregate payment
CN113723943A (en) * 2021-09-02 2021-11-30 广东付惠吧数据服务有限公司 Make things convenient for commercial tenant account management's polymerization payment platform

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10304057B1 (en) * 2017-02-07 2019-05-28 Vagabond Vending, LLC Vending equipment for remote selection of items via a mobile device
CN111738706A (en) * 2020-06-23 2020-10-02 江苏苏宁银行股份有限公司 Aggregated payment system, method and equipment
US11055692B1 (en) * 2020-09-10 2021-07-06 Square, Inc. Application integration for contactless payments
CN113067879A (en) * 2021-03-26 2021-07-02 中国工商银行股份有限公司 Business service method and device based on multiple business service parties and financial system

Also Published As

Publication number Publication date
CN115018485A (en) 2022-09-06

Similar Documents

Publication Publication Date Title
US8738476B2 (en) Architectural design for selling standardized services application software
US20180046947A1 (en) Data processing framework
US8332378B2 (en) File listener system and method
CN108960941A (en) E-payment billing method
CN115018485B (en) Aggregate payment operation management platform and aggregate payment method
US20150012400A1 (en) Systems and methods for switching credit card accounts
KR20010008360A (en) A credit card payment method for electronic commerce
CN112862548A (en) Intelligent processing management system for issuing invoices and management method thereof
US20110119178A1 (en) Metadata driven processing
KR100942828B1 (en) Voucher total management system and voucher adjustment method using the same
US20110119188A1 (en) Business to business trading network system and method
CN108009794A (en) A kind of method and apparatus of electronics authority condition managing
KR101984620B1 (en) Electronic Payment System
CN109377155A (en) The loan information measures and procedures for the examination and approval and device
CN110490535A (en) Lease class financial affair work management integration management service system
KR100476236B1 (en) System and method for treating sales check of credit card based on Internet
US11514490B2 (en) System and process for electronic calendar payments
US20190197541A1 (en) Real-time monitoring system
AU2010322244B2 (en) Business to business trading network system and method
KR102597510B1 (en) the managing and processing of payment of advance payments
CN116562949A (en) Method for combining mobile payment and electronic invoice issuing
KR20030003434A (en) Method for Internet Banking Service in Enterprise using Internet
CN115545946A (en) Financing management system and method
KR20070040194A (en) System and method for operating integrated points by using mobile devices number, devices for operating points, recording medium and information storing medium
KR20070040182A (en) System for operating certificate gift issued by bank, devices for operating certificate gift and recording medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant