US 11,080,701 B2Granted

Secure processing of electronic payments

AssigneeRoyal Bank of Canada

InventorsStephen James Scott, Weigiang Yin, Edison U. Ortiz, Terry W. Lee, Gabriel Y. Woo, Judy Dinn, Chai Lam

Life of this patent

Estimating the term…

Loading patent…

Abstract

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.

Claims19

Dependent claims

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.

15 more elements

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.

10 more elements

Dependencies are inferred from the claim text.

Facts

Application: 15/201,428Filed 2 Jul 2016 · continuation in part
Priority: 2 Jul 2015
Published: US 2017/0017958 A119 Jan 2017
Granted: 3 Aug 2021
Term ends: Not estimatedThe source records don’t support an estimate.

Classification7 codes

G06Q 20/40
Payment protocols; Details thereof: authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and…
G06Q 20/023
Involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]: the neutral party being a clearing house
G06Q 20/12
Payment architectures: specially adapted for electronic shopping systems
G06Q 20/326
Using wireless devices: payment applications installed on the mobile devices

Family

Application62/188,067Us provisional application · filed 2 Jul 2015
Application62/200,859Us provisional application · filed 4 Aug 2015
Application15/000,685Parent of this continuation-in-part · filed 19 Jan 2016
US 2017/0017958 A1Pre-grant publication · published 19 Jan 2017
US 11,080,700 B2Related patent
US 2016/0210626 A1Published application
US 11,080,701 B2This patent

From the US filing history. Foreign family members aren’t listed.