TW202205167A - 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 combine credit card payment to achieve electronic payment or electronic wallet functions.

Even though every mobile application can realize electronic payment or electronic wallet by credit card, however, the user needs 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 a solution to improve the convenience of use for the inconvenience of entering credit card information one by one in electronic payment or electronic wallet.

The purpose of this summary is to provide a simplified abstract of the present disclosure so that the reader can have a basic understanding of the content of the present case. This summary is not an exhaustive overview of the disclosure, and it is not intended to identify key/critical elements of the present embodiments or to delimit the scope of the present disclosure.

According to an embodiment of the present application, 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 a credit card with the card account information is activated. A merchant database enables an electronic device to read the credit card information in the merchant database when executing a merchant application, so as to perform the electronic payment operation.

According to another embodiment, a credit card management server for electronic payment is disclosed, comprising: 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; judging that when the member information does not exist, the processor receives a registration request through the communication interface, and automatically executes a registration procedure of the merchant member; after completing the After the registration process, determine 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, according to the binding request, compare whether a user information of the bank account is consistent with a merchant membership information of the merchant application to determine whether the user information is consistent with The merchant member information is integrated and recorded into an electronic payment database.

The following disclosure provides many different embodiments or examples for implementing different features of the present case. Specific embodiments of elements and arrangements are described below to simplify the present case. Of course, these examples are exemplary only and are not intended to be limiting. For example, the terms "first" and "second" are used to describe elements in this case, only to distinguish the same or similar elements or operations, and the terms are not used to limit the technical elements of this case, nor to Restricts the order or sequence of operations. In addition, reference numerals and/or letters may be repeated in each example herein, and the same technical term may be used with the same and/or different reference numerals in each embodiment. This repetition is for the purpose of brevity and clarity, and does not in itself indicate a relationship between the various embodiments and/or configurations discussed.

Please refer to FIG. 1 , which is a schematic diagram of a credit card management server 100 for electronic payment according to some embodiments of the present application. The credit card management server 100 may be a banking server, which receives, stores, manages and utilizes bank user data. As shown in FIG. 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 the credit card information of bank users and perform electronic payment services. For example, services such as credit card binding of 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 for storing credit card data, such as personal data 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 executing electronic payment, 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 capable of executing the merchant application program falls within the scope of this application. For example, the merchant application may be a banking 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 an online shopping mall or a mobile application of electronic payment can be executed on the electronic device 600, so that users can purchase items or Make electronic payments. For example, the merchant server 700 can be a Yahoo online shopping server, a full-link shopping server, a unified supermarket server, and the like. Correspondingly, the electronic device 600 may be installed with a Yahoo mobile application, a full-link mobile application, a unified supermarket application, etc., that is, 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 the mobile applications provided by the merchants to complete the electronic payment service.

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

In some embodiments, the electronic device 600 can be used to execute a banking mobile application of banking business and a mobile application provided by a merchant. When the user wants to use the mobile application provided by the merchant side to perform electronic payment, if the merchant side user does not have a credit card of the bank at this time, in addition to providing the user with credit card application service 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 at the same time when the banking business has completed the credit card verification and the new card is in the process of opening the card, so that the credit card information can be The user can complete the credit card binding of the merchant application 610 at the same time when the card is opened.

Please refer to FIG. 2 , which shows a flowchart of a credit card management method according to some embodiments of the present application. For a clear explanation of 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 application for credit card webpage.

It is worth mentioning that, in the embodiment in which step S201 is performed, 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, and another embodiment is provided in this case to apply for a credit card, as in step S202.

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

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

In some embodiments, the merchant application has a hyperlink (eg, 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 implemented as a subprogram of a bank mobile application program or a web application program.

In some embodiments, when a hyperlink is clicked to generate a card application request, the electronic device 600 will pop up a prompt message whether to agree to the personal information terms. After obtaining the user's consent to the personal information terms, the card application request and the data of agreeing to the personal information terms are simultaneously transmitted to the credit card management server 100 .

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

In step S204 , the user clicks 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, and this case is not limited to whether the user has membership. 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 execute 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, the credit card management server 100 reads a merchant label and a card account information in the card application request to For follow-up member data comparison.

In some embodiments, the user sends application information through the bank's credit card application webpage (step S201 ) or interfaces to the application webpage through the merchant application (step S202 ), and completes identity verification online. For example, the user performs one-time password (OTP) authentication 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 cardholder is a member of the merchant. In the embodiment in which it is determined that the cardholder is a member of the merchant, the determination 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 membership information (eg, merchant tag and membership number) with the card account 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 tag is Quanlian Company, query is made to the merchant server 700 of Quanlian Company.

In some embodiments, the merchant database 710 stores the member data of a plurality of merchants, such as the member data of Quanlian. The merchant server 700 compares the member information according to 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, 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 card account information may be, but not limited to, phone numbers, project codes, member identification codes, and the like.

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 the Quanlian Company.

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

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

In some embodiments, since the credit card application process is initiated through the merchant application 610 (eg, a mobile application of Quanlian Corporation), the credit card management server 100 associates the credit card application data with the merchant's member data. For example, the information of this credit card will be registered and associated with the All-Union member.

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 and stores the aforementioned credit card application data and the merchant's membership data in the credit card database 132 after the card is verified.

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

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

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

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 are inconsistent, execute S214.

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

In some embodiments, the merchant membership information associated with the card opening request may be, but not limited to, the merchant's membership identification code, merchant key value (eg, phone number, such as mobile phone number, local phone number, Internet phone number, etc.) ) 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 process and the merchant membership credit card binding.

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

In this way, in step S212, the opening of the credit card and the binding of the merchant member's credit card can be completed at the same time. When the electronic device 600 executes the merchant application 610 again, since the electronic payment database 134 already stores the merchant's membership information and the corresponding credit card information, when the user operates the merchant application 610 on the electronic device 600, the merchant application 610 A credit card transaction request can be sent, so that the electronic device 600 can directly debit the credit card transaction on the merchant application 610 , such as shopping on the mobile application of Quantum, 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 card opening process of the credit card, but the merchant member's credit card binding fails, that is, no 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 an 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 the identity verification before executing 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 the verification is successful, the electronic device 600 can execute the electronic payment function of the merchant application 610 .

This case provides a server and method for digital card-raising, card-opening and binding of merchant's e-wallet. The user can perform online digital card application by operating the electronic device 600, and after the card is successfully opened, the merchant member's credit card can be completed. bind. In this way, it integrates the trinity and provides online card application and electronic payment binding of merchants at the same time.

Please refer to FIG. 3A to FIG. 3B , which are flowcharts of a credit card management method according to other embodiments of the present application. The credit card management method shown in Figure 3A to Figure 3B provides that the merchant member's credit card can be bound without inputting the card number information of the credit card. For a clear explanation of 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 mobile banking 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 applications 610 the credit cards of the bank account are bound to.

In some embodiments, the credit card management server 100 may query the merchant membership 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 label of record (such as Quanlian), it means that the credit card has been bound to a merchant application (such as Quanlian's PX Pay application).

In step S306, a binding list is generated by the processor 110.

In some embodiments, processor 110 pre-fetches all merchant applications. If the processor 110 determines which merchant applications have completed the binding of bank credit cards, it records 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, the binding list will The three bound merchant apps and the two unbound merchant apps are 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. The UI contains multiple blocks or links to display bound and unbound merchant apps. 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 the credit card to some merchant applications, he can click or select multiple blocks or links in the operation interface to generate a card binding request to the merchant application. . For example, by clicking on the button box displaying "Bind to Quanlian PX Pay", the bank mobile application 620 will generate a card binding request for binding the credit card to Quanlian PX Pay.

In step S312 , the user information of the bank account is transmitted to the credit card management server 100 by the electronic device 600 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 transmits the 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 user of the bank is a merchant member. Next, the merchant server 700 will return the reply information of whether the merchant 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, in step S314, a registration request is received through the credit card management server 100. For example, a membership notification message is generated by 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 membership, so as to execute the membership registration procedure. In some embodiments, the user may perform an operation of adding a merchant member online on the electronic device 600 . For example, the merchant application of the electronic device 600 will receive a prompt message whether to add the membership and card binding terms.

In step S316, the processor 110 determines whether the agreement message for joining the merchant membership and the card binding 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 also agree to bind the card, step S320 is executed.

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

In step S318, the electronic device 600 displays a message of failure to join the merchant membership and/or failure to bind the credit card.

In step S320, the membership procedure is executed.

In some embodiments, in the membership procedure, the credit card management server 100 automatically generates a 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 the mobile phone number, to the merchant server 700 to automatically complete the registration process of the merchant member.

In step S322, the card binding procedure is executed.

In some embodiments, the electronic device 600 displays merchants that can bind credit cards. For example, the electronic device 600 displays merchants such as Quanlian, Yahoo, and Uni-President. 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 asks 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 procedure.

In some embodiments, the credit card management server 100 integrates and records credit card data, such as credit card number, expiration date, merchant membership information, and electronic payment membership identification code, into the electronic payment database 134 . In some embodiments, after the credit card management server 100 successfully binds the credit card, a success message is sent to the mobile banking application 620 of the electronic device 600 for display.

In step S328, the identity of the user 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 the identity verification before executing 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 the credit card, and transmits an activation request to the credit card management server 100 .

Next, 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 the verification is successful, the electronic device 600 can execute the electronic payment function of the merchant application 610 . If the verification fails, it means that the binding of the credit card fails.

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

This case provides a server and a method for card-free binding merchant wallet and card binding management. Users can manage personal credit cards by operating the banking mobile application 620 of the electronic device 600, and directly bind the credit card on the operation interface. 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 Chaohao Pay and other electronic payments or e-wallet. In this way, the user does not need to input the card numbers one by one to the electronic payment or electronic wallet to be used, and only needs to perform electronic payment for fast binding and/or unbinding of credit cards from the banking mobile application 620 of the electronic device 600 . or management of electronic wallets.

In some embodiments, when it is determined that the user of the bank is not a merchant member, the credit card management server 100 may further perform the step of quickly joining the merchant member. For example, when the user executes the banking mobile application 620 through the electronic device 600 and completes the authentication and login, the electronic device 600 will ask the user whether to agree to use the relevant information of the logged-in bank account when the electronic device 600 executes the merchant application 610 To add a member of the 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 process of adding a merchant member. In this way, as long as the user clicks consent on the bank mobile application 620, the user can use the bank's user information to quickly join the merchant's membership, eliminating the user's trouble of entering information.

In some embodiments, the procedure of quickly joining a merchant member may be through logging in the user account of the bank mobile application 620 on the merchant application 610, so as to bring in the user information of the bank to the merchant application 610, so as to realize the quick joining of the merchant. member.

The foregoing outlines features of several embodiments so that those skilled in the art may better understand aspects of the present case. Those skilled in the art will appreciate that the foregoing may readily be used as a basis for designing or modifying other variations for carrying out the same purposes and/or realizations of the embodiments described herein without departing from the spirit and scope of the present case. Same advantage. The above content should be construed as an example of this case, and its protection scope 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: Electronics 610: Merchant Apps 620: Banking Mobile Apps 700: Merchant Server 710: Merchant Database 800: Communication Network S201~S216, S302~S328: Steps

The following detailed description will facilitate a better understanding of aspects of the disclosure when read in conjunction with the accompanying drawings. It should be noted that the various features in the drawings have not necessarily been drawn to scale, as required by practice in the drawings. In fact, the dimensions of the various features may be arbitrarily increased or decreased for clarity of discussion. FIG. 1 is a schematic diagram of a credit card management server for electronic payment according to some embodiments of the present application. FIG. 2 shows a flowchart of a credit card management method according to some embodiments of the present application. 3A to 3B are flowcharts illustrating a method for managing a credit card according to other embodiments of the present application.

Domestic storage information (please note in the order of storage institution, date and number) without Foreign deposit information (please note in the order of deposit 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: Electronics

610: Merchant Apps

620: Banking Mobile Apps

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 includes a merchant label and card account information; and a processor coupled to the communication interface, wherein the processor is configured to read the merchant tag and the card account information of the card application request; The processor is configured to send the credit card information to a merchant database corresponding to the merchant tag through the communication interface after enabling a credit card with the card account information to bind the credit card, so that an electronic device executes A merchant application can read the credit card information in the merchant database to perform the electronic payment operation. The credit card management server as described in claim 1, further comprising: A storage medium coupled to the processor, wherein the storage medium is configured to store a credit card database having the card account information of the merchant tag. The credit card management server of claim 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 according to claim 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 label, At least one of a member identification code and a member phone number of the merchant label. 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 membership information are integrated and stored in the credit card database.

Images