CN115423543A - Payment billing method, device, platform, equipment, medium and product - Google Patents
Payment billing method, device, platform, equipment, medium and product Download PDFInfo
- Publication number
- CN115423543A CN115423543A CN202211015077.7A CN202211015077A CN115423543A CN 115423543 A CN115423543 A CN 115423543A CN 202211015077 A CN202211015077 A CN 202211015077A CN 115423543 A CN115423543 A CN 115423543A
- Authority
- CN
- China
- Prior art keywords
- order
- payment
- invoicing
- request
- billing
- 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
- G06Q30/00—Commerce
- G06Q30/04—Billing or invoicing
Landscapes
- Business, Economics & Management (AREA)
- Development Economics (AREA)
- Accounting & Taxation (AREA)
- Economics (AREA)
- Finance (AREA)
- Marketing (AREA)
- Strategic Management (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The application discloses a payment billing method, a payment billing device, a payment billing platform, equipment, a medium and a product, which belong to the technical field of data processing, and the method comprises the following steps: acquiring billing information of the first order under the condition that the payment of the first order is finished; generating an invoicing request based on the invoicing information of the first order; sending an invoicing request of the first order to the payment platform so that the payment platform checks the invoicing request based on the payment transaction information of the first order; and under the condition that the invoicing request is matched with the payment transaction information, receiving an invoicing result of the first order sent by the payment platform, wherein the invoicing result is generated based on the invoicing request. According to the embodiment of the application, the billing supervision degree can be increased, and the billing behavior is standardized.
Description
Technical Field
The application belongs to the technical field of electronic invoices, and particularly relates to a payment billing method, a payment billing device, a payment billing platform, a payment billing device, a payment billing medium and a payment billing product.
Background
With the rapid development of the internet, payment modes are more and more diversified, and at present, electronic payment has become a main payment mode in daily life of people due to the characteristics of convenience and quickness.
In the related technology, a user usually has a billing requirement after completing bill payment, at this time, a merchant can apply for invoicing on a third-party invoice service platform, and the third-party invoice service platform obtains an invoice through docking with a tax system. However, the invoicing mode has supervision loopholes, insufficient supervision, and non-standard behaviors of no real transaction false invoicing, inconsistency of invoicing information with real payment transaction conditions and the like.
Disclosure of Invention
The embodiment of the application provides a payment billing method, a payment billing device, a payment billing platform, payment billing equipment, payment billing media and payment billing products, which can increase billing supervision and standardize billing behaviors.
In a first aspect, an embodiment of the present application provides a payment billing method, where the method includes: acquiring billing information of the first order under the condition that the payment of the first order is finished; generating an invoicing request based on the invoicing information of the first order; sending an invoicing request of the first order to the payment platform so that the payment platform checks the invoicing request based on the payment transaction information of the first order; and under the condition that the invoicing request is matched with the payment transaction information, receiving an invoicing result of the first order sent by the payment platform, wherein the invoicing result is generated based on the invoicing request.
In a second aspect, an embodiment of the present application provides a payment billing method, which is applied to a payment platform, and includes: under the condition that the payment of the first order is completed, receiving an invoicing request of the first order sent by a merchant system or an order receiving system to obtain payment transaction information of the first order; verifying the invoicing request of the first order based on the payment transaction information; under the condition that the billing request is matched with the payment transaction information, forwarding the billing request to a bill management system so that the bill management system performs billing based on the billing request to generate a billing result; and under the condition of receiving the billing result sent by the bill management system, sending the billing result to the merchant system or the acquiring system.
In a third aspect, an embodiment of the present application provides a payment billing apparatus, including: the acquisition module is used for acquiring the billing information of the first order under the condition that the payment of the first order is completed; the generating module is used for generating an invoicing request based on the invoicing information of the first order; the payment platform comprises a sending module and a receiving module, wherein the sending module is used for sending an invoicing request of a first order to the payment platform so that the payment platform checks the invoicing request based on payment transaction information of the first order; the receiving module is used for receiving the invoicing result of the first order sent by the payment platform under the condition that the invoicing request is matched with the payment transaction information, and the invoicing result is generated based on the invoicing request.
In a fourth aspect, an embodiment of the present application provides a payment platform, including: the receiving module is used for receiving an invoicing request of the first order sent by the merchant system or the order receiving system under the condition that the payment of the first order is completed; the acquisition module is used for acquiring payment transaction information of the first order; the checking module is used for checking the invoicing request of the first order based on the payment transaction information; the forwarding module is used for forwarding the billing request to the bill management system under the condition that the billing request is matched with the payment transaction information, so that the bill management system performs billing based on the billing request to generate a billing result; and the sending module is used for sending the billing result to the merchant system or the acquiring system under the condition of receiving the billing result sent by the bill management system.
In a fifth aspect, an embodiment of the present application provides an electronic device, including: a processor and a memory storing computer program instructions; the steps of the payment invoicing method of the first or second aspect are implemented by a processor executing computer program instructions.
In a sixth aspect, the present application provides a computer-readable storage medium, on which a program or instructions are stored, which when executed by a processor implement the steps of the payment billing method as shown in the first or second aspect.
In a seventh aspect, the present application provides a computer program product, which is stored in a non-volatile storage medium, and when executed by at least one processor, implements the steps of the payment billing method according to the first aspect or the second aspect.
In an eighth aspect, embodiments of the present application provide a chip, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to execute a program or instructions to implement the steps of the payment billing method according to the first aspect or the second aspect.
The embodiment of the application provides a payment billing method, a payment billing device, a payment billing platform, payment billing equipment, a payment billing medium and a payment billing product, and acquiring the billing information of the first order under the scene that billing is needed for the transaction when the payment of the first order is completed, and generating a billing request based on the billing information of the first order. The payment link of the first order is completed by the payment platform, so that the payment transaction information of the first order acquired by the payment platform is real and accurate, and the payment platform can verify the invoicing request based on the real and accurate payment transaction information by sending the invoicing request of the first order to check whether the invoicing request is matched with the real payment transaction information. And the merchant can obtain the invoicing result of the first order only in the scene that the invoicing request is matched with the payment transaction information. That is, for the case that the invoicing request does not accord with the real payment transaction condition or the invoicing condition of the real transaction is not carried out, the merchant can not obtain the invoicing. Therefore, the embodiment of the application can ensure that the fund flow is consistent with the invoice flow, improve the phenomenon of no real transaction false invoicing, increase the invoicing supervision and standardize the invoicing behavior.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required to be used in the embodiments of the present application will be briefly described below, and for those skilled in the art, other drawings may be obtained according to the drawings without creative efforts.
Fig. 1 is an architecture diagram of an example of an application scenario of a payment billing method provided in an embodiment of the present application;
fig. 2 is an architecture diagram of another example of an application scenario of a payment billing method provided in an embodiment of the present application;
fig. 3 is a flowchart of an embodiment of a payment billing method provided in the first aspect of the present application;
FIG. 4 is a flow chart of an embodiment of a method of billing payment provided by a second aspect of the present application;
fig. 5 is a schematic structural diagram of an embodiment of a payment billing apparatus provided in the third aspect of the present application;
FIG. 6 is a schematic structural diagram of an embodiment of a payment platform provided in the fourth aspect of the present application;
fig. 7 is a schematic structural diagram of an embodiment of an electronic device provided in a fifth aspect of the present application.
Detailed Description
Features of various aspects and exemplary embodiments of the present application will be described in detail below, and in order to make objects, technical solutions and advantages of the present application more apparent, the present application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are intended to be illustrative only and are not intended to be limiting. It will be apparent to one skilled in the art that the present application may be practiced without some of these specific details. The following description of the embodiments is merely intended to provide a better understanding of the present application by illustrating examples thereof.
With the rapid development of the internet, payment modes are more and more diversified, and at present, electronic payment has become a main payment mode in daily life of people due to the characteristics of convenience and quickness. In the related technology, a user usually has a billing requirement after completing bill payment, at this time, a merchant can apply for invoicing on a third-party invoice service platform, and the third-party invoice service platform obtains an invoice through docking with a tax system.
However, in the related art, the payment transaction link is usually completed through a payment platform, and the invoicing link is completed through a third-party invoice service platform, so that the payment transaction link and the invoicing link are respectively completed by two parties and are relatively independent and split. Because the third-party invoice service platform does not relate to the payment transaction link, real and accurate payment transaction information cannot be obtained, the invoicing request cannot be verified, the monitoring loophole exists, and irregular invoicing behaviors such as no real transaction false invoicing, inconsistency between the invoicing information and the real payment transaction condition and the like easily occur.
Based on the above problems, embodiments of the present application provide a payment billing method, device, platform, device, medium, and product, where a payment transaction link and a billing link are both completed through a payment platform, and the payment platform can obtain real and accurate payment transaction information, so that a billing request is verified through the real payment transaction information, whether the billing request matches with the real payment transaction information can be checked, and a merchant can obtain a billing result of a first order only in a scenario where the billing request matches with the payment transaction information. That is, for the case that the invoicing request does not accord with the real payment transaction condition or the invoicing condition of the real transaction is not carried out, the merchant can not obtain the invoicing. Therefore, the embodiment of the application can ensure that the fund flow is consistent with the invoice flow, improve the phenomenon of no real transaction false invoicing and increase the invoicing supervision.
The payment billing method in the embodiment of the present application may be applied to a billing scenario after completion of a payment transaction, and the payment billing architecture in the embodiment of the present application is described in detail below with reference to fig. 1 and fig. 2.
Fig. 1 is a schematic architecture diagram of an example of an application scenario of a payment billing method provided in an embodiment of the present application, in which the payment billing method may involve a merchant system, a payment platform, and a ticket management system.
As shown in fig. 1, the architecture system of the payment billing method may include a merchant system 11, a payment platform 12, and a ticket management system 13.
The merchant system 11 may be configured to interact with the payment platform 12 in the payment billing process, and may include one or more electronic devices, where the electronic devices may specifically be a mobile phone, a tablet computer, an intelligent wearable device, an intelligent sales device (Point of sales, a Point), an edge device, or a cloud service device, and the like, and the types and the number of the electronic devices in the merchant system 11 are not limited herein. In the payment billing scenario shown in fig. 1, the merchant system 11 may send a billing request to the payment platform 12, so that the payment platform 12 verifies the billing request.
The payment platform 12 can be used for communicating with the merchant system 11 and the bill management system 13 respectively, and the payment platform 12 can receive and verify the invoicing request sent by the merchant system 11, and forward the invoicing request to the bill management system 13 when the invoicing request passes the verification. Meanwhile, the payment platform 12 may provide transmission of payment resources for the payment service and the collection service, thereby completing deduction of a payment account and collection of a collection account, and may also be used for verification, control, clearing of payment risks, and the like.
The bill management system 13 has a function of issuing bills, can be in communication and butt joint with the payment platform 12, receives an invoicing request sent by the payment platform 12, issues bills based on the invoicing request to obtain an invoicing result, and returns the invoicing result to the payment platform 12.
Fig. 2 is a schematic architecture diagram of another example of an application scenario of a payment billing method provided in an embodiment of the present application, in which the payment billing method may involve a merchant system, an acquiring system, a payment platform, and a bill management system
As shown in fig. 2, the architecture system of the payment billing method may include a merchant system 11, a payment platform 12, a ticket management system 13, and an acquiring system 14.
In the payment billing scenario shown in fig. 2, the merchant system 11 may send billing information to the acquiring system 14, and the acquiring system 14 may generate a billing request based on the billing information, and based on this, the acquiring system 14 may send the billing request to the payment platform 12, so that the payment platform 12 verifies the billing request.
The payment billing method provided by the embodiment of the present application is explained in detail based on the payment billing architecture provided by the embodiment of the present application shown in fig. 1 and 2.
The first aspect of the present application provides a payment billing method, which may be applied to a merchant system or an acquiring system, that is, the payment billing method may be executed by the merchant system or the acquiring system. For specific contents of the merchant system or the acquirer system, reference may be made to the relevant description in the above embodiments, and details are not described here.
Fig. 3 is a flowchart of an embodiment of a payment billing method provided in the first aspect of the present application. As shown in fig. 3, the payment billing method may include steps 310 to 340.
In step 310, when the payment of the first order is completed, obtaining the billing information of the first order.
In step 320, an invoicing request is generated based on the invoicing information of the first order.
And 340, receiving the invoicing result of the first order sent by the payment platform under the condition that the invoicing request is matched with the payment transaction information.
Wherein the billing result is generated based on the billing request.
According to the payment billing method provided by the embodiment of the application, under the scene that the payment of the first order is finished and the billing for the transaction payment needs to be carried out, the merchant system or the billing system can obtain the billing information of the first order and generate the billing request based on the billing information of the first order. On the basis, the payment transaction link of the first order is completed by the payment platform, so that the payment transaction information of the first order acquired by the payment platform is real and accurate, the invoicing request can be verified by the payment platform based on the real and accurate payment transaction information by sending the invoicing request of the first order to check whether the invoicing request is matched with the real payment transaction information, and the merchant can acquire the invoicing result of the first order only in the scene that the invoicing request is matched with the payment transaction information. That is, for the case that the invoicing request does not accord with the real payment transaction condition or the invoicing condition of the real transaction is not carried out, the merchant can not obtain the invoicing. Therefore, the embodiment of the application can ensure that the fund flow is consistent with the invoice flow, improve the phenomenon of no real transaction false invoicing and increase the invoicing supervision.
The following describes specific implementation of the above steps in detail with reference to embodiments, and the specific implementation is as follows.
Referring to step 310, in the event that payment for the first order is complete, billing information for the first order is obtained.
The first order may be an order in which the payment transaction process is completed in the merchant system, that is, the payer of the first order has successfully deducted the money; the billing information may include, but is not limited to: seller information, buyer information, tax rate, tax amount, transaction details, and commodity details.
The seller information and the buyer information may include fields such as name, taxpayer identification number, account opening row, account opening number, etc.
In one embodiment, the buyer information in the billing information is associated with the payer, for example, the buyer information may be personal information of the payer, and may also be enterprise information associated with the payer.
For example, user a often purchases office supplies for a business, then user a may fill in the business invoice header based on the business information and set it as default payer information.
In some embodiments of the present application, the merchant system may directly interface with the payment platform, and the merchant system directly sends an invoicing request to the payment platform, and the method may be applied to the merchant system shown in fig. 1, where step 310 may specifically include: and acquiring the billing information of the first order under the condition of receiving the payment result of the first order sent by the payment platform.
Specifically, the payment result is used to characterize the completion of the payment of the first order; since there is usually a billing demand after the user completes the order payment, the merchant system may obtain billing information of the first order after the order payment is completed, and generate a billing request based on the billing information.
In the embodiment of the application, after the first order transaction is finished, the merchant system may automatically obtain the billing information of the first order and generate a billing request. The merchant system does not need to communicate with a third-party invoice service platform, the effective verification of the invoicing request is realized by sending the invoicing request to the payment platform, the phenomenon that the invoicing request is inconsistent with the real payment transaction condition can be avoided, the merchant foreground can issue invoices without sensing, manual operation is not needed, the invoicing process is simplified, and the invoicing efficiency and the invoicing experience are improved.
In one embodiment, the method may further comprise: and receiving the buyer information sent by the user terminal.
Specifically, when the first order payment is completed, that is, the deduction is completed, the user terminal may display the billing option on the billing interface for the user to select, and after the user checks the billing option and selects the invoice heading, the user terminal may send the buyer information to the merchant system, so that the merchant system obtains the buyer information.
In other embodiments of the present application, the acquiring system may directly interface with the payment platform, and the acquiring system directly sends the billing request to the payment platform, and the method may be applied to the acquiring system shown in fig. 2, and step 310 may specifically include: receiving the billing information of the first order sent by the merchant system under the condition that the payment of the first order is completed; after step 340, the method may further specifically include: and forwarding the billing result of the first order to the merchant system.
Specifically, when the payment of the first order is completed, the merchant system may send the billing information of the first order to the acquiring system, so that the acquiring system generates a billing request based on the billing information, and forwards the billing request to the payment platform. And under the condition that the billing request passes the verification, the billing system can receive the billing result returned by the payment platform, and the billing result is forwarded to the merchant system to complete the payment billing process.
In the embodiment of the application, the invoice system can be used as an information transmission medium between the merchant system and the payment platform to assist the merchant system in completing the verification process of the invoicing request, so that the phenomenon that the invoicing request is inconsistent with the real payment transaction condition is avoided, the flexible and convenient invoicing service is realized, and the invoicing experience is improved.
Involving step 320, an invoicing request is generated based on the invoicing information of the first order.
Specifically, the merchant system or the acquiring system may add the billing information to the billing request, so that the billing request includes a content field of the billing information.
Involving step 330, sending an invoicing request for the first order to the payment platform, such that the payment platform verifies the invoicing request based on the payment transaction information for the first order.
The payment transaction information may include, but is not limited to: the order identification, the transaction details, the commodity category, and the transaction details may include information related to payment, such as information of a payer, information of a payee, a payment amount, and a payment time, and are not limited herein. The payment payee information may include information such as a merchant name and a merchant account, and the payment payer information may include information such as a payer account, payer payment card information and a payer identification, which are not limited herein.
In some embodiments of the present application, the method may further comprise: under the condition that the first order payment is completed, acquiring an order identification of the first order; step 330 may specifically include: and sending an invoicing request and an order identification of the first order to the payment platform, so that the payment platform acquires payment transaction information of the first order based on the order identification.
Specifically, the order identifier is a unique identifier of the order, for example, the order identifier may be an order serial number, and the payment platform may query, based on the order identifier, payment transaction information associated with the order identifier, that is, real payment transaction information of the first order, in the database by sending the order identifier to the payment platform. If the payment platform does not inquire the order identification of the first order in the database, that is, the payment transaction information of the first order is not acquired, the invoicing request is the false invoicing without real transaction.
In the embodiment of the application, when the invoicing request is sent to the payment platform, the order identification is sent to the payment platform together, so that the payment platform can obtain real payment transaction information of the first order based on the order identification, check the invoicing request based on the real payment transaction information, check whether the invoicing request is matched with the real payment transaction information or not, and realize effective check of the invoicing request and effective supervision of a payment invoicing process.
Involving step 340, receiving an invoicing result of the first order sent by the payment platform in case the invoicing request matches the payment transaction information.
In some embodiments of the present application, in a case that the invoicing request and the payment transaction information satisfy the first matching condition and the second matching condition, it is described that the invoicing request is matched with the payment transaction information, and the invoicing request is verified to be passed; the first matching condition may include that the order marking, the transaction detail and the commodity type in the billing request and the payment transaction information are consistent, and the billing state of the order corresponding to the order marking is a target state; the second matching condition may include that the invoiced amount in the invoicing request is less than or equal to the transaction amount in the payment transaction information.
Specifically, the first matching condition and the second matching condition may be used to determine whether the billing request matches the payment transaction information, and if the billing request and the payment transaction information satisfy the first matching condition and the second matching condition, it indicates that the billing request matches the payment transaction information, and the billing request passes verification, and at this time, the payment platform may forward the billing request to the bill management system, so that the bill management system makes an invoice to obtain a billing result.
The billing state can be divided into a billed state and an unpinned state, and the target state can be an unpinned state.
In one example, the order identifier of the first order is abc, and if the payment platform queries that the invoicing state of the order corresponding to the abc is "invoiced state", it indicates that the order corresponding to the abc has invoiced the corresponding invoice, so that it may be determined that the invoicing request is a repeated invoicing behavior.
In another example, if the invoicing amount in the invoicing request is 120 and the transaction amount is 100, the invoicing amount exceeds the transaction amount, so that the invoicing request is determined to be inconsistent with the real payment transaction condition.
In the embodiment of the application, illegal invoicing behaviors that the invoicing request is inconsistent with the payment transaction information can be timely sensed by checking order identification, transaction detail and commodity types in the invoicing request and the payment transaction information; the illegal behavior of repeated invoicing of the same transaction of a merchant can be monitored by checking the invoicing state of the order corresponding to the order mark; by checking the invoicing amount in the invoicing request and the transaction amount in the payment transaction information, the condition that the invoicing amount exceeds the actual transaction amount can be avoided, the condition that the invoicing amount is consistent with the invoice flow is ensured, the phenomenon that the invoicing cost is higher due to the fact that the invoicing amount exceeds the actual transaction amount is improved, and the merchant invoicing behavior is effectively monitored.
The second aspect of the present application provides a payment billing method, which can be applied to a payment platform, that is, the payment billing method can be executed by the payment platform. For details of the payment platform, reference may be made to the related description in the above embodiments, and details are not repeated herein.
Fig. 4 is a flowchart of an embodiment of a payment billing method provided in the second aspect of the present application. As shown in fig. 4, the payment billing method may include steps 410 to 450.
And step 410, receiving an invoicing request of the first order sent by the merchant system or the order receiving system under the condition that the payment of the first order is completed.
At step 420, payment transaction information for the first order is obtained.
Specifically, the first order is an order with completed payment, and since the payment transaction link of the first order is completed through the payment platform, the payment transaction information of the first order is stored in the database of the payment platform, and the payment platform can directly obtain the payment transaction information.
In one embodiment, step 410 may specifically include: receiving an invoicing request and an order mark of a first order sent by a merchant system or an order receiving system; step 420 may specifically include: payment transaction information for the first order is obtained based on the order identification.
Specifically, the payment platform may query an order identifier of the first order in the database, and obtain payment transaction information of the first order based on the order identifier when the order identifier is queried, so as to check the invoicing request based on the payment transaction information in the next step; if the order identification is not inquired and further the payment transaction information of the first order cannot be acquired, the invoicing request is determined to be no real transaction virtual invoicing.
In the embodiment of the application, the payment transaction link of the first order is completed through the payment platform, so that the payment platform acquires the payment transaction information of the first order based on the order identification, the authenticity and the accuracy of the payment transaction information can be ensured, and the accuracy and the validity of a verification result are ensured when the invoicing request is verified based on the payment transaction information.
The invoicing request for the first order is verified based on the payment transaction information, step 430.
In some embodiments of the present application, step 430 may specifically include: and under the condition that the invoicing request and the payment transaction information meet the first matching condition and the second matching condition, determining that the invoicing request is matched with the payment transaction information, and verifying the invoicing request to pass.
The first matching condition comprises that the invoicing request is consistent with an order mark, a transaction detail and a commodity type in the payment transaction information, and the invoicing state of the order corresponding to the order mark is a target state; the second matching condition includes that the invoiced amount in the invoicing request is less than or equal to the transaction amount in the payment transaction information.
The first matching condition and the second matching condition can be used for judging whether the invoicing request is matched with the payment transaction information or not, if the invoicing request and the payment transaction information meet the first matching condition and the second matching condition, the invoicing request is matched with the payment transaction information, the invoicing request is verified to be passed, and at the moment, the payment platform can forward the invoicing request to the bill management system, so that the bill management system can invoice to obtain an invoicing result.
The billing state can be divided into a billed state and an unpinned state, and the target state can be an unpinned state.
In the embodiment of the application, illegal invoicing behaviors that the invoicing request is inconsistent with the payment transaction information can be timely sensed by checking order identification, transaction detail and commodity types in the invoicing request and the payment transaction information; illegal invoicing behaviors of repeated invoicing of the same transaction of a merchant can be monitored by checking the invoicing state of the order corresponding to the order mark; by checking the invoicing amount in the invoicing request and the transaction amount in the payment transaction information, the condition that the invoicing amount exceeds the actual transaction amount can be avoided, the condition that the invoicing amount is consistent with the invoice flow is ensured, the phenomenon that the invoicing cost is higher due to the fact that the invoicing amount exceeds the actual transaction amount is improved, and the merchant invoicing behavior is effectively monitored.
In some embodiments of the present application, the payment platform may include an invoicing system, and step 430 may specifically include: the invoicing system takes the tax number of the payee of the first order as an index and verifies whether the invoicing request is matched with the payment transaction information.
Specifically, the payment platform can be directly connected with the bill management system through the billing system, the billing system can obtain the tax number of a payee (namely, a merchant and a seller) of the first order from the billing request, the tax number is used as an index, the payment transaction information is inquired in the database, and whether the billing request is matched with the payment transaction information or not is verified.
And step 440, forwarding the billing request to the bill management system under the condition that the billing request is matched with the payment transaction information, so that the bill management system performs billing based on the billing request to generate a billing result.
Specifically, after receiving an invoicing request sent by the payment platform, the ticket management system can perform invoicing based on the invoicing request to generate an invoicing result, and return the invoicing result to the payment platform.
In one embodiment, in the case that the invoicing request is not matched with the payment transaction information, the payment platform sends an invoicing feedback message to the merchant system or the acquiring system, wherein the invoicing feedback message is used for representing that the invoicing request is not matched with the payment transaction information and rejecting the invoicing.
And step 450, sending the billing result to the merchant system or the acquiring system under the condition of receiving the billing result sent by the bill management system.
In the embodiment of the application, the payment transaction link of the first order is completed by the payment platform, so that the payment transaction information of the first order acquired by the payment platform is real and accurate, and the payment platform can check the invoicing request based on the real and accurate payment transaction information by sending the invoicing request of the first order to the payment platform so as to check whether the invoicing request is matched with the real payment transaction information or not, so that the condition that the fund flow is consistent with the invoice flow can be ensured, and the invoicing supervision is strengthened. And only in the scene that the billing request is matched with the payment transaction information, the payment platform can send the billing request to the bill management system, so that the bill management system generates a billing result based on the billing request, and the guarantee is provided for the billing process of the bill. Therefore, the payment platform can provide the consistent circulation of payment and bill information, is directly connected with the bill management system, provides the bill making request checking capability for the bill management system, and solves the problems of information loss, fragmentation, information islanding and the like of front and back links in the bill circulation process.
Based on the same inventive concept, the third aspect of the present application provides a payment billing device. Fig. 5 is a schematic structural diagram of an embodiment of a payment billing apparatus according to a third aspect of the present application.
The payment billing apparatus 500 can be applied to the merchant system 11 shown in fig. 1 or the acquirer system 14 shown in fig. 2.
As shown in fig. 5, the payment billing apparatus 500 may specifically include: an obtaining module 510, configured to obtain billing information of a first order when payment of the first order is completed; a generating module 520, configured to generate an invoicing request based on the invoicing information of the first order; a sending module 530, configured to send an invoicing request of the first order to the payment platform, so that the payment platform verifies the invoicing request based on the payment transaction information of the first order; the receiving module 540 is configured to receive an invoicing result of the first order sent by the payment platform when the invoicing request is matched with the payment transaction information, where the invoicing result is generated based on the invoicing request.
According to the payment billing device provided by the embodiment of the application, in a scene that billing needs to be performed on the transaction when the payment of the first order is completed, billing information of the first order is obtained, and a billing request is generated based on the billing information of the first order. The payment link of the first order is completed by the payment platform, so that the payment transaction information of the first order acquired by the payment platform is real and accurate, and the payment platform can verify the invoicing request based on the real and accurate payment transaction information by sending the invoicing request of the first order to check whether the invoicing request is matched with the real payment transaction information. And the merchant can obtain the invoicing result of the first order only in the scene that the invoicing request is matched with the payment transaction information. That is, for the case that the invoicing request does not accord with the real payment transaction condition or the invoicing condition of the real transaction is not carried out, the merchant can not obtain the invoicing. Therefore, the embodiment of the application can ensure that the fund flow is consistent with the invoice flow, improve the phenomenon that no real transaction invoices are made falsely, increase the invoicing supervision degree and standardize the invoicing behavior.
The following describes in detail the payment billing apparatus 500 provided in the embodiment of the present application.
In some embodiments of the present application, the apparatus further comprises: an obtaining module 510, configured to obtain an order identifier of a first order when payment of the first order is completed; the sending module 530 is specifically configured to send an invoicing request and an order identifier of the first order to the payment platform, so that the payment platform obtains payment transaction information of the first order based on the order identifier.
In some embodiments of the present application, in the case where the invoicing request and the payment transaction information satisfy the first matching condition and the second matching condition, the invoicing request is matched with the payment transaction information; the first matching condition comprises that the invoicing request is consistent with an order mark, transaction details and commodity types in the payment transaction information, and the invoicing state of the order corresponding to the order mark is a target state; the second matching condition includes that the invoiced amount in the invoicing request is less than or equal to the transaction amount in the payment transaction information.
In some embodiments of the present application, the apparatus is applied to a merchant system, and the obtaining module 510 is specifically configured to: and acquiring the billing information of the first order under the condition of receiving the payment result of the first order sent by the payment platform, wherein the payment result is used for representing the completion of the payment of the first order.
In some embodiments of the present application, the apparatus is applied to an acquiring system, and the obtaining module 510 is specifically configured to: receiving the billing information of the first order sent by the merchant system under the condition that the payment of the first order is completed; the device also includes: and the forwarding module is used for forwarding the invoicing result of the first order to the merchant system after receiving the invoicing result of the first order sent by the payment platform.
Based on the same inventive concept, the fourth aspect of the present application provides a payment platform. Fig. 6 is a schematic structural diagram of an embodiment of a payment platform provided in the fourth aspect of the present application.
As shown in fig. 6, the payment platform 600 may specifically include: a receiving module 610, configured to receive an invoicing request of a first order sent by a merchant system or an order receiving system when payment of the first order is completed; an obtaining module 620, configured to obtain payment transaction information of the first order; a verification module 630 for verifying the invoicing request of the first order based on the payment transaction information; the forwarding module 640 is configured to forward the billing request to the ticket management system when the billing request is matched with the payment transaction information, so that the ticket management system performs billing based on the billing request to generate a billing result; and the sending module 650 is configured to send the billing result to the merchant system or the acquiring system when the billing result sent by the bill managing system is received.
According to the payment platform provided by the embodiment of the application, the payment transaction link of the first order is completed by the payment platform, so that the payment transaction information of the first order acquired by the payment platform is real and accurate, and the payment platform can check the invoicing request based on the real and accurate payment transaction information by sending the invoicing request of the first order to the payment platform so as to check whether the invoicing request is matched with the real payment transaction information or not, so that the condition that a fund flow is consistent with an invoice flow can be ensured, and the invoicing supervision is enhanced. And only in the scene that the billing request is matched with the payment transaction information, the payment platform can send the billing request to the bill management system, so that the bill management system generates a billing result based on the billing request, and the guarantee is provided for the billing process of the bill. Therefore, the payment platform can provide the consistent circulation of payment and bill information, is directly connected with the bill management system, provides the bill making request checking capability for the bill management system, and solves the problems of information loss, fragmentation, information islanding and the like of the front link and the rear link in the bill circulation process.
In some embodiments of the present application, the receiving module 610 is specifically configured to: receiving an invoicing request and an order identification of a first order sent by a merchant system or an order receiving system; the obtaining module 620 is specifically configured to: payment transaction information for the first order is obtained based on the order identification.
In some embodiments of the present application, the checking module 630 is specifically configured to: under the condition that the invoicing request and the payment transaction information meet the first matching condition and the second matching condition, the invoicing request is determined to be matched with the payment transaction information, and the invoicing request passes the verification; the first matching condition comprises that the invoicing request is consistent with an order mark, a transaction detail and a commodity type in the payment transaction information, and the invoicing state of the order corresponding to the order mark is a target state; the second matching condition includes that the invoiced amount in the invoicing request is less than or equal to the transaction amount in the payment transaction information.
In some embodiments of the present application, the payment platform includes an invoicing system for verifying whether the invoicing request matches the payment transaction information indexed by a tax number of the payee of the first order.
The fifth aspect of the present application further provides an electronic device. Fig. 7 is a schematic structural diagram of an embodiment of an electronic device provided in a fifth aspect of the present application. As shown in fig. 7, the electronic device 700 comprises a memory 701, a processor 702 and a computer program stored on the memory 701 and executable on the processor 702.
In one example, the processor 702 may include a Central Processing Unit (CPU), or an Application Specific Integrated Circuit (ASIC), or may be configured to implement one or more Integrated circuits of embodiments of the present Application.
Memory 701 may include Read-Only Memory (ROM), random Access Memory (RAM), magnetic disk storage media devices, optical storage media devices, flash Memory devices, electrical, optical, or other physical/tangible Memory storage devices. Thus, in general, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., a memory device) encoded with software comprising computer-executable instructions and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the payment invoicing method according to embodiments of the first, second or third aspects of the application.
The processor 702 runs a computer program corresponding to the executable program code by reading the executable program code stored in the memory 701, for implementing the payment billing method in the embodiment of the first aspect or the second aspect described above.
In some examples, electronic device 700 may also include a communication interface 703 and a bus 704. As shown in fig. 7, the memory 701, the processor 702, and the communication interface 703 are connected via a bus 704 to complete communication therebetween.
The communication interface 703 is mainly used for implementing communication between modules, apparatuses, units and/or devices in this embodiment of the application. Input devices and/or output devices may also be accessed through communications interface 703.
The bus 704 includes hardware, software, or both to couple the components of the electronic device 700 to one another. By way of example and not limitation, bus 704 may include an Accelerated Graphics Port (AGP) or other Graphics Bus, an Enhanced Industry Standard Architecture (EISA) Bus, a Front-Side Bus (Front Side Bus, FSB), a Hyper Transport (HT) Interconnect, an Industry Standard Architecture (ISA) Bus, an infiniband Interconnect, a Low Pin Count (LPC) Bus, a memory Bus, a microchannel Architecture (MCA) Bus, a Peripheral Component Interconnect (PCI) Bus, a PCI-Express (PCI-E) Bus, a Serial Advanced Technology Attachment (attached) Bus, an attached Local Electronics Standard Association (vlo) Bus, a Local Electronics Standard Association (vlo) Bus, or a combination of two or more of these as appropriate. Bus 704 may include one or more buses, where appropriate. Although specific buses are described and shown in the embodiments of the present application, any suitable buses or interconnects are contemplated by the present application.
A sixth aspect of the present application provides a computer-readable storage medium, where a program or an instruction is stored on the computer-readable storage medium, and when the program or the instruction is executed by a processor, the payment billing method according to the first aspect or the second aspect may be implemented, and the same technical effect may be achieved, and in order to avoid repetition, details are not repeated here. The computer-readable storage medium may include a non-transitory computer-readable storage medium, such as a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and is not limited herein.
A seventh aspect of the present application provides a computer program product, where the computer program product is stored in a non-volatile storage medium, and when executed by at least one processor, the computer program product implements the steps of the payment billing method shown in the first aspect or the second aspect, and specific contents of the payment billing method may be referred to in the description of the foregoing embodiments, and are not described herein again.
An eighth aspect of the present application provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled with the processor, and the processor is configured to execute a program or an instruction, to implement the steps of the payment billing method shown in the first aspect or the second aspect, and can achieve the same technical effects, and in order to avoid repetition, details are not repeated here.
It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as system-on-chip, system-on-chip or system-on-chip, etc.
The present application may also provide a payment billing system, where the payment billing system may include the merchant system, the acquiring system, the payment platform, and the ticket management system in the foregoing embodiments, and specific contents may refer to relevant descriptions in the foregoing embodiments, and are not described herein again.
It should be clear that the embodiments in this specification are described in a progressive manner, and the same or similar parts between the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. For apparatus embodiments, user terminal embodiments, device embodiments, system embodiments, and computer-readable storage medium embodiments, reference may be made to the description of the method embodiments for relevant points. The present application is not limited to the particular steps and structures described above and shown in the drawings. Those skilled in the art may make various changes, modifications and additions or change the order between the steps after appreciating the spirit of the present application. Also, a detailed description of known process techniques is omitted herein for the sake of brevity.
Aspects of the present application are described above with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, implement the functions/acts specified in the flowchart and/or block diagram block or blocks. Such a processor may be, but is not limited to, a general purpose processor, a special purpose processor, an application specific processor, or a field programmable logic circuit. It will also be understood that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware for performing the specified functions or acts, or combinations of special purpose hardware and computer instructions.
It will be appreciated by persons skilled in the art that the above embodiments are illustrative and not restrictive. Different features which are present in different embodiments may be combined to advantage. Other variations to the disclosed embodiments can be understood and effected by those skilled in the art in practicing the claimed subject matter, from a study of the drawings, the disclosure, and the appended claims. In the claims, the term "comprising" does not exclude other means or steps; the word "a" or "an" does not exclude a plurality; the terms "first" and "second" are used to denote a name and not to denote any particular order. Any reference signs in the claims shall not be construed as limiting the scope. The functions of the various parts appearing in the claims may be implemented by a single hardware or software module. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage.
Claims (14)
1. A method of issuing an invoice, the method comprising:
acquiring billing information of a first order under the condition that payment of the first order is completed;
generating an invoicing request based on the invoicing information of the first order;
sending an invoicing request of the first order to a payment platform so that the payment platform verifies the invoicing request based on the payment transaction information of the first order;
and receiving an invoicing result of the first order sent by the payment platform under the condition that the invoicing request is matched with the payment transaction information, wherein the invoicing result is generated based on the invoicing request.
2. The method of claim 1, further comprising:
under the condition that the payment of the first order is completed, obtaining an order mark of the first order;
the sending the invoicing request of the first order to the payment platform comprises:
and sending an invoicing request and an order identification of the first order to the payment platform so that the payment platform acquires payment transaction information of the first order based on the order identification.
3. The method according to claim 1, wherein the invoicing request is matched with the payment transaction information in case the invoicing request and the payment transaction information satisfy a first matching condition and a second matching condition;
the first matching condition comprises that the invoicing request is consistent with an order mark, transaction details and a commodity type in the payment transaction information, and the invoicing state of an order corresponding to the order mark is a target state;
the second matching condition comprises that the invoicing amount in the invoicing request is less than or equal to the transaction amount in the payment transaction information.
4. The method according to claim 1, wherein the method is applied to a merchant system, and the obtaining of the billing information of the first order in case of the completion of the payment of the first order comprises:
and acquiring the invoicing information of the first order under the condition of receiving a payment result of the first order sent by the payment platform, wherein the payment result is used for representing that the payment of the first order is completed.
5. The method of claim 1, wherein the method is applied to an acquirer system,
the obtaining of the billing information of the first order under the condition that the payment of the first order is completed includes:
receiving the billing information of the first order sent by a merchant system under the condition that the payment of the first order is completed;
after the receiving the invoicing result of the first order sent by the payment platform, the method further comprises:
and forwarding the billing result of the first order to the merchant system.
6. A payment billing method is applied to a payment platform, and comprises the following steps:
under the condition that the payment of a first order is completed, receiving an invoicing request of the first order sent by a merchant system or an order receiving system;
acquiring payment transaction information of the first order;
verifying the invoicing request of the first order based on the payment transaction information;
under the condition that the invoicing request is matched with the payment transaction information, forwarding the invoicing request to a bill management system so that the bill management system performs invoicing based on the invoicing request to generate an invoicing result;
and sending the billing result to the merchant system or the acquiring system under the condition of receiving the billing result sent by the bill management system.
7. The method of claim 6,
the receiving an invoicing request of the first order sent by the merchant system or the order receiving system comprises:
receiving an invoicing request and an order identification of the first order sent by the merchant system or the order receiving system;
the obtaining of the payment transaction information of the first order includes:
and acquiring the payment transaction information of the first order based on the order identification.
8. The method of claim 6, wherein the verifying the request for the first order based on the payment transaction information comprises:
under the condition that the invoicing request and the payment transaction information meet a first matching condition and a second matching condition, determining that the invoicing request is matched with the payment transaction information, and the invoicing request passes verification;
the first matching condition comprises that the invoicing request is consistent with an order mark, transaction details and a commodity type in the payment transaction information, and the invoicing state of an order corresponding to the order mark is a target state;
the second matching condition comprises that the invoicing amount in the invoicing request is less than or equal to the transaction amount in the payment transaction information.
9. The method of claim 6, wherein the payment platform comprises an invoicing system, and wherein verifying the invoicing request for the first order based on the payment transaction information comprises:
and the invoicing system takes the tax number of the payee of the first order as an index and verifies whether the invoicing request is matched with the payment transaction information.
10. A payment billing apparatus comprising:
the acquisition module is used for acquiring the billing information of the first order under the condition that the payment of the first order is completed;
the generating module is used for generating an invoicing request based on the invoicing information of the first order;
the sending module is used for sending the invoicing request of the first order to a payment platform so that the payment platform verifies the invoicing request based on the payment transaction information of the first order;
the receiving module is used for receiving the invoicing result of the first order sent by the payment platform under the condition that the invoicing request is matched with the payment transaction information, and the invoicing result is generated based on the invoicing request.
11. A payment platform, comprising:
the receiving module is used for receiving an invoicing request of the first order sent by a merchant system or an order receiving system under the condition that the payment of the first order is completed;
the acquisition module is used for acquiring payment transaction information of the first order;
the checking module is used for checking the invoicing request of the first order based on the payment transaction information;
the forwarding module is used for forwarding the invoicing request to a bill management system under the condition that the invoicing request is matched with the payment transaction information, so that the bill management system performs invoicing based on the invoicing request to generate an invoicing result;
and the sending module is used for sending the invoicing result to the merchant system or the acquiring system under the condition of receiving the invoicing result sent by the bill management system.
12. An electronic device, characterized in that the device comprises: a processor and a memory storing computer program instructions;
the processor, when executing the computer program instructions, implements a method of making payment invoices according to any one of claims 1 to 9.
13. A computer-readable storage medium, on which a program or instructions are stored, which when executed by a processor, implements the payment invoicing method of any one of claims 1 to 8.
14. A computer program product, stored in a non-volatile storage medium, which when executed by at least one processor implements the method of payment invoicing of any one of claims 1 to 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211015077.7A CN115423543A (en) | 2022-08-23 | 2022-08-23 | Payment billing method, device, platform, equipment, medium and product |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211015077.7A CN115423543A (en) | 2022-08-23 | 2022-08-23 | Payment billing method, device, platform, equipment, medium and product |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115423543A true CN115423543A (en) | 2022-12-02 |
Family
ID=84197409
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211015077.7A Pending CN115423543A (en) | 2022-08-23 | 2022-08-23 | Payment billing method, device, platform, equipment, medium and product |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115423543A (en) |
-
2022
- 2022-08-23 CN CN202211015077.7A patent/CN115423543A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20190220865A1 (en) | Account type detection for fraud risk | |
| US20200286132A1 (en) | Second-hand vehicle transaction method and server | |
| US20190220856A1 (en) | Techniques for conducting transactions utilizing cryptocurrency | |
| US11087371B2 (en) | Blockchain-based invoice creation method apparatus, and electronic device | |
| US20230106544A1 (en) | Data integrity resolution systems and methods | |
| CN112184240A (en) | Refund request processing method and device | |
| US11348100B2 (en) | Foreign currency transaction system and method | |
| CN109582550A (en) | A kind of method, apparatus and server obtaining full dose business scenario failure collection | |
| CN109978542B (en) | Accounts payable data management method, system, storage medium and electronic device | |
| CN111325533A (en) | Decentralized transaction method, decentralized transaction system and computer equipment | |
| CN113222570B (en) | Payment method, platform device, system and storage medium | |
| WO2021120760A1 (en) | Method and device for issuing electronic invoice employing blockchain | |
| CN112330448A (en) | Fund management method, terminal device and storage medium | |
| CN115423543A (en) | Payment billing method, device, platform, equipment, medium and product | |
| CN116205641A (en) | Payment method, device, equipment, medium and product | |
| CN115689570A (en) | Business information risk identification method, device, equipment and medium | |
| CN111210345A (en) | Signature method and device based on block chain network transaction and terminal equipment | |
| CN114661740A (en) | Data processing method, device, equipment, computer storage medium and program product | |
| CN113988844A (en) | Service subscription method, device and system | |
| CN108961039B (en) | Transaction processing method, device and system | |
| CN117437076B (en) | Account checking method, device, equipment and medium based on account checking code | |
| CN111178850B (en) | Transaction method, device and system | |
| CN114997939A (en) | Information processing method, information processing apparatus, electronic device, information processing medium, and program product | |
| CN116010682A (en) | Data query method and device, equipment, medium and product thereof | |
| CN118195621A (en) | Method, device, equipment and storage medium for improving payment amount |
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 |