# US 2014/0279425 A1 · Methods, systems, and devices for handling multiple disparate systems

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

- Number: US 2014/0279425 A1
- Document ID: US20140279425A1
- Status: Published application
- Kind: A1
- Application number: 13/932,991
- Filed: 2013-07-01
- Published: 2014-09-18
- Earliest claimed: 2013-03-15
- Assignees: Elwha LLC
- Applicants: Elwha LLC
- Inventors: Pablos Holman; Roderick A. Hyde; Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud
- Web page: https://patentgrep.com/patent/US20140279425A1

## CPC

- G06Q 20/10: specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
- G06Q 20/08: Payment architectures
- 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

## Abstract

Computationally implemented methods and systems include acquiring at least one user payment channel, said at least one user payment channel including at least one of a user payment option and a user payment modality, acquiring at least one vendor payment channel, said at least one vendor payment channel including at least one of a vendor payment option and a vendor payment modality, wherein at least a portion of the at least one vendor payment channel is different from the at least one user payment channel, and facilitating a first portion of a potential transaction between a first party and a second party by using the at least one user payment channel. In addition to the foregoing, other aspects are described in the claims, drawings, and text.

## Claims

### Claim at position 1

1-169. (canceled)

### Claim 170

A device, comprising:
a client payment channel obtaining module, wherein the client payment channel includes one or more of at least one client payment option and at least one client payment modality;
a vendor payment channel obtaining module, wherein the vendor payment channel includes one or more of at least one vendor payment option that is different from the at least one client payment option and at least one vendor payment modality that is different than the client payment modality;
a client payment channel application to a first portion of a potential transaction between a client and a vendor assisting module; and
a vendor payment channel application to a second portion of the potential transaction between the client and the vendor conducing through use of at least a partial result of the first portion of the potential transaction module.

### Claim 171 (depends on 170)

The device of claim 170, wherein said client payment channel obtaining module, wherein the client payment channel includes one or more of at least one client payment option and at least one client payment modality comprises:
a client payment channel receiving module, wherein the client payment channel includes one or more of at least one client payment option and at least one client payment modality.

### Claim 172

(canceled)

### Claim 173

(canceled)

### Claim 174

(canceled)

### Claim 175

(canceled)

### Claim 176 (depends on 171)

The device of claim 171, wherein said client payment channel receiving module, wherein the client payment channel includes one or more of at least one client payment option and at least one client payment modality comprises:
a client payment channel that includes one or more of at least one client payment option and at least one client payment modality receiving from a device-accessible marketplace entity module.

### Claim 177

(canceled)

### Claim 178 (depends on 176)

The device of claim 176, wherein said client payment channel that includes one or more of at least one client payment option and at least one client payment modality receiving from a device-accessible marketplace entity module comprises:
a client payment channel that includes one or more of at least one client payment option and at least one client payment modality receiving from a marketplace that has access to data regarding a client-related device entity module.

### Claim 179 (depends on 170)

The device of claim 170, wherein said client payment channel obtaining module, wherein the client payment channel includes one or more of at least one client payment option and at least one client payment modality comprises:
a client payment channel acquiring from an entity configured to store transaction data module, wherein the client payment channel includes one or more of at least one client payment option and at least one client payment modality.

### Claim 180

(canceled)

### Claim 181 (depends on 179)

The device of claim 179, wherein said client payment channel acquiring from an entity configured to store transaction data module, wherein the client payment channel includes one or more of at least one client payment option and at least one client payment modality comprises:
a client payment channel including one or more of at least one client payment option and at least one client payment modality acquiring from an entity configured to transmit transaction detail data module.

### Claim 182

(canceled)

### Claim 183 (depends on 170)

The device of claim 170, wherein said client payment channel obtaining module, wherein the client payment channel includes one or more of at least one client payment option and at least one client payment modality comprises:
a client payment channel including one or more of at least one client payment option and at least one client payment modality acquiring from a device data collecting entity module.

### Claim 184 (depends on 170)

The device of claim 170, wherein said client payment channel obtaining module, wherein the client payment channel includes one or more of at least one client payment option and at least one client payment modality comprises:
a client payment channel that includes one or more of at least one client payment option and at least one client payment modality acquiring from a device design and/or manufacturing contributing entity module.

### Claim 185 (depends on 184)

The device of claim 184, wherein said client payment channel that includes one or more of at least one client payment option and at least one client payment modality acquiring from a device design and/or manufacturing contributing entity module comprises:
a client payment channel that includes one or more of at least one client payment option and at least one client payment modality acquiring from a device kernel at least partial authoring entity module.

### Claim 186 (depends on 184)

The device of claim 184, wherein said client payment channel that includes one or more of at least one client payment option and at least one client payment modality acquiring from a device design and/or manufacturing contributing entity module comprises:
a client payment channel that includes one or more of at least one client payment option and at least one client payment modality acquiring from an application at least partial authoring entity module.

### Claim 187 (depends on 170)

The device of claim 170, wherein said client payment channel obtaining module, wherein the client payment channel includes one or more of at least one client payment option and at least one client payment modality comprises:
a client payment channel that includes one or more of at least one client payment option and at least one client payment modality acquiring from a service providing entity module.

### Claim 188

(canceled)

### Claim 189

(canceled)

### Claim 190

(canceled)

### Claim 191

(canceled)

### Claim 192 (depends on 170)

The device of claim 170, wherein said client payment channel obtaining module, wherein the client payment channel includes one or more of at least one client payment option and at least one client payment modality comprises:
a data regarding an application configured to manage at least a portion of client payment data acquiring module;
a client payment data retrieving from the application module; and
a client payment channel generating at least partly from retrieved client payment data module.

### Claim 193 (depends on 192)

The device of claim 192, wherein said data regarding an application configured to manage at least a portion of client payment data acquiring module comprises:
a data identifying an application that is configured to manage at least a portion of client payment data acquiring module.

### Claim 194

(canceled)

### Claim 195

(canceled)

### Claim 196 (depends on 192)

The device of claim 192, wherein said data regarding an application configured to manage at least a portion of client payment data acquiring module comprises:
a data identifying an application that is configured to manage at least a portion of client payment data stored on a client device configured to carry out one or more applications acquiring module.

### Claim 197

(canceled)

### Claim 198

(canceled)

### Claim 199 (depends on 192)

The device of claim 192, wherein said data regarding an application configured to manage at least a portion of client payment data acquiring module comprises:
a condition for accessing at least a portion of client payment data acquiring module.

### Claim 200

(canceled)

### Claim 201

(canceled)

### Claim 202

(canceled)

### Claim 203

(canceled)

### Claim 204 (depends on 192)

The device of claim 192, wherein said client payment data retrieving from the application module comprises:
a client payment data including client payment channel set retrieving from the application module.

### Claim 205

(canceled)

### Claim 206

(canceled)

### Claim 207 (depends on 192)

The device of claim 192, wherein said client payment channel generating at least partly from retrieved client payment data module comprises:
a client payment channel generating at least partly from retrieved client payment data and at least partly based on a property of a device environment module.

### Claim 208

(canceled)

### Claim 209

(canceled)

### Claim 210

(canceled)

### Claim 211

(canceled)

### Claim 212

(canceled)

### Claim 213

(canceled)

### Claim 214 (depends on 170)

The device of claim 170, wherein said vendor payment channel obtaining module, wherein the vendor payment channel includes one or more of at least one vendor payment option that is different from the at least one client payment option and at least one vendor payment modality that is different than the client payment modality comprises:
a vendor payment channel that includes one or more of at least one vendor payment option that is different from the at least one user payment option and at least one vendor payment modality that is different from the at least one user payment modality generating module.

### Claim 215 (depends on 214)

The device of claim 214, wherein said vendor payment channel that includes one or more of at least one vendor payment option that is different from the at least one user payment option and at least one vendor payment modality that is different from the at least one user payment modality generating module comprises:
a vendor payment channel that includes one or more of at least one vendor payment option that is different from the at least one user payment option and at least one vendor payment modality that is different from the at least one user payment modality generating at least partly based on one or more factors regarding the vendor module.

### Claim 216

(canceled)

### Claim 217

(canceled)

### Claim 218 (depends on 214)

The device of claim 214, wherein said vendor payment channel that includes one or more of at least one vendor payment option that is different from the at least one user payment option and at least one vendor payment modality that is different from the at least one user payment modality generating module comprises:
a vendor payment channel that includes one or more of at least one vendor payment option that is different from the at least one user payment option and at least one vendor payment modality that is different from the at least one user payment modality generating at least partly based on one or more factors regarding the vendor collected by a client-related device module.

### Claim 219 (depends on 170)

The device of claim 170, wherein said vendor payment channel obtaining module, wherein the vendor payment channel includes one or more of at least one vendor payment option that is different from the at least one client payment option and at least one vendor payment modality that is different than the client payment modality comprises:
a vendor payment channel including one or more of at least one vendor payment option that is different from the at least one user payment option and at least one vendor payment modality that is different from the at least one user payment modality generating at least partly based on a vendor characteristic module.

### Claim 220

(canceled)

### Claim 221

(canceled)

### Claim 222

(canceled)

### Claim 223 (depends on 170)

The device of claim 170, wherein said client payment channel application to a first portion of a potential transaction between a client and a vendor assisting module comprises:
a first portion of the potential transaction between the client and the vendor executing through use of the at least one client payment channel module.

### Claim 224 (depends on 223)

The device of claim 223, wherein said first portion of the potential transaction between the client and the vendor executing through use of the at least one client payment channel module comprises:
a first portion of the potential transaction that includes intake of client data using the at least one client payment channel executing module.

### Claim 225 (depends on 224)

The device of claim 224, wherein said first portion of the potential transaction that includes intake of client data using the at least one client payment channel executing module comprises:
a first portion of the potential transaction including that includes intake of client data executing through use of at least one of a client payment option and a client payment modality module.

### Claim 226

(canceled)

### Claim 227 (depends on 170)

The device of claim 170, wherein said client payment channel application to a first portion of a potential transaction between a client and a vendor assisting module comprises:
a client payment channel selection from client payment channel set module; and
a selected client payment channel application to the first portion of the potential transaction between the client and the vendor assisting module.

### Claim 228 (depends on 227)

The device of claim 227, wherein said client payment channel selection from client payment channel set module comprises:
a client payment channel set selection from client payment channel set at least partly based on one or more vendor payment channels module.

### Claim 229

(canceled)

### Claim 230 (depends on 228)

The device of claim 228, wherein said client payment channel set selection from client payment channel set at least partly based on one or more vendor payment channels module comprises:
a client payment channel set and vendor payment channel set union as empty set determination module; and
an at least one compatible client payment channel determining module; and
a determined client payment channel selection from client payment channel set module.

### Claim 231

(canceled)

### Claim 232 (depends on 230)

The device of claim 230, wherein said at least one compatible client payment channel determining module comprises:
an at least one compatible client payment channel determining at least partly based on capacity for translating data communicable using the client payment channel into data communicated using the vendor payment channel module.

### Claim 233 (depends on 232)

The device of claim 232, wherein said at least one compatible client payment channel determining at least partly based on capacity for translating data communicable using the client payment channel into data communicated using the vendor payment channel module comprises:
an at least one compatible client payment channel determining at least partly based on a client-related device capacity for translating data communicable using the client payment channel into data communicated using the vendor payment channel.

### Claim 234

(canceled)

### Claim 235

(canceled)

### Claim 236 (depends on 170)

The device of claim 170, wherein said vendor payment channel application to a second portion of the potential transaction between the client and the vendor conducing through use of at least a partial result of the first portion of the potential transaction module comprises:
a vendor payment channel application to a second portion of a potential transaction between the client and the vendor conducting through use of at least a partial result of the first portion of the potential transaction module.

### Claim 237 (depends on 236)

The device of claim 236, wherein said vendor payment channel application to a second portion of a potential transaction between the client and the vendor conducting through use of at least a partial result of the first portion of the potential transaction module comprises:
a vendor payment channel applying to a second portion of a potential transaction between the client and the vendor that uses at least a partial result of a portion of the potential transaction regarding the client conducting module.

### Claim 238

(canceled)

### Claim 239

(canceled)

### Claim 240 (depends on 170)

The device of claim 170, wherein said vendor payment channel application to a second portion of the potential transaction between the client and the vendor conducing through use of at least a partial result of the first portion of the potential transaction module comprises:
a vendor payment channel application to a second portion of a potential transaction between the client and the vendor that uses data from at least a partial result of the first portion of the potential transaction that has been manipulated conducing module.

### Claim 241 (depends on 240)

The device of claim 240, wherein said vendor payment channel application to a second portion of a potential transaction between the client and the vendor that uses data from at least a partial result of the first portion of the potential transaction that has been manipulated conducing module comprises:
a vendor payment channel application to a second portion of a potential transaction between the client and the vendor that uses data from at least a partial result of the first portion of the potential transaction that has been manipulated by an external data manipulator conducing module.

### Claim 242

(canceled)

### Claim 243 (depends on 240)

The device of claim 240, wherein said vendor payment channel application to a second portion of a potential transaction between the client and the vendor that uses data from at least a partial result of the first portion of the potential transaction that has been manipulated conducing module comprises:
a vendor payment channel application to a second portion of a potential transaction between the client and the vendor that uses data from at least a partial result of the first portion of the potential transaction that has been manipulated using a conversion algorithm conducing module.

### Claim 244 (depends on 170)

The device of claim 170, wherein said vendor payment channel application to a second portion of the potential transaction between the client and the vendor conducing through use of at least a partial result of the first portion of the potential transaction module comprises:
a data from at least a partial result of the first portion of the potential transaction transmitting to an external data manipulator module; and
a particular data configured to be used in facilitating the second portion of the potential transaction receiving from the external data manipulator module.

### Claim 245

(canceled)

### Claim 246 (depends on 244)

The device of claim 244, wherein said data from at least a partial result of the first portion of the potential transaction transmitting to an external data manipulator module comprises:
a location of external data manipulator determining module; and
a data from at least a partial result of the first portion of the potential transaction transmitting to the external data manipulator at the determined location module.

### Claim 247 (depends on 246)

The device of claim 246, wherein said location of external data manipulator determining module comprises:
a location of external data manipulator determining at least partly based on the data module.

### Claim 248 (depends on 246)

The device of claim 246, wherein said location of external data manipulator determining module comprises:
a location of external data manipulator determining using a first party-related device-accessible directory module.

### Claim 249

(canceled)

### Claim 250 (depends on 170)

The device of claim 170, wherein said vendor payment channel application to a second portion of the potential transaction between the client and the vendor conducing through use of at least a partial result of the first portion of the potential transaction module comprises:
an external data facilitator within a particular client proximity determining module;
a data from at least a partial result of the first portion of the potential transaction transmitting to the external data facilitator module; and
a particular data configured to be used in carrying out the second portion of the potential transaction receiving from the external data facilitator module.

### Claim 251

(canceled)

### Claim 252 (depends on 250)

The device of claim 250, wherein said external data facilitator within a particular client proximity determining module comprises:
an external data facilitator selecting from a set of one or more external facilitators that have indicated availability to a client-associated device module.

### Claim at position 85

253-256. (canceled)
