Card management device and program

Abstract

To provide a card management device that is able to reliably increase the number of card users by allowing the users to place unique images of the users on cards.SOLUTION: A card management server 10 accepts an application for a card, with a uniquely-designed card image being registered according to an operation on a user terminal 20. If a card user is creditworthy, the card is issued and a digital card (normal card CD2) with a specific design is made available (displayable) on the user terminal 20. Then, the public usability of the registered card image is examined. When the card image is approved to be usable (OK), the card design of the digital card made available on the user terminal 20 is switched to the unique design, which is the registered card image, and an original card (digital card) CD1, which is a one-and-only card, is made available (displayable) on the user terminal 20, and an original card (physical card) CA1 is mailed.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] An embodiment of the present invention relates to a card management device and a program. [Background technology]

[0002] Conventionally, a card production support device has been devised that, when applying for a credit card, allows a user making an application to provide a card issuer with a unique image of the user, for example, a photograph of the user's pet, and enables the card issuer to issue a credit card with an original design with the user's unique image printed on the card face.

[0003] Cardholders have the option of using credit cards with their own personal images, such as their pets, printed on them. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2000-190669 [Non-patent literature]

[0005] [Non-Patent Document 1] Orient Corporation's corporate and IR information, [online], [searched December 5, 2023], Internet<URL:https: / / www.orico.co.jp / company / news / 2012 / 0207.html> Summary of the Invention [Problem to be solved by the invention]

[0006] Conventional card production support devices issue credit cards with original designs with a user's unique image printed on the face of the card, which provides a strong motivation for users to apply for the card, but the card will not be issued if the content of the image printed on the face of the card does not match predetermined standards.

[0007] The problem to be solved by the present invention is to provide a card management device and program that can reliably increase the number of card users by allowing users to place their own images on cards. [Means for solving the problem]

[0008] The card management device of the present invention comprises: A card management device having a communication function with a user terminal of a user, A process of storing the image transmitted from the user terminal in a storage unit; a process of issuing a first card having a first design that does not include the image to the user; The system is equipped with a control unit that executes a process of reviewing whether the image is suitable for public use based on pre-stored criteria for reviewing whether the image is a correct image that can be used publicly, and if the image is suitable for review, switching the first card issued to the user to a second card with a second design that includes the image. [Effects of the Invention]

[0009] According to the card management device of the present invention, it is possible to steadily increase the number of card users by allowing users to place their own images on the cards. [Brief explanation of the drawings]

[0010] [Figure 1] 1 is a schematic diagram showing the overall configuration of a card management system 1 according to an embodiment of the present invention. [Figure 2] FIG. 2 is a block diagram showing the configuration of a card management server 10. [Figure 3]12 is a diagram showing an example of the contents of card image examination criteria data 12p3E included in the card issuance application 12p3 of the card management server 10. FIG. [Figure 4] 12 is a diagram showing an example of the contents of image examination notification data 12p3R included in the card issuance application 12p3 of the card management server 10. FIG. [Figure 5] FIG. 2 is a block diagram showing the configuration of a user terminal 20. [Figure 6] 10 is a flowchart showing the original card application acceptance process of the card management server 10. [Figure 7] 10 is a diagram showing an example of screen transitions for generating and registering a card image IMC of an original design displayed on the user terminal 20 in accordance with the original card application acceptance process of the card management server 10. FIG. [Figure 8] 10A and 10B are diagrams showing an example of screen transitions for inputting personal identification information and user information displayed on the user terminal 20 in accordance with the original card application acceptance process of the card management server 10. [Figure 9] 10 is a flowchart showing an original card issuing process (part 1) of the card management server 10. [Figure 10] 10 is a flowchart showing the original card issuing process (part 2) of the card management server 10. [Figure 11] 10 is a flowchart showing an original card issuing process (part 3) of the card management server 10. [Figure 12] 10 is a diagram showing a state in which an email MR0 notifying the user that the image examination has been successful is displayed on the user terminal 20 in accordance with the original card issuance process (part 1) of the card management server 10. FIG. [Figure 13] 10 is a diagram showing a state in which an email MR1 for an image re-registration request (1) R1, which is also a notification that the image review was rejected, is displayed on the user terminal 20 in accordance with the original card issuance process (part 2) of the card management server 10. FIG. [Figure 14] 10 is a flowchart showing card usage handling processing of the card management server 10. [Figure 15]10 is a diagram showing a state in which a regular card (digital card) CD2 with a specific design is displayed on the user terminal 20 in accordance with the card usage handling process of the card management server 10. FIG. [Figure 16] 10 is a diagram showing a state in which an original card (digital card) CD1, which is a one-of-a-kind card, is displayed on the user terminal 20 in accordance with the card usage handling process of the card management server 10. FIG. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, an embodiment of the present invention will be described with reference to the drawings.

[0012] (Configuration of the embodiment) FIG. 1 is a schematic diagram showing the overall configuration of a card management system 1 according to an embodiment of the present invention.

[0013] The card management system 1 includes a card management server 10 (card management device) of a card issuing company, a user terminal 20 (user terminal) of a card user who applies for issuance of a card to the card issuing company or who is the user of a card issued by the card issuing company, and a credit information providing server 30 that provides the card user's credit information to the card management server 10.

[0014] The function of providing credit information by the credit information providing server 30 may be provided by the card management server 10.

[0015] Furthermore, the card management server 10 is not limited to a single server, but may be configured such that a plurality of servers work together to achieve the desired function.

[0016] The user terminal 20 consists of a terminal such as a smartphone, tablet terminal, or personal computer that has been registered with the card management server 10 as a terminal used by a card user, and has communication functions that enable it to communicate with the card management server 10 via a public communication network (Internet) N.

[0017] The user terminal 20 downloads, installs, and uses a card application / usage application 22p2 (see Figure 5) provided to the card user by the card company from a program server (here, an app store) (not shown) on the communication network (Internet) N.

[0018] The card management server 10 is communicatively connected to the member store terminals of member stores of cards issued by card issuers via a card payment online network (not shown).

[0019] In the card management system 1 of the embodiment, the card management server 10 has at least the following functions (a) to (l):

[0020] (a) A function for accepting card applications from the user terminal 20.

[0021] (b) When accepting a card application from the user terminal 20, a function to generate and register (store) a card image of the user's unique card design (original design) based on the image sent and uploaded from the user terminal 20 in accordance with the operation of the user terminal 20.

[0022] (c) When accepting a card application from the user terminal 20, a function to obtain the card user's credit information based on the personal identification information (bank account information, official identification information, etc.) and user information (name, date of birth, email address, etc.) entered from the user terminal 20, and determine whether the card user is creditworthy.

[0023] (d) If the card user is creditworthy, a card is issued to the card user, and information about the issued card [user ID (e.g., "app ID"), password, card number, card image (card image with original design), card design (information indicating "regular" or "original" ("regular" at the time of issue"), etc.] is associated with information about the card user (terminal device number, name, email address, telephone number, etc.) and information about card usage (card number, date and time of usage, name of store used, amount used, payment method, etc.) and managed in a database DB, and a function that enables the use (display) of a regular card (digital card) CD2 with a specific design indicating that the card image is under review on the user terminal 20.

[0024] In the embodiment, a normal card refers to a card rank that can be issued by the card management server 10, and corresponds to a "lower" rank general card when there are multiple ranks, such as a "lower" rank general card issued based on the credit check of the card user, a "middle" rank gold card issued after the credit check of the card user is also based on an income check, or a "higher" rank platinum card, but normal cards are not limited to "lower" rank cards.

[0025] (e) A function to determine whether or not an original design card image (image registered by the user terminal 20) generated in accordance with the operation of the user terminal 20 can be used publicly based on pre-set review criteria (card image review criteria data 12p3E: see Figure 3).

[0026] (f) If the card image registered by the user terminal 20 is permitted for public use (approved (OK)) (image review completed), the card design of the digital card that has been made available for use on the user terminal 20 is switched from “normal” to “original,” enabling the use (display) of an original card (digital card) CD1 with an original design card image on the user terminal 20, and also providing instructions to mail an original card (physical card) CA1, a one-of-a-kind card with an original design card image printed on it, to the card user.

[0027] (g) When the card image registered by the user terminal 20 cannot be used publicly (review not possible (NG)) (image review incomplete), a function to send an image re-registration request (1) R1 (see Figure 4) to the user terminal 20 by email, which is also an image review not possible notification containing the reason for the review not possible (NG) and a message encouraging the user to re-register (re-store) the card image (new card image).

[0028] (h) A function to re-determine whether or not the re-created card image (re-registered image) is suitable for public use in accordance with the card image review criteria data 12p3E (see Figure 3) each time an original design card image (new card image) is re-created in accordance with the operation of the user terminal 20 before a specific period (e.g., 15 days) for the final NG notice has elapsed since the first image review NG notice (image re-registration request (1) R1) was sent.

[0029] (i) A function to send an image re-registration request (2) R2 and an image re-registration request (3) R3 (see Figure 4) by email to the user terminal 20, respectively, when the card image re-registered by the user terminal 20 does not pass review (OK) after the first image review NG notice (image re-registration request (1) R1) is sent and the pre-set period for the second NG notice (e.g., "3 days") has passed, and when the pre-set period for the third NG notice (e.g., "14 days" (the day before the period for the final NG notice)) has passed.

[0030] (j) If the card image re-registered by the user terminal 20 does not pass review (OK) after the initial image review NG notice (image re-registration request (1) R1) is sent and a specific period (e.g., 15 days) for a predetermined final NG notice has elapsed, an image review incomplete notice R4 (see Figure 4) containing a message to the user terminal 20 stating that the image review has not been completed, a message to the effect that a regular card (physical card) CA2 with a regular design that does not include the re-registered card image will be mailed, and a message to the effect that the card image can be re-registered, and a function to instruct the regular card (physical card) CA2 to be mailed to the card user.

[0031] (k) After the image review incomplete notification R4 (see Figure 4) is sent to the user terminal 20, if the original design card image (re-registered image) regenerated in accordance with the operation of the user terminal 20 is approved for review (OK), the function processes the card design change (from "normal" to "original") and the instruction to mail the one-of-a-kind original card (physical card) CA1 free of charge for a pre-set free period (for example, "until the end of the following month") after the arrival of the normal card (physical card) CA2 to the card user is confirmed, and then processes the request for a fee after the free period.

[0032] (l) In response to a request for a digital card from the user terminal 20, if the card design of the information about the card managed in the database DB in association with information about the card user of the user terminal 20 is “original,” an original card (digital card) CD1 is displayed on the user terminal 20, and if the card design is “normal,” a normal card (digital card) CD2 with a specific design is displayed on the user terminal 20.

[0033] Note that the specific period (here, "15 days") from the sending of the initial image review NG notice (image re-registration request (1) R1) for the final NG notice, the period (here, "3 days" and "14 days") for repeated NG notices and the number of times for each, and the pre-set period (here, "until the end of the following month") during which the card design can be changed free of charge after the arrival of the regular card (physical card) CA2 to the card user is confirmed are all not limited, and may be set by the card issuing company at its discretion.

[0034] These predetermined periods may also be set based on, for example, Ebbinghaus' forgetting curve.

[0035] In this embodiment, the regular cards (digital card CD2 with a specific design and physical card CA2 with a standard design) are defined as the first card, and the original cards (digital card CD1 and physical card CA1) that are one-of-a-kind cards are defined as the second card. Also, the regular design or the specific design is defined as the first design, and the original design is defined as the second design.

[0036] <Configuration of card management server 10> FIG. 2 is a block diagram showing the configuration of the card management server 10. As shown in FIG.

[0037] The card management server 10 includes a control unit 11 (CPU: processor). The control unit 11 (CPU) may include multiple CPUs (processors).

[0038] The control unit 11 (CPU) controls the operation of each part of the circuit and executes various functions in accordance with a program pre-stored in a storage unit 12 such as a hard disk or flash memory, a program read by a storage medium reading unit 14 from an external storage medium 13 such as a CD-ROM and stored in the storage unit 12, or a program downloaded via a communication unit 15 from a web server (in this case, a program server) (not shown) on the communication network N and stored in the storage unit 12.

[0039] The storage unit 12 may be composed of one or more storage units.

[0040] The control unit 11 is connected to a memory unit 12, a recording medium reading unit 14, a communication unit 15 which is a communication interface with the communication network N, an input unit 16 such as a keyboard and a pointing device, and a display unit 17 via a system bus (Bus).

[0041] The storage unit 12 has a plurality of types of data storage areas, such as a program storage area 12P and a management data storage area (database) 12D.

[0042] The program storage area 12P stores a server system program 12p1 that controls the entire card management server 10, as well as a card application acceptance application 12p2, a card issuing application 12p3, and a card usage application 12p4.

[0043] The card application acceptance application 12p2 is a program that works in conjunction with the card application / usage application 22p2 (see Figure 5) installed on the user terminal 20 to accept card applications from card users in response to operations on the user terminal 20, and includes programs for executing the above-mentioned functions (a) and (b).

[0044] The card issuance application 12p3 is a program that works in conjunction with the card application / usage application 22p2 (see Figure 5) installed on the user terminal 20 to issue a card to the card user based on the details of the card application accepted from the user terminal 20, and includes programs for executing the above-mentioned functions (c) to (k).

[0045] The card issuing application 12p3 may include card image examination criteria data 12p3E (see FIG. 3) and image examination notification data 12p3R (see FIG. 4).

[0046] FIG. 3 is a diagram showing an example of the contents of the card image examination criteria data 12p3E included in the card issuing application 12p3 of the card management server 10. As shown in FIG.

[0047] The card image review criteria data 12p3E is data that indicates the criteria for reviewing whether an original design card image (registered image) generated upon acceptance of an application for an original card from the user terminal 20 is a correct image that can be used publicly.

[0048] A card image uploaded and registered from the user terminal 20 to the card management server 10 is determined to be a valid card image that can be officially used (approved (OK)) if it satisfies, for example, all eight criteria (1) to (8).

[0049] In card management server 10, the process of determining whether a card image registered from user terminal 20 is permitted for official use may be performed, for example, by an operator of card management server 10 operating input unit 16 to display the card image to be judged and a criteria confirmation window GE (see FIG. 3) listing each of the criteria (1) to (8) in card image examination criteria data 12p3E side by side on display unit 17, and the operator visually confirming the card image to be judged and each of the criteria (1) to (8) while inputting the confirmation result (check mark). Alternatively, the process may be performed by using image recognition processing to recognize one or more partial images included in the card image to be judged and automatically determining whether each of the criteria (1) to (8) is met.

[0050] FIG. 4 is a diagram showing an example of the contents of the image examination notification data 12p3R included in the card issuing application 12p3 of the card management server 10. As shown in FIG.

[0051] The image review notification data 12p3R is message (email content) data used to notify the user terminal 20 by email of the results (OK or NG) of the review of whether the card image uploaded and registered from the user terminal 20 to the card management server 10 is a correct card image that can be publicly used.

[0052] When the card image registered by the user terminal 20 is approved (OK) (image review completed), the card management server 10 sends an image review OK notification R0 to the user terminal 20, which includes a message, for example, that the image review has been completed and the original card (physical card) CA1 will be mailed.

[0053] In response to a case where the card image registered by the user terminal 20 is rejected (NG) (image review incomplete), the card management server 10 sends to the user terminal 20, for example, an image re-registration request (1) R1 including the reason for the rejection (NG) and a first message encouraging the user to re-register the card image, as well as a connection URL for re-registration.

[0054] In response to a request for image re-registration (2) R2 to the user terminal 20 when the card image registered by the user terminal 20 has failed to be reviewed (NG) and three days have passed since the initial transmission (notification) of the image re-registration request (1) R1, the card management server 10 will, for example, send the user terminal 20 an image re-registration request (2) R2 including the reason for the failure to be reviewed (NG), a second message that more strongly urges the user to re-register the card image than the first message, and a connection URL for re-registration.

[0055] In response to a case where the card image registered by the user terminal 20 has failed to be reviewed (NG) and 14 days have passed since the first image re-registration request (1) R1 was sent (notified), the card management server 10 will send to the user terminal 20 an image re-registration request (3) R3, which includes, for example, the reason for the failure to be reviewed (NG), a third message that more strongly urges the user to re-register the card image than the second message, and a connection URL for re-registration.

[0056] In response to a request for image re-registration (1) R1 being rejected (NG) and 15 days have passed since the initial request for image re-registration (1) R1 was sent (notified), the card management server 10 will send an image review incomplete notification R4 to the user terminal 20, which includes, for example, a message stating that the image review has not been completed, a message stating that a regular card (physical card) CA2 with a regular design will be mailed, and a message stating that the card image can be re-registered.

[0057] The reasons for rejection (NG) included in each of the image re-registration requests (1) R1, (2) R2, and (3) R3 are reflected, for example, by copying the content of the criteria for which the confirmation result (check mark) that the criteria were met was not entered in the card image review criteria data 12p3E (criteria confirmation window GE) shown in Figure 3.

[0058] The card usage application 12p4 is a program that works in conjunction with the card application / usage application 22p2 (see FIG. 5) installed on the user terminal 20 to display a digital card (original card CD1 or a regular card CD2 with a specific design) on the user terminal 20, calculates the payment amount for a specified card usage period determined by the monthly card usage deadline, for example, based on the card user's usage amount, the payment method for each usage (one-time payment / installment payment / revolving payment), a preset interest rate, etc., depending on the usage of the digital card or physical card (original card CA1 or regular card CA2), and displays the usage amount, the calculated payment amount, etc. on the card user's user terminal 20. The card usage application 12p4 includes a program for executing the above-mentioned functions (l: L).

[0059] The card application acceptance application 12p2, the card issuance application 12p3, and the card usage support application 12p4 naturally cooperate with each other, but may be configured as four or more application programs that further subdivide the functions they perform, or as a single program.

[0060] The management data storage area 12D stores card application management data 12d1, card user management data 12d2, card usage data 12d3, and the like.

[0061] The card application management data 12d1 stores various data such as the terminal device number, card image (original design), telephone number, personal identification information (bank account information, official identification information, etc.), card design (original), and user information (name, date of birth, email address, etc.) for each card user (user terminal 20) who applied for a card, in correspondence with each other.

[0062] The card user management data 12d2 stores various data such as the user ID (e.g., an identification number such as an "app ID"), password, card number, card image (original design), card design ("normal" or "original"), terminal device number, name, email address, telephone number, awarded points, and credit status for each card user (user terminal 20) to whom the card was issued, in correspondence with each other.

[0063] The credit status may include a credit status based on the credit information of the relevant card user provided by an external credit information providing server 30.

[0064] Card usage data 12d3 is the confirmed data of the card usage amount according to the card user's card usage, and is stored as credit data for each card user. The credit data includes the card number, date and time of use, name of the store used, amount used, payment method (one-time / installment / revolving), credit limit, and payment status (including delayed payments).

[0065] In the card management server 10 configured in this manner, the control unit 11 controls the operation of each part of the circuit in accordance with the instructions written in each program 12p1 to 12p4, and the software and hardware operate in cooperation to realize various functions including the original card application acceptance function (see Figure 6), the original card issuance function (see Figures 9 to 11), and the card usage support function (see Figure 14), as described in the operation explanation below.

[0066] <Configuration of user terminal 20> FIG. 5 is a block diagram showing the configuration of the user terminal 20. As shown in FIG.

[0067] The user terminal 20 includes a control unit 21 (CPU: processor). The control unit 21 (CPU) may include multiple CPUs (processors).

[0068] The control unit 21 (CPU) controls the operation of each part of the circuit and executes various functions in accordance with a program pre-stored in a storage unit 22 such as a flash memory, a program read by a storage medium reading unit 24 from an external storage medium 23 such as a memory card and stored in the storage unit 22, or a program downloaded via a communication unit 26 from a web server (in this case, a program server) (not shown) on the communication network N and stored in the storage unit 22.

[0069] The control unit 21 is connected to a memory unit 22, a recording medium reading unit 24, a communication unit 26 which is a communication interface with the communication network N, a touch panel display unit 25, an imaging unit 27 (camera), and the like via a system bus Bus.

[0070] The storage unit 22 has a plurality of types of data storage areas, such as a terminal data storage area 22R, a program storage area 22P, and a work data storage area 22W.

[0071] The terminal data storage area 22R stores various data (terminal device information) such as a terminal device number unique to the user terminal 20, an email address, and a telephone number.

[0072] The program storage area 22P stores a terminal system program 22p1 that controls the entire user terminal 20, as well as a card application / usage application 22p2 and the like.

[0073] The card application / usage application 22p2 is a program downloaded and installed from a program server (here, an app store) (not shown) on the communication network N based on terminal device information specific to the user terminal 20, and is a program that works in conjunction with the card management server 10 to generate and display display screens for each of the card applications, issuances, and usages.

[0074] After the card management server 10 issues the card to the user terminal 20, the card application / usage application 22p2 may include the data of the digital card (the original card CD1 or the regular card CD2 with a specific design).

[0075] The work data memory area 22W stores data 22w1 for generating a display screen, bitmap display data 22w2 for display on the touch panel display unit 25, and image data 22w3 obtained by capturing an image using the imaging unit 27 (camera).

[0076] As the display screen generating data 22w1, data for generating various screens transmitted from the card management server 10 is received by the user terminal 20 and stored.

[0077] The data for various screens stored as the display screen generating data 22w1 is written as display data 22w2 at the timing when each screen is to be displayed, and is displayed on the touch panel display unit 25.

[0078] In the user terminal 20 configured in this manner, the control unit 21 controls the operation of each part of the circuit in accordance with the instructions written in each program 22p1, 22p2, and the software and hardware operate in cooperation to realize various functions, including the display screen generation and display function, as described in the operation explanation below.

[0079] (Operation of the embodiment) Next, the operation of the card management system 1 according to the embodiment will be described.

[0080] <Original card application acceptance function> FIG. 6 is a flowchart showing the original card application acceptance process of the card management server 10.

[0081] FIG. 7 is a diagram showing an example of screen transitions for generating and registering a card image IMC of an original design to be displayed on the user terminal 20 in accordance with the original card application acceptance process of the card management server 10. In FIG.

[0082] FIG. 8 is a diagram showing an example of screen transitions for inputting personal verification information and user information displayed on the user terminal 20 in accordance with the original card application acceptance process of the card management server 10. In FIG.

[0083] When the user terminal 20 is connected to the card management server 10 via communication and an item related to an original card (also called an only one card) is selected on the home screen (not shown) displayed on the user terminal 20 by the card management server 10, the control unit 11 of the card management server 10 causes the touch panel display unit 25 of the user terminal 20 to display the original card (only one card) application screen GM0, which is the initial screen for accepting applications for an original card (only one card), as shown in Figure 7 (A), for example (step S1).

[0084] When the card user applying for a card touches the [Create a card] button B0 on the original card (one-of-a-kind card) application screen GM0 and the card management server 10 determines that there is a request to create an original card (step S2 (Yes)), the control unit 11 sequentially displays design creation screens (image file selection screen GM1 to card image completion screen GM5) for creating an original design card image on the touch panel display unit 25 of the user terminal 20, as shown in Figures 7(B) to 7(F), and creates an original design card image in accordance with the operation of the user terminal 20 (steps S3, S4).

[0085] That is, the card management server 10 first displays on the user terminal 20 an image file selection screen GM1, as shown in FIG. 7(B), which prompts the card user to upload a unique image to be used for the card image of the original design.

[0086] When the user operates the [Select File] button B1 and the [Next] button B2 on the image file selection screen GM1 to select, for example, a unique image of the card user, such as a photograph of the card user's pet, from the image data 22w3 of the user terminal 20, the card management server 10 causes the user terminal 20 to display an image confirmation screen GM2 containing the selected unique image P0, as shown in Figure 7(C).

[0087] When the unique image P0 selected by the card user is confirmed on the image confirmation screen GM2 and the [Next] button B2 is operated, the card management server 10 causes the user terminal 20 to display the card type selection screen GM3, which includes an option to select either a [landscape card] or a [portrait card], as shown in Figure 7(D).

[0088] When the card user selects the [Horizontal Card] or [Portrait Card] item on the card type selection screen GM3 and operates the [Next] button B2, the card management server 10 causes the user terminal 20 to display a card image trimming screen GM4, as shown in Figure 7 (E), which combines a trimming area Ap that prompts the card user to adjust the size and position to be used as the card image within the area of the unique image P0 selected by the card user.

[0089] On the card image trimming screen GM4, the card user operates the trimming area Ap to adjust the size and position within the area of the unique image P0 to be used as the card image, and when the [Next] button B2 is operated, the user terminal 20 displays the completed card image screen GM5, which shows the area cut out from the card user's unique image P0 by the trimming area Ap as an original design card image IMC, as shown in Figure 7(F).

[0090] On the card image completion screen GM5, when the card image IMC of the original design created by the card user is confirmed and the [Apply with this design] button B3 is operated, the card management server 10 registers (stores) the card image IMC of the original design created and uploaded by the card user in the card application management data 12d1.

[0091] As shown in Figures 7(G) and 7(H), the card management server 10 sequentially displays a screen switching message screen GM6 and an image transmission completion screen GM7 on the user terminal 20 to inform the card user that the creation and upload (registration) of the original design card image IMC has been completed.

[0092] In this way, when the upload (registration) of the original design card image IMC created in accordance with the operation of the user terminal 20 is completed in the card management server 10 (step S5 (Yes)), the control unit 11 downloads the card application / usage application 22p2 to the user terminal 20, starts it, and displays the home screen GA0 of the card application / usage application 22p2 as shown in Figure 8 (A) (step SA).

[0093] As shown in Figure 8(B), the control unit 11 displays an identity verification selection screen GA1 on the user terminal 20 to allow the card user to select a method of identity verification, and allows the card user to select, for example, whether to verify identity based on bank account information, or based on an official photo ID and an image of the card user's own face taken by the user terminal 20.

[0094] When the card user selects a method of identity verification (bank account information or official ID with photograph) on the identity verification selection screen GA1, the card management server 10 causes the user terminal 20 to sequentially display multiple identity verification screens (not shown) that prompt the card user to sequentially input the identity verification information that needs to be obtained according to the selected identity verification method (step S6).

[0095] When the card user's personal identification information is entered according to multiple personal identification screens (not shown) displayed on the user terminal 20 (step S7 (Yes)), the card management server 10 registers the entered personal identification information in the card application management data 12d1.

[0096] Next, the card management server 10 sequentially displays on the user terminal 20 a user information input screen GA2 for allowing the card user to input the card user's user information (such as name, date of birth, and email address) and a user information confirmation screen GA3 for allowing the card user to confirm the user information entered according to the user information input screen GA2, as shown in Figures 8(C) and 8(D) (step S8).

[0097] When the user information entered by the card user is confirmed on the user information confirmation screen GA3 and the [Confirm details and apply] button B4 is operated (step S9 (Yes)), the card management server 10 registers the confirmed user information in the card application management data 12d1 and displays an application completion screen GA4 on the user terminal 20, including a message that the card application has been accepted, as shown in Figure 8 (E) (step S10).

[0098] As a result, the card image of the original design created by the card user, the card user's personal identification information, and the card user's user information are associated with the terminal device information of the user terminal 20 and registered in the card application management data 12d1 of the card management server 10, thereby completing the acceptance of the original card (one-of-a-kind card).

[0099] <Original card issuing function> FIG. 9 is a flowchart showing the original card issuing process (part 1) of the card management server 10.

[0100] FIG. 10 is a flowchart showing the original card issuing process (part 2) of the card management server 10.

[0101] FIG. 11 is a flowchart showing the original card issuing process (part 3) of the card management server 10.

[0102] FIG. 12 is a diagram showing a state in which the email MR0 of the image examination OK notification R0 is displayed on the user terminal 20 in accordance with the original card issuance process (part 1) of the card management server 10.

[0103] FIG. 13 is a diagram showing a state in which the email MR1 of the image re-registration request (1) R1, which is also a notification that the image review was rejected, is displayed on the user terminal 20 in accordance with the original card issuance process (part 2) of the card management server 10.

[0104] The control unit 11 of the card management server 10 obtains the credit information of a card user who has completed an application for an original card (one-of-a-kind card) registered in the card application management data 12d1 from the credit information providing server 30 based on, for example, personal identification information and user information, and determines whether the card user is eligible for credit (step S12).

[0105] When it is determined that a card user who has applied for an original card (one-of-a-kind card) is creditworthy (step S12 (Yes)), the control unit 11 generates and registers card user management data 12d2 (user ID, password, card number, card image (original design), card design (here, "normal"), terminal device number, name, email address, telephone number, etc.) of the card user who has been determined to be creditworthy based on the card application management data 12d1 (terminal device number, card image (original design), telephone number, personal identification information, card design (original), user information, etc.), and executes the process of issuing a card to the card user (step S13).

[0106] The control unit 11 sends a notification of the issuance of the digital card, including a message indicating that a digital card (a regular card CD2 with a specific design) (see Figures 1 and 15(B)) has been issued, via email to the user terminal 20 of the card user to whom the card was issued (step S14).

[0107] As a result, a card user who has applied for an original card can display the normal card (digital card) CD2 on the user terminal 20 and use it immediately after it is determined that the card user is creditworthy.

[0108] On the other hand, if it is determined that the card user who applied for an original card (one-of-a-kind card) is not authorized (step S12 (No)), the control unit 11 sends an issuance denial notice to the user terminal 20, including a message stating that the card cannot be issued, according to, for example, the email address of the user terminal 20 that applied for the card registered in the card application management data 12d1 (step S15).

[0109] When a card user who has applied for an original card (one-of-a-kind card) is determined to be creditworthy and a digital card (a regular card CD2 with a specific design) (see Figure 15(B)) is issued (steps S12 to S14), the control unit 11 of the card management server 10 examines the card image of the original design registered in the card user management data 12d2 based on the card image examination criteria data 12p3E (see Figure 3) to determine whether it is a valid card image eligible for public use (step S16), and determines whether the examination is successful (step S17).

[0110] Here, if it is determined that the card image of the original design registered in the card user management data 12d2 is OK for review (image review completed) (step S17 (Yes)), the control unit 11 switches the card design registered in the card user management data 12d2 from "normal" to "original" (step S18).

[0111] As a result, a card user who has applied for an original card can display the original card (digital card) CD1, which is a one-of-a-kind card, on the user terminal 20 and use it.

[0112] Based on the image review notification data 12p3R (see Figure 4), the control unit 11 sends an email MR0 containing an image review OK notification R0 to the user terminal 20, including a message indicating that the image review has been completed and the original card (physical card) CA1 will be mailed, as shown in Figure 12 (step S19).

[0113] The control unit 11 instructs the card user to mail an original card (physical card) CA1 on which an image of a card with an original design is printed (step S20).

[0114] This allows the card user to display and use the original card (digital card) CD1, which is a one-of-a-kind card, on the user terminal 20, and also to use the original card (physical card) CA1, which is a one-of-a-kind card that has been mailed to him / her.

[0115] On the other hand, if it is determined that the original design card image registered in the card user management data 12d2 is not eligible for review (NG) (image review incomplete) (step S17 (No)), the control unit 11 sends an email MR1 to the user terminal 20 (step S21) containing an image re-registration request (1)R1 (re-storage request), which is also an image review NG notification and includes, for example, a first message indicating the reason for the NG review and encouraging the re-registration (re-storage) of the card image (new card image), and a connection URL for re-registration, based on the image review notification data 12p3R (see Figure 4), as shown in Figure 13, for example.

[0116] As a result, a card user who has applied for an original card can confirm, based on the email MR1 of the image re-registration request (1) R1, that the card image created by the card user himself / herself has been rejected (NG) and the reason for this, and can then attempt to recreate an original design card image that will be accepted (OK) and re-register it.

[0117] The control unit 11 determines whether a predetermined specific period of "15 days" for the final NG notification has elapsed since the sending of the email MR1 of the image re-registration request (1) R1, which is also the initial image review NG notification (step S22).

[0118] When it is determined that the period of "15 days" for the final NG notification has not elapsed since the sending of the email MR1 of the image re-registration request (1) R1, which is also the initial image review NG notification (step S22 (No)), for example, as shown in Figure 13, when the connection URL for re-registration included in the email MR1 of the image re-registration request (1) R1 displayed on the user terminal 20 is specified, the control unit 11 determines that a request for re-registration of the card image has been made from the user terminal 20 (step S23 (Yes)).

[0119] Then, the control unit 11 causes the touch panel display unit 25 of the user terminal 20 to sequentially display the design creation and registration screens (image file selection screen GM1 to image transmission completion screen GM7) for re-creating and re-registering a card image with the original design, as shown in Figures 7(B) to 7(H), and recreates a card image with the original design in accordance with the operation of the user terminal 20 (steps S24, S25).

[0120] The control unit 11 erases or overwrites the card image that is currently determined to be unacceptable (NG) in the card user management data 12d2, and re-registers the regenerated card image (step S26).

[0121] When a card image of an original design registered in the card user management data 12d2 is recreated and re-registered in response to an operation of the user terminal 20 (step S26 (Yes)), the control unit 11 again examines the re-registered card image based on the card image examination criteria data 12p3E (see Figure 3) to determine whether it is a correct card image eligible for public use (step S16), and determines whether the examination is successful (step S17).

[0122] When the control unit 11 determines that the re-registered card image with the original design is OK for review (image review completed) (step S17 (Yes)), as described above, it switches the card design from "normal" to "original" (step S18), and as shown in Figure 12, it sends an email MR0 notifying the user that the image review is OK R0 to the user terminal 20 (step S19), and instructs the card user to mail the original card (physical card) CA1, which is a one-of-a-kind card, to the card user (step S20).

[0123] This allows card users to switch between the regular card (digital card) CD2 and the original card (physical card) CA1, which is a one-of-a-kind card bearing a re-registered card image of the original design.

[0124] Furthermore, if the control unit 11 determines again that the re-registered original design card image is not eligible for review (NG) (image review incomplete) (step S17 (No)), it again sends an email MR1 containing an image re-registration request (1) R1, which is also a notification that the image review has been rejected, to the user terminal 20 (step S21), as shown in Figure 13 above.

[0125] When the control unit 11 determines that the period of "15 days" for the final NG notification has not elapsed since the sending of the email MR1 of the image re-registration request (1) R1, which is also the initial image review NG notification (step S22 (No)), and the original design card image has not been re-registered, or the original design card image has been re-registered but has repeatedly been determined to be NG (step S23 (No)), and determines that three days have elapsed since the sending of the email MR1 of the initial image re-registration request (1) R1 (step S27 (Yes)), the control unit 11 sends to the user terminal 20 an email MR2 of the image re-registration request (2) R2 (not shown) which includes, for example, the reason for the NG review and a second message that is more strongly urging the user to re-register the card image than the first message, and a connection URL for re-registration, based on the image review notification data 12p3R (see Figure 4) (step S28).

[0126] As a result, a card user who has applied for an original card can receive an email MR2 (not shown) for an image re-registration request (2) R2 at an early stage after the card image is determined to be unsuccessful (NG), regardless of whether or not the card user has confirmed the email MR1 for an image re-registration request (1) R1, which is also the image review NG notification shown in Figure 13.The card user can confirm that the card image they created themselves has been unsuccessful (NG) and the reason for this, and can attempt to recreate and re-register a card image with an original design that will pass the review (OK).

[0127] If the control unit 11 determines that the period of 15 days for the final NG notice has not elapsed since the sending of the email MR1 of the image re-registration request (1) R1, which is also the initial image review NG notice (step S22 (No)), and if the original design card image has not been re-registered, or if the original design card image has been re-registered but has repeatedly been determined to be NG (step S23 (No)), and if it determines that 14 days, the day before the period for the final NG notice, have elapsed since the sending of the email MR1 of the initial image re-registration request (1) R1 (step S29 (Yes)), the control unit 11 sends to the user terminal 20 an email MR3 (not shown) of the image re-registration request (3) R3, which includes, for example, the reason for the NG review and a third message that is more strongly urging the user to re-register the card image than the second message, and a connection URL for re-registration, based on the image review notification data 12p3R (see Figure 4) (step S30).

[0128] As a result, a card user who has applied for an original card can receive an email MR3 (not shown) for an image re-registration request (3) R3 just before the 15-day period for the final NG notice expires, regardless of whether or not they have confirmed the email MR1 for image re-registration request (1) R1, which is also the image review NG notice shown in Figure 13, and the email MR2 (not shown) for image re-registration request (2) R2, which is sent three days after the initial NG notice.The card user can then confirm that the card image they created themselves has failed to pass the review (NG) and the reason for this, and attempt to recreate a card image with an original design that will pass the review (OK) and re-register it.

[0129] After this, if the control unit 11 determines that the period of "15 days" for the final NG notice has elapsed since the sending of the email MR1 of the image re-registration request (1) R1, which is also the initial image review NG notice (step S22 (Yes)), while the original design card image has not been re-registered (step S23 (No)), or while the original design card image has been re-registered but has been determined to be repeatedly unreviewable (NG) (step S17 (No)), the control unit 11 sends to the user terminal 20 an email MR4 (not shown) of an image review incomplete notice R4, which includes, for example, a message that the image review has not been completed, a message that a regular card (physical card) CA2 with a regular design will be mailed, and a message that the card image can be re-registered (steps S31, S32), based on the image review notification data 12p3R (see Figure 4).

[0130] The control unit 11 instructs the regular card (physical card) CA2 with the regular design to be mailed to the card user (step S33).

[0131] As a result, even if the card user is unable to use the original card (digital card) CD1 and original card (physical card) CA1, which are one-of-a-kind cards bearing an image of a card with an original design, because the card image cannot be reviewed (NG), the card user can immediately display and use the regular card (digital card with a specific design) CD2 on the user terminal 20 once it is determined that the card user is creditworthy, and can also use the regular card (physical card with a regular design) CA2 that has been mailed to the card user.

[0132] After this, for example, if the user terminal 20 re-registers an original design card image that passes the review (OK) to the card management server 10 based on the connection URL for image re-registration notified to the user terminal 20 by email from the card management server 10 (step S34 (Yes)), the control unit 11 determines whether it is within a pre-set free period (for example, "until the end of the following month") since the information indicating the arrival of the regular card (physical card) CA2 that was instructed to be mailed in step S33 was acquired (confirmed) (step S35).

[0133] If the control unit 11 determines that the free period is in progress (step S35 (Yes)), it processes the change in card design (from "normal" to "original") and the instruction to mail the original card (physical card) CA1 free of charge (step S36), and if it determines that the free period has passed (step S35 (No)), it processes the change in card design (from "normal" to "original") and the instruction to mail the original card (physical card) CA1 for a fee (step S37).

[0134] As a result, even if a card user who has applied for an original card has not noticed the email MR1 of image re-registration request (1) R1, which is also a notification that the image review has been rejected, the email MR2 (not shown) of image re-registration request (2) R2 three days after the initial rejection notification, or the email MR3 (not shown) of image re-registration request (3) R3 fourteen days after the initial rejection notification, and the period of "15 days" for the final rejection notification has passed, the card user can re-register an original design card image that passes review (OK) free of charge from the user terminal 20 to the card management server 10 within the preset free period, switch the card design (from "normal" to "original"), obtain the original card (digital card) CD1 on the user terminal 20, and receive the original card (physical card) CA1 by mail.

[0135] <Card usage support function> FIG. 14 is a flowchart showing the card usage handling process of the card management server 10.

[0136] FIG. 15 is a diagram showing a state in which a regular card (digital card) CD2 with a specific design is displayed on the user terminal 20 in accordance with the card usage handling process of the card management server 10. As shown in FIG.

[0137] FIG. 16 is a diagram showing a state in which an original card (digital card) CD1, which is a one-of-a-kind card, is displayed on the user terminal 20 in accordance with the card usage handling process of the card management server 10. In FIG.

[0138] When the card application / usage application 22p2 is launched on the user terminal 20 and the main menu GC of the card application / usage application 22p2 is displayed on the touch panel display unit 25 as shown in FIG. 15(A) or FIG. 16(A) (step S41), if the [Digital Card] icon X on the main menu GC is touched to use a digital card, the control unit 11 of the card management server 10 determines that there is a request to use a digital card (step S42).

[0139] Then, the control unit 11 of the card management server 10 determines whether the card design (information indicating "regular" or "original") registered in the card user management data 12d2 in association with the user ID or terminal device information of the user terminal 20 is "regular" or "original" (step S43).

[0140] Here, since the card user of the user terminal 20 has already been determined to be creditworthy, when a digital card with a specific design (regular card CD2) is issued (see steps S12 to S14 in Figure 9), if the card image registered in the card user management data 12d2 has not yet been determined to be OK (see step S17 (No) in Figure 9), the control unit 11 determines that the card design registered in the card user management data 12d2 is "regular" (step S43 (regular)).

[0141] The control unit 11 then displays a digital card screen GD on the touch panel display unit 25 of the user terminal 20, as shown in Figure 15 (B), which displays a regular card CD2, which is a digital card with a specific design, allowing the card user to use the regular card (digital card) CD2 (step S45).

[0142] On the other hand, for example, when the card image registered in the card user management data 12d2 is determined to be OK and the card design is switched from "normal" to "original" (see step S17 (Yes) → S18 in Figure 9), the control unit 11 determines that the card design registered in the card user management data 12d2 is "original" (step S43 (original)).

[0143] The control unit 11 then displays the digital card screen GD, which displays the original card CD1 (one-of-a-kind card), a digital card with an original design, on the touch panel display unit 25 of the user terminal 20, as shown in Figure 16 (B), allowing the card user to use the original card (digital card) CD1 (step S44).

[0144] That is, a card user who has applied for an original card can display and use a regular card (digital card with a specific design) CD2 on the user terminal 20 as soon as the card management server 10 determines that the application is creditworthy, and can also display and use an original card (digital card) CD1, which is a one-of-a-kind card that has been switched from the regular card (digital card with a specific design) CD2, on the user terminal 20 as soon as the card image registered with the application is determined to be acceptable (OK).The card user can also use an original card (physical card) CA1, which is a one-of-a-kind card that has been mailed to them.

[0145] (Summary of the embodiment) According to the card management system 1 of the embodiment, the card management server 10 uploads and registers (stores) a card image of a card user's unique card design (original design) in response to the operation of the user terminal 20, and when the card application is accepted, it determines the card user's creditworthiness, and if creditworthy, issues the card and makes a digital card (normal card (digital card) CD2) (first card) of a specific design available (displayed) on the user terminal 20.

[0146] The card management server 10 then examines the registered card image to determine whether it is suitable for public use, and if it determines that it is acceptable (OK), it switches the card design of the digital card that has been made available (displayable) on the user terminal 20 from "normal" (here, a specific design) to "original" (the original design that is the registered card image), makes the one-of-a-kind original card (digital card) CD1 (second card) available (displayable) on the user terminal 20, and mails the original card (physical card) CA1 (second card).

[0147] If the card management server 10 determines that a registered card image is not acceptable for review (NG), it sends an image re-registration request (1) R1 (re-storage request) to the user terminal 20 by email, which includes the reason for the non-acceptance of review (NG) and a message encouraging the user to re-register (re-store) the card image. Until a specific period (here, "15 days") for a predetermined final NG notification has elapsed, the card management server 10 repeatedly reviews the re-registered card image each time it is re-registered after being recreated by the user terminal 20. If the card image is acceptable for review (OK), it switches the card design of the digital card that has been made available (displayable) on the user terminal 20 from "normal" to "original," makes the one-of-a-kind original card (digital card) CD1 available (displayable) on the user terminal 20, and mails the original card (physical card) CA1.

[0148] As a result, even if a card user who applied for an original card has their card image registered with their application rejected (NG), they can confirm the rejection and the reason for it and re-register a card image that will be accepted (OK), and they can continue to use the regular card (digital card with a specific design) CD2 until it is accepted (OK).As soon as it is accepted (OK), they can use the original card (digital card) CD1, which is the one-of-a-kind card that has been switched from the regular card (digital card) CD2.

[0149] In addition, whenever a card image re-registered by the user terminal 20 does not pass review (OK) and multiple preset periods for NG notification (here, "3 days" and "14" days) have elapsed, the card management server 10 sends an image re-registration request (here, image re-registration requests (2) R2 and (3) R3) by email to the user terminal 20, which includes the reason for the NG review and a message urging the user to re-register the card image.

[0150] As a result, card users who have applied for an original card can repeatedly receive image re-registration requests (2)R2 and (3)R3 after their card image has been determined to be unacceptable (NG), regardless of whether they have confirmed the image re-registration request (1)R1, which is also the initial NG notice, and can re-register a card image that will be approved (OK).

[0151] Furthermore, if the card image re-registered by the user terminal 20 does not pass review (OK) and a specific period (here, "15 days") for a preset final NG notification has elapsed, the card management server 10 will email an image review incomplete notification R4 to the user terminal 20, which includes a message stating that the image review has not been completed and that the card image can be re-registered, and will mail a regular card (physical card) CA2 (first card) with a regular design to the card user.

[0152] If the card image re-registered by the user terminal 20 is approved (OK) within a pre-set free period (here, "until the end of the following month") after the regular card (physical card) CA2 is mailed to the card user, the card management server 10 performs the process of switching the card design to the original design and the process of mailing the one-of-a-kind original card (physical card) CA1 free of charge, and after the free period, performs these processes for a fee.

[0153] As a result, even if a card user who has applied for an original card has passed the period for the final NG notification (here, "15 days") without noticing any of the image re-registration requests (1)R1 to (3)R3 repeatedly sent from the card management server 10, the card user can still use the regular card CD2, which is a digital card with a specific design, and the regular card CA2, which is a physical card with a regular design, and re-register a card image that passes review (OK) free of charge within the pre-set free period, and can obtain the original card (digital card) CD1 on the user terminal 20 by switching the card design, and receive the original card (physical card) CA1 by mail.

[0154] By accepting applications for original cards, which are one-of-a-kind cards, the card issuer, who is the administrator of the card management server 10, can issue a regular card (digital card with a specific design) CD2 if the card user's credit is approved, even if the card image with an original design based on the card user's unique image registered with the application is rejected (NG), and can continuously encourage the card user to re-register a card image that is approved (OK), thereby ensuring the switch to one-of-a-kind original cards (digital card) CD1 and original card (physical card) CA1.

[0155] Therefore, according to the card management system 1 of the embodiment, it is possible to steadily increase the number of card users by allowing users to place their own images on the cards.

[0156] (Other embodiments) In the card management system 1 of the above embodiment, the case where the card management server 10 issues a credit card has been described, but the cards to be issued are not limited to credit cards, and various types of cards such as prepaid cards and membership cards may also be issued.

[0157] In the card management system 1 of the above embodiment, when a card user is creditworthy, the user terminal 20 allows the use (display) of a regular card CD2, which is a digital card with a specific design that indicates that the card image is under review. However, this is not limited to this, and it may also allow the use (display) of a regular card, which is a digital card with a regular design (a digital card version of a regular card CA2, which is a physical card with a regular design).

[0158] The "card" described in the above embodiment includes both a "digital card" and a "physical card."

[0159] The processing methods performed by the card management server 10 and user terminal 20 of the card management system 1 described in each of the above embodiments, i.e., the original card application acceptance processing shown in the flowchart of Figure 6, the original card issuance processing shown in the flowcharts of Figures 9 to 11, and the card usage response processing shown in the flowchart of Figure 14, can all be stored in a recording medium such as a memory card (ROM card, RAM card, etc.), a magnetic disk (floppy (registered trademark) disk, hard disk, etc.), an optical disk (CD-ROM, DVD, etc.), or semiconductor memory and distributed as a program that can be executed by a computer.

[0160] In addition, the program data for realizing each technique of each of the above-mentioned embodiments can be transmitted over a communication network in the form of program code, and the various functions described above can be realized by importing this program data into the communication unit of a computer (processor) of an electronic device connected to the communication network.

[0161] The present invention is not limited to the above-described embodiments, and various modifications can be made in the implementation stage without departing from the spirit of the invention. Furthermore, the embodiments may be implemented in appropriate combinations, in which case the combined effects can be obtained. Furthermore, the above-described embodiments include various inventions, and various inventions can be extracted by combining selected elements from the disclosed elements. For example, if the problem can be solved and the desired effect can be obtained even if some elements are deleted from all elements shown in the embodiments, the configuration from which these elements are deleted can be extracted as an invention. [Explanation of symbols]

[0162] 1. Card management system 10...Card management server 11...Control unit (CPU) 12...Storage section 12P...Program storage area 12p1...Server system program 12p2...Card application acceptance app 12p3...Card issuing app 12p3E...Card image review criteria data 12p3R...Image review notification data 12p4...Card-compatible app 12D...Management data storage area 12d1...Card application management data 12d2...Card user management data 12d3...Card usage data 15...Communications Department 20...User terminal 21...Control unit (CPU) 22...Storage section 22R...Device data storage area 22P...Program storage area 22p1...Terminal system program 22p2...Card application / usage app 22W...Work data storage area 22w1...Data for generating display screen 22w2...Display data 22w3...Image data 25...Touch panel display 26...Communications Department 27...imaging unit (camera) 30...Credit information server N...Communication network (Internet) GM0...Original card (one-of-a-kind card) application screen GM1...Image file selection screen GM2...Image confirmation screen GM3...Card type selection screen GM4...Card image trimming screen GM5...Card image completion screen P0 … Unique image of cardholder IMC…Original design card image R0... Image review OK notification R1~R3...Image re-registration request (1)~(3) R4...Notice of incomplete image review GC...Main Menu X ... [Digital Card] icon GD...Digital card screen CD1...Original card (digital card with original design) CD2...Normal card (special design or normal design digital card) CA1...Original card (physical card with original design) CA2...Normal card (physical card with normal design)

Claims

1. A card management device having a communication function with a user terminal of a user, A process of storing the image transmitted from the user terminal in a storage unit; a process of issuing a first card having a first design that does not include the image to the user; a process of examining whether the image is suitable for public use based on pre-stored criteria for examining whether the image is a valid image suitable for public use, and if the image is suitable for public use, replacing the first card issued to the user with a second card of a second design that includes the image; A card management device having a control unit that executes the above.

2. The control unit acquiring credit information of the user, and if the user is creditworthy, executing a process of issuing the first card to the user; 2. The card management device according to claim 1.

3. the process of issuing the first card to the user includes a process of making the first card, which is a digital card of the first design, displayable on the user terminal; the switching process includes a process of switching the first card that has been made displayable on the user terminal to the second card, which is a digital card with the second design; 3. The card management device according to claim 1.

4. The control unit If the image is approved, a process is executed to mail the second card, which is a physical card with a second design including the image, to the user.

4. The card management device according to claim 3.

5. The control unit If the image is not acceptable for review, a process of re-storing a new image sent from the user terminal is executed; The switching process includes a process of re-examining whether or not the new image can be used each time the new image is re-stored, and if the new image is approved for use, switching the first card issued to the user to a second card of a second design including the new image.

3. The card management device according to claim 1.

6. The restoring process includes: If the image is not acceptable for review, a process of sending a re-storage request to the user terminal, the re-storage request including a message prompting the user to re-store the new image and a reason why the image is not acceptable for review is included.

6. The card management device according to claim 5.

7. The control unit and executing a process of repeatedly transmitting a next re-storage request to the user terminal, the next re-storage request including a message that is stronger than the previous re-storage request and urges the user terminal to re-store the new image, every time a preset period has elapsed since the first re-storage request was transmitted to the user terminal.

7. The card management device according to claim 6.

8. The control unit when a specific period longer than the preset period has elapsed since the initial request for restoring the stored data was sent to the user terminal, execute a process of mailing the first card, which is a physical card with the first design, to the user.

8. The card management device according to claim 7.

9. The control unit When the specific period has elapsed, a process is executed to send to the user terminal a notice of incomplete review, which includes a message that the review of the image has not been completed and a message that the image can be re-stored free of charge for a preset free period.

9. The card management device according to claim 8.

10. The control unit If the re-stored new image is approved for review before the free period expires, a process of switching from the first card to the second card is executed free of charge. The card management device according to claim 9.

11. The first design does not include the image and is a specific design indicating that the image is under review, or a general design that is not the specific design; the first card is a regular card with the specific design or the regular design, the second design is an original design including the image; The second card is an original card with the original design.

3. The card management device according to claim 1.

12. the restoring request includes a destination URL for restoring the new image; 7. The card management device according to claim 6.

13. A control unit of a card management device having a communication function with a user terminal of a user, A process of storing the image transmitted from the user terminal in a storage unit; a process of issuing a first card having a first design that does not include the image to the user; a process of examining whether the image is suitable for public use based on pre-stored criteria for examining whether the image is a valid image suitable for public use, and if the image is suitable for public use, replacing the first card issued to the user with a second card of a second design that includes the image; A program to execute.

Images