Secure processing of electronic payments

Patent metadata

Field	Value
Publication number	US-11080700-B2
Application number	US-201615000685-A
Country	US
Kind code	B2
Filing date	Jan 19, 2016
Priority date	Jan 19, 2015
Publication date	Aug 3, 2021
Grant date	Aug 3, 2021

Abstract

Systems (100), 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. Common application programming interfaces executed by devices (110) may facilitate push and pull processes between electronic wallets (112) and other secure data stores (136, 120, 160). Users (190) may thereby initiate and complete electronic transactions directly from within applications on trusted devices (110′).

First claim

The invention claimed is:

1. 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 data representing at least:
a plurality of secure payment tokens, each secure payment token comprising data representing an identifier associated with one of a plurality of sources of transaction payment resources and a security key uniquely associated with said source of transaction payment resources; and
one or more sets of machine-interpretable instructions;

the at least one data processor adapted, by execution of the one or more stored sets of machine-interpretable instructions, to:
receive a first set of signals from a merchant application on the user device, the first set of signals including data representing a merchant certificate used as part of a query of the plurality of secure payment tokens;
initiate on the user device, in response to the first set of signals, a payment transaction process, the payment transaction process generating, 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;
upon verification, at the user device, of the merchant certificate, select, from the plurality of secure payment tokens stored in the at least one persistent memory, at least one secure payment token associated with the merchant;
in response to a second set of signals generated by the at least one user input interface, initiate a universal wallet application on the user device, the universal wallet application comprising stored machine-interpretable instructions configured to generate, at the user device, transaction authorization request data sets, each transaction authorization request data set comprising at least one of the selected at least one secure payment token, and at least one transaction payment amount;
in response to a third set of signals generated by the at least one user input interface, the third set of signals representing at least a user selection identifying one of the plurality of sources of transaction payment resources, generate a transaction authorization request data set on the user device, the generated transaction authorization request data set comprising at least one of the selected at least one secure payment token associated with the selected source of transaction payment resources, and the transaction amount payable to the merchant;
using the at least one network communication interface, send the generated transaction authorization request data set to a merchant backend server to be routed to a server associated with the identified source of payment resources; and
receive confirmation that the transaction was completed.

2. The user device of claim 1 , wherein generation and routing of the transaction authorization request data set is conditioned upon receipt by the at least one data processor of a fourth set of signals generated by the at least one user input interface, the fourth set of signals comprising at least a secure identifier associated with an authorized user of the device.

3. The user device of claim 1 , wherein the at least one data processor is adapted, by execution of the same or other stored sets of machine-interpretable instructions, to:
using the same or another user device, receive, from the same or another server associated with the identified source of payment resources, a secure transaction authorization request data set; and
using the same or another of the at least one communication interface, route the secure transaction authorization request data set to a transaction processing system associated with the merchant.

4. The user device of claim 1 , wherein at least a portion of the transaction payment resources represent currency.

5. The user device of claim 1 , wherein at least a portion of the transaction payment resources represent non-currency redeemable points.

6. A user device comprising:
at least one output display;
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 data representing at least:
a plurality of secure payment tokens, each secure payment token comprising data representing an identifier associated with one of a plurality of sources of transaction payment resources; and
one or more sets of machine-interpretable instructions;

the at least one data processor adapted, by execution of the one or more stored sets of machine-interpretable instructions, to:
initiate at the user device, in response to a first set of signals generated by the at least one user input interface, a payment transaction process, the payment transaction process generating, 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;
upon verification, at the user device, of a merchant certificate associated with the merchant identifier, select, from the plurality of secure payment tokens stored in the at least one persistent memory, at least one secure payment token associated with the merchant; and
in response to a second set of signals generated by the at least one user input interface, initiate a first wallet application, the first wallet application comprising at least a first one of the plurality of secure payment tokens and stored machine-interpretable instructions which configure the at least one data processor to:
cause the at least one output display to display a human-interpretable user interface adapted to solicit a user selection of one a plurality of sources of payment resources to be applied toward satisfaction of a requested transaction, at least one of the sources of payment resources associated with the source of payment resources identified by the first one of the plurality of secure payment tokens, and at least a second of the sources of payment resources not associated with the source of payment resources identified by the first one of the plurality of secure payment tokens;
receive from the at least one user input interface signals representing a user selection of one of the plurality of sources of payment resources to be applied toward satisfaction of a related transaction;
when the user selection of one of the plurality of sources of payment resources corresponds to the source of payment resources identified by the first one of the plurality of secure payment tokens,
generate, at the user device, a transaction authorization request data set comprising at least the first one of the plurality of secure payment tokens,
and
send the transaction authorization request data set to a merchant backend server to be routed to a server associated with the source of payment resources identified by the first one of the plurality of secure payment tokens; and

receive confirmation that the transaction was completed.

7. The user device of claim 6 , wherein the at least one data processor is adapted, by execution of the same or other stored sets of machine-interpretable instructions, to:
when the user selection of one of the plurality of sources of payment resources does not correspond to the source of payment resources identified by the first one of the plurality of secure payment tokens, initiate a second wallet application, the second wallet application comprising at least a second one of the plurality of secure payment tokens and stored machine-interpretable instructions configured to cause the same or another data proces

Assignees

• Royal Bank Of Canada

Inventors

• Ortiz Edison U
• Lee Terry W
• Woo Gabriel Y
• Scott Stephen James
• Yin Weiqiang
• Dinn Judy
• Lam Chai

Classifications

• G06Q20/227 Primary

  characterised in that multiple accounts are available, e.g. to the payer · CPC title

• G06Q20/40 Primary

  Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists · CPC title

• G06Q20/385

  using an alias or single-use codes · CPC title

• G06Q20/363

  with the personal data of a user · CPC title

• G06Q20/3227

  using secure elements embedded in M-devices · CPC title