CN114971620A

CN114971620A - Card information management, apparatus, device, medium, and program product

Info

Publication number: CN114971620A
Application number: CN202210650641.6A
Authority: CN
Inventors: 刘晶; 李新印
Original assignee: Industrial and Commercial Bank of China Ltd ICBC
Current assignee: Industrial and Commercial Bank of China Ltd ICBC
Priority date: 2022-06-09
Filing date: 2022-06-09
Publication date: 2022-08-30

Abstract

The present disclosure provides a card information management that may be applied in the financial or other fields. The card information management includes: counting users corresponding to all cards, and establishing an account list; setting each account in the account list and all cards under the name of the account in a correlation manner, and setting a priority payment sequence of the cards; when a payment request is received, logging in a corresponding account, and completing payment based on a priority payment sequence, wherein the type of the payment request comprises payment through no card, payment through one of cards associated with the account, and payment through an account card established based on the account. The present disclosure also provides a card information management apparatus, a device, a storage medium, and a program product.

Description

Card information management, apparatus, device, medium, and program product

Technical Field

The present disclosure relates to the field of finance, specifically the field of financial information, and more specifically to card information management, apparatus, devices, media, and program products.

Background

With the development of banking business and the occupation of market demands, various banking card businesses are released by various banks, and different banking card issuing schemes, such as a certain joint card, a certain commemorative card and the like, appear based on different card issuing purposes, different partners or different functions, but each scheme aims at one entity banking card, so that the situation that a plurality of banking cards of the same bank exist in one user hand occurs, and the various cards not only cause interference and confusion to the card management card of the user, but also cause great waste to database resources of the bank.

Disclosure of Invention

In view of the foregoing, the present disclosure provides a card information management, apparatus, device, medium, and program product.

According to a first aspect of the present disclosure, there is provided a card information management including: counting users corresponding to all cards, and establishing an account list; setting each account in the account list and all cards under the name of the account in a correlation manner, and setting a priority payment sequence of the cards; when a payment request is received, logging in the corresponding account, and completing payment based on the priority payment sequence, wherein the type of the payment request comprises payment through no card, payment through one of the cards associated with the account, and payment through an account card established based on the account.

Optionally, each account in the account list is set in association with all cards in the name thereof, and setting a priority payment order of the cards includes: establishing the priority payment sequence based on the use frequency of each card, the credit of each card or the balance of each card; or setting the priority payment sequence according to the user requirement.

Optionally, when a payment request is received, logging in the corresponding account, and completing payment based on the priority payment order, where the type of the payment request includes payment by card-less payment, payment by one of the cards associated with the account, and payment by an account card established based on the account, and includes: when the type of the received payment request is through card-free payment or account card payment established based on an account, logging in the corresponding account; completing payment based on the priority payment order.

Optionally, when a payment request is received, logging in the corresponding account, and completing payment based on the priority payment order, where the type of the payment request includes payment by no card, payment by one of the cards associated with the account, and payment by an account card established based on the account, further including: logging in the card when the received payment request type is payment through one of the cards related to the account; logging in the account through the association of the card and the account; completing payment based on the priority payment order.

Optionally, counting users corresponding to all cards, and establishing an account list includes: and distinguishing the accounts in the account list by setting corresponding account numbers. Optionally, the method further comprises: receiving a card opening request of a user; judging whether the user has an account in the account list or not; adding a new card when the user does not have an account in the account list, adding a new account in the account list, and establishing the association between the new account and the new card; adding a new card when the user has an account in the account list, and establishing the association between the account and the new card; setting the priority payment order for all of the cards associated with the account.

Optionally, the method further comprises: receiving a card selling request of a user; judging whether the user has an account in the account list or not; deleting a specified card when the user has an account in the account list; adjusting a priority payment order for the remaining cards associated with the account.

Optionally, adjusting the payment sequence of the remaining cards associated with the account further includes: judging whether the account has an associated card or not; and if the account does not have the associated card, deleting the account from the account list.

Optionally, the method further comprises: receiving a user cancellation request of a user; judging whether the user has an account in the account list or not; and when the user has the account in the account list, deleting the account from the account list, and deleting all cards related to the account.

A second aspect of the present disclosure provides a card information management method apparatus, including: the account list establishing module is used for counting users corresponding to all the cards and establishing an account list; the association setting module is used for performing association setting on each account in the account list and all cards under the name of the account, and setting a priority payment sequence of the cards; and the payment module is used for logging in the corresponding account when a payment request is received, and completing payment based on the priority payment sequence, wherein the type of the payment request comprises payment through no card, payment through one of the cards associated with the account, and payment through an account card established based on the account.

A third aspect of the present disclosure provides an electronic device, comprising: one or more processors; a memory for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the card information management.

A fourth aspect of the present disclosure also provides a computer-readable storage medium having stored thereon executable instructions that, when executed by a processor, cause the processor to perform the above card information management.

The card information management method has at least the following advantages:

(1) the processing speed of the system is improved: in the traditional management mode of the card information, the data of all the cards are stored in the card list, and only no repeated accounts are stored in the account list, so that the data volume is reduced, and the data processing speed is increased.

(2) The user experience is improved: in the traditional management mode of card information, if a user applies for a plurality of cards, the user can consume the cards only by taking the corresponding entity card in the management process, and in the invention, the user can complete the management of all cards under the name of the user by logging in an account or logging in any card associated with the account.

Drawings

The foregoing and other objects, features and advantages of the disclosure will be apparent from the following description of embodiments of the disclosure, which proceeds with reference to the accompanying drawings, in which:

FIG. 1 schematically illustrates an application scenario diagram of card information management, apparatus, device, medium, and program product according to an embodiment of the present disclosure;

FIG. 2 schematically illustrates a flow diagram of a card information management method according to an embodiment of the disclosure;

FIG. 3 schematically illustrates a flow diagram of a card opening method of card information management according to an embodiment of the disclosure;

FIG. 4 schematically illustrates a flow chart of a method of card pinning for card information management according to an embodiment of the disclosure;

FIG. 5 schematically illustrates a flow chart of a method of card information management for a sales outlet, according to an embodiment of the present disclosure;

FIG. 6A schematically illustrates a diagram of a bank's universal card stock list, according to an embodiment of the disclosure;

FIG. 6B schematically illustrates an account list diagram according to an embodiment of the disclosure;

FIG. 7 is a block diagram schematically illustrating an apparatus of a card information management method according to an embodiment of the present disclosure; and

FIG. 8 schematically illustrates a block diagram of an electronic device suitable for implementing card information management according to an embodiment of the present disclosure.

Detailed Description

Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is illustrative only and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the disclosed embodiments. It may be evident, however, that one or more embodiments may be practiced without these specific details. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present disclosure.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.

All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It is noted that the terms used herein should be interpreted as having a meaning that is consistent with the context of this specification and should not be interpreted in an idealized or overly formal sense.

Where a convention analogous to "at least one of A, B and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B and C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).

It should be noted that the card information management method and apparatus of the present disclosure can be used in the financial field, and can also be used in any field other than the financial field.

In the technical scheme of the disclosure, the collection, storage, use, processing, transmission, provision, disclosure, application and other processing of the personal information of the related user are all in accordance with the regulations of related laws and regulations, necessary confidentiality measures are taken, and the customs of the public order is not violated.

An embodiment of the present disclosure provides a card information management method, including: counting accounts corresponding to all cards, and establishing an account list; setting each account in the account list and all cards under the name of the account in a correlation manner, and setting a priority payment sequence of the cards; when a payment request is received, logging in a corresponding account, and completing payment based on a priority payment sequence, wherein the type of the payment request comprises payment through no card, payment through one of cards associated with the account, and payment through an account card established based on the account.

Fig. 1 schematically illustrates an application scenario diagram of a card information management method and apparatus according to a regulation of the present disclosure.

As shown in fig. 1, according to the application scenario 100 of the embodiment, a network 104 is used to provide a medium of communication links between

terminal devices

101, 102, 103 and a server 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.

The

terminal devices

101, 102, 103 may be various payment devices having a payment function, or electronic devices having a web browsing function, including but not limited to smart phones, tablet computers, and the like.

The server 105 may be a server providing various services, such as a bank account background management server (for example only) providing support for users using the

terminal devices

101, 102, 103 payment platform. The background management server can process the received data such as the user request and the like and feed back the processing result to the terminal equipment. The background management server processes the card opening request, the card selling request, the customer selling request and the like sent by the electronic equipment and returns the processing result to the electronic equipment.

It should be noted that the card information management method provided by the embodiment of the present disclosure may be generally executed by the server 105. Accordingly, the card information management apparatus provided by the embodiment of the present disclosure may be generally disposed in the server 105. The card information management method provided by the embodiment of the present disclosure may also be executed by a server or a server cluster that is different from the server 105 and is capable of communicating with the

terminal devices

101, 102, 103 and/or the server 105. Accordingly, the card information management apparatus provided in the embodiment of the present disclosure may also be provided in a server or a server cluster different from the server 105 and capable of communicating with the

terminal devices

101, 102, and 103 and/or the server 105.

It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

The card information management method of the disclosed embodiment will be described in detail below with reference to fig. 2 to 6 based on the scenario described in fig. 1.

Fig. 2 schematically illustrates a flow chart of a card information management method according to an embodiment of the present disclosure.

As shown in fig. 2, the card information management method of the embodiment includes operations S210 to S230.

In operation S210, users corresponding to all cards are counted, and an account list is established.

According to an embodiment of the present disclosure, the card may be a bank card. Because a user often applies for a plurality of different types of cards in one bank, such as a deposit card, a credit card, and the like. When the bank stores card information, it is generally stored in a card list, as shown in fig. 6A. When a user consumes a certain card on a POS machine, the user needs to retrieve the current card from the card list, and the data size of the card list is enormous, so the retrieval speed is limited. In the embodiment of the disclosure, users corresponding to all cards are counted, and an account list is established. Each account in the account list corresponds to a holder of a card and there are no duplicate accounts in the account list.

Establishing the account list further comprises: and distinguishing the accounts in the account list by setting corresponding account numbers. For example, when an account generates a physical account card, an account number of the account card is generated based on a corresponding encoding rule, and when the account card is used for payment, the account is found by retrieving the account number on the account card in an account list; or when the user identity information is stored in the account, the corresponding account number is set based on the identity information of the user, the identity information comprises the identity card information, the mobile phone number and the like of the user, and the account number corresponds to the user identity information one to one, so that the user can find the corresponding account in an account list by using the identity card and the mobile phone number to carry out card-free payment.

The data volume of the established account list is smaller than that of the card list, when the user pays through the account, the corresponding account is retrieved from the account list, and the data processing speed is accelerated.

In operation S220, each account in the account list is set in association with all cards in the name thereof, and a priority payment order of the cards is set.

According to the embodiment of the present disclosure, as shown in fig. 6B, each account in the account list is set in association with a card under the user name corresponding to the account. And setting a priority payment order in the process of the association setting. The setting of the priority payment order may be a default setting based on each card use frequency, each card amount, or each card balance. When the rule of the priority payment sequence is card use frequency, the card with higher card use frequency is closer to the priority payment sequence, when the rule of the priority payment sequence is a card amount, the card with higher card amount is closer to the priority payment sequence, and when the rule of the priority payment sequence is a card balance, the card with higher card amount is closer to the priority payment sequence. For example, an account associated card has three cards: the card 1, the card 2 and the card 3 are used according to the frequency, the use frequency of the cards is the cards 1, the cards 2 and the cards 3, and when the priority payment sequence of the cards is set according to the use frequency, the higher the use frequency is, the higher the priority payment sequence of the cards is, the cards 1, the cards 2 and the cards 3 are. The priority payment order can be comprehensively set by integrating three aspects of the use frequency of each card, the credit of each card or the balance of each card. In addition, the priority payment sequence can be adjusted according to the user requirement. For example, an account associated card has three cards: card 1, card 2, according to the user's demand, arrange card 2's priority payment order first, the priority payment order of three cards at this moment is card 2, card 1.

In operation S230, when a payment request is received, logging in a corresponding account, and completing payment based on a priority payment order, wherein the type of the payment request includes payment through no card, payment through one of cards associated with the account, and payment through an account card established based on the account.

And when the type of the received payment request is payment without a card, searching whether an account exists from an account list according to the number corresponding to the user identity information, if the account exists, logging in the account through verification, and selecting the card from the cards related to the account based on the priority payment sequence to finish payment. For example, the account number corresponds to a mobile phone number of the user, when the card-free payment mode is a mobile phone number, the corresponding account number is searched in the account list according to the mobile phone number input by the user, when the account number is searched, user identity authentication is performed, when the user identity authentication passes, the account logs in, and payment is performed through cards in which the payment sequence is arranged at the first position in each card associated with the account.

And when the type of the received payment request is the payment through an account card established based on the account, searching in an account list based on the number of the account card, logging in the account corresponding to the account card, and selecting the card to complete the payment based on the priority payment sequence. When the card with the multiple cards combined into one is generated, the card number corresponds to the account number, so that when the card number is searched, whether the account corresponding to the card exists in the account list or not is searched through searching the card number. After the account is searched, the account is authenticated and logged in, and payment is carried out through the cards with the payment sequence arranged at the first position in the cards related to the account.

When the type of the received payment request is one of the card payment related to the account, the card is logged in, the account is logged in through the relation between the card and the account, and the bank card is selected to complete payment based on the priority payment sequence. When the user carries a card with him, the user can log in the account of the user by logging in the card, and select other cards under the account to pay.

Fig. 3 schematically illustrates a flow diagram of a card opening method of card information management according to an embodiment of the present disclosure.

In operation S310, a card-open request of a user is received.

In operation S320, it is determined whether the user has an account in the account list.

After receiving a card opening request of a user, one step of judging whether the user has an account before is needed. For example, when the account stores the user identity information, whether the user has an account is retrieved from the account list through the number corresponding to the identity information; when the account has the corresponding entity account card, the user searches whether the user has the account in the account list by inputting the number of the account card; when a user judges that the account list is summarized and accounts exist through a certain card, whether the card exists or not is searched in the card list, and when the card exists in the card list, the account related to the card necessarily exists.

In operation S330, when the user does not have an account in the account list, a new card is added, a new account is added in the account list, and an association of the new account with the new card is established.

In operation S340, when the user has an account in the account list, adding a new card, and establishing an association between the account and the new card;

in operation S350, a priority payment order for all cards associated with the account is set.

When the user has an account in the account list, the user adds new card information in the card list, establishes the association between the account and the new card, and adjusts the priority payment sequence of all bank cards associated with the account. For example, a user has an account, the account is associated with a card, a current user wants to apply for a new card, new card information is entered into a card list, the card is associated with the current account of the user, after the association, a default priority payment sequence of the new card and all the original cards is automatically generated based on information such as the balance, the amount and the like of the new card and the original cards, and the user can also arrange the priority payment sequence of the new card in the front by self-setting.

When the user does not have an account in the account list, the user adds new card information in the card list and adds a new account in the account list. And establishes an association and a priority payment order between the account and the new card. At this time, since the account is associated with only one card, the priority payment order of the new card is the highest.

Fig. 4 schematically illustrates a flow chart of a method of card pinning for card information management according to an embodiment of the disclosure.

At operation 410, a user's card-pinning request is received.

At operation 420, it is determined whether the user has an account in the account list.

At operation 430, the designated card is deleted when the user has an account in the account list.

At operation 440, when the user does not have an account in the list of accounts, a prompt is issued to "no such account exists".

At operation 450, the priority payment order of the remaining cards associated with the account is adjusted.

For example, card 1, card 2, and card 3 are associated with the user account, and the preferred payment order is card 1, card 2, and card 3. When the user wants to log off the card 1, and finds the account corresponding to the user in the account list, the association between the account and the card 1 is deleted, and the data of the card 1 in the card list is deleted. After the card 1 is deleted, the priority payment sequence of the card 2 and the card 3 is sequentially moved forward, and the priority payment sequence of the card 2 and the card 3 can be reset according to the user requirement.

Wherein the card-pinning method further comprises operations 460 through 470.

At operation 460, it is determined whether an associated card exists for the account.

At operation 470, if the account does not have an associated card, the account is deleted from the account list.

For example, a card 1 is associated with the user account. When the user wants to log off the card 1, and finds the account corresponding to the user in the account list, the association between the account and the card 1 is deleted, and the data of the card 1 in the card list is deleted. After the card 1 is deleted, the account name has no associated card, and the account can be directly cancelled, so that the data volume of the account list is reduced.

Fig. 5 schematically illustrates a flow diagram of a card information management sales method according to an embodiment of the present disclosure.

At operation 510, a customer cancellation request is received from a customer.

At operation 520, it is determined whether the user has an account in the account list.

At operation 530, when the user has an account in the account list, the account is deleted from the account list and all cards associated with the account are deleted.

At operation 540, when the user does not have an account in the account list, a prompt is issued to "no such account exists".

For example, card 1, card 2, and card 3 are associated under the user account. When the user wants to log off the account of the user, the data of the card 1, the card 2 and the card 3 in the stored card list are all deleted and the account is deleted after the corresponding account of the user is found in the account list.

Based on the card information management method, the disclosure also provides a card information management method and device. The apparatus will be described in detail below with reference to fig. 7.

Fig. 7 is a block diagram schematically illustrating a card information management method apparatus according to an embodiment of the present disclosure.

As shown in fig. 7, the card information management method apparatus 700 of this embodiment includes an account list establishing module 710, an association setting module 720, a payment module 730, a card opening module 740, a card selling module 750, and a card seller module 760.

The account list establishing module 710 is configured to count users corresponding to all cards, and establish an account list. In an embodiment, the account list establishing module 710 may be configured to perform the operation S210 described above, which is not described herein again.

The association setting module 720 is configured to perform association setting on each account in the account list and all cards in the name of the account, and set a priority payment order of the cards. In an embodiment, the association setting module 720 may be configured to perform the operation S220 described above, which is not described herein again.

The payment module 730 is configured to log in a corresponding account when a payment request is received, and complete payment based on a priority payment order, where the type of the payment request includes payment by no card, payment by one of cards associated with the account, and payment by an account card established based on the account. In an embodiment, the payment module 730 may be configured to perform the operations S310 to S350 described above, which are not described herein again.

The card-opening module 740 is used for processing a card-opening request of a user. In an embodiment, the payment module 730 may be configured to perform the operations S410 to S470 described above, which are not described herein again.

The card-pinning module 750 is used for processing a card-pinning request of a user. In one embodiment, the payment module 730 may be used to perform the operation S-seller request described above. In an embodiment, the payment module 730 may be configured to perform the operations S510 to S550 described above, which are not described herein again.

According to the embodiment of the present disclosure, any plurality of the account list establishing module 710, the association setting module 720, the payment module 730, the card opening module 740, the card selling module 750 and the seller module 760 may be combined into one module to be implemented, or any one of the modules may be split into a plurality of modules. Alternatively, at least part of the functionality of one or more of these modules may be combined with at least part of the functionality of the other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the account list establishing module 710, the association setting module 720, the payment module 730, the card opening module 740, the card selling module 750, and the card selling module 760 may be at least partially implemented as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented by hardware or firmware in any other reasonable manner of integrating or packaging a circuit, or implemented by any one of three implementations of software, hardware, and firmware, or by a suitable combination of any several of them. Alternatively, at least one of the account list establishing module 710, the association setting module 720, the payment module 730, the card opening module 740, the card swiping module 750, and the card seller module 760 may be at least partially implemented as a computer program module, which when executed, may perform the corresponding functions.

As shown in fig. 8, an electronic device 800 according to an embodiment of the present disclosure includes a processor 801 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)802 or a program loaded from a storage section 808 into a Random Access Memory (RAM) 803. The processor 801 may include, for example, a general purpose microprocessor (e.g., CPU), an instruction set processor and/or associated chipset, and/or a special purpose microprocessor (e.g., Application Specific Integrated Circuit (ASIC)), among others. The processor 801 may also include onboard memory for caching purposes. Processor 801 may include a single processing unit or multiple processing units for performing different acts of a method flow in accordance with an embodiment of the present disclosure.

In the RAM 803, various programs and data necessary for the operation of the electronic apparatus 800 are stored. The processor 801, the ROM 802, and the RAM 803 are connected to each other by a bus 804. The processor 801 performs various operations of the method flows according to the disclosed embodiments by executing programs in the ROM 802 and/or RAM 803. Note that the programs may also be stored in one or more memories other than the ROM 802 and RAM 803. The processor 801 may also perform various operations of the method flows according to the disclosed embodiments by executing programs stored in the one or more memories.

Electronic device 800 may also include input/output (I/O) interface 805, input/output (I/O) interface 805 also connected to bus 804, according to an embodiment of the present disclosure. Electronic device 800 may also include one or more of the following components connected to I/O interface 805: an input portion 806 including a keyboard, a mouse, and the like; an output section 807 including a signal such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 808 including a hard disk and the like; and a communication section 809 including a network interface card such as a LAN card, a modem, or the like. The communication section 809 performs communication processing via a network such as the internet. A drive 810 is also connected to the I/O interface 805 as necessary. A removable medium 811 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 810 as necessary, so that a computer program read out therefrom is mounted on the storage section 808 as necessary.

The present disclosure also provides a computer-readable storage medium, which may be contained in the apparatus/device/system described in the above embodiments; or may exist separately and not be assembled into the device/apparatus/system. The computer-readable storage medium carries one or more programs which, when executed, implement the method according to an embodiment of the disclosure.

According to embodiments of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, which may include, for example but is not limited to: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. For example, according to embodiments of the present disclosure, a computer-readable storage medium may include the ROM 802 and/or RAM 803 described above and/or one or more memories other than the ROM 802 and RAM 803.

Embodiments of the present disclosure also include a computer program product comprising a computer program containing program code for performing the method illustrated in the flow chart. When the computer program product runs in a computer system, the program code is used for causing the computer system to realize the item recommendation method provided by the embodiment of the disclosure.

The computer program performs the above-described functions defined in the system/apparatus of the disclosed embodiment when executed by the processor 801. The above described systems, devices, modules, units, etc. may be implemented by computer program modules according to embodiments of the present disclosure.

In one embodiment, the computer program may be hosted on a tangible storage medium such as an optical storage device, a magnetic storage device, or the like. In another embodiment, the computer program may also be transmitted in the form of a signal on a network medium, distributed, downloaded and installed via communication section 809, and/or installed from removable media 811. The computer program containing program code may be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.

In such an embodiment, the computer program can be downloaded and installed from a network through the communication section 809 and/or installed from the removable medium 811. The computer program, when executed by the processor 801, performs the functions defined in the system of the disclosed embodiment. The systems, devices, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.

In accordance with embodiments of the present disclosure, program code for executing computer programs provided by embodiments of the present disclosure may be written in any combination of one or more programming languages, and in particular, these computer programs may be implemented using high level procedural and/or object oriented programming languages, and/or assembly/machine languages. The programming language includes, but is not limited to, programming languages such as Java, C + +, python, the "C" language, or the like. The program code may execute entirely on the user computing device, partly on the user device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

It will be appreciated by persons skilled in the art that various combinations and/or combinations of features recited in the various embodiments of the present disclosure and/or in the claims can be made even if such combinations or combinations are not explicitly recited in the present disclosure. In particular, various combinations and/or combinations of the features recited in the various embodiments and/or claims of the present disclosure may be made without departing from the spirit or teaching of the present disclosure. All such combinations and/or associations are within the scope of the present disclosure.

The above describes embodiments of the present disclosure. However, these examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described separately above, this does not mean that the measures in the embodiments cannot be used in advantageous combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be devised by those skilled in the art without departing from the scope of the present disclosure, and such alternatives and modifications are intended to be within the scope of the present disclosure.

Claims

1. A card information management method, comprising:

counting users corresponding to all cards, and establishing an account list;

setting each account in the account list and all cards under the name of the account in a correlation manner, and setting a priority payment sequence of the cards;

when a payment request is received, logging in the corresponding account, and completing payment based on the priority payment sequence, wherein the type of the payment request comprises payment through no card, payment through one of the cards associated with the account, and payment through an account card established based on the account.

2. The card information management method according to claim 1, wherein setting each account in the account list in association with all cards in its name, and setting a priority payment order of cards comprises:

establishing the priority payment sequence based on the use frequency of each card, the credit of each card or the balance of each card; or

And setting the priority payment sequence according to the user requirements.

3. The card information management method according to claim 1, wherein when a payment request is received, logging in the corresponding account, and completing payment based on the priority payment order, wherein the type of the payment request includes payment by no card, payment by one of the cards associated with the account, and payment by an account card established based on the account, and the method includes:

when the type of the received payment request is payment through no card or payment through an account card established based on the account, logging in the corresponding account;

completing payment based on the priority payment order.

4. The card information management method according to claim 1, wherein when a payment request is received, the corresponding account is logged in, and payment is completed based on the priority payment order, wherein the type of the payment request includes payment by no card, payment by one of the cards associated with the account, payment by an account card established based on the account, and further comprising:

logging in the card when the type of the received payment request is one of the cards associated with the account for payment;

logging in the account through the association of the card and the account;

completing payment based on the priority payment order.

5. The card information management method according to claim 1, wherein the counting users corresponding to all cards, and the creating an account list includes:

and distinguishing the accounts in the account list by setting corresponding account numbers.

6. The card information management method according to claim 1, further comprising:

receiving a card opening request of a user;

judging whether the user has an account in the account list or not;

adding a new card when the user does not have an account in the account list, adding a new account in the account list, and establishing the association between the new account and the new card;

adding a new card when the user has an account in the account list, and establishing the association between the account and the new card;

setting the priority payment order for all of the cards associated with the account.

7. The card information management method according to claim 1, further comprising:

receiving a card selling request of a user;

judging whether the user has an account in the account list or not;

deleting a specified card when the user has an account in the account list;

adjusting a priority payment order for the remaining cards associated with the account.

8. The card information management method according to claim 7, wherein when the user has the account in the account list, deleting a card, and adjusting a payment sequence of the remaining cards associated with the account, further comprises:

judging whether the account has an associated card or not;

and if the account does not have the associated card, deleting the account from the account list.

9. The card information management method according to claim 1, further comprising:

receiving a user cancellation request of a user;

judging whether the user has an account in the account list or not;

and when the user has the account in the account list, deleting the account from the account list, and deleting all cards related to the account.

10. A card information management method and device comprises the following steps:

the account list establishing module is used for counting users corresponding to all the cards and establishing an account list;

the association setting module is used for performing association setting on each account in the account list and all cards under the name of the account, and setting a priority payment sequence of the cards;

and the payment module is used for logging in the corresponding account when a payment request is received, and completing payment based on the priority payment sequence, wherein the type of the payment request comprises payment through no card, payment through one of the cards associated with the account, and payment through an account card established based on the account.

11. An electronic device, comprising:

one or more processors;

a storage device for storing one or more programs,

wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the method of any of claims 1-9.

12. A computer readable storage medium having stored thereon executable instructions which, when executed by a processor, cause the processor to perform the method of any one of claims 1 to 9.