[go: up one dir, main page]

JP2004287933A - System for warrantying banking transaction - Google Patents

System for warrantying banking transaction Download PDF

Info

Publication number
JP2004287933A
JP2004287933A JP2003080178A JP2003080178A JP2004287933A JP 2004287933 A JP2004287933 A JP 2004287933A JP 2003080178 A JP2003080178 A JP 2003080178A JP 2003080178 A JP2003080178 A JP 2003080178A JP 2004287933 A JP2004287933 A JP 2004287933A
Authority
JP
Japan
Prior art keywords
transfer
notice
bank server
loan
request
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
JP2003080178A
Other languages
Japanese (ja)
Other versions
JP3923916B2 (en
Inventor
Michio Tanaka
美智男 田中
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Mitsubishi Electric Information Systems Corp
Mitsubishi Electric Information Technology Corp
Original Assignee
Mitsubishi Electric Information Systems Corp
Mitsubishi Electric Information Technology Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Mitsubishi Electric Information Systems Corp, Mitsubishi Electric Information Technology Corp filed Critical Mitsubishi Electric Information Systems Corp
Priority to JP2003080178A priority Critical patent/JP3923916B2/en
Publication of JP2004287933A publication Critical patent/JP2004287933A/en
Application granted granted Critical
Publication of JP3923916B2 publication Critical patent/JP3923916B2/en
Anticipated expiration legal-status Critical
Expired - Fee Related legal-status Critical Current

Links

Images

Landscapes

  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

<P>PROBLEM TO BE SOLVED: To warranty transactions at the account of a transfer destination even when a transfer or withdraw to be requested in advance is made in failure due to the interference of a bank system in a system for warrantying transactions between banks. <P>SOLUTION: A transfer advance notice notifying part 22 of a transfer source bank server 20 transmits a transfer request as a transfer advance notice to a transfer destination bank server 30. In a transfer destination bank server 30, a transfer confirming part 33 confirms whether the transfer has been performed as the transfer advance notice is notified, and a loan determining part 36 further determines a loan within the range of a transfer amount of the transfer advance notice when the transfer destination account when the transfer has not been performed does not have sufficient funds and also charges the transfer source bank side for a loan charge. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

【0001】
【発明の属する技術分野】
本発明は、銀行間の取引を保証するシステムに係り、銀行のシステム障害により事前に依頼されている振込や引落が失敗した場合でも、振込先口座での取引を保証するシステムに関する。
【0002】
【従来の技術】
本発明は、銀行間の取引において、振込や引落が失敗する事態における不具合を最小限に押さえることを目的とする。係る事態における不具合として、最も重大なことは、振り込まれることが予定されていた口座からの出金や引落等の取引の失敗である。
【0003】
取引の予告を利用する技術として、特開2002−041785号公報「代行支払システム」が開示されているが、このシステムは、日本銀行が提供するRTGS(即時決済)システムと接続し、顧客の代行決済を行う代行支払システムであり、支払内容を示す決済予定明細を受け取り、後に承認された場合に、代行支払を行うように構成されており、振込の失敗等と対応するものではない。
【0004】
【特許文献1】
特開2002−041785号公報
【0005】
【発明が解決しようとする課題】
本発明は、上記した従来技術の欠点を除くためになされたものであって、その目的とするところは、銀行間の取引を保証するシステムに係り、銀行のシステム障害により事前に依頼されている振込や引落が失敗した場合でも、振込先口座での取引を保証することを課題とする。
【0006】
【課題を解決するための手段】
本発明に係る銀行取引保証システムは、
振込元銀行サーバと振込先銀行サーバとからなる銀行取引保証システムであって、
振込元銀行サーバは、
(1)振込依頼を入力する振込依頼受信部と、
(2)前記振込依頼を、振込予告として、振込先銀行サーバへ送信する振込予告通知部とを有し、
振込先銀行サーバは、
(3)前記振込予告を受信する振込予告受付部と、
(4)前記振込予告の通りに振込が実行されたか確認する振込確認部と、
(5)前記振込が行われなかった振込先口座に残高不足が生じる場合に、振込予告の振込金額の範囲内で融資を決定する融資判定部とを有することを特徴とする。
【0007】
本発明に係る銀行取引保証システムは、
振込元銀行サーバと振込先銀行サーバとからなる銀行取引保証システムであって、
振込元銀行サーバは、
(1)振込依頼を入力する振込依頼受信部と、
(2)前記振込依頼を、振込予告として、振込先銀行サーバへ送信する振込予告通知部と、
(3)前記振込予告の通りに振込が実行できない場合に、振込不可情報を送信する振込不可情報送信部とを有し、
振込先銀行サーバは、
(4)前記振込予告を受信する振込予告受付部と、
(5)前記振込不可情報を受信する振込不可情報受付け部と、
(6)前記振込不可情報により特定される前記振込予告で指定されている振込先口座に残高不足が生じる場合に、振込予告の振込金額の範囲内で融資を決定する融資判定部とを有することを特徴とする。
【0008】
本発明に係る銀行取引保証システムは、
振込元銀行サーバと振込先銀行サーバとからなる銀行取引保証システムであって、
振込元銀行サーバは、
(1)引落依頼を入力する引落依頼受信部と、
(2)前記引落依頼を、振込予告として、振込先銀行サーバへ送信する振込予告通知部とを有し、
振込先銀行サーバは、
(3)前記振込予告を受信する振込予告受付部と、
(4)前記振込予告の通りに振込が実行されたか確認する振込確認部と、
(5)前記振込が行われなかった振込先口座に残高不足が生じる場合に、振込予告の振込金額の範囲内で融資を決定する融資判定部とを有することを特徴とする。
【0009】
本発明に係る銀行取引保証システムは、
振込元銀行サーバと振込先銀行サーバとからなる銀行取引保証システムであって、
振込元銀行サーバは、
(1)引落依頼を入力する引落依頼受信部と、
(2)前記引落依頼を、振込予告として、振込先銀行サーバへ送信する振込予告通知部と、
(3)前記振込予告の通りに振込が実行できない場合に、振込不可情報を送信する振込不可情報送信部とを有し、
振込先銀行サーバは、
(4)前記振込予告を受信する振込予告受付部と、
(5)前記振込不可情報を受信する振込不可情報受付け部と、
(6)前記振込不可情報により特定される前記振込予告で指定されている振込先口座に残高不足が生じる場合に、振込予告の振込金額の範囲内で融資を決定する融資判定部とを有することを特徴とする。
【0010】
振込先銀行サーバは、決定した融資に係る融資手数料の請求を振込元銀行サーバへ送信する融資手数料請求処理部を有することを特徴とする。
【0011】
【発明の実施の形態】
実施の形態1.
以下本発明を図面に示す実施例に基づいて説明する。図1は、実施の形態1における銀行間の関係を示す図である。
この図に従って、本システムを用いた取引を説明する。例えば、雇用主である振込依頼者1は、自身の口座から従業員である振込先口座名義人4の口座への給与等の振込を、振込元銀行2に依頼する。振込元銀行2は、振込先銀行3に振込予告を通知する。そして、振込元銀行2で不具合等により振込処理に失敗した場合には、振込先銀行3は、期日に至っても振込が行われないと判断し、振込先の口座からの出金、引落、振込、振替の際の残高不足分を自動的に融資し、補填する。
【0012】
次に、振込元銀行2のサーバである振込元銀行サーバ20と、振込先銀行3のサーバである振込先銀行サーバ30の構成について説明する。図2は、実施の形態1における振込元銀行サーバと振込先銀行サーバの構成を示す図である。
振込元銀行サーバ20は、振込依頼受信部21、振込予告通知部22、振込処理部23、振込依頼記憶部24、及び融資手数料請求受信部25の要素を有している。一方、振込先銀行サーバ30は、振込予告受付部31、振込予告記憶部32、振込確認部33、口座管理データベース34、融資候補口座情報記憶部35、融資判定部36、融資処理部37、及び融資手数料請求処理部38の要素を有している。
【0013】
続いて、処理について説明する。まず、振込元銀行サーバ20側の前処理について説明する。図3は、振込依頼受付け処理フロー(振込元銀行サーバ)を示す図である。
振込依頼受信部21は、銀行内端末等から振込依頼者からの振込依頼を入力する(S301)。振込依頼は、振込元口座番号、振込先銀行名及び店名、振込先口座番号、振込金額、振込予定日の情報を含んでいる。そして、入力した振込依頼を、振込依頼記憶部24に記憶し(S302)、振込依頼を、振込予告として、振込先銀行サーバ30へ送信する(S303)。
【0014】
一方、振込先銀行サーバ30側の前処理について説明する。図4は、振込予告受付け処理フロー(振込先銀行サーバ)を示す図である。
振込予告受付部31は、振込先銀行サーバ30から振込予告を受信し(S401)、振込予告を記憶する(S402)。このとき、振込先銀行サーバ30の銀行名及び店名も併せて記憶する。
【0015】
上述の前処理が完了した振込依頼に関する振込予定日の処理について説明する。振込先銀行サーバ30では、振込確認部33により振込確認処理を行う。図5は、振込確認処理フロー(振込先銀行サーバ)を示す図である。
振込予告記憶部32に記憶している振込予告毎に以下の処理を繰り返す(S501)。振込予定日に至っても、予告通り振り込まれていない場合に(S502,S503)、振込先口座番号を融資候補口座番号として、また、予定されていた振込額を融資可能額として、これらを対応付けて融資候補口座情報記憶部35に記憶する(S504)。
そして、すべての振込予告について処理した時点で終了する(S505)。
これにより、融資の準備が完了する。
【0016】
振込先銀行サーバ30は、振込先銀行3で開設されている口座で、出金、引落、振込、振替の処理の際の残高不足が発生した場合に、立替検討処理を行う。図6は、立替検討処理フロー(振込先銀行サーバ)を示す図である。
まず、融資判定部36による融資判定処理(S601)を行う。図7は、融資判定処理フロー(振込先銀行サーバ)を示す図である。
融資判定部36は、残金不足が生じた口座番号とその不足金額を取得する(S701)。そして、残金不足口座番号は、いずれかの融資候補口座番号と一致するか判定する(S702)。つまり、残金不足口座が、融資候補口座として融資候補口座情報記憶部35に登録されているか判定する。
登録されている場合には、不足金額が、融資可能金額の範囲内か判定する(S703)。
範囲内の場合には、融資候補口座番号を融資口座番号として、不足金額を融資金額として、融資を決定する(S704)。そして、融資可能金額から融資金額を差し引いて、融資可能金額を更新する(S705)。
【0017】
融資処理部37は、融資処理(S602)により、融資口座番号に融資金額の融資処理を行う。これにより、前述の出金、引落、振込、振替の処理が正常に処理されることになる。
【0018】
最後に、融資手数料請求処理部38による融資手数料請求処理(S603)を行う。これにより、融資に伴う手数料を振込元銀行2に請求する情報を振込元銀行サーバ20に送信する。この際、振込元口座番号と融資金額と併せて送信することが有効である。
【0019】
実施の形態2.
振込元銀行2で振込ができない場合に、振込元銀行サーバ20から振込先銀行サーバ30へ振込できないことを通知する形態について説明する。これにより、振込先銀行サーバ30の処理を軽減することができる。図8は、実施の形態2における振込元銀行サーバと振込先銀行サーバの構成を示す図である。
振込元銀行サーバ20は、振込依頼が実行できない場合に、振込不可情報を送信する振込不可情報送信部26を有する。一方、振込先銀行サーバ30は、振込不可情報を受信する振込不可情報受付部39を有している。図9は、振込不可情報受付け処理フロー(振込先銀行サーバ)を示す図である。
振込不可情報受付部39は、振込予告を特定可能な情報(振込予告ID)を含む振込不可情報を受信し(S901)、振込先口座番号を融資候補口座番号として、予定されていた振込額を融資可能額として、これらを対応付けて記憶する(S902)。
この処理は、実施の形態1における振込確認部33の処理に代わる処理である。
【0020】
実施の形態3.
本実施の形態では、自動振込が失敗した場合の処理について説明する。図10は、実施の形態3における銀行間の関係を示す図である。
例えば、納税者である自動振込依頼者5は、予め振込元銀行2へ、自己の口座から税金の自動振込(引き落し)を依頼している。振込元銀行2は、地方公共団体等である引落依頼者6から引落依頼を受付けると、引落依頼者6の口座が開設されている振込先銀行3へ、振込予告を通知する。そして、振込元銀行2で振込に失敗した場合に、振込先銀行3は前述の形態同様に引落依頼者6の口座の残高不足に対する融資する処理を行う。
【0021】
図11は、実施の形態3における振込元銀行サーバと振込先銀行サーバの構成を示す図である。
図2の振込依頼受信部21と振込依頼記憶部24に代えて、引落依頼受信部27と引落依頼記憶部28を備えている。
【0022】
図12は、引落依頼受付け処理(振込元銀行サーバ)を示す図である。引落依頼受信部27は、振込依頼者1からの振込依頼に代えて、引落依頼者6からの引落依頼を入力する(S1201)。引落依頼は、振込依頼と同様の情報を含んでいる。そして、引落依頼記憶部28は、この引落依頼を記憶する(S1202)。そして、引落依頼を、振込予告として、振込先銀行サーバ30へ送信する(S1203)。
【0023】
また、自動振込(引き落し)の場合に、実施の形態2と同様に、振込元銀行サーバ20から振込先銀行サーバ30へ振込不可情報を送信する構成としてもよい。
【0024】
振込元銀行サーバ20と振込先銀行サーバ30は、コンピュータであり、各要素はプログラムにより処理を実行することができる。また、プログラムを記憶媒体に記憶させ、記憶媒体からコンピュータに読み取られるようにすることができる。
【0025】
【発明の効果】
本発明においては、振込が行われなかった振込先口座に残高不足が生じる場合に、振込予告の振込金額の範囲内で融資を決定するので、振込失敗が生じた場合でも、予定振込先での残高不足による取引の失敗を予防できる。
【図面の簡単な説明】
【図1】実施の形態1における銀行間の関係を示す図である。
【図2】実施の形態1における振込元銀行サーバと振込先銀行サーバの構成を示す図である。
【図3】振込依頼受付け処理フロー(振込元銀行サーバ)を示す図である。
【図4】振込予告受付け処理フロー(振込先銀行サーバ)を示す図である。
【図5】振込確認処理フロー(振込先銀行サーバ)を示す図である。
【図6】立替検討処理フロー(振込先銀行サーバ)を示す図である。
【図7】融資判定処理フロー(振込先銀行サーバ)を示す図である。
【図8】実施の形態2における振込元銀行サーバと振込先銀行サーバの構成を示す図である。
【図9】振込不可情報受付け処理フロー(振込先銀行サーバ)を示す図である。
【図10】実施の形態3における銀行間の関係を示す図である。
【図11】実施の形態3における振込元銀行サーバと振込先銀行サーバの構成を示す図である。
【図12】引落依頼受付け処理(振込元銀行サーバ)を示す図である。
【符号の説明】
1 振込依頼者、2 振込元銀行、3 振込先銀行、4 振込先口座名義人、5 自動振込依頼者、6 引落依頼者、20 振込元銀行サーバ、21 振込依頼受信部、22 振込予告通知部、23 振込処理部、24 振込依頼記憶部、25 融資手数料請求受信部、26 振込不可情報送信部、27 引落依頼受信部、28 引落依頼記憶部、30 振込先銀行サーバ、31 振込予告受付部、32 振込予告記憶部、33 振込確認部、34 口座管理データベース、35融資候補口座情報記憶部、36 融資判定部、37 融資処理部、38 融資手数料請求処理部、39 振込不可情報受付部。
[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a system for guaranteeing a transaction between banks, and more particularly to a system for guaranteeing a transaction in a transfer destination account even if a transfer or debit requested in advance fails due to a bank system failure.
[0002]
[Prior art]
An object of the present invention is to minimize a problem in a case where a transfer or debit fails in a transaction between banks. The most serious problem in such a situation is a failure in the transaction such as withdrawal or debit from the account that was scheduled to be transferred.
[0003]
Japanese Patent Application Laid-Open No. 2002-041785 discloses a "proxy payment system" as a technique for utilizing a notice of a transaction. This system is connected to an RTGS (immediate settlement) system provided by the Bank of Japan to provide a proxy for a customer. It is a proxy payment system that performs payment, and is configured to receive a payment schedule statement indicating payment details and to perform proxy payment when it is approved later, and does not correspond to a transfer failure or the like.
[0004]
[Patent Document 1]
JP-A-2002-041785
[Problems to be solved by the invention]
The present invention has been made in order to eliminate the above-mentioned drawbacks of the prior art, and aims at a system for guaranteeing transactions between banks, which has been requested in advance due to a bank system failure. An object of the present invention is to guarantee a transaction in a transfer destination account even when a transfer or debit has failed.
[0006]
[Means for Solving the Problems]
The bank transaction guarantee system according to the present invention comprises:
A bank transaction guarantee system comprising a transfer source bank server and a transfer destination bank server,
The transfer source bank server
(1) a transfer request receiving unit for inputting a transfer request,
(2) a transfer notice notification unit for transmitting the transfer request as a transfer notice to a transfer destination bank server;
The transfer destination bank server
(3) a transfer notice receiving unit that receives the transfer notice;
(4) a transfer confirmation unit for confirming that the transfer has been executed as described in the transfer notice,
(5) When there is a shortage of funds in the transfer destination account where the transfer has not been made, a loan determination unit that determines a loan within the range of the transfer amount of the transfer notice is provided.
[0007]
The bank transaction guarantee system according to the present invention comprises:
A bank transaction guarantee system comprising a transfer source bank server and a transfer destination bank server,
The transfer source bank server
(1) a transfer request receiving unit for inputting a transfer request,
(2) a transfer notice notification unit for transmitting the transfer request as a transfer notice to a transfer destination bank server;
(3) a transfer-impossible information transmitting section that transmits transfer-impossible information when the transfer cannot be executed as described in the transfer notice,
The transfer destination bank server
(4) a transfer notice receiving unit that receives the transfer notice,
(5) a transfer-impossible information receiving unit that receives the transfer-impossible information;
(6) When there is a shortage of funds in the transfer destination account specified in the transfer notice specified by the transfer prohibition information, a loan determination unit that determines a loan within the transfer amount of the transfer notice is provided. It is characterized by.
[0008]
The bank transaction guarantee system according to the present invention comprises:
A bank transaction guarantee system comprising a transfer source bank server and a transfer destination bank server,
The transfer source bank server
(1) Withdrawal request receiving unit for inputting a withdrawal request,
(2) a transfer notice notification unit for transmitting the debit request as a transfer notice to a transfer destination bank server;
The transfer destination bank server
(3) a transfer notice receiving unit that receives the transfer notice;
(4) a transfer confirmation unit for confirming that the transfer has been executed as described in the transfer notice,
(5) When there is a shortage of funds in the transfer destination account where the transfer has not been made, a loan determination unit that determines a loan within the range of the transfer amount of the transfer notice is provided.
[0009]
The bank transaction guarantee system according to the present invention comprises:
A bank transaction guarantee system comprising a transfer source bank server and a transfer destination bank server,
The transfer source bank server
(1) Withdrawal request receiving unit for inputting a withdrawal request,
(2) a transfer notice notification unit that transmits the debit request as a transfer notice to a transfer destination bank server;
(3) a transfer-impossible information transmitting section that transmits transfer-impossible information when the transfer cannot be executed as described in the transfer notice,
The transfer destination bank server
(4) a transfer notice receiving unit that receives the transfer notice,
(5) a transfer-impossible information receiving unit that receives the transfer-impossible information;
(6) When there is a shortage of funds in the transfer destination account specified in the transfer notice specified by the transfer prohibition information, a loan determination unit that determines a loan within the transfer amount of the transfer notice is provided. It is characterized by.
[0010]
The transfer destination bank server has a loan charge request processing unit that transmits a request for a loan fee relating to the determined loan to the transfer source bank server.
[0011]
BEST MODE FOR CARRYING OUT THE INVENTION
Embodiment 1 FIG.
Hereinafter, the present invention will be described based on embodiments shown in the drawings. FIG. 1 is a diagram showing a relationship between banks in the first embodiment.
The transaction using this system will be described with reference to FIG. For example, the transfer requester 1 as an employer requests the transfer source bank 2 for a transfer of salary or the like from an account of the transferee to an account of a transferee account holder 4 as an employee. The transfer source bank 2 notifies the transfer destination bank 3 of a transfer notice. Then, if the transfer process fails due to a problem or the like at the transfer source bank 2, the transfer destination bank 3 determines that the transfer is not performed even when the due date is reached, and withdraws, withdraws, and transfers from the transfer destination account. Automatically finance and compensate for the balance shortfall at the time of transfer.
[0012]
Next, the configurations of the transfer source bank server 20 as the server of the transfer source bank 2 and the transfer destination bank server 30 as the server of the transfer destination bank 3 will be described. FIG. 2 is a diagram showing a configuration of a transfer source bank server and a transfer destination bank server in the first embodiment.
The transfer source bank server 20 includes elements of a transfer request receiving unit 21, a transfer notice notice unit 22, a transfer processing unit 23, a transfer request storage unit 24, and a loan fee request receiving unit 25. On the other hand, the transfer destination bank server 30 includes a transfer notice receiving unit 31, a transfer notice storage unit 32, a transfer confirmation unit 33, an account management database 34, a loan candidate account information storage unit 35, a loan determination unit 36, a loan processing unit 37, It has an element of the loan fee request processing unit 38.
[0013]
Next, the processing will be described. First, the pre-processing on the transfer source bank server 20 side will be described. FIG. 3 is a diagram showing a transfer request acceptance processing flow (transfer source bank server).
The transfer request receiving unit 21 inputs a transfer request from a transfer requester from a terminal in a bank or the like (S301). The transfer request includes information of a transfer source account number, a transfer destination bank name and a store name, a transfer destination account number, a transfer amount, and a scheduled transfer date. Then, the input transfer request is stored in the transfer request storage unit 24 (S302), and the transfer request is transmitted to the transfer destination bank server 30 as a transfer notice (S303).
[0014]
On the other hand, the preprocessing on the transfer destination bank server 30 will be described. FIG. 4 is a diagram showing the flow of the transfer notice acceptance processing (transfer destination bank server).
The transfer notice receiving unit 31 receives the transfer notice from the transfer destination bank server 30 (S401), and stores the transfer notice (S402). At this time, the bank name and store name of the transfer destination bank server 30 are also stored.
[0015]
A description will be given of the scheduled transfer date processing relating to the transfer request for which the above-described preprocessing has been completed. In the transfer destination bank server 30, the transfer confirmation unit 33 performs a transfer confirmation process. FIG. 5 is a diagram showing a transfer confirmation processing flow (transfer destination bank server).
The following process is repeated for each transfer notice stored in the transfer notice storage unit 32 (S501). If the transfer has not been made as scheduled even before the scheduled transfer date (S502, S503), the transfer destination account number is set as the loan candidate account number, and the planned transfer amount is set as the loanable amount, and these are associated with each other. And store it in the loan candidate account information storage unit 35 (S504).
Then, the process ends when all the transfer notices have been processed (S505).
Thus, preparation for the loan is completed.
[0016]
The transfer-destination bank server 30 performs a transfer-examination process when an account opened at the transfer-destination bank 3 has a shortage of balance in the processing of withdrawal, withdrawal, transfer, and transfer. FIG. 6 is a diagram showing a transfer examination processing flow (transfer destination bank server).
First, a loan determination process (S601) by the loan determination unit 36 is performed. FIG. 7 is a diagram showing a loan determination processing flow (transfer destination bank server).
The loan determination unit 36 acquires the account number where the remaining balance is insufficient and the amount of the shortage (S701). Then, it is determined whether the account number of the insufficient balance of the account matches one of the loan candidate account numbers (S702). That is, it is determined whether or not the account with insufficient balance is registered in the loan candidate account information storage unit 35 as a loan candidate account.
If registered, it is determined whether the shortage amount is within the range of the loanable amount (S703).
If it is within the range, a loan is determined with the loan candidate account number as the loan account number and the shortage amount as the loan amount (S704). Then, the financing amount is updated by subtracting the financing amount from the financing amount (S705).
[0017]
The loan processing unit 37 performs the loan processing of the loan amount for the loan account number by the loan processing (S602). As a result, the processing of the above-described withdrawal, withdrawal, transfer, and transfer is normally processed.
[0018]
Finally, the financing fee request processing unit 38 performs a financing fee requesting process (S603). As a result, information for requesting the transfer source bank 2 for the commission associated with the loan is transmitted to the transfer source bank server 20. At this time, it is effective to transmit the transfer source account number and the loan amount together.
[0019]
Embodiment 2 FIG.
A description will be given of a mode of notifying that the transfer cannot be made from the transfer source bank server 20 to the transfer destination bank server 30 when the transfer cannot be made at the transfer source bank 2. Thereby, the processing of the transfer destination bank server 30 can be reduced. FIG. 8 is a diagram showing a configuration of a transfer source bank server and a transfer destination bank server in the second embodiment.
The transfer-source bank server 20 has a transfer-disabled information transmitting unit 26 that transmits transfer-disabled information when a transfer request cannot be executed. On the other hand, the transfer-destination bank server 30 has a transfer-impossible information receiving unit 39 that receives transfer-impossible information. FIG. 9 is a diagram showing a transfer-impossible information receiving process flow (transfer-destination bank server).
The transfer-impossible information receiving unit 39 receives transfer-impossible information including information (transfer notice ID) that can specify a transfer notice (S901), and uses the transfer-destination account number as a loan candidate account number and transfers the scheduled transfer amount. These are stored in association with each other as a possible loan amount (S902).
This process is a process replacing the process of the transfer confirmation unit 33 in the first embodiment.
[0020]
Embodiment 3 FIG.
In the present embodiment, a process in the case where the automatic transfer has failed will be described. FIG. 10 is a diagram illustrating a relationship between banks according to the third embodiment.
For example, the automatic transfer requester 5, who is a taxpayer, has previously requested the transfer source bank 2 to automatically transfer (deduct) tax from its own account. When receiving the debit request from the debit requester 6, which is a local public organization, the transfer source bank 2 notifies the transfer destination bank 3 in which the account of the debit requester 6 is opened of a transfer notice. Then, when the transfer fails at the transfer source bank 2, the transfer destination bank 3 performs a process of financing for the shortage of the balance of the account of the debit requester 6 as in the above-described embodiment.
[0021]
FIG. 11 is a diagram showing a configuration of a transfer source bank server and a transfer destination bank server in the third embodiment.
A transfer request receiving unit 27 and a transfer request storage unit 28 are provided instead of the transfer request receiving unit 21 and the transfer request storage unit 24 in FIG.
[0022]
FIG. 12 is a diagram showing the withdrawal request accepting process (transfer source bank server). The debit request receiving unit 27 inputs a debit request from the debit requester 6 instead of the transfer request from the transfer requester 1 (S1201). The withdrawal request includes the same information as the transfer request. Then, the withdrawal request storage unit 28 stores this withdrawal request (S1202). Then, the debit request is transmitted to the transfer destination bank server 30 as a transfer notice (S1203).
[0023]
Further, in the case of automatic transfer (withdrawal), as in the second embodiment, a configuration in which transfer-disabled information is transmitted from the transfer-source bank server 20 to the transfer-destination bank server 30 may be adopted.
[0024]
The transfer source bank server 20 and the transfer destination bank server 30 are computers, and each element can execute processing by a program. Further, the program can be stored in a storage medium, and can be read by the computer from the storage medium.
[0025]
【The invention's effect】
In the present invention, when a shortage occurs in the transfer destination account where the transfer has not been made, the loan is determined within the range of the transfer amount of the transfer notice, so even if a transfer failure occurs, the transfer at the scheduled transfer destination is performed. Transaction failure due to insufficient balance can be prevented.
[Brief description of the drawings]
FIG. 1 is a diagram showing a relationship between banks in the first embodiment.
FIG. 2 is a diagram showing a configuration of a transfer source bank server and a transfer destination bank server in the first embodiment.
FIG. 3 is a diagram showing a transfer request acceptance processing flow (transfer source bank server).
FIG. 4 is a diagram showing a transfer notice acceptance processing flow (transfer destination bank server).
FIG. 5 is a diagram showing a transfer confirmation processing flow (transfer destination bank server).
FIG. 6 is a diagram showing a transfer examination processing flow (transfer destination bank server).
FIG. 7 is a diagram showing a loan determination processing flow (transfer destination bank server).
FIG. 8 is a diagram showing a configuration of a transfer source bank server and a transfer destination bank server in the second embodiment.
FIG. 9 is a diagram showing a transfer-impossible information receiving process flow (transfer-destination bank server).
FIG. 10 is a diagram showing a relationship between banks in the third embodiment.
FIG. 11 is a diagram showing a configuration of a transfer source bank server and a transfer destination bank server in a third embodiment.
FIG. 12 is a diagram showing a debit request accepting process (transfer source bank server).
[Explanation of symbols]
1 transfer requester, 2 transfer source bank, 3 transfer destination bank, 4 transfer destination account holder, 5 automatic transfer requester, 6 transfer requester, 20 transfer source bank server, 21 transfer request receiving section, 22 transfer notice notification section , 23 transfer processing section, 24 transfer request storage section, 25 loan fee request receiving section, 26 transfer impossible information transmitting section, 27 withdrawal request receiving section, 28 withdrawal request storage section, 30 transfer destination bank server, 31 transfer notice receiving section, 32 transfer notice storage unit, 33 transfer confirmation unit, 34 account management database, 35 loan candidate account information storage unit, 36 loan determination unit, 37 loan processing unit, 38 loan fee request processing unit, 39 transfer impossible information receiving unit.

Claims (5)

振込元銀行サーバと振込先銀行サーバとからなる銀行取引保証システムであって、
振込元銀行サーバは、
(1)振込依頼を入力する振込依頼受信部と、
(2)前記振込依頼を、振込予告として、振込先銀行サーバへ送信する振込予告通知部とを有し、
振込先銀行サーバは、
(3)前記振込予告を受信する振込予告受付部と、
(4)前記振込予告の通りに振込が実行されたか確認する振込確認部と、
(5)前記振込が行われなかった振込先口座に残高不足が生じる場合に、振込予告の振込金額の範囲内で融資を決定する融資判定部とを有することを特徴とする銀行取引保証システム。
A bank transaction guarantee system comprising a transfer source bank server and a transfer destination bank server,
The transfer source bank server
(1) a transfer request receiving unit for inputting a transfer request,
(2) a transfer notice notification unit for transmitting the transfer request as a transfer notice to a transfer destination bank server,
The transfer destination bank server
(3) a transfer notice receiving unit that receives the transfer notice;
(4) a transfer confirmation unit for confirming that the transfer has been executed as described in the transfer notice,
(5) A bank transaction guarantee system comprising: a loan determination unit that determines a loan within the range of the transfer amount of a transfer notice when a shortage occurs in a transfer destination account in which the transfer has not been performed.
振込元銀行サーバと振込先銀行サーバとからなる銀行取引保証システムであって、
振込元銀行サーバは、
(1)振込依頼を入力する振込依頼受信部と、
(2)前記振込依頼を、振込予告として、振込先銀行サーバへ送信する振込予告通知部と、
(3)前記振込予告の通りに振込が実行できない場合に、振込不可情報を送信する振込不可情報送信部とを有し、
振込先銀行サーバは、
(4)前記振込予告を受信する振込予告受付部と、
(5)前記振込不可情報を受信する振込不可情報受付け部と、
(6)前記振込不可情報により特定される前記振込予告で指定されている振込先口座に残高不足が生じる場合に、振込予告の振込金額の範囲内で融資を決定する融資判定部とを有することを特徴とする銀行取引保証システム。
A bank transaction guarantee system comprising a transfer source bank server and a transfer destination bank server,
The transfer source bank server
(1) a transfer request receiving unit for inputting a transfer request,
(2) a transfer notice notification unit for transmitting the transfer request as a transfer notice to a transfer destination bank server;
(3) a transfer-impossible information transmitting section that transmits transfer-impossible information when the transfer cannot be executed as described in the transfer notice,
The transfer destination bank server
(4) a transfer notice receiving unit that receives the transfer notice,
(5) a transfer-impossible information receiving unit that receives the transfer-impossible information;
(6) When there is a shortage of funds in the transfer destination account specified in the transfer notice specified by the transfer prohibition information, a loan determination unit that determines a loan within the transfer amount of the transfer notice is provided. A bank transaction guarantee system.
振込元銀行サーバと振込先銀行サーバとからなる銀行取引保証システムであって、
振込元銀行サーバは、
(1)引落依頼を入力する引落依頼受信部と、
(2)前記引落依頼を、振込予告として、振込先銀行サーバへ送信する振込予告通知部とを有し、
振込先銀行サーバは、
(3)前記振込予告を受信する振込予告受付部と、
(4)前記振込予告の通りに振込が実行されたか確認する振込確認部と、
(5)前記振込が行われなかった振込先口座に残高不足が生じる場合に、振込予告の振込金額の範囲内で融資を決定する融資判定部とを有することを特徴とする銀行取引保証システム。
A bank transaction guarantee system comprising a transfer source bank server and a transfer destination bank server,
The transfer source bank server
(1) Withdrawal request receiving unit for inputting a withdrawal request,
(2) a transfer notice notification unit for transmitting the debit request as a transfer notice to a transfer destination bank server;
The transfer destination bank server
(3) a transfer notice receiving unit that receives the transfer notice;
(4) a transfer confirmation unit for confirming that the transfer has been executed as described in the transfer notice,
(5) A bank transaction guarantee system comprising: a loan determination unit that determines a loan within the range of the transfer amount of a transfer notice when a shortage occurs in a transfer destination account in which the transfer has not been performed.
振込元銀行サーバと振込先銀行サーバとからなる銀行取引保証システムであって、
振込元銀行サーバは、
(1)引落依頼を入力する引落依頼受信部と、
(2)前記引落依頼を、振込予告として、振込先銀行サーバへ送信する振込予告通知部と、
(3)前記振込予告の通りに振込が実行できない場合に、振込不可情報を送信する振込不可情報送信部とを有し、
振込先銀行サーバは、
(4)前記振込予告を受信する振込予告受付部と、
(5)前記振込不可情報を受信する振込不可情報受付け部と、
(6)前記振込不可情報により特定される前記振込予告で指定されている振込先口座に残高不足が生じる場合に、振込予告の振込金額の範囲内で融資を決定する融資判定部とを有することを特徴とする銀行取引保証システム。
A bank transaction guarantee system comprising a transfer source bank server and a transfer destination bank server,
The transfer source bank server
(1) Withdrawal request receiving unit for inputting a withdrawal request,
(2) a transfer notice notification unit that transmits the debit request as a transfer notice to a transfer destination bank server;
(3) a transfer-impossible information transmitting section that transmits transfer-impossible information when the transfer cannot be executed as described in the transfer notice,
The transfer destination bank server
(4) a transfer notice receiving unit that receives the transfer notice,
(5) a transfer-impossible information receiving unit that receives the transfer-impossible information;
(6) When there is a shortage of funds in the transfer destination account specified in the transfer notice specified by the transfer prohibition information, a loan determination unit that determines a loan within the transfer amount of the transfer notice is provided. A bank transaction guarantee system.
振込先銀行サーバは、決定した融資に係る融資手数料の請求を振込元銀行サーバへ送信する融資手数料請求処理部を有することを特徴とする請求項1から5のいずれかに記載の銀行取引保証システム。The bank transaction guarantee system according to any one of claims 1 to 5, wherein the transfer destination bank server has a loan fee request processing unit that transmits a request for a loan fee relating to the determined loan to the transfer source bank server. .
JP2003080178A 2003-03-24 2003-03-24 Bank transaction guarantee system Expired - Fee Related JP3923916B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2003080178A JP3923916B2 (en) 2003-03-24 2003-03-24 Bank transaction guarantee system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
JP2003080178A JP3923916B2 (en) 2003-03-24 2003-03-24 Bank transaction guarantee system

Publications (2)

Publication Number Publication Date
JP2004287933A true JP2004287933A (en) 2004-10-14
JP3923916B2 JP3923916B2 (en) 2007-06-06

Family

ID=33294112

Family Applications (1)

Application Number Title Priority Date Filing Date
JP2003080178A Expired - Fee Related JP3923916B2 (en) 2003-03-24 2003-03-24 Bank transaction guarantee system

Country Status (1)

Country Link
JP (1) JP3923916B2 (en)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2009064384A (en) * 2007-09-10 2009-03-26 Oki Electric Ind Co Ltd Transfer system
US7716113B2 (en) * 2003-05-15 2010-05-11 Cantor Index, Llc System and method for providing an intermediary for a transaction
US7835974B2 (en) 2003-05-15 2010-11-16 Cantor Index, LLC. System and method for managing risk associated with product transactions
US7925577B2 (en) 2003-05-15 2011-04-12 Cantor Index Llc System and method for establishing and providing access to various types of online accounts
US7996297B2 (en) 2003-05-15 2011-08-09 Cantor Index, Llc System and method for providing access to and managing account activity for an online account
US8001039B2 (en) 2003-05-15 2011-08-16 Cantor Index, Llc System and method for establishing and providing access to an online account
US8799121B2 (en) 2003-05-15 2014-08-05 Cantor Index, Llc System and method for managing trading order requests
JP2020205085A (en) * 2020-09-03 2020-12-24 アルトア株式会社 Account management equipment and programs

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8160953B2 (en) 2003-05-15 2012-04-17 Cantor Index, Llc System and method for managing risk associated with product transactions
US7716113B2 (en) * 2003-05-15 2010-05-11 Cantor Index, Llc System and method for providing an intermediary for a transaction
US7835974B2 (en) 2003-05-15 2010-11-16 Cantor Index, LLC. System and method for managing risk associated with product transactions
US7925577B2 (en) 2003-05-15 2011-04-12 Cantor Index Llc System and method for establishing and providing access to various types of online accounts
US7996297B2 (en) 2003-05-15 2011-08-09 Cantor Index, Llc System and method for providing access to and managing account activity for an online account
US8001039B2 (en) 2003-05-15 2011-08-16 Cantor Index, Llc System and method for establishing and providing access to an online account
US8417626B2 (en) 2003-05-15 2013-04-09 Cantor Index, Llc System and method for sports betting
US8498924B2 (en) 2003-05-15 2013-07-30 Cantor Index Llc Managing risk associated with betting transactions
US8655768B2 (en) 2003-05-15 2014-02-18 Cantor Index, Llc System and method for managing risk associated with product transactions
US8799121B2 (en) 2003-05-15 2014-08-05 Cantor Index, Llc System and method for managing trading order requests
JP2009064384A (en) * 2007-09-10 2009-03-26 Oki Electric Ind Co Ltd Transfer system
JP2020205085A (en) * 2020-09-03 2020-12-24 アルトア株式会社 Account management equipment and programs
JP7049417B2 (en) 2020-09-03 2022-04-06 アルトア株式会社 Account management equipment and programs

Also Published As

Publication number Publication date
JP3923916B2 (en) 2007-06-06

Similar Documents

Publication Publication Date Title
US8538875B2 (en) Process for linked healthcare and financial transaction initiation
US7885451B1 (en) Systems and methods for displaying negotiable instruments derived from various sources
EP0913786B1 (en) A transaction manager
US20040210521A1 (en) Web-based payment system with consumer interface and methods
JP7728652B2 (en) Data processing device and data processing method
US20100299230A1 (en) Recurring transaction processing
US20060282376A1 (en) System and method for automated processing of real estate title commitments
US7788115B2 (en) System and method for coordination of benefits in a healthcare system
US20050015272A1 (en) Computer system and computer-implemented method for creating travel-expense statements
JP7506805B1 (en) BANKING SYSTEM AND METHODS PERFORMED BY BANKING SYSTEM - Patent application
JP2015141597A (en) Payment system and method using electronic money
JP7422923B1 (en) Information processing device, information processing method, and information processing program
JP2004287933A (en) System for warrantying banking transaction
US20060206419A1 (en) Business process and user interfaces for money transfer
US20040138973A1 (en) Method and system for exchange of currency related instructions
JP4689990B2 (en) Method and system for charging electronic money
AU2003236192A1 (en) Consideration payment management method and server, consideration payment management program and computer-readable recording medium, and consideration payment management medium and consideration payment recording medium
KR101880734B1 (en) Financial system for matching suitable investors based on the user&#39;s loan conditions
JP2006113816A (en) System for automatic payment by deduction from savings account
US20070203829A1 (en) System and methods for transmitting funds and instituting loans
JP7569417B1 (en) Payment processing device, payment processing method, and program
EP1486895A1 (en) Computer system and computer-implemented method for creating travel-expense statements
JP7502529B1 (en) Payment processing device, payment processing method, and program
JP2005216264A (en) Payment surrogate system and method
JP7519428B2 (en) Information processing device, method, and system

Legal Events

Date Code Title Description
A621 Written request for application examination

Free format text: JAPANESE INTERMEDIATE CODE: A621

Effective date: 20040913

A977 Report on retrieval

Free format text: JAPANESE INTERMEDIATE CODE: A971007

Effective date: 20060629

A131 Notification of reasons for refusal

Free format text: JAPANESE INTERMEDIATE CODE: A131

Effective date: 20060704

A521 Request for written amendment filed

Free format text: JAPANESE INTERMEDIATE CODE: A523

Effective date: 20060821

TRDD Decision of grant or rejection written
A01 Written decision to grant a patent or to grant a registration (utility model)

Free format text: JAPANESE INTERMEDIATE CODE: A01

Effective date: 20070220

A61 First payment of annual fees (during grant procedure)

Free format text: JAPANESE INTERMEDIATE CODE: A61

Effective date: 20070222

R150 Certificate of patent or registration of utility model

Free format text: JAPANESE INTERMEDIATE CODE: R150

FPAY Renewal fee payment (event date is renewal date of database)

Free format text: PAYMENT UNTIL: 20130302

Year of fee payment: 6

FPAY Renewal fee payment (event date is renewal date of database)

Free format text: PAYMENT UNTIL: 20140302

Year of fee payment: 7

R250 Receipt of annual fees

Free format text: JAPANESE INTERMEDIATE CODE: R250

R250 Receipt of annual fees

Free format text: JAPANESE INTERMEDIATE CODE: R250

LAPS Cancellation because of no payment of annual fees