US 11,699,152 B2
Secure processing of electronic payments
Stephen James Scott, Oakville (CA); Weiqiang Yin, Mississauga (CA); Edison U. Ortiz, Orlando, FL (US); Terry W. Lee, Toronto (CA); Gabriel Y. Woo, Toronto (CA); Judy Dinn, Toronto (CA); and Chai Lam, Toronto (CA)
Assigned to ROYAL BANK OF CANADA, Montreal (CA)
Filed by ROYAL BANK OF CANADA, Toronto (CA)
Filed on Jul. 30, 2021, as Appl. No. 17/389,984.
Application 17/389,984 is a continuation of application No. 15/201,428, filed on Jul. 2, 2016, granted, now 11,080,701.
Application 15/201,428 is a continuation in part of application No. 15/000,685, filed on Jan. 19, 2016, granted, now 11,080,700.
Claims priority of provisional application 62/200,859, filed on Aug. 4, 2015.
Claims priority of provisional application 62/188,067, filed on Jul. 2, 2015.
Claims priority of provisional application 62/105,061, filed on Jan. 19, 2015.
Prior Publication US 2022/0020016 A1, Jan. 20, 2022
This patent is subject to a terminal disclaimer.
Int. Cl. G06Q 20/40 (2012.01); G06Q 20/36 (2012.01); G06Q 20/12 (2012.01); G06Q 20/02 (2012.01)
CPC G06Q 20/40 (2013.01) [G06Q 20/023 (2013.01); G06Q 20/12 (2013.01); G06Q 20/36 (2013.01)] 19 Claims
OG exemplary drawing
 
1. A computer-implemented method comprising:
using signals generated by at least one user input interface of a user device, and signals received from a merchant transaction system via at least one near-field communication interface:
generating, by at least one third-party wallet application at the user device, 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:
generating, by at least one trusted wallet application at 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 a communication interface of the user device:
routing, by the at least one trusted wallet application, the transaction authorization request data set to a transaction processing system;
receiving, 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;
passing, by the at least one trusted wallet application to the at least one third-party wallet application, the dynamic card token;
sending, by the at least one third-party wallet application, the dynamic card token to the merchant transaction system; and
receiving, at the user device, a confirmation message that the transaction is complete.