JP7340674B1 - Payment server and payment method - Google Patents

Abstract

An object of the present invention is to provide a payment server, an application program, and a payment method that can increase the possibility that a user will purchase products sold by an operator of a member store. [Solution] Stores setting information for a benefit set by a member of an electronic payment service that exempts the burden of installment interest fees when paying in installments using the electronic payment service, and provides the benefit at the request of the user. distributes a privilege ticket indicating the right to use the service, executes payment processing for electronically paying the user's payment to the member based on the payment information received via the communication network at the time of payment request, and in the payment processing, Among the user's past payments, those for which a bonus ticket has been obtained are identified as eligible payments for which the award is applied, and for the eligible payments, the user specifies the split method for the specified installment payment, which is the installment payment to which the award is applied. In this case, the payment server changes the payment method of the target payment to a specific installment payment using the specified division method. [Selection diagram] Figure 1

Description

The present invention relates to a payment server, an application program, and a payment method.

Conventionally, there are electronic payment systems that support electronic payment by operators of member stores. For example, Patent Document 1 proposes a system that performs product purchase processing after charging the balance when the purchaser's balance is less than the price of the product to be purchased.

Japanese Patent Application Publication No. 2020-115278

With conventional techniques, there have been cases in which it has not been possible to increase the possibility that a user will purchase a product sold by an operator of a member store.

The present invention has been made in consideration of these circumstances, and provides a payment server, an application program, and a payment method that can further increase the possibility that users will purchase products sold by member store operators. One of the purposes is to provide

One aspect of the present invention is a payment server that provides an electronic payment service, and is a benefit set by a member of the electronic payment service, in which the burden of installment interest fees is waived when paying in installments using the electronic payment service. a storage unit that stores setting information of the benefits to be provided; a benefit distribution unit that delivers a benefit ticket indicating the right to use the benefits to the terminal device in response to an acquisition request from the user's terminal device; and a communication network when requesting payment. a payment processing unit that executes payment processing for electronically settling the user's payment to the affiliate based on payment information received via the payment processing unit; Based on the payment history of the user and the distribution history of the benefit ticket, among the past payments made by the user, the payment for which the user has already obtained the benefit ticket is identified as the target payment to which the benefit is applicable. However, for the specified eligible payment, if the user specifies a split method for a specific installment that is an installment payment to which the benefit is applied, the payment method for the eligible payment will be changed to the specified installment using the specified split method. Change the payment server.

According to one aspect of the present invention, it is possible to provide a payment server, an application program, and a payment method that can further increase the possibility that a user will purchase products sold by an operator of a member store.

1 is a diagram illustrating an example of a configuration for realizing an electronic payment service. FIG. 1 is a sequence diagram (Part 1) illustrating the general flow of electronic payment. FIG. 2 is a sequence diagram (Part 2) illustrating the general flow of electronic payment. FIG. 1 is a configuration diagram of a payment server 100 according to a first embodiment. 3 is a diagram showing an example of the contents of user information 172. FIG. It is a diagram showing an example of the contents of member store/store information 176. 2 is a diagram illustrating an example of the configuration of a specific payment processing section 160. FIG. FIG. 3 is a diagram illustrating an example of a screen used by an operator of a member store when setting and registering benefits. FIG. 3 is a diagram showing an example of displaying benefit information on the user terminal device 10. FIG. 2 is a diagram illustrating an example of a process flow in which a payment server 100 and a user terminal device 10 cooperate to realize electronic payment by specific installment payment. FIG. It is a figure which shows the example of a transition of the screen displayed by the user terminal device 10 in electronic payment by a specific installment payment. FIG. 3 is a diagram showing the flow of money exchanges among members, payment providers, and users in specific installment payments. FIG. 2 is a diagram summarizing the contents of exchanges between a user, an operator of a member store, and an operator of an electronic payment service in a specific installment payment according to the embodiment.

DESCRIPTION OF THE PREFERRED EMBODIMENTS Embodiments of a payment server, an application program, and a payment method of the present invention will be described below with reference to the drawings. The application program and the payment server work together to provide electronic payment services. In the following description, the application program will be referred to as a payment application. An electronic payment service is a service that supports payments for purchases of products and services at stores. A store is, for example, a physical store (actual store) that exists in real space, but may also include a virtual store for electronic commerce. The virtual store may include one provided by an entity different from the operator of the electronic payment service (hereinafter also referred to as "payment operator"). In this case, when paying for shopping at the virtual store, the screen is controlled to transition to an interface screen of the electronic payment service. In an electronic payment service, a store is treated as belonging to a member store (brand), for example, and processing such as payment when a purchase is made at a store is mainly performed between a user and the member store. Alternatively, processing such as payment may be performed between the user and the store.

[Electronic payment service]
FIG. 1 is a diagram illustrating an example of a configuration for realizing an electronic payment service. The electronic payment service is realized mainly by the payment server 100. The payment server 100 communicates with each of the one or more user terminal devices 10, the one or more first store terminal devices 50, and the one or more second store terminal devices 70, for example, via the network NW. The network NW includes, for example, the Internet, a LAN (Local Area Network), a wireless base station, a provider device, and the like.

The user terminal device 10 is, for example, a portable terminal device such as a smartphone or a tablet terminal. The user terminal device 10 is a computer device having at least an optical reading function, a communication function, a display function, an input reception function, and a program execution function. In the following description, the configurations for realizing these functions are respectively referred to as a camera, a communication device, a touch panel, a CPU (Central Processing Unit), and the like. In the user terminal device 10, the payment application 20 is executed by a processor such as a CPU, so that the payment application 20 operates in cooperation with the payment server 100 to provide electronic payment services to the user. The payment application 20 is installed on the user terminal device 10 from an application store, for example, and controls a camera, a communication device, a touch panel, and the like.

The first store terminal device 50 is installed in a store, for example. The first store terminal device 50 is a computer device having at least a product price acquisition function, an optical reading function, a program execution function, and a communication function. The first store terminal device 50 includes a so-called POS (Point of Sale) device, and the POS device may realize a product price acquisition function and an optical reading function. The store code image 60 is placed in a store, and a code image such as a QR code (registered trademark) is printed on a paper or plastic medium. Note that the store code image 60 may be displayed on a display (or a display of a terminal device such as a smartphone) placed in the store.

The second store terminal device 70 is used by an operator of a member store (hereinafter referred to as a "member"). The second store terminal device 70 is a smartphone, a tablet terminal, a personal computer, or the like. In the second store terminal device 70, an interface 72 for member stores operates. The member store interface 72 may be an application for member stores or may be a browser. The member store interface 72 receives coupon settings and the like from the member and transmits them to the payment server 100. The second store terminal device 70, which is a smartphone, has the function of displaying a code image corresponding to the store code image and reading the code image displayed by the user terminal device 10 by executing an application for member stores. have

The payment server 100 realizes electronic payment based on payment information received from the user terminal device 10 or the first store terminal device 50. The first store terminal device 50 may include a POS device and a member store server, in which case payment information is transmitted from the POS device to the payment server 100 via the member store server. In the following description, it is assumed that payment information is transmitted from the first store terminal device 50 without making any particular distinction.

2 and 3 are sequence diagrams illustrating the general flow of electronic payment. There may be two patterns, pattern 1 and pattern 2, in electronic payment.

In the case of pattern 1 (hereinafter referred to as user scan) shown in FIG. 2, the user terminal device 10 with the payment application 20 activated decodes the store code image 60 using an optical reading function (S1). The store code image 60 includes information on a store URL (Uniform Resource Locator). This store URL is the domain of the electronic payment service added with information that can identify the store, and is associated with member store IDs, store IDs, etc. in the payment server 100 (described later). The payment application 20 transmits first payment information including the store URL and account ID to the payment server 100 (S2). The payment server 100 searches for store information (described later) from the member store ID and store ID corresponding to the store URL, obtains the member store name and store name information (S3), and sends the information to the payment application 20 (S4). . The user inputs the payment amount into the user terminal device 10 on the screen on which the member store name and store name are displayed (S5). Then, the user terminal device 10 generates second payment information including at least the payment amount and transmits it to the payment server 100 (S6). The payment server 100 performs electronic payment based on the received second payment information (S7). Then, the payment server 100 transmits a payment completion notification (information for displaying the payment completion screen) to the payment application 20 (S8), and the payment application 20 displays the payment completion screen (S9). Note that when the store code image 60 is displayed on a display placed in a store, the store code image 60 may include not only the store URL but also information on the payment amount. In this case, the step for the user to input the payment amount is omitted, and the first payment information includes information on the payment amount and is sent to the payment server 100. Information on the member store name and store name may be included and displayed on the payment completion screen.

In the case of pattern 2 (hereinafter referred to as store scan) shown in FIG. 3, when the payment application 20 is started, when a payment operation is performed on the payment application 20, and when the automatic update timing (for example, every minute) is reached. , and at other timings, the payment application 20 transmits a one-time code issuance request to the payment server 100 (S11). The payment server 100 generates a one-time code (S12) and sends it to the payment application 20 (S13). The payment application 20 displays a code image, such as a QR code or barcode, generated based on the one-time code (S14). The user holds up (presents) the display surface of the user terminal device 10 to the first store terminal device 50, and the first store terminal device 50 decodes the code image using an optical reading function and obtains a one-time code, etc. (S15). Then, the first store terminal device 50 generates payment information including a one-time code, payment amount, member store ID, store ID, etc., and transmits it to the payment server 100 (S16). Information on the payment amount is obtained in advance by barcode reading, manual input, etc. The payment server 100 identifies the user corresponding to the one-time code based on the received information and performs electronic payment (S17). Then, the payment server 100 transmits a payment completion notification to the payment application 20 (S18), and the payment application 20 displays a payment completion screen (S19).

Note that electronic payment may be performed using only one of the above patterns. Moreover, the "account ID" explained in FIG. 2 may be other information (for example, a telephone number) that can be used as user identification information. Furthermore, the issuance of a one-time code may be omitted in the store scan, and the payment application 20 may display a code image generated based on the user's account ID. In that case, the payment server 100 identifies the user corresponding to the account ID instead of identifying the user corresponding to the one-time code.

[Payment server]
FIG. 4 is a configuration diagram of the payment server 100 according to the first embodiment. The payment server 100 includes, for example, a communication section 110, a payment content providing section 120, a payment processing section 130, an information management section 140, and a storage section 170. Components other than the communication unit 110 and the storage unit 170 are realized by, for example, a hardware processor such as a CPU executing a program (software). Some or all of these components are hardware (circuit parts) such as LSI (Large Scale Integration), ASIC (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array), and GPU (Graphics Processing Unit). (including circuitry), or may be realized by collaboration between software and hardware. The program may be stored in advance in a storage device (a storage device with a non-transitory storage medium) such as an HDD (Hard Disk Drive) or flash memory, or may be stored in a removable storage device such as a DVD or CD-ROM. It may be stored in a medium (non-transitory storage medium), and installed in the storage device by loading the storage medium into a drive device.

The storage unit 170 is an HDD, flash memory, RAM (Random Access Memory), or the like. The storage unit 170 may be a NAS (Network Attached Storage) device that can be accessed by the payment server 100 via a network. The storage unit 170 stores information such as user information 172, payment content information 174, and member store/store information 176.

The communication unit 110 is a communication interface for connecting to the network NW. Communication unit 110 is, for example, a network interface card.

The payment content providing unit 120 has, for example, the function of a web server, and provides the user terminal device 10 with information (content) for displaying various screens of the electronic payment service. The payment content providing unit 120 reads necessary content from the payment content information 174 as appropriate and provides it to the user terminal device 10. The user terminal device 10 receives various inputs from the user while the content is being played by the payment application 20, and transmits the above-mentioned payment information and the like to the payment server 100.

The payment processing unit 130 performs payment processing based on the payment information transmitted by the user terminal device 10 or the first store terminal device 50. The payment processing unit 130 performs payment processing while referring to the user information 172.

FIG. 5 is a diagram showing an example of the contents of the user information 172. User information 172 is an example of user registration information. User information 172 includes, for example, user URL, account ID, phone number, password, email address, user ID, name/address/date of birth, registration date, charge balance, deferred payment setting, deferred payment limit, deferred payment. Information such as usage amount, available deferred payment amount, payment method settings, bank account, credit card number, charge history information, payment history information, and user benefit information are associated with each other. The user URL is used for remittance processing between users. When registering for a new electronic payment service, it is mandatory to register a phone number and password. The account ID is issued to the user by the payment server 100, and the user ID is an ID that can be arbitrarily set (or does not need to be set) by the user. Similarly, e-mail address, name, address, and date of birth are information that can (or does not need to be) set arbitrarily by the user. The registration date is the date the user registered with the electronic payment service (the date the account was created). Hereinafter, the user instance (electronic payment account) to which this information is associated will be referred to as an account.

The charge balance is information indicating the balance of electronic money set by the user transferring money to the account in advance. Methods of remittance include remittance from an ATM (Automatic Teller Machine) of a designated business (bank), remittance from a registered bank account, etc. The deferred payment setting is information indicating whether the settings for enabling electronic payment by deferred payment have been completed, and is set to either "completed" or "not yet". The deferred payment allowance is the maximum amount of deferred payment that can be used each month, the deferred payment usage amount is the amount of deferred payment that has already been used in the current month, and the available deferred payment amount is calculated by subtracting the deferred payment usage amount from the deferred payment allowance. , is the amount of deferred payment available for the current month. In the figure, only one deferred payment limit is shown, but in reality, there are additional daily upper limit amounts, and the lower of these may be set as the deferred payment limit. Further details of deferred payment will be discussed later. The payment method setting is setting information that indicates whether the user will perform electronic payment using the charge balance or payment by deferred payment at that time. The bank account and credit card number are each information about a bank account or credit card number (account number, card number) that can be used to deposit money into the electronic payment service. The charging history information is a history of the user increasing the charging balance by remitting money to the electronic payment service in advance. The payment history information is information that shows the details of the payments made by the user (date and time, store ID of the store where the purchase was made, payment amount, payment method, etc.) for each payment.

The user benefit information is information regarding a benefit notified to the target user by the benefit information distribution unit 162, which will be described later. The user benefit information includes information such as the identification information of the benefit, the distribution status of the benefit ticket to the user, the contents of settings regarding the use of the benefit ticket (usage settings), and the status of application for the benefit ticket. The privilege ticket is information indicating the right to use the privilege notified to the user, and is obtained by the user requesting the payment server 100 via the payment application 20.

FIG. 6 is a diagram showing an example of the contents of the affiliated store/store information 176. The affiliated store/store information 176 includes, for example, a first table 176A in which affiliated store IDs and store IDs are associated with store URLs, and affiliated store names and sales proceeds (described above) are associated with affiliated store IDs. A third table 176C in which store IDs are associated with store IDs, and a fourth table 176D in which member benefit information is associated with member store IDs. In addition to this information, the member store/store information 176 may include information such as the member store or store category, store location, payment pattern, and the like. Affiliate benefit information is information regarding benefits set by the affiliate. The member benefit information includes, for example, information such as the settings of the benefit and the conditions for applying the benefit to the user. Details of the settings for the benefit and the application conditions will be described later with reference to FIG. As illustrated in FIG. 6, member benefit information may include a plurality of benefits (for example, benefit A, benefit B,...) registered for each member, or one benefit (for example, benefit C). may be registered.

The information management unit 140 manages user information 172 and member store/store information 176 based on information acquired from the user terminal device 10 and the second store terminal device 70. The information management unit 140 adds, edits, deletes, etc. new records for the user information 172 and member store/store information 176.

[Electronic payment]
When payment information is acquired from the user terminal device 10 or the first store terminal device 50, the payment processing unit 130 refers to the user information 172 and acquires the "payment method setting" of the user. The payment processing unit 130 performs electronic payment as follows for a user whose "payment method setting" is set to "charge balance". The payment processing unit 130 performs electronic payment by, for example, decreasing the charge balance managed in association with the user ID and increasing the item value of the member store's sales proceeds. For example, the item value of the sales proceeds of a member store is not used as electronic money itself, but the amount corresponding to the item value of the sales proceeds is determined in a cycle according to the agreement between the member store and the electronic payment service. Money will be transferred to your bank account.

The payment processing unit 130 performs electronic payment in the following manner for users whose "setting information" is set to "deferred payment." Deferred payment is set up separately from "credit payment" in collaboration with a credit card company, which is a separate entity from the operator of the electronic payment service, and the operator of the electronic payment service is the creditor. , which allows electronic payments that do not depend on the charge balance within the deferred payment limit. Note that in order to receive the deferred payment service, the user may be required to obtain a credit card provided by the operator of the electronic payment service. The amount used for deferred payment is paid in one month's worth on the next month's payment date, for example, by debiting from a bank account. In this case, the payment processing unit 130 performs provisional payment by adding the payment amount to the deferred payment usage amount and subtracting the same amount from the available deferred payment amount, and on the closing date, the payment for the current month is transferred to the next month's payment date as described above. Process to withdraw the money. Note that if the payment amount exceeds the available deferred payment amount at the time of provisional payment, an error notification is sent back to the payment application 20.

In addition, in this embodiment, in addition to the above-mentioned payment methods such as "charge balance" and "deferred payment", "specific installment payment", which is installment payment that can be used with benefits, may be set as one of the payment methods. Specified installment payment, similar to the above-mentioned deferred payment, is set separately from "installment payment" in credit payment, and the member becomes the creditor and the member pays the interest rate of the installment within the predetermined allowable range. The fee will be borne by the applicant. Hereinafter, this default allowable range will be referred to as the "usage limit." The usage limit is set individually by the member providing the benefits, and the right to use specific installment payments is a benefit (hereinafter referred to as the "Instalment Interest Burden Exemption Benefit") for users who meet the specified usage conditions. ). Hereinafter, when the term "benefits" is simply used, it means the benefit of exemption from installment interest charges. Specified installment payment is applied by the user acquiring benefits in advance and exercising the right to use them at the time of payment. Note that the creditor in the specified installment payment may include the operator of the electronic payment service, and a part of the interest fee paid by the member in the specified installment payment may be borne by the operator of the electronic payment service.

In the payment server 100 of this embodiment, the payment processing unit 130 includes a normal payment processing unit 150 that realizes electronic payment using conventionally available general payment methods, such as the above-mentioned charge balance, deferred payment, and credit payment, and the above-mentioned A specific payment processing unit 160 that executes specific payment processing for electronic payment using specific installment payments is provided.

FIG. 7 is a diagram showing an example of the configuration of the specific payment processing section 160. The specific payment processing unit 160 includes, for example, a benefit registration unit 161, a benefit information distribution unit 162, a usage availability determination unit 163, a payment management unit 164, and a sales proceeds depositing unit 165. The benefit registration unit 161 registers benefit settings in the payment server 100 in response to a request from a member. More specifically, the benefit registration unit 161 accepts a benefit setting operation via the member store interface 72 of the second store terminal device 70 and stores the input setting information in the member store/store information 176. This registers the benefit settings in the payment server 100. For example, the benefit setting information is managed in association with the identification information (affiliate store ID, store ID) of the corresponding member store or store. In addition, the benefit setting information includes information such as the size of the usage limit for specific installment payments, the expiration date of the benefit, the conditions under which the user is eligible for the benefit, the options for payment method and number of payments, and the terms of use of the benefit. May be included.

If a member registers in the payment server 100 the setting of a benefit that exempts the installment interest burden by making a specific installment payment, the benefit information distribution unit 162 makes the benefit available to users to whom the benefit is applicable. Notify me of something. Specifically, the benefit information distribution unit 162 identifies users to whom the benefit can be applied based on the benefit setting information and user information 172 registered in the payment server 100, and Benefit information regarding benefits applicable to the terminal device 10 is distributed.

The availability determination unit 163 determines whether or not a benefit can be used by a user who has applied for benefit usage in connection with purchasing a product. For example, the availability determination unit 163 may determine availability of the benefit based on the determination results of the following first usage conditions and second usage conditions. The availability determination unit 163 may determine that the benefit can be used when either one of the first usage condition and the second usage condition is satisfied, or may determine that the benefit can be used when either one of the first usage condition and the second usage condition is satisfied. It may be determined that the benefit can be used when the following is satisfied. Further, the availability determining unit 163 may determine whether or not the benefit can be used based on a combination of the determination results of the following first usage conditions and second usage conditions and the determination results of other usage conditions.

(First Terms of Use)
The first condition of use is that the total amount of split interest fees that the member has borne (or has decided to bear) to date (hereinafter referred to as the "total amount borne") does not exceed the scope of the usage limit. . That is, the first usage condition is that the total amount of split interest fees paid by the member is less than the threshold amount that defines the usage limit. Here, the total burden of split interest fees is managed for each benefit, and the threshold amount is set for each benefit by the member. The specific payment processing unit 160 cumulatively updates the total burden each time an electronic payment by specific installment payment is carried out, and the availability determination unit 163 updates the total burden at that time and the threshold value when using a benefit. By comparing the amount with the amount, it can be determined whether or not the first usage condition is satisfied. In other words, the first usage condition can be simply said to be that there is a vacancy in the privilege usage slot.

(Second Terms of Use)
The second condition for use is that the user who applied for the benefit must be eligible for credit for specific installment payments. For example, the availability determining unit 163 can determine whether a user can receive credit by inquiring with an external credit institution. Further, for example, the availability determining unit 163 may be configured to determine whether credit is available on its own based on information such as payment history and payment history included in the user information 172.

The payment management unit 164 executes processing for settling the purchase price of the product in specific installments (hereinafter referred to as "specific payment processing") based on the determination result of the availability of the benefit by the availability determination unit 163. . More specifically, the payment management unit 164 refers to the payment history information and selects among the electronic payments (hereinafter referred to as "conducted normal payments") performed using a normal payment method (for example, payment from the charge balance). If a payment to which the benefit can be applied is identified and notified to the user, and the user applies for the benefit by specifying one of the notified standard payments that have been implemented, the payment method specified by the user Specified installment payments are applied after the fact to regular payments. When an application for the use of a benefit is made, the payment management section 164 uses the availability determining section 163 to recognize whether or not the benefit can be used at that time, and executes specific payment processing when it is determined that the benefit can be used.

Specific payment processing includes, for example, the first process of notifying the user of the payment history to which benefits can be applied, the second process of receiving applications for the use of benefits and deciding whether or not to apply benefit installments, and the monthly payment by specific installment payments. A third process is included to manage payments. For example, in the first process, the payment management unit 164 may specify completed normal payments performed within a period from the present to a predetermined point in the past as applicable targets for the specific installment payment. Furthermore, in the second process, the payment management unit 164 may accept an application for benefit use when a division method for a specific installment payment is specified. Further, when accepting the designation of a division method for a specific installment payment, the payment management unit 164 may calculate the monthly payment amount according to the designated division method and present it to the user. The monthly payment amount for installment payments with a credit card is the monthly installment amount of the purchase price plus the monthly installment interest fee depending on the number of payments; however, for specified installment payments, the installment interest fee is borne by the member. Therefore, the monthly payment amount for specific installment payments is calculated as a monthly installment of the purchase price.

Furthermore, in the third process, the payment management unit 164 executes a payment record management process and a monthly payment amount billing process. The payment management unit 164 collects the amount set as the monthly payment amount from the target user's charge balance when a predetermined payment date arrives in each month set corresponding to the number of payments. Generally, the monthly payment amount for credit card installment payments is the sum of the monthly installment amount of the purchase price and the monthly installment interest fee according to the number of payments. will pay the installment interest fee, so the monthly payment amount will be calculated as a monthly installment of the purchase price. The number of payments in a particular installment may be specified by the user. For example, the number of payments may be selected by the user from among predetermined options of the number of payments, similar to payment in installments using a credit card. In addition, as mentioned above, the specified installment payment of this embodiment is set separately from the credit card payment and does not require credit from the credit card company, so the number of payments is determined by the installment interest rate that the member pays. It may be something that the user can specify arbitrarily as long as it is possible to pay for it.

The sales proceeds depositing unit 165 performs processing for paying sales proceeds to the member of the sales agency based on the product purchase price received from the user by the payment management unit 164. More specifically, the sales proceeds depositing unit 165 deducts the usage fee for a service that allows the use of specified installment payments as a payment method in an electronic payment service (hereinafter referred to as "specific payment service") from the amount of the product purchase price. The amount received will be calculated as the sales proceeds that should be paid to the merchant's member. In other words, the operator of the electronic payment service further deducts an amount equivalent to the installment interest fee from the product purchase price paid through specified installment payments (purchase price exempted from the installment interest fee) as usage fee for the specified payment service. The amount will be credited to the member as sales proceeds. As a result, the operator of the electronic payment service temporarily assumes the burden of the installment interest fee until the full price of the product purchased through specified installment payment is received, and then pays the sales proceeds to the merchant member (deposit payment). ), the burden of split interest charges can be offset as usage fees for specified payment services. That is, in this embodiment, the operator of the electronic payment service provides the specified payment service to the member on the condition that the member pays the split interest fee on behalf of the user.

[Benefit settings by member]
FIG. 8 is a diagram illustrating an example of a settings registration screen G10 used by members when setting and registering benefits. The setting registration screen G10 is provided by the benefit registration unit 161, for example. The content necessary for the setting registration screen G10 may be stored in the storage unit 170 as part of the payment content information 174. For example, the settings registration screen G10 has various input interfaces G11 to G18 for inputting benefit setting information. For example, the input interface G11 is a text box that accepts input of the name of the benefit to be registered. Further, for example, the input interface G12 is a text box that accepts an input of the limit amount of the split interest fee that the member pays for the target benefit as the size of the usage limit for the target benefit. Further, for example, the input interface G13 is a text box that accepts input of the validity period of the target benefit. Further, for example, the input interface G14 is a text box that accepts input for setting the number of payments in a specific installment. FIG. 8 shows an example in which an upper limit on the number of payments and conditions for the purchase amount under which each upper limit is valid are set using the input interface G14. For example, in Figure 8, for purchases of less than 10,000 yen, 3 times is presented as the number of payment options, and for purchases of 10,000 yen or more but less than 100,000 yen, 3 times and 5 times are presented as the number of payment options. This is a setting example in which 3, 5, and 10 payments are presented as options for purchases of 100,000 yen or more. Further, for example, the input interface G15 is a check box that accepts input of settings for determining whether or not a benefit can be used depending on the type of purchased product. Furthermore, for example, the input interface G16 is a check box and a text box that accept input for setting conditions (application conditions) for users who can receive the benefit. Further, for example, the input interface G17 is a check box that accepts an input for setting whether or not to include "monthly fixed amount payment" as a payment method option for a specific installment payment. Note that the monthly fixed amount payment here is a payment method in which the monthly payment amount is approximately constant regardless of whether or not a product is purchased, the amount, the number of purchases, etc. The fixed monthly payment may be a so-called revolving payment. If a fixed monthly payment can be used for specified installment payments, the user can maintain the same monthly payment amount while enjoying the benefit of being exempt from installment interest charges. Further, for example, the input interface G18 is a button that accepts an input of an operation instructing registration of a benefit based on the input settings. In response to the input interface G18 being pressed, the benefit registration unit 161 registers the input setting information in the member store/store information 176 in association with the member store ID, store ID, and the like.

FIG. 9 is a diagram showing a privilege notification screen G20 as an example of display of privilege information on the user terminal device 10. As described above, the benefit information is distributed by the benefit information distribution unit 162 to users to whom the benefit is applicable in response to the benefit settings being registered in the payment server 100. The benefit notification screen G20 is provided by the benefit information distribution unit 162, for example. The content necessary for the benefit notification screen G20 may be stored in the storage unit 170 as part of the payment content information 174. For example, the benefit notification screen G20 includes a display interface G21 for information regarding the benefit, and an input interface G22 for operations regarding the use of the benefit.

For example, the display interface G21 includes a display area for an image IMG1 related to the member store that provides the benefit, and a display area for text information indicating the content of the benefit. Through such a display interface G21, the user can recognize the member store that provides the benefit, and also that the member store will be responsible for the interest and fees for the installment payment, and that the total amount to be borne by the member store. There is an upper limit, and you can be aware that the benefits will end as soon as the total burden reaches the upper limit. The input interface G22 is a button that accepts an input for an operation to acquire the right to use the benefit (hereinafter referred to as a "privilege ticket"). The input interface G22 transmits a privilege ticket acquisition request to the payment server 100 in response to the button being pressed. The payment server 100 not only responds to the payment application 20 to the effect that the request for obtaining a privilege ticket has been received, but also records and manages the fact that the user has obtained a privilege ticket in the payment server 100. In the payment server 100, the specific payment processing unit 160 recognizes the bonus ticket that the user has already acquired, and notifies the payment application 20 of the completed normal payment to which the benefit related to the bonus ticket can be applied. The user can specify the target for which he/she will apply for the benefit from among the completed normal payments notified in this way. The fact that a user has acquired a benefit ticket means that, for example, the identification information of the benefit, the identification information of the member store providing the benefit, the information indicating the validity period of the benefit, etc. are recorded in association with the user's identification information. Managed by.

[Flow of electronic payment by specified installment payment]
FIG. 10 is a diagram showing an example of a process flow in which the payment server 100 and the user terminal device 10 cooperate to realize electronic payment by specific installment payment. Moreover, FIG. 11 is a diagram showing an example of transition of the screen displayed by the user terminal device 10 in electronic payment by specific installment payment. The processing flow in FIG. 10 will be described below with appropriate reference to the screen transition example in FIG. 11. It is assumed that at the start of the processing flow shown in FIG. 10, the normal payment to which the benefit is applied has already been performed. First, in the user terminal device 10, the payment application 20 receives an input operation for displaying the payment history of electronic payments made by the user using the electronic payment service (S101). Subsequently, the payment application 20 transmits a payment history inquiry request to the payment server 100 in response to the input of this operation (S102).

Subsequently, in the payment server 100, the specific payment processing unit 160 acquires the user's payment history information from the user information 172 (S103), and recognizes the privilege ticket already acquired by the user (S104). Subsequently, the specific payment processing unit 160 refers to the acquired payment history information, identifies completed regular payments that are candidates for application of the benefits related to the acquired benefit ticket (S105), and The payment history information of the user including the payment is notified to the payment application 20 (S106). Here, the regular payment that has been made to which the benefit is applied may be specified as a regular payment that was made within a period from the present to a predetermined point in the past, as described above, or may be specified as a regular payment that was made within a period from the present to a predetermined point in the past, or may be determined based on such timing conditions. In addition, it may be specified as a normal payment that satisfies the conditions for product sales by the affiliate, such as the product type, product price, and store where it is sold. Next, in the user terminal device 10, the payment application 20 uses the history information of the regular payments made by the user, based on the payment history information notified from the payment server 100, to calculate the benefits for each regular payment. Applicability is displayed on the user terminal device 10 in a recognizable manner (S107).

For example, the payment application 20 displays the balance history screen G30A illustrated in FIG. 11 in step S107. For example, the balance history screen G30A is a screen that shows the update history of the user's charge balance. The balance history screen G30A is an example in which a history H31 of withdrawals from completed normal payments and a history H32 to H34 of point allocation are displayed. In addition, the balance history screen G30A may display a history of deposits by charging, a history of point usage, and the like. At this time, if the payment application 20 recognizes in step S104 that there is an acquired bonus ticket, it notifies that the bonus ticket is available for the payment history. For example, the balance history screen G30A is an example in which the payment application 20 notifies by displaying a benefit notification G31 that a benefit ticket can be used for payment of the payment history H31.

In this case, the user who sees the balance history screen G30A recognizes that a special installment benefit ticket can be used to pay for the payment history H31, and selects the payment history H31 to apply for the use of the benefit ticket. . When the payment history H31 is selected on the balance history screen G30A, the payment application 20 then displays a detailed screen G30B that leads to an application for the benefit related to the benefit notification G31 notified about the payment history H31. The detailed screen G30B includes, for example, detailed information G32 regarding the selected payment history H31 and a button G33 for accepting the designation of a division method for a specific installment payment related to the target benefit. In addition to the illustrated information, the detailed information G32 may include information such as payment date and time, number of acquired points, store, and purchased products.

Subsequently, the payment application 20 accepts the designation of the division method for the completed regular payment to which the benefit can be applied (S108), and also accepts an application for the use of the benefit ticket (S109). The payment application 20 requests the payment server 100 to apply a specific installment payment according to the specified division method for the specified regular payment that has been performed (S110: application for use of a benefit ticket). In the payment server 100 that receives the application for the use of the benefit ticket, the specific payment processing unit 160 determines whether the benefit can be used at that time (S111), and if it is determined that the benefit is available, the specified payment processing unit 160 determines whether the benefit can be used at that time. For the completed normal payment, a specific installment payment using the specified splitting method is applied (S112).

For example, when the button G33 is pressed on the details screen G30B, the payment application 20 displays an application screen G30C for specifying a division method and accepting an application for using a benefit ticket. The application screen G30C includes, for example, a monthly display section G34 that updates the display of the monthly payment amount according to the selected division method, a button group G35 that presents multiple options regarding the division method, and a button group G35 that displays multiple options for the division method selected. button G36 for accepting an application for the use of the bonus ticket. The application screen G30C shown in FIG. 11 is an example in which 33,333 yen is displayed as the monthly payment amount in accordance with the state where 3 times is selected as the division method for the total payment amount of 100,000 yen. Further, the application screen G30C shown in FIG. 11 represents a state where the button G36 is pressed with the number of divisions of three times being selected as the division method. In this case, the payment application 20 applies for the use of a benefit ticket for the completed normal payment related to the payment history H31 so that the specified installment payment is made with the selected number of installments of 3 times.

Note that in the example of FIG. 10, if there are multiple completed normal payments that are candidates for the benefit application, the payment application 20 accepts the selection of the target to apply for the benefit from among the notified candidates, It is also possible to accept the designation of the division method for the selected normal payment. Further, the candidates to which the benefit is applied may be recognized on the user terminal device 10 side. In this case, for example, the payment application 20 identifies the candidate regular payment that has been made in the same manner as in step S105, and if the award ticket has been acquired on the user terminal device 10, the payment application 20 selects the target payment and The specification of the division method may also be accepted.

FIG. 12 is a diagram showing the flow of money exchanges among members, payment providers, and users in specific installment payments of this embodiment. In this figure, solid line arrows indicate money exchanges, and dashed line arrows indicate application for benefit tickets. Furthermore, the numbers in parentheses [] in the figure represent the financial balance of each party based on the start of the exchange. First, the user pays the payment amount (100,000 yen in this example) by electronic payment using a normal payment method (this payment will become a completed normal payment from now on) (S201). As a result of this payment, 100,000 yen is collected from the user's charge balance, so the user's balance at this point is [-100,000]. On the other hand, the payment provider deposits the 100,000 yen collected from the user into the member's account as sales proceeds (S202). As a result, the payment provider's balance becomes [±0], and the member's balance becomes [+100,000] due to the receipt of this sales proceeds.

The above is the flow of money at the time of the first payment, which is a completed normal payment. After that, the user checks his or her own payment history and recognizes that the award ticket can be used for the regular payment that has been made, and specifies the splitting method to the payment provider. An application for the use of a bonus ticket is made (S203). Step S203 is not a flow of money, so it is represented by a broken line arrow. The payment provider accepts this usage application and applies the specified installment payment to the completed normal payment (S204). In addition, here, the explanation will be continued assuming that the user specifies the number of times of division as three times as the division method when applying for the use of the bonus ticket.

Subsequently, the first payment timing T1 for the specific installment payment arrives. At the payment timing T1, the payment provider refunds to the user an amount of 66,667 yen, which is obtained by offsetting the first payment amount of 33,333 yen from the 100,000 yen already collected from the user in the completed normal payment (S205). As a result, at the payment timing T1, the user has substantially paid the first payment amount of 33,333 yen. That is, at payment timing T1, the user's balance becomes [-33333]. On the other hand, the payment provider collects the interest fee α yen for the first split from the member (S206). As a result, at the payment timing T1, the member's balance becomes [+100000-α], and the payment provider's balance becomes [-66667+α]. Here, α is an example of the amount obtained by dividing the total amount of split interest fees proportionally by the number of payments. Note that the amount collected monthly from members as split interest fees may be a different amount each month. For example, in this case, the amount to be collected monthly may be set to be larger at later payment timings. Further, the total amount of the split interest fee may be paid in one lump sum at any one payment timing.

Subsequently, the second payment timing T2 for the specific installment payment arrives. At the payment timing T2, the payment provider collects the second payment amount of 33,334 yen from the user (S207). Here, the fractional amount of 1 yen divided into three payments is collected at the second payment, but the fractional amount may be collected at any time from the first to the third payment. As a result, at payment timing T2, the user's balance becomes [-66667]. On the other hand, the payment provider collects the interest fee α yen for the second split from the member (S208). As a result, at the payment timing T2, the member's balance becomes [+100000-2α], and the payment provider's balance becomes [-33333+2α].

Subsequently, the third payment timing T3 for the specific installment payment arrives. At payment timing T3, the payment provider collects the third payment amount of 33,333 yen from the user (S209). As a result, at payment timing T3, the balance of the user becomes [-100000]. On the other hand, the payment provider collects the third installment interest fee α yen from the member (S210). As a result, at the payment timing T3, the member's balance becomes [+100000-3α], and the payment provider's balance becomes [+2α].

As a result of such money exchange, the member will bear the split interest fee for the user's payment amount of 100,000 yen, and the payment provider will specify the split interest fee to be borne by the member in the electronic payment service. A member is charged a service usage fee when using installment payment, and the user can pay the purchase price without having to pay the installment interest fee.

FIG. 13 is a diagram summarizing the contents of the exchange between the user, the member, and the operator of the electronic payment service in the specific installment payment according to the embodiment. Such interaction is realized by the user terminal device 10, the first store terminal device 50, the second store terminal device 70, and the payment server 100 executing the above-mentioned processing. By realizing such exchange, the specific installment payment of the embodiment is realized. In FIG. 13, the user corresponds to the user terminal device 10 or the payment application 20, the member corresponds to the first store terminal device 50 or the second store terminal device 70, and the operator of the electronic payment service corresponds to the payment server 100. This corresponds to

First, a member registers a benefit in the payment server 100 using the second store terminal device 70 (S61). The payment server 100 identifies users to whom the registered benefits are applicable, and distributes benefit information regarding the applicable benefits to the user terminal devices 10 of the identified users (S62). Note that, as described above, the results of checking the credit risk for the user may be taken into consideration as the conditions for determining that the benefit is applicable to the user. The user checks the benefit information distributed from the payment server 100, and (if necessary) acquires a benefit ticket to the user terminal device 10 (S63). The exchanges up to this point are carried out before the user makes a specific installment payment.

Next, the user makes a payment to the member store by electronic payment using a normal payment method (for example, payment from the charge balance) (S71: normal payment). After performing the normal payment, the user applies for the use of a bonus ticket to the payment server 100 for the normal payment (S72). If the benefit ticket is available, the payment server 100 applies a specific installment payment to the normal payment using the division method specified by the user (S73: benefit application). That is, in this case, the normal payment in step S71 becomes the completed normal payment to which the benefit is applied.

Subsequently, the payment server 100 performs a billing process for monthly payment in specific installments for the completed normal payment, and the payment is completed when the set number of payments has been received (S81). Note that if the user has set an automatic deposit operation when the charge balance is insufficient (so-called auto charge), if the charge balance is insufficient at the time of monthly payment, the payment server 100 will The charge may be debited after depositing money into the charge balance from the user account at the financial institution. The operator of the electronic payment service deducts the amount equivalent to the split interest fee as a service fee from the amount paid by the user and deposits the amount as sales proceeds into the member's account (S82).

In addition, in FIG. 13, for the sake of simplicity, the image is shown in which the user makes a monthly payment to the payment provider as the specific installment payment in step S81, but as explained in FIG. 12, the user Since the payment has already been made to the member at the time of normal payment (S71), the payment provider gives the user a rebate for installment payment (S205). Similarly, payments of service usage fees from member stores to payment providers are made on a monthly basis in accordance with monthly payments.

According to the embodiment described above, it is possible to apply payment by specific installment payment, which exempts the user from paying the installment interest fee, to the regular payment made by the user who meets the application conditions of the benefit, so that the member can It is possible to further increase the possibility that users will purchase products sold by those who sell products.

Although the mode for implementing the present invention has been described above using embodiments, the present invention is not limited to these embodiments in any way, and various modifications and substitutions can be made without departing from the gist of the present invention. can be added.

DESCRIPTION OF SYMBOLS 10... User terminal device, 20... Payment application, 50... First store terminal device, 60... Store code image, 70... Second store terminal device, 72... Interface for member stores, 100... Payment server, 110... Communication department , 120...Payment content providing unit, 130...Payment processing unit, 140...Information management unit, 150...Normal payment processing unit, 160...Specific payment processing unit, 161...Benefit registration unit, 162...Benefit information distribution unit, 163...Usage Possibility determination unit, 164...Payment management unit, 165...Sales deposit unit, 170...Storage unit, 172...User information, 174...Payment content information, 176...Store information

Claims (12)

A payment server that provides electronic payment services,
a storage unit that stores setting information of a benefit set by a member of the electronic payment service, which exempts the burden of installment interest fees when paying in installments using the electronic payment service;
a benefit distribution unit that distributes a benefit ticket indicating the right to use the benefit to the terminal device in response to an acquisition request from the user's terminal device;
a payment processing unit that executes payment processing for electronically settling the user's payment to the affiliate based on payment information received via a communication network at the time of the payment request;
Equipped with
The payment processing unit is
Based on the payment history of the user and the distribution history of the benefit ticket, among the completed payments that the user has made in the past, the payment for which the user has already acquired the benefit ticket is classified as a payment history of the benefit ticket. Identification as a covered payment that is applicable;
For the identified target payment, if the user specifies a split method for a specific installment payment that is an installment payment to which the benefit is applied, the payment method for the target payment is changed to the specific installment payment using the specified split method. It is a thing,
When the payment of the user's payment is completed by the payment processing and the payment satisfies the conditions for applying the benefit, a screen indicating the completion of the payment is displayed, and a user interface for accepting an application to use the benefit is displayed. displaying a payment completion screen including the payment completion screen on the user's terminal device in response to the user's operation;
When the payment processing unit receives an application for the use of the benefit through the user interface, the payment processing unit accepts the designation of the division method related to the benefit, and changes the payment method of the payment to the specific installment payment using the division method. do,
Payment server. A payment server that provides electronic payment services,
a storage unit that stores setting information of a benefit set by a member of the electronic payment service, which exempts the burden of installment interest fees when paying in installments using the electronic payment service;
a benefit distribution unit that distributes a benefit ticket indicating the right to use the benefit to the terminal device in response to an acquisition request from the user's terminal device;
a payment processing unit that executes payment processing for electronically settling the user's payment to the affiliate based on payment information received via a communication network at the time of the payment request;
Equipped with
The payment processing unit is
Based on the payment history of the user and the distribution history of the benefit ticket, among the completed payments that the user has made in the past, the payment for which the user has already acquired the benefit ticket is classified as a payment history of the benefit ticket. Identification as a covered payment that is applicable;
For the identified target payment, if the user specifies a split method for a specific installment payment that is an installment payment to which the benefit is applied, the payment method for the target payment is changed to the specific installment payment using the specified split method. It is a thing,
A payment history screen showing the user's payment history, each history linked to a respective payment completion screen, and displaying the history that satisfies the application conditions of the benefit among the payment history in an identifiable manner. displaying a screen on the user's terminal device;
a user interface for accepting an application for the use of the benefit is displayed on the payment completion screen linked to the history that satisfies the application conditions of the benefit;
When an application for the use of the benefit is made through the user interface with respect to a history that satisfies the conditions for applying the benefit among the payment history displayed on the payment history screen, accepting the designation of the division method for the benefit; , changing the payment method of the payment to the specific installment payment according to the division method;
Payment server. A payment server that provides electronic payment services,
a storage unit that stores setting information of a benefit set by a member of the electronic payment service, which exempts the burden of installment interest fees when paying in installments using the electronic payment service;
a benefit distribution unit that distributes a benefit ticket indicating the right to use the benefit to the terminal device in response to an acquisition request from the user's terminal device;
a payment processing unit that executes payment processing for electronically settling the user's payment to the affiliate based on payment information received via a communication network at the time of the payment request;
Equipped with
The payment processing unit is
Based on the payment history of the user and the distribution history of the benefit ticket, among the completed payments that the user has made in the past, the payment for which the user has already acquired the benefit ticket is classified as a payment history of the benefit ticket. Identification as a covered payment that is applicable;
For the specified eligible payment, if the user specifies a splitting method for a specific installment payment that is an installment payment to which the benefit is applied, the payment method for the eligible payment will be changed to the specific installment payment using the specified splitting method. , the payment of the usage fee imposed on the member regarding the use of the specified installment payment is offset by having the member bear the installment interest fee related to the specified installment payment;
Collecting an amount obtained by dividing a split interest fee according to the number of payments in the splitting method in proportion to the number of payments from the member in accordance with the monthly payment by the specific installment payment;
Payment server. The payment information is generated based on information read by the user's terminal device from the two-dimensional code presented by the member,
The payment processing unit obtains the payment information from the user's terminal device.
The payment server according to any one of claims 1 to 3 . The payment information is generated based on information read by the member's store terminal device from a two-dimensional code presented by the user's terminal device,
The payment processing unit obtains the payment information from the member's store terminal device.
The payment server according to any one of claims 1 to 3 . The payment processing unit, in the first payment by the specific installment payment, uses the amount that is obtained by offsetting the monthly payment amount according to the number of payments in the payment method from among the amount paid by the user in the target payment. rebate to the person,
The payment server according to any one of claims 1 to 3 . The system further includes a benefit registration unit that receives registration of the benefit settings for each member of the electronic payment service.
The payment server according to any one of claims 1 to 3 . The benefit distribution unit identifies users to whom the benefit is applicable from among the users of the electronic payment service based on the configuration information of the benefit, and transmits the applicable benefit to the terminal device of the identified user. Distributing benefit information that encourages acquisition of the benefit ticket regarding the benefit;
The payment server according to any one of claims 1 to 3 . The payment processing unit notifies the terminal device of payments performed within a predetermined period from the current payment date among the completed payments as candidates for the target payment, and selects the target payment selected from the candidates. Regarding payment, change the payment method mentioned above,
The payment server according to any one of claims 1 to 3 . A payment server that provides electronic payment services is
storing setting information of a benefit set by a member of the electronic payment service, which exempts the burden of installment interest fees when paying in installments using the electronic payment service;
delivering a benefit ticket indicating the right to use the benefit to the terminal device in response to an acquisition request from the user's terminal device;
executing a payment process for electronically settling the user's payment to the member based on the payment information received via the communication network at the time of the payment request;
In the payment processing,
Based on the payment history of the user and the distribution history of the benefit ticket, among the completed payments that the user has made in the past, the payment for which the user has already acquired the benefit ticket is classified as a payment history of the benefit ticket. Identification as a covered payment that is applicable;
For the identified target payment, if the user specifies a split method for a specific installment payment that is an installment payment to which the benefit is applied, the payment method for the target payment is changed to the specific installment payment using the specified split method. It is a thing,
When the payment of the user's payment is completed by the payment processing and the payment satisfies the conditions for applying the benefit, a screen indicating the completion of the payment is displayed, and a user interface for accepting an application to use the benefit is displayed. Displaying a payment completion screen including the payment completion screen on the user's terminal device in response to the completion of the payment,
when an application for the use of the benefit is accepted through the user interface, accepting the designation of the division method for the benefit, and changing the payment method of the payment to the specific installment payment according to the division method;
Payment Method. A payment server that provides electronic payment services is
storing setting information of a benefit set by a member of the electronic payment service, which exempts the burden of installment interest fees when paying in installments using the electronic payment service;
delivering a benefit ticket indicating the right to use the benefit to the terminal device in response to an acquisition request from the user's terminal device;
executing a payment process for electronically settling the user's payment to the member based on the payment information received via the communication network at the time of the payment request;
In the payment processing,
Based on the payment history of the user and the distribution history of the benefit ticket, among the completed payments that the user has made in the past, the payment for which the user has already acquired the benefit ticket is classified as a payment history of the benefit ticket. Identification as a covered payment that is applicable;
For the identified target payment, if the user specifies a split method for a specific installment payment that is an installment payment to which the benefit is applied, the payment method for the target payment is changed to the specific installment payment using the specified split method. It is a thing,
A payment history screen showing the user's payment history, each history being linked to a respective payment completion screen, and displaying the history that satisfies the application conditions of the benefit among the payment history in an identifiable manner. displaying a screen on the user's terminal device;
a user interface for accepting an application to use the benefit is displayed on the payment completion screen linked to the history that satisfies the application conditions of the benefit;
When an application for the use of the benefit is made through the user interface with respect to a history that satisfies the conditions for applying the benefit among the payment history displayed on the payment history screen, accepting the designation of the division method for the benefit; , changing the payment method of the payment to the specific installment payment according to the division method;
Payment Method. A payment server that provides electronic payment services is
storing setting information of a benefit set by a member of the electronic payment service, which exempts the burden of installment interest fees when paying in installments using the electronic payment service;
delivering a benefit ticket indicating the right to use the benefit to the terminal device in response to an acquisition request from the user's terminal device;
executing a payment process for electronically settling the user's payment to the member based on the payment information received via the communication network at the time of the payment request;
In the payment processing,
Based on the payment history of the user and the distribution history of the benefit ticket, among the completed payments that the user has made in the past, the payment for which the user has already acquired the benefit ticket is classified as a payment history of the benefit ticket. Identification as a covered payment that is applicable;
For the specified eligible payment, if the user specifies a splitting method for a specific installment payment that is an installment payment to which the benefit is applied, the payment method for the eligible payment will be changed to the specific installment payment using the specified splitting method. , the payment of the usage fee imposed on the member regarding the use of the specified installment payment is offset by having the member bear the installment interest fee related to the specified installment payment;
Collecting an amount obtained by dividing a split interest fee according to the number of payments in the splitting method in proportion to the number of payments from the member in accordance with the monthly payment by the specific installment payment;
Payment Method.

Images