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: 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 token and transaction management are disclosed. According to one embodiment, in an issuer wallet server comprising at least one computer processor, a method for token and transaction management may include: (1) receiving a update for an attribute for a Device WalletID or an issuer wallet application executed by an electronic device; (2) providing the update to the issuer wallet application; (3) providing the update to a third party wallet server associated with a third party wallet application executed by the electronic device, wherein the third party wallet server communicates the update to the third party wallet application; and (4) updating the attribute in the Device WalletID.

Abstract: In one embodiment, in an information processing apparatus comprising at least one computer processor, a method for issuing an identity verification token to a user may include: (1) receiving, from a user, identity information; (2) generating an identity profile for the user comprising the identity information; (3) associating an identity verification token with at least some of the identity information in the identity profile; and (4) communicating the identity verification token to the user. The user may store the identity verification token in an electronic wallet.

Abstract: Systems and methods for digital identity verification are disclosed. In one embodiment, in an information processing apparatus comprising at least one computer processor, a method for digital identify verification may include: (1) receiving, from a user electronic device or at a website, an image of an identity document for a user, the identity document comprising an image of the user; (2) processing the identity document with at least one business-specific rule; (3) extracting identity information from the identity document; (4) determining a match rate of the image of the user on the identity document to a captured image; (5) assigning a verification score to the user based on extracted identity information and the match rate; and (6) publishing the verification score to at least one system.

Abstract: Systems, methods, and devices for obfuscation of browser fingerprint data are disclosed. In one embodiment, in an information processing apparatus comprising at least one computer processor, a method may include: (1) receiving an electronic communication from an electronic device to a destination; (2) identifying a raw device fingerprint value in the electronic communication from an electronic device; (3) selecting at least one replacement value for the raw device fingerprint value; (4) replacing the raw device fingerprint value with the replacement value in the electronic communication; and (5) sending the electronic communication with the replacement value to the destination.

Abstract: A system and a method are provided for facilitating a transaction. The method may include: obtaining information that relates to a user's intention with respect to a desired experience; determining user benefits that apply to proposed transactions that relate to the desired experience with merchants; providing information that relates to the proposed user benefits to the user; and providing, to the user, an instrument that is configured to facilitate a performance of the proposed transactions.

Abstract: Systems and methods for facilitating banking transactions at a point of sale device are disclosed. In one embodiment, in an information processing apparatus for a financial institution comprising at least one computer processor, a method for facilitating banking transactions at a third-party point of transaction device may include: (1) receiving, from a computer application executed by a customer electronic device, a request for a code to conduct a remote banking transaction with an account associated with the customer at the financial institution; (2) generating the code; (3) providing the code to the customer; (4) receiving, from a payment enabler, a banking transaction request from a third party comprising the code and a transaction amount for the banking transaction; and (5) updating a balance for the account based on the transaction amount.

Abstract: Systems and methods for identifying and processing person-to-person payments are disclosed. In one embodiment, in an information processing apparatus comprising at least one computer processor, a method for processing a transaction may include: (1) receiving, from a third-party payment platform and via a card association and an acquirer, a transaction request comprising a person-to-person payment indicator in a pass-through field in the transaction request; (2) updating a token transaction characteristic value to contain a person-to-person payment flag; and (3) applying a business rule to the transaction request based on the person-to-person payment flag.

Abstract: Systems and methods for token and transaction management are disclosed. According to one embodiment, in an issuer wallet server comprising at least one computer processor, a method for token and transaction management may include: (1) receiving a update for an attribute for a Device WalletID or an issuer wallet application executed by an electronic device; (2) providing the update to the issuer wallet application; (3) providing the update to a third party wallet server associated with a third party wallet application executed by the electronic device, wherein the third party wallet server communicates the update to the third party wallet application; and (4) updating the attribute in the Device WalletID.

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.

Abstract: Systems and methods for securely calling APIs on an API gateway from applications that need first party authentication are disclosed. In one embodiment, a method may include: (1) receiving, from a protected service, an authentication system token/cookie identifier, a first plurality of user identifying attributes, and a request to create an oAuth access token; (2) creating an attribute string; (3) encrypting the attribute string with a private key, resulting in the oAuth access token; (4) sending the oAuth access token to the first party computer application; (5) receiving, from the first party computer application, a request to access a backend service, a second plurality of user identifying attributes, and the oAuth access token; (6) decrypting the oAuth access token; (7) validating the decrypted oAuth access token; (8) inserting the authentication system token/cookie identifier into the request to access; and (9) communicating the request to the backend service.

Abstract: Systems and methods for facilitating payments and reward tracking are disclosed. In one embodiment, in a merchant information processing apparatus comprising at least one computer processor, a method for facilitating customer payments and reward tracking may include: (1) providing an interface for accessing a financial institution backend in a merchant interface; (2) receiving user information from the financial institution backend; (3) generating a merchant loyalty account for the user based on the user information received from the financial institution backend; and (4) providing merchant loyalty account information to the financial institution backend.

Abstract: In one embodiment, in an information processing apparatus comprising at least one computer processor, a method for binding a GET/AUTHORIZE URL to a proxy through a native application may include: (1) receiving, at a native application executed by an electronic device, an applink call or a universal link call from a third-party application executed by the electronic device, the redirect comprising at least one parameter; (2) providing a Get/Authorize call with the at least one parameter to an API gateway; (3) receiving a 302 redirect from the API gateway; (4) providing authentication information to an authorization platform; (5) receiving an authorization code from the authorization platform; and (6) redirecting the third-party application with the redirect URL and authorization code.

Abstract: Systems and methods for out-of-band, time-based matching for applying issuer benefits to a transaction are disclosed. In one embodiment, in an issuer authorization platform comprising at least one computer processor, a method for out-of-band, time-based matching for applying issuer benefits to a transaction may include: (1) receiving, from a computer application executed by an electronic device and over a communication network, a payment option to apply to a transaction conducted with a merchant; (2) receiving, from a payment network, an authorization request for the transaction from the merchant; (3) matching the payment option to the authorization request when the payment option and the authorization request are received within a predetermined time of each other; and (4) applying the payment option to the transaction.

Abstract: System and methods for managing third party tokens and transaction across issuer ecosystems are disclosed. In one embodiment, in an information processing device comprising at least one computer processor, a method for managing payment tokens may include: (1) a first computer program associated with a financial institution and executed by the information processing device accessing a payment token associated with a second computer program executed by the information processing device; (2) the first computer program identifying the payment token as associated with a financial instrument issued by the financial institution; (3) a backend for the financial institution generating an association between the payment token and the financial institution; and (4) the backend for the financial institution communicating the association to an authorization platform for the financial institution.

Abstract: Systems and methods for secure digital safe deposit boxes are disclosed. In one embodiment, a method for using a secure digital safe deposit box may include: (1) receiving permission from a customer to access internal and third party financial or confidential information for the customer; (2) retrieving the internal financial or confidential information for the customer; (3) receiving account information accounts held with a third party that holds financial or confidential information; (4) jointly authenticating the customer with the third party; (5) receiving the third party financial or confidential information for the customer from the third party; (6) receiving permission to share at least some of the internal or third party financial or confidential information for the customer with an external party; and (7) sharing the internal or third party financial or confidential information for the customer with the external party in accordance with the permission.

Abstract: Systems and methods for using a cryptogram lockbox are disclosed. In one embodiment, in a merchant-specific cryptogram lockbox comprising at least one computer processor, a method for generating a cryptogram locally using a cryptogram lockbox may include: (1) receiving, from merchant backend, a request for a cryptogram comprising an account identifier received from a customer in a transaction; (2) generating a cryptogram for the account identifier using a limited use key for the account identifier; and (3) returning the cryptogram to the merchant backend. The merchant may conduct the transaction using the cryptogram.

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.