# US 2017/0286956 A1 · Cross-channel security authentication

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2017/0286956 A1
- Document ID: US20170286956A1
- Status: Published application
- Kind: A1
- Application number: 15/085,039
- Filed: 2016-03-30
- Published: 2017-10-05
- Earliest claimed: 2016-03-30
- Assignees: NCR Corporation
- Applicants: NCR Corporation
- Inventors: Andrew William Richards
- Web page: https://patentgrep.com/patent/US20170286956A1

## CPC

- G06Q 20/401: {Transaction verification}
- G06K 7/1404: {Methods for optical code recognition}
- G06K 19/06112: {the marking being simulated using a light source, e.g. a barcode shown on a display or a laser beam with time-varying intensity profile}
- G06Q 20/327: {Short range or proximity payments by means of M-devices}
- G07F 7/127: {in which both online and offline card verification can take place}
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06K: GRAPHICAL DATA READING (image or video recognition or understanding G06V); PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
- G07F: COIN-FREED OR LIKE APPARATUS (coin sorting G07D3/00; coin testing G07D5/00; {handling coins or paper currencies apart from payment activated apparatus G07D; payment architectures, schemes or protocols G06Q20/00})

## Abstract

Various embodiments each include at least one of systems, devices, methods, and software for cross-channel security authentication, such as with regard to providing of payment card (e.g., credit and debit card) data for payment within a transaction. One such embodiment, in the form of a method includes receiving, by a payment account app on a mobile device, a payment authorization request and subsequently receiving approval or denial input within the payment account app following receipt of valid payment account authentication input. This method, following receipt of approval input, further includes generating authorized payment output to provide in response to the received payment authorization request.

## Claims

### Claim 1

A method comprising:
receiving, by a payment account app on a mobile device, a payment authorization request including a payment amount and payee identifying data;
retrieving an available funds amount of the payment account over a network by the payment account app on the mobile device from a process of a financial institution that maintains the payment account;
verifying the payment amount included in payment authorization request is no greater than the retrieved available funds amount;
receiving approval or denial input within the payment account app following receipt of valid payment account authentication input; and
following receipt of approval input:
generating authorized payment output to provide in response to the received payment authorization request; and
transmitting data representative of at least a portion of the authorized payment output to a financial institution that maintains a payment account from which payment is to be made, the data representative of at least a portion of the authorized payment output notifying the financial institution of the authorization to preauthorize the financial institution to make the payment.

### Claim 2 (depends on 1)

The method of claim 1, wherein:
the payment authorization request is received by the payment account app as an app-to-app call on the mobile device from another app on the mobile device requesting payment; and
returning the authorized payment output to the app requesting payment.

### Claim 3 (depends on 1)

The method of claim 1, wherein:
generating the authorized payment output includes generating a scanable barcode encoded with data to facilitate processing of the requesting payment by a source of the payment authorization request; and
presenting the scanable barcode on a display of the mobile device.

### Claim at position 4

4-5. (canceled)

### Claim 6 (depends on 5)

The method of claim 5, wherein the available funds amount is a lesser amount of a daily payment account limit and an amount of funds within a pre-paid account or a credit limit of a post-paid account.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
upon receipt of the payment authorization request, transmitting, by the payment account app from the mobile device over a network to a payment authorization process of a financial institution that maintains the payment account, the received payment authorization request augmented with at least payment account identifying data;
receiving, by the payment account app on the mobile device, an authorization of the payment authorization request from the payment authorization process; and
presenting a user interface on the mobile device within which the approval or denial input is received.

### Claim 8 (depends on 7)

The method of claim 7, further comprising:
upon receipt of the approval input, transmitting data indicating receipt of the approval input in the payment account app from the mobile device to the payment authorization process of the financial institution, the indication of receipt of the approval input notifying the financial institution that a payment request will be forthcoming via a payment processing network.

### Claim 9 (depends on 1)

The method of claim 1, wherein the authorized payment output includes payment account data for processing of the payment request on a payment processing network, at least a portion of the payment account data being a hashed representation thereof.

### Claim 10 (depends on 9)

The method of claim 9, wherein the hashed representation of the at least a portion of the payment account data is generated within the payment account app on the mobile device by application of a hashing algorithm to the at least a portion of the payment account data.

### Claim 11

A method comprising:
receiving, via a network from a payment account app that executes on a mobile device, approved payment transaction data including data identifying an authenticated payment account, a payment amount, and a payee identifier; and
storing the approved payment transaction data at least until a corresponding payment transaction is received via a payment processing network and matched with the approved payment transaction data indicating the transaction of the approved transaction data was initiated and approved by an authenticated account holder via the payment account app that executes on the mobile device.

### Claim 12 (depends on 11)

The method of claim 11, wherein the received approved payment transaction data further includes a token that is provided by the payment account app to the payee, is subsequently received via the payment processing network, and is utilized in the matching of the transaction received via the payment processing network with the approved payment transaction data.

### Claim 13 (depends on 12)

The method of claim 12, wherein the token is a hashed representation of at least a portion of the approved payment transaction data.

### Claim 14 (depends on 11)

The method of claim 11, further comprising:
transmitting, via the network to the payment account app, an approval of the transaction of the approved payment transaction when a payment amount is no greater than a lesser amount of a daily payment account limit and an amount of funds within a pre-paid account or a credit limit of a post-paid account; and
receiving, via the network from the payment account app, an indication of tendering of the payment of the approved payment transaction.

### Claim 15

A device comprising:
at least one processor;
at least one memory device;
at least one input device;
a display device;
at least one network interface device; and
a payment account app stored in the at least one memory device and executable by the at least one processor to perform data processing activities comprising:
receiving a payment authorization request including a payment amount and payee identifying data;
retrieving an available funds amount of the payment account over a network by the payment account app on the mobile device from a process of a financial institution that maintains the payment account;
verifying the payment amount included in payment authorization request is no greater than the retrieved available funds amount:
presenting a representation of the payment authorization request on the display device;
receiving approval or denial input via the at least one input device following receipt of valid payment account authentication input via the at least one input device; and
following receipt of approval input:
generating authorized payment output to provide in response to the received payment authorization request; and
transmitting, via the at least one network interface device, data indicating receipt of the approval input to a payment authorization process of a financial institution that maintains the payment account, the indication of receipt of the approval input notifying the financial institution that an authenticated payment request will be forthcoming via a payment processing network.

### Claim 16 (depends on 15)

The device of claim 15, wherein:
the payment authorization request is received by the payment account app via an application programming interface (API) call originating with another app on the mobile device or another device via a wireless signal requesting payment; and
returning the authorized payment output to the originator of the payment authorization request

### Claim 17 (depends on 16)

The device of claim 16, further comprising:
a radio transceiver device; and
wherein:
the payment authorization request is received wirelessly via the radio transceiver device; and
the authorized payment output to the originator of the payment authorization request is returned as a transmission of the authorized payment output via the radio transceiver device.

### Claim 18 (depends on 15)

The device of claim 15, wherein:
generating the authorized payment output includes generating a scanable barcode encoded with data to facilitate processing of the requesting payment by a source of the payment authorization request; and
presenting the scanable barcode on the display device.

### Claim 19

(canceled)

### Claim 20 (depends on 15)

The device of claim 15, wherein the authorized payment output includes payment account data for processing of the payment request on a payment processing network, at least a portion of the payment account data being a hashed representation thereof.
