Conducting transactions using electronic devices with non-native credentials
Systems, methods, and computer-readable media for conducting a transaction using an electronic device with a non-native credential are provided. In one embodiment, a client electronic device in a system including a credential subsystem, a processing subsystem, and a host electronic device may include an online communications component and a processor that accesses, from the processing subsystem, potential transaction data indicative of a transaction, communicates, to the host electronic device using the online communications component, credential request data based on the potential transaction data, receives, from the host electronic device using the online communications component, host credential data based on the credential request data, and communicates, to the processing subsystem, the host credential data, wherein the host credential data is operative to access funds or other suitable enabling elements from the credential subsystem for funding at least a portion of the transaction. Additional embodiments are also provided.
1. A method comprising:
at a host electronic device:
receiving, from a client electronic device that is associated with a same user account as the host electronic device, payment request data corresponding to a financial transaction between the client electronic device and a merchant subsystem, the payment request data comprising:
merchant subsystem identifier information that identifies the merchant subsystem; and
host credential application identifier information that identifies a host credential application provisioned on a secure element of the host electronic device;
generating, on the secure element using the host credential application identified by the received payment request data, first data that comprises host payment credential data;
generating, on the secure element, second data by encrypting the first data and the merchant subsystem identifier information of the received payment request data with a first key;
transmitting, to a commercial entity subsystem, the second data;
receiving third data that comprises the first data encrypted with a second key that is associated with the merchant subsystem identifier information; and
transmitting the received third data to fund at least a portion of the financial transaction between the client electronic device and the merchant subsystem.
2. The method of claim 1 , wherein:
the first key is not accessible to the merchant subsystem; and
the second key is not accessible to the host electronic device.
3. The method of claim 1 , wherein the third data is not encrypted with the first key.
4. The method of claim 1 , wherein the first key is accessible to the commercial entity subsystem.
5. The method of claim 1 , wherein:
the generating the first data comprises generating the first data by encrypting the host payment credential data with a third key; and
at least a portion of the third data is encrypted with the third key.
6. The method of claim 5 , wherein the third key is not accessible to the merchant subsystem.
7. The method of claim 5 , wherein the third key is not accessible to the commercial entity subsystem.
8. The method of claim 1 , wherein the receiving the third data comprises receiving the third data from the commercial entity subsystem after the transmitting the generated second data.
9. The method of claim 1 , further comprising, prior to the generating the second data, receiving, at the host electronic device, the first key from the commercial entity subsystem.
10. The method of claim 1 , wherein the transmitting the received third data comprises transmitting the received third data to the client electronic device.
11. The method of claim 10 , wherein:
the second key is not accessible to the host electronic device; and
the second key is not accessible to the client electronic device.
12. The method of claim 10 , further comprising:
at the client electronic device:
accessing potential transaction data via an online resource of the merchant subsystem;
identifying the merchant subsystem identifier information from the accessed potential transaction data; and
generating the payment request data using the identified merchant subsystem identifier information.
13. The method of claim 12 , further comprising:
at the client electronic device:
receiving the third data transmitted by the host electronic device; and
transmitting the received third data to the merchant subsystem using the accessed online resource.
14. The method of claim 12 , further comprising:
at the client electronic device:
identifying at least one payment type acceptable to the merchant subsystem from the accessed potential transaction data; and
transmitting a host availability request that identifies the identified at least one payment type.
15. The method of claim 14 , further comprising:
prior to the receiving the payment request data, at the host electronic device:
receiving the transmitted host availability request;
determining that the host credential application satisfies the identified at least one payment type of the received host availability request; and
based on the determination, transmitting a host availability response comprising the host credential application identifier information.
16. The method of claim 1 , further comprising:
prior to the receiving the payment request data, at the host electronic device:
receiving, from the client electronic device, a host availability request; and
based on the received host availability request, transmitting, to the client electronic device, a host availability response comprising the host credential application identifier information.
17. The method of claim 1 , wherein the receiving the payment request data comprises the host electronic device receiving the payment request data from the client electronic device via an online communications path.
18. The method of claim 1 , wherein the transmitting the received third data comprises transmitting the received third data from the host electronic device to the client electronic device via an online communications path.
19. The method of claim 1 , wherein:
the transmitting the received third data comprises transmitting the received third data to the client electronic device; and
the method further comprises the client electronic device transmitting the third data to the merchant subsystem.
20. The method of claim 1 , wherein:
the payment request data further comprises a unique payment request identifier; and
the transmitting the received third data comprises transmitting the received third data and the unique payment request identifier to the client electronic device.
21. A host electronic device comprising:
a communications component;
a secure element and a host credential application provisioned on the secure element; and
a processor that:
receives, from a client electronic device using the communications component, payment request data corresponding to a transaction between the client electronic device and a merchant subsystem, the payment request data comprising:
merchant identifier information that identifies the merchant subsystem; and
host credential application identifier information that identifies the host credential application provisioned on the secure element;
generates, on the secure element using the host credential application identified by the received payment request data, first data that comprises host payment credential data;
generates, on the secure element, second data by encrypting the first data with a first key;
transmits, to a commercial entity subsystem using the communications component, the second data and the merchant identifier information of the received payment request data; and
receives third data that comprises the first data encrypted with a second key that is associated with the merchant identifier information.
22. The host electronic device of claim 21 , wherein the first key is not accessible to the merchant subsystem.
23. The host electronic device of claim 21 , wherein the second key is not accessible to the host electronic device.
24. The host electronic device of claim 21 , wherein the third data is not encrypted with the first key.
25. The host electronic device of claim 21 , wherein the first key is accessible to the commercial entity subsystem.
26. The host electronic device of claim 21 , wherein:
the processor generates the first data by encrypting the host payment credential data with a third key; and
at least a portion of the third data is encrypted with the third key.
27. The host electronic device of claim 26 , wherein the third key is not accessible to the merchant subsystem.
28. The host electronic device of claim 26 , wherein the third key is not accessible to the commercial entity subsystem.
29. The host electronic device of claim 21 , wherein the processor transmits the received third data to the client electronic device.
30. The host electronic device of claim 29 , wherein:
the second key is not accessible to the host electronic device; and
the second key is not accessible to the client electronic device.
31. The host electronic device of claim 21 , wherein, prior to receiving the payment request data, the processor:
receives, from the client electronic device using the communications component, a host availability request; and
based on the received host availability request, transmits, to the client electronic device using the communications component, a host availability response comprising the host credential application identifier information.
32. The host electronic device of claim 21 , wherein:
the payment request data further comprises a unique payment request identifier; and
the processor transmits the received third data and the unique payment request identifier to the client electronic device.
33. A non-transitory computer-readable storage medium storing at least one program, the at least one program comprising instructions, which when executed by a host electronic device comprising a secure element and a host credential application provisioned on the secure element, cause the host electronic device to:
receive, from a client electronic device, payment request data that comprises:
a merchant identifier that identifies a merchant subsystem; and
a host credential application identifier that identifies the host credential application;
generate, on the secure element using the host credential application identified by the received payment request data, first data that comprises host payment credential data;
generate second data by encrypting the first data with a first key; and
transmitting, to a commercial entity subsystem, the second data and the merchant identifier of the received payment request data.
34. The non-transitory computer-readable storage medium of claim 33 , wherein the instructions, when executed by the host electronic device, further cause the host electronic device to receive third data that comprises the first data encrypted with a second key that is associated with the merchant subsystem identifier information.
35. The non-transitory computer-readable storage medium of claim 34 , wherein the instructions, when executed by the host electronic device, further cause the host electronic device to transmit the received third data to fund at least a portion of a financial transaction.