On-boarding of Mobile-Wallet Datasets
A system for onboarding banking-account information for use in future transactions includes a banking-device terminal to read banking-account information from a banking card and input device(s) to receive a verification input associating the banking card with a banking customer. A secured-bank server receives an account number from the banking-account information and the verification input to verify the account number corresponds with the verification input to authorize the onboarding transaction, wherein when the onboarding transaction is authorized the banking-device terminal requests a customer device identification of a mobile-customer device, wherein when the onboarding transaction is authorized the banking-device terminal causes account credentials banking-account information to be stored in the mobile-customer device and not in the secured-bank server, and wherein when the onboarding transaction is authorized the banking-device terminal causes the account number of the banking-account information to be stored in the secured-bank server and not in the mobile-customer device.
1 . A system comprising:
a banking-device terminal comprising:
a card-reading device configured to receive a banking card and to read banking-account information that includes an account number and account credentials from the banking card;
an input device configured to receive a verification input that associates the banking card with a banking customer, and wherein the input device is adapted to receive a request for an onboarding transaction; and
an secured-bank server configured to receive the banking-account information and the verification input and to verify the banking-account information corresponds with the verification input to authorize the onboarding transaction, wherein when the onboarding transaction is authorized the banking-device terminal is configured to request a customer-device identification of a mobile-customer device for use in future-banking transactions, wherein when the onboarding transaction is authorized the banking-device terminal causes banking card credentials of the banking-account information to be stored in the mobile-customer device and not in the secured-bank server, and wherein when the onboarding transaction is authorized the banking-device terminal causes the account number of the banking-account information to be stored in the secured-bank server and not in the mobile-customer device.
2 . The system of claim 1 wherein the future-banking transactions are performed by accessing the secured-bank server without accessing the banking card.
3 . The system of claim 1 wherein the mobile-customer device is a phone.
4 . The system of claim 3 wherein the customer-device identification is a phone number.
5 . The system of claim 1 wherein banking terminal device is selected from the group consisting of an automatic transaction device (ATM) and a point of sale (POS) device.
6 . The system of claim 1 wherein the input further comprises:
a keypad.
7 . The system of claim 1 wherein the verification input is a personal identification number (PIN).
8 . The system of claim further comprising:
a token platform configured to create tokenized data of at least one of the group of: the customer-device identification, the banking-account information and the verification input, wherein the banking-account information stored on the secured-bank server is the tokenized data.
9 . The system of claim 8 further comprising:
an application used to request the future-banking transactions, wherein the application is software protected; and
a device-validation engine, wherein the tokenized platform is configured to interrogate the device-validation engine, wherein upon a successful interrogation the token platform is configured to provide the mobile-customer device with a link for downloading the application to the mobile-customer device.
10 . The system of claim 9 wherein the device-validation engine is configured to perform the interrogation by determining if the at least one of the group of: the customer-device identification and the banking-account information are consistent with a corresponding name in a pre-known billing record.
11 . The system of claim 10 wherein the pre-known billing record is a mobile network operator (MNO) billing record.
12 . The system of claim 1 further comprising:
an application used to request the future-banking transactions. wherein when the onboarding transaction is authorized the secured-bank server is configured to send data for downloading the application to the mobile-customer device.
13 . The system of claim 1 wherein the at-least-one input device further comprises:
a biometric data input device and wherein the verification input is selected from the group consisting of a scan of a portion of an eye of the banking customer, a scan of a face of the banking customer and a scan of a portion of a fingerprint of the banking customer.
14 . The system of claim 1 wherein the secured-bank server is configured to not authorize the onboarding transaction when the banking-account information does not correspond with the verification input.
15 . The system of claim 1 wherein the banking card is a credit card wherein the system copies existing security credentials from the credit card to the mobile-customer device.
16 . A method of onboarding financial data comprising:
reading banking-account information including an account number and account credentials from the banking card;
receiving a verification input that associates the banking card with a banking customer;
verifying on a secure-banking system that the banking-account information corresponds with the verification input;
when the verification is successful requesting a customer-device identification of a mobile-customer device, wherein the customer device is to be used for a future-banking transaction;
receiving the customer-device identification; and
when the verification is successful storing the account number and verification input in the secured-banking system and not on the mobile-customer device; and wherein when the verification is successful storing the account credentials in the mobile-customer device and not on the secured-banking system.
17 . The method of claim 16 wherein the future-banking transaction is later performed at an automatic transaction machine (ATM) without accessing the banking card.
18 . The method of claim 16 wherein the mobile-customer device is a phone.
19 . A network-banking system for performing onboarding of data associated with a customer-banking account comprising:
a banking device with a first input device configured to read banking-account information associated with the customer-banking account from a banking card issued to a banking customer, wherein the banking-account information includes an account number and account credentials associated with the account number;
a second input device on the banking device configured to receive verification data that associates the banking customer with the banking card; and
a secured-banking system configured to receive and verify that the banking-account information matches the verification data and requests device identification information that identifies a personal device that the banking customer may use to request future transactions using the customer-banking account, wherein the network-banking system is configured to store the account number in the secured-banking system and not on the personal device, wherein the network-banking system is configured to store the account credentials in the personal device and not in the secured-banking system.
20 . The system for performing onboarding of data associated with a customer-banking account of claim 19 wherein the banking device is an ATM, the verification data is a PIN, the personal device is a mobile phone and the device identification information is a phone number of the mobile phone.