Abstract: Methods and systems consistent with the disclosure include a method for secure transfer using digital channels, comprising: receiving, by a platform executed by one or more processors of a server, a notification of a customer call, wherein the notification comprises an incoming phone call from a user; initiating a customer assist instance responsive to the notification; determining whether to ask the user for a document scan based on whether a user's device is known by the platform; sending, based on a determination that authorization is required, an event to the user's device with a unique scan session; receiving a scanned document from a user's device via use of the unique scan session; and determining, based on the scanned document, to allow a transaction.

Abstract: A method may include: receiving, by a backend computer program and from a service provider system, a message for customer; storing, by the backend computer program, the message with a message identifier for the message; marking, by the backend computer program, a customer electronic device associated with the customer to receive the message on a next customer login on the customer electronic device; receiving, by the backend computer program and from a mobile application or a browser executed by the customer electronic device, a login from the customer; authenticating, by the backend computer program, the customer; confirming, by the backend computer program, that the customer electronic device is marked; and providing, by the backend computer program, the message identifier to the mobile application or the browser; wherein the mobile application or the browser may be configured to retrieve the message using the message identifier and to display the message.

Abstract: In some aspects, the techniques described herein relate to a method including: receiving, at a change request service, a request to update contact information data; receiving, at the change request service, from a verification service provider, a raw ownership score; normalizing, by the change request service, the raw ownership score; sending, by the change request service, the contact information data, the customer identifier, and the normalized ownership score to a risk engine; receiving, by the change request service from the risk engine, a confidence score; providing, by the change request service, the confidence score, the normalized ownership score, and historical data associated with the stored customer profile, to a consolidation function; receiving, by the change request service and from the consolidation function, a consolidated trust score; and updating a datastore record associated with a customer represented by the customer identifier with the contact information data.

Abstract: A method for generating keys in a multi-cloud environment that minimizes the impact of a breach may include: generating and storing a first key encryption key (KEK) in a first environment key management service (KMS); generating a first data encryption key (DEK) using the first KMS; generating a second DEK for a second environment using the first KMS; encrypting the first DEK with the first KEK and the second DEK with the first KEK; storing the encrypted first DEK and the encrypted second DEK in a database; generating a second KEK and storing the second KEK in a second environment KMS; encrypting the first DEK with the second KEK and the second DEK with the second KEK; and storing the encrypted first DEK and the encrypted second DEK in the database.

Abstract: In some aspects, the techniques described herein relate to a method including: receiving, at a change request service, a request to update contact information data; receiving, at the change request service, from a verification service provider, a raw ownership score; normalizing, by the change request service, the raw ownership score; sending, by the change request service, the contact information data, the customer identifier, and the normalized ownership score to a risk engine; receiving, by the change request service from the risk engine, a confidence score; providing, by the change request service, the confidence score, the normalized ownership score, and historical data associated with the stored customer profile, to a consolidation function; receiving, by the change request service and from the consolidation function, a consolidated trust score; and updating a datastore record associated with a customer represented by the customer identifier with the contact information data.

Abstract: Blockchain identity proofing via federation protocols is disclosed.

Abstract: In some aspects, the techniques described herein relate to a method including: receiving, at a change request service, a request to update contact information data; receiving, at the change request service, from a verification service provider, a raw ownership score; normalizing, by the change request service, the raw ownership score; sending, by the change request service, the contact information data, the customer identifier, and the normalized ownership score to a risk engine; receiving, by the change request service from the risk engine, a confidence score; providing, by the change request service, the confidence score, the normalized ownership score, and historical data associated with the stored customer profile, to a consolidation function; receiving, by the change request service and from the consolidation function, a consolidated trust score; and updating a datastore record associated with a customer represented by the customer identifier with the contact information data.

Abstract: In some aspects, the techniques described herein relate to a method including: receiving, at a threat mitigation platform, payment information from a payment product application; providing the payment information to a threat analysis engine of the threat mitigation platform as input to the threat analysis engine; generating, as output of the threat analysis engine and based on the payment information, a threat identifier; querying, by an authorization engine, a threat repository using the threat identifier as a lookup key; receiving, by the authorization engine and from the threat repository, information associated with the threat identifier; and communicating the information associated with the threat identifier to the payment product application.

Abstract: A method for generating keys in a multi-cloud environment that minimizes the impact of a breach may include: generating and storing a first key encryption key (KEK) in a first environment key management service (KMS); generating a first data encryption key (DEK) using the first KMS; generating a second DEK for a second environment using the first KMS; encrypting the first DEK with the first KEK and the second DEK with the first KEK; storing the encrypted first DEK and the encrypted second DEK in a database; generating a second KEK and storing the second KEK in a second environment KMS; encrypting the first DEK with the second KEK and the second DEK with the second KEK; and storing the encrypted first DEK and the encrypted second DEK in the database.

Abstract: Systems and methods for key synchronization in multi-cloud environments are disclosed. A method may include: (1) generating, by a synching computer application and using a first key management service in a first cloud environment, a data encryption key and storing the data encryption key in the first key management service; (2) generating, by the synching computer application and using a second key management service in a second cloud environment, a key encryption key pair comprising a private key and a public key and storing the key encryption key pair in the second key management service; (3) fetching, by the synching computer application, the public key from the second key management service; (4) encrypting, by the synching computer application, the data encryption key with the public key; and (5) storing, by the synching computer application, the encrypted data encryption key in a database in the second cloud environment.

Abstract: Systems and methods for enhancing digital wallet security are disclosed. In one embodiment, a method may include a service provider computer program: (1) receiving a request from a computer program executed by a user electronic device for user authentication with a product identifier for a product; (2) generating a verification code; (3) communicating the product identifier and the verification code to a verification computer program, wherein the verification computer program is configured to retrieve user contact information for a user associated with the product identifier and communicate the verification code to the user electronic device; (4) receiving, by the service provider computer program, a received verification code from the computer program, wherein the received verification code was received at the user electronic device; and (5) communicating authorization for an action involving the product to the computer program in response to the received verification code matching the verification code.