AU2021221623A1

AU2021221623A1 - Digital technology associated with the facilitation of real time deposits and withdrawals across multibank networks

Info

Publication number: AU2021221623A1
Application number: AU2021221623A
Authority: AU
Inventors: Achim Boers; Andrew Moss; Fernando Rojo; Matt Sykes; Glenn Walburn
Original assignee: Prosegur SPV 1 Pty Ltd
Current assignee: Prosegur SPV 1 Pty Ltd
Priority date: 2021-07-06
Filing date: 2021-08-25
Publication date: 2023-02-02

Abstract

A system for performing a transaction, the system being configured to: receive a transaction request from a Smart Automatic Teller Machine (ATM), the transaction request including customer identification data associated with a user; process the transaction request; send the transaction request to a financial institution through a New Payments Platform (NPP) system; receive confirmation of the transaction request from the financial institution associated with the customer identification data; and process the transaction request in real-time. [Figure 1] Receive transaction request with customer ID 100 Process request 110 Send request to financial institution via a New Payments Platform system 120 Receive confirmation of the request from the financial institution, 130 associated with the customer ID Process transaction request in real time 140 FIG1

Description

Receive transaction request with customer ID 100

Process request 110

Send request to financial institution via a New Payments Platform system 120

Receive confirmation of the request from the financial institution, 130 associated with the customer ID

Process transaction request in real time 140

FIG1

Digital technology associated with the facilitation of real time deposits and withdrawals across multibank networks

Technical Field

The present invention relates to a system/method of performing transactions. In particular as an example the present invention relates to a system and method for processing and/or performing multi-banking transactions or the like.

Background of the Invention

The following references to and descriptions of prior proposals or products are not intended to be and are not to be construed as, statements or admissions of common general knowledge in the art. In particular, the following prior art discussion does not relate to what is commonly or well known by the person skilled in the art, but assists in the understanding of the inventive step of the present invention of which the identification of pertinent prior art proposals is but one part.

Currently, when using an ATM to either withdraw cash, request a balance on an account, or to deposit cash, customers often seek an ATM associated with their particular bank to perform the transaction. Often this can be inconvenient, expensive and time consuming, especially if an ATM is not available at the user's location.

Thus, there is required a system and process which can allow customers to transact at any ATM or a general ATM, and have the transaction occur in real time.

The present invention seeks to provide a system/method for performing transactions which may ameliorate the foregoing shortcomings and disadvantages or which will at least provide a useful alternative.

Summary of the Invention

According to one aspect of the invention, there is provided herein a system for performing a transaction, the system being configured to: receive a transaction request from a Smart Automatic Teller Machine (ATM), the transaction request including customer identification data associated with a user; process the transaction request; send the transaction request to a financial institution through a New Payments Platform (NPP) system; receive confirmation of the transaction request from the financial institution associated with the customer identification data; and process the transaction request in real-time.

According to one example, the transaction includes a cardless cash withdrawal, the system configured to: send the transaction request from the ATM to an NPP processing application; receive, from the processing application a unique PaylD, registered with NPP; send the unique PaylD to the ATM; receive confirmation that the customer transferred the funds using the PaylD; and, dispense the funds on the ATM.

In another example, the system is configured to: receive payment notification from the financial institution, the payment notification being associated with the unique pay identifier; and, generate the cardless cash withdrawal via the ATM.

According to another example, the transaction includes a cash deposit, the system being configured to: send the transaction request, including customer identification information from the ATM to an NPP processing application; NPP processing application transfer the funds to the customer's account; receive confirmation of the cash deposit from the NPP processing application; and, send confirmation of the cash deposit to the ATM.

According to another aspect, there is provided herein a method of performing a transaction, the method including the steps of, in a system: receiving a transaction request from a Smart Automatic Teller Machine (ATM), the transaction request including customer identification data associated with a user; processing the transaction request; sending/transmitting the transaction request to a financial institution through a New Payments Platform (NPP) system; receiving confirmation of the transaction request from the financial institution associated with the customer identification data; and processing the transaction request in real-time.

According to a further aspect, there is provided herein a system for performing a transaction, the system configured to activate a primary user, the system configured to perform the steps of: (a) receive customer identification information associated with the primary user; (b) receive customer bank/financial details associated with the customer identification information; (c) generate a micro-payment; (d) receive confirmation of payment; and (e) complete authentication of the primary user.

According to one example, the system further verifies the customer identification information prior to generating the micro-payment.

In yet another example, the system receives an indication of a secondary user.

According to a further example, the system associates the secondary user with the primary user or a primary user account.

In yet another example, when either one or a combination of the primary or the secondary user make a deposit request at an ATM, the system generates a unique code associated with the primary user account for providing to the ATM.

According to another aspect, there is provided herein an Automatic Teller Machine (ATM), the ATM being configured to form part of and/or interact with the system as described herein.

According to yet another aspect, there is provided herein an Automatic Teller Machine (ATM), for performing a transaction, the ATM being configured to: (a) receive a deposit request; (b) receive an indication of a unique code associated with a user; and, (c) perform/generate the transaction accordingly.

According to a further aspect, there is provided herein a method for performing a transaction, the method including the steps of, in a system configured to activate a primary user, steps of: (a) receiving customer identification information associated with the primary user; (b) receiving customer bank/financial details associated with the customer identification information; (c) generating a micro-payment; (d) receiving confirmation of payment; and (e) completing authentication of the primary user.

In yet a further aspect, there is provided herein a method for performing a transaction, the method being configured to perform the steps of, in any of the systems as described herein.

It will be appreciated that any combination of the features, aspects, elements, examples and embodiments described herein is possible.

Brief Description of the Drawings

The invention may be better understood from the following non-limiting description of a preferred embodiment, in which:

Figure 1 is a flowchart of an example process/method of performing a transaction;

Figure 2 is a flowchart of another example process/method of performing a transaction;

Figure 3 is a flowchart of another example of a process/method of performing a transaction;

Figure 4 is a diagram of an example system which can implement the process/method as described herein;

Figure 5 is a diagram of an example process of performing a transaction as described herein;

Figure 6 is a diagram of an example process of performing a transaction as described herein; and,

Figure 7 is a diagram of an example process of performing a transaction as described herein;

Figure 8 is a diagram of a further example process/method of performing a transaction;

Figure 9 is a diagram of a particular example of the process/method of Figure 8;

Figure 10 is a diagram of a particular example of the process/method of Figure 8; and,

Figure 11 is a diagram of a further example process/method of performing a transaction as described herein.

Detailed Description of the Drawings

An example of a system/method for performing a transaction is shown in Figures 1 to 7.

In particular, Figure 1 shows an example of a method/system for performing a transaction where the system is configured to receive a transaction request from a Smart Automatic Teller Machine (ATM), the transaction request including customer identification data or information which is typically associated with a user at step 100, process the transaction request at step 110, send the transaction request to a financial institution through a New Payments Platform (NPP) system at step 120, receive confirmation of the transaction request from the financial institution associated with the customer identification data at step 130; and process the transaction request in real-time at step 140.

Thus, for example, the method/system of the present invention can include a base or primary system (shown for example at 404in Figure 4). The base system can include one or more processing systems or computer systems either in a discrete or networked environment, with access to one or more data stores, such that the base system can effectively coordinate and communicate with all other applications and systems described herein.

Accordingly, in the example of Figure 1, the base system can receive a transaction request from a smart ATM, such as cardless cash withdrawal or cash deposit. The transaction request often includes customer identification data which is typically unique to a particular customer. The customer ID can be provided/sent to the base system via the smart ATM either through a bankcard, or through a separate customer ID and unique PaylD verification process or application (for example this can include an email address, a phone number, a business number, or a business/organisation name that has been registered by a user to be linked to their bank account). The base system can then send the transaction request to customer's financial institution by connecting through the NPP and thus process the transaction in real-time.

Notably, the New Payments Platform (NPP) is an example of a payments platform that includes a distributed switch of payment gateways that can route and exchange financial messages between each other so that financial payments can be made expeditiously. The platform is an example of a standardised messaging platform agreed to by a network of financial institutions. It will be appreciated that any agreed messaging standard can be used.

Figure 2 shows an example of a transaction which includes a cardless cash withdrawal, where at step 200 the system receives a transaction request from the ATM, where the transaction request includes cardless cash withdrawal and customer identification data. At step 210, the system/process includes sending the transaction request from the ATM to an NPP processing application, at step 220 receive, from the processing application a unique ID, such as for example, a unique PaylD, registered with NPP, at step 230 send the unique PaylD to the ATM, where confirmation that the customer transferred the funds using the PaylD is received such as a notification from the financial institution/processing application at step 240 and funds are dispensed, typically through the generation of cardless cash withdrawal via the ATM at step 250.

Figure 3 shows a further example, wherein the transaction includes a cash deposit, the system being configured to at step 300 send the transaction request, including customer identification information from the ATM to an NPP processing application, at step 310 send transaction request to a NPP processing application, at step 320 NPP processing application transfer the funds to the customer's account, at step 330 receive confirmation of the cash deposit from the NPP processing application and, at step 340 send confirmation of the cash deposit to the ATM.

It will be appreciated that the systems and methods described herein can allow for smart ATM multi-bank transactions to occur in real-time, thus allowing users to use any ATM, and particularly those not affiliated with their particular financial institution/bank to process transactions such as cardless cash withdrawals and cash deposits.

Further more specific examples of the system/method described herein is provided below.

Example: Smart ATM - Multibank

Figure 4 shows an example of a high-level architecture of how the system and method described herein can provide a multi-bank transaction. In this particular example, at 401, a smart Automatic Teller Machine (Smart ATM), which is typically an ATM that not only allows users to withdraw cash but also allows users to make deposits of cash) is able to receive identification information from a bank customer 402. Typically, the customer 402 has identification information in the form of a bank card (as shown at 403), or other identification indicators, which allow the user to be uniquely identified. The

ATM at 401 communicates with the customer to receive identification information and will send the transaction (PCI or Non-PCI route) through to the system presently described herein at 404 and choose the transaction they wish to complete. As an example, the transactions can include a balance enquiry or a cash withdrawal (where PCI authorization is required), and a note deposit or a cardless cash withdrawal.

As an example, the system at 405 can then communicate through a new payments platform's service provider API (in this example, such as, Azupay) at 406, with the customer's bank at 407, to ensure that the transaction is conducted in real-time.

At 408, if there is withdrawal or balance enquiry request, the system at 404 works with a PCI transactions Switch, such as, EFTEX at 408 and various card schemes at 409 and the customer's bank at 410 in order to process the request accordingly.

Example: Cash Deposit

Figure 5 shows an example of a cash deposit process which can be implemented by the system/process described herein.

In this particular example, a customer at 501 is identified through an identification means or indicator, such as by inserting their bankcard (like a debit or credit card) into the ATM to commence the transaction. At step 502, the customer typically deposits cash in the ATM and the ATM generates a transaction request to send it to the system of the present invention at 504 via a TNS Transaction Network Service router and TNS communications infrastructure or the like (shown at 503). The system at 504, typically acquires the cash deposited and transfers the funds to the customer's bank 506, via the NPP and through an NPP service provider such as Azupay at 505. Thus, according to one example, the system can allow for funds to be deposited into the customer/user's account in real-time.

Example: Cash deposit and carded withdrawal and Infrastructure flow

Figure 6 shows an example of a cash deposit and card withdrawal where at step 601 the TNS can communicate the ATM transaction that has occurred to the System as presently described. At 602, the transaction is received by the System, such as through the system firewall and passed onto the specific API (Application Programming Interface) gateway and a request is sent to the System via a gateway at 603, where the System sends a confirmation to the DMZ once the request has been received. At 603, the System will then typically send, via a System API Gateway to an application which can generate a Payin or PayOut order at step 604. In this particular example, the software application is Marketpay, but it will be appreciated that any other software application that can generate the order via a secure VPN connection and can handle smart payments and generate payment orders can be used. At step 605, the order can then be processed via Azupay API when the transaction is requested from Azupay at 606 and confirmation of that transaction as processed by Azupay is received.

Example: Cardless Cash Withdrawal

Figure 7. shows an example of a Cardless cash withdrawal implemented by the currently system/method as described herein.

In this example, at 701, the customer typically selects a cardless withdrawal option at the ATM at 702, such as through Azupay. At step 2, the ATM at 702 sends a request to the system at 703 requesting to initiate an Azupay withdrawal. At step 3, the system calls the Azupay API and requests the generation of a unique PaylD. At 704, Azupay creates the Payld and at step 4, registers the PaylD with the New Payments Platform at 705. The NPP will then typically return the unique PaylD to the ATM via the system at 703 by confirming with the customer's bank at 706. The ATM can then display the unique PaylD details in the form of a QR code.

At step 5, the customer then uses a smart device such as a mobile phone 707, re the like to then scan the QR code displayed on the ATM at step 6 and copies the PaylD to their phone. At step 7, the customer will then typically complete the PaylD payment via their online banking application via their smart device. At step 8, the Customer's bank transfers funds via the NPP to the Base System with Azupay and at step 9, the funds are received in the Base System account. At step 10, typically Azupay validates the payment and notifies the Base System infrastructure via the appropriate API. At step 11, the Base system can then instruct the ATM to dispense the cash and at step 12, the customer will receive the cash from the ATM (that is, the ATM will dispense the cash accordingly).

Example: Customer Verification/Registration or Account Creation

According to one particular example, the system can be configured to activate a primary user or a primary user's account. This for example is shown in Figure 8A.

In Figure 8A, at step 800, the user can download onto a user's device such as a smart mobile telecommunication device, or any type of processing system used by the user, a software application which allows the user to perform the steps of registration. This example application is referred to herein as a System Identification Application (SIA). This is an optional step as the process can also be performed without downloading the application.

At step 805, the system can receive customer identification (ID) information associated with the primary user. This can include the user's name, address details, and also other identification details such as a driver's licence or the like. At step 810, the system can verify the customer ID information provided by the user. This can include checking or verifying the details with a third party provider (such as a provider that verifies the drivers licence number, for example).

At step 815, the system can receive customer bank/financial details associated with the customer identification information. Thus, for example, the primary user can provide their bank account details which they wish to have associated with their account. They can provide one or more accounts.

At step 820, the system generates a micro-payment to the nominated bank account provided by the user. The micro-payment is typically a nominal amount transferred to the associated bank account to confirm the existence of the bank account and to check the account details. Thus, at step 825 the system can receive confirmation of the payment to the user's bank or .financial institution. This is typically achieved through receiving confirmation that the payment has been received by the nominated account.

At step 830, the system can activate the primary user account and/or complete authentication of the primary user, which typically includes completing the association of the bank accounts with a verified primary user.

In this example, the SIA can work with a primary user or can have one or more secondary users also associated with the primary user's account. In this particular example, the one or more secondary users can thus be authorised to make deposits into the primary user's account or on behalf of the primary user. Thus, for example, at step 835, the system can receive an indication of a secondary user by receiving secondary user information to be associated with the primary user or the primary user account. Thus, the system can associate the secondary user with the primary user or a primary user account, and at step 840, the secondary user can be registered against the primary user's account.

Accordingly, either one or a combination of the primary or the secondary user can make a deposit request at an ATM, where the system can generate a unique code associated with the primary user account for providing to the ATM.

This is shown more particularly in Figure 8B, where at step 845 the primary or secondary user can download/open/activate the SIA. At 850, the system can receive an indication that the user would like to make a deposit (i.e. a deposit request). Thus at step 855, the system can generate a unique code for use at Smart ATM associated with transaction request and primary user account. An example of a unique code that can be generated is a QR code or the like. Thus, once the QR code is generated, the processes of Figures 1 and 3 can be performed but with the QR code as the mode of identification of the financial account where the transaction is to occur.

Further examples are provided in Figures 9 to 11.

Figure 9 shows an example of a customer on-boarding system, where as an example, at step 901, the customer, who is typically the account owner decides that they would like to make a deposit on a Smart ATM. At step 902, the customer downloads the SIA or System Identification Application on their mobile telecommunication device or smart phone and begins the registration process. At step 903, the Customer's ID is verified by the SIA by typically communicating with a third party provider. At step 904, after successful verification, the customer can add their bank account details by, for example, entering the PaylD or BSB/Account number, or any other bank account identifier. Typically, at step 905, the system can then verify the bank account details using a system such as Azupay (or any other system). At step 906, the customer can identify themselves at a Smart ATM with the SIA. In this example, the ATM typically scans a unique code such as a QR Code or the like and identifies the user/customer and the related account.

Figure 10 shows an example of user management through the SIA for cash deposits, as an example. In this particular example, at step 1001, the owner of the account set up through the steps of Figure 9, for example would like to add another user (i.e. a secondary user) so that this user can make deposits on the owner's (i.e. primary user's) behalf. At step 1002, from the SIA, the owner inputs the details of the new user and at step 1003, the new user typically receives an activation code either through electronic mail (email),

SMS (short messaging service), or the like, which includes an activation link such that at step 1004 the secondary or new user can download the SIA and activate the account on their smart telecommunication device (or any other processing system) or the like. At step 1005, the secondary user can now identity himself/herself at a Smart ATM with the SIA and make deposits on behalf of the owner of the account accordingly, typically by receiving and scanning a Unique Code such as a QR code or the like. At step 1006, the ATM can scan the QR code on the SIA and can thus identify the primary user and the account related to the primary user.

Figure 11 shows an example of a cash deposit by using the SIA as described herein. At step 1101, the bank customer (either primary or secondary user) can use a bank card or the SIA as an identification method at the smart ATM, where the ATM scans the QR code generated by the SIA and identifies the user and the related/associated bank account. At step 1102, the customer typically deposits cash into the ATM and the device generates a transaction request to send to the System via TNS communication infrastructure at step 1103. At 1104, the Base/Primary System typically then acquires the cash deposited and transfers the funds to the customer's bank via the NPP and at step 1105, the transaction is typically processed using either the PaylD or the BSB/Account number of the customer, by communicating with the customer's bank/financial institution 1106, where the funds are deposited into the customer's account in real-time.

It will be appreciated that systems/applications described herein such as Azupay and Marketpay are provided as examples only and can include any application/system with the required functionality.

As an example, Azupay is payments platform which generates a QR code for initiating a payment and includes the PaylD and the transaction payload. Marketpay is an application which can provide connectivity between the base system and Azupay, as an example.

It will further be appreciated that any combination of processes, methods, system features or elements as described herein is possible. The term "comprise" and variants of that term such as "comprises" or "comprising" are used herein to denote the inclusion of a stated integer or integers but not to exclude any other integer or integers, unless in the context or usage an exclusive interpretation of the term is required.

Those skilled in the art will appreciate that the invention described herein is susceptible to variations and modifications other than those specifically described. All such variations and modifications are to be considered within the scope and spirit of the present invention the nature of which is to be determined from the foregoing description.

Claims

1. A system for performing a transaction, the system being configured to:

receive a transaction request from a Smart Automatic Teller Machine (ATM), the transaction request including customer identification data associated with a user;

process the transaction request;

send the transaction request to a financial institution through a New Payments Platform (NPP) system;

receive confirmation of the transaction request from the financial institution associated with the customer identification data; and

process the transaction request in real-time.

2. The system of claim 1, wherein the transaction includes a cardless cash withdrawal, the system configured to:

send the transaction request from the ATM to an NPP processing application;

receive, from the processing application a unique PaylD, registered with NPP;

send the unique PaylD to the ATM;

receive confirmation that the customer transferred the funds using the PaylD; and,

dispense the funds on the ATM.

3. The system of claim 2, wherein the system is configured to:

receive payment notification from the financial institution, the payment notification being associated with the unique pay identifier; and,

generate the cardless cash withdrawal via the ATM.

4. The system of claim 1, wherein the transaction includes a cash deposit, the system being configured to: send the transaction request, including customer identification information from the ATM to an NPP processing application;

NPP processing application transfer the funds to the customer's account; receive confirmation of the cash deposit from the NPP processing application; and, send confirmation of the cash deposit to the ATM.

5. A system for performing a transaction, the system configured to activate a primary user, the system configured to perform the steps of:

(a) receive customer identification information associated with the primary user;

(b) receive customer bank/financial details associated with the customer identification information;

(c) generate a micro-payment;

(d) receive confirmation of payment; and

(e) complete authentication of the primary user.

6. The system of claim 5, wherein the system further verifies the customer identification information prior to generating the micro-payment.

7. The system of any one of claims 5 or 6, wherein the system receives an indication of a secondary user.

8. The system of claim 7, wherein the system associates the secondary user with the primary user or a primary user account.

9. The system of claim 8 wherein when either one or a combination of the primary or the secondary user make a deposit request at an ATM, the system generates a unique code associated with the primary user account for providing to the ATM.

10. An Automatic Teller Machine (ATM), the ATM being configured to interact with the system of any one of claims 5 to 8 to perform the transaction.

11. An Automatic Teller Machine (ATM), for performing a transaction, the ATM being configured to:

(a) receive a deposit request;

(b) receive an indication of a unique code associated with a user; and,

(c) perform/generate the transaction accordingly.

12. The ATM of claim 11, wherein the ATM interacts with the system of any one of claims 1 to 8 to perform the transaction.