CN111932227A - Method for processing transaction data, mobile terminal and server of payment platform - Google Patents

Method for processing transaction data, mobile terminal and server of payment platform Download PDF

Info

Publication number
CN111932227A
CN111932227A CN202011029229.XA CN202011029229A CN111932227A CN 111932227 A CN111932227 A CN 111932227A CN 202011029229 A CN202011029229 A CN 202011029229A CN 111932227 A CN111932227 A CN 111932227A
Authority
CN
China
Prior art keywords
transaction
transaction data
target
mobile terminal
server
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
Application number
CN202011029229.XA
Other languages
Chinese (zh)
Inventor
冯晓蓉
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
AlipayCom Co ltd
Original Assignee
Alipay Hangzhou Information Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Alipay Hangzhou Information Technology Co Ltd filed Critical Alipay Hangzhou Information Technology Co Ltd
Priority to CN202011029229.XA priority Critical patent/CN111932227A/en
Publication of CN111932227A publication Critical patent/CN111932227A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/04—Payment circuits
    • G06Q20/06—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
    • G06Q20/065—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • G06Q20/108—Remote banking, e.g. home banking
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/20—Point-of-sale [POS] network systems
    • G06Q20/206—Point-of-sale [POS] network systems comprising security or operator identification provisions, e.g. password entry
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401—Transaction verification
    • G06Q20/4014—Identity check for transactions

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Finance (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Databases & Information Systems (AREA)
  • Computer Security & Cryptography (AREA)
  • General Engineering & Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Computing Systems (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

The specification provides a method for processing transaction data, a mobile terminal and a server of a payment platform. For a mobile terminal, the method for processing transaction data comprises the following steps: completing electronic payment to a payee of a target transaction through a payment platform, wherein transaction data of the target transaction is uploaded to a target block chain; receiving the transaction data downloaded by a server of the payment platform from the target blockchain; and displaying the transaction data. For a server, the method of processing transaction data includes: confirming that a payer logs in the payment platform; making an electronic payment to a payee for a target transaction, the target transaction being made between the payer and the payee; receiving a request from a mobile terminal of the payer to acquire the transaction data; sending a request for obtaining the transaction data to the target block chain; downloading the transaction data from the target blockchain; and sending the transaction data to the mobile terminal.

Description

Method for processing transaction data, mobile terminal and server of payment platform
Technical Field
The present disclosure relates to the field of internet technologies, and in particular, to a method for processing transaction data, a mobile terminal, and a server of a payment platform.
Background
After the consumer settles the purchase, the paper ticket provided by the merchant is generally received as a transaction certificate to facilitate the consumer to check the transaction details.
However, printing of paper tickets consumes paper, is not easy to keep, and does not facilitate statistics of relevant transaction data. With the development of internet technology, electronic bills gradually replace traditional paper receipts due to their advantages of convenience, environmental protection and uneasy loss.
However, for electronic tickets, further improvements are needed in the processing of transaction data.
Disclosure of Invention
One or more exemplary embodiments of the present description prevent loss and tampering by uploading transaction data to a blockchain, while a user can download transaction data for tracing through a mobile terminal at any time.
One aspect of the present specification provides a method of processing transaction data for a mobile terminal and comprising: completing electronic payment to a payee of a target transaction through a payment platform, wherein transaction data of the target transaction is uploaded to a target block chain; receiving the transaction data downloaded by a server of the payment platform from the target blockchain; and displaying the transaction data.
In one or more exemplary embodiments, the completing, by the payment platform, the electronic payment to the payee of the target transaction includes: and sending the data of the payment account and payment authorization data to transaction equipment so as to authorize the transaction equipment to receive transaction amount from the payment account through the payment platform.
In one or more exemplary embodiments, the completing, by the payment platform, the electronic payment to the payee of the target transaction includes: the electronic payment is completed by providing identity information to the transaction device.
In one or more exemplary embodiments, the transaction data is uploaded onto the target blockchain by the transaction device.
In one or more exemplary embodiments, the method further comprises: displaying a target interface, wherein the target interface comprises a request link of the transaction data; receiving a triggering instruction of a payer to the request link; and in response to the triggering instruction, sending a request instruction to the server to instruct the server to download the transaction data from the target blockchain.
In one or more exemplary embodiments, the request instruction includes a request to obtain the list of transaction data, and the method further includes: receiving the list from the server; and displaying the list.
In one or more exemplary embodiments, the method further comprises: displaying an operation control of at least one of the payee and the payment platform based on the transaction data.
In one or more exemplary embodiments, the transaction data includes at least one of bank account information of the payee, bank account information of a payer of the target transaction, and a taxpayer identification number of the payer.
Another aspect of the present specification provides a mobile terminal, comprising: at least one storage medium storing at least one set of instructions for processing transaction data; and at least one processor communicatively coupled to the at least one storage medium, wherein the at least one processor performs the method of any of the preceding embodiments when the at least one processor executes the at least one set of instructions.
Yet another aspect of the present specification provides a method of processing transaction data for a server of a payment platform and comprising: confirming that a payer logs in the payment platform; making an electronic payment to a payee for a target transaction, the target transaction being made between the payer and the payee; receiving a request from a mobile terminal of the payer to acquire the transaction data; sending a request for acquiring the transaction data to a target block chain; downloading the transaction data from the target blockchain; and sending the transaction data to the mobile terminal.
In one or more exemplary embodiments, the method further comprises: and acquiring at least one of an order number of the target transaction, bank account information of the payee and a taxpayer identification number of the payer from the payee, wherein the transaction data comprises the order number.
In one or more exemplary embodiments, the method further comprises: receiving a request from the mobile terminal to obtain the list of transaction data; and sending the list to the mobile terminal.
In one or more exemplary embodiments, the method further comprises: performing out-of-block monitoring on the target block chain; receiving an out-of-block notification from the target blockchain; sending a request for extracting block data to the target block chain; and receiving the block data from the target blockchain.
In one or more exemplary embodiments, the method further comprises: sending a request for extracting a payment order to an order receiving system of the payment platform; and receiving the payment order from the acquiring system.
In one or more exemplary embodiments, the method further comprises: pushing an operation control of at least one of the payee and the payment platform to the mobile terminal based on the transaction data.
Yet another aspect of the present description provides a server of a payment platform, comprising: at least one storage medium storing at least one set of instructions for processing transaction data; and at least one processor communicatively coupled to the at least one storage medium, wherein the at least one processor performs the method of any of the preceding embodiments when the at least one processor executes the at least one set of instructions.
Yet another aspect of the present specification provides a method of processing transaction data, comprising: the payer completes electronic payment to the payee of the target transaction through the transaction device via the payment platform; the transaction equipment uploads transaction data of the target transaction to a target block chain; the target block chain sends the transaction data to a server of the payment platform; the server sends the transaction data to a mobile terminal of the payer; and the mobile terminal displays the transaction data.
In one or more exemplary embodiments, the method further comprises: the mobile terminal displays a target interface, and the target interface comprises a request link of the transaction data; the mobile terminal receives a trigger instruction of the payer for the request link; and the mobile terminal responds to the trigger instruction and sends a request instruction to the server to instruct the server to download the transaction data from the target blockchain.
In one or more exemplary embodiments, the method further comprises: the mobile terminal displays an operation control of at least one of the payee and the payment platform based on the transaction data.
In the method for processing transaction data, the mobile terminal and the server of the payment platform provided in one or more embodiments of the present specification, the transaction data is uploaded to the blockchain to be stored in time, which not only prevents loss and tampering, but also enables other members in the blockchain to download the transaction data, and increases the operation reach of each party and improves the management and reconciliation capability of each party on the transaction data.
Additional features of the methods and systems disclosed in this specification will be set forth in part in the description which follows. The contents of the following figures and examples will be apparent to those of ordinary skill in the art in view of this description. The inventive aspects of this application can be fully explained by the practice or use of the methods, apparatus and combinations described in the detailed examples below.
Drawings
In order to more clearly illustrate the technical solutions in one or more embodiments of the present disclosure, the drawings used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present disclosure, and it is obvious for those skilled in the art that other drawings can be obtained based on these drawings without creative efforts.
FIG. 1 schematically shows a diagram of an application scenario for processing transaction data according to one or more exemplary embodiments of the present description;
FIG. 2 schematically shows a timing diagram for processing transaction data according to one or more exemplary embodiments of the present description;
FIG. 3 schematically depicts a flow diagram of a method of processing transaction data according to one or more exemplary embodiments of the present description;
FIG. 4 schematically illustrates a flow diagram of a method of processing transaction data for a mobile terminal according to one or more exemplary embodiments of the present description;
FIG. 5 schematically illustrates a schematic diagram of use of a mobile terminal according to one or more exemplary embodiments of the present description;
fig. 6 schematically illustrates a flow diagram of a method for processing transaction data for a server of a payment platform according to one or more exemplary embodiments of the present description.
Detailed Description
The following description is presented to enable any person skilled in the art to make and use the present description, and is provided in the context of a particular application and its requirements. Various local modifications to the disclosed embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the present disclosure. Thus, the present disclosure is not to be limited to the embodiments shown, but is to be accorded the widest scope consistent with the claims.
The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting. For example, as used herein, the singular forms "a", "an", "the" and "the" may include the plural forms as well, unless the context clearly indicates otherwise. The terms "comprises," "comprising," "includes," and/or "including," when used in this specification, are intended to specify the presence of stated integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
These and other features of the present disclosure, as well as the operation and function of the related elements of the structure, and the combination of parts and economies of manufacture, may be particularly improved upon in view of the following description. All of which form a part of the present disclosure, with reference to the accompanying drawings. It is to be expressly understood, however, that the drawings are for the purpose of illustration and description only and are not intended as a definition of the limits of the disclosure. It should also be understood that the drawings are not drawn to scale.
Furthermore, certain terminology has been used in this specification to describe embodiments of the disclosure. For example, "one embodiment," "an embodiment," and/or "some embodiments" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the present disclosure. Therefore, it is emphasized and should be appreciated that two or more references to "an embodiment" or "one embodiment" or "an alternative embodiment" in various portions of this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined as suitable in one or more embodiments of the disclosure.
After reading this detailed disclosure, those skilled in the art will appreciate that the foregoing detailed disclosure may be presented by way of example only, and may not be limiting. Those skilled in the art will appreciate that the present description is intended to cover various reasonable changes, adaptations, and modifications of the embodiments described herein, although not explicitly described herein. Such alterations, improvements, and modifications are intended to be suggested by this disclosure, and are within the spirit and scope of the exemplary embodiments of this disclosure.
It should be appreciated that in the foregoing description of embodiments of the disclosure, to facilitate an understanding of one feature, the description combines various features in a single embodiment, figure, or description thereof for the purpose of simplifying the disclosure. This is not to be taken as an admission that any of the features are required in combination, and it is fully possible for one skilled in the art to extract some of the features as separate embodiments when reading this specification. That is, embodiments in this specification may also be understood as an integration of a plurality of sub-embodiments. And each sub-embodiment described herein is equally applicable to less than all features of a single foregoing disclosed embodiment.
Fig. 1 schematically illustrates an application scenario for processing transaction data according to one or more exemplary embodiments of the present description.
As shown in fig. 1, the transaction data is processed with multiple parties involved. For example, the multiple parties include, but are not limited to: payer 10, mobile terminal 12, transaction device 20, payee 30, blockchain 40, server 50, ticketed enterprise 60, electronic invoice service platform 70. The transaction device 20, payee 30, server 50, ticketed enterprise 60, electronic invoice service platform 70 may be in communication with the blockchain 40. In some exemplary embodiments, the mobile terminal 12 may also communicate with the blockchain 40.
In a practical application scenario, a payer 10 (e.g., a consumer or user) may complete an electronic payment to a payee 30 (e.g., a merchant or service provider) of a transaction via a payment platform (not shown) through a transaction device 20. Transaction device 20 may upload transaction data for the transaction to blockchain 40. The server 50 may download the transaction data from the blockchain 40 and may send the transaction data to the mobile terminal 12 of the payer 10. The mobile terminal 12 may display the transaction data.
Electronic payment refers to the act of securely transmitting payment information between a consumer, a merchant and a financial institution to a bank or a corresponding processing institution via an information network by using secure electronic means to realize currency payment or fund transfer. Namely, the payment information of the novel payment means (including electronic cash, credit card, debit card, smart card and the like) is transmitted to the bank or a corresponding processing mechanism through network security to realize electronic payment.
The payment platform can be a service intermediary mechanism independent of a bank, a website and a third party of a merchant, and is used for providing an electronic payment system for guaranteeing benefits of two transaction parties under the supervision of the bank. The payment platform can be used for transmitting payment information of novel payment means (such as electronic cash, credit card, debit card and smart card) to a bank or a corresponding processing mechanism through network security to realize electronic payment. The payment platform may provide an electronic payment channel by way of web pages, applications, technical plug-ins, etc. for the payer 10 and payee 30 to make money transactions. The payment platform may be a mobile payment platform for enabling electronic payment between mobile electronic devices. The payment platform is accessible or usable by both the mobile terminal 12 and the transaction device 20.
The transaction device 20 may be provided by the paymate 30 to assist the payee 30 in completing an electronic transaction with the payer 10. In some exemplary embodiments, the transaction device 20 may also be a mobile terminal of the payee 30, which is installed with an application authorized by the payment platform. The transaction device 20 may be capable of using the electronic payment channel provided by the payment platform and capable of interacting with the payer 10 or the mobile terminal 12 to complete an electronic payment. The transaction device 20 may be provided with the ability to use an electronic payment channel provided by a payment platform. The transaction device 20 may be a POS machine, an internet of things (IOT) device, a self-service cash register, a self-service ordering machine, an electronic device installed with a payment platform application, and the like.
The transaction device 20 may comprise an identity verification means for verifying the identity of the payer 10 or the mobile terminal 12. The identity may be verified through identity information, which may be an identification number of the payer 10, biometric information of the payer 10, a preset password, a device ID of the mobile terminal 12, and the like. In some exemplary embodiments, the transaction device 20 may include a biometric information acquisition device for acquiring biometric information (e.g., facial pattern, voice print, iris pattern, fingerprint, gait) of the payer 10 to verify the identity of the payer 10. In some exemplary embodiments, the transaction device 20 may complete the authentication of the payer 10 by the server 50 by transmitting the biometric information to the server 50.
The transaction device 20 may generate a machine code (e.g., barcode, two-dimensional code) associated with the transaction that the payer 10 may scan for electronic payment via the mobile terminal 12. In some exemplary embodiments, the transaction device 20 may also complete the collection of funds by scanning a machine code presented by the mobile terminal 12.
The transaction device 20 may upload transaction data for the transaction to the payment platform server first, and then to the blockchain 40 by the payment platform server. In some exemplary embodiments, the transaction device 20 may also directly transmit the transaction data to the mobile terminal 12. In some exemplary embodiments, the payer 10 may send information of the payment account number and payment authorization data (e.g., identity information of the payer 10) to the transaction device 20 via the mobile terminal 12 to authorize the transaction device 20 to collect the transaction amount from the payment account number via the payment platform. The transaction amount may be the value of real money, or may be the value of virtual money or tokens, or the like.
The transaction device 20 may upload the transaction data to the server 50 first, and then upload the transaction data from the server 50 to the blockchain 40. In some exemplary embodiments, the transaction device 20 may upload the transaction data directly to the blockchain 40 without any intermediate links. In some exemplary embodiments, after the transaction device 20 uploads the transaction data to the blockchain 40, the blockchain 40 sends verification information (e.g., a hash value) to the transaction device 20. The transaction device 20 can determine whether the transaction data received by the blockchain 40 is tampered with through the verification information.
The transaction data may be a receipt, slip, invoice or other transaction credential. For example, the transaction data may include, but is not limited to: payment credentials for the transaction, a payment method for the transaction, a payment amount for the transaction, a payment time for the transaction, a payment location for the transaction, a name of a good involved in the transaction, a quantity of a good involved in the transaction, a transaction order number provided by a payee 30, payee account number information for a payee 30, a taxpayer identification number for a payee 30, an award obtained by a payee 30 from the paymate, payment account number information for a payer of the transaction, a taxpayer identification number for the payer, and an award obtained by the payer from the paymate.
The server 50 may be an IOT server of the payment platform or a server independent of the payment platform. The server 50 may confirm whether the payer 10 or the mobile terminal 12 is logged in the payment platform. After confirming that the payer 10 or the mobile terminal 12 conducts a transaction with the payee 30 through the payment platform, the server 50 may make an electronic payment to the payee 30 of the transaction, i.e., transfer funds in the payment account of the payer 10 to the collection account of the payee 30. After receiving a request from the payer 10 or the mobile terminal 12 to obtain the transaction data, the server 50 may send a request to obtain the transaction data to the blockchain 40. After downloading the transaction data from the blockchain 40, the server 50 may send the transaction data to the payer 10 or the mobile terminal 12.
The blockchain 40 is a shared database that can implement a comprehensive transfer of information throughout the network and can verify the accuracy of the information through a hierarchical structure of a loose network of nodes. The data or information stored in the block chain 40 has features of "unforgeable", "whole-course traceable", "publicly transparent", "collective maintenance", and the like. Blockchain 40 may be an IOT blockchain for the payment platform or a blockchain independent of the payment platform. The nature of the blockchain 40 itself dictates that the information for the transaction can be recorded for download by any party or third party to the transaction. For example, the payee 30 may generate invoice information from the transaction information and upload the invoice information to the blockchain 40 for download by other entities accessing the blockchain 40. For example, the ticketed enterprise may download the invoice information for querying and reimbursement. As another example, the payer 10 or the mobile terminal 12 may apply for electronic invoicing to an electronic invoice service platform, which may obtain the invoice information from the ticketed enterprise. After generating an electronic invoice based on the invoice information, the electronic invoice service platform may send the electronic invoice to the payer 10 or the mobile terminal 12 while uploading the electronic invoice to the blockchain 40 for download use by other entities accessing the blockchain 40.
Fig. 2 schematically illustrates a timing diagram in accordance with one or more exemplary embodiments of the present description. FIG. 3 schematically illustrates a flow diagram of a method of processing transaction information according to one or more exemplary embodiments of the present description.
As shown in fig. 3, the method 200 of processing transaction information may include at least one or more of step S202, step S204, step S206, step S208, step S210, step S212, step S214, step S216, step S218, step S220, step S222, step S224, step S226, step S228, and step 230.
Step S202: payer 10 logs on to the payment platform.
For example, the payer 10 may log into the payment platform via the transaction device 20. In some exemplary embodiments, payer 10 may also log into the payment platform via mobile terminal 12. In some exemplary embodiments, payer 10 may also log into the payment platform via server 50. In some exemplary embodiments, whether the payer 10 is logged in the payment platform may be confirmed by the server 50.
Step S204: the payer 10 completes an electronic payment to the payee 30 of the target transaction via the payment platform through the transaction device 20.
For example, the payer 10 may complete the identity information collection by face brushing before the transaction device 20, and then the transaction device 20 sends the identity information to the paymate, which completes the identity verification and transfer of funds from the payment account of the payer 10 to the collection account of the payee 30. In some exemplary embodiments, the payer 10 completes the identity information collection directly through the transaction device 20. In some exemplary embodiments, the payer 10 may also complete the collection of the identity information through the mobile terminal 12, and the collected identity information is sent to the transaction device 20 by the mobile terminal 12. In some exemplary embodiments, the server 50 may confirm whether the payer 10 is logged in the paymate, and make an electronic payment to the payee 30 of the target transaction after confirming that the payer 10 is logged in the paymate.
Step S206: transaction device 20 uploads transaction data for the target transaction onto blockchain 40.
For example, the transaction device 20 may upload the transaction data directly to the blockchain 40, or may first forward the transaction data to the payment platform (e.g., the server 50 of the payment platform), and the payment platform uploads the transaction data to the blockchain 40. Upon receiving the transaction data uploaded by the transaction device 20, the blockchain 40 may return verification information (e.g., a hash value) to the transaction device 20 for verification by the transaction device 20. In some exemplary embodiments, the transaction device 20 may also send the transaction data directly to the mobile terminal 12 for use by the mobile terminal 12.
Step S208: the server 50 performs out-of-block snooping on the block chain 40.
Blockchain 40 is a database that is updated in real time. In block chain 40, a new block may appear each time. For example, one or more transaction devices 20 associated with the blockchain 40 may have the potential to upload various transaction data at any time. Therefore, the server 50 needs to keep block snooping on the block chain 40 at any time, so that it can perform queries and data updates as soon as a new block is generated. For example, the server 50 may perform block snooping on the blockchain 40 by periodically sending query requests to the blockchain 40.
Step S210: the server 50 receives out-of-block notifications from the blockchain 40.
For example, blockchain 40 may provide feedback to server 50 when a new tile is generated, indicating that a new tile is generated in blockchain 40.
Step S212: the server 50 sends a request to the tile chain 40 to extract tile data.
For example, after receiving an out-of-block notification for blockchain 40, server 50 may send a request to blockchain 40 to pull the data content of the new block.
Step S214: the server 50 receives the block data from the blockchain 40.
For example, the blockchain 40 may send the data of the new chunk to the server 50 after receiving a request from the server 50 to pull the data content of the new chunk.
In some exemplary embodiments, the method 200 of processing transaction data may further include: the server 50 sends a request for extracting a payment order to the acquiring system of the payment platform; the server 50 receiving the payment order from the acquiring system; and the server 50 supplements the payment information based on the payment order.
In some exemplary embodiments, the method 200 of processing transaction data may further include: the server 50 stores the valid tile data in the database and creates an index for it.
In some exemplary embodiments, the method 200 of processing transaction data may further include: the server 50 records the processing status of the block data.
Step S216: the server 50 sends a message to the payer 10 or the mobile terminal 12 indicating that the transaction data for the targeted transaction is already available for viewing.
For example, the server 50 may send the message to the notification service provider, which forwards the message to the payer 10 or the mobile terminal 12.
Step S218: the mobile terminal 12 displays a target interface including a requested link to the transaction data.
For example, mobile terminal 12 may display a message at mobile terminal 12 containing a requested link to the transaction data after receiving the message indicating that the transaction data for the target transaction is already available for viewing.
In some exemplary embodiments, the message may contain a request link to the list of transaction data. In some exemplary embodiments, the message may contain an interface jump link. For example, when the payer 10 clicks on the message, the current interface of the mobile terminal 12 will jump to a menu interface containing the requested link to the list of transaction data.
Step S220: the mobile terminal 12 receives a trigger instruction for the payer 10 to request the link.
For example, the triggering instruction may be a gesture operation trigger (e.g., sliding, clicking, touching) by the payer 10, a voice trigger by the payer 10, other devices of the mobile terminal 12 (e.g., an accelerator, a gyroscope, a GPS, a camera, an earpiece, a speaker), or other devices in communication with the mobile terminal 12, such as a message trigger from other devices or a trigger by other devices via remote assistance software installed on the mobile terminal 12.
Step S222: the mobile terminal 12 sends a request instruction to the server 50 in response to the trigger instruction to instruct the server 50 to download the transaction data from the target blockchain 40.
In some exemplary embodiments, the request instruction may include a request to obtain the list of transaction data, and the method 200 further includes: the mobile terminal 12 sends a request instruction to the server 50 to request to acquire the list of transaction data from the server 50 in response to the trigger instruction. The server 50, upon receiving the request instruction, may send the list of transaction data to the mobile terminal 12.
Step S224: the server 50 sends a request to the blockchain 40 to obtain the transaction data.
Step S226: the server 50 downloads the transaction data from the blockchain 40.
In some exemplary embodiments, blockchain 40 may send the transaction data to server 50.
Step S228: the server 50 transmits the transaction data to the mobile terminal 12.
In some exemplary embodiments, the server 50 may push an operation control of at least one of the payee 30 and the payment platform to the mobile terminal 12 based on the transaction data. Payer 10 may interact with payee 30 and/or a program or plug-in provided by the paymate through the operational control, e.g., by accessing a webpage of payee 30 and/or the paymate through a link provided by the operational control or receiving a push of message from payee 30 and/or the paymate.
Step S230: the mobile terminal 12 displays the transaction data.
Fig. 4 schematically illustrates a flow diagram of a method for processing transaction data for a mobile terminal according to one or more exemplary embodiments of the present description. Fig. 5 schematically illustrates a usage diagram of a mobile terminal according to one or more exemplary embodiments of the present description.
As shown in fig. 4, the method 300 of processing transaction information may include at least one or more of step S302, step S304, step S306, step S308, step S310, and step S312. The method 300 of processing transaction information may be used with a mobile terminal 12.
Step S302: the mobile terminal 12 completes the electronic payment to the payee 30 of the target transaction through the payment platform, whose transaction data is uploaded onto the target blockchain 40.
In some exemplary embodiments, completing an electronic payment to a payee 30 of the target transaction by the payment platform may include: the data of the payment account number and the payment authorization data are sent to the transaction device 20 to authorize the transaction device 20 to collect the transaction amount from the payment account number through the payment platform.
In some exemplary embodiments, completing an electronic payment to a payee 30 of the target transaction by the payment platform may include: the electronic payment is completed by providing the identity information to the transaction device 20. The identity information may be an identification number of the payer 10, biometric information of the payer 10, a preset password, a device ID of the mobile terminal 12, etc.
In some exemplary embodiments, the transaction data is uploaded by the transaction device 20 onto the target blockchain 40.
In some exemplary embodiments, the transaction data includes at least one of bank account information of the payee 30, bank account information of the payer 10 for the target transaction, and a taxpayer identification number of the payer 10.
Step S304: the mobile terminal 12 displays a target interface including a requested link to the transaction data.
In some exemplary embodiments, the target interface may include a request link to the listing of transaction data.
Step S306: the mobile terminal 12 receives a trigger instruction for the payer 10 to request the link.
Step S308: the mobile terminal 12 sends a request instruction to the server in response to the trigger instruction to instruct the server to download the transaction data from the target blockchain.
In some exemplary embodiments, the request instruction includes a request to obtain the list of transaction data, and the method 300 may further include: the mobile terminal 12 receives the list of transaction data from the server 50; and the mobile terminal 12 displays the list of transaction data.
Step S310: the mobile terminal 12 receives the transaction data downloaded by the server 50 of the payment platform from the target blockchain 40.
Step S312: the mobile terminal 12 displays the transaction data.
In some exemplary embodiments, the method 300 of processing transaction data may further include: displaying an operational control of at least one of a payee 30 and the payment platform based on the transaction data. In some exemplary embodiments, the operator control allows a program of payee 30 to access a display interface of the transaction data.
In some exemplary embodiments, the mobile terminal 12 may display the list of transaction data. In some exemplary embodiments, the list may contain a link to view the transaction data.
The mobile terminal 12 may include at least one storage medium that may store at least one set of instructions for processing transaction data and at least one processor (see fig. 1) communicatively coupled to the at least one storage medium. Wherein when the at least one processor executes the at least one set of instructions, the at least one processor performs the method 300 of processing transaction data.
The at least one storage medium may be various forms of program storage media and data storage media, such as a magnetic disk, Read Only Memory (ROM), Random Access Memory (RAM), flash memory, volatile memory, non-volatile memory, cache memory, buffers, short term storage units, long term storage units, or other suitable storage units for storing various data files to be processed and/or transmitted. The at least one storage medium may be a storage medium local to the mobile terminal 12, or may be a storage medium shared by the mobile terminal 12. The at least one processor may be a Central Processing Unit (CPU), Micro Processing Unit (MPU), Digital Signal Processor (DSP), circuitry, logic unit, Integrated Circuit (IC), or the like. The mobile terminal 12 may be implemented on a distributed computing system. For example, the mobile terminal 12 may be a single or multiple computing devices on the distributed computing system. The mobile terminal 12 may also be a general purpose computer or a special purpose computer. For example, the mobile terminal 12 may be a server, a personal computer, a portable computer (such as a notebook computer, a tablet computer, etc.), a mobile phone, a smart phone, a cellular phone, a handheld device, a PDA device, or an electronic device with other computing capabilities. The mobile terminal 12 may include a COM port that may be connected to or taken out of a network to which it is connected to facilitate data communication. The mobile terminal 12 may also include an internal communication bus. The mobile terminal 12 may also include I/O components to support data communication with other computing devices in the distributed computing system. The I/O components may include an input unit, which may include, for example, a keyboard, keypad, mouse, touch screen, touch pad, trackball, stylus, microphone, or other suitable pointing device or input device, and an output unit. The output unit may include, for example, a monitor, a screen, a touch screen, a flat panel display, a Light Emitting Diode (LED) display unit, a Liquid Crystal Display (LCD) display unit, a plasma display unit, one or more speakers or headphones, or other suitable output device. The mobile terminal 12 may also receive programming and data via a communication network. The communication network may include a wired network, a Local Area Network (LAN), a wireless LAN (wlan) network, a radio network, a cellular network, a wireless fidelity (WiFi) network, an IR network, a Bluetooth (BT) network, and so forth.
Fig. 6 schematically illustrates a flow diagram of a method for processing transaction data for a server of a payment platform according to one or more exemplary embodiments of the present description.
As shown in fig. 6, the method 400 of processing transaction information may include at least one or more of step S402, step S404, step S406, step S408, step S410, and step S412. The method 400 of processing transaction information may be used with the server 50.
Step S402: the server 50 confirms that the payer 10 logs on the payment platform.
For example, payer 10 may log onto the payment platform (e.g., via mobile terminal 12) to complete authentication before completing the electronic payment.
Step S404: the server 50 makes an electronic payment to the payee 30 of the target transaction, which is made between the payer 10 and the payee 30.
For example, after the payer 10 completes the identity verification and sends the data for the payment account number and the payment authorization data to the transaction device 20 to authorize the transaction device 20 to collect the transaction amount from the payment account number through the paymate, the server 50 may complete the actual payment (e.g., funds transfer) to the recipient 30 for the target transaction.
In some exemplary embodiments, the server 50 may acquire at least one of an order number of the target transaction, bank account information of the payee 30, and a taxpayer identification number of the payer 10 from the payee 30. In some exemplary embodiments, the transaction data for the target transaction includes the order number.
In some exemplary embodiments, the method 400 of processing transaction data may include: the server 50 performs block output monitoring on the target block chain 40; the server 50 receives out-chunk notifications from the target blockchain 40; the server 50 sends a request for extracting block data to the target block chain 40; and the server 50 receives the block data from the target block chain 40.
In some exemplary embodiments, the method 400 of processing transaction data may include: the server 50 sends a request for extracting a payment order to the acquiring system of the payment platform; and the server 50 receives the payment order from the acquiring system.
In some exemplary embodiments, the method 400 of processing transaction data may include: the server 50 supplements the payment information based on the payment order.
In some exemplary embodiments, the method 400 of processing transaction data may include: the server 50 stores the valid tile data in the database and creates an index for it.
In some exemplary embodiments, the method 400 of processing transaction data may include: the server 50 records the processing status of the block data.
Step S406: the server 50 receives a request from the mobile terminal 12 of the payer 10 to obtain the transaction data.
In some exemplary embodiments, the server 50 may receive a request from the mobile terminal 12 of the payer 10 to obtain the list of transaction data. Upon receiving a request from the mobile terminal 12 to obtain the list of transaction data, the server 50 may send the list of transaction data to the mobile terminal 12. In some exemplary embodiments, the list may contain a request link for the transaction data.
In some exemplary embodiments, the method 400 of processing transaction data may include: the server 50 receives a request from the mobile terminal 12 to obtain the list of transaction data; and the server 50 sends the list to the mobile terminal 12.
Step S408: the server 50 sends a request to the target blockchain 40 to obtain the transaction data.
Step S410: the server 50 downloads the transaction data from the target blockchain 40.
Step S412: the server 50 sends the transaction data to the mobile terminal 12.
In some exemplary embodiments, the method 400 of processing transaction data may include: the server 50 pushes an operation control of at least one of the payee 30 and the payment platform to the mobile terminal 12 based on the transaction data.
The server 50 may include at least one storage medium that may store at least one set of instructions for processing transaction data and at least one processor (see fig. 1) communicatively coupled to the at least one storage medium. Wherein when the at least one processor executes the at least one set of instructions, the at least one processor performs the method 400 of processing transaction data.
The at least one storage medium may be various forms of program storage media and data storage media, such as a magnetic disk, Read Only Memory (ROM), Random Access Memory (RAM), flash memory, volatile memory, non-volatile memory, cache memory, buffers, short term storage units, long term storage units, or other suitable storage units for storing various data files to be processed and/or transmitted. The at least one storage medium may be a storage medium local to the server 50 or a storage medium shared by the mobile terminals 12. The at least one processor may be a Central Processing Unit (CPU), Micro Processing Unit (MPU), Digital Signal Processor (DSP), circuitry, logic unit, Integrated Circuit (IC), or the like. The server 50 may be applied on a distributed computing system. For example, the server 50 may be a single or multiple computing devices on the distributed computing system. The server 50 may also be a general purpose computer or a special purpose computer. For example, the server 50 may be a server, a personal computer, a portable computer (such as a notebook computer, a tablet computer, etc.), a mobile phone, a smart phone, a cellular phone, a handheld device, a PDA device, or an electronic device with other computing capabilities. The server 50 may include COM ports that may be connected to or from a network to which it is connected to facilitate data communications. The server 50 may also include an internal communication bus. The server 50 may also include I/O components to support data communications with other computing devices in the distributed computing system. The I/O components may include an input unit, which may include, for example, a keyboard, keypad, mouse, touch screen, touch pad, trackball, stylus, microphone, or other suitable pointing device or input device, and an output unit. The output unit may include, for example, a monitor, a screen, a touch screen, a flat panel display, a Light Emitting Diode (LED) display unit, a Liquid Crystal Display (LCD) display unit, a plasma display unit, one or more speakers or headphones, or other suitable output device. The server 50 may also receive programming and data via a communication network. The communication network may include a wired network, a Local Area Network (LAN), a wireless LAN (wlan) network, a radio network, a cellular network, a wireless fidelity (WiFi) network, an IR network, a Bluetooth (BT) network, and so forth.
In this specification, a method/step/operation performed by one processor may also be performed by a plurality of processors collectively or individually. For example, if in this specification, the processor may perform step a and step B simultaneously. It should be understood that steps a and B may also be performed by two different processors together. For example, a first processor performs step a and a second processor performs step B, or the first processor and the second processor perform steps a and B together.
Each patent, patent application, publication of a patent application, and other material, such as articles, books, descriptions, publications, documents, articles, and the like, cited herein is hereby incorporated by reference. All matters hithertofore set forth herein except as related to any prosecution history, may be inconsistent or conflicting with this document or any prosecution history which may have a limiting effect on the broadest scope of the claims. Now or later associated with this document. For example, if there is any inconsistency or conflict in the description, definition, and/or use of terms associated with any of the included materials with respect to the terms, descriptions, definitions, and/or uses associated with this document, the terms in this document are used.
While certain embodiments of the present disclosure have been described above, other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
Finally, it should be understood that the embodiments of the application disclosed herein are illustrative of the principles of the embodiments of the present specification. Other modified embodiments are also within the scope of this description. Accordingly, the disclosed embodiments are to be considered in all respects as illustrative and not restrictive. Those skilled in the art may implement the applications in this specification in alternative configurations according to the embodiments in this specification. Therefore, the embodiments of the present description are not limited to the embodiments described precisely in the application.

Claims (19)

1. A method of processing transaction data for a mobile terminal, comprising:
completing electronic payment to a payee of a target transaction through a payment platform, wherein transaction data of the target transaction is uploaded to a target block chain;
receiving the transaction data downloaded by a server of the payment platform from the target blockchain; and
and displaying the transaction data.
2. The method of claim 1, wherein the completing, by the payment platform, the electronic payment to the payee of the target transaction comprises:
and sending the data of the payment account and payment authorization data to transaction equipment so as to authorize the transaction equipment to receive transaction amount from the payment account through the payment platform.
3. The method of claim 2, wherein the completing, by the payment platform, the electronic payment to the payee of the target transaction comprises:
the electronic payment is completed by providing identity information to the transaction device.
4. The method of claim 2, wherein the transaction data is uploaded onto the target blockchain by the transaction device.
5. The method of claim 1, further comprising:
displaying a target interface, wherein the target interface comprises a request link of the transaction data;
receiving a triggering instruction of a payer to the request link; and
in response to the triggering instruction, sending a request instruction to the server to instruct the server to download the transaction data from the target blockchain.
6. The method of claim 5, wherein,
the request instruction includes a request to obtain the list of transaction data, an
The method further comprises the following steps:
receiving the list from the server; and
and displaying the list.
7. The method of claim 1, further comprising:
displaying an operation control of at least one of the payee and the payment platform based on the transaction data.
8. The method of claim 1, wherein the transaction data includes at least one of bank account information of the payee, bank account information of a payer of the target transaction, and a taxpayer identification number of the payer.
9. A mobile terminal, comprising:
at least one storage medium storing at least one set of instructions for processing transaction data; and
at least one processor communicatively coupled to the at least one storage medium,
wherein the at least one processor performs the method of any one of claims 1 to 8 when the at least one processor executes the at least one set of instructions.
10. A method of processing transaction data for a server of a payment platform, comprising:
confirming that a payer logs in the payment platform;
making an electronic payment to a payee for a target transaction, the target transaction being made between the payer and the payee;
receiving a request from a mobile terminal of the payer to acquire the transaction data;
sending a request for acquiring the transaction data to a target block chain;
downloading the transaction data from the target blockchain; and
and sending the transaction data to the mobile terminal.
11. The method of claim 10, further comprising:
obtaining at least one of an order number of the target transaction, bank account information of the payee, and a taxpayer identification number of the payer from the payee,
wherein the transaction data includes the order number.
12. The method of claim 10, further comprising:
receiving a request from the mobile terminal to obtain the list of transaction data; and
and sending the list to the mobile terminal.
13. The method of claim 10, further comprising:
performing out-of-block monitoring on the target block chain;
receiving an out-of-block notification from the target blockchain;
sending a request for extracting block data to the target block chain; and
receiving the block data from the target blockchain.
14. The method of claim 13, further comprising:
sending a request for extracting a payment order to an order receiving system of the payment platform; and
receiving the payment order from the acquiring system.
15. The method of claim 10, further comprising:
pushing an operation control of at least one of the payee and the payment platform to the mobile terminal based on the transaction data.
16. A server of a payment platform, comprising:
at least one storage medium storing at least one set of instructions for processing transaction data; and
at least one processor communicatively coupled to the at least one storage medium,
wherein the at least one processor performs the method of any one of claims 10 to 15 when the at least one processor executes the at least one set of instructions.
17. A method of processing transaction data, comprising:
the payer completes electronic payment to the payee of the target transaction through the transaction device via the payment platform;
the transaction equipment uploads transaction data of the target transaction to a target block chain;
the target block chain sends the transaction data to a server of the payment platform;
the server sends the transaction data to a mobile terminal of the payer; and
and the mobile terminal displays the transaction data.
18. The method of claim 17, further comprising:
the mobile terminal displays a target interface, and the target interface comprises a request link of the transaction data;
the mobile terminal receives a trigger instruction of the payer for the request link; and
and the mobile terminal responds to the trigger instruction and sends a request instruction to the server so as to instruct the server to download the transaction data from the target blockchain.
19. The method of claim 17, further comprising:
the mobile terminal displays an operation control of at least one of the payee and the payment platform based on the transaction data.
CN202011029229.XA 2020-09-27 2020-09-27 Method for processing transaction data, mobile terminal and server of payment platform Pending CN111932227A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011029229.XA CN111932227A (en) 2020-09-27 2020-09-27 Method for processing transaction data, mobile terminal and server of payment platform

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011029229.XA CN111932227A (en) 2020-09-27 2020-09-27 Method for processing transaction data, mobile terminal and server of payment platform

Publications (1)

Publication Number Publication Date
CN111932227A true CN111932227A (en) 2020-11-13

Family

ID=73334257

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011029229.XA Pending CN111932227A (en) 2020-09-27 2020-09-27 Method for processing transaction data, mobile terminal and server of payment platform

Country Status (1)

Country Link
CN (1) CN111932227A (en)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112613873A (en) * 2020-11-20 2021-04-06 北京尚博信科技有限公司 Traceable payment method and payment equipment for energy charging station
CN112667968A (en) * 2020-12-22 2021-04-16 银联商务股份有限公司 Data processing device, method, equipment and readable storage medium
CN113409038A (en) * 2021-06-30 2021-09-17 中国银行股份有限公司 Payment service processing method and device based on block chain
CN114389816A (en) * 2021-12-21 2022-04-22 南京欣网互联网络科技有限公司 Block chain-based online service system and method for service ecological supply alliance

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101165716A (en) * 2006-10-16 2008-04-23 祁勇 Electronic payment procedure based on transaction code
CN108876359A (en) * 2018-01-03 2018-11-23 上海指旺信息科技有限公司 Stored value card platform based on block chain
CN110930151A (en) * 2019-11-29 2020-03-27 中国工商银行股份有限公司 Transaction processing method and device based on block chain, computing equipment and medium

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101165716A (en) * 2006-10-16 2008-04-23 祁勇 Electronic payment procedure based on transaction code
CN108876359A (en) * 2018-01-03 2018-11-23 上海指旺信息科技有限公司 Stored value card platform based on block chain
CN110930151A (en) * 2019-11-29 2020-03-27 中国工商银行股份有限公司 Transaction processing method and device based on block chain, computing equipment and medium

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112613873A (en) * 2020-11-20 2021-04-06 北京尚博信科技有限公司 Traceable payment method and payment equipment for energy charging station
CN112613873B (en) * 2020-11-20 2024-01-12 北京尚博信科技有限公司 Traceable payment method and payment equipment for energy charging station
CN112667968A (en) * 2020-12-22 2021-04-16 银联商务股份有限公司 Data processing device, method, equipment and readable storage medium
CN112667968B (en) * 2020-12-22 2023-01-24 银联商务股份有限公司 Data processing device, method, equipment and readable storage medium
CN113409038A (en) * 2021-06-30 2021-09-17 中国银行股份有限公司 Payment service processing method and device based on block chain
CN114389816A (en) * 2021-12-21 2022-04-22 南京欣网互联网络科技有限公司 Block chain-based online service system and method for service ecological supply alliance

Similar Documents

Publication Publication Date Title
CN110612546B (en) Method and apparatus for digital asset account management
US20210216990A1 (en) Systems, methods and apparatus for payment terminal management
CN111932227A (en) Method for processing transaction data, mobile terminal and server of payment platform
US11651352B2 (en) Digital asset distribution by transaction device
US8620260B2 (en) Payment application download to mobile phone and phone personalization
CN101990770A (en) Ghosting payment account data in a mobile telephone payment transaction system
CN107924521B (en) Systems, methods, and apparatus for updating an existing dynamic transaction card
CN101223729B (en) Updating a mobile payment device
JP5775663B2 (en) White card usage limit increase system and its operation method
KR100869157B1 (en) Apparatus, Method and Computer Program Recorded Medium for Providing Electronic Wallet Service
CN1930592A (en) Emv transactions in mobile terminals
KR20070065863A (en) Apparatus, system, method and computer program recorded medium for providing electronic waller service by using usim (universal subscriber identity module) card
CN103065241A (en) Cloud credit card transaction system and transaction method thereof
TWM589842U (en) Mobile trading desk with real-name phone
TW201643782A (en) A computing device, system, method, computer program and data signal arranged to facilitate payments
KR20110035548A (en) Apparatus and method of credit card settlement using a mobile station in a electronic settlement system and system thereof
RU115528U1 (en) TERMINAL (TAXOMAT) FOR THE EXCHANGE OF LEGALLY VALUABLE INFORMATION
KR100914662B1 (en) Method for Providing Cash-back Correspond to Medical Supplies Purchasing
US11783330B2 (en) System and method for processing secure transactions using account-transferable transaction cards
KR20070094221A (en) System and method for processing financial transaction and recording medium
WO2023152757A1 (en) A system and a method for payment and instant refund using a biometric digital wallet
JP5885361B2 (en) White card usage limit increase system and its operation method
KR100966295B1 (en) Method for Providing Electronic Wallet Service by Using Universal Subscriber Identity Module Card and Electronic Wallet Apparatus
KR20090128944A (en) Financial terminal with function of applying giro automatic payment, system and method for applying giro automatic payment by using terminal
KR20090001879A (en) System and method for reinvesting deductions and exemptions refund from income and program recording medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
TA01 Transfer of patent application right

Effective date of registration: 20230112

Address after: 200120 Floor 15, No. 447, Nanquan North Road, Free Trade Pilot Zone, Pudong New Area, Shanghai

Applicant after: Alipay.com Co.,Ltd.

Address before: 310000 801-11 section B, 8th floor, 556 Xixi Road, Xihu District, Hangzhou City, Zhejiang Province

Applicant before: Alipay (Hangzhou) Information Technology Co.,Ltd.

TA01 Transfer of patent application right