TWM599948U - 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 payment

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

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

Even though every mobile application can use a credit card to realize electronic payment or electronic wallet, however, users need to activate the mobile application one by one, manually enter the 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 for the inconvenience of electronic payment or electronic wallet inputting credit card information one by one to improve the convenience of use.

According to an embodiment of the present 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 Set to read a merchant label and card account information of the card request; wherein the processor is configured to send the credit card information to the corresponding merchant label 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 running 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 account information in the database; when it is judged that the member information does not exist, the processor receives a registration request through the communication interface, and then automatically executes a registration procedure of the merchant member; After the registration process, it is determined whether a credit card of a bank account is 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 Receiving 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 the user information is consistent with The merchant member information is integrated and recorded into an electronic payment database.

100: Management server

100: Management server

110: processor

120: Communication interface

130: storage media

132: Credit Card Database

134: Electronic Payment Database

600: Electronic device

610: Merchant Application

620: Bank Mobile App

700: Merchant server

710: Merchant Database

S202~S216, S302~S328: steps

When the following detailed description is read in conjunction with the accompanying drawings, it will help to better understand the aspect of the present disclosure. It should be noted that according to the practical needs of the description Seeking, the various features in the diagram are not necessarily drawn to scale. In fact, for the purpose of clarity, the size of each feature may be increased or decreased arbitrarily.

Figure 1 shows a schematic diagram of a credit card management server for electronic payment according to some embodiments of the present case.

Figure 2 shows a flowchart of a credit card management method according to some embodiments of this case.

Figures 3A to 3B show a flow chart of a credit card management method according to other embodiments of the present case.

The following disclosure provides many different embodiments or examples in order to implement different features of the case. Specific embodiments of elements and arrangements are described below to simplify the case. Of course, these examples are only illustrative and not intended to be limiting. For example, the terms "first" and "second" used to describe elements in this case are only used to distinguish the same or similar elements or operations. The terms are not used to limit the technical elements of the case, nor are they used to Limit the order or sequence of operations. In addition, in this case, component symbols and/or letters may be repeated in each example, and the same technical term may use the same and/or different component symbols in each embodiment. This repetition is for the purpose of conciseness and clarity, and does not in itself indicate the 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 case. The credit card management server 100 may be a server of a banking enterprise, which receives, stores, manages and uses bank user data. As shown in Figure 1, the credit card management server The 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 the 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 a 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, when 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 may be a mobile electronic device, a desktop computer, a notebook computer, etc., and any electronic device that can execute a merchant application program falls within the scope of this case. For example, the merchant application can be a bank client application installed on a mobile electronic device.

In some embodiments, the merchant server 700 may be an online shopping mall or a server running electronic payment, so that the electronic device 600 can execute an online shopping mall or a mobile application for electronic payment, so that users can purchase items or Make electronic payments. For example, the merchant server 700 may be a Yahoo online shopping server, a Quanlian shopping server, a unified supermarket server, and so on. Correspondingly, the Yahoo mobile application can be installed on the electronic device 600 It is the applications released by different commodity and/or service providers (hereinafter referred to as merchants). In the following description in this case, the merchant application 610 will be used to represent these mobile applications provided by the merchant. 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 business, such as the banking mobile application 620, or the electronic device 600 can connect to the management server of the banking business through a mobile webpage.

In some embodiments, the electronic device 600 can be used to execute a banking mobile application of a banking business and a mobile application provided by a merchant. When the user wants to use the mobile application provided by the merchant to perform electronic payment, if the merchant user does not have a bank credit card at this time, in addition to providing the user with a credit card application service through the credit card management server 100, You can also complete the verification of the credit card in the banking business and when the new card is in the process of opening the card, at the same time, the credit card information of the user can be added to the merchant database 710 of the merchant server 700 through the credit card management server 100, so that the credit card The user can complete the credit card binding of the merchant application 610 at the time of opening the card.

Please refer to Figure 2, which illustrates a flowchart of a credit card management method in some embodiments of the present case. In order to clearly explain the credit card management method in this case, please refer to Figure 1 together.

In step S201, the electronic device 600 is used to execute the bank's online credit card application webpage.

It is worth mentioning that, in the embodiment where step S201 is executed, the 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. Another embodiment is provided in this case to execute the credit card application, such as step S202.

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

In some embodiments, whether it is step S201 or step S202, the user is not yet a member of the merchant. What I want to explain is that the merchants in this case refer to goods or service providers such as Quanlian, Yahoo, and Unicom, and the merchant applications refer to applications owned by these goods or service providers.

In some embodiments, the merchant application has a hyperlink (for example, a banner advertisement link), and the hyperlink is used to request server services from the management server 100, such as a card application request. The 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 a sub-program of a bank mobile application or a web application.

In some embodiments, when the hyperlink is clicked and the card application request is generated, the electronic device 600 will pop up a prompt message whether to agree to the personal data terms. After obtaining the user's agreement to the personal information terms, the card application request and the information of the personal information terms are sent to the credit card management server 100 at the same time.

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

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

In some embodiments, any user can click the card registration link on the merchant application. This case is not limited to whether the user has a membership status. For example, regardless of whether the user is a merchant member or not, 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 this link to perform the subsequent card application process.

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 account information in the card request For subsequent member data comparison.

In some embodiments, the user sends application information through the bank's credit card application webpage (such as step S201) or interfaces to the application webpage through a merchant application (such as 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 can selectively determine whether the card account is a member of the merchant. When the cardholder is judged to be a merchant In the embodiment of the member, the judgment procedure of step S210 can be selectively omitted. If the merchant server 700 replies that the card account is a member of the merchant, the credit card management server 100 associates the merchant's member information (such as the merchant label and the member number) with the card account information.

In some embodiments, the processor 110 queries the corresponding merchant server 700 for information based on the merchant tag. For example, if the merchant label is Quanlian Company, the merchant server 700 of Quanlian Company is inquired.

In some embodiments, the merchant database 710 stores the member information of multiple merchants, such as the member information of Quanlian Company. The merchant server 700 compares the member information based on the card account 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 call). 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 card account information may be, but is not limited to, a phone number, project code, member identification code, etc.

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

In step S206, the credit card management server 100 executes the credit card application procedure according to the user's credit card application data. Wherein, the credit card application data will be associated with the merchant tag, and the credit card management server 100 will manage the merchants to which the credit card is currently bound.

In some embodiments, the user's credit card application information is stored in the credit card database 132. Credit card application information can be but not limited to User identification code, phone number, project code, merchant's member identification code, etc. are related to the user's communication data and personal information.

In some embodiments, since the credit card application process is initiated through the merchant application 610 (for example, the mobile application of Quanlian Company), the credit card management server 100 associates the credit card application information with the member information of the merchant. For example, the information of this credit card will be annotated to be associated with Quanlian members.

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 account information of the card opening request.

In some embodiments, the credit card management server 100 integrates the aforementioned credit card application information and merchant's membership information into the credit card database 132 after verifying the card.

In some embodiments, the user can execute the opening procedure of the credit card after receiving the nuclear card notification. In the card opening process, the credit card management server 100 reads the information of the credit card related to the card opening request, and compares the user information in the credit card database 132 with these data. The credit card information can be but not limited to credit card number, expiration date, card face code, project code, birthday, mobile phone number, email address, Chinese name, etc.

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

In some embodiments, the user can open the card through the bank webpage or the bank mobile application. The user can select the credit card merchant to be bound before or after the card is opened. For example, if a user applies for a co-branded card in an American store (such as Costco), he can choose to use the card after opening the card. The credit card is bound to the member account of the American store or other merchants. In other embodiments, the user can also select the merchant to which the credit card can be bound during the process of filling in the information for applying for the credit card, and step S209 is omitted.

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

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

In some embodiments, the credit card management server 100 reads the merchant member information associated with the card opening request in the credit card database 132 to confirm the member identity information with 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 not limited to, the merchant's member identification code, merchant key value (such as phone number, such as mobile phone number, local phone number, Internet phone ) 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 in the electronic payment database 132 to complete the credit card opening procedure and merchant membership Credit card binding.

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

In this way, in step S212, the opening of the credit card and the binding of the credit card of the merchant member can be completed at the same time. When the electronic device 600 executes again When the merchant application 610 is executed, since the electronic payment database 134 has stored member information of the merchant and the corresponding credit card information, when the user operates the merchant application 610 on the electronic device 600, the merchant application 610 can send a credit card transaction request , 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, it will not The relevant information of the credit card is stored in the electronic payment database 134.

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

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

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 executing the electronic payment of the merchant application 610.

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

This case provides a server and method for digital card issuance and merchant e-wallet binding. The user can use the electronic device 600 to apply for the digital card online, and after the card is successfully opened, the merchant member’s credit card can be completed Bind. In this way, the trinity is integrated while providing online card application and merchant electronic payment binding.

Please refer to FIG. 3A to FIG. 3B, which illustrate a flowchart of a credit card management method according to other embodiments of the present case. The credit card management methods shown in Figure 3A to Figure 3B provide merchant members’ credit card binding without entering the credit card number information by themselves. In order to clearly explain the credit card management method in this case, please refer to Figure 1 together.

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, a Cathay Bank credit card digital banking application.

In step 304, the credit card management server 100 reads which merchant application 610 the credit card of the bank account is bound to.

In some embodiments, the credit card management server 100 can 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 of a bank account has a merchant tag (such as Quanlian Company), it means that the credit card has been bound to a 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 obtains all merchant applications in advance. If the processor 110 determines which merchant applications have completed the bank credit card binding, it will record it 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 the third merchant application and the fifth merchant application have not been bound, the binding list The three bound merchant apps and the two unbound merchant apps will be recorded.

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

In some embodiments, the electronic device 600 executes the banking mobile application 620 to display an operation interface. This operation interface contains multiple blocks or links to display bound merchant applications and unbound merchant applications. These blocks or links can be button boxes generated by a 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 a user wants to bind a credit card to a certain merchant application, he can click or select multiple blocks or links on the operation interface to generate a card binding request for the merchant application . For example, click on the button box that shows "bind to Quanlian PX Pay", and the bank mobile application 620 will generate a request for binding 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 executed. 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 sends user information of the bank account, 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 bank user 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 prompt message for joining a member is generated through the credit card management server 100 to be displayed on the electronic device 600 for the user to decide whether to register to join the member, so as to perform the registration process of joining the member. In some embodiments, the user can perform the operation of adding merchant members 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 the card binding terms.

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

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

In some embodiments, the user can click or select the merchant member information displayed on the bank 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, the electronic device 600 displays a message indicating failure to join the merchant member and/or failure to bind the credit card.

In step S320, the membership joining procedure is executed.

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

In step S322, the card binding procedure is executed.

In some embodiments, the electronic device 600 displays merchants available for binding credit cards. For example, the electronic device 600 displays merchants such as Quanlian, Yahoo, and Unicom. 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, expiration date, merchant member information, and electronic payment member identification code, into the electronic payment database 134. In some embodiments, after successfully binding the credit card, the credit card management server 100 sends 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 executing the electronic payment 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 the 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 the merchant application 610 of the electronic device 600 to verify. After the verification is successful, the electronic device 600 can execute the electronic payment of the merchant application 610. If the verification fails, it means that the credit card binding failed.

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

This case provides a server and method for binding merchant wallets and card binding management without a card. Users can manage personal credit cards by operating the bank mobile application 620 of the electronic device 600, and directly bind the credit cards on the operation interface. Card program, users can freely choose which credit cards are bound 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 Superpay and other electronic payments Or electronic wallet. In this way, the user does not need to enter the card number one by one to the electronic payment or electronic wallet to be used, and 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 the management of electronic wallets.

In some embodiments, when it is determined that the user of the bank is not a member of the merchant, the credit card management server 100 may also perform the step of quickly joining the member of the merchant. For example, when the user executes the bank mobile application 620 through the electronic device 600 and completes identity verification and login, the electronic device 600 executes the merchant application 610, and the user is asked whether he agrees to use the relevant information of the logged-in bank account To add a member as a merchant, for example, the credit card management server 100 transmits the user data of the credit card database 132 to the merchant database of the merchant server 700 through the application program interface to complete the merchant member joining process. In this way, the user can use the bank’s user information to quickly join the merchant’s membership by simply clicking on “Agree” on the bank mobile application 620, eliminating the hassle for the user to input data.

In some embodiments, the process of quickly joining a merchant member may be by logging into the bank mobile application 620 on the merchant application 610 The user account is used to bring the user data into the bank to the merchant application 610, so as to quickly join the merchant member.

The above content summarizes the features of several embodiments, so that those familiar with the technology can better understand the aspect of the case. Those familiar with this technology should understand that without departing from the spirit and scope of the case, the above content can be easily used as a basis for design or modification for other changes in order to implement the same purpose and/or realization of the embodiments introduced in this article Same advantage. The above content should be understood as an example of this case, and the 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 device

610: Merchant Application

620: Bank Mobile App

700: Merchant server

710: Merchant Database

Claims (10)

A credit card management server for electronic payment, including: A communication interface for receiving a card request; and A processor coupled to the communication interface, wherein the processor is configured to read a merchant tag and card user information requested by the card; The processor is configured to send the credit card information to a merchant database corresponding to the merchant label through the communication interface after activating a credit card with the card account information, so that an electronic device can read a merchant application program when running Obtain the credit card information in the merchant database to perform the electronic payment operation. The credit card management server described in claim 1, further comprising: A storage medium is coupled to the processor, wherein the storage medium is configured to store a credit card database, the credit card database having the card account information of the merchant tag. The credit card management server according to claim 2, wherein when the processor determines that the card account information is the same as a member information in the merchant database, the member information is associated with the card account information. For example, the credit card management server described in claim 3, wherein the electronic device executes a bank online credit card application webpage or the merchant application A program is used to issue the card application request, wherein the card application request includes at least one of a project code of the merchant label, a member identification code of the merchant label, and a member phone number. The credit card management server according to claim 4, wherein the processor activates the credit card according to a card opening request sent by the electronic device, so that the credit card information and the member information are integrated and stored in the credit card database. A credit card management server for electronic payment, including: A communication interface; and A processor coupled to the communication interface, wherein the processor is configured to query whether a merchant database corresponding to a merchant tag has a member profile corresponding to the card account profile; when it is determined that the member profile does not exist, the The processor receives a registration request through the communication interface, and then automatically executes a registration procedure of the merchant member; after completing the registration procedure, it determines whether the credit card of a bank account is bound to a merchant application, and when the processor When determining that the credit card of the bank account is not bound to the merchant application, the processor receives a binding request through the communication interface; The processor is further configured to compare whether a user profile of the bank account is consistent with a merchant membership profile of the merchant application according to the binding request, to determine whether the user profile matches the merchant membership profile. The materials are integrated and recorded into an electronic payment database. The credit card management server described in claim 6 further includes: A storage medium coupled to the processor, wherein the storage medium is configured to store the electronic payment database, which is used to record the bank account and the merchant application of the credit card bound to the bank account. The credit card management server according to claim 6, wherein the processor automatically generates a membership application data to a merchant server to automatically complete the registration process of the merchant membership information, wherein the membership application data includes Information about the bank account. The credit card management server according to claim 8, wherein the processor is further configured to record the merchant application to which the credit card of the bank account has been bound in a binding list. The credit card management server according to claim 9, wherein the processor is further configured to control an electronic device for executing the merchant application to perform identity verification after the credit card is bound to the merchant application, so as to enable The electronic payment.

Images