Abstract: Mebendazole is an antiparasitic drug with over 40 years of safe use. Recently mebendazole was repurposed for glioblastoma therapy. Three polymorphs of mebendazole exist, but the relative polymorph content for existing drugs varies, and the therapeutic anti-cancer relevance of the different polymorphs was unknown. As an oral drug mebendazole polymorph C is a superior form, and it reaches the brain and brain tumors in effective concentrations. Efficacy is further improved by combining mebendazole with a P-glycoprotein inhibitor. Mebendazole may also be used for therapy of other cancers, as well as a chemo-preventative agent.

Abstract: Embodiments of the invention are directed to methods, apparatuses, computer readable media and systems for providing, along with a token, a token assurance level and data used to generate the token assurance level. At the time a token is issued, one or more Identification and Verification (ID&V) methods may be performed to ensure that the token is replacing a PAN that was legitimately used by a token requestor. A token assurance level may be assigned to a given token in light of the type of ID&V that is performed and the entity performing the ID&V. Different ID&Vs may result in different token assurance levels. An issuer may wish to know the level of assurance and the data used in generating the level of assurance associated with a token prior to authorizing a payment transaction that uses the token.

Abstract: Embodiments of the invention are directed to methods, apparatuses, computer readable media and systems for providing, along with a token, a token assurance level and data used to generate the token assurance level. At the time a token is issued, one or more Identification and Verification (ID&V) methods may be performed to ensure that the token is replacing a PAN that was legitimately used by a token requestor. A token assurance level may be assigned to a given token in light of the type of ID&V that is performed and the entity performing the ID&V. Different ID&Vs may result in different token assurance levels. An issuer may wish to know the level of assurance and the data used in generating the level of assurance associated with a token prior to authorizing a payment transaction that uses the token.

Abstract: A computer-implemented method for verifying cardholder authenticity when provisioning a token is provided. The method uses an authentication server system having a processor and a memory. The method includes receiving, by the processor, a payment card account identifier provided by a payment requestor. The payment card account identifier for identifying a payment account associated with a cardholder. The method also includes determining a plurality of authentication data associated with the payment requestor, and performing an authentication process using the plurality of authentication data. The authentication process is configured to determine if the payment requestor is the cardholder. The method further includes determining an assurance level associated with the authentication process. The assurance level represents a level of confidence in the authentication process.

Abstract: Embodiments of the invention are directed to methods, apparatuses, computer readable media and systems for providing, along with a token, a token assurance level and data used to generate the token assurance level. At the time a token is issued, one or more Identification and Verification (ID&V) methods may be performed to ensure that the token is replacing a PAN that was legitimately used by a token requestor. A token assurance level may be assigned to a given token in light of the type of ID&V that is performed and the entity performing the ID&V. Different ID&Vs may result in different token assurance levels. An issuer may wish to know the level of assurance and the data used in generating the level of assurance associated with a token prior to authorizing a payment transaction that uses the token.

Abstract: Embodiments of the invention are directed to methods, apparatuses, computer readable media and systems for providing, along with a token, a token assurance level and data used to generate the token assurance level. At the time a token is issued, one or more Identification and Verification (ID&V) methods may be performed to ensure that the token is replacing a PAN that was legitimately used by a token requestor. A token assurance level may be assigned to a given token in light of the type of ID&V that is performed and the entity performing the ID&V. Different ID&Vs may result in different token assurance levels. An issuer may wish to know the level of assurance and the data used in generating the level of assurance associated with a token prior to authorizing a payment transaction that uses the token.

Abstract: A computer-implemented method for verifying cardholder authenticity when provisioning a token is provided. The method uses an authentication server system having a processor and a memory. The method includes receiving, by the processor, a payment card account identifier provided by a payment requestor. The payment card account identifier for identifying a payment account associated with a cardholder. The method also includes determining a plurality of authentication data associated with the payment requestor, and performing an authentication process using the plurality of authentication data. The authentication process is configured to determine if the payment requestor is the cardholder. The method further includes determining an assurance level associated with the authentication process. The assurance level represents a level of confidence in the authentication process.

Abstract: A computer-implemented method for verifying cardholder authenticity when provisioning a token is provided. The method uses an authentication server system having a processor and a memory. The method includes receiving, by the processor, a payment card account identifier provided by a payment requestor. The payment card account identifier for identifying a payment account associated with a cardholder. The method also includes determining a plurality of authentication data associated with the payment requestor, and performing an authentication process using the plurality of authentication data. The authentication process is configured to determine if the payment requestor is the cardholder. The method further includes determining an assurance level associated with the authentication process. The assurance level represents a level of confidence in the authentication process.

Abstract: A method for confirmation of a suspect transaction includes: storing device profiles, each including a device identifier and registered biometric data; receiving a confirmation request from a third party entity including a specific device identifier and a transaction identifier and data values associated with a suspect transaction; identifying a specific device profile that includes the specific device identifier; transmitting a biometric request to the computing device related to the specific device profile, the biometric request including the transaction identifier and data values; receiving a confirmation message from the computing device including confirmation of the suspect transaction, the transaction identifier, and supplied biometric data; verifying the supplied biometric data as being equivalent to the registered biometric data in the specific device profile; and transmitting a confirmation response to the third party entity including the indicated confirmation, an indication of positive verification

Abstract: Embodiments of the invention are directed to methods, apparatuses, computer readable media and systems for providing, along with a token, a token assurance level and data used to generate the token assurance level. At the time a token is issued, one or more Identification and Verification (ID&V) methods may be performed to ensure that the token is replacing a PAN that was legitimately used by a token requestor. A token assurance level may be assigned to a given token in light of the type of ID&V that is performed and the entity performing the ID&V. Different ID&Vs may result in different token assurance levels. An issuer may wish to know the level of assurance and the data used in generating the level of assurance associated with a token prior to authorizing a payment transaction that uses the token.

Abstract: A computer-implemented method for verifying cardholder authenticity when provisioning a token is provided. The method uses an authentication server system having a processor and a memory. The method includes receiving, by the processor, a payment card account identifier provided by a payment requestor. The payment card account identifier for identifying a payment account associated with a cardholder. The method also includes determining a plurality of authentication data associated with the payment requestor, and performing an authentication process using the plurality of authentication data. The authentication process is configured to determine if the payment requestor is the cardholder. The method further includes determining an assurance level associated with the authentication process. The assurance level represents a level of confidence in the authentication process.

Abstract: Systems and methods for conducting 3-D Secure transactions on-behalf-of (OBO) merchants. In an embodiment, a payer authentication response (PARes) message indicating enrollment in the 3-D Secure OBO merchants authentication service is received from an access control server by a computer and stored. The computer later receives a purchase transaction authorization request message, determines that data of the purchase transaction authorization request message matches stored PARes message data, and then injects a UCAF into the purchase transaction authorization request message to generate an updated transaction authorization request message. The updated transaction request message is then transmitted to an issuer financial institution for 3-D Secure purchase transaction authorization processing.

Abstract: A method for authenticating a user in a payment transaction using a computing device includes: storing location data entries, each entry including a geographic location of a mobile device and a time; receiving an authorization request for a payment transaction, the request including an account identifier, location identifier, and authorization time; identifying a specific data entry where the included time is within a predetermined period of time of the authorization time; when the location included in the specific data entry is indicative of the mobile device being not present at the location of the location identifier, transmitting a request to a computing device associated with the account identifier for action by a user to prove their identity; receiving, data conveying the action taken by the user; and authenticating the user based on the received data and authentication information associated with a payment account corresponding to the account identifier.