Secure processing of electronic payments
Systems ( 100, 900 ), methods, and machine-executable data structures for the processing of data for the secure creation, administration, manipulation, processing, and storage of electronic data useful in the processing of electronic payment transactions and other secure data processes. Aspects of such systems ( 100 ) include trusted platforms ( 120 ) by which networked communication devices ( 110 ) and merchant systems ( 130 ) may registered as trusted entities 110′, 130 . Information associated with particular payment means, such as accounts or payment tokens, can be stored on device(s) secure data sets known as virtual or electronic wallets ( 112 ), or in the form of secure payment tokens. Among other improvements, the invention enables the use of multiple payment accounts to fund purchases and other electronic transactions.
1. A user device comprising:
at least one user input interface;
at least one near-field communication interface;
at least one network communication interface;
at least one data processor; and
at least one persistent memory, the at least one persistent memory comprising stored data and machine-interpretable instructions representing:
at least one third-party wallet application; and
at least one trusted wallet a application;
the at least one data processor configured, by execution of the one or more sets of stored, machine-interpretable instructions to:
using signals generated by the at least one user input device and signals received from a merchant transaction system via the at least one near-field communication interface, generate, by the at least one third-party wallet application, a requested transaction data set, the requested transaction data set comprising at least an identifier associated with a merchant and a transaction amount payable to the merchant;
in response to further signals generated by the at least one user input interface, generate, by the at least one trusted wallet application, a transaction authorization request data set comprising data representing at least the merchant, the transaction amount payable to the merchant, at least two transaction payment funding sources, and a portion of the transaction amount payable to the merchant to be funded using each of the plurality of transaction payment funding sources;
using at least one of the at least one network communication interface and the near field communication interface, route, by the at least one trusted wallet application, the transaction authorization request data set to a transaction processing system;
receive, by the at least one trusted wallet application from the transaction processing system, in response to the transaction authorization request data set, a dynamic card token comprising the transaction amount payable to the merchant, and a single transaction payment funding source identifier;
pass, by the at least one trusted wallet application to the at least one third-party wallet application, the dynamic card token;
send, by the at least one third-party wallet application, the dynamic card token to the merchant transaction system; and
receive a confirmation message that the transaction is complete.
2. The user device of claim 1 , comprising at least one touch-sensitive input-output display interface, the at least one persistent memory comprising stored, machine-interpretable instructions which configure the at least one data processor to:
display, on the at least one touch sensitive input-output display interface, an interactive slider graphical device adapted to enable a user of the device to designate a desired portion of the transaction amount payable to the merchant to be funded using at least one of the plurality of payment funding sources; and
using signals generated in response to user designation of the desired portion, generate the same or another transaction authorization request data set.
3. The user device of claim 1 , wherein the plurality of transaction payment funding sources comprises at least any two of: a least one currency debit account, at least one currency credit account, and at least one non-currency value account.
4. The user device of claim 3 , wherein at least of the at least one currency debit account and at least one currency credit account comprises a gift account.
5. The user device of claim 3 , wherein the at least one non-currency value account comprises at least one of a loyalty points account, a rewards points account, and a gift account.
6. The user device of claim 1 , wherein the plurality of transaction payment funding sources comprises at least one of: a loyalty points account, a rewards points account, and a gift account; which is not acknowledged by said merchant as a transaction payment funding source.
7. The user device of claim 1 , wherein the generated transaction authorization request data set comprises data interpretable by the transaction processing platform as an instruction to cause the amount payable to the merchant to be funded using at least one interim funding source.
8. The user device of claim 7 , wherein the at least one interim funding source is not represented by the data representing the at least two transaction payment funding sources.
9. The user device of claim 1 , wherein the transaction authorization request data set is formatted in accordance with a payment protocol, the payment protocol providing a discretionary data field, and the discretionary data field comprises data encoded to represent the at least two payment funding sources and the portion of the transaction amount payable to the merchant to be funded using each of the plurality of payment funding sources.
10. A user device comprising:
at least one user input interface;
at least one network communication interface;
at least one data processor and
at least one persistent memory, the at least one persistent memory comprising stored, machine-interpretable instructions which configure the at least one data processor to:
using the at least one network communication interface, establish, by a third-party wallet application on the user device, a transaction communication session with a merchant transaction system;
using signals generated by the at least one user input interface and signals received from a merchant transaction system via the transaction communication session, generate, by the third-party wallet application, a requested transaction data set, the requested transaction data set comprising at least an identifier associated with a merchant and a transaction amount payable to the merchant;
in response to further signals generated by the at least one user input interface, generate, by a trusted wallet application on the user device, a transaction authorization request data set comprising data representing at least the merchant, the transaction amount payable to the merchant, at least two transaction payment funding sources, and a portion of the transaction amount payable to the merchant to be funded using each of the plurality of transaction payment funding sources;
using at least one of the at least one network communication interface and the at least one data processor, route, by the trusted wallet application, the transaction authorization request data set to a transaction processing system;
receive, by the trusted wallet application from the transaction processing system, in response to the transaction authorization request data set, a dynamic card token comprising the transaction amount payable to the merchant, and a single transaction payment funding source identifier;
pass, by the trusted wallet application to the third-party wallet application, the dynamic card token;
send, by the third-party wallet application, the dynamic card token to the merchant transaction system; and
receive a confirmation message that the transaction is complete.
11. The user device of claim 10 , wherein the transaction communication session is established by execution of stored, machine-interpretable instructions associated with a merchant transaction application.
12. The user device of claim 10 , wherein the transaction communication session is established by execution of stored, machine-interpretable instructions associated with a network browser application.
13. The user device of claim 11 , wherein the plurality of transaction payment funding sources comprises at least any two of: a least one currency debit account, at least one currency credit account, and at least one non-currency value account.
14. The user device of claim 12 , wherein at least of the at least one currency debit account and at least one currency credit account comprises a gift account.
15. The user device of claim 12 , wherein the at least one non-currency value account comprises at least one of a loyalty points account, a rewards points account, and a gift account.
16. The user device of claim 10 , wherein the plurality of transaction payment funding sources comprises at least one of: a loyalty points account, a rewards points account, and a gift account; which is not acknowledged by said merchant as a transaction payment funding source.
17. The user device of claim 10 , wherein the generated transaction authorization request data set comprises data interpretable by the transaction processing platform as an instruction to cause the amount payable to the merchant to be funded using at least one interim funding source.
18. The user device of claim 17 , wherein the at least one interim funding source is not represented by the data representing the at least two transaction payment funding sources.
19. The user device of claim 10 , wherein the transaction authorization request data set is formatted in accordance with a payment protocol, the payment protocol providing a discretionary data field, and the discretionary data field comprises data encoded to represent the at least two payment funding sources and the portion of the transaction amount payable to the merchant to be funded using each of the plurality of payment funding sources.