Automated bluetooth pairing
This disclosure relates to creating a Bluetooth and/or BLE connection between two devices without using a UUID and/or MAC address. For example, a first device storing a private key may enter advertising mode to create a Bluetooth/BLE connection. An advertising packet (e.g., advertising channel packet data unit (PDU)) may be transmitted (e.g., in encrypted format). A second device may enter scanning or initiator mode and may receive the advertising packet. A second device may request that a user log into an account associated with the first device (e.g., a customer account, a financial account, an employee account, and/or the like) in order to initiate a Bluetooth/BLE connection. A second device user may enter login credentials via the second device, which may then be transmitted to a backend system. A backend system may receive and validate the login credentials and, in response, transmit a public key to the second device. The public key may be transmitted in an encrypted format. A second device may receive the public key and may use the public key to perform a public/private key handshake in order to validate the first device. The handshake may then be validated by the first device and a Bluetooth and/or BLE connection may be created.
1. A system comprising:
a mobile device comprising:
one or more processors;
a first antenna; and
memory storing a first application that, when executed, causes the mobile device to:
request login credentials for a financial account associated with a dynamic transaction card;
receive the login credentials for the financial account;
transmit, with the first antenna, a request to a backend system for a public key associated with the financial account, the request including the login credentials;
receive, with the first antenna, the public key from the backend system; and
generate, with the one or more processors, an encrypted handshake with the public key; and
the dynamic transaction card comprising:
a EuroPay-MasterCard-Visa (EMV) chip having a secure memory storing a private key;
a second antenna;
a microprocessor; and
a second application that, when executed, causes the dynamic transaction card to:
transmit, via the second antenna, a connection attempt to the mobile device;
receive, via the second antenna, the encrypted handshake from the mobile device;
decrypt, using the private key and the microprocessor, the encrypted handshake;
validate, using the microprocessor, the encrypted handshake; and
create, with the second antenna, a secure Bluetooth or BLE connection between the dynamic transaction card and the mobile device in response to validating the encrypted handshake.
2. The system of claim 1 , wherein the microprocessor validates the encrypted handshake based in part on a public key/private key pair generated by the backend system; and
wherein the public key/private key pair is assigned to the financial account associated with the dynamic transaction card by the backend system.
3. The system of claim 2 , wherein the first application further causes the mobile device to:
request that a user log into the financial account associated with the dynamic transaction card.
4. The system of claim 2 , wherein the first application further causes the mobile device to:
transmit the success or failure of the secure Bluetooth or BLE connection to the backend system.
5. The system of claim 4 , wherein the first application further causes the mobile device to:
transmit a timestamp associated with the connection attempt.
6. The system of claim 1 , wherein second application further causes the dynamic transaction card to:
enter advertising mode; and
transmit advertising packets to the mobile device.
7. The system of claim 6 , wherein the advertising packets are transmitted in an encrypted format.
8. The system of claim 1 , wherein the mobile device receives the public key in an encrypted format.
9. The system of claim 1 , wherein the public key is received at the mobile device via the first application.
10. The system of claim 1 , wherein the backend system stores at least one of account numbers, account names, passwords, or user names for the financial account associated with the dynamic transaction card.
11. A process, comprising:
requesting, via a mobile device, login credentials for a financial account associated with a dynamic transaction card;
receiving, at the mobile device, the login credentials;
transmitting, with a first antenna of a mobile device, a request to a backend system for a public key associated with the financial account, the request including the login credentials;
receiving, at the first antenna, the public key;
generating, by a first microprocessor of the mobile device, an encrypted handshake using the public key;
transmitting, from a second antenna of the dynamic transaction card, a connection attempt to the mobile device;
receiving, at the second antenna, the encrypted handshake from the mobile device;
retrieving, with a second microprocessor of the dynamic transaction card, a private key from a secure memory of the dynamic transaction card;
decrypting, with the second microprocessor, the encrypted handshake using the private key;
validating, with the second microprocessor, the encrypted handshake based on a successful decryption; and
creating, in response to validating the encrypted handshake, a secure Bluetooth or Bluetooth Low Energy (BLE) connection between the dynamic transaction card and the mobile device.
12. The process of claim 11 , wherein:
the second microprocessor validates the encrypted handshake based in part on a public key/private key pair generated by the backend system; and
the public key/private key pair is assigned to the financial account associated with the dynamic transaction card by the backend system.
13. The process of claim 12 , further comprising:
transmitting, with the first antenna, the success or failure of the secure Bluetooth or BLE connection to the backend system.
14. The process of claim 13 , further comprising:
transmitting, with the first antenna, a timestamp associated with the connection attempt.
15. The process of claim 11 , further comprising:
entering, by the dynamic transaction card, advertising mode; and
transmitting, by the second antenna, advertising packets to the mobile device.
16. The process of claim 15 , wherein the advertising packets are encrypted.
17. The process of claim 11 , wherein the first antenna receives the public key in an encrypted format.
18. The process of claim 11 , wherein the backend system stores at least one of account numbers, account names, passwords, or user names for the financial account associated with the dynamic transaction card.