Abstract: Systems and methods for using device data to validate a mobile user are disclosed. In accordance with aspects, a method may include receiving, at a backend processing infrastructure of a third party and from a backend processing infrastructure of a mobile application provider, a first copy of location information and an IP address, wherein the location information and the IP address are associated with a mobile device; receiving, at the backend processing infrastructure of the third party and from a mobile application provided by the third party, a second copy of the location information and the IP address, wherein the mobile application provided by the third party is executed on the mobile device; and verifying, by the backend processing infrastructure of the third party, that the first copy of the location information and the IP address matches the second copy of the location information and the IP address.

Abstract: Systems and methods for facilitating payment application provisioning and transacting are disclosed. According to one embodiment, a method for provisioning a token to a third party payment application on a mobile device may include (1) receiving a logon from a customer using a mobile application for a financial institution executed on a mobile device and a device identifier for the mobile device; (2) receiving a request to provision a token for a third party payment application; (3) authenticating the customer using the logon information and the device identifier; (4) provisioning a token for a payment device associated with the customer; and (5) providing the token to the third party payment application for transaction processing.

Abstract: Systems and methods for establishing trust between a conventional mobile application and a micro application are disclosed.

Abstract: Systems and methods for online billpay using credit products are disclosed. In one embodiment, in an information processing apparatus comprising at least one computer processor, a method for online billpay using a credit product may include: (1) receiving, from a customer, an identification of a merchant for online credit-based bill pay; (2) retrieving accepted payment mechanisms from the merchant; (3) selecting a payment mechanism from the accepted payment mechanisms; (4) receiving an invoice for a customer transaction with the merchant from the merchant; (5) conducting a payment transaction with the selected payment mechanism; and (6) charging the payment transaction to a credit account associated with the customer.

Abstract: Systems and methods for issuer-specified domain control on a payment instrument are disclosed. In one embodiment, in an information processing apparatus comprising at least one computer processor, a method for issuer-specified domain controls on a payment instrument may include: (1) receiving, from an issuer of a financial instrument, an identification of a domain control or restriction on a payment token for the financial instrument, the domain control or restriction to be applied by the issuer; (2) requesting generation of the payment token with a pass-through indicator from a token service provider; (3) receiving, from the token service provider, the payment token; and (4) storing an association of the domain control or restriction and the payment token.

Abstract: Systems and methods for online billpay using credit products are disclosed. In one embodiment, in an information processing apparatus comprising at least one computer processor, a method for online billpay using a credit product may include: (1) receiving, from a customer, an identification of a merchant for online credit-based bill pay; (2) retrieving accepted payment mechanisms from the merchant; (3) selecting a payment mechanism from the accepted payment mechanisms; (4) receiving an invoice for a customer transaction with the merchant from the merchant; (5) conducting a payment transaction with the selected payment mechanism; and (6) charging the payment transaction to a credit account associated with the customer.

Abstract: Systems and methods for issuer-specified domain control on a payment instrument are disclosed. In one embodiment, in an information processing apparatus comprising at least one computer processor, a method for issuer-specified domain controls on a payment instrument may include: (1) receiving, from an issuer of a financial instrument, an identification of a domain control or restriction on a payment token for the financial instrument, the domain control or restriction to be applied by the issuer; (2) requesting generation of the payment token with a pass-through indicator from a token service provider; (3) receiving, from the token service provider, the payment token; and (4) storing an association of the domain control or restriction and the payment token.

Abstract: System and methods for supporting legacy and tokenized transactions are disclosed. According to one embodiment, in an information processing device comprising at least one computer processor, a method for selecting an electronic payment credential to communicate to a merchant, may include (1) an electronic wallet backend receiving a plurality of payment credentials associated with a payment account; (2) the electronic wallet backend receiving a credential capability for a merchant; (3) the electronic wallet backend selecting one of the payment credentials for a transaction with the merchant based on the credential capability; and (4) the electronic wallet backend communicating the selected payment credential to a point of transaction device for the merchant.

Abstract: Systems, methods, and devices for integrating a first party service into a second party computer application are disclosed. In one embodiment, in a financial institution comprising at least one computer processor, a method for integrating a financial services payment service into a merchant computer application may include (1) receiving customer electronic device information from a customer electronic device using a first communication channel; (2) transmitting a passcode to the customer electronic device using a second communication channel; (3) receiving the passcode from the customer electronic device over the first communication channel; (4) sending a session identifier to electronic device over first communication channel; (5) receiving the session identifier from a merchant host; and (6) sending an authentication value to a merchant host. The merchant host may provide the authentication value to the customer electronic device.

Abstract: Systems and methods for issuer-specified domain control on a payment instrument are disclosed. In one embodiment, in an information processing apparatus comprising at least one computer processor, a method for issuer-specified domain controls on a payment instrument may include: (1) receiving, from an issuer of a financial instrument, an identification of a domain control or restriction on a payment token for the financial instrument, the domain control or restriction to be applied by the issuer; (2) requesting generation of the payment token with a pass-through indicator from a token service provider; (3) receiving, from the token service provider, the payment token; and (4) storing an association of the domain control or restriction and the payment token.

Abstract: Systems, methods, and devices for integrating a first party service into a second party computer application are disclosed. In one embodiment, in a financial institution comprising at least one computer processor, a method for integrating a financial services payment service into a merchant computer application may include (1) receiving customer electronic device information from a customer electronic device using a first communication channel; (2) transmitting a passcode to the customer electronic device using a second communication channel; (3) receiving the passcode from the customer electronic device over the first communication channel; (4) sending a session identifier to electronic device over first communication channel; (5) receiving the session identifier from a merchant host; and (6) sending an authentication value to a merchant host. The merchant host may provide the authentication value to the customer electronic device.

Abstract: Systems, methods, and devices for assigning a transaction risk score are disclosed. According to one embodiment, a method for generating a transaction risk score may include: (1) receiving, by a transaction scoring service computer program and from an electronic device, a merchant URL that is being accessed by an application or a browser executed on the electronic device; (2) retrieving, by the transaction scoring service computer program, a plurality of transactions involving the merchant URL; (3) generating, by the transaction scoring service computer program, a risk score for the merchant URL based on the plurality of transactions; (4) generating, by the transaction scoring service computer program, a warning in response to the risk score exceeding a predetermined threshold; and (5) communicating, by the transaction scoring service computer program, the warning to the application or the browser.

Abstract: Systems and methods for conducting transactions using cards with keys are disclosed. In one embodiment, a method may include: receiving, at a backend for a financial institution in a transaction, a unique identifier for a card, a key read from the card by a card reading device, and additional data received by the card reading device, the card reading device associated with a merchant; retrieving, by the backend, stored additional data associated with the unique identifier; retrieving, by the backend, a stored key associated with the unique identifier in response to the received additional data matching the stored additional data; confirming, by the backend, that the received key and the stored key are related; retrieving, by the backend, a payment mechanism for the transaction; conducting, by the backend, the transaction with the retrieved payment mechanism; and settling, by the backend, the transaction with the merchant.

Abstract: System and methods for supporting legacy and tokenized transactions are disclosed. According to one embodiment, in an information processing device comprising at least one computer processor, a method for selecting an electronic payment credential to communicate to a merchant, may include (1) an electronic wallet backend receiving a plurality of payment credentials associated with a payment account; (2) the electronic wallet backend receiving a credential capability for a merchant; (3) the electronic wallet backend selecting one of the payment credentials for a transaction with the merchant based on the credential capability; and (4) the electronic wallet backend communicating the selected payment credential to a point of transaction device for the merchant.

Abstract: Systems and methods for facilitating payment service-based guest checkout with a merchant are disclosed. According to one embodiment, a method for facilitating payment service-based guest checkout with a merchant may include: (1) receiving, from a merchant's application or website, a redirect of an online interaction between the merchant and a customer; (2) retrieving, from an issuer payment service, wallet information comprising a plurality of payment options for the customer; (3) receiving a selection of one of the payment options; (4) communicating the selection of the payment option to the payment service for the issuer. The issuer payment service provides a session identifier to the merchant application website, the merchant application or website provides transaction information and the session identifier to a merchant payment host, the merchant payment host retrieves the selected payment option from the issuer payment service and conducts the transaction using the selected payment option.

Abstract: System and methods for supporting legacy and tokenized transactions are disclosed. According to one embodiment, in an information processing device comprising at least one computer processor, a method for selecting an electronic payment credential to communicate to a merchant, may include (1) an electronic wallet backend receiving a plurality of payment credentials associated with a payment account; (2) the electronic wallet backend receiving a credential capability for a merchant; (3) the electronic wallet backend selecting one of the payment credentials for a transaction with the merchant based on the credential capability; and (4) the electronic wallet backend communicating the selected payment credential to a point of transaction device for the merchant.

Abstract: An embodiment of the present invention is directed to systems and methods for securing contactless cards from unauthorized payments, including card cloning attacks. An embodiment of the present invention provides a password at the time of usage of the card to decrypt the data contained in the card at the time when the user is initiating a transaction. In this exemplary illustration, card data may be encrypted at rest, and decrypted at the time of use. Other variations may include a switchable antenna that is disabled at rest and enabled during a transaction.

Abstract: Systems and methods for managing token-based transactions are disclosed. According to one embodiment, a method for managing token-based transactions may include (1) a token manager server comprising at least one computer processor receiving, from a customer, a request to provide a payment token to a merchant; (2) the token manager server receiving, from the customer, an identification of a first financial instrument and a second financial instrument to associate with the payment token; (3) the token manager server receiving, from the customer, an allocation of a transaction between the first financial instrument and the second financial instrument; (4) the token manager server generating the payment token and associating the payment token with the first financial instrument and the second financial instrument; and (5) the token manager server providing the payment token to the merchant.

Abstract: A method for accepting cash deposits or billpays at merchant point of transaction devices may include: (1) receiving, from a customer mobile device, a mobile deposit request comprising a deposit account identifier for a deposit or a mobile billpay request including a payee identifier and a billpay amount; (2) generating a code for the mobile deposit request or the mobile billpay request; (3) communicating the code to the customer mobile device; (4) receiving, from a merchant point of transaction device, a deposit request or a billpay request comprising the code and a received amount; (5) identifying, from the code, the deposit account identifier or the billpay payee identifier and billpay amount; and (6) depositing the received deposit amount to a deposit account associated with the deposit account identifier or executing a billpay to payee associated with the payee identifier for the billpay amount.

Abstract: A system and method of storing purchase card information to enable a consumer to make purchases without carrying a separate purchase card for a plurality of accounts at disparate financial institutions. The system and method may additionally provide a consumer with vendor product and service offerings in a format common across multiple vendors. The system and method may also provide the consumer with a way to pay for products and services using purchase card information stored by an exemplary embodiment.