Abstract
Computationally implemented methods and systems include acquiring an indication of one or more conditions related to a potential transaction between a vendor and a user, acquiring a vendor payment channel set, said vendor payment channel set including one or more vendor payment channels, at least one of said one or more vendor payment channels including at least one of a vendor payment option and a vendor payment modality, and adapting at least one user payment channel for use with a vendor payment channel of the vendor payment channel set to facilitate at least a portion of the potential transaction, wherein the adapting at least one user payment channel includes one or more of selecting a user payment channel that is present in the vendor payment channel set and interfacing a user payment channel that is absent in the vendor payment channel set. In addition to the foregoing, other aspects are described in the claims, drawings, and text.
Claims
-
A computationally-implemented method, comprising:
acquiring an indication of one or more conditions related to a potential transaction between a vendor and a user;
acquiring a vendor payment channel set, said vendor payment channel set including one or more vendor payment channels, at least one of said one or more vendor payment channels including at least one of a vendor payment option and a vendor payment modality; and
adapting at least one user payment channel for use with a vendor payment channel of the vendor payment channel set to facilitate at least a portion of the potential transaction, wherein the adapting at least one user payment channel includes one or more of selecting a user payment channel that is present in the vendor payment channel set and interfacing a user payment channel that is absent in the vendor payment channel set.
-
The computationally-implemented method of claim 1, wherein said acquiring an indication of one or more conditions related to a potential transaction between a vendor and a user comprises:
receiving an indication that a user has interacted with an interface of a personal device, said interaction related to the potential transaction between the vendor and the user.
- (canceled)
- (canceled)
-
The computationally-implemented method of claim 1, wherein said acquiring an indication of one or more conditions related to a potential transaction between a vendor and a user comprises:
detecting one or more conditions related to the potential transaction between the vendor and the user.
- (canceled)
- (canceled)
-
The computationally-implemented method of claim 5, wherein said detecting one or more conditions related to the potential transaction between the vendor and the user comprises:
detecting that the user carried out one or more particular actions.
- (canceled)
- (canceled)
- (canceled)
-
The computationally-implemented method of claim 1, wherein said acquiring an indication of one or more conditions related to a potential transaction between a vendor and a user comprises:
receiving, from a third party contracting from the vendor, an indication of a potential transaction between the vendor and the user.
- (canceled)
- (canceled)
- (canceled)
- (canceled)
- (canceled)
- (canceled)
-
The computationally-implemented method of claim 1, wherein said acquiring a vendor payment channel set, said vendor payment channel set including one or more vendor payment channels, at least one of said one or more vendor payment channels including at least one of a vendor payment option and a vendor payment modality comprises:
acquiring the vendor payment channel set, said vendor payment channel set including a particular vendor payment channel set, said particular vendor payment channel set including a particular vendor payment modality set.
- (canceled)
- (canceled)
- (canceled)
- (canceled)
- (canceled)
-
The computationally-implemented method of claim 1, wherein said acquiring a vendor payment channel set, said vendor payment channel set including one or more vendor payment channels, at least one of said one or more vendor payment channels including at least one of a vendor payment option and a vendor payment modality comprises:
receiving the vendor payment channel set including one or more vendor payment channels.
- (canceled)
-
The computationally-implemented method of claim 25, wherein said receiving the vendor payment channel set including one or more vendor payment channels comprises:
receiving the vendor payment channel set, including one or more vendor payment channels, from a channel set manager.
- (canceled)
- (canceled)
-
The computationally-implemented method of claim 1, wherein said acquiring a vendor payment channel set, said vendor payment channel set including one or more vendor payment channels, at least one of said one or more vendor payment channels including at least one of a vendor payment option and a vendor payment modality comprises:
generating the vendor payment channel set, including one or more vendor payment channels.
-
The computationally-implemented method of claim 30, wherein said generating the vendor payment channel set, including one or more vendor payment channels comprises:
generating the vendor payment channel set, including one or more vendor payment channels, from information obtained about the vendor.
- (canceled)
- (canceled)
- (canceled)
- (canceled)
-
The computationally-implemented method of claim 1, wherein said adapting at least one user payment channel for use with a vendor payment channel of the vendor payment channel set to facilitate at least a portion of the potential transaction, wherein the adapting at least one user payment channel includes one or more of selecting a user payment channel that is present in the vendor payment channel set and interfacing a user payment channel that is absent in the vendor payment channel set comprises:
generating a user payment channel set, said user payment channel set at least partly based on one or more attributes of a user device; and
adapting a user payment channel of the user payment channel set to facilitate at least a portion of the potential transaction, by selecting a user payment channel that is present in the vendor payment channel set.
-
The computationally-implemented method of claim 36, wherein said generating a user payment channel set, said user payment channel set at least partly based on one or more attributes of a user device comprises:
generating the user payment channel set, said user payment channel set at least partly based on one or more attributes of the user device, said user payment channel set including a user payment channel that is present in the vendor payment channel set.
- (canceled)
-
The computationally-implemented method of claim 36, wherein said generating a user payment channel set, said user payment channel set at least partly based on one or more attributes of a user device comprises:
generating the user payment channel set, said user payment channel set at least partly based on one or more user device settings.
- (canceled)
-
The computationally-implemented method of claim 36, wherein said generating a user payment channel set, said user payment channel set at least partly based on one or more attributes of a user device comprises:
retrieving a list of one or more user payment channel preferences; and
generating the user payment channel set, at least partly based on the retrieved list of one or more user payment channel preferences.
-
The computationally-implemented method of claim 41, wherein said retrieving a list of one or more user payment channel preferences comprises:
retrieving the list of one or more user payment channel preferences, said list of one or more user payment channel preferences including one or more of a list of at least one user payment modality preference and a list of at least one user payment option preference.
-
The computationally-implemented method of claim 41, wherein said retrieving a list of one or more user payment channel preferences comprises:
retrieving a ranked list of one or more user payment channel preferences, said ranked list of one or more user payment channel preferences including one or more ordered rankings of the one or more user payment channel preferences.
-
The computationally-implemented method of claim 43, wherein said retrieving a ranked list of one or more user payment channel preferences, said ranked list of one or more user payment channel preferences including one or more ordered rankings of the one or more user payment channel preferences comprises:
retrieving the ranked list of one or more user payment channel preferences, said ranked list of one or more user payment channel preferences including an ordered ranking of one or more of at least one user payment modality preference and at least one user payment option preference.
- (canceled)
- (canceled)
-
The computationally-implemented method of claim 36, wherein said generating a user payment channel set, said user payment channel set at least partly based on one or more attributes of a user device comprises:
generating the user payment channel set, said user payment channel set at least partly based on one or more user device settings that are set by a user device manufacturer.
-
The computationally-implemented method of claim 36, wherein said generating a user payment channel set, said user payment channel set at least partly based on one or more attributes of a user device comprises:
generating the user payment channel set, said user payment channel set at least partly based on one or more user device settings that are set by an application operating on the user device.
-
The computationally-implemented method of claim 36, wherein said generating a user payment channel set, said user payment channel set at least partly based on one or more attributes of a user device comprises:
generating the user payment channel set, said user payment channel set at least partly based on one or more input and/or output capabilities of the user device.
- (canceled)
- (canceled)
-
The computationally-implemented method of claim 36, wherein said generating a user payment channel set, said user payment channel set at least partly based on one or more attributes of a user device comprises:
generating the user payment channel set, said user payment channel set at least partly based on one or more data access levels of the user device.
-
The computationally-implemented method of claim 52, wherein said generating the user payment channel set, said user payment channel set at least partly based on one or more data access levels of the user device comprises:
generating the user payment channel set, said user payment channel set at least partly based on the user device access to a translation table for one or more proprietary vendor codes.
- (canceled)
-
The computationally-implemented method of claim 1, wherein said adapting at least one user payment channel for use with a vendor payment channel of the vendor payment channel set to facilitate at least a portion of the potential transaction, wherein the adapting at least one user payment channel includes one or more of selecting a user payment channel that is present in the vendor payment channel set and interfacing a user payment channel that is absent in the vendor payment channel set comprises:
selecting a user payment channel from a user payment channel set for use with a vendor payment channel of the vendor payment channel set to facilitate at least a portion of the potential transaction, wherein said selected user payment channel is present in the vendor payment channel set.
- (canceled)
- (canceled)
- (canceled)
- (canceled)
- (canceled)
-
The computationally-implemented method of claim 1, wherein said adapting at least one user payment channel for use with a vendor payment channel of the vendor payment channel set to facilitate at least a portion of the potential transaction, wherein the adapting at least one user payment channel includes one or more of selecting a user payment channel that is present in the vendor payment channel set and interfacing a user payment channel that is absent in the vendor payment channel set comprises:
generating a user payment channel; and
adapting the generated user payment channel for use with the vendor payment channel of the vendor payment channel set to facilitate at least a portion of the potential transaction.
- (canceled)
-
The computationally-implemented method of claim 61, wherein said generating a user payment channel comprises:
generating one or more user payment options and/or one or more user payment modalities by contacting one or more entities associated with one or more user payment options and/or one or more user payment modalities
-
The computationally-implemented method of claim 1, wherein said adapting at least one user payment channel for use with a vendor payment channel of the vendor payment channel set to facilitate at least a portion of the potential transaction, wherein the adapting at least one user payment channel includes one or more of selecting a user payment channel that is present in the vendor payment channel set and interfacing a user payment channel that is absent in the vendor payment channel set comprises:
adapting at least one user payment channel for use with a vendor payment channel of the vendor payment channel set to facilitate at least a portion of the potential transaction, wherein the adapting at least one user payment channel includes selecting a user payment channel that is present in the vendor payment channel set
-
The computationally-implemented method of claim 64, wherein said adapting at least one user payment channel for use with a vendor payment channel of the vendor payment channel set to facilitate at least a portion of the potential transaction, wherein the adapting at least one user payment channel includes selecting a user payment channel that is present in the vendor payment channel set comprises:
selecting the user payment channel that is present in the vendor payment channel set to facilitate at least a portion of the potential transaction, said facilitating including using the selected user payment channel.
-
The computationally-implemented method of claim Error! Reference source not found., wherein said Error! Reference source not found. comprises:
selecting the user payment channel that is present in the vendor payment channel set to facilitate at least a portion of the potential transaction, said selecting at least partly based on one or more vendor payment channel preferences.
- (canceled)
-
The computationally-implemented method of claim 66, wherein said selecting the user payment channel that is present in the vendor payment channel set to facilitate at least a portion of the potential transaction, said selecting at least partly based on one or more vendor payment channel preferences comprises:
receiving a first portion of the vendor payment channel set including a first one or more vendor payment channels;
receiving a second portion of the vendor payment channel set including a second one or more vendor payment channels; and
selecting a user payment channel from the second one or more vendor payment channels.
-
The computationally-implemented method of claim 68, wherein said selecting a user payment channel from the second one or more vendor payment channels comprises:
selecting the user payment channel from the second one or more vendor payment channels after rejecting one or more of the first one or more vendor payment channels.
-
The computationally-implemented method of claim 66, wherein said selecting the user payment channel that is present in the vendor payment channel set to facilitate at least a portion of the potential transaction, said selecting at least partly based on one or more vendor payment channel preferences comprises:
selecting a user payment modality that is present in a user payment modality set to facilitate at least a portion of the potential transaction, said selecting at least partly based on one or more vendor payment modality preferences.
- (canceled)
-
The computationally-implemented method of claim 1, wherein said adapting at least one user payment channel for use with a vendor payment channel of the vendor payment channel set to facilitate at least a portion of the potential transaction, wherein the adapting at least one user payment channel includes one or more of selecting a user payment channel that is present in the vendor payment channel set and interfacing a user payment channel that is absent in the vendor payment channel set comprises:
adapting at least one user payment channel for use with a vendor payment channel of the vendor payment channel set to facilitate at least a portion of the potential transaction, wherein the adapting at least one user payment channel includes interfacing a user payment channel that is absent in the vendor payment channel set.
- (canceled)
-
The computationally-implemented method of claim 72, wherein said adapting at least one user payment channel for use with a vendor payment channel of the vendor payment channel set to facilitate at least a portion of the potential transaction, wherein the adapting at least one user payment channel includes interfacing a user payment channel that is absent in the vendor payment channel set comprises:
carrying out a user portion of the potential transaction using the user payment channel; and
facilitating at least a portion of the potential transaction using the vendor payment channel.
- (canceled)
-
The computationally-implemented method of claim 72, wherein said adapting at least one user payment channel for use with a vendor payment channel of the vendor payment channel set to facilitate at least a portion of the potential transaction, wherein the adapting at least one user payment channel includes interfacing a user payment channel that is absent in the vendor payment channel set comprises:
carrying out a user portion of the potential transaction using a user payment option of the user payment channel; and
converting at least a portion of the data received from the user portion of the potential transaction into data acceptable by a vendor payment option of the vendor payment channel set.
- (canceled)
- (canceled)
-
The computationally-implemented method of claim 1, wherein said adapting at least one user payment channel for use with a vendor payment channel of the vendor payment channel set to facilitate at least a portion of the potential transaction, wherein the adapting at least one user payment channel includes one or more of selecting a user payment channel that is present in the vendor payment channel set and interfacing a user payment channel that is absent in the vendor payment channel set comprises:
carrying out a user portion of the potential transaction by using a user payment modality of the user payment channel that is absent in the vendor payment channel set; and
carrying out a vendor portion of the potential transaction by using a vendor payment modality of the vendor payment channel.
-
The computationally-implemented method of claim 79, wherein said carrying out a vendor portion of the potential transaction by using a vendor payment modality of the vendor payment channel comprises:
contacting an external resource configured to use the vendor payment modality of the vendor payment channel; and
carrying out a vendor portion of the potential transaction using the external resource as an intermediary.
-
The computationally-implemented method of claim 80, wherein said contacting an external resource configured to use the vendor payment modality of the vendor payment channel comprises:
obtaining a list of one or more external resources from a resource manager; and
contacting an external resource from the list of one or more external resources.
- (canceled)
- (canceled)
- (canceled)
-
The computationally-implemented method of claim 81, wherein said obtaining a list of one or more external resources from a resource manager comprises:
obtaining a list of one or more external resources that have a particular attribute, from the resource manager.
- (canceled)
-
The computationally-implemented method of claim 85, wherein said obtaining a list of one or more external resources that have a particular attribute, from the resource manager comprises:
obtaining a list of one or more external resources that have the external resource payment channel set, said external resource payment channel set including one or more payment channels that are present in the vendor payment channel set and one or more payment channels that are present in a user payment channel set.
- (canceled)
- (canceled)
- (canceled)
- (canceled)
-
A computationally-implemented system, comprising:
circuitry for acquiring an indication of one or more conditions related to a potential transaction between a vendor and a user;
circuitry for acquiring a vendor payment channel set, said vendor payment channel set including one or more vendor payment channels, at least one of said one or more vendor payment channels including at least one of a vendor payment option and a vendor payment modality; and
circuitry for adapting at least one user payment channel for use with a vendor payment channel of the vendor payment channel set to facilitate at least a portion of the potential transaction, wherein the adapting at least one user payment channel includes one or more of selecting a user payment channel that is present in the vendor payment channel set and interfacing a user payment channel that is absent in the vendor payment channel set.
- 93-183. (canceled)
Owners (US)
-
Elwha Llc
(Aug 07 2013)
Explore more patents:
Applicants
-
Elwha Llc
Explore more patents:
Inventors
-
Holman Pablos
Explore more patents:
-
Hyde Roderick A
Explore more patents:
-
Levien Royce A
Explore more patents:
-
Lord Richard T
Explore more patents:
-
Lord Robert W
Explore more patents:
-
Malamud Mark A
Explore more patents:
IPC Classifications
-
G06Q20/12
Explore more patents:
US Classifications
-
705/39
Explore more patents:
Document Preview
- Publication: Sep 18, 2014
-
Application:
May 31, 2013
US 201313907565 A
-
Priority:
May 31, 2013
US 201313907565 A
-
Priority:
Mar 15, 2013
US 201313843118 A