Abstract: A method for verifying origin of request for payments may include a financial institution computer program: receiving a request for a payment URL from a merchant, the payment URL provided for a transaction with a customer; generating the payment URL, wherein the payment URL comprises a pointer to a network location for the financial institution; providing the payment URL to a customer electronic device; receiving, from the customer electronic device and at a browsed URL, a stored or pinned certificate of domain for the payment URL; (5) comparing the stored or pinned certificate of domain for the payment URL to a certificate of domain for the browsed URL; presenting a payment page in response to a match; and returning an error in response to a mismatch.

Abstract: Systems and methods for protection of data across multiple users and devices are disclosed. According to one embodiment, in privacy server comprising at least one computer processor, a method for protection of data across multiple users and devices may include: (1) receiving, from a first user device, a data sharing permission for the first user device and a data sharing permission for a second user device, the first user device and the second user device associated with the same user; (2) provisioning the data sharing permission for the second user device; and (3) communicating the provisioned data sharing permission to the second user device, wherein the second user device shares data with the first user device according to the provisioned data sharing permission.

Abstract: Systems and methods for conversational transacting are disclosed. In one embodiment, a method may include: (1) receiving, by a merchant computer program, a payment instrument from a customer; (2) initiating, by the merchant computer program, a session with the customer by providing a session identifier for the session to a customer electronic device; (3) during the session: receiving, by the merchant computer program, a plurality of transactions from the customer, each with the session identifier; and authorizing, by the merchant computer program, each of the plurality of transactions with an issuer of the payment instrument; and (4) at an end of the session: aggregating, by the merchant computer program, the transactions that were authorized by the issuer; and submitting, by the merchant computer program, the aggregated transactions to the issuer for payment.

Abstract: A method may include: a credit classification computer program (1) ingesting historical data for prior credit applications; (2) separating the historical data into a plurality of categories; (3) encrypting the historical data in each category; (4) training a machine learning model for each category with the encrypted historical data for that category; (5) receiving, from a credit applicant computer program, credit applicant information; (6) separating the credit applicant information into the plurality of categories; (7) predicting, using the plurality of machine learning models for each category, a credit classification using the credit application information for that category; (8) aggregating the plurality of credit classifications into a final credit classification; and (9) outputting the final credit classification to a downstream system, wherein the downstream system is configured to execute an action in response to the final credit classification.

Abstract: A method for verifying origin of request for payments may include a financial institution computer program: receiving a request for a payment URL from a merchant, the payment URL provided for a transaction with a customer; generating the payment URL, wherein the payment URL comprises a pointer to a network location for the financial institution; providing the payment URL to a customer electronic device; receiving, from the customer electronic device and at a browsed URL, a stored or pinned certificate of domain for the payment URL; (5) comparing the stored or pinned certificate of domain for the payment URL to a certificate of domain for the browsed URL; presenting a payment page in response to a match; and returning an error in response to a mismatch.

Abstract: A mobile computer application may (1) access a financial institution mobile application to determine if there is an account that is eligible for provisioning to the mobile computer application; (2) initiate a secure session with the financial institution backend in response to a determination that there is an account eligible for provisioning to the mobile computer application; (3) request an identification of an account that is eligible for provisioning to the mobile computer application from the financial institution backend; (4) receive a pointer to an account that is eligible for provisioning to the mobile computer application from the financial institution backend; (5) display an icon for the eligible account; (6) receive a selection of the icon; (7) return the pointer to the financial institution backend; (8) receive a provisioning payload for the eligible account from the financial institution backend; and (9) initiate in-application provisioning of the eligible account.

Abstract: Systems and methods for dynamic inclusion of enhanced data in transactions are disclosed. According to another embodiment, in an information processing apparatus comprising at least one computer processor, a method for conducting a mobile wallet payment with dynamic enhanced data using a mobile payment application may include: (1) receiving, from a merchant point of transaction device, a transaction request from a mobile payment application executed by a mobile electronic device, the transaction request comprising a unique identifier for a financial instrument provisioned to a mobile wallet computer application and a payment option selection; and (2) processing the transaction request according to the payment option selection.

Abstract: A method may include: an originating system receiving decisioning data from an applicant as part of an application for a product, the originating system redirecting the applicant to a sensitive data capture computer program; the sensitive data capture computer program receiving a unique identifier from the originating system; the sensitive data capture computer program receiving the sensitive data from the applicant, wherein the originating system does not have access to the sensitive data; the sensitive data capture computer program associating the sensitive data with the unique identifier; a matching computer program receiving a decision from the originating system on the application and the unique identifier; the matching computer program receiving the sensitive data and the unique identifier from the sensitive data capture computer program and matching the sensitive data and the decision using the unique identifier; and a compliance reporting program generating a report using the match.

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

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

Abstract: Systems and methods for providing embedded banking services are disclosed. In one embodiment, a method for providing embedded banking services on an electronic device may include (1) a computer program executed by an electronic device comprising a computer processor generating a request to enable embedded banking services for a financial institution on the electronic device; (2) the computer program communicating the request to a host for the electronic device; (3) the computer program receiving a secure token and an encryption key from one of the host of the electronic device and the financial institution; (4) the computer program storing the secure token and encryption key in secure storage of the electronic device; and (5) the computer program enabling embedded banking services on the electronic device.

Abstract: Systems and methods for restricted resource access management are disclosed. A method may include: a user application executed by a user electronic device receiving a request for access to a restricted resource, generating a machine-readable code comprising a unique identifier and a uniform resource locator, communicating the machine-readable code to a backend computer program, and presenting the machine-readable code to an access device for the restricted resource. The access device may communicate the machine-readable code to the backend computer program using the uniform resource locator. The backend computer program may compare the machine-readable code received from the user application to the machine-readable code received from the access device, and may send a control signal to the access device to grant access in response to a match. The access device may grant access to the restricted resource in response to receiving the first control signal.

Abstract: Transaction cards are disclosed. In one embodiment, a transaction card may include: a substrate having a top surface and a bottom surface; a chip comprising a plurality of electrical contacts and positioned in the substrate below the top surface of the substrate; and a first conductive material provided between the plurality of electrical contacts and the top surface of the substrate, wherein the first conductive material provides an electrical connection to the chip such that the chip is readable by a chip reading device. The chip may not be visible from the top surface of the substrate.

Abstract: Systems and methods for using display-enabled transaction cards are disclosed. A display-enabled transaction card may include: a substrate; a display on the substrate; an interface that may be configured to receive a card feature to display on the display; and a controller that may be configured to display the card feature on the display. A method may include: (1) receiving, by a controller of a display-enabled transaction card and via an interface on the display-enabled transaction card, a card feature, wherein the card feature may include card art, a reward status, or an account status; and (2) displaying, on a display of the display-enabled transaction card, the card feature.

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: A method for providing online security may include: (1) receiving, by a validation computer program executed by a trusted entity backend for a trusted entity, a call from a web browser executed on a customer electronic device browsing a webpage for an online entity, the call comprising an online entity identifier for the online entity and a session identifier, wherein the webpage for the online entity may include a hidden <iframe> comprising code that causes the web browser to execute the call; (2) confirming, by the validation computer program, that a cookie for the trusted entity may be stored on the customer electronic device; and (3) returning, by the validation computer program, a first value indicating that the customer electronic device is known to the trusted entity or a second value indicating that the customer electronic device is not known to the trusted entity based on the confirmation.

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 establishing trust between a conventional mobile application and a micro application are disclosed.

Abstract: A method for local data storage governance may include: authenticating, by a privacy service computer program, a user accessing the privacy service using a privacy application; receiving, by the privacy service computer program and from a proxy service, user activity data; saving, by the privacy service computer program, the user activity data to a privacy database; receiving, by the privacy service computer program and from the privacy application, a request for the user activity data; retrieving, by the privacy service computer program and from the privacy database, the user activity data; communicating, by the privacy service computer program, the user activity data to the privacy application, wherein the privacy application stores the user activity data in local storage; receiving, by the privacy service computer program, an acknowledgement of the user activity data; and purging, by the privacy service computer program, the user activity data from the privacy database.

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.