Data processing method, related device and system

Abstract

The present invention provides a data processing method, device and system. In the commodity payment method provided by the present invention, when the payment server makes payment according to the payment amount and the payment voucher of the payee, it has already obtained the merchant information and commodity information of the commodity to be paid, and after the payment is successful, a corresponding relationship between the service verification code and the merchant information and commodity information is established. Therefore, after the payment server sends the service verification code to the terminal corresponding to the payee, the user can verify the payment system according to the service verification code. Furthermore, when users who purchase commodities on different sales platforms and pay through the same payment system request commodities or services from merchants, the merchant only needs to verify the service verification code provided by the user in the payment system, and does not need to verify with different sales platforms, which improves the verification efficiency and reduces the transaction cost.

Description

Technical Field

[0001] This invention relates to the field of mobile communication technology, and more specifically to a data processing method, related apparatus, and system. Background Art

[0002] Mobile payment, also known as mobile phone payment, allows users to pay for goods or services using their mobile devices. Platforms or systems that provide mobile payment services are called mobile payment systems. Examples include PayPal (eBay), Alipay (Alibaba), and M-pesa (Vodafone).

[0003] With the prevalence of mobile payments, more and more users are purchasing goods or services from service providers (or commercial providers), such as bus tickets and movie tickets, through websites provided by sales platforms (such as Groupon and Amazon) or self-service terminals. After the user completes payment through a mobile terminal, the sales platform sends a service verification code (also known as an electronic ticket) to the mobile terminal via a short message. The user then requests the goods or services from the service provider (such as a train station or a movie theater) based on the service verification code.

[0004] Users can obtain paper tickets (train or movie tickets) at self-service terminals provided by the sales platform using the service verification code, and then use the ticket to access services. Alternatively, users can directly present the service verification code to the service provider, who will then verify the code with the sales platform and provide services based on the verification result.

[0005] However, service providers usually list goods or services on multiple different sales platforms to increase revenue, which will result in multiple sales platforms needing to provide self-service terminals at the service provider's location (such as Groupon group buying self-service terminals, Amazon group buying self-service terminals, etc.), or the service provider needing to verify the service verification codes provided by different sales platforms with different sales platforms, which increases transaction costs and has low verification efficiency. Summary of the Invention

[0006] This invention provides a method and apparatus for improving the efficiency of mobile payments.

[0007] In one aspect, embodiments of the present invention provide a data processing method applied to a payment server, comprising:

[0008] The payment server obtains the product information, merchant information, payment voucher, and payment amount data of the goods to be paid, and then makes the payment based on the payment voucher, merchant information, and payment amount data. After successful payment, a service verification code is generated to verify the goods, and a correspondence is established between the service verification code and the merchant information and product information. After the correspondence is established, a first notification message is sent to the terminal corresponding to the payer, and the first notification message carries the service verification code.

[0009] In this embodiment of the invention, since the payment server has already obtained the merchant information and product information of the goods to be paid for when processing the payment based on the payment amount and the payer's payment voucher, and has established a correspondence between the service verification code and the merchant information and product information after successful payment, the user can verify the service verification code in the payment system after the payment server sends the service verification code to the payer's corresponding terminal. Therefore, when users who purchase goods on different sales platforms and pay through the same payment system request goods or services from merchants, the merchants only need to verify the service verification code provided by the user in the payment system, without needing to verify it on different sales platforms, thus improving verification efficiency and reducing transaction costs.

[0010] In one possible design, the payment server may obtain the product information, merchant information, and payment amount data of the product to be paid in the following ways:

[0011] The payment server receives a first payment request sent by the terminal corresponding to the payer. The first payment request carries the payer's payment voucher and merchant information. That is, the payment server obtains the aforementioned merchant information and the payer's payment voucher based on the first payment request.

[0012] The payment server receives a second payment request sent by the platform server. The second payment request carries product information, merchant information, and payment amount data of the goods to be paid. That is, the payment server obtains the above-mentioned product information, merchant information, and payment amount data according to the second payment request.

[0013] Furthermore, if the first payment request includes product information, merchant information, user payment voucher, and payment amount data for the selected goods, the payment server only needs to obtain the above information based on the first payment request.

[0014] In one possible design, if the second payment request received by the payment server also carries a merchant credential, the payment server will further verify whether the merchant credential carried in the second payment request is consistent with the merchant credential stored locally.

[0015] If they are consistent, the payment process is triggered based on the payer's payment voucher, merchant information, and payment amount data. If they are inconsistent, the data processing process is stopped.

[0016] This design can prevent illegal merchants from stealing payment information by verifying the merchant's merchant credentials, thereby enhancing the security of data processing.

[0017] In one possible design, when a user makes a purchase at a merchant using a verification code and merchant information, the payment server also receives a verification request from the merchant's verification terminal. This verification request carries the merchant information and the service verification code entered by the user. The payment server then searches a previously stored correspondence for the product information that corresponds to the merchant information and service verification code carried in the verification request and returns it to the verification terminal. The merchant then provides the user with goods or services based on the information returned by the payment server. If the payment server cannot find the corresponding product information, the merchant does not provide the user with the product or service.

[0018] In one possible design, if the payer user also wants other terminals to receive the service verification code, the payment server can also obtain the identifier of the terminal that receives the service verification code, and then send a second notification message to the terminal that receives the service verification code. The second notification message carries the service verification code, product information and merchant information, and then terminals other than the payer can also go to the merchant to consume based on the received service verification code, thereby improving consumption flexibility.

[0019] In one possible design, in order to further improve the security of data processing, after obtaining the identification of the terminal that receives the service verification code, the payment server also establishes a correspondence between the generated service verification code and the identification of the terminal that receives the service verification code. Then, during subsequent consumption, the correspondence between the terminal and the service verification code is verified to prevent others from impersonating the service verification code, thereby improving the security of mobile payments.

[0020] In one possible design, the first payment request sent by the platform server and received by the payment server also carries an order number used to identify the transaction event. After that, after the payment is successful, the payment server sends a third notification message to the platform server, and the third notification message carries the order number. The platform server then associates the product information, merchant information and payer user information according to the order number, which facilitates subsequent data maintenance, such as query, payment, settlement, etc.

[0021] On the other hand, an embodiment of the present invention provides a payment server having the function of implementing the data processing method of the first aspect described above. These functions can be implemented through hardware modules or by hardware executing software.

[0022] In one possible design, the payment server includes: a first acquisition module, used to acquire product information, merchant information, payment voucher of the payer, and payment amount data of the goods to be paid; a data processing module, used to make payment based on the payment voucher, merchant information, and payment amount data acquired by the first acquisition module; an association module, used to generate a service verification code for verifying the goods after successful payment, and to establish a correspondence between the service verification code and the merchant information and product information; and a first sending module, used to send a first notification message to the terminal corresponding to the payer, the first notification message carrying the service verification code.

[0023] In one possible design, the payment server further includes: a first receiving module for receiving a verification request sent by a verification terminal, the verification request carrying merchant information and a service verification code entered by the user; and a lookup module for searching for product information corresponding to the merchant information and service verification code carried in the verification request within the correspondence established by the association module, and returning it to the verification terminal, so that the merchant can provide goods or services to the user based on the information returned by the payment server. If the payment server does not find the corresponding product information, the merchant will not provide goods or services to the user.

[0024] In one possible design, the first acquisition module in the payment server is also used to acquire the identifier of the terminal receiving the service verification code; the first sending module is also used to send a second notification message to the terminal receiving the service verification code. The second notification message carries the service verification code, product information and merchant information, so that terminals other than the payer can also make purchases at merchants based on the received service verification code, thereby improving the flexibility of consumption.

[0025] In one possible design, the first acquisition module of the payment server acquiring the product information, merchant information, and payment amount data of the goods to be paid for may include: the first acquisition module receiving a first payment request sent by the terminal corresponding to the payer, the first payment request carrying the payer's payment voucher and merchant information, that is, the first acquisition module acquiring the payer's payment voucher and merchant information based on the first payment request. The first acquisition module also receives a second payment request sent by the platform server, the second payment request carrying the product information, merchant information, and payment amount data of the goods to be paid for, that is, the first acquisition module acquiring the product information, merchant information, and payment amount data based on the second payment request.

[0026] In one possible design, the first payment request received by the payment server also carries an order number to identify the transaction event. The first sending module is also used to send a third notification message to the platform server after the payment is successful. The third notification message carries the order number, so that the platform server knows that the order has been successfully paid, which is convenient for the background to record.

[0027] In the embodiments provided in combination with the first aspect and the second aspect, the second notification message sent by the payment server may further carry product information and merchant information, thereby providing more information to the terminal receiving the service verification code.

[0028] In the embodiments provided in combination with the first aspect and the second aspect, the product information is the product name and the quantity of the product, the merchant information is the merchant name and address information, and the payer's payment voucher is the user name and password registered by the payer in the payment system. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for describing the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without inventive efforts. Among them:

[0030] Figure 1 1 is a network diagram of a data processing system provided in Example 1 of the present invention;

[0031] Figure 2 is a flow chart of a data processing method provided in Embodiment 2 of the present invention;

[0032] Figure 3 is a flow chart of a data processing method provided in Embodiment 3 of the present invention;

[0033] Figure 4 This is a schematic diagram of the structure of a payment server provided in Embodiment 4 of the present invention;

[0034] Figure 5 It is a structural diagram of the payment server provided in the fifth embodiment of the present invention. DETAILED DESCRIPTION

[0035] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of them. All other embodiments obtained by ordinary technicians in this field based on the embodiments of the present invention without making any creative efforts shall fall within the scope of protection of the present invention.

[0036] The present invention provides a data processing method, related devices and systems, see Figure 1 , Figure 1 This is a network diagram of the data processing system provided in Example 1 of the present invention.

[0037] like Figure 1As shown, the data processing system involved in the present invention can be applied to the payment scenario provided in the background technology. The system mainly includes a payment server 10, platform servers 21 and 22, a payment terminal 30, a verification terminal 50 and a merchant sales system 40.

[0038] Platform servers 21, 22, and payment terminal 30 are all registered with the same payment server 10. As the backend device of the payment system, payment server 10 primarily processes payment-related data submitted by platform servers 21, 22 or payment terminal 30 and performs account management. Both platform servers 21, 22 and payment server 10 can be constructed using general-purpose servers, including components such as a processor, memory, hard disk, and bus.

[0039] Platform servers 21 and 22 serve as the backend for the sales platform. The webpages they provide display merchandise for sale. Users can access these webpages by operating a payment terminal 30. Furthermore, both platform servers 21 and 22 are connected to the merchant sales system 40, from which they obtain information such as product inventory. Merchant products can be sold independently on both platform servers 21 and 22. For example, Cinema A lists movie tickets on both Groupon and Amazon. The platform servers on both Groupon and Amazon are connected to the cinema's ticketing system. After a user successfully pays for a product, platform servers 21 and 22 notify the merchant sales system 40 that the product has been sold.

[0040] The payment terminal 30 can be a mobile terminal with an application (APP) installed. Users can use the APP on the mobile terminal to view the products sold on the platform servers 21 and 22. The mobile terminal can be installed with a shopping application corresponding to the platform servers 21 and 22, which can also be called a shopping client, such as an Amazon client. The mobile terminal also has a payment application corresponding to the payment server 10 installed (which can be called a payment client, such as a PayPal client that uses the technical solution of the present invention). The payment application and shopping application can be deployed on the subscriber identification module (SIM) card of the mobile terminal or on an intelligent operating system (such as Android or iOS systems).

[0041] The payment terminal 30 may also be an ordinary personal computer (PC). The user may use a browser in the PC to log in to the web page provided by the platform servers 21 and 22 to view the commodities sold on the platform servers 21 and 22 .

[0042] The verification terminal 50 is connected to the payment server 10 and is used to verify the service verification code provided by the user. The service verification code is used to verify that the product requested by the user when making a purchase at the merchant is consistent with the product purchased by the user on the platform server 21 or 22. The verification terminal 50 can be a self-service terminal. Upon successful verification, the self-service terminal prints out paper tickets such as train or movie tickets, or can also deliver the product. The verification terminal 50 can also be a mobile terminal equipped with verification functionality, with an application corresponding to the payment server 10 installed on the mobile terminal, which provides the verification functionality.

[0043] In the data processing system provided by an embodiment of the present invention, multiple users access shopping platforms provided by different platform servers 21 and 22 and purchase goods from the same merchant. These different users all select the same payment system to make their payment. After successful payment, the payment server saves the product information and the corresponding merchant information. When these users subsequently purchase goods at the same merchant, the merchant only needs to verify the purchased goods information with the payment system, without having to verify them separately with different shopping platforms. This improves verification efficiency and reduces transaction costs.

[0044] For a more detailed understanding of the embodiments of the present invention, a detailed method flow is given below to illustrate the present invention. Figure 2 , Figure 2 This is a flowchart of a data processing method according to a second embodiment of the present invention using the data processing system provided in the first embodiment, for example.

[0045] In the embodiment of the present invention, the user views the commodities sold on the platform server 21 through the mobile terminal 30, and after determining the commodities to be purchased, the user selects a payment system to make payment. Figure 1 The payment server 10 shown begins by executing the following steps:

[0046] Step 201: The payment server obtains product information, merchant information, the payer's payment voucher, and payment amount data of the product to be paid.

[0047] Among them, the payment terminal used by the user (payer) can send a first payment request to the payment server corresponding to the payment system. The first payment request carries the product information of the product selected by the user (such as movie tickets), merchant information, user's payment voucher and payment amount data, etc.

[0048] Specifically, the product information may include the product name and quantity, and the merchant information may include the merchant's name and address. The payer's payment credentials may be a username or username and password registered by the payer in the payment server. The payer may register in the payment system before requesting payment, and the registered username and password may be stored on the payment server.

[0049] Furthermore, if a user accesses a webpage provided by the platform server via a PC, selects a suitable product, and chooses to pay, the payment server will receive two payment requests, one from the PC and the other from the platform server. The first payment request sent by the PC may carry the payer's payment voucher and the merchant information, as well as product information and payment amount data. The second payment request sent by the platform server carries product information, merchant information, and payment amount data for the product to be paid for. The payment server combines the information from the first and second payment requests to execute the subsequent payment process. Optionally, the second payment request may also carry the merchant's voucher in the payment system (referred to as the merchant voucher). The payment server verifies whether the merchant voucher is consistent with the locally stored merchant voucher, that is, whether the merchant is registered in the payment system. If they are consistent, the subsequent step 202 is executed. If they are inconsistent, it indicates that the merchant is not registered in the payment system, that is, the merchant is illegal, and the data processing process is stopped. This embodiment can further improve the security of data processing by verifying the merchant voucher.

[0050] Specifically, if a user accesses a webpage provided by the platform server via a PC, selects a suitable product, and chooses to pay, the platform server will request the payment server to return a voucher input page. The platform server displays this voucher input page, where the paying user can enter their payment voucher (such as username and password). The PC then sends this payment voucher to the payment server for processing via the first payment request mentioned above.

[0051] Step 202: The payment server makes payment based on the payer's payment voucher, merchant information, and payment amount data.

[0052] Specifically, the payment server can verify whether the payer's payment credentials match those previously stored. For example, it can verify whether the username and password carried in the first payment request match those previously stored on the payment server. If they match, the verification is considered successful; otherwise, the verification fails.

[0053] After the payment voucher is verified, the payment server makes the payment based on the payment amount data, the payment voucher, and the merchant information. For example, the payment amount is transferred from the account corresponding to the username to the account corresponding to the merchant information.

[0054] Step 203: The payment server generates a service verification code for verifying the product, and establishes a corresponding relationship between the service verification code and the merchant information and product information.

[0055] Specifically, the payment server processes the payment based on the payment amount data, such as deducting funds from the account corresponding to the user's payment voucher. If the deduction is successful, a service verification code is generated. This service verification code can be a string of code. It is used to verify the goods purchased by the user. More precisely, the service verification code verifies whether the goods requested by the user for subsequent purchases at the merchant match the goods the user has currently paid for.

[0056] If the deduction fails, the payment process fails, and the payment server returns a payment failure response to the user (payment terminal).

[0057] Establishing a correspondence between the generated service verification code and merchant and product information can be understood as associating the service verification code with merchant and product information.

[0058] Step 204: The payment server sends a first notification message to the terminal corresponding to the payer, where the first notification message carries the service verification code.

[0059] Specifically, the payment server can send a first notification message to the terminal that the payer has pre-registered with the payment server (the default terminal to receive messages), and it can also send the first notification message to the mobile terminal that sent the first payment request (i.e., the terminal corresponding to the payer, referred to as the payment terminal). The first notification message can be sent via SMS or push notification from the payment app, and it carries a generated service verification code. After obtaining this service verification code, the user can use it to request verification from the payment system at the merchant's location and obtain the goods or services offered by the merchant based on the verification result.

[0060] In this embodiment of the invention, since the payment server has already obtained the merchant information and product information of the goods to be paid for when processing the payment based on the payment amount and the payer's payment voucher, and has established a correspondence between the service verification code and the merchant information and product information after successful payment, the user can verify the service verification code in the payment system after the payment server sends the service verification code to the payer's corresponding terminal. Therefore, when users who purchase goods on different sales platforms and pay through the same payment system request goods or services from merchants, the merchants only need to verify the service verification code provided by the user in the same payment system, without needing to verify it on different sales platforms, thus improving verification efficiency and reducing transaction costs.

[0061] In addition, in this embodiment, the payment server generates a service verification code after successful payment and sends it to the terminal corresponding to the payer. The sales platform does not need to generate a service verification code or send a service verification code to the terminal, which can reduce the cost of the sales platform and the cost of the seller.

[0062] In this embodiment, if a user purchases movie tickets for someone else, such as a friend, through a mobile terminal, the service verification code provided by the payment system can be sent to a terminal other than the payment terminal. Specifically, the payment server can also perform the following steps:

[0063] Step 205: The payment server obtains the identifier of the terminal that receives the service verification code.

[0064] Specifically, when the user determines the product they wish to purchase, they send a first payment request, including the identifier of the terminal that received the service verification code, to the payment server via their mobile terminal. The payment server then obtains the identifier of the terminal that received the service verification code based on the first payment request. After obtaining the identifier, the payment server can associate it with the service verification code and proceed to step 206.

[0065] In addition, the second payment request sent by the platform server may carry the identifier of the terminal receiving the service verification code. This identifier is sent by the user to the platform server via the mobile terminal when the user determines the goods to be purchased, and the platform server then sends the identifier to the payment server. The terminal identifier can be a Mobile Station International Service Digital Network (MSISDN) number.

[0066] Step 206: The payment server sends a second notification message to the terminal that receives the service verification code. The second notification message carries the service verification code, product information, and merchant information.

[0067] After the payment server sends the service verification code to the terminal, other users can request the corresponding goods or services from the merchant based on the service verification code. If the terminal that receives the service verification code is the same as the terminal corresponding to the payer, the first notification message and the second notification message are the same message.

[0068] If the user requests the corresponding product or service from the merchant according to the service verification code, the payment server will execute steps 207-208.

[0069] Step 207: The payment server receives the verification request, which carries the merchant information and the service verification code entered by the user.

[0070] Specifically, the payment server may receive a verification request from a verification terminal. This verification request may include merchant information and a service verification code. Furthermore, the verification request may include the identifier of the terminal providing the service verification code. This verification request may be triggered by the user entering the service verification code, or by the merchant based on the user-provided service verification code and terminal identifier.

[0071] Step 208: The payment server searches for and displays the product information corresponding to the merchant information and service verification code carried in the verification request within the corresponding relationship.

[0072] The payment server determines that the verification is successful if the merchant information and service verification code carried in the verification request correspond one-to-one with the merchant information and service verification code in the corresponding relationship, and returns the product information to the verification terminal for the merchant to confirm.

[0073] Furthermore, if the verification request carries not only merchant information and the service verification code entered by the user, but also product information of the selected product and the identifier of the terminal providing the service verification code, then step 208 can specifically be as follows: The payment server first verifies whether the identifier of the terminal carried in the request is consistent with the identifier obtained in step 205. If they are consistent, the subsequent verification continues; if they are inconsistent, the verification fails, indicating that another user has illegally used the service verification code. The payment server verifies whether the merchant information, service verification code, and product information carried in the verification request correspond one-to-one with the merchant information, service verification code, and product information in the previously established correspondence. If they correspond one-to-one, the verification succeeds; otherwise, the verification fails. For example, if the merchant information for one item does not correspond, the verification fails.

[0074] See also Figure 3 , Figure 3 This is a flowchart of the data processing method provided in Embodiment 3 of the present invention.

[0075] In this embodiment, users can purchase movie tickets through different shopping platforms. In this embodiment, a user purchases two movie tickets for 50 yuan each through the Groupon app on a mobile terminal. The user submits the order, and the data processing method provided in this embodiment includes the following steps:

[0076] Step 301: The mobile terminal submits the order to the platform server of the group buying application.

[0077] Specifically, after a user selects movie tickets on the Groupon app, they submit an order request to the Groupon app's platform server. The order request includes information such as the selected product, merchant information, and order amount, for example, the following information:

[0078] Cinema: MGM Grand Cinema

[0079] Movie Title: The Martian

[0080] Seating: Row 7, Hall 8

[0081] Session: 2016-03-28 22:00

[0082] Ticket price: 50.00 yuan

[0083] Step 302: The platform server returns order confirmation information.

[0084] The platform server receives the order request submitted by the user, confirms the product information selected by the user (for example, confirms with the merchant sales system whether the movie ticket selected by the user is available for purchase), and after confirming that the purchase is available, generates an order, which includes an order number. The platform server returns the order number to the mobile terminal.

[0085] The Groupon application on the mobile terminal also calls a payment application installed on the mobile terminal (e.g., a PayPal application using the solution of the present invention). The Groupon application sends the order number, product information, merchant information, and payment amount data to the payment application. The payment application then displays a payment interface to the user, which may include the order number, product information, merchant information, payment amount data, etc.

[0086] Step 303: The mobile terminal sends the first payment request to the payment server.

[0087] In this scenario, the user makes a payment through the payment application's interface. The mobile terminal sends a first payment request to the payment application's backend server (payment server). This payment request includes the order number, product information, merchant information, payment amount data, and the user's payment voucher. The user can either enter the payment voucher on the payment interface or have it automatically retrieved by the PayPal application. In this embodiment, the payment voucher is the user's registered username and password in the payment system. The user has already logged into the PayPal application, which automatically retrieves the payment voucher.

[0088] In this embodiment, the user wishes to receive a service verification code for verifying the product through the mobile terminal currently used, so the first payment request also carries the identifier of the mobile terminal, such as the MSISDN number 13621524568 or the International Mobile Equipment Identity (IMEI) of the terminal.

[0089] Step 304: The payment server obtains product information, merchant information, user payment vouchers, and payment amount data.

[0090] The payment server obtains the above-mentioned product information, merchant information, user's payment voucher and payment amount data by parsing the first payment request. In addition, the payment server can also obtain the order number and the identification of the mobile terminal.

[0091] In this embodiment, the user's payment credentials are the user's username and password in the payment system.

[0092] Step 305: The payment server makes payment based on the user's payment credentials, merchant information, and payment amount data.

[0093] Specifically, the payment server first verifies whether the username and password match those stored on the server. If they match, it transfers funds from the account corresponding to the username to the merchant's account based on the payment amount. If the transfer is successful, step 306 is executed; otherwise, the user is prompted that the payment has failed. It should be noted that the payment server can also transfer funds from the account corresponding to the username to an intermediary account based on the payment amount, simultaneously associating this transfer with the merchant's account. Once the user confirms their purchase at the merchant, the funds are then transferred from the intermediary account to the associated merchant's account, thereby enhancing transaction security.

[0094] If the username and password in the first payment request are inconsistent with the username and password stored in the payment system, the transfer fails and the user is prompted that the payment failed.

[0095] Step 306: The payment server generates a service verification code for verifying the product, and establishes a correspondence between the service verification code and the merchant information, product information, and terminal identification.

[0096] Specifically, after the transfer is successful, the payment server generates a service verification code, such as 65954123, for verifying the above-mentioned movie ticket.

[0097] The corresponding relationship established by the payment server is as follows:

[0098] Service verification code Product Information Merchant Information Terminal Identification 65954123 Movie Tickets - The Martian MGM International Cinema 13621524568

[0099] Step 307: The payment server sends a third notification message to the platform server, where the third notification message carries the order number.

[0100] Specifically, after the payment is completed, the payment server sends a third notification message to the PayPal payment platform server. This third notification message carries the order number of the completed order, so that the platform server is informed that the order has been paid for. The platform server can then associate the movie ticket and the theater selected by the user based on the order number.

[0101] Step 308: The payment server sends a first notification message to the mobile terminal, where the first notification message carries the service verification code, product information, and merchant information.

[0102] Specifically, the payment server can send a service verification code, product information, and merchant information to the mobile terminal via a PayPal app push notification. The notification message pushed by the PayPal app carries the service verification code 65954123, product information "Movie Tickets - The Martian," and merchant information "MGM Grand International Studios." The verification code can be displayed in the form of a QR code or barcode.

[0103] Users bring their mobile terminals to MGM Cinemas for consumption. Before watching a movie, they need to verify the service verification code with the verification terminal.

[0104] The verification terminal is a self-service terminal located at the cinema. It includes a display screen, keyboard, and barcode scanner. The user presents the verification code to the verification terminal using a mobile device and enters the terminal's identifier, 13621524568. After obtaining this information, the verification terminal sends a verification request to the payment server. This request also includes the merchant's information (automatically obtained by the verification terminal), which is MGM Cinemas.

[0105] Step 309: The payment server receives the verification request sent by the verification terminal. The verification request carries the merchant information, the terminal identifier, and the service verification code entered by the user.

[0106] Among them, an encrypted connection is used between the payment server and the verification terminal, and the verification request is transmitted to the payment server after being encrypted, thereby enhancing transaction security.

[0107] Step 310: The payment server searches for product information corresponding to the merchant information, terminal identifier, and service verification code carried in the verification request in a previously saved correspondence relationship according to the verification request.

[0108] Specifically, the payment server may first verify whether the formats (e.g., number of digits) of the service verification code and the terminal identifier are correct. If the formats are correct, it may further search the previously saved correspondence for product information corresponding to the merchant information, terminal identifier, and service verification code carried in the verification request.

[0109] Step 311: The payment server returns a verification response to the verification terminal, which carries product information.

[0110] If the corresponding product information is found, a verification response is returned to the verification terminal, which carries the product information, such as movie ticket information. In this embodiment, after finding the movie ticket, the payment server can also mark the movie ticket as having been consumed at the MGM Cinema, and the terminal identifier of the consumer user is 13621524568.

[0111] If the corresponding product information is not found, a verification response is returned to the verification terminal, and the response carries verification failure information.

[0112] Furthermore, if the format of the verification code and the terminal identifier in step 310 is incorrect, a verification response is returned, which carries information indicating that the verification failed.

[0113] After receiving the verification response, the verification terminal displays the verification failure message or product information (movie ticket information in this embodiment) to facilitate user confirmation. In this embodiment, the verification terminal can directly print out the movie ticket or prompt the user for entry, allowing the user to enter the theater directly with the ticket to watch the movie.

[0114] The above describes the data processing flow provided by this embodiment of the invention in detail, using a single user as an example. If multiple users purchase movie tickets for the same cinema through shopping platforms provided by different platform servers, the payment server and the corresponding platform server re-execute the above method flow. In this embodiment of the invention, since multiple users use the same payment system when purchasing goods, and the payment server establishes a correspondence between the service verification code and the merchant information and product information after successful payment, these users can all verify their purchases at the cinema using the same payment system based on the service verification code, without needing to verify with different sales platforms. This improves verification efficiency and reduces transaction costs.

[0115] Furthermore, in this embodiment of the invention, since users do not need to verify product information with different sales platforms, the sales platforms also do not need to deploy self-service terminals with verification functions at merchants, thus reducing the cost of the sales platforms.

[0116] See also Figure 4 , Figure 4 This is a schematic diagram of the payment server provided in Embodiment 4 of the present invention.

[0117] Wherein, the payment server can be Figure 1 The payment server 10 shown is equipped with general-purpose computer hardware, including a processor 101, a memory 102, a bus 103, an input device 104, an output device 105, and a network interface 106.

[0118] Specifically, memory 102 may include computer storage media in the form of volatile and / or non-volatile memory, such as read-only memory and / or random access memory. Memory 102 may store operating system, application programs, other program modules, executable code, and program data.

[0119] Input device 104 can be used to input commands and information to the payment server. Input device 104 may be a keyboard or pointing device such as a mouse, trackball, touchpad, microphone, joystick, gamepad, satellite TV antenna, scanner, or similar device. These input devices can be connected to processor 101 via bus 103.

[0120] Output device 105 can be used to output information to the payment server. In addition to the monitor, output device 105 can also be used for other peripheral output devices, such as speakers and / or printing devices. These output devices can also be connected to processor 101 via bus 103.

[0121] The payment server can be connected to a network via network interface 106, such as a local area network (LAN). In a networked environment, the computer execution instructions stored in the payment server can be stored on a remote storage device, not just locally.

[0122] When the processor 101 in the payment server executes the executable code or application stored in the memory 102, the payment server can execute the method steps on the payment server side in Embodiments 2 and 3 above, such as executing steps 201-208, 304-307, 310-311, etc., which have the same beneficial effects. For the specific execution process, please refer to Embodiments 2 and 3 above, which will not be repeated here.

[0123] See also Figure 5 , Figure 5 It is a structural diagram of the payment server provided in the fifth embodiment of the present invention.

[0124] As shown in the figure, the payment server provided by the embodiment of the present invention includes:

[0125] The first acquisition module 510 is used to acquire product information, merchant information, payment voucher of the payer, and payment amount data of the goods to be paid. Specifically, the first acquisition module 510 can be used to execute steps 201, 205, and 304 in the above embodiments. For the specific execution process, please refer to the description of the above method embodiments.

[0126] The data processing module 520 is used to make payments based on the payer's payment voucher, merchant information, and payment amount data. Specifically, the data processing module 520 can be used to execute steps 202 and 305 in the above embodiments, and the specific execution process is described in the above method embodiments.

[0127] The association module 530 is used to generate a service verification code for verifying the product and establish a correspondence between the service verification code and the merchant information and product information. Specifically, the association module 530 can be used to execute steps 203 and 306 in the above embodiments, and the specific execution process is described in the above method embodiments.

[0128] The first sending module 540 is used to send a first notification message to the terminal corresponding to the payer, the first notification message carrying the service verification code. Specifically, the first sending module 540 can be used to execute steps 204, 206, 307 and 308 in the above embodiments, and the specific execution process is described in the above method embodiments.

[0129] The payment server provided in this embodiment of the present invention can be used in the aforementioned method embodiments 2 and 3. It implements the method steps on the payment server side of the second and third embodiments through the cooperation between the aforementioned first acquisition module 510, data processing module 520, association module 530, and first sending module 540. Compared to payment servers in the prior art, the payment server provided in this embodiment achieves the same beneficial effects as the aforementioned method embodiments when performing data processing.

[0130] Specifically, the first acquisition module 510 in the payment server acquires the product information, merchant information and payment amount data of the product to be paid, including:

[0131] receiving a first payment request sent by a terminal corresponding to the payer, wherein the first payment request carries the payment credential of the payer and the merchant information;

[0132] A second payment request sent by the platform server is received, wherein the second payment request carries product information, merchant information, and payment amount data of the product to be paid.

[0133] Further, Figure 5 The payment server further includes:

[0134] The first receiving module 550 is used to receive a verification request sent by the verification terminal. The verification request carries merchant information and a service verification code entered by the user. Specifically, the first receiving module 550 can be used to execute steps 207 and 309 in the above embodiments. For the specific execution process, please refer to the description of the above method embodiments.

[0135] The lookup module 560 is used to find the product information corresponding to the merchant information and service verification code carried in the verification request in the correspondence and return it to the verification terminal. Specifically, the lookup module 560 can be used to execute steps 208 and 310-311 in the above embodiments, and the specific execution process is described in the above method embodiments.

[0136] In the payment server provided in this embodiment, the first obtaining module 510 is further configured to obtain an identifier of a terminal that receives a service verification code;

[0137] The first sending module 540 is further configured to send a second notification message to the terminal that received the service verification code. The second notification message carries the service verification code, product information, and merchant information. Furthermore, the second notification message also carries the product information and merchant information, thereby facilitating the terminal that received the service verification code to purchase at the merchant based on the product information, thereby improving consumption flexibility and convenience.

[0138] In the payment server provided in this embodiment, the first payment request also carries an order number for identifying a transaction event (i.e., the transaction fact that the user purchases goods). The first sending module 540 is also used to send a third notification message to the platform server after the payment is successful. The third notification message carries the order number, so that the platform server is informed that the order has been paid successfully, which facilitates background recording.

[0139] In this embodiment, the payment server is presented in the form of a functional unit. The "unit" here can refer to an application-specific integrated circuit (ASIC), a circuit, a processor and memory that executes one or more software or firmware programs, an integrated logic circuit, and / or other devices that can provide the above functions. In a simple embodiment, those skilled in the art can imagine that the payment server can also adopt Figure 4 The functions implemented by the first acquisition module 510, the data processing module 520, the association module 530, the first sending module 540, the first receiving module 550 and the search module 560 can all be realized by Figure 4 For example, the first acquisition module 510 acquires the commodity information, merchant information, the payer's payment voucher and the payment amount data of the commodity to be paid by executing the code stored in the memory 102 by the processor 101.

[0140] The processor used to implement the payment server of the present invention can be a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the present disclosure. The processor can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and so on.

[0141] Those skilled in the art will appreciate that various aspects of the present invention, or various aspects of possible implementation, can be specifically embodied as a system, method, or computer program product. Therefore, various aspects of the present invention, or various aspects of possible implementation, can adopt the form of a complete hardware embodiment, a complete software embodiment (including firmware, resident software, etc.), or a combination of software and hardware embodiments, all collectively referred to herein as "circuit," "module," or "system." In addition, various aspects of the present invention, or various aspects of possible implementation, can adopt the form of a computer program product, which refers to a computer-readable program code stored in a computer-readable medium.

[0142] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any modifications or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be based on the scope of protection of the claims.

Claims

1. A data processing method, characterized in that: include: The payment server generates a service verification code, establishes a corresponding relationship between the service verification code and the merchant information and product information, and sends the service verification code to the user's mobile terminal; The merchant's verification terminal obtains the service verification code input by the user, and sends a verification request to the payment server, wherein the verification request includes the service verification code; The payment server receives the verification request sent by the verification terminal, and returns a verification response to the verification terminal based on the corresponding relationship and the verification request.

2. The data processing method according to claim 1, characterized in that: The verification response is used to enable the user to obtain or consume the goods or services corresponding to the product information provided by the merchant.

3. The data processing method according to claim 1, characterized in that: The verification request also includes the merchant information and / or the product information.

4. The data processing method according to claim 1, characterized in that: The payment server returns a verification response to the verification terminal based on the corresponding relationship and the verification request, including: The payment server marks that the commodity corresponding to the service verification code has been consumed.

5. The data processing method according to claim 1, characterized in that: Also includes: The verification terminal outputs the commodity or service corresponding to the commodity information, or prompts the user to consume the commodity or service corresponding to the commodity information.

6. The data processing method according to claim 1, characterized in that: Also includes: The mobile terminal receives the service verification code and displays the service verification code to the verification terminal.

7. The data processing method according to claim 6, characterized in that: The mobile terminal displays the service verification code to the verification terminal in the form of a barcode or a QR code.

8. The data processing method according to claim 1, characterized in that: Before generating the service verification code, the method further includes: The payment server obtains the commodity information, the merchant information, the payment voucher and the payment amount data of the payer; The payment server makes payment according to the payment voucher, the merchant information and the payment amount data.

9. The data processing method according to claim 8, characterized in that: The payment server obtains the commodity information, the merchant information, the payment voucher of the payer and the payment amount data, including: The payment server receives a first payment request sent by a terminal corresponding to the payer, where the first payment request includes a payment credential of the payer and the merchant information; The payment server receives a second payment request sent by the platform server, where the second payment request includes the product information, the merchant information and the payment amount data.

10. The data processing method according to any one of claims 1 to 9, characterized in that: The payment server returns a verification response to the verification terminal based on the corresponding relationship and the verification request, including: The payment server searches for commodity information corresponding to the service verification code based on the corresponding relationship.

11. The data processing method according to any one of claims 1 to 9, characterized in that: The service verification code is used to verify whether the product or service requested by the user from the merchant is consistent with the product or service corresponding to the product information.

12. The data processing method according to any one of claims 1 to 9, characterized in that: The payment server also sends the merchant information and / or the product information to the mobile terminal.

13. A data processing method, characterized in that: include: The payment server generates a service verification code and establishes a corresponding relationship between the service verification code and the merchant information and product information; The payment server sends the service verification code to the user's mobile terminal; The payment server receives a verification request sent by a verification terminal of the merchant, wherein the verification request includes the service verification code input by the user; The payment server returns a verification response to the verification terminal based on the corresponding relationship and the verification request.

14. The data processing method according to claim 13, characterized in that: The verification response is used to enable the user to obtain or consume the goods or services corresponding to the product information provided by the merchant.

15. The data processing method according to claim 13, characterized in that: The verification request also includes the merchant information and / or the product information.

16. The data processing method according to claim 13, characterized in that: The payment server returns a verification response to the verification terminal based on the corresponding relationship and the verification request, including: The payment server marks that the commodity corresponding to the service verification code has been consumed.

17. The data processing method according to claim 13, characterized in that: Before generating the service verification code, the method further includes: The payment server obtains the commodity information, the merchant information, the payment voucher and the payment amount data of the payer; The payment server makes payment according to the payment voucher, the merchant information and the payment amount data.

18. The data processing method according to claim 17, characterized in that: The payment server obtains the commodity information, the merchant information, the payment voucher of the payer and the payment amount data, including: The payment server receives a first payment request sent by a terminal corresponding to the payer, where the first payment request includes a payment credential of the payer and the merchant information; The payment server receives a second payment request sent by the platform server, where the second payment request includes the product information, the merchant information and the payment amount data.

19. A payment server, characterized in that: include: An association module, used to generate a service verification code and establish a corresponding relationship between the service verification code and merchant information and product information; A sending module, used for sending the service verification code to the user's mobile terminal; A receiving module, configured to receive a verification request sent by a verification terminal of a merchant, wherein the verification request includes the service verification code input by the user; A search module is used to return a verification response to the verification terminal based on the corresponding relationship and the verification request.

20. The payment server according to claim 19, characterized in that: The verification response is used to enable the user to obtain or consume the goods or services corresponding to the product information provided by the merchant.

21. The payment server according to claim 19, characterized in that: The verification request also includes the merchant information and / or the product information.

22. The payment server according to claim 19, characterized in that: The search module is also used to: The product corresponding to the service verification code is marked as consumed.

23. The payment server according to claim 19, characterized in that: Also includes: An acquisition module, used to acquire the commodity information, the merchant information, the payment voucher of the payer and the payment amount data; A data processing module is used to make payment according to the payment voucher, the merchant information and the payment amount data.

24. A data processing system, characterized in that It includes a payment server and a verification terminal, wherein: The payment server is used to: generate a service verification code, establish a corresponding relationship between the service verification code and merchant information and product information, and send the service verification code to the user's mobile terminal; The verification terminal is used to: obtain the service verification code input by the user, and send a verification request to the payment server, wherein the verification request includes the service verification code; The payment server is further configured to: receive the verification request sent by the verification terminal, and return a verification response to the verification terminal based on the corresponding relationship and the verification request.

25. The data processing system according to claim 24, characterized in that The verification response is used to enable the user to obtain or consume the goods or services corresponding to the product information provided by the merchant.

26. The data processing system according to claim 24, characterized in that The verification request also includes the merchant information and / or the product information.

27. The data processing system according to claim 24, characterized in that The payment server is also used to mark that the commodity corresponding to the service verification code has been consumed.

28. The data processing system according to claim 24, characterized in that The verification terminal is further used to output the commodity or service corresponding to the commodity information, or prompt the user to consume the commodity or service corresponding to the commodity information.

29. The data processing system according to claim 24, characterized in that Also included is the mobile terminal, which is used to receive the service verification code and display the service verification code to the verification terminal.

30. The system according to any one of claims 24 to 29, characterized in that: The payment server is also used for: Obtain the product information, the merchant information, the payer's payment voucher and payment amount data; The payment is made according to the payment voucher, the merchant information and the payment amount data.

Images