TWI832100B - Credit card management server for electronic payment - Google Patents

Abstract

A credit card management server for electronic payment includes a communication interface and a processor. The processor is configured to read a trade flag and a card-user data of a request for applying cards; the processor is configured to transmit data of the credit card through the communication interface to a trade database of the trade flag after activating a credit card of the card-user data, such that an electronic device reads the data of the credit card of the trade database while executing a trade application, in order to operate the electronic payment.

Description

Credit card management server for electronic payments

This case relates to an electronic payment device, and in particular to a credit card management server for electronic payment.

With the development of electronic payment functions, more and more mobile applications can be combined with credit card payments to achieve the functions of electronic payment or electronic wallet.

Even though every mobile application can implement electronic payment or e-wallet through credit cards, users need to launch the mobile application one by one, manually enter credit card information, verify the credit card authorization on the mobile application, etc. The method is quite inconvenient.

Accordingly, it is necessary to propose solutions to improve the convenience of use in response to the inconvenience of entering credit card information one by one in electronic payments or electronic wallets.

This Summary is intended to provide a simplified summary of the disclosure to provide the reader with a basic understanding of the disclosure. This summary is not an extensive overview of the disclosure, and it is not intended to identify key/critical elements of the embodiments or to delineate the scope of the disclosure.

According to one embodiment of this case, a credit card management server for electronic payment is disclosed, including: a communication interface for receiving a card application request; and a processor coupled to the communication interface, wherein the processor is configured To read a merchant tag and a card account information of the card application request; wherein the processor is configured to send the credit card information to the corresponding merchant tag through the communication interface after activating a credit card with the card account information. A merchant database allows an electronic device to read the credit card information in the merchant database when executing a merchant application to perform the electronic payment operation.

According to another embodiment, a credit card management server for electronic payment is disclosed, including: a communication interface; and a processor coupled to the communication interface, wherein the processor is configured to query a merchant corresponding to a merchant tag Whether there is a member information corresponding to the card user information in the database; when it is determined that the member information does not exist, the processor receives a registration request through the communication interface, and automatically executes a registration process for the merchant member; after completing the After the registration process, it is determined whether a credit card of a bank account has been bound to a merchant application, and when the processor determines that the credit card of the bank account is not bound to the merchant application, the processor uses the communication interface Receive a binding request; wherein the processor is further configured to compare whether a user information of the bank account is consistent with a merchant member information of the merchant application according to the binding request, to determine whether to combine the user information with the merchant application. The merchant's membership information is integrated and recorded into an electronic payment database.

The following disclosure provides many different embodiments or examples for implementing various features of the present invention. Specific examples of components and arrangements are described below to simplify the present invention. Of course, these examples are merely illustrative and not intended to be limiting. For example, the use of terms such as "first" and "second" in this case to describe components is only used to distinguish the same or similar components or operations. These terms are not used to limit the technical components of this case, nor are they used to Define the order or sequence of operations. In addition, the present invention may repeat component symbols and/or letters in each embodiment, and the same technical terms may use the same and/or different component symbols in each embodiment. This repetition is for simplicity and clarity and does not by itself indicate a relationship between the various embodiments and/or configurations discussed.

Please refer to Figure 1 , which illustrates a schematic diagram of a credit card management server 100 for electronic payment according to some embodiments of the present invention. The credit card management server 100 may be a server of a banking institution, which receives, stores, manages and uses bank user information. As shown in Figure 1, the credit card management server 100, the electronic device 600 and the merchant server 700 can exchange data with each other through the communication network 800. In some embodiments, the credit card management server 100 can manage credit card information of bank users and perform electronic payment services. For example, services such as credit card binding for merchant services are described in detail below.

The credit card management server 100 includes a processor 110, a communication interface 120 and a storage medium 130. The processor 110 is coupled to the communication interface 120 and the storage medium 130 . The storage medium 130 is used to store the credit card database, such as the personal information of each bank user. In some embodiments, the storage medium 130 includes a credit card database 132 and an electronic payment database 134.

In some embodiments, the electronic payment database 134 is used for the electronic device 600 to execute the merchant application 610. When the electronic payment is executed, the credit card management server 100 maintains the merchant's cash flow management services and operations.

In some embodiments, the electronic device 600 can be a mobile electronic device, a desktop computer, a notebook computer, etc., and any electronic device that can execute merchant applications falls within the scope of this case. For example, the merchant application may be a bank client application installed on the mobile electronic device.

In some embodiments, the merchant server 700 can be an online shopping mall or a server that runs electronic payment, so that the electronic device 600 can execute a mobile application of the online shopping mall or electronic payment, allowing the user to purchase items or Make electronic payments. For example, the merchant server 700 can be a Yahoo online shopping server, a Quanlian shopping server, a unified supermarket server, etc. Correspondingly, the electronic device 600 can be installed with Yahoo mobile applications, Quanlian mobile applications, unified supermarket applications, etc., that is, applications released by different product and/or service providers (hereinafter referred to as merchants). In the following description in this case, merchant application 610 will be used to represent these mobile applications provided by merchants. The electronic device 600 can execute mobile applications provided by these merchants to complete electronic payment services.

In some embodiments, the electronic device 600 can execute a mobile application provided by the banking enterprise, such as the bank mobile application 620, or the electronic device 600 can connect to the management server of the banking enterprise through a mobile web page.

In some embodiments, the electronic device 600 can be used to execute banking mobile applications and mobile applications provided by merchants. When the user wants to use the mobile application provided by the merchant to perform electronic payment, if the merchant user does not hold a bank credit card at this time, in addition to providing the user with credit card application services through the credit card management server 100, It is also possible to add the user's credit card information to the merchant database 710 of the merchant server 700 through the credit card management server 100 when the bank has completed the approval of the credit card and the new card is undergoing the card opening procedure, so that the credit card can be The user can complete the credit card binding in the merchant application 610 at the same time when opening the card.

Please refer to Figure 2, which illustrates a flow chart of a credit card management method according to some embodiments of this case. To clearly explain the credit card management method in this case, please refer to Figure 1 as well.

In step S201, the bank's online credit card application webpage is executed through the electronic device 600.

It is worth mentioning that in the embodiment in which step S201 is executed, subsequent steps S206 and S209 are also performed through the bank's online webpage.

Step S201 is a way to apply for a credit card online through a bank. This case also provides another embodiment to apply for a credit card, such as step S202.

In step S202, the merchant application is executed through the electronic device 600.

In some embodiments, in either step S201 or step S202, the user is not a member of the merchant yet. It should be noted that the merchants in this case refer to product or service providers such as Quanlian, Yahoo, and Uni-President Supermarket, and the merchant applications refer to the applications owned by these product or service providers.

In some embodiments, the merchant application has a hyperlink (such as a banner ad link), and this hyperlink is used to request server services from the credit card management server 100, such as a card application request. The credit card management server 100 responds to the card application request of the electronic device 600, so that the screen of the electronic device 600 will display the screen of the credit card application program. In some embodiments, the credit card application program may be implemented as a sub-program of a bank's mobile application or as a web application.

In some embodiments, when a hyperlink is clicked to generate a card application request, the electronic device 600 will pop up a prompt message asking whether to agree to the personal data terms. After the user agrees to the personal data terms, the card application request and the data agreeing to the personal data terms are simultaneously sent to the credit card management server 100 .

In some embodiments, as different merchant applications 610 are executed, the corresponding merchant tag (flag) will be appended to the card application request.

In step S204, the user clicks the card application link of the merchant application and sends the card application request to the credit card management server 100 through the electronic device 600.

In some embodiments, any user can click on the card application link on the merchant's application. This case is not limited to whether the user has membership status. For example, regardless of whether the user is a member of the merchant, the merchant application can be installed on the electronic device 600 . Since the card application link can be embedded in the merchant application in advance, all users can click on this link to perform subsequent card application procedures.

In some embodiments, since the credit card management server 100 does not know whether the user is already a member of the merchant at the beginning, the credit card management server 100 reads a merchant tag and a card user information in the card application request to For subsequent comparison of member information.

In some embodiments, the user submits application information through the bank's credit card application webpage (eg, step S201) or connects to the application webpage through the merchant application (eg, step S202), and completes identity verification online. For example, the user performs one-time password (OTP) verification through the electronic device 600 .

In some embodiments, after step S201/step S202 to step S204 and before step S206, the merchant server 700 may selectively determine whether the cardholder is a member of the merchant. In the embodiment of determining that the cardholder is a member of the merchant, the determination procedure of step S210 may be optionally omitted. If the merchant server 700 replies that the cardholder is a member of the merchant, the credit card management server 100 associates the merchant's membership information (such as merchant label and membership number) to the cardholder information.

In some embodiments, the processor 110 queries the corresponding merchant server 700 for data according to the merchant tag. For example, if the merchant label is Quanlian Company, a query is made to the merchant server 700 of Quanlian Company.

In some embodiments, the merchant database 710 stores member information of multiple merchants, such as member information of Quanlian Company. The merchant server 700 compares the member information based on the card user information. For example, the card account information includes a phone number (such as a phone number, such as a mobile phone number, a local phone number, and an Internet phone number). If the merchant server 700 finds the same phone number in the merchant database 710, it represents the bank. The user is a member of Quanlian Company.

In some embodiments, the cardholder information may be, but is not limited to, a phone number, a project code, a member identification code, etc.

On the other hand, if the merchant server 700 queries the merchant database 710 and there is no member information corresponding to the card account information, it means that the bank user is not a member of Quanlian Company.

In step S206, the credit card management server 100 executes a credit card application process based on the user's credit card application information. Among them, this credit card application information will be associated with a merchant tag, and the credit card management server 100 will manage which merchants the credit card is currently bound to.

In some embodiments, the user's credit card application information will be stored in the credit card database 132 . Credit card application information can be, but is not limited to, user identification code, phone number, project code, merchant's membership identification code and other communication information and personal information about the user.

In some embodiments, since the credit card application process is initiated through the merchant application 610 (such as the mobile application of Quanlian Company), the credit card management server 100 will associate the credit card application information with the membership information of the merchant. For example, the credit card information will be associated with the All-Union membership.

In step S208, after the credit card management server 100 receives a card opening request, the processor 110 activates the credit card according to the card user information in the card opening request.

In some embodiments, after approving the card, the credit card management server 100 will integrate and store the aforementioned credit card application information and the merchant's membership information into the credit card database 132 .

In some embodiments, after receiving the card approval notification, the user can perform the credit card opening procedure. During the card opening procedure, the credit card management server 100 will read the relevant credit card information in the card opening request, and use this information to compare the user information in the credit card database 132 . Credit card information can be, but is not limited to, credit card number, expiration date, card code, project code, birthday, mobile phone number, email address, Chinese name, etc.

In step S209, select the merchant to which the credit card is to be bound.

In some embodiments, users can open a card through the bank's webpage or bank's mobile application. Users can choose the credit card merchant they want to bind before or after opening the card. For example, if a user applies for a co-branded card from an American store (such as Costco), they can choose to bind the credit card to the American store's membership account or other merchants after opening the card. In other embodiments, the user can also select the merchant to which the credit card can be bound during the process of filling in information for applying for a credit card, and skip step S209.

In step S210, the processor 110 determines whether the merchant member information in the credit card database 132 is consistent with the member information in the merchant database 710 according to the card opening request.

In some embodiments, if the data are consistent, step S212 is performed. If the data is inconsistent, execute S214.

In some embodiments, the credit card management server 100 will read the merchant member information associated with the card opening request in the credit card database 132 to confirm the member identity information to the merchant server 700 based on the merchant member information.

In some embodiments, the merchant member information associated with the card opening request may be, but is not limited to, the merchant's member identification code, merchant key value (such as a phone number, such as a mobile phone number, a local phone number, an Internet phone number) ) and other information.

When the merchant member information in the credit card database 132 is consistent with the member information in the merchant database 710, in step S212, the credit card management server 100 stores the credit card information to the electronic payment database 134 to complete the credit card opening procedure and merchant membership. credit card binding.

In some embodiments, the credit card information may be a credit card number, expiration date, merchant's membership identification code, etc.

In this way, in step S212, the opening of the credit card and the binding of the credit card to the merchant member can be completed at the same time. When the electronic device 600 executes the merchant application 610 again, since the electronic payment database 134 has stored the merchant's membership information and corresponding credit card information, when the user operates the merchant application 610 on the electronic device 600, the merchant application 610 The credit card transaction request can be transmitted so that the electronic device 600 can directly perform credit card transaction deductions on the merchant application 610, such as shopping on the Quanlian mobile application, and use the credit card number to perform electronic payment operations.

When the merchant member information in the credit card database 132 is inconsistent with the member information in the merchant database 710, in step S214, the credit card management server 100 only completes the credit card opening procedure, but the merchant member's credit card binding fails, that is, no The credit card related information is stored in the electronic payment database 134.

After completing the credit card binding in step S212, step S216 is executed.

In step S216, the credit card management server 100 executes the electronic payment verification process.

In some embodiments, after the credit card management server 100 successfully binds the credit card, the electronic device 600 needs to complete identity verification before it can execute the electronic payment function of the merchant application 610.

The credit card management server 100 generates a password, such as a one-time password (OTP), for verification by the merchant application 610 of the electronic device 600 . After successful verification, the electronic device 600 can execute the electronic payment function of the merchant application 610 .

This project provides a server and method for digital card opening and binding of merchant electronic wallets. Users can apply for online digital cards by operating the electronic device 600, and after the card is successfully opened, the merchant member's credit card can be completed. Binding. In this way, the trinity is integrated while providing online card processing and merchant electronic payment binding.

Please refer to Figures 3A to 3B, which illustrate a flow chart of a credit card management method according to other embodiments of the present case. The credit card management method in Figures 3A to 3B provides the ability to bind credit cards to merchant members without having to enter the credit card number information yourself. To clearly explain the credit card management method in this case, please refer to Figure 1 as well.

In step S302, the bank mobile application 620 is executed by the electronic device 600 to log in to the bank account.

In some embodiments, the banking mobile application 620 is, for example, the Cathay Bank Credit Card digital banking application.

In step S304, the credit card management server 100 reads which merchant applications 610 the credit cards of the bank account have been bound to.

In some embodiments, the credit card management server 100 may query the merchant member information corresponding to each credit card of each bank account in the electronic payment database 134 to determine whether the credit card has been bound. For example, if the credit card in the bank account has a merchant tag recorded (such as Quanlian Company), it means that the credit card has been bound to the merchant application (such as Quanlian Company's PX Pay application).

In step S306, the processor 110 generates a binding list.

In some embodiments, the processor 110 pre-fetches all merchant applications. If the processor 110 determines which merchant applications have completed binding of bank credit cards, it will record them in the binding list. For example, if the credit card has been bound to the first merchant application, the second merchant application and the fourth merchant application, but has not been bound to the third merchant application and the fifth merchant application, then the binding list The three bound merchant applications and the two unbound merchant applications are logged.

In step S308, the electronic device 600 displays bound merchant applications and unbound merchant applications according to the binding list.

In some embodiments, the electronic device 600 executes the banking mobile application 620 to display an operation interface. This UI contains multiple sections or links to display bound merchant applications and unbound merchant applications. These blocks or links can be button boxes generated by the graphical interface.

In step S310, a card binding request is generated through the operation interface of the bank mobile application 620.

In some embodiments, if the user wants to bind a credit card to certain merchant applications, he or she can click or select multiple blocks or links in the operating interface to generate a card binding request for the merchant application. . For example, if you click the button box that displays "Bind to Quanlian PX Pay", the bank mobile application 620 will generate a card binding request to bind the credit card to Quanlian PX Pay.

In step S312, the electronic device 600 transmits the user information of the bank account to the credit card management server 100 to compare whether the user information of the bank account is consistent with the merchant member information of the credit card database 132.

In some embodiments, if the user information of the bank account is inconsistent with the merchant member information of the merchant database 710, step S314 is performed. If the user information of the bank account is consistent with the merchant member information of the merchant database 710, step S320 is executed.

In some embodiments, the credit card management server 100 transmits bank account user information, such as the user's phone number, to the merchant server 700 . The merchant server 700 determines whether the user information of the bank account is recorded in the merchant database 710, thereby determining whether the user of the bank is a merchant member. Then, the merchant server 700 will return the reply information of whether it is a merchant member to the credit card management server 100.

If it is determined that the user of the bank account is not a merchant member, then in step S314, a registration request is received through the credit card management server 100. For example, a membership prompt message is generated through the credit card management server 100 and displayed on the electronic device 600 for the user to decide whether to register to become a member and to execute the membership registration process. In some embodiments, the user can join the merchant membership online on the electronic device 600 . For example, the merchant application of the electronic device 600 will receive a prompt message indicating whether to join the membership and bind the card terms.

In step S316, the processor 110 determines whether an agreement message for joining the merchant membership and binding card terms is received.

In some embodiments, if the user clicks on the prompt message to join the merchant membership, it means that the user agrees to join the merchant membership. In some embodiments, if the user does not agree to the terms, step S318 is performed. If the user agrees to join the merchant membership and bind the card, step S320 is executed.

In some embodiments, the user can click or select the merchant member information displayed on the banking mobile application 620 of the electronic device 600 and agree to the credit card binding terms to generate an instruction to agree or disagree with the terms.

In step S318, a message indicating failure to join the merchant membership and/or failure to bind a credit card is displayed on the electronic device 600.

In step S320, the membership joining process is executed.

In some embodiments, during the membership membership process, the credit card management server 100 automatically generates membership membership application information to the merchant server 700 for background application processing. For example, the credit card management server 100 automatically forwards the user's bank account information, such as a mobile phone number, to the merchant server 700 to automatically complete the merchant membership registration process.

In step S322, the card binding procedure is executed.

In some embodiments, merchants available for binding credit cards are displayed on the electronic device 600 . For example, the electronic device 600 displays merchants such as Quanlian, Yahoo, and Uni-President Supermarket. If the user selects Quanlian, it means that the user wants to bind the credit card to Quanlian PX PAY.

In step S324, the merchant server 700 queries the credit card management server 100 for the electronic payment member identification code of the merchant member information.

In step S326, the credit card management server 100 starts the credit card binding process.

In some embodiments, the credit card management server 100 integrates and records credit card information, such as credit card number, validity period, merchant membership information, electronic payment member identification code and other information, into the electronic payment database 134 . In some embodiments, after successfully binding the credit card, the credit card management server 100 will send a success message to the bank mobile application 620 of the electronic device 600 for display.

In step S328, the user's identity is verified through the merchant application 610 of the electronic device 600.

In some embodiments, after the credit card management server 100 successfully binds the credit card, the electronic device 600 needs to complete identity verification before it can execute the electronic payment function of the merchant application 610.

In some embodiments, the credit card management server 100 sends a verification message to the merchant application 610 of the electronic device 600 . For example, the merchant application 610 of the electronic device 600 displays a dialog box for clicking to activate a credit card, and sends an activation request to the credit card management server 100 .

Then, the credit card management server 100 generates a password, such as a one-time password (OTP), for verification by the merchant application 610 of the electronic device 600 . After successful verification, the electronic device 600 can execute the electronic payment function of the merchant application 610 . If the verification fails, it means that the credit card binding fails.

In some embodiments, the connection between the credit card management server 100 and the merchant server 700 in Figure 1 uses an application programming interface (Application Programming Interface, API) to implement data exchange.

This project provides a server and method for cardless merchant wallet and card binding management. Users can manage personal credit cards by operating the bank mobile application 620 of the electronic device 600 and bind the credit cards directly on the operating interface. In the card program, users can freely choose which credit cards to bind to which merchants. For example, a credit card can be bound to one or more merchants at the same time, such as Quanlian PX Pay, Jiekou Pay, Qimo Super Pay and other electronic payments. Or e-wallet. In this way, the user does not need to enter the card number one by one into the electronic payment or electronic wallet that he wants to use. He only needs to use the bank mobile application 620 of the electronic device 600 to quickly bind the credit card and/or unbind the electronic payment of the credit card. or management of electronic wallets.

In some embodiments, when it is determined that the bank user is not a merchant member, the credit card management server 100 may also perform steps to quickly join the merchant member. For example, when the user executes the bank mobile application 620 through the electronic device 600 and completes identity verification and login, when the electronic device 600 executes the merchant application 610, the user will be asked whether he agrees to use the relevant information of the logged-in bank account. To add a merchant member, for example, the credit card management server 100 transmits the user information of the credit card database 132 to the merchant database of the merchant server 700 through the application programming interface to complete the merchant membership joining process. In this way, as long as the user clicks to agree on the bank mobile application 620, the user information of the bank can be used to quickly join the merchant's membership, eliminating the user's trouble of entering information.

In some embodiments, the process of quickly joining a merchant member may be to log in to the user account of the bank mobile application 620 on the merchant application 610, thereby bringing the bank's user information to the merchant application 610 to quickly join the merchant. Member.

The above content summarizes the features of several embodiments so that those familiar with the art can better understand the aspect of the present invention. Those skilled in the art should understand that the above may be readily used as a basis for designing or modifying other variations to carry out the same purposes and/or implementations of the embodiments described herein without departing from the spirit and scope of the invention. Same advantages. The above content should be understood as an example of this case, and its scope of protection should be subject to the scope of the patent application.

100:Credit card management server 110: Processor 120: Communication interface 130:Storage media 132:Credit card database 134: Electronic payment database 600: Electronic devices 610:Merchant Application 620:Banking Mobile App 700:Merchant server 710: Merchant database 800: Communication network S201~S216, S302~S328: steps

The following detailed description, when read in conjunction with the accompanying drawings, will help to better understand the aspect of this disclosure document. It should be noted that, based on practical needs for illustration, features in the drawings are not necessarily drawn to scale. In fact, the dimensions of various features may be arbitrarily increased or reduced for the purpose of clarity of discussion. Figure 1 is a schematic diagram of a credit card management server for electronic payment according to some embodiments of the present invention. Figure 2 illustrates a flow chart of a credit card management method according to some embodiments of this case. Figures 3A to 3B illustrate a flow chart of a credit card management method according to other embodiments of the present case.

Domestic storage information (please note in order of storage institution, date and number) without Overseas storage information (please note in order of storage country, institution, date, and number) without

100:Credit card management server

110: Processor

120: Communication interface

130:Storage media

132:Credit card database

134: Electronic payment database

600: Electronic devices

610:Merchant Application

620:Banking Mobile App

700:Merchant server

710: Merchant database

800: Communication network

Claims (5)

A credit card management server for electronic payment, including: a communication interface for receiving a card application request from a credit card, wherein the card application request is issued by an electronic device, and the card application request includes a merchant tag and A card account information; and a processor coupled to the communication interface, wherein the processor is configured to read the merchant tag of the card application request and the card account information; wherein the processor is further based on the information sent by the electronic device. A card opening request is made to determine whether to activate a credit card corresponding to the card account information; wherein, in response to determining whether to activate the credit card corresponding to the card account information, the processor sends the credit card information to the corresponding merchant tag through the communication interface. A merchant database of a merchant server is used to bind the credit card, so that when the electronic device executes a merchant application, it can read the credit card information in the merchant database to perform the electronic payment operation. The credit card management server of claim 1, further comprising: a storage medium coupled to the processor, wherein the storage medium is configured to store a credit card database, the credit card database has the card user with the merchant tag. material. A credit card management server as described in request 2, wherein When the processor determines that the card account information is the same as a member information in the merchant database, the processor associates the member information with the card account information. The credit card management server as described in request item 3, wherein the electronic device executes a bank online credit card application web page or the merchant application to issue the card application request, wherein the card application request includes a project code of the merchant tag, At least one of a member identification code and a member phone number of the merchant tag. The credit card management server as described in claim 4, wherein the processor activates the credit card according to the card opening request issued by the electronic device, so that the credit card information and the member information are integrated and stored in the credit card database.