Information processing apparatus, information processing method, and program

The information processing device facilitates point transfers between independent credit card members by using a server to manage and execute transfers within groups, addressing limitations in existing systems and enhancing point-sharing flexibility.

JP2024157204AActive Publication Date: 2024-11-07SUMITOMO MITSUI CARD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2023071409
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-04-25
Publication Date
2024-11-07
Estimated Expiration
2043-04-25

AI Technical Summary

Technical Problem

Existing credit card systems limit point transfers to a primary member and family card holders, restricting the ability to transfer points beyond this framework.

Method used

An information processing device that allows point transfers between members with independent credit card payment accounts, utilizing a server to manage and execute point transfers between members within a group, including a reception unit to receive transfer applications, a storage unit to store member information, and a change unit to modify point balances.

Benefits of technology

Enables point transfers between independent credit card members, enhancing flexibility and allowing members to share points outside traditional primary-member and family-card holder frameworks.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024157204000001_ABST
    Figure 2024157204000001_ABST
Patent Text Reader

Abstract

To provide a technique for transferring points between cards of members being credit card members and solely having a settlement account.SOLUTION: An Information processing apparatus includes: reception means for, from a first member solely having a settlement account of a credit card, information relating to a transfer request for transferring points of the first member to a second member solely having a settlement account for a credit card; storage means for storing the information regarding the first member and the second member; and changing means for, based on the information relating to the received transfer request, changing the information relating to the first member and the second member stored in the storage means.SELECTED DRAWING: Figure 4
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to an information processing device, an information processing method, and a program, and more particularly to an information processing device, an information processing method, and a program that enable points to be transferred between cards of credit card members who have their own settlement accounts. [Background technology]

[0002] There is known a technology that allows a parent, who is the primary credit card holder, to transfer points earned by using the credit card to a child (see Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 7189250 Summary of the Invention [Problem to be solved by the invention]

[0004] There are also family cards available for credit cards. Family cards can generally be owned by the spouse, parents, and children over the age of 18 who live in the same household as the main cardholder. Points are awarded when a family card is used and are added to the main cardholder's points. When a family card holder uses a family card, the payment is made into the main cardholder's payment account. In such a system, it is common for points to be transferred. In the above-mentioned Patent Document 1, points are transferred from a parent (main member) to a child (family card holder) in this system. However, there has been a demand for the ability to transfer earned points beyond the conventional framework of a main member and a family card holder.

[0005] The present invention has been made in consideration of such problems, and aims to provide technology that enables points to be transferred between cards of credit card members who have their own payment accounts. [Means for solving the problem]

[0006] An information processing device according to one embodiment of the present invention comprises a receiving means for receiving information relating to a transfer application from a first member who has his / her own credit card payment account to a second member who has his / her own credit card payment account to transfer the points of the first member to a second member who has his / her own credit card payment account, a storage means for storing information relating to the first member and the second member, and a modification means for modifying the information relating to the first member and the second member stored in the storage means based on the information relating to the accepted transfer application. Effect of the Invention

[0007] According to the present invention, points can be transferred between cards of credit card members who have their own settlement accounts. [Brief description of the drawings]

[0008] A more detailed understanding of the embodiments disclosed herein can be had from the following description, taken in conjunction with the accompanying drawings, in which: [Figure 1] FIG. 2 is a diagram showing an overview of services provided by the information processing device according to the present embodiment. [Diagram 2] 1 is a diagram illustrating an example of the configuration of an information processing system according to an embodiment of the present invention. [Diagram 3] FIG. 2 is a diagram illustrating an example of a hardware configuration of a server according to the embodiment. [Figure 4] FIG. 2 is a diagram illustrating an example of a functional configuration of a server according to the present embodiment. [Diagram 5] 5 is a flowchart showing an example of the flow of processing executed by a server having the functional configuration of FIG. 4. [Figure 6] FIG. 13 is a diagram showing an example of a group registration content inquiry screen according to the embodiment. [Figure 7] FIG. 13 is a diagram showing an example of a transfer application screen according to the embodiment; [Figure 8] FIG. 13 is a diagram showing an example of a transfer history inquiry screen according to the present embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] (overview) FIG. 1 is a diagram showing an overview of a service (hereinafter, referred to as this service) provided by an information processing device (server 1) according to this embodiment. This service enables the transfer of points between member cards. In this service, "member" refers to a credit card member who has an independent payment account. Members are not like family card holders who are linked to a main member. Members are independent entities in terms of livelihood, place of residence, payment account, etc. This service operates under a different system than the main member-family card holder framework described above.

[0010] A member (e.g., member A, the grantor) applies for the transfer of points using member terminal 2a. The member applies for the transfer by specifying the number of points to be transferred and the grantee to whom the points will be transferred. The points transferred by the member may be, for example, limited-time points. Server 1 accepts the number of points (e.g., 400 points) and identification information of the grantee (e.g., member B, the recipient) from member terminal 2a. Server 1 may limit the number of points it accepts (e.g., by setting an upper limit). The server 1 changes the points held by each member based on the number of points accepted and the identification information of the grantee. For example, the server 1 subtracts member A's points from 1200 points to 800 points. The server 1 adds member B's points from 600 points to 1000 points simultaneously with the subtraction process or after the subtraction process has been successfully completed. Details of the server 1's acceptance process for transfer applications will be described later.

[0011] (System Configuration) FIG. 2 is a diagram showing an example of the overall configuration of the information processing system of this embodiment. The information processing system includes a server 1 (information processing device), a member terminal 2a, and a member terminal 2b, which are communicatively connected via a network N. The member terminal 2a is, for example, a terminal used by the above-mentioned member A. The member terminal 2b is, for example, a terminal used by the above-mentioned member B. The member terminals 2a and 2b can be mobile terminals such as smartphones and tablet terminals, or computers such as PCs (Personal Computers), and are equipped with a web browser, e-mail software, or other applications. The network N may include wired or wireless networks including LANs (Local Area Networks) and WANs (Wide Area Networks). It should be noted that the numbers of servers 1, member terminals 2a, and member terminals 2b are not limited to those shown in the figure.

[0012] (Hardware configuration) 3 shows an example of the hardware configuration of the server 1 according to this embodiment. The server 1 includes a processor 301, a memory 302, a storage device 303, a communication interface (I / F) 304, an input device 305, and an output device 306, which are communicatively connected via a bus 310.

[0013] The processor 301 may be a CPU (Central Processing Unit) and controls each component connected via a bus 310 and processes data. The processor 301 also reads and executes a program stored in the memory 302 or the storage device 303 to execute various processes according to this embodiment.

[0014] The memory 302 may be a memory such as a ROM (Read Only Memory) or a RAM (Random Access Memory), and stores programs and data for executing various processes according to the present embodiment. The RAM operates as a working memory, and can load programs read by the processor 301.

[0015] The storage device 303 can be a large-capacity storage device such as a hard disk drive (HDD) or a solid state drive (SDD), and stores programs and data for executing various processes according to this embodiment.

[0016] A communication interface (I / F) 304 is an interface for connecting to a wired or wireless network and transmitting and receiving data, enabling communication with other computers.

[0017] The input device 305 may be a keyboard, a mouse, a touch panel display that also serves as the output device 306, or the like.

[0018] The output device 306 may be a liquid crystal display, an organic EL (Electro Luminescence) display, or the like.

[0019] The hardware configuration of the server 1 is not limited to the above-mentioned example configuration, and may include other elements.

[0020] (Functional configuration) Fig. 4 is a diagram showing an example of the functional configuration of the server 1 according to this embodiment. In Fig. 4, the server 1 includes a presentation unit 401, a reception unit 402, a change unit 403, a notification unit 404, an output unit 405, a group DB (database) 406, and a point DB 407. These functional units can be implemented by the processor 301 reading and executing a program stored in the memory 302 or the storage device 303. Note that, although the functional units relating to this embodiment will be described in particular in this specification, the server 1 may also include other functional units.

[0021] In this embodiment, an example will be described in which members form a group, and points are transferred between cards of members in the group. A group may be formed, for example, by a member inviting other members and registering only those members who accept the invitation as group members. Also, the identity of the member who accepts the invitation may be verified (for example, by telephone or SMS). The server 1 can identify each member of the group by, for example, the card number of each member. The card number of each member is assumed to be acquired by the server 1 when the member starts using the service.

[0022] The presentation unit 401 presents a transfer application screen for a point transfer application. The presentation unit 401 may generate a transfer application screen by referring to information related to the transfer application (e.g., group members and owned points) stored in a group DB 406 and a point DB 407 described later, and present the transfer application screen. The presentation unit 401 presents a transfer application screen, for example, to a member terminal (e.g., member terminal 2a) used by the member who is applying to transfer points. Hereinafter, the member who transfers points is referred to as the "grantor," and the member who receives the points is referred to as the "recipient." The grantor applies for a transfer by inputting the necessary information in the fields displayed on the transfer application screen (e.g., grantee, etc.). Information regarding the transfer application entered by the grantor is accepted by the acceptance unit 402 via the member terminal 2a used by the grantor. Details of the transfer application screen will be explained in FIG. 7. The presentation unit 401 may present the transfer application screen to a terminal used by the recipient (for example, the member terminal 2b). This is because a grantor can become a recipient and a recipient can become a grantor.

[0023] The receiving unit 402 receives information regarding a transfer application from a first member (grantor) who has a sole credit card settlement account to transfer the first member's points to a second member (recipient) who has a sole credit card settlement account. The receiving unit 402 receives at least the number of the first member's points to be transferred by the first member and the identification information of the grantee who will receive the transfer of the first member's points. The receiving unit 402 receives, for example, information such as "number of points - 400" and "recipient - member B" from the member terminal 2a used by the grantor. The received information is passed to the changing unit 403 described below and used in the change process by the changing unit 403. The identification information of the grantee may be, for example, the card number of the grantee. The accepting unit 402 may also identify the grantee using the card number as an identifier.

[0024] The change unit 403 changes the information on the first member and the second member stored in a database described below, based on the information on the transfer application received by the reception unit 402. Specifically, the change unit 403 identifies the information to be changed from the information on the first member and the second member stored in the group DB 406 and the point DB 407 described below, based on the information on the transfer application, and executes a change process on the identified change target. More specifically, the change unit 403 compares the points held by the first member stored in the point DB 407 with the number of points of the first member to be transferred included in the transfer application, and if the points held by the first member are greater, it subtracts the points held by the first member and adds the points held by the second member.

[0025] The change unit 403 acquires from the reception unit 402 the number of points to be transferred by the grantor and information on the grantee (i.e., the recipient). The change unit 403 identifies the points held by the grantor with reference to the point DB 407. The change unit 403 also identifies the recipient to whom the points will be transferred with reference to the group DB 406. The change unit 403 compares the points held by the identified grantor with the number of points of the grantor to be transferred. If the points held by the grantor are greater than the number of points to be transferred, the change unit 403 subtracts the points held by the grantor. At the same time as subtracting the points held by the grantor, or after the subtraction process has been successfully completed, the change unit 403 adds the points held by the identified recipient.

[0026] For example, in the example shown in FIG. 1, the giver is member A. The recipient identified by the change unit 403 is member B. Member A and member B belong to the same group. Member A's owned points are 1,200 points, and the number of points of the giver to be transferred is 400 points. Member A's owned points are more than the 400 points to be transferred. Therefore, the change unit 403 subtracts 400 points from the points held by member A. At the same time as subtracting member A's owned points, or after the subtraction process has been successfully completed, the change unit 403 adds 400 points to the points held by member B.

[0027] In this manner, the change process is performed by the change unit 403. The server 1 may include an update unit (not shown) that updates the points held by each member stored in the point DB 407 after the subtraction and addition processes are performed by the change unit 403. The difference between the points held by each member before and after the update by the update unit can be output by the output unit 405, which will be described later, as a transfer history.

[0028] When the change unit 403 executes the subtraction process and / or the addition process, the notification unit 404 issues a predetermined notification regarding the subtraction and / or addition to the member. The notification unit 404, for example, refers to the point DB 407 to check whether the points held by the giver and the recipient have been subtracted and / or added by the change unit 403. After checking, the notification unit 404 issues a predetermined notification regarding the subtraction and / or addition.

[0029] For example, when the change unit 403 does not execute the subtraction and the points held by the grantor are not subtracted, the notification unit 404 may notify the member terminal 2a used by the grantor that the subtraction is not possible. An example of a case in which the change unit 403 does not execute the subtraction is when the points held by the grantor are less than the number of points to be transferred. Also, for example, when the change unit 403 does not complete the addition and the points held by the recipient are not added, the notification unit 404 may notify the member terminal 2a used by the giver that the addition will not be made. An example of a case in which the change unit 403 does not complete the addition is when the recipient has withdrawn from the formed group. Also, for example, when the subtraction process and the addition process by the change unit 403 are successful, the notification unit 404 may notify the member terminal 2a used by the giver that the transfer has been completed. The notification unit 404 may also notify the member terminal 2b used by the recipient that the transfer has been completed. The notification unit 404 may notify, for example, "400 points have been transferred from XXX."

[0030] When both the subtraction process and the addition process performed by the change unit 403 are successful, the output unit 405 outputs the number of points of the member that was the subject of the subtraction or addition as a transfer history. The output unit 405 can, for example, refer to the points DB 407 and output, as a transfer history, the difference in the points held by the giver and the recipient before and after the update by the update unit described above.

[0031] There are no limitations on the manner of output by the output unit 405. For example, the output unit 405 may generate a point transfer history inquiry screen including the transfer history. The giver and the recipient can check the transfer history by accessing this screen via the member terminal 2a used by the giver and the member terminal 2b used by the recipient. Also, for example, when the output unit 405 receives a signal requesting output from the member terminal 2a used by the grantor, the output unit 405 may output the transfer history to the member terminal 2a. Also, for example, the output unit 405 may output the transfer history by sending it to the recipient's email address.

[0032] The group DB 406 stores information about groups. As described above, in this embodiment, members form groups. The group DB 406 stores information about the groups formed. The information about the groups includes, for example, a group number, group members, the number of people registered in the group, etc. The card number of each group member may be stored in association with each group member. The information about groups stored in the group DB 406 is used, for example, to generate a transfer request screen by the presentation unit 401 and to identify a grantee who will receive a transfer of points by the change unit 403. The information about groups stored in the group DB 406 can also be used, for example, in a process of identifying a grantor who is about to make a transfer request.

[0033] The points DB 407 stores information related to member points. The information related to member points includes, for example, the points owned by each member, the update history of the points, etc. The points owned by each member may be stored in association with the member's card number. The information regarding the member's points stored in the point DB 407 is used, for example, by the presentation unit 401 to generate a transfer application screen, by the change unit 403 to confirm the member's owned points, by the change unit 403 to compare the member's owned points with the number of points to be transferred, and by the output unit 405 to output the transfer history.

[0034] The functional configuration of the server 1 is not limited to the above-mentioned functional configuration, and may include other components.

[0035] (Processing contents) FIG. 5 is a flowchart showing an example of the flow of processing executed by the server 1 having the functional configuration of FIG.

[0036] In step S1, the presentation unit 401 presents a transfer application screen for applying for the transfer of points. The presentation unit 401 presents the transfer application screen to, for example, the member terminal 2a used by the giver who applies for the transfer of points. The presentation unit 401 may also present the transfer application screen to the member terminal 2b used by the recipient. This is because a giver can become a recipient and a recipient can become a giver. The grantor applies for a transfer by inputting the necessary information in the items (e.g., grantee, etc.) displayed on the transfer application screen. The information related to the transfer application input by the grantor is accepted by the acceptance unit 402 via the member terminal 2a used by the grantor.

[0037] In step S2, the reception unit 402 receives information regarding a transfer application from a first member (grantor) who solely has a credit card payment account to transfer the first member's points to a second member (recipient) who solely has a credit card payment account. The reception unit 402 receives at least the number of points of the first member to be transferred by the first member and the identification information of the grantee who will receive the transfer of the first member's points. For example, the reception unit 402 receives information such as "number of points - 400" and "grantee - member B" from the member terminal 2a used by the grantor. The received information is passed to the change unit 403, which will be described later, and is used in the change process by the change unit 403.

[0038] In step S3, the change unit 403 compares the points held by the grantor stored in the point DB 407 with the number of points of the grantor to be transferred, which is included in the transfer application.

[0039] In step S4, the change unit 403 determines whether the points held by the grantor can be subtracted. Specifically, the change unit 403 determines whether the points held by the grantor are greater than the number of points of the grantor to be transferred. If the points held by the grantor can be subtracted, the process proceeds to step S6. If the points held by the grantor cannot be subtracted, the process proceeds to step S5.

[0040] In step S5, the notification unit 404 notifies the user that the points are not transferable. For example, if the number of points held by the grantor is 300 and the number of points to be transferred is 400, the notification unit 404 notifies the member terminal 2a used by the grantor that the points are not transferable.

[0041] In step S6, the change unit 403 performs a process of subtracting the points held by the giver and a process of adding the points held by the recipient. More specifically, the change unit 403 adds the points held by the recipient at the same time as subtracting the points held by the giver or after the subtraction process has been successfully completed.

[0042] In step S7, the output unit 405 outputs, as a transfer history, the number of points of the member that has been subtracted or added by the change unit 403. The output unit 405 may, for example, refer to the point DB 407 and output, as a transfer history, the difference in the points held by the giver and the recipient before and after the subtraction or addition of points. There are no limitations on the manner of output by the output unit 405. For example, the output unit 405 may generate a point history inquiry screen including the transfer history. The giver and the recipient can check the transfer history by accessing this screen via the member terminal 2a used by the giver and the member terminal 2b used by the recipient. Also, for example, when the output unit 405 receives a signal requesting output from the member terminal 2a used by the grantor, the output unit 405 may output the transfer history to the member terminal 2a. Also, for example, the output unit 405 may output the transfer history by sending it to the recipient's email address.

[0043] (Example output) FIG. 6 is a diagram showing an example of a group registration content inquiry screen according to this embodiment. The group registration content inquiry screen is a screen showing the current state of the group to which the member belongs. As described above, in this embodiment, members form groups together. Therefore, when a member initiates the transfer of points, a task of confirming group members may occur. The group registration details inquiry screen 600 displays the current registration details, group members, and a button 601 for transferring points. The current registration details include the group number and the number of registered members. In Figure 6, the group number is 123456 and the number of registered members is 3. Below the current registration details, the group members are shown, along with the names and card names of the members who belong to the group. In Fig. 6, three members, XXX, OOOO, and □□□□, and the names of the cards that each of them owns are shown. Although Fig. 6 shows one card for each member, multiple cards may be shown. A button 601 for transferring points is displayed below the group members, and is labeled with the words "Transfer points." When transferring points, the giver presses this button 601 for transferring points. When the giver presses the button, the screen transitions to a transfer application screen, which will be described later.

[0044] Fig. 7 is a diagram showing an example of a transfer application screen according to this embodiment. The screen shown in Fig. 7 is a screen for a member to transfer points. The transfer application screen 700 displays the giver's current points, a target selection field 701, a notice stating "cannot be canceled once confirmed," a button 702 for confirming the point transfer, and a back button 703. Note that the target selection field 701 displays group members other than the giver. Let XXX shown in FIG. 6 be the grantor in FIG. 7. The grantor XXX enters the necessary information in the target selection field 701. Specifically, the grantor enters the member to whom the points will be transferred and the points to be granted. XXX selects member XXX and checks the selection box. XXX also sets the points to be granted to 400 points. To confirm the transfer application with this content, the grantor XXX checks the notes and then presses button 702 to confirm the point transfer. Pressing the confirm button completes the transfer application. On the other hand, to cancel the transfer application, the grantor XXX presses back button 703. In FIG. 7, only one person, XXX, is selected as the recipient of the award, but multiple recipients can be selected.

[0045] Fig. 8 is a diagram showing an example of a transfer history inquiry screen according to this embodiment. The screen shown in Fig. 8 is a screen for displaying the number of points that have been transferred as a transfer history when the transfer of points has been established. The transfer history inquiry screen 800 is a screen that can be viewed by the giver. The transfer history inquiry screen 800 shows the date and the awarded points. The date shown in FIG. 8 may be the date when the giver transferred the points. The awarded points are the number of points that the giver transferred. In FIG. 8, it is shown as - (minus) 400 points. The transfer history inquiry screen 801 is a screen that the recipient can view. The transfer history inquiry screen 801 shows the date, the received points, and the received expiration date. The date shown in FIG. 8 may be the date on which the giver received the points. The received points are the number of points received by the recipient. In FIG. 8, it is shown as + (plus) 400 points. The received expiration date is the expiration date of the points received by the recipient. In FIG. 8, it is shown as the end of September 2023. As described above, the points transferred by the giver may be limited-time points. Therefore, when the recipient receives limited-time points, the received expiration date may be shown in this manner.

[0046] Although the principles of the present invention have been described above with reference to exemplary embodiments, it will be understood by those skilled in the art that various embodiments that change in configuration and details can be realized without departing from the gist of the present invention. That is, the present invention can be embodied as, for example, a system, an apparatus, a method, a program, or a storage medium. [Explanation of symbols]

[0047] 1 Server 401 Presentation section 402 Reception 403 Changes 404 Notification Department 405 Output section 406 Group DB 407 points DB

Claims

1. a receiving means for receiving information on a transfer application from a first member who has a sole credit card settlement account to transfer points of the first member to a second member who has a sole credit card settlement account; A storage means for storing information regarding the first member and the second member; a change means for changing the information about the first member and the second member stored in the storage means based on information about the accepted transfer application; An information processing device comprising:

2. The receiving means receives at least the number of points of the first member to be transferred by the first member and identification information of a recipient to whom the points of the first member are to be transferred. The information processing device according to claim 1 .

3. A presentation means for presenting a transfer application screen for the transfer application is further provided. The information processing device according to claim 1 .

4. the change means, based on the information on the transfer application, identifies an object to be changed from among the information on the first member and the second member stored in the storage means, and executes a change process on the identified object to be changed; The information processing device according to claim 1 .

5. the storage means stores at least the points held by the first member and the second member; the change means compares the points held by the first member stored in the storage means with the number of points held by the first member to be transferred, included in the transfer application, and, if the number of points held by the first member is greater, subtracts the points held by the first member and adds the points held by the second member; The information processing device according to claim 1 .

6. The system further includes a notification unit that, when the subtraction process and / or the addition process is executed by the change unit, issues a predetermined notification regarding the subtraction and / or the addition to the first member. The information processing device according to claim 5 .

7. and an output unit configured to output, when both the subtraction process and the addition process by the change unit are successful, the number of points of the first member that are the subject of the subtraction and the addition as a transfer history. The information processing device according to claim 6.

8. An information processing method executed by an information processing device, a receiving step of receiving information regarding a transfer application from a first member who has a sole credit card settlement account to transfer points of the first member to a second member who has a sole credit card settlement account; a storing step of storing information regarding the first member and the second member; a changing step of changing the information about the first member and the second member stored in the storing step based on the information about the accepted transfer application; An information processing method comprising the steps of:

9. A program for causing a computer to execute the method according to claim 8.

Citation Information

Patent Citations

  • Point management system, point management method and program

    JP7189250B2