JP2023069400A - Member store deposit processing system and method - Google Patents

Abstract

To provide a member store deposit processing system and a method for enabling flexible deposit processing to a member store account.SOLUTION: A member store deposit processing system for performing deposit processing to a member store account includes first deposit means and second deposit means. With the first deposit means, an amount of deposit to the member store account is moved to a tunnel account of a settlement financial institution. The tunnel account is an account for temporarily holding the amount of deposit. With the second deposit means, the amount of deposit is deposited from the tunnel account to the member store account at an arbitrary timing of the member store.SELECTED DRAWING: Figure 4

Description

The present disclosure relates to merchant payment processing systems and methods.

In recent years, payment methods have diversified, such as debit payment, credit payment, and electronic money payment. In order to deal with such payment methods, many member stores provide users with various payment methods by contracting with payment service providers who comprehensively handle each payment method.

With the above payment methods, the payment to the member store account after settlement is basically made via a payment agency, and in most cases, the payment agency collects the deposit amount for each payment method and deposits it into the member store account. be.

FIG. 8 is a diagram illustrating a conventional member store deposit scheme. Here, a member store deposit scheme by debit settlement will be described as an example.

In the conventional member store payment scheme 800, first, when a transaction occurs at a member store, the money is withdrawn from the user account 801, and two business days after the transaction occurs, the money is transferred to a separate deposit account (for debit) 802 at the settlement financial institution. will be credited to Next, clearing data 804 (so-called Clearing process 805 is performed based on the settlement end data), and the member store account is cleared on the next business day after the deposit is made to the separate deposit account (for debit) 802, that is, three business days after the transaction occurs at the member store. Deposit is made at 806 . In the conventional merchant deposit scheme 800, such deposit processing is performed on a merchant account on a daily basis.

For example, Patent Literature 1 discloses a settlement system that uses a consolidated account (separate deposit account) to deposit money into a member store.

JP 2018-055669 A

However, as described above, there is a problem that fund management on the part of the member store becomes complicated if the member store account is credited daily three business days after the transaction occurs at the member store.

The present disclosure has been made in view of such problems, and aims to provide a member store deposit processing system and method that enable flexible processing of deposits to member store accounts.

According to one embodiment, a member store deposit processing system that performs deposit processing to a member store account is a first deposit means for transferring the deposit amount to the member store account to a tunnel account of a settlement financial institution, The tunnel account is an account that temporarily holds the deposit amount, and a second deposit means that deposits the deposit amount from the tunnel account to the member store account at an arbitrary timing of the member store. and a deposit means of

In addition, according to one embodiment, the method of performing deposit processing to the member store account includes a first deposit step of transferring the deposit amount to the member store account to a tunnel account of a settlement financial institution, the tunnel account is an account that temporarily holds the deposit amount; step.

According to the present disclosure, it is possible to flexibly process deposits to member store accounts.

1 is a diagram illustrating an overview of a member store deposit scheme according to one embodiment; FIG. 1 is a schematic configuration diagram of a member store payment processing system according to one embodiment; FIG. It is a figure which shows the hardware structural example of the computer which concerns on one Embodiment. 1 is a diagram showing a functional configuration example of a settlement financial institution system according to one embodiment; FIG. 6 is a flowchart of member store deposit processing according to one embodiment. It is a figure which shows the example of the payment cycle information which concerns on one Embodiment. FIG. 4 is a diagram illustrating a specific example of member store deposit processing according to an embodiment; It is a diagram for explaining an outline of a conventional member store deposit scheme.

Embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. The same reference numerals are given to the same elements throughout the specification and the attached drawings, and duplicate descriptions are omitted.

(overview)
FIG. 1 is a diagram illustrating an overview of a member store deposit scheme according to one embodiment. Here, as in FIG. 8, a member store payment scheme by debit settlement will be described as an example. Methods such as J-Debit (registered trademark) and Bank Pay (registered trademark) are known as debit payment methods. It is also possible to make payments.

Compared to the member store deposit scheme 800 in FIG. 8, the member store deposit scheme 100 is different from the payment method of each financial institution through a separate deposit account 107 (hereinafter also referred to as a tunnel account) of the settlement financial institution after the clearing process 105. It differs in that it is made possible to perform deposit processing to the member store account 108 .

In the member store payment scheme 100, first, when a transaction occurs at a member store (i.e., when a debit payment is made), the payment is withdrawn from the user account 101, and two business days after the date of occurrence, payment is made to the payment financial institution. Payment is made to the separate deposit account (for debit) 102 . Next, clearing data 104 (so-called The clearing process 105 is performed based on the settlement end data), and the clearing process 105 is performed on the business day following the payment to the separate deposit account (for debit) 102, that is, three business days after the transaction occurs at the member store. Payment is made to the member store account 106 based on the received payment cycle information, or payment is made to a separate deposit account (tunnel account) 107 of the settlement financial institution. Next, based on the deposit cycle information, the money is deposited from the tunnel account 107 to the affiliated store account 108 at any timing of each affiliated store. In addition, when a payment is made, the payment data is accumulated and stored, and a payment statement addressed to the member store is created based on the payment data. The deposit cycle means a monthly deposit processing cycle for member stores. Also, the deposit cycle information will be described later.

The clearing center 103 can link debit payment transaction data between the member store and the financial institution based on data received from CAFIS (Credit and Finance Information Switching system). Member store payment processing (clearing processing) is performed based on the "member store sales deposit data file" (clearing data 104) of the transaction data.

As described above, in the member store deposit scheme 100 according to the present embodiment, the member store's deposit amount is once transferred to the tunnel account 107, and then the tunnel account is transferred to the tunnel account at an arbitrary timing according to the deposit cycle specified by the member store. Payment processing from 107 to member store account 108 is performed. That is, the tunnel account 107 is an account that temporarily holds the deposited amount. In addition, the amount deposited into the member store account for which the deposit cycle is not set is not transferred to the tunnel account 107, but is directly deposited into the member store account three business days after the date of the transaction as in the conventional case. By doing so, it is possible to flexibly perform deposit processing to the account of the member store, and it is possible to make fund management on the side of the member store easier.

(System configuration example)
FIG. 2 is a schematic configuration diagram of a member store payment processing system according to one embodiment. In the merchant deposit system 200, a clearing center 201 and a settlement financial institution system 202 are communicably connected via a secure network 206 such as a dedicated line or encrypted communication network to which access from the outside is restricted. there is The settlement financial institution system 202 manages a separate deposit account (for debit) 102 and a tunnel account 107, receives clearing data 104 from the clearing center 201, and performs clearing processing 105. The clearing process 105 includes deposit processing for merchant accounts 106 and tunnel accounts 107 . In addition, in the member store deposit system 200, the payment financial institution system 202 and the financial institution systems 203, 204, and 205 are connected via a secure network 207 such as a dedicated line or encrypted communication network to which external access is restricted. After being communicatively connected and performing the clearing process 105, the settlement financial institution system 202 transmits payment instruction data to the member store accounts managed by the financial institution systems 203, 204, and 205 (that is, the payment process is performed). do).

The clearing center 201, settlement financial institution system 202, and financial institution systems 203, 204, and 205 are configured by one or more server computers and perform various processes as described above. Note that the number of financial institution systems that manage member store accounts is not limited to the three shown in FIG.

(computer hardware configuration)
FIG. 3 shows a hardware configuration example of a computer according to one embodiment. Computer 300 may be one or more server computers that make up clearing center 201 , settlement financial institution system 202 , and financial institution systems 203 , 204 , 205 .

Computer 300 in this embodiment comprises processor 301 , memory 302 , storage device 303 , communication interface (I/F) 305 , input device 306 , and display device 307 , which are connected via bus 310 . Connected for communication.

Processor 301 can be a CPU (Central Processing Unit), controls other components connected via bus 310, and processes data. The processor 301 also reads and executes programs stored in the memory 302 or storage device 303, thereby executing various processes according to the present embodiment.

The memory 302 includes ROM (Read Only Memory), RAM (Random Access Memory), etc., and stores programs and data for executing various processes according to the present embodiment. The RAM operates as a work memory and can load programs read by the processor 301 .

The storage device 303 can be a large-capacity storage device such as an HDD (Hard Disk Drive) or an SDD (Solid State Drive), and stores programs and data for executing various processes according to this embodiment.

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

The input device 306 can be a keyboard, a mouse, a touch panel display that also serves as the display device 307, or the like.

The display device 307 can be a liquid crystal display, an organic EL (Electro Luminescence) display, or the like.

The hardware configuration of the computer is not limited to the configuration example described above, and may include other components.

(Functional configuration)
FIG. 4 is a diagram showing a functional configuration example of a settlement financial institution system according to one embodiment. Settlement financial institution system 400 includes clearing data receiving section 401 , first deposit processing section 403 , and second deposit processing section 405 . These functional units can be implemented by the processor 301 of the computer 300 reading and executing programs stored in the memory 302 or the storage device 303, as described with reference to FIG. Here, the functional units particularly related to this embodiment will be described, but the settlement financial institution system 400 can of course also include other functional units.

The clearing data receiving unit 401 receives and stores clearing data from the clearing center 410 .

The first deposit processing unit 403 deposits the deposit amount into the member store account or the tunnel account based on the received clearing data and prestored deposit cycle information. The payment processing here is performed three business days after the date of transaction occurrence. Also, the deposit amount of the member store for which the deposit cycle information is set is deposited into the tunnel account, and the deposit amount of the member store for which the deposit cycle information is not set is deposited into the member store account.

Based on the deposit cycle information, the second deposit processing unit 405 transmits deposit instruction data from the tunnel account to the member store account to the financial institution system that manages the deposit target member store account (that is, performs deposit processing). do). Here, the deposit instruction data is transmitted according to the desired deposit cycle of the member store specified by the deposit cycle information. Details will be described later.

(Merchant payment processing)
FIG. 5 shows a flowchart of member store deposit processing according to one embodiment. Each step of the member store deposit processing described below is performed by the functional units of the settlement financial institution system 400 described above with reference to FIG.

In step S<b>501 , the clearing data receiving unit 401 of the settlement financial institution system 400 receives clearing data from the clearing center 410 . The received clearing data is stored in settlement financial institution system 400 .

Next, in step S502, the first deposit processing unit 403 of the settlement financial institution system 400 calculates the deposit amount based on the clearing data received in S501 and the deposit cycle information pre-stored in the settlement financial institution system 400. to the merchant account or tunnel account. Specifically, when payment cycle information is set for the member store to be processed, the amount of money to be paid by the member store is deposited into the tunnel account. On the other hand, if no deposit cycle information is set for the member store to be processed, the deposit amount of the member store is directly deposited into the account of the member store. The payment processing in this step is performed three business days after the transaction occurs, that is, the day the user uses debit payment at the affiliated store.

In step S503, the second deposit processing unit 405 of the settlement financial institution system 400 sends deposit instruction data from the tunnel account to the member store account to the financial institution system that manages the member store account to be deposited based on the deposit cycle information. to send. More specifically, the deposit instruction data is transmitted according to the desired deposit cycle of the member store for which the deposit cycle information is set.

(Concrete example)
FIG. 6 is a diagram showing an example of deposit cycle information according to one embodiment. The payment cycle information 600 includes a handling start date 601, a handling end date 602, deposit account information 603, a flag 604, a member store code 605, a member store subcode 606, a transaction aggregation date 607, a deposit date 608, a holiday code 609, and a service code. 610 included. Information included in the deposit cycle information 600 is not limited to these.

A handling start date 601 and a handling end date 602 indicate the period during which the set deposit cycle is valid.

Deposit account information 603 includes the deposit store number, item, and account number, and indicates the deposit account of the member store (ie, member store account).

The flag 604 indicates whether to collectively process deposits for some member store codes or to process them separately for a plurality of member store codes that have the same deposit account and the same deposit cycle. When the flag 604 is "0", the deposit processing is performed to each deposit account corresponding to the target member store code. When the flag 604 is "1", if the deposit account corresponding to the target member store code is the same, deposit processing is performed collectively for the target destinations. If the flag 604 is " " (blank), the payment processing is performed for each member store code. In this way, by using the flag 604, it is possible to select whether to unify or separate deposit details for the same deposit account and same deposit cycle.

The member store code 605 and member store subcode 606 are codes for uniquely identifying the member store.

Transaction Aggregation Date 607 includes a start date and an end date, and specifies the start and end dates (ie, the aggregation period) of the eligible transactions to be aggregated for credit from the tunnel account to the merchant account. For example, when monthly deposits are collected in two installments, the dates from the 1st to the 15th and the dates from the 16th to the 31st can be set. Not limited to this, if you divide the monthly payment into 3 times and aggregate it, you can set from the 1st to the 10th, from the 11th to the 20th, and from the 21st to the 31st, or set it to 6 times. 1st to 5th, 6th to 10th, 11th to 15th, 16th to 20th, 21st to 25th, and 26th to 26th Until the 31st may be set.

Deposit date 608 indicates the deposit date on which the aggregated subject transaction is deposited into the merchant account. The deposit date 608 can be set as the 5th, 10th, 15th, 20th, 25th, 31st, etc. of each month for each transaction aggregation date.

A holiday code 609 indicates whether the payment date is the previous business day or the next business day when the payment date 608 is a holiday. For example, if the holiday code 609 is "1", the payment date is changed to the previous business day, and if the holiday code 609 is "2", the payment date is changed to the next business day. That is, the holiday code 609 designates the payment date when the payment date is a holiday.

The service code 610 specifies the type of target transaction. For example, when the service code 610 is "1", it is for Bank Pay transactions, and when the service code 610 is "2", it is for J-Debit transactions. Both Bank Pay transactions and J-Debit transactions are debit settlement transactions.

For example, in the first and second lines of the deposit cycle information 600, transactions from the 1st to the 15th of every month for the member store identified by the member store code "2a00001" and the member store subcode "0001" are aggregated. , the aggregated transactions will be deposited on the 31st (end of the month), and the transactions from the 16th to the 31st (end of the month) will be aggregated and the aggregated transactions will be deposited on the 15th. It is In both cases, the flag is " " (blank), so the deposit processing is performed assuming that there is no addition target. In both cases, the holiday code 609 is "1", so if the specified payment day is a holiday, the payment process is performed on the previous business day. In both cases, the service code 610 is "1", so the target transaction is a Bank Pay transaction.

For example, in the 14th to 16th lines of the deposit cycle information 600, the member stores identified by the member store code "2c00001" and the member store subcodes "1111", "2222", and "3333" Transactions up to the 31st (the end of the month) are aggregated, and payment of the aggregated transactions is performed on the 10th. The member store identified by the member store code "2c00001" and the member store sub-code "1111" has a flag of "0", so the deposit processing is performed individually. On the other hand, since the member stores identified by the member store code "2c00001" and the member store subcodes "2222" and "3333" have flags of "1", they are collectively subjected to deposit processing. In both cases, the holiday code 609 is "1", so if the specified payment day is a holiday, the payment process is performed on the previous business day. In both cases, the service code 610 is "1", so the target transaction is a Bank Pay transaction. In this example, payment details can be unified for member stores identified by member store code "2c00001" and member store subcodes "2222" and "3333".

In this way, it is possible to once move the deposit amount of the member store to the tunnel account and set the deposit cycle information specified by the member store for the deposit processing from the tunnel account to the member store account. , it is possible to flexibly perform deposit processing to the account of the member store, and the fund management on the side of the member store can be made easier.

FIG. 7 is a diagram illustrating a specific example of member store deposit processing according to one embodiment. FIG. 7(a) shows the first deposit processing three business days after the date of occurrence of the transaction. In FIG. 7A, the total amount of member stores A+B+C is withdrawn from a separate deposit account (for debit) 701 (head office sales department: 200), A member store account 702, B member store account 703, and tunnel account 704 has been deposited.

FIG. 7(b) shows the second deposit processing performed on the deposit date specified by the deposit cycle information. In FIG. 7(b), the target five transactions (1) to (5) are aggregated in the tunnel account 704, are withdrawn from the tunnel account 704, and are deposited into the C member store account 705. In FIG.

As described above, according to the present embodiment, it is possible to provide a member store deposit processing system and method that enable flexible processing of deposit to a member store account.

400 settlement financial institution system 401 clearing data receiving unit 403 first deposit processing unit 405 second deposit processing unit 410 clearing center 420 each financial institution system

Claims (7)

A member store payment processing system for processing payment to a member store account,
A first deposit means for transferring the deposit amount to the member store account to a tunnel account of a settlement financial institution, wherein the tunnel account is an account that temporarily holds the deposit amount. and,
and a second deposit means for depositing the deposit amount from the tunnel account to the member store account at any timing of the member store. 2. The member store deposit processing system according to claim 1, wherein said second deposit means performs deposit processing to said member store account based on deposit cycle information set for each said member store. The payment cycle information includes the member store code for identifying the target member store, the transaction aggregation date specifying the target transaction aggregation period, the date of payment to the member store account, and the payment processing of the member store code. A flag that specifies whether or not to target, a holiday code that specifies whether the payment date is the previous business day or the next business day if the payment date is a holiday, and further specifies the type of the target transaction. 3. The member store payment processing system according to claim 2, further comprising a service code. 3. The first deposit means directly deposits the deposit amount to the affiliated store for which the deposit cycle information is not set to the affiliated store account without transferring it to the tunnel account. The member store deposit processing system according to 2 or 3. 5. The method according to any one of claims 1 to 4, wherein said second depositing means deposits a total amount of a plurality of transactions held in said tunnel account as said deposit amount into said member store account for each said member store. The member store payment processing system according to any one of the items. The member store deposit processing system according to any one of claims 1 to 5, wherein the deposit amount is generated by debit settlement. A method of depositing money into a member store account,
A first deposit step of transferring the deposit amount to the member store account to a tunnel account of a settlement financial institution, wherein the tunnel account is an account that temporarily holds the deposit amount. and,
and a second deposit step of depositing said deposit amount from said tunnel account to said merchant account at any time of the merchant.

Images