Payment processing device, method, and program
The payment processing device allows customers to dynamically set authentication items, addressing the challenge of unreliable user identification in existing systems by enabling flexible personal authentication configurations.
Patent Information
- Application Number
- JP2023208533
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2023-12-11
- Publication Date
- 2024-11-06
- Estimated Expiration
- 2043-12-11
AI Technical Summary
Companies face the burden of building their own websites for account transfer applications, and existing general-purpose services lack flexibility in setting authentication items, making it difficult to reliably identify end users.
A payment processing device that allows customers to dynamically set authentication items and configure authentication interfaces based on user access, enabling flexible personal authentication for each customer company.
Enables flexible setting of authentication items for personal authentication, allowing companies to share a payment information registration site without fixed input items, enhancing user identification reliability.
Smart Images

Figure 0007578788000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a payment processing device, method, and program that provides a client company with a mechanism for implementing a service that accepts registration of payment information such as account transfers on the Web and registers data necessary for continuous billing processing. More specifically, the present invention relates to a payment processing device, method, and program that allows an end user to flexibly set, for each client company, authentication items used for identity authentication when applying for a service of the client company. [Background technology]
[0002] In the past, businesses have provided continuous services to end users and periodically billed them for the services. Such businesses bill users through payment methods such as direct debit and credit cards.
[0003] When entering into a direct debit contract with a user, a company would build its own website that was linked to a service such as that shown in Non-Patent Document 1. The company would accept direct debit applications from end users, receive account information for direct debit, and have the end users enter information required for identity verification, thereby carrying out continuous billing processes such as direct debit. [Prior art documents] [Non-patent literature]
[0004] [Non-Patent Document 1] NTT Data Corporation, "Starts offering the "Internet Direct Debit Reception Gateway Service," a service that enables direct debit contracts over the Internet," [online], March 25, 2008, [Retrieved November 13, 2023], Internet<https: / / www.nttdata.com / global / ja / news / release / 2008 / 032500 / > Summary of the Invention [Problem to be solved by the invention]
[0005] It is a heavy burden for a company to build its own website for direct debit applications, even if the system part to be built is only the front part that links to a service such as Non-Patent Document 1. Even if a general-purpose service exists that provides a mechanism for the front part that links to a service such as Non-Patent Document 1, and a company introduces such a service, since the information suitable for identifying an end user differs from company to company, if the screen input items of the general-purpose service are fixed, it is difficult to set flexible authentication items (customer identification items) according to the service content of the company. Furthermore, if the screen input items are fixed in this way, it is very difficult to reliably identify the end user.
[0006] The present invention has been made to solve such problems, and aims to provide a payment processing device, method, and program that enable authentication items used for identity verification when an end user applies for a service from a client company to be flexibly set for each client company. [Means for solving the problem]
[0007] A payment processing device according to one aspect of the present invention is a payment processing device including a communication unit for communicating with an external network, a storage unit, and a control unit, the storage unit stores display control information and authentication master information; The control unit is receiving, via the communication unit, from the first device, one or more customer-selected authentication items selected and changed by a customer from among a plurality of authentication items; storing the one or more received customer selected authentication items in the display control information of the storage unit; dynamically configuring an authentication interface to include one or more customer-selected authentication items associated with the customer and providing the authentication interface to a second device in response to user access associated with the customer via the communication unit; The apparatus is configured to execute the following steps: Effect of the Invention
[0008] According to the present invention, authentication items used for identity verification when an end user applies for a service of a client company can be flexibly set for each client company. Also, each client company does not need to set up its own payment information registration site, and even if a payment information registration site is one that can be shared by various client companies, the input items, i.e., authentication items (client identification items), are not fixed and can be dynamically changed according to the client. [Brief description of the drawings]
[0009] 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] 1 is a configuration diagram of an entire system including a payment processing device 10 according to the present invention. [Diagram 2] 1 is a system configuration diagram of a payment processing device 10 according to the present invention. [Diagram 3] 10 is a diagram illustrating an example of a data structure of customer-specific display information 106. FIG. [Figure 4] 10 is a diagram illustrating an example of a data structure of authentication master accounting information 107. FIG. [Diagram 5] FIG. 13 is a flow diagram illustrating the processing of a payment information registration reception service. [Figure 6] FIG. 6 is a diagram illustrating an example of an authentication item setting screen 600 for allowing a customer to select one or more arbitrary authentication items from among a plurality of authentication items and change the names of the authentication items. [Figure 7] FIG. 7 illustrates an example of a login screen 700 on which a user inputs a user ID and authentication information set by a customer. [Figure 8] FIG. 8 is a diagram illustrating a service application and payment method selection screen 800. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0010] (Overall structure and functions of each component) FIG. 1 is a configuration diagram of an entire system including a payment processing device 10 according to the present invention. The payment processing device 10 is connected to a payment agency system 11, an end user terminal 12, and a customer device 13 so that they can communicate with each other. The payment agency system 11 and the customer device 13 are connected to each other so that they can communicate with each other. Although only one end user terminal 12 and one customer device 13 are shown in FIG. 1, there may be a plurality of end user terminals 12 and customer devices 13. As known to those skilled in the art, the payment agency system 11 may be used by a payment agency that acts as an intermediary between companies and financial institutions for payment methods such as account transfers and credit card payments.
[0011] In this specification, a "customer" refers to any entity, such as a company, a local government, a non-profit organization, etc., and the terms "customer" and "company," "local government," "non-profit organization," etc. are used interchangeably. In addition, a "user" refers to an end user who receives a service from a customer, and the terms "user" and "end user" are used interchangeably.
[0012] The payment processing device 10 provides the customer device 13 with an authentication item setting screen 600, allowing the customer device 13 to set one or more authentication items that each customer requests of the user, and stores the set information as authentication master information. Authentication items can also be referred to as customer identification items. The payment processing device 10 receives user master billing information to be used for authenticating each user from the customer device 13, and stores it within the device.
[0013] In response to user access based on access information (e.g., a URL) assigned to each customer, the payment processing device 10 provides the end user terminal 12 with a login screen 700 associated with each customer, and allows the end user to input authentication information set for each customer. That is, the payment processing device 10 can change the screen interface of the login screen 700 for each customer by preparing a URL for the end user login screen 700 for each customer. The login screen 700 has authentication items (customer identification items) that may differ for each customer, and the number of authentication items that need to be input or selected on the screen and their names may differ.
[0014] The payment processing device 10 provides an interface for inputting billing information to the end user terminal 12 for an authenticated end user, causes the end user to input user information including payment information such as a recurring billing method, an account number, and a credit card number, and receives the user information. The payment processing device 10 can change the input interface in cooperation with the payment agency system 11 according to the content of the user information to be acquired. The payment processing device 10 can transmit the user information to the payment agency system 11, and provide response data from the payment agency system 11 to the customer device 13. In addition, information inputted in a certain input interface (screen) can also be directly transmitted to the payment agency system 11 (without being temporarily stored in the payment processing device 10) and registered when a predetermined registration event occurs.
[0015] The payment agency system 11 can receive and store user information including payment information such as a recurring billing method, account number, and credit card number for each user from the payment processing device 10 and / or end user terminal 12. The payment agency system 11 receives a payment request (e.g., an account transfer request) associated with each user from the customer device 13, and requests a relevant financial institution system to perform payment processing (e.g., account transfer) based on the user's payment request. The account transfer processing is the same as conventional processing, and a detailed description thereof will be omitted in this specification.
[0016] The end-user terminal 12 may be any type of device (eg, a smartphone, a PC, a tablet terminal, etc.) capable of operating in a wired or wireless environment, and is not limited to any particular apparatus or device.
[0017] The end user terminal 12 receives access information (e.g., a URL) for logging in to a login screen 700 associated with each customer from the customer device 13. The end user terminal 12 can access the login screen 700 provided by the payment processing device 10 via the access information and input authentication information.
[0018] After authentication, the end user terminal 12 can input user information including payment information such as a recurring billing method, an account number, a credit card number, etc. via one or more interfaces for inputting billing information. The information input via these interfaces may be registered in the payment processing device 10 or may be registered in the payment agency system 11.
[0019] The customer equipment 13 may be any type of device (eg, a smartphone, a PC, a tablet terminal, etc.) or a server device that can operate in a wired or wireless environment, and is not limited to a specific equipment or device.
[0020] Customer device 13 can select one or more authentication items that the customer requests from the end user via authentication item setting screen 600 provided by payment processing device 10, and can register an alias for each selected authentication item in payment processing device 10. Customer device 13 can transmit or register user master billing information to be used for authenticating each user in payment processing device 10.
[0021] The customer device 13 transmits access information (e.g., a URL) for logging in to the login screen 700 associated with each customer to the end user terminal 12. The customer device 13 transmits a payment request (e.g., an account transfer request) associated with each user to the payment agency system 11.
[0022] (System Configuration) 2 is a system configuration diagram of payment processing device 10 according to the present invention. Like a general computer, payment processing device 10 comprises control unit 101, main memory unit 102, auxiliary memory unit 103, IF unit 104, and output unit 105, which are interconnected by bus 120 or the like. Payment processing device 10 also comprises customer-specific display information 106 and authentication master billing information 107 in the form of storage means such as a file / database in auxiliary memory unit 103.
[0023] The control unit 101 is also called a central processing unit (CPU), and controls each component of the payment processing device 10 and performs data calculations, and also reads out various programs stored in the auxiliary storage unit 103 into the main storage unit 102 and executes them. The main storage unit 102 is also called a main memory, and can store various received data, computer-executable instructions, and data after calculation processing based on the instructions. The auxiliary storage unit 103 is a storage device typified by a hard disk drive (HDD), and is used for long-term storage of data and programs.
[0024] The embodiment in Fig. 2 describes an embodiment in which control unit 101, main memory unit 102, and auxiliary memory unit 103 are provided in the same computer, but in another embodiment, payment processing device 10 can be configured to realize parallel distributed processing by multiple computers by using multiple control units 101, main memory units 102, and auxiliary memory units 103. Also, in another embodiment, it is possible to install multiple servers for payment processing device 10, and have the multiple servers share one auxiliary memory unit 103.
[0025] The IF unit 104 plays the role of an interface (IF) when transmitting and receiving data to and from other systems and devices, and also provides an interface for receiving various commands and input data (various masters, tables, etc.) from a system operator. The output unit 105 provides a display screen for displaying processed data and a printing means for printing the data.
[0026] Components with functions similar to those of the control unit 101, main memory unit 102, auxiliary memory unit 103, IF unit 104 and output unit 105 also exist in the payment agency system 11, end user terminal 12 and customer device 13, but descriptions of these will be omitted in this specification.
[0027] The customer-specific display information 106 stores information on one or more authentication items for identifying an end user, which are set by each customer. The data in the customer-specific display information 106 may differ for each customer. FIG. 3 is a diagram for explaining an example of the data structure of the customer-specific display information 106. The customer-specific display information 106 may include a customer ID 301, an authentication item name N302, and an authentication item name before change N303, but is not limited to these data items and may also include other data items. For example, it may also include information such as the display start date and display period (such as the display start date to display end date) of the authentication item name to be displayed to the end user.
[0028] The customer ID 301 is an identifier for identifying a customer who uses the payment information registration and reception service provided by the payment processing device 10 according to the present invention. As described above, the customer is not limited to a company, but refers to any entity such as a local government or a non-profit organization. The authentication item name N302 is an item name selected by the customer in the payment information registration and reception service, and indicates the item name displayed to the customer's end user. N represents a natural number, and for example, if there are three authentication item names selected by the customer, the authentication item name N302 can indicate a first authentication item name, a second authentication item name, and a third authentication item name.
[0029] The authentication item name before change N303 indicates the name of each authentication item before the change when the authentication item name selected by the customer is changed. The payment information registration reception service has multiple default authentication item names, and the customer can decide the number of authentication items to prompt the end user to enter, select that number of authentication items, and change the names of the selected authentication items as desired. For example, in the payment information registration reception service, if the authentication item name that was initially displayed as "customer number" is changed to something like "student ID number," the name of the authentication item before the change becomes "customer number." The name of the authentication item before the change is not shown to the end user.
[0030] Returning to FIG. 2, the authentication master billing information 107 stores authentication master information and billing information of each user associated with authentication information specified by the customer. Since the data of the authentication master billing information 107 includes authentication information specified by the customer, the contents of the data format may differ depending on the customer. FIG. 4 is a diagram explaining an example of the data structure of the authentication master billing information 107. The authentication master billing information 107 can include a customer ID 301, a user ID 401, an authentication item name N302, user authentication information N402, a payment method flag 403, and payment method information 404, but is not limited to these data items and can also include other data items.
[0031] As described above, the customer ID 301 is an identifier for identifying a customer who uses the payment information registration and reception service. The user ID 401 is an identifier for identifying an end user of the customer. The authentication item name N302 is an authentication item name selected by the customer as described above, and indicates the authentication item name displayed to the end user of the customer. The user authentication information N402 indicates authentication information (e.g., customer number, name, telephone number, etc.) corresponding to the authentication item name N302. N is a natural number, and when the number of authentication item names selected by the customer is 2, the user authentication information N402 includes first user authentication information and second user authentication information. The payment method flag 403 indicates a payment method (e.g., direct debit, credit card payment) selected by the user for continuous charges by the customer. The payment means information 404 indicates information on a payment means corresponding to the information of the payment method flag 403, such as bank account information, credit card number, etc. In embodiments in which bank account information or credit card number is stored in payment agency system 11, payment method information 404 may include an identifier of the payment agency system performing the storage, and information for identifying the bank account information or credit card number.
[0032] (Processing details of payment information registration reception service) FIG. 5 is a flow diagram illustrating the processing of the payment information registration reception service executed by payment processing device 10. As shown in FIG.
[0033] In S501, the payment processing device 10 provides the authentication item setting screen 600 to the customer device 13 in response to a request from the customer device 13, and allows the customer to select a desired authentication item. The payment processing device 10 has a plurality of authentication items that can be used in the payment information registration reception service. The customer determines the number of authentication items that the end user is prompted to input according to the type of business or service content of the customer, and selects the determined number of authentication items from the plurality of available authentication items. Furthermore, the customer can change the authentication item names of the selected authentication items as necessary. FIG. 6 illustrates an authentication item setting screen 600 for the customer to select one or more arbitrary authentication items from the plurality of authentication items and change the names of the authentication items.
[0034] The authentication item setting screen 600 includes user authentication item candidates 601, user authentication required items 602, a change title 603, and a registration button 604. The user authentication item candidates 601 indicate a plurality of authentication items that are predefined by the payment processing device 10 and can be used in the payment information registration reception service. The user authentication required items 602 indicate authentication items selected by the customer from among the authentication items indicated in the user authentication item candidates 601. The user authentication required items 602 can be used to add new authentication items or delete existing authentication items by an operator operation. The change title 603 indicates a name obtained by changing the name of the customer-selected authentication item indicated in the user authentication required items 602 to a name that is easy for an end user to understand according to the business type and service contents of the customer. The registration button 604 is a button for performing a registration process in which the content selected and input by the customer is stored in the customer-specific display information 106.
[0035] Payment processing device 10 stores one or more authentication items selected by the customer on authentication item setting screen 600 in customer-specific display information 106, and can also receive an authentication item name changed by the customer for any of the one or more authentication items, and store the name in customer-specific display information 106. One or more authentication items selected by the customer on authentication item setting screen 600 are displayed to the end user.
[0036] In S502, payment processing device 10 receives authentication master information from customer device 13 and stores it in authentication master billing information 107. The authentication items included in the authentication master information are the authentication items selected by the customer in S501, and the authentication master information includes authentication information of each user associated with the customer. Payment processing device 10 can transmit a data format for registering the authentication master information to customer device 13, and can also provide a registration screen for registering the authentication master information, although the method is not particularly limited.
[0037] In S503, in response to the authentication master information being stored in authentication master billing information 107, payment processing device 10 generates access information (e.g., a URL) for the customer to access the payment information registration acceptance service and transmits it to customer device 13. The customer's access information includes information that can identify the customer. In response to receiving the access information for the customer, customer device 13 notifies the customer's user of the access information via any communication means such as email.
[0038] In S504, in response to a user access based on customer access information (e.g., a URL) from the end user terminal 12, the payment processing device 10 provides the end user terminal 12 with a login screen 700 associated with the access information. In detail, the payment processing device 10 identifies customer information associated with the user access, reads out the authentication item name N302 associated with the identified customer information from the customer-specific display information 106, and dynamically configures the login screen 700 described below to display the read authentication item name, and provides the login screen 700 to the end user terminal 12. If the content of the authentication item name N302 has been changed by the customer as described above, the changed name may be displayed on the login screen 700.
[0039] FIG. 7 illustrates a login screen 700 in which an end user inputs a user ID and authentication information set by a customer. The login screen 700 includes a user information input field 701 and a login button 702. The user information input field 701 is a field for inputting a user ID and one or more authentication items set by a customer. The login button 702 is a button for starting an authentication process based on the information input in the user information input field 701. The user ID is a user identifier assigned to the end user by the customer. The one or more authentication items indicate authentication items selected by the customer in the authentication item setting screen 600. In other words, the authentication items are items arbitrarily selected by the customer, and the names of the authentication items can be set by the customer, so that the contents displayed on the login screen 700 may differ for each customer. The part marked "authentication item 1" in FIG. 7 can display the name set by the customer in the change title 603 of the authentication item setting screen 600 in FIG. 6.
[0040] The payment processor 10 receives the user ID and one or more authentication items entered by the end user.
[0041] In S505, the payment processing device 10 queries the authentication master billing information 107 based on the customer ID associated with the login screen 700 and the input user ID, identifies user information, and reads out the user ID 401, authentication item name N302, and user authentication information N402 of the identified user information. The payment processing device 10 compares the user ID and one or more authentication items input via the login screen 700 with the read out user ID 401, authentication item name N302, and user authentication information N402 to determine whether they match. If they match, the process proceeds to S506, whereas if they do not match, a message indicating login failure is displayed on the login screen 700, and the process returns to S504 to display a message prompting re-input.
[0042] At S506, after the authentication process is successfully completed, the payment processing device 10 provides a service application and payment method selection screen 800 to the end user terminal 12. Figure 8 illustrates an example of the service application and payment method selection screen 800 on which the user selects a payment method and inputs payment information (e.g., account information, credit card information, etc.) corresponding to the selected payment method.
[0043] Service application and payment method selection screen 800 includes payment method 801, settlement information 802, and registration button 803. Payment method 801 includes a payment method selection field for recurring charges. Any payment method can be selected in the payment method selection field. In the example of FIG. 8, an example is shown in which direct debit and credit card can be selected, but any other payment method such as debit card and electronic money may also be selectable. Furthermore, service application and payment method selection screen 800 may display on the screen and change the information to be entered / selected based on the content of the service provided by the customer.
[0044] Payment information 802 is a field for inputting payment information corresponding to the payment method selected in payment method 801. For example, account information for direct debit or card information for credit card payment may be input in payment information 802. The system in which the input information is registered may differ depending on the type of information input. For example, account information for direct debit may be registered in payment agency system 11, and credit card information may be registered in payment processing device 10, but is not limited to these embodiments. Register button 803 is a button for storing and processing the information input in service application and payment method selection screen 800 in a predetermined storage location, for example, payment processing device 10 or payment agency system 11.
[0045] In response to pressing of the register button 803, the payment processing device 10 can store the information entered on the service application and payment method selection screen 800 in the authentication master billing information 107. The payment processing device 10 can also transmit the entered information to the payment agency system 11 for registration. Note that in the example of FIG. 8, the service application and payment method selection screen 800 shows input fields for the payment method, account information for direct debit, and credit card information, but the present invention is not limited to this example of screen 800. For example, the items displayed on the screen may be divided according to the storage destination where the information is registered.
[0046] In S507, in response to the completion of the storage process in the authentication master billing information 107, the payment processing device 10 can provide the stored information to the customer device 13. The information can be provided to the customer device 13 in a form in which the payment processing device 10 transmits a data set at a predetermined timing, or in a form in which a search is performed using a reference screen (not shown) and the target data is downloaded all at once. This allows the customer to generate an account transfer request for billing the user and transmit it to the payment agency system 11 when a predetermined due date arrives.
[0047] As another embodiment of the present invention, when a credit card is selected as the payment method for charging, the payment processing device 10 can store information required for card payment, i.e., card number, card expiration date, security code, etc., in the payment method information 404 and provide it to the customer device 13, or the card number, card expiration date, security code, etc. can be stored in the payment agency system 11, and information specifying information such as the identifier of the payment agency system 11 where the information is stored and the card number can be stored in the payment method information 404 and provided to the customer device 13. When processing charges for the end user, the customer device 13 will send an authorization message and a sales message to the corresponding card company, in the same way as in conventional card payments.
[0048] 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]
[0049] 10 Payment processing device 11 Payment processing system 12 End-user terminals 13 Customer equipment 101 Control section 102 Main memory 103 Auxiliary storage 104 IF Section 105 Output section 106 Display information by customer 107 Authentication Master Billing Information
Claims
1. A payment processing device including a communication unit for communicating with an external network, a storage unit, and a control unit, the storage unit stores display control information and authentication master information; The control unit is Providing a plurality of authentication items selectable by a customer to a customer device via the communication unit, wherein the names of the authentication items can be changed by the customer; receiving, via the communication unit, from the customer device, one or more customer-selected authentication items which are authentication items selected by the customer from among the plurality of authentication items, and at least one of the names of the one or more customer-selected authentication items has been changed by the customer; storing the one or more received customer selected authentication items in the display control information of the storage unit; dynamically configuring an authentication interface to include the one or more customer-selected authentication items associated with the customer in response to user access of a user associated with the customer via the communication unit, and providing the authentication interface to a user device, wherein at least one of the names of the one or more customer-selected authentication items included in the authentication interface is a name that has been changed by the customer; 3. A payment processor configured to:
2. The control unit is receiving, via the communication unit, first authentication information of each user associated with a first customer-selected authentication item among the one or more customer-selected authentication items from the customer device, and storing the first authentication information in the authentication master information; receiving second authentication information from the user device via the authentication interface; querying the authentication master information based at least on a user identifier included in the second authentication information to obtain the first authentication information of a user associated with the user identifier; Matching the acquired first authentication information with the acquired second authentication information; The payment processor of claim 1 , further configured to:
3. A payment processing device as claimed in claim 2, wherein the control unit is further configured to generate access information associated with the customer for the user access in response to the first authentication information of each user being stored in the authentication master information, and send the access information to the customer device.
4. A method executed by a payment processing device having a communication unit for communicating with an external network, a storage unit, and a control unit, comprising: the storage unit stores display control information and authentication master information; The control unit provides a plurality of authentication items selectable by a customer to the customer device via the communication unit, and the names of the authentication items can be changed by the customer; and the control unit receives from the customer device, via the communication unit, one or more customer-selected authentication items which are authentication items selected by the customer from among the plurality of authentication items, and at least one of the names of the one or more customer-selected authentication items has been changed by the customer; The control unit stores the received one or more customer selection authentication items in the display control information of the storage unit; the control unit dynamically configures an authentication interface to include the one or more customer-selected authentication items associated with the customer in response to user access by the user associated with the customer via the communication unit, and provides the configured authentication interface to the user device, wherein at least one of the names of the one or more customer-selected authentication items included in the authentication interface is a name that has been changed by the customer; A method for providing the above.
5. the control unit receives, via the communication unit, first authentication information of each user associated with a first customer-selected authentication item among the one or more customer-selected authentication items from the customer device, and stores the first authentication information in the authentication master information; the control unit receiving second authentication information from the user device via the authentication interface; the control unit queries the authentication master information based at least on a user identifier included in the second authentication information to obtain the first authentication information of a user associated with the user identifier; The control unit compares the acquired first authentication information with the acquired second authentication information; The method of claim 4 further comprising:
6. The method of claim 5, further comprising the control unit generating and transmitting access information associated with the customer for the user access to the customer device in response to the first authentication information of each user being stored in the authentication master information.
7. A program that causes a computer to execute a method according to any one of claims 4 to 6.
Citation Information
Patent Citations
Information processing method, information processing system, program and recording medium
JP2005157687A
Automatic transaction device
JP2006227769A
On-vehicle navigation device and own vehicle position correction method
JP2008032500A
JPP7349071B
