WO2000036571A1 - Euro payment routing and intra-day flow control system and method - Google Patents
Euro payment routing and intra-day flow control system and method Download PDFInfo
- Publication number
- WO2000036571A1 WO2000036571A1 PCT/GB1999/004159 GB9904159W WO0036571A1 WO 2000036571 A1 WO2000036571 A1 WO 2000036571A1 GB 9904159 W GB9904159 W GB 9904159W WO 0036571 A1 WO0036571 A1 WO 0036571A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- clearing
- payment
- recited
- payment transaction
- channel
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/04—Billing or invoicing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/02—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/02—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
- G06Q20/023—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP] the neutral party being a clearing house
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/04—Payment circuits
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
Definitions
- the present invention generally relates to systems and methods for the routing of payment transactions between financial institutions and more particularly to a system and method for routing and controlling the flow of Euro payments through a plurality of clearing channels.
- the Trans-European Automated Real-Time Gross settlement Express Transfer (TARGET) system is the electronic payment system which is a crucial instrument for the European Central Bank's conduct of monetary policy. It is one mechanism which enables the cross boarder transfer of funds between banks in real time and allows payments to be made through the Euro zone at low cost with high security and very short processing times. TARGET also helps the development of sound and efficient payment mechanisms in the single market. Together with the fifteen National Central Banks (NCBs) of the member countries, the ECB is part of the European System of Central Banks (ESCB) whose primary objective is mamtaining price stability.
- NCBs National Central Banks
- ESCB European System of Central Banks
- the ESCB's basic tasks includes defining and implementing monetary policy for the Euro, conducting foreign exchange operation and holding and managing the official foreign reserves of the membered states.
- the ECB also promotes the smooth operation of payment systems and contributes to the work of the relevant national authorities and supervising credit institutions and stability of the financial system.
- FIG. 1 illustrates a clearing process prior to the introduction of the Euro.
- the example depicted in Figure 1 is a clearance between two German clearers 10, 15.
- TARGET system 50 to reach a destination Euro clearer 30, 35.
- a Euro clearer 30, 35 can use a correspondent financial institution 55 to directly clear a payment or use the correspondent 55 to clear a payment through an RTGS or non RTGS system 60 to which the Euro clearer is not a member.
- a clearer 30, 35 will be a member of one or more of the RTGS or non RTGS systems.
- the present invention is a system and method of routing Euro payments through one of the plurality of clearing channels.
- the method of the present invention is accomplished by two main processes, a routing process, and a flow control process.
- the routing process decides which clearing channel to use based on a number of factors such as the availability of the channel, customer instructions for routing, the clearing system memberships of the destination bank, agreements with the destination bank, priorities, and the type of payment.
- the flow control process monitors the balance for a clearing member within a selected channel, and the balance of the channel as a whole. Depending on whether the balances exceed predetermined limits, the flow control process will either hold a routed payment or release it down the channel.
- the system and method will allow customers to request specific Euro clearing mechanisms to be used for the Euro payment.
- all clearing transactions for a financial institution will be processed by a central legal hub. This is likely to require cross border membership of clearing systems.
- the routing and flow control processes are executed at this central hub.
- the routing clearing system memberships/access can be accomplished on a branch by branch basis, but with central control monitoring the routing and flow control.
- Figure 1 illustrates a prior art method of clearing a payment
- Figure 2 depicts the prior art channels of clearance after the introduction of the Euro
- FIG. 3 illustrates an overview of the system of the present invention.
- Figure 4 illustrates a preferred embodiment of the system of the present invention.
- Figure 5 is a flow chart of the preprocessing, routing and flow control processing at a hub location.
- Figure 6 shows the initial flow chart of the routing process.
- Figure 7 is a flow chart of the routing process when no route has been specified.
- Figure 8 depicts the decision process for selecting a channel where multiple are available.
- Figure 9 is a table containing details of the members of the clearing systems.
- Figure 10 illustrates a table containing the details of all the channels through which the hub can directly or indirectly process a payment.
- Element 100 represents the global operations of a financial institution such as a bank.
- Elements 105-115 represent the branches or subsidiaries of the bank distributed throughout the world.
- Element 120 represents a central legal entity, a hub, of the bank. In a preferred embodiment of the invention, hub 120 is a branch or subsidiary of the bank itself.
- Elements 125-150 represent six specific clearing channels to which the hub 120 is connected.
- Element 45 generically represents any RTGS clearing system while element 40 generically represents the MLNS systems.
- the hub 120 is also connected to correspondent financial institutions 55.
- each of the RTGSs 45, 125, 130 and 135 are illustrated as being connected to the TARGET system 50.
- TARGET system 50 As previously explained, through the TARGET system 50 any of the RTGSs are able to clear a payment through another RTGS.
- Other RTGS 45 and other non RTGS 40 clearing systems are important because they illustrate the flexibility of this invention. It is easy to add or drop clearing systems as appropriate with negligible impact on customers. This flexibility in using alternative channels is also very valuable in contingency situations.
- Step 200 in Fig. 5 processes incoming electronic messages (payment instructions) received by the hub 120. Such messages are transferred between the branches 105-115 and the hub 120 and between the institutional and corporate customers 160 and the hub 120. These messages can take many forms. Alternatively, payment instructions may be handled manually in which they are entered for processing via Manual Payment Input 215. With respect to payments, the transaction normally contains all of the relevant information required to process the payment including at least an identification of the payor, the payee and the amount. Sometimes it is necessary to refer back to the transaction originator.
- the instruction may, but does not have to include routing instructions.
- the customer of the hub might specify that the payment should be cleared through either RTGS or non RTGS without specifying the specific system to which routing can be made.
- the customer of the hub 120 can signify RTGS or non RTGS and additionally specify the specific RTGS non RTGS channel for use in the routing. If a specific channel is identified, the hub 120 may or may not be a member of that specific channel. If the hub 120 is a member of that specific channel, the routing process described below will attempt to satisfy that specific request. If the hub 120 is not a member of the specific requested channel, the straight through processing 220 will set the payment type to CLG which indicates that the router is free to decide upon the route which the payment will take. Similarly, if the customer of the hub 120 does not specify any routing preferences, the payment type will be set to CLG.
- the straight through processing 220 also ensures that sufficient details are contained in the payment instruction from the customer of the hub such that once the transaction gets to the payment routing (described below) the router will have sufficient details to choose any of the available clearing channels without having to send the transaction for manual inspection and repair.
- the validation process in step 220 ensures that sufficient details are available to process the payment transaction through the preferred payment channel for the transaction. If the payment is for same day value, then any closed channels (past cut off) are ignored when detern ining the preferred channel. If the payment can be made through only one clearing system then step 220 will ensure that sufficient details are present to process the payment transaction through that clearing system. If the payment can be made through many clearing systems, the straight through processing step 220 will ensure that sufficient details exist to process the payment transaction through only the preferred clearing system.
- Initial message processing 200 also processes incoming messages from the clearing systems which contain credits for customers
- the credit message identifies the clearing channel from which the credit came and the bank which sent the payment into the clearing channel. For credits received cross-border via TARGET the bank who sent the payment into the clearing channel will be the National Central Bank for that channel.
- the flow control process of the present invention described below is not interested in the particular customer 160 of the financial institution 100 for which the credit is destined (or for itself), flow control is only interested in the fact that a credit came in from a particular clearing channel. This is because flow control is only interested in maintaining balances on all of the channels and pay-banks and in keeping track of when a particular channel or pay-bank reaches its limit.
- the further processing of credits do not form part of the present invention and are not discussed herein.
- step 210 the initial message processing has identified outgoing payments received from customers of the hub 120.
- Payment instructions may be received via automated (steps 200-210) or manual (step 215) means. Certain automated instructions may be of such a format that they are printed and processed as manual instructions. With transactions which are processed automatically, there are sophisticated processes to try to process these transactions without any manual intervention whatsoever. This is referred to as Straight Through Processing (STP) and the primary processing is in boxes 200, 210 and 220. Where such a transaction cannot be processed straight through, it will go to payment repair 225 where an operator will amend the transaction such that it can continue processing. Only those details which are invalid or missing need be manually entered as all other details from the electronic processing are available.
- STP Straight Through Processing
- Manual Payment Input 215 performs an equivalent role to initial message processing 200 and the two subsequent stages 210 and 212, but on manual transactions.
- Manual transactions may originate as manual instructions, or from automated instructions which are printed on receipt, or from automated instructions which are removed from Payment Repair 225, or from certain other exception situations.
- Transactions entered via manual payment input 215 are subject to Verification 230 of critical data by a second operator.
- transactions going though payment repair 225 are also subject to Verification 230. If an error is identified at Verification 230, the transaction is returned to an earlier stage for correction.
- automated instructions may be sent direct from Straight Through Processing 220 to Verification 230. In rare instances, transactions at subsequent stages may be returned to Payment Repair 225.
- transactions are fully validated.
- Forward Value 235 transactions may be held in a queue awaiting value date. When the value date occurs, the transactions are released from the forward queue.
- Transactions are subject to Risk Control 245 which ensures that the outgoing payments for a particular customer do not exceed the receipts by more than a defined limit. It is desirable to do this process as late as possible to keep the limits to the minimum.
- Full automation of all subsequent stages of processing, e.g. in payment routing and flow control, is essential to minimize the limits, and therefore the risk which is taken by the financial institution.
- Element 250 is the Payment Router of the present invention.
- Payment router 250 shall be discussed below in more detail, but in general the Payment Router 250 decides, based on a series of rules, how a payment should be routed through the various channels 280. Channels 280 generically describe the various RTGS and non RTGS channels previously described. Once the appropriate channel for transmission of the payment has been determined by Payment Router 250, the Payment Router 250 passes the payment transaction onto the flow control processes 255.
- the first flow control method bi-lateral limit validation 260, checks the proposed payment against the balance currently maintained by the hub 120 for the clearing member (the destination pay-bank on an individual channel basis). This will only apply where the transaction is being routed down a channel to which both the hub 120 and the destination pay bank are directly connected. All cross border transactions via TARGET will be accumulated against the National Central Bank which operates the system.
- the flow control processing monitors the bi-lateral limits within the clearing systems. It maintains the total number and amounts of payment set to each destination clearer on a daily basis. If a proposed payment would put the totals over the limit which has been set for that destination clearer, then the flow control process puts a hold on the payment and will not let it be transferred out of the hub 120.
- a second process 262 performed in the Flow Control module 255 looks at the maximum amount for an individual payment through each channel 280. Transactions which are above this maximum level require manual action.
- the third process 265 performed in the flow control method 255 looks at the balance for the selected channel as a whole. In steps 260- 265, it is determined whether or not the proposed payment transaction exceeds set limits. If the proposed payment would exceed one of these predetermined limits in any of theses steps 260-265, the determination of the fate of the proposed payment may be determined in an on-line flow control process 270. Alternatively there are automated re-try processes within the bi-lateral 260 and overall checks 265 which are invoked periodically during the day to take into account each new credit received for the relevant channel 280.
- an operator manually reviews the transaction and the current circumstances which caused the transaction to exceed the predetermined limits.
- the operator may have additional knowledge by which he or she may determine that a payment may be passed on to a particular channel even though its clearing will exceed the predetermined limits. For example, the operator might have knowledge that a particular credit has not yet been posted to the channel balance and that the processing of the proposed payment transaction will not be denied by the channel because of excess debits. At this stage, in rare instances, the operator may need to return the payment to Payment Repair 225.
- the on-line flow control function 270 also provides for inquiring on and controlling payments held at the various stages of the flow control checks 260, 265.
- the on-line flow control process 270 is manually operated by the operators at the hub 120. Using this on-line system 270 the operators are able to select one or more of the clearing queues in order to display all of the held payments. Additionally, the operators can manually release any of the queued payments down the specified channel 280 if 5 required. Furthermore, the operators can manually put a payment back into the Payment Router 250 so a different channel 280 can be selected. Rerouting back to the Routing module 250 or releasing of a payment from the hold queue will cause the bi-lateral and channel totals to be automatically updated as appropriate.
- the flow control limits for each of the channels and the clearing member banks are stored in a table. These limits are keyed both with respect to the clearing member bank to which payment instructions are sent, and by the clearing channel.
- the table contains the agreed upon balance limits, the current balance, the number of payments held due to the 5 limit checks, and the maximum value of individual payments allowed.
- the flow control processing has a number of generic defaults which apply in new situations where limits have not previously been set by the operators. For example where a new bank joins a clearing, if an 5 operator has not previously defined a limit for that bank then some default processing will apply to control payments for that bank with a limit forcing all payments to be held.
- the Product Generation module 275 the actual message which is transmitted to the channels 280 for clearing is generated.
- the format of the messages which are generated, will differ depending on which channel 280 is used.
- the channel 280 Upon reaching a defined stage of processing, the channel 280 will return an acknowledgment 285 which is used to update the hub's 120 records as appropriate.
- Other products may be generated in Product Generation 275 such as advices to various parties to the transaction.
- a contingency function is provided to capture payments that have either been rejected at the clearing bank or encountered in an error at some stage of the payment flow out to the clearing bank. If such is the case, the rejected or errored payments can be manually set back to payment repair (step 225) or back to the Payment Router 250 (see step 300 in Fig.
- FIGS. 6-8 illustrate the processing of the Payment Router 250 of the presentinvention.
- the processing starts at step 300 with an initialization process 305 in which technical preparatory work is performed.
- step 310 the record for the proposed transaction is read.
- the message from the customers of the hub 120 will contain at least an identification of the payor, payee and the amount of the payment.
- the transaction record may contain an identification of a clearing channel which is preferred by the customer 160. If the customer does not identify a preferred channel of clearance, this field will contain the payment type CLG.
- step 325 it is determined whether or not a clearing channel has yet been identified. As previously described, this channel can be identified by the customer, or alternatively can be manually entered by the operators of the hub 120. If the payment type is set to CLG, the router is free to automatically determine the appropriate channel for routing as illustrated in Figures 7 and 8.
- Step 330 initiates the process of deciding if the specified channel is available.
- step 335 it is determined whether or not the channel is available for use at all.
- a channel table is maintained which contains the status of all of the channels to which the hub 120 is connected.
- An example of such a clearing channel table is in contained in Figure 10. If the channel is not available as determined by the status field contained in the clearing channel table, the process continues at step 365 described below. If the channel is available, it is then decided at step 340 whether or not the particular channel is on holiday. As some of the institutions which maintain the channels recognize national holidays which are not universal, a channel could be on a different holiday schedule than observed by the hub 120. The holiday schedule for each channel is maintained in the clearing channel table (Fig. 10). If the channel is on holiday, the processing will continue in step 365.
- the cut off time is the last time of day at which a channel will except a payment for processing.
- the cut-off time details are contained in the channel table illustrated in Figure 10. If the cut-off time has already passed, processing continues in step 365. If there is sufficient time to pass the payment on to the channel, the process continues in step 350. Step 350 has been included in this Figure to indicate that additional checks may be made with respect to the channel availability such as the current debit position. 5 If the channel availability tests 335-350 are all satisfied, it is determined in step 355 if there are any other special formatting requirements. The payment transaction is sent to the flow control processing in step 360 (see step 255 in Fig. 5).
- step 365 it is because the 0 requested or designated channel is not available for use.
- step 365 it is determined whether or not the payment is a liquidity payment i.e., a payment initiated by the hub 120 solely for the purposes of moving funds from one channel to another - moving the liquidity.
- the channel can not be 5 changed because of the nature of the payment as described above (step
- step 370 If such is the case, the payment is sent back to payment repair in step 375 (see Fig. 5).
- step 365 it is determined whether or not there is any o information contained in the payment transaction record which identifies the type of channel which should be used (e.g., use RTGS, but the specific RTGS channel is not identified). If such information does exist in the payment transaction record, the channel type is set to the appropriate type (e.g., RTGS)(step 390).
- /NETT/ is a generic coding used in the 5 system to identify a request for a non RTGS clearing channel
- /RTGS/ identifies a request for an RTGS channel. If no such channel details exists in the transaction record, the channel type is set depending on the payment type of the instruction. The payment type will indicate the channel which was originally chosen. If this is of type RTGS, channel type 0 will be set to /RTGS/. If it is of non RTGS type, channel type will be set to /NETT/. The channel type is retrieved from the channel table contained in Figure 10.
- the payment type is set to CLG (step 395) and the payment transaction is sent on to the process for determining the particular channel as illustrated in Figure 7.
- Step 400 in Figure 7 is the initiation of the routing process when no specific route has been identified (step 327 in Fig. 6) or when the request for a specified channel could not be satisfied (step 397 in Fig. 6).
- step 405 a list of available clearing channels is retrieved using the clearing channel tables depicted in Figures 9 and 10. If the transaction specifies that the payment should be processed through an RTGS or a non RTGS channel, any non-RTGS or RTGS clearing channels respectively should be excluded from this list.
- step 410 it is determined whether or not a destination clearing bank is directly connected to any of the same clearing systems as the hub 120. If clearing channel returned is TGT (TARGET) or COR (correspondent), there is no such mutual direct connection.
- step 415 it is determined whether there is more than one. This determination is made using the clearing channel options determined in 405.
- the CMD table depicted in Figure 9 allows for the maintenance of channel membership by pay- bank. Each pay-bank/channel combination is held in a different record in the table. This structure allows for easier prioritizing of channels when a pay-bank is a member of more than one clearing system.
- the pay-bank/ channel information can either be manually maintained or an electronic batch process may capture the channel membership details.
- the CMD table also contains details relating to the preferred routing method. If a pay-bank and the hub 120 have more than one mutual direct connection, the priority is indicated in the CMD table but only if this differs from the default priority as held on the ECC table illustrated in Figure 10. If the pay-bank and the hub 120 do not have a mutual direct connection, TGT (TARGET) and/or COR
- a validation is performed in order to verify that that channel can be used (step 420).
- such validation can include determining if the channel is on holiday or if the cut-off time for that channel has been reached. Again, this validation process employs the clearing channel table as depicted in Figure 10. If it is determined that the channel cannot be used (NO out of step 425) the proposed transaction is sent to repair for manual determination of how to process the transaction as previously described. If the channel can be used, the payment type in the transaction record is set to the specified channel in step 435.
- step 440 it is determined whether it is the TARGET system or a correspondent which is to be used. If a correspondent is to be used, the payment type is set to CPO and the correspondent details are read from the clearing channel table (Fig. 10). In step 445, the record for the correspondent in the clearing channel table is read which contains the SWIFT addressed for the correspondent which will enable routing of the payment transaction.
- step 450 the process determines if there are any specific formatting requirements for the channel which has been specified by the 5 routing process, and the payment transaction is forwarded to the flow control process in step 455 (see Fig. 5).
- step 440 If it is determined in step 440 that the TARGET system is to be used, the list of available clearing channels obtained in step 405 is narrowed to only included the RTGS clearings. This narrowed list is then o prioritized according to default priorities.
- step 465 if a pay- bank is a member of more than one clearing system (YES out of step 415) the available clearing systems to which the pay-bank is a member are prioritized. However, in the instance the pay-bank override priority from the CMD table ( Figure 9) will be used if it is present. In either of these 5 cases, the list of available prioritized channels is passed to the process (Fig.
- step 500 of Figure 8 the prioritized list of channels which can be used to route the payment is provided to the channel decision process.
- step 505 the priority will be changed if required by 5 circumstances at the time the final decision is being made. For example, certain payment channels require a minimum volume of payments to be submitted as held on the ECC table ( Figure 10). These "priority changes" are automated.
- step 510 it is determined whether all of the channels in the o list have been processed. If not, a decision making process is performed in steps 515-530.
- the decision making process 515-530 is the same as discussed above with respect to step 420 in Figure 7 and steps 335-350 in Figure 6. If a channel passes all the rules and can therefore be used, the payment type is set to the specified channel and any special formatting required for that channel is identified in step 535. The payment transaction is then sent to the flow control process in step 540.
- step 510 If all of the available channels have been processed and none of them, for one reason or another, is available for use (YES out of step 510) an error is generated as no channel can be used (step 545). If such is the case, the payment transaction is sent to repair for manual determination of the appropriate channel to use in routing the transaction (step 550).
- Supporting this invention there are a number of generic "housekeeping" processes which will run on periodic bases to ensure the smooth operation.- These are not defined specifically, but include a nightly reset of Flow Control balances to zero and a cleardown of historical data from the Flow Control Process.
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP99959562A EP1141908A1 (en) | 1998-12-15 | 1999-12-10 | Euro payment routing and intra-day flow control system and method |
AU16702/00A AU1670200A (en) | 1998-12-15 | 1999-12-10 | Euro payment routing and intra-day flow control system and method |
HK02102590.8A HK1044841A1 (en) | 1998-12-15 | 2002-04-08 | Euro payment routing and intra-day flow control system and method |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11233198P | 1998-12-15 | 1998-12-15 | |
US60/112,331 | 1998-12-15 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2000036571A1 true WO2000036571A1 (en) | 2000-06-22 |
Family
ID=22343324
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/GB1999/004159 WO2000036571A1 (en) | 1998-12-15 | 1999-12-10 | Euro payment routing and intra-day flow control system and method |
Country Status (4)
Country | Link |
---|---|
EP (1) | EP1141908A1 (en) |
AU (1) | AU1670200A (en) |
HK (1) | HK1044841A1 (en) |
WO (1) | WO2000036571A1 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1686471A1 (en) * | 2005-01-31 | 2006-08-02 | Ubs Ag | Method for the scheduling of software modules |
US7689483B2 (en) | 2003-05-20 | 2010-03-30 | Amegy Bank of Texas | System to facilitate payments for a customer through a foreign bank, software, business methods, and other related methods |
EP2413277A1 (en) * | 2010-07-26 | 2012-02-01 | Accenture Global Services Limited | System and method for prioritizing processing of payment instructions |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4823264A (en) * | 1986-05-27 | 1989-04-18 | Deming Gilbert R | Electronic funds transfer system |
US5848400A (en) * | 1996-07-01 | 1998-12-08 | Sun Microsystems, Inc. | Electronic check exchange, clearing and settlement system |
-
1999
- 1999-12-10 WO PCT/GB1999/004159 patent/WO2000036571A1/en not_active Application Discontinuation
- 1999-12-10 AU AU16702/00A patent/AU1670200A/en not_active Abandoned
- 1999-12-10 EP EP99959562A patent/EP1141908A1/en not_active Ceased
-
2002
- 2002-04-08 HK HK02102590.8A patent/HK1044841A1/en unknown
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4823264A (en) * | 1986-05-27 | 1989-04-18 | Deming Gilbert R | Electronic funds transfer system |
US5848400A (en) * | 1996-07-01 | 1998-12-08 | Sun Microsystems, Inc. | Electronic check exchange, clearing and settlement system |
Non-Patent Citations (1)
Title |
---|
D. O'MAHONY M. PIERCE H. TEWARI: "Electronic Payment System", 1997, ARTECH HOUSE, BOSTON LONDON, XP002137255, 236620 * |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7689483B2 (en) | 2003-05-20 | 2010-03-30 | Amegy Bank of Texas | System to facilitate payments for a customer through a foreign bank, software, business methods, and other related methods |
EP1686471A1 (en) * | 2005-01-31 | 2006-08-02 | Ubs Ag | Method for the scheduling of software modules |
WO2006081917A2 (en) * | 2005-01-31 | 2006-08-10 | Ubs Ag | Method for the control of software modules |
WO2006081917A3 (en) * | 2005-01-31 | 2006-11-30 | Ubs Ag | Method for the control of software modules |
EP1760587A1 (en) * | 2005-01-31 | 2007-03-07 | Ubs Ag | Method for the scheduling of software modules |
US7818750B2 (en) | 2005-01-31 | 2010-10-19 | Usb Ag | Method for controlling software modules |
EP2413277A1 (en) * | 2010-07-26 | 2012-02-01 | Accenture Global Services Limited | System and method for prioritizing processing of payment instructions |
US8458091B2 (en) | 2010-07-26 | 2013-06-04 | Accenture Global Services Limited | System and method for prioritizing processing of payment instructions |
Also Published As
Publication number | Publication date |
---|---|
HK1044841A1 (en) | 2002-11-01 |
AU1670200A (en) | 2000-07-03 |
EP1141908A1 (en) | 2001-10-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10262306B2 (en) | System and method for intraday netting payment finality with supplemental funding | |
US8543477B2 (en) | Value tracking and reporting of automated clearing house transactions | |
US8417636B2 (en) | Approving ACH operator processing of ACH payments based on an originating depository financial institution's approved originator list | |
US6970843B1 (en) | Financial management system | |
US7899743B2 (en) | Method for fully insuring large bank deposits using a plurality of banks that receive portions of each large deposit | |
KR100237935B1 (en) | Electronic transaction system | |
EP2219147A1 (en) | Systems, methods and computer program products for managing payment processes in a comprehensive payment hub system | |
US7580886B1 (en) | Managing foreign payments in an international ACH | |
US6996542B1 (en) | System and method for paying bills and other obligations including selective payor and payee controls | |
US5956700A (en) | System and method for paying bills and other obligations including selective payor and payee controls | |
AU2011204887B2 (en) | System and method for prioritizing processing of payment instructions | |
US20070162387A1 (en) | System and method for optimized funding of electronic transactions | |
US20040128240A1 (en) | Method and system for managing financial transactions | |
US20070005498A1 (en) | System and method for optimized funding of electronic transactions | |
US20090076935A1 (en) | System and Method of Account Reconciliation for Electronic Transactions | |
US20100211499A1 (en) | Systems, methods and computer program products for optimizing routing of financial payments | |
JP2004213124A (en) | Fund management method and system | |
WO2003079261A1 (en) | Card-based system and method for issuing negotiable instruments | |
US20130036047A1 (en) | Method, system and process for centralized management and control of a budget and electronic mass distribution of funds | |
WO2009029331A1 (en) | Methods and systems for executing a plurality of money transfers having a fluctuating parameter | |
US20100211495A1 (en) | Systems, methods and computer program products for improving foreign currency exchange in a comprehensive payment hub system | |
US8099359B1 (en) | System and method for issuing negotiable instruments by licensed money transmitter from direct deposits | |
EP1141908A1 (en) | Euro payment routing and intra-day flow control system and method | |
JP2003288490A (en) | Automatic processing system, aggregation server and automatic processing method | |
JPH05135253A (en) | Cash management system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
ENP | Entry into the national phase |
Ref country code: AU Ref document number: 2000 16702 Kind code of ref document: A Format of ref document f/p: F |
|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AL AM AT AU AZ BA BB BG BR BY CA CH CN CU CZ DE DK DM EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): GH GM KE LS MW SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
WWE | Wipo information: entry into national phase |
Ref document number: 1999959562 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 09868176 Country of ref document: US |
|
WWP | Wipo information: published in national office |
Ref document number: 1999959562 Country of ref document: EP |
|
REG | Reference to national code |
Ref country code: DE Ref legal event code: 8642 |
|
WWR | Wipo information: refused in national office |
Ref document number: 1999959562 Country of ref document: EP |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: 1999959562 Country of ref document: EP |