The present invention relates to the field of electronic transactions, and more specifically to systems, methodsand computer program products for responding to network communication failure when implementing electronic transactions.
Background
[002] Electronic payment transactions involving payment cards or other electronic tokens are increasingly prevalent — particularly with the increase in e-commerce transactions.
[003] Figure 1 illustrates a prior art system environment 100 including entities involved in a typical electronic payment transaction. System environment 100 includes a payor bank 102, a payment network 104 and a payee bank 106.
[004] In implementing an electronic payment transaction, payor bank 102 transmits to payment network 104, apayment instruction for transferring a transaction amount from a payor payment account held at payor bank 102 to a payee payment account held at payee bank 106. Transmission of the payment instruction is accompanied by payor bank 102 debiting or placing a hold on the transaction amount at the payor payment account. Payment network 104 transmits to payee bank 106, a payment message informing payee bank 106 that payor bank 102 is transferring the transaction amount into a payee payment account. Payee bank 106 uses the information within the payment message to update its internal records. During the next transaction settlement between payor bank 102 and payee bank 106, the transaction amount is transferred from payor bank 102 to payee bank 106, and payee bank 106 credits the transaction amount to the payee bank account.
[005] Figure 2 illustrates a prior art system environment 200 that illustrates in detail, entities within system environment 100.System environment 200 includes payor institution server platform 202, payment network server 204, and payee institution server platform 206.

[006] Payor institution server platform 202 is a server platform configured to implement the functionality of payor bank 102 — and includes payment network interface processor (PNIP) 202a, server 202b and database 202c.PNIP 202a is a processor or server that is implemented at the edges of payment network 204, and which is a hardware communication interface between server 202b and payment network 204. In an embodiment, PNIP 202a may be configured to have at least two ports. The first port provides a direct link between PNIP 202a and payment network 204 (to which server 202b has no direct access) and the second port is integrated or communicably coupled with server 202b through any of a TCP/IP protocol / a switch / a router / a firewall device.PNIP 202a therefore serves as a secure communication intermediary that enables server 202b and payment network 204 to communicate with each other through PNIP 202a. In an embodiment where payment network 204 is the Mastercard ® payment network, PNIP 202a includes one or more Mastercard Interface Processors (MIPs) that are installed in the form of one or more servers on the premises of the payor institution.
[007] Server 202b includes one or more servers, including hardware, software and other equipment used by payor institution server platform 202 to maintain and operate payment accounts held with the payor institution, and to implement electronic payment transactions involving payment accounts held with the payor institution. Database 202c includes non-transitory memory based database(s), configured to store data records corresponding to payment accounts held with the payor institution and electronic payment transactions initiated at or processed through server 202b.
[008] Payee institution server platform 206 is a server platform configured to implement the functionality of payee bank 106 (in Figure 1) — and includes payment network interface processor (PNIP) 206a, server 206b and database 206c. PNIP 206a is a processor or server that is implemented at the edges of payment network 204, and which serves as a hardware communication interface between server 206b and payment network 204. In an embodiment, PNIP 206a may be configured to have at least two ports .The first port provides a direct link between PNIP 206a and payment network 204 (to which server 206b has no direct access) and the second port is integrated or communicably coupled with server 206b through any of a TCP/IP protocol / a switch / a router / a firewall device. PNIP 206a therefore serves as a secure communication intermediary that enables server 206b and payment network 204 to communicate with each other through PNIP 206a. In an

embodiment where payment network 204 is the Mastercard ® payment network, PNIP 206a includes one or more Mastercard Interface Processors (MIPs) installed in the form of one or more servers on the premises of the payor institution.
[009] Server 206b includes one or more servers, including hardware, software and other equipment used by payee institution server platform 206 to maintain and operate payment accounts at the payee institution, and to implement electronic payment transactions involving one or more payment accounts held with the payee institution. Database 206c includes non-transitory memory based database(s), configured to store data records corresponding to payment accounts held with the payee institution and electronic payment transactions initiated or processed through server 206b.
[0010] Payment network server 204 includes one or more servers configured to function as an intermediary network communicatively disposed between payor institution server platform 202 and payee institution server platform 206 — and is configured to enable communication and electronic payment transactions between the two entities.
[0011] Figure 3 illustrates a prior art method for responding to network communication failure when implementing electronic transactions within system environment 200.
[0012] Step 302 includes receiving from server 202b within payor institution server platform 202, a payment instruction initiated by a payor — and identifying a payor payment account, payee payment account and transaction amount. The payment instruction is routed to payment network server 204 through PNIP 202a. At step 304, server 202b debits or places a hold on the transaction amount, at the payor payment account.
[0013] At step 306, payment network server 204 initiates transmission of a transaction instruction to server 206b within payee institution server platform 206. Transmission of the transaction instruction to server 206b is routed through payment network interface processor 206a.
[0014] At step 308, responsive to detection of a transmission failure event associated with the data transmission at step 306, payment network server 204 sends a transaction failure message to server 202b withinpayor institution server platform 202. At step 310, responsive to receipt of a transaction

failure message, server 202b in turn notifies the payor of the transaction failure. Thereafter at step 312, server 202b initiates the process of crediting back, or releasing the hold on, the transaction amount at the payor payment account.
[0015] The process of crediting back, or releasing a hold on, a transaction amount ordinarily takes between 10 to 48 hours — duringwhich period, the payor is unable to access or use the funds associated with the transaction amount. Existing payment systems are unable eliminate this time window, for the reason that payment network 204 and / or payor institution server platform 202 requires this time to ensure that the funds have not been already credited to the payee payment account.
[0016] There is accordingly a need to ensure that transaction funds can be immediately credited back or released into a payor payment account, in response to detection of a payment transaction failure event — while simultaneously ensuring that the credit or release only occurs after ensuring that the funds have not already been credited to the payee.
Summary
[0017] The present invention provides systems, methods and computer program products for responding to network communication failure when implementing electronic transactions.
[0018] The invention provides a method for responding to a transmission failure event corresponding to an electronic payment transaction. The method comprises the steps of (i) receiving a payment instruction initiated by a payor for transferring a transaction amount from a payor payment account to a payee payment account, (ii) initiating at a payment network server, transmission of a transaction instruction to a first communication end point of a payee institution server, (iii) responsive to detection of a transmission failure event in connection with transmission of the payment transaction instruction to the payee institution server (a) initiating transmission of a first transaction failure message to a payor institution server, and (b) initiating transmission of a second transaction failure message to a second communication end point of the payee institution server.

[0019] The payor institution server may be configured to respond to receiving the first transaction failure message by reversing a previous debit or transaction hold corresponding to the transaction amount that has been applied by the payor institution server at the payor payment account.
[0020] In a method embodiment, the first communication end point of the payee institution server and the second communication end point of the payee institution server are distinct.
[0021] In another embodiment of the method, transmission of the first transaction failure message and transmission of the second transaction failure message are both initiated at the payment network server.
[0022] In a particular embodiment of the method, (i) the payment instruction initiated by the payor is transmitted to the payment network server from a first communication end point of the payor institution server, and (ii) the first transaction failure message is transmitted to a second communication end point of the payor institution server, wherein the second communication end point of the payor institution server is distinct from the first communication end point of the payor institution server.
[0023] In another embodiment of the method, (i) the first communication end point of the payee institution server is a payment network interface processor, and (ii) the second communication end point of the payee institution server is an alternate server interface.
[0024] In an exemplary embodiment of the method, (i) the first communication end point of the payor institution server is a payment network interface processor, and (ii) the second communication end point of the payor institution server is an alternate server interface.
[0025] In a specific embodiment of the method, the transmission failure event comprises (i) a detected failure in establishing a communication channel between any of (a) the payment network server and the payee institution server, (b) the payment network server and the first communication end point of the payee institution server, or (c) a first communication end point of the payee institution server and the payee institution server, or (ii) a detected response timeout event corresponding to any data message related to the transaction instruction transmitted to the first

communication end point of the payee institution server over a communication channel established between any of (d) the payment network server and the payee institution server, (e) the payment network server and the first communication end point of the payee institution server, or (f) a first communication end point of the payee institution server and the payee institution server.
[0026] The invention also provides a system configured for responding to a transmission failure event corresponding to an electronic payment transaction. The system comprises a payment network server configured for (i) receiving a payment instruction initiated by a payor for transferring a transaction amount from a payor payment account to a payee payment account, (ii) initiating transmission of a transaction instruction to a first communication end point of a payee institution server, (iii) responsive to detection of a transmission failure event in connection with transmission of the payment transaction instruction to the payee institution server, (a) initiating transmission of a first transaction failure message to a payor institution server, and (b) initiating transmission of a second transaction failure message to a second communication end point of the payee institution server. The payor institution server may be configured to respond to receiving the first transaction failure message by reversing a previous debit or transaction hold corresponding to the transaction amount that has been applied by the payor institution server at the payor payment account.
[0027] The system may be configured such that the first communication end point of the payee institution server and the second communication end point of the payee institution server are distinct.
[0028] In an embodiment, the system may be configured such that transmission of the first transaction failure message and transmission of the second transaction failure message are both initiated at the payment network server.
[0029] In a particular system embodiment, (i) the payment instruction initiated by the payor is transmitted to the payment network server from a first communication end point of the payor institution server, and (ii) the first transaction failure message is transmitted to a second communication end point of the payor institution server, wherein the second communication end point of the payor institution server is distinct from the first communication end point of the payor institution server.

[0030] In one embodiment of the system, (i) the first communication end point of the payee institution server is a payment network interface processor, and (ii) the second communication end point of the payee institution server is an alternate server interface.
[0031] The system may be configured such that (i) the first communication end point of the payor institution server is a payment network interface processor, and (ii) the second communication end point of the payor institution server is an alternate server interface.
[0032] In a particular embodiment, the system is configured such that the transmission failure event comprises (i) a detected failure in establishing a communication channel between any of (a) the payment network server and the payee institution server, (b) the payment network server and the first communication end point of the payee institution server, or (c) a first communication end point of the payee institution server and the payee institution server, or (ii) a detected response timeout event corresponding to any data message related to the transaction instruction transmitted to the first communication end point of the payee institution server over a communication channel established between any of (d) the payment network server and the payee institution server, (e) the payment network server and the first communication end point of the payee institution server, or (f) a first communication end point of the payee institution server and the payee institution server.
[0033] The invention provides a computer program product for responding to a transmission failure event corresponding to an electronic payment transaction. The computer program product comprises a non-transitory computer readable medium having a computer readable program code embodiment therein, the computer readable program code comprising instructions for (i) receiving a payment instruction initiated by a payor for transferring a transaction amount from a payor payment account to a payee payment account, (ii) initiating at a payment network server, transmission of a transaction instruction to a first communication end point of a payee institution server, (iii) responsive to detection of a transmission failure event in connection with transmission of the payment transaction instruction to the payee institution server (a) initiating transmission of a first transaction failure message to a payor institution server, and (b) initiating transmission of a second transaction failure message to a second communication end point of the payee institution server. The payor institution server may be configured to respond to receiving the first transaction failure

message by reversing a previous debit or transaction hold corresponding to the transaction amount that has been applied by the payor institution server at the payor payment account.
Brief Description of the Accompanying Drawings
[0034] Figure 1 illustrates a prior art system environment including entities involved in an electronic payment transaction.
[0035] Figure 2 illustrates a prior system environment that includes component level entities involved in effecting an electronic payment transaction between a payor bank and a payee bank.
[0036] Figure 3 is a flowchart illustrating a prior art method for responding to a transmission failure event detected during implementation of an electronic payment transaction within the system environment of Figure 2.
[0037] Figure 4 illustrates a system environment configured in accordance with the teachings of the present invention, for effecting an electronic payment transaction between a payor institution and a payee institution.
[0038] Figure 5 is a flowchart illustrating a first method for responding to a transmission failure event detected during implementation of an electronic payment transaction within the system environment of Figure 4.
[0039] Figure 6is a communication flow diagram illustrating communication flow between system entities, for implementing the method of Figure 5.
[0040] Figure 7 is a flowchart illustrating a second method for responding to a transmission failure event detected during implementation of an electronic payment transaction within the system environment of Figure 4.
[0041] Figure 8 is a communication flow diagram illustrating communication flow between system entities, for implementing the method of Figure 7.

[0042] Figure 9 is a flowchart illustrating a method implemented by a payor institution server (or payor institution server platform) in response to receiving intimation of transaction failure.
[0043] Figure 10A is a flowchart illustrating a first method for responding to detection of a transmission failure event in connection with an electronic payment transaction.
[0044] Figure 10B is a flowchart illustrating a second method for responding to detection of a transmission failure event in connection with an electronic payment transaction.
[0045] Figure 11 illustrates an embodiment of a payment network server configured to implement the teachings of the present invention.
[0046] Figure 12 illustrates an exemplary data message record structure for communicating information relating to a transmission failure event.
[0047] Figure 13 illustrates an exemplary computer system of a type that may be used to implement the teachings of the present invention.
Detailed Description
[0048] The invention provides systems, methods and computer program products for responding to network communication failure when implementing electronic transactions. It is an object of the invention to ensure that transaction funds that have been debited from a payor account or that have been subjected to a hold at the payor account, in response to initiation of an electronic payment transaction, can be credited back or released into the payor payment account expeditiously in case the payment transaction fails. A second object of the invention is to ensure that anysuch credit or release of a transaction hold only occurs after ascertaining that the funds have not already been credited to the payee.
[0049] For the purposes of the present invention, the following terms shall be understood to
have the corresponding meanings provided below.

[0050] "Payee" shall mean an individual or entity receiving an electronic payment.
[0051] "Payee Bank" or'Tayee Institution" shall mean an institution or business (e.g., a
financial institution or a merchant bank) that contracts with a payee to hold or maintain a payment account in the name of a payee, and which coordinates with other institutions or businesses to enable sending or receiving of electronic payments from or into one or more payment accounts held at or maintained with such institution.
[0052] "Payment account" shall mean any account that may be used for the purposes of
effecting an electronic payment or electronic transaction, and shall include any electronic transaction account, payment card account, bank account or electronic wallet account.
[0053] "Payment network" shall refer to any intermediary network communicatively disposed
between a payor bank and a payee bank. In certain embodiments, the payment network may include a network that enables communication between the payor bank and the payee bank (for example, Mastercard® or Visa®). In such embodiments, the payment network primarily coordinates payment transactions between a payor bank and a payee bank, and additionally coordinates clearing and settlement services to transfer payments from payor(s)to payee(s).
[0054] "Payor" shall mean an individual or entity making an electronic payment.
[0055] "Payor Bank" or "Payor Institution" shall mean an institution or business (e.g., a
financial institution or a merchant bank) that contracts with a payor to hold or maintain a payment account in the name of a payor, and which coordinates with other institutions or businesses to enable sending or receiving of electronic payments from or into one or more payment accounts held at or maintained with such institution.
[0056] Figure 4 illustrates a system environment 400 configured in accordance with the teachings of the present invention, for effecting an electronic payment transaction between a payor institution and a payee institution.

[0057] System environment 400 includes payor institution server platform 402, payment network server 404, and payee institution server platform 406.
[0058] Payor institution server platform 402 is a server platform configured to implement the functionality of a payor bank — and includes payment network interface processor (PNIP) 402a, server 402b, database 402c, and alternate server interface 402d. In an embodiment, payor institution server platform 402 may be implemented within the infrastructure of a payor institution. PNIP 402a is a processor or server that is implemented at the edges of payment network 404, and which serves as a first communication end point associated with server 402b within payor institution server platform 402. PNIP 402a includes a first hardware communication interface between server 402b and payment network 404. In an embodiment, PNIP 402a may be configured to have at least two ports. The first port provides a direct link between PNIP 402a and payment network 404 (to which server 402b has no direct access) and the second port is integrated or communicably coupled with server 402b through any of a TCP/IP protocol / a switch / a router / a firewall device. PNIP 402a therefore serves as a secure communication intermediary that enables server 402b and payment network 404 to communicate with each other through PNIP 402a.In an embodiment where payment network 404 is the Mastercard ® payment network, PNIP 402a includes one or more Mastercard Interface Processors (MIPs) that are installed in the form of one or more servers on the premises of the payor institution.
[0059] Server 402b includes one or more servers, including hardware, software and other equipment used by payor institution server platform 402 to maintain and operate payment accounts held with the payor institution, and to implement electronic payment transactions involving payment accounts held with the payor institution. Database 402c includes non-transitory memory based database(s), configured to store data records corresponding to payment accounts held with the payor institution and electronic payment transactions initiated at or processed through server 402b.
[0060] Alternate server interface 402d includes a processor, server or other processor based communication end point, which is a second communication end point associated with server 402b within payor institution server platform 402. Alternate server interface 402d includes a second communication interface (and may include a hardware communication interface, a software communication interface, or a combination of the two) between server 402b and payment network

404. In an embodiment, alternate server interface 402d may also be configured to have at least two ports. The first port may provide a second communication link between alternate server interface 402d and payment network 404 (to which server 402b has no direct access) and the second port may be integrated or communicably coupled with server 402b. As a result, alternate server interface 402d serves as an alternate communication intermediary that enables server 402b and payment network 404 to communicate with each other through alternate server interface 402d.
[0061] Payee institution server platform 406 is a server platform configured to implement the functionality of a payeeinstitution — and includes payment network interface processor (PNIP) 406a, server 406b, database 406c, and alternate server interface 406d. In an embodiment, payee institution server platform 406 may be implemented within the infrastructure of a payee institution.
[0062] PNIP 406a is a processor or server that is implemented at the edges of payment network 404, and which is a first communication end point associated with server 406b within payee institution server platform 406. PNIP 406a includes a first hardware communication interface between server 406b and payment network 404. In an embodiment, PNIP 406a may be configured to have at least two ports. The first port provides a first direct link between PNIP 406a and payment network 404 (to which server 406b has no direct access) and the second port is integrated or communicably coupled with server 406b through any of a TCP/IP protocol / a switch / a router / a firewall device. PNIP 406a therefore serves as a secure communication intermediary that enables server 406b and payment network 404 to communicate with each other through PNIP 406a.In an embodiment where payment network 404 is the Mastercard ® payment network, PNIP 406a includes one or more Mastercard Interface Processors (MIPs) that are installed in the form of one or more servers on the premises of the payee institution.
[0063] Server 406b includes one or more servers, including hardware, software and other equipment used by payee institution server platform 406 to maintain and operate payment accounts held with the payee institution, and to implement electronic payment transactions involving payment accounts held with the payee institution. Database 406c includes non-transitory memory based database(s), configured to store data records corresponding to payment accounts held with the payee institution and electronic payment transactions initiated at or processed through server 406b.

[0064] Alternate server interface 406d includes a processor, server or other processor based communication end point, which is a second communication end point associated with server 406b within payee institution server platform 406. Alternate server interface 406d includes a second communication interface (and may include a hardware communication interface, a software communication interface, or a combination of the two) between server 406b and payment network 404. In an embodiment, alternate server interface 406d may also be configured to have at least two ports. The first port may provide a communication link between alternate server interface 406d and payment network 404 (to which server 402b has no direct access) and the second port may be integrated or communicably coupled with server 402b. Alternate server interface 406d therefore serves as a secure communication intermediary that enables server 406b and payment network 404 to communicate with each other through alternate server interface 406d.
[0065] Payment network server 404 includes one or more servers configured to function as an intermediary network communicatively disposed between payor institution server platform 402 and payee institution server platform 406 — and is configured to enable communication and electronic payment transactions between the two entities.
[0066] Figure 5 is a flowchart illustrating a first method for responding to a transmission failure event detected during implementation of an electronic payment transaction within the system environment of Figure 4.
[0067] Step 502 includes receiving from server 402b within payor institution server platform 402, a payment instruction initiated by a payor. The payment instruction may be received at payment network server 404 and may identify a payor payment account, payee payment account and transaction amount. The payment instruction may be routed to payment network server 404 by server 402b through PNIP 402a.
[0068] At step 504, server 402b debits or places a hold on the transaction amount, at the payor payment account that is held at or maintained by payor institution server platform 402.
[0069] Step 506includes initiating transmission of a payment transaction instruction from payment network server 404 to a first communication end point of server 406b within payee institution sever

platform 406. In an embodiment, the first communication end point of server 406b is PNIP 406a — which first communication end point is configured to route the received payment transaction instruction to server 406b within payee institution server platform 406.
[0070] At step 508, responsive to detection of a transmission failure event in connection with transmission of the payment transaction instruction to server 406b, payment network server 404 (i) initiatestransmission of a first transaction failure communication to server 402b within payor institution server platform 402, and(ii) initiates transmission of a second transaction failure communication to server 406b within payee institution server platform 406.
[0071] The second transaction failure communication at step 508, is sent to a second communication end point of server 406b within payee institution server platform 406. The second communication end point of server 406b is a communication end point that is distinct from, and preferably isolated from,the first communication end point (PNIP 406a) of server 406b. In an embodiment of the method of Figure 5, the second communication end point of server 406b is alternate server interface 406d.
[0072] The first transaction failure communication at step 508that is transmitted to server 402b within payor institution server platform 402 may be routed through either (i) a first communication end point (PNIP 402a) of server 402b including PNIP 402a, or (ii) a second communication end point of server 402b that is distinct from, and preferably isolated from, the first communication end point 402a. In an embodiment, the second communication end point of server 402b is alternate server interface 402d.
[0073] The transmission failure event detected at step 508 mayinclude a detected transmission failure at any point within a communication channel established,or that is sought to be established, between payment network server 404 and server 406b within payee institution server platform 406. In an embodiment, the detected transmission failure event may include a detected transmission failure at any point within a communication channel established,or that is sought to be established, between payment network server 404 and the first communication end point (i.e. PNIP 406a) of server 406b within payee institution server platform 406. In another embodiment, the detected transmission failure event may include a detected transmission failure at any point within a

communication channel established,or that is sought to be established, between the first communication end point (i.e. PNIP 406a) of server 406b and server 406b itself.The communication channel(s) described above may include any of a circuit switched communication channel, a hardware communication channel, a packet switched communication channel or a logical communication channel between two entities.
[0074] Detection of the transmission failure event may be achieved in any number of ways that would be apparent to the skilled person, and which may be specific to actual configurations of system entities within system environment 400. In an embodiment of the invention, detection of the transmission failure event may include detection of any of (i) failure to establish a communication channel or a communication session between payment network server 404 and the first communication end point (PNIP 406a), (ii) failure to establish a communication channel or a communication session between the first communication end point (PNIP 406a) and server 406b within payee institution server platform 406, (iii) detection of a response timeout event for any data message related to the payment instruction sent by payment network server 404 over a communication channel or within a communication session established between payment network server 404 and the first communication end point (PNIP 406a), (iv) detection of a response timeout event corresponding to a data message related to the payment instruction sent by the first communication end point (PNIP 406a) to server 406b within payee institution server platform 406, over a communication channel or within communication session established between the first communication end point (PNIP 406a) and server 406b, or (v) detection of a response timeout event corresponding to a data message related to the payment instruction sent by payment network server 404 to server 406b within payee institution server platform 406 through the first communication end point (PNIP 406a), over a communication channel or within communication session established between payment network server 404, the first communication end point (PNIP 406a) and server 406b.
[0075] In an embodiment of the method of Figure 5, the first transaction failure communication transmitted at step 508 to server 402b within payor institution server platform 402includes a data communication or data message informing server 402b that a payment instruction initiated by a payor through payment network server 404 has failed, and providing server 402b with information regarding the payment instruction and / or regarding the failure event. In a particular embodiment,

said data communication or data message may be generated based on the exemplary data message format 1200 illustrated in Figure 12, including a plurality of standard data elements or data fields that are prescribed under the IS08583 messaging standard prescribed by the International Organization for Standardization. In a more particular embodiment, information regarding the failure event, including one or more of the type of failure event and the parameters of the failure event may be included within data element 48.19 (DE 48.19) within data message format 1200.
[0076] Likewise, in an embodiment of the method of Figure 5, the second transaction failure communication transmitted at step 508 to server 406b within payee institution server platform 406includes a data communication or data message informing server 406b that a payment instruction initiated by a payor through payment network server 404 has failed, and providing server 406b with information regarding the payment instruction and regarding the failure event. In a particular embodiment, said data communication or data message may be generated based on the exemplary data message format 1200 illustrated in Figure 12. In a more particular embodiment, information regarding the failure event, including one or more of the type of failure event and the parameters of the failure event may be included within data element 48.19 (DE 48.19) within the data message format 1200.
[0077] Step 510 includes initiating at server 402b within payor institution server platform 402, performance of a transaction failure response process. The transaction failure response process may be initiated in response to server 402b receiving the first transaction failure communication from payment network server 404.
[0078] Figure 6 is a communication flow diagram illustrating communication flow between system entities, for implementing the method of Figure 5.
[0079] Step 6002 includes receiving at a payor institution server platform 602 (for example, at a server within payor institution server platform 602), a payment instruction initiated by a payor. The payment instruction may be received at payor institution server platform 602 through one or more inputs provided by a payor through a user interface, and may identify a payor payment account, payee payment account and transaction amount.

[0080] Payor institution server platform 602 responds to receipt of the payment instruction by debiting or placing a transaction hold on funds equal to the transaction amount at a payor payment account. Thereafter, at step 6004, the payment instruction is transmitted by payor institution server platform 602 (for example, from a server within payor institution server platform 602) to payment network server 604.
[0081] At step 6006, payment network server 604 initiates transmission of a payment transaction instruction to a first communication end point 606 of a payee institution server (which is situated within a payee institution platform). In an embodiment, the first communication end point 606may include a payment network interface processor of the type illustrated as PNIP 406a in Figure 4. Said first communication end point 606 may be configured to route the received payment transaction instruction onward to the payee institution server that is situated within the payee institution server platform.
[0082] Payment network server 604 thereafter determines whether there is a transmission failure event.
[0083] The transmission failure event may include any detected transmission failure at any point within a communication channel established,or that is sought to be established, between payment network server 604 and a server within the payee institution server platform. In an embodiment, the detected transmission failure event may include a detected transmission failure at any point within a communication channel established,or that is sought to be established, between payment network server 604 and first communication end point 606. In another embodiment, the detected transmission failure event may include a detected transmission failure at any point within a communication channel established,or that is sought to be established, between first communication end point 606 and a server within the payee institution server platform. The communication channel(s) described above may include any of a circuit switched communication channel, a hardware communication channel, a packet switched communication channel or a logical communication channel between two entities.
[0084] Detection of the transmission failure event may be achieved in any number of ways that would be apparent to the skilled person, and which may be specific to actual configurations of the

system entities within Figure 6. In various embodiment of the invention, detection of the transmission failure event may include detection of any of (i) failure to establish a communication channel or a communication session between payment network server 604 and first communication end point 606, (ii) failure to establish a communication channel or a communication session between first communication end point 606 and a server within the payee institution server platform, (iii) detection of a response timeout event for any data message related to the payment instruction (that has been initiated by the payor) sent by payment network server 604 over a communication channel or within a communication session established between payment network server 604 and first communication end point 606, (iv) detection of a response timeout event corresponding to a data message related to the payment instruction (that has been initiated by the payor) sent by the first communication end point (PNIP 406a) to a server within the payee institution server platform, over a communication channel or within a communication session established between first communication end point 606 and said server, or (v) detection of a response timeout event corresponding to a data message related to the payment instruction (that has been initiated by the payor) sent by payment network server 604 to a server within the payee institution server platform through first communication end point 606, over a communication channel or within a communication session established between payment network server 604, first communication end point 606 and the server within the payee institution server platform.
[0085] At step 6008, responsive to detection of a transmission failure event, payment network server 604 (i) initiates transmission of a first transaction failure communication to payor institution server platform 602, and(ii) initiates transmission of a second transaction failure communication to a second communication end point 608 of the server within the payee institution server platform. Second communication end point 608 is a communication end point that is distinct from, and preferably isolated from, first communication end point 606. In an embodiment, second communication end point 606 may include alternate server interface 406d from Figure 4.
[0086] Responsive to receiving a first transaction failure communication, payor institution server platform 602 credits back or releases an implemented transaction hold on the transaction amount at the payor payment account, and at step 6012 transmits a transaction failure message or alert to the payor (for example to a payor terminal or to an electronic address associated with the payor).

[0087] Figure 7 is a flowchart illustrating a second method for responding to a transmission failure event detected during implementation of an electronic payment transaction within the system environment of Figure 4.
[0088] Step 702 includes receiving from a first communication end point of server 402b within payor institution server platform 402, a payment instruction initiated by a payor. In an embodiment, the first communication end point of server 402b is PNIP 402a.The first communication end point (PNIP 402a) is configured to route the received payment transaction instruction from server 402b within payor institution server platform 402 to payment network server 404. The payment instruction received at payment network server 404 may identify a payor payment account, payee payment account and transaction amount associated with the payment instruction.
[0089] At step 704, server 402b debits or places a hold on funds equal to the transaction amount, at the payor payment account that is held at or maintained by payor institution platform 402.
[0090] Step 706 includes initiating transmission of a payment transaction instruction from payment network server 404 to a first communication end point of server 406b within payee institution platform 406. In an embodiment, the first communication end point of server 406b is PNIP 406a — which PNIP 406 is configured to route the received payment transaction instruction to server 406b within payee institution server platform 406.
[0091] At step 708, responsive to detection of a transmission failure event in connection with transmission of the payment transaction instruction to server 406b within payee institution server platform 406, payment network server 404 (i) initiates transmission of a first transaction failure communication to server 402b within payor institution server platform 402, and(ii) initiates transmission of a second transaction failure communication to server 406b within payee institution server platform 406.
[0092] In the method of Figure 7, the first transaction failure communication at step 708that is transmitted back to server 402b within payor institution server platform 402is routed through a second communication end point of server 402b that is distinct from, and preferably isolated from,

first communication end point 402a. In an embodiment, the second communication end point of server 402b is alternate server interface 402d.
[0093] The second transaction failure communication at step 708, is sent to a second communication end point of server 406b within payee institution server platform 406. The second communication end point of server 406b is a communication end point that is distinct from, and preferably isolated from, the first communication end point (PNIP 406a). In an embodiment, the second communication end point of server 406b is alternate server interface 406d.
[0094] The transmission failure event detected at step 708 may include a detected transmission failure at any point within a communication channel established,or that is sought to be established, between payment network server 404 and server 406b within payee institution server platform 406. In an embodiment, the detected transmission failure event may include a detected transmission failure at any point within a communication channel established,or that is sought to be established, between payment network server 404 and the first communication end point (i.e. PNIP 406a) within payee institution server platform 406. In another embodiment, the detected transmission failure event may include a detected transmission failure at any point within a communication channel established,or that is sought to be established, between the first communication end point (i.e. PNIP 406a) and server 406b within payee institution server platform 406.The communication channel(s) described above may include any of a circuit switched communication channel, a hardware communication channel, a packet switched communication channel or a logical communication channel between two entities.
[0095] As in the case of the method of Figure 5, detection of the transmission failure event may be achieved in any number of ways that would be apparent to the skilled person, and which may be specific to actual configurations of system entities within system environment 400. In an embodiment of the invention, detection of the transmission failure event may include detection of any of (i) failure to establish a communication channel or a communication session between payment network server 404 and the first communication end point (PNIP 406a) of server 406b, (ii) failure to establish a communication channel or a communication session between the first communication end point (PNIP 406a) of server 406b and server 406b within payee institution server platform 406, (iii) detection of a response timeout event for any data message related to the

payment instruction (that has been initiated by the payor) sent by payment network server 404 over a communication channel or within communication session established between payment network server 404 and the first communication end point (PNIP 406a) of server 406b, (iv) detection of a response timeout event corresponding to a data message related to the payment instruction (that has been initiated by the payor) sent from the first communication end point (PNIP 406a) of server 406b, to server 406b within payee institution server platform 406, over a communication channel or within a communication session established between the first communication end point (PNIP 406a) of server 406b, and server 406b, or (v) detection of a response timeout event corresponding to a data message related to the payment instruction (that has been initiated by the payor) sent by payment network server 404 to server 406b within payee institution server platform 406 through the first communication end point (PNIP 406a) of server 406b, over a communication channel or within communication session established between payment network server 404, the first communication end point (PNIP 406a) of server 406b, and server 406b.
[0096] In an embodiment of the method of Figure 7, the first transaction failure communication transmitted to server 402b within payor institution server platform 402 at step 708 includes a data communication or data message informing server 402b that a payment instruction initiated by a payor through payment network server 404 has failed, and providing server 402b with information regarding the payment instruction and the failure event. In a particular embodiment, said data communication or data message may be generated based on the exemplary data message format 1200 illustrated in Figure 12. In a more particular embodiment, information regarding the failure event, including one or more of the type of failure event and the parameters of the failure event may be included within data element 48.19 (DE 48.19) within the data message format.
[0097] Similarly, the second transaction failure communication transmitted to server 406b within payee institution server platform 406 at step 708 includes a data communication or data message informing server 406b that a payment instruction initiated by a payor through payment network server 404 has failed, and providing server 406b with information regarding the payment instruction and the failure event. In a particular embodiment, said data communication or data message may be generated based on the exemplary data message format 1200 illustrated in Figure 12. In a more particular embodiment, information regarding the failure event, including one or more of the type of

failure event and the parameters of the failure event may be included within data element 48.19 (DE 48.19) within the data message format.
[0098] Step 710 includes initiating at server 402b within payor institution server platform 402, a transaction failure response process. The transaction failure response process may be initiated in response to server 402b within payor institution server platform 402 receiving the first transaction failure communication from payment network server 404.
[0099] Figure 8 is a communication flow diagram illustrating communication flow between system entities, for implementing the method of Figure 7.
[00100] Step 8002 includes receiving at a first communication end point 804 of a server
within a payor institution server platform, a payment instruction initiated by a payor. In an embodiment, first communication end point 804 is a PNIP interposed as a communication interface between the server within the payor institution server platform and payment network server 806. The payment instruction may be received at the first communication end point 804 based on one or more inputs provided by a payor through a user interface, and may identify a payor payment account, payee payment account and transaction amount.
[00101] At step 8004, the payment instruction is transmitted by first communication end point 804 to payment network server 806. Although not specifically shown in Figure 8, the onward transmission of the payment instruction by first communication end point 804 to payment network server 806 may be accompanied by, the server within the payor institution server platform debiting or placing a transaction hold on funds equal to the transaction amount at a payor payment account.
[00102] At step 8006, payment network server 806 initiates transmission of a payment
transaction instruction to a first communication end point 808 of a server situated within a payee institution platform. In an embodiment, the first communication end point 808 may include a payment network interface processor of the type illustrated as PNIP 406a in Figure 4. Said first communication end point 808 may be configured to route the received payment transaction instruction onward to the server that is situated within the payee institution server platform.

[00103] Payment network server 806 thereafter determines whether there is a transmission
failure event.
[00104] The transmission failure event may include any detected transmission failure at any
point within a communication channel established,or that is sought to be established, between payment network server 806 and a server within the payee institution server platform. In an embodiment, the detected transmission failure event may include a detected transmission failure at any point within a communication channel established,or that is sought to be established, between payment network server 806 and the first communication end point 808 of payee institution server. In another embodiment, the detected transmission failure event may include a detected transmission failure at any point within a communication channel established,or that is sought to be established, between the first communication end point 808 and the server within the payee institution server platform. The communication channel(s) described above may include any of a circuit switched communication channel, a hardware communication channel, a packet switched communication channel or a logical communication channel between two entities.
[00105] Detection of the transmission failure event may be achieved in any number of ways
that would be apparent to the skilled person, and which may be specific to actual configurations of the system entities within Figure 8. In an embodiment of the invention, detection of the transmission failure event may include detection of any of (i) failure to establish a communication channel or a communication session between payment network server 806 and the first communication end point 808, (ii) failure to establish a communication channel or a communication session between first communication end point 808 and the server within the payee institution server platform, (iii) detection of a response timeout event for any data message related to the payment instruction (that has been initiated by the payor) sent by payment network server 806 over a communication channel or within a communication session established between payment network server 806 and first communication end point 808, (iv) detection of a response timeout event corresponding to a data message related to the payment instruction (that has been initiated by the payor) sent by first communication end point808 to a server within the payee institution server platform, over a communication channel or within a communication session established between first communication end point 808 and said server, or (v) detection of a response timeout event

corresponding to a data message related to the payment instruction (that has been initiated by the payor) sent by payment network server 806 to a server within the payee institution server platform through first communication end point 808, over a communication channel or within a communication session established between payment network server 806, first communication end point 808 and the server within the payee institution server platform.
[00106] At step 8008, responsive to detection of a transmission failure event, payment
network server 806 initiates transmission of a first transaction failure communication to a second communication end point 802 of the server within the payor institution server platform. At step 8010, responsive to detection of a transmission failure event, payment network server 806 also initiates transmission of a second transaction failure communication to a second communication end point 810 of the server within the payee institution server platform.
[00107] Second communication end point 802 within the payor institution server platform is
a communication end point that is distinct from, and preferably isolated from, first communication end point 804within the payor institution server platform. Second communication end point 810 within the payee institution server platform is a communication end point that is distinct from, and preferably isolated from, first communication end point 808within the payor institution server platform. In an embodiment of the method of Figure 7, second communication end point 802 may include the alternate server interface 402d from Figure 4, and / or second communication end point 810 may include the alternate server interface 406d from Figure 4.
[00108] Responsive to receiving the first transaction failure communication, the server
withinthe payor institution server platform credits back or releases the transaction hold on the transaction amount at the payor payment account, and at step 8012 transmits a transaction failure message or alert to the payor (for example to a payor terminal or to an electronic address associated with the payor).
[00109] Figure 9 is a flowchart illustrating a method implemented by a payment institution
server (or payment institution server platform) in response to receiving a transaction failure communication. In an embodiment, the method of Figure 9 is implemented at step 510 of Figure 5, or at step 710 of Figure 7 for initiating a transaction failure response process at a server within a

payor institution server platform in response to detection of a transmission failure event by a payment network server. The method of Figure 9 may be implemented at a server within a payor institution server platform — for example, at server 402b within payor institution server platform 402.
[00110] Step 902 includes receiving a transaction failure notification or communication. In an embodiment, the transaction failure notification or communication may have been generated by a payment network server 404 and may have been transmitted to a server 402b within the payor institution server platform 402. In one embodiment, the transaction failure notification or communication may be routed to server 402b through alternate server interface 402d within payor institution server platform 402. In another embodiment, the transaction failure notification or communication may be routed to server 402b through PNIP 402a within payor institution server platform 402.
[00111] At step 904, server 402b within payor institution server platform 402 notifies or alerts the payor regarding the transaction failure. Notifying the payor, may in an embodiment,include transmitting a transaction failure message or alert to the payor (for example to a payor terminal or to an electronic address associated with the payor).
[00112] At step 906, server 402b within payor institution server platform 906 (i) releases a previously implemented hold on the transaction amount corresponding to the failed payment transaction at the payor payment account or (ii) credits a previously debited transaction amount corresponding to the failed payment transaction back to the payor payment account.
[00113] Figure 10A is a flowchart illustrating a first method for responding to detection of a transmission failure event in connection with an electronic payment transaction. In an embodiment, the method of Figure 10A is implemented at step 508 of Figure 5, or at step 708 of Figure 7 for responding to detection of a transmission failure event by a payment network server. The method of Figure 10A may be implemented at a payment network server— for example, at payment network server 404.

[00114] At step 1002A, responsive to determining that a detected transmission failure event includes non-functioning or improper functioning of a first communication end point corresponding to a server 406b within a payee server institution platform 406 (e.g. non-functioning or improper functioning of PNIP 406a) and that a payment transaction instruction is undelivered to the server 406b, payment network server 404 (i) initiates transmission of a first transaction failure status message to server 402b within payor institution server platform 402 — wherein the first transaction failure status message notifies server 402b that the payment transaction instruction is undelivered to the payee institution server platform 406 and / or a server 406b within the payee institution server platform 406, and (ii) initiates transmission of a second transaction failure status message to a second communication end point 406d of server 406b within payee institution server platform 406 — wherein the second transaction failure status message notifies server 406b that a payment transaction instruction is undelivered to the payee institution server platform 406 and / or to server 406b. In an embodiment of method step 1002A, the first transaction failure status message is transmitted by payment network server 404 to a second communication end point 402d of server 402b within the payor institution server platform 402.
[00115] Figure 10B is a flowchart illustrating a second method for responding to detection of a transmission failure event in connection with an electronic payment transaction.In an embodiment, the method of Figure 10B is implemented at step 508 of Figure 5, or at step 708 of Figure 7 for responding to detection of a transmission failure event by a payment network server. The method of Figure 10A may be implemented at a payment network server — for example, at payment network server 404.
[00116] At step 1002B, responsive to determining that a payment transaction instruction initiated by payment network server 404 has been delivered to a server 406b within a payee institution server platform 406, and where the detected transmission failure event includes a response timeout event associated with the delivered payment transaction instruction (i.e. wherein server 406b's response or acknowledgement corresponding to the delivered payment transaction instruction is not received at payment network server 404 within a predefined timeout window), payment network server 404 (i) initiates transmission of a first transaction failure status message to server 402b within payor institution server platform 402 — wherein the first transaction failure status message notifies server 402b that the payment transaction instruction is delivered to the payee institution server platform

406 and / or a server 406b within the payee institution server platform 406 and that a response timeout has been detected in connection with the delivered payment transaction instruction, (ii) initiates transmission of a second transaction failure status message to a second communication end point 406d of server 406b within payee institution server platform 406 — wherein the second transaction failure status message notifies server 406b that a payment transaction instruction is delivered to the payee institution server platform 406 and / or to server 406b and that a response timeout has been detected in connection with the delivered payment transaction instruction, and (iii) initiates transmission of a third payment transaction cancellation message to the second communication end point 406d of server 406b within payee institution server platform 406 — wherein the third payment transaction cancellation message notifies server 406b that the payment transaction corresponding to the payment transaction instruction that was previously delivered from payment network server 404 to server 406b has been cancelled.
[00117] By transmitting the third payment transaction cancellation message, payment network server 404 ensures that server 406b and / or payee institution server platform 406 does not in any way act upon the previously delivered payment transaction instruction — and as a result, the transaction funds that have been debited from or placed under a transaction hold at the payor payment account can be credited back or released from the transaction hold in real time.
[00118] In an embodiment of method step 1002B, the first transaction failure status message is transmitted by payment network server 404 to a second communication end point 402d of server 402b within the payor institution server platform 402.
[00119] Figure 11 illustrates an embodiment of a payment network server 1100 configured to implement the teachings of the present invention.lt would be understood that payment network server 1100 may include an embodiment of payment network server 404 of Figure 4.
[00120] Payment network server 1100 may include (i) an operator interface 1102 configured to enable an operator to configure or control payment network server 1100, (ii) a processor 1104 configured for data processing operations within payment network server 1100, (iii) a transceiver 1106 configured for enabling network communication to and from payment network server 1100,

and (iv) a memory 1108, which memory 1108may include transitory memory and / or non-transitory memory.
[00121] In an embodiment, memory 1108 may have stored therewithin, (i) an operating system 1110 configured for managing device hardware and software resources and that provides common services for software programs implemented within payment network server 1100, (ii) a payor institution server interface 1112 which is configured to interface with one or more communication end points corresponding to server 402b within payor institution server platform 402 (for example with PNIP 402a and / or with alternate server interface 402d), (iii) a payee institution server interface 1114 which is configured to interface with one or more communication end points corresponding to server 406b within payee institution server platform 406 (for example with PNIP 406a and / or with alternate server interface 406d), (iv) a transaction monitor 1116 configured to detect transmission failure events corresponding to payment transaction instructions transmitted by payment network server 1100 to payee institution server platform 406, (v) a payor institution routing switch 1118 configured to selectively route communications or messages directed to a server 402b within a payor institution server platform 402 through either a first communication end point (for example PNIP 402a) or a second communication end point (for example alternate server interface 402d), (vi) a payee institution routing switch 1120 configured to selectively route communications or messages directed to a server 406b within a payee institution server platform 406 through either a first communication end point (for example PNIP 406a) or a second communication end point (for example alternate server interface 406d), and (vii) a failure event response controller 1122 which is configured to select and initiate an appropriate response to a detected transmission failure event (for example in accordance with any of method steps 508, 708, 1002A or 1002B of Figures 5, 7, 10A and 10B respectively).
[00122] Figure 13 illustrates an exemplary computer system of a type that may be used to
implement the teachings of the present invention.
[00123] Computer system 1302 includes one or more processors 1304 and at least one memory 1306. Processor 1304 is configured to execute program instructions.Processor 1304 may be a real processor or a virtual processor. It will be understood that computer system 1302 does not suggest any limitation as to scope of use or functionality of described embodiments. The computer system

1302 may include, but is not be limited to, one or more of a general-purpose computer, a programmed microprocessor, a micro-controller, an integrated circuit, and other devices or arrangements of devices that are capable of implementing the steps that constitute the method of the present invention. Exemplary embodiments of a computer system 1302 in accordance with the present invention may include one or more servers, desktops, laptops, tablets, smart phones, mobile phones, mobile communication devices, tablets, phablets and personal digital assistants. In an embodiment of the present invention, the memory 1306 may store software for implementing various embodiments of the present invention. The computer system 1302 may have additional components. For example, the computer system 1302 may include one or more communication channels 1308, one or more input devices 1310, one or more output devices 1312, and storage 1314. An interconnection mechanism (not shown) such as a bus, controller, or network, interconnects the components of the computer system 1302. In various embodiments of the present invention, operating system software (not shown) provides an operating environment for various softwares executing in the computer system 1302 using a processor 1304, and manages different functionalities of the components of the computer system 1302.
[00124] The communication channel(s) 1308 allow communication over a communication
medium to various other computing entities. The communication medium provides information such as program instructions, or other data in a communication media. The communication media includes, but is not limited to, wired or wireless methodologies implemented with an electrical, optical, RF, infrared, acoustic, microwave, Bluetooth or other transmission media.
[00125] The input device(s) 1310 may include, but is not limited to, a touch screen, a
keyboard, mouse, pen, joystick, trackball, a voice device, a scanning device, or any another device that is capable of providing input to the computer system 1302. In an embodiment of the present invention, the input device(s) 1310 may be a sound card or similar device that accepts audio input in analog or digital form. The output device(s) 1312 may include, but not be limited to, a user interface on CRT, LCD, LED display, or any other display associated with any of servers, desktops, laptops, tablets, smart phones, mobile phones, mobile communication devices, tablets, phablets and personal digital assistants, printer, speaker, CD/DVD writer, or any other device that provides output from the computer system 1302.

[00126] The storage 1314 may include, but not be limited to, magnetic disks, magnetic tapes,
CD-ROMs, CD-RWs, DVDs, any types of computer memory, magnetic stripes, smart cards, printed barcodes or any other transitory or non-transitory medium which can be used to store information and can be accessed by the computer system 1302. In various embodiments of the present invention, the storage 1314 may contain program instructions for implementing any of the described embodiments.
[00127] In an embodiment of the present invention, the computer system 1302 is part of a
distributed network or a part of a set of available cloud resources.
[00128] The present invention may be implemented in numerous ways including as a system,
a method, or a computer program product such as a computer readable storage medium or a computer network wherein programming instructions are communicated from a remote location.
[00129] The present invention may suitably be embodied as a computer program product for
use with the computer system 1302. The method described herein is typically implemented as a computer program product, including a set of program instructions that is executed by the computer system 1302 or any other similar device. The set of program instructions may be a series of computer readable codes stored on a tangible medium, such as a computer readable storage medium (storage 1314), for example, diskette, CD-ROM, ROM, flash drives or hard disk, or transmittable to the computer system 1302, via a modem or other interface device, over either a tangible medium, including but not limited to optical or analogue communications channel(s) 1308. The implementation of the invention as a computer program product may be in an intangible form using wireless techniques, including but not limited to microwave, infrared, Bluetooth or other transmission techniques. These instructions can be preloaded into a system or recorded on a storage medium such as a CD-ROM, or made available for downloading over a network such as the Internet or a mobile telephone network. The series of computer readable instructions may embody all or part of the functionality previously described herein.
[00130] It would be understood that the above described methods and systems enable a
payment network server to respond to a detected payment instruction transmission failure, by ensuring that funds that have been debited or subjected to a transaction hold at a payor payment

account are not credited to a payee payment account, and by providing confirmation of this information to a payor institution server platform or to a server within such payor institution server platform. As a result, the debited or held funds can be credited back or released into the payor payment account immediately, thereby eliminating the 10 to 48 waiting period that was previously required for effecting the credit or release.
[00131] While the exemplary embodiments of the present invention are described and illustrated herein, it will be appreciated that they are merely illustrative. It will be understood by those skilled in the art that various modifications in form and detail may be made therein without departing from or offending the spirit and scope of the invention as defined by the appended claims. Additionally, the invention illustratively disclose herein suitably may be practiced in the absence of any element which is not specifically disclosed herein — and in a particular embodiment that is specifically contemplated, the invention is intended to be practiced in the absence of any one or more element which are not specifically disclosed herein.

We Claim:

1.A method for responding to a transmission failure event corresponding to an electronic
payment transaction, comprising the steps of:
receiving a payment instruction initiated by a payor for transferring a transaction amount from a payor payment account to a payee payment account;
initiating at a payment network server, transmission of a transaction instruction to a first communication end point of a payee institution server;
responsive to detection of a transmission failure event in connection with transmission of the payment transaction instruction to the payee institution server:
initiating transmission of a first transaction failure message to a payor institution server; and
initiating transmission of a second transaction failure message to a second communication end point of the payee institution server;
wherein the payor institution server is configured to respond to receiving the first transaction failure message by reversing a previous debit or transaction hold corresponding to the transaction amount that has been applied by the payor institution server at the payor payment account.
2. The method as claimed in claim 1, wherein the first communication end point of the payee institution server and the second communication end point of the payee institution server are distinct.
3. The method as claimed in claim 1 wherein transmission of the first transaction failure message and transmission of the second transaction failure message are both initiated at the payment network server.

4. The method as claimed in claim 1, wherein:
the payment instruction initiated by the payor is transmitted to thepayment network server from a first communication end point of the payor institution server; and
the first transaction failure message is transmitted to a second communication end point of the payor institution server, wherein the second communication end point of the payor institution server is distinct from the first communication end point of the payor institution server.
5. The method as claimed in claim 1, wherein:
the first communication end point of the payee institution server is a payment network interface processor; and
the second communication end point of the payee institution server is an alternate server interface.
6. The method as claimed in claim 4, wherein:
the first communication end point of the payor institution server is a payment network interface processor; and
the second communication end point of the payor institution server is an alternate server interface.
7. The method as claimed in claim 1, wherein the transmission failure event comprises:
a detected failure in establishing a communication channel between any of:
(i) the payment network server and the payee institution server;
(ii) thepayment network server and the first communication end point of the payee
institution server; or (iii) a first communication end point of the payee institution server and the payee
institution server;

or
a detected response timeout event corresponding to any data message related to the transaction instruction transmitted to the first communication end point of the payee institution server over a communication channel established between any of:
(iv) the payment network server and the payee institution server;
(v) thepayment network server and the first communication end point of the payee
institution server; or (vi) a first communication end point of the payee institution server and the payee
institution server.
8. A system configured for responding to a transmission failure event corresponding to an
electronic payment transaction, comprising a payment network server configured for:
receiving a payment instruction initiated by a payor for transferring a transaction amount from a payor payment account to a payee payment account;
initiating transmission of a transaction instruction to a first communication end point of a payee institution server;
responsive to detection of a transmission failure event in connection with transmission of the payment transaction instruction to the payee institution server:
initiating transmission of a first transaction failure message to a payor institution server; and
initiating transmission of a second transaction failure message to a second communication end point of the payee institution server;

wherein the payor institution server is configured to respond to receiving the first transaction failure message by reversing a previous debit or transaction hold corresponding to the transaction amount that has been applied by the payor institution server at the payor payment account.
9. The system as claimed in claim 8, wherein the first communication end point of the payee institution server and the second communication end point of the payee institution server are distinct.
10. The system as claimed in claim 8 wherein transmission of the first transaction failure message and transmission of the second transaction failure message are both initiated at the payment network server.
11. The system as claimed in claim 8, wherein:
the payment instruction initiated by the payor is transmitted to the payment network server from a first communication end point of the payor institution server; and
the first transaction failure message is transmitted to a second communication end point of the payor institution server, wherein the second communication end point of the payor institution server is distinct from the first communication end point of the payor institution server.
12. The system as claimed in claim 8, wherein:
the first communication end point of the payee institution server is a payment network interface processor; and
the second communication end point of the payee institution server is an alternate server interface.
13. The system as claimed in claim 11, wherein:
the first communication end point of the payor institution server is a payment network interface processor; and

the second communication end point of the payor institution server is an alternate server interface.
14. The system as claimed in claim 8, wherein the transmission failure event comprises:
a detected failure in establishing a communication channel between any of:
(i) the payment network server and the payee institution server;
(ii) thepayment network server and the first communication end point of the payee
institution server; or (iii) a first communication end point of the payee institution server and the payee
institution server; or
a detected response timeout event corresponding to any data message related to the transaction instruction transmitted to the first communication end point of the payee institution server over a communication channel established between any of:
(iv) the payment network server and the payee institution server;
(v) thepayment network server and the first communication end point of the payee
institution server; or (vi) a first communication end point of the payee institution server and the payee
institution server.
15. A computer program product for responding to a transmission failure event corresponding
to an electronic payment transactioncomprising a non-transitory computer readable medium having
a computer readable program code embodiment therein, the computer readable program code
comprising instructions for:
receiving a payment instruction initiated by a payor for transferring a transaction amount from a payor payment account to a payee payment account;

initiating at a payment network server, transmission of a transaction instruction to a first communication end point of a payee institution server;
responsive to detection of a transmission failure event in connection with transmission of the payment transaction instruction to the payee institution server:
initiating transmission of a first transaction failure message to a payor institution server; and
initiating transmission of a second transaction failure message to a second communication end point of the payee institution server;
wherein the payor institution server is configured to respond to receiving the first transaction failure message by reversing a previous debit or transaction hold corresponding to the transaction amount that has been applied by the payor institution server at the payor payment account.