Abstract:
A method for real-time invoice updating and account-to-account payment includes: receiving invoice data based on presentation of an invoice by a distributor to a recipient at a delivery location, modification of the invoice by the recipient, and acceptance of the invoice by the recipient; generating a request for payment (RFP) message based on the invoice data; transmitting the RFP message to a financial institution associated with the recipient via a financial institution of the distributor; receiving, from the financial institution associated with the distributor, a payment confirmation for the invoice based on a real-time payment from the financial institution associated with the recipient; generating reconciliation data based on the payment confirmation and the invoice data; and transmitting the reconciliation data to a computing device of the distributor and a computing device of the recipient.
Abstract:
Methods and apparatus for securing access to an encrypted personal data store on a mobile device. In some embodiments, a universal integrated circuit card (UICC) processor receives, from a mobile device processor of a mobile device having an encrypted Personal Data Store (PDS), a PDS access request associated with a mobile application, then determines that access control rules are stored in at least one access control rules database and transmits to the mobile device processor, the access control rules governing access to the data in the encrypted PDS. The process also includes the UICC processor receiving a request for a symmetric shared secret and transmitting the symmetric shared secret to the mobile device processor for use in accessing the PID of the user stored in the encrypted PDS in accordance with the access control rules.
Abstract:
Methods and systems for protecting sensitive data and applications on a mobile device. In an embodiment, a mobile device processor of a mobile device downloads, from a digital wallet server computer, a mobile wallet application including a white box software development kit (SDK) which includes code protection processes, then obfuscates, by running the code protection processes of the white box SDK, consumer financial data and consumer authentication data and stores the obfuscated consumer financial data and consumer authentication data in a regular memory of the mobile device. The process also includes protecting, by the mobile device processor running the white box SDK, sensitive applications stored in the regular memory which execute during a transaction from attack, and re-obfuscating, by the mobile device processor, at least one of the consumer financial data and the consumer authentication data according to a predetermined time interval.
Abstract:
Systems and methods are provided for enabling, providing, and managing digital identities in association with mobile devices. One example method includes determining, by a mobile device, that identity data of a user is changed, and prompting the user to identify a third party separate from the mobile device to authenticate the user. The method also includes requesting the third party to authenticate the user, and causing an authentication interface of the third party to be displayed at the mobile device where the authentication interface solicits login credentials for an account of the user at the third party. The method then includes granting, by the mobile device, access to one or more aspects of a mobile application installed at the mobile device, in response to an indication of a successful authentication of the user from the third party.
Abstract:
Systems and methods are provided for managing digital identities associated with users. One exemplary method includes receiving, at a computing device, an encrypted message from a communication device associated with a user where the message includes a changed attribute for the user. The method also includes generating a first hash of a first digital identity for the user with the changed attribute and generating a second hash of a second digital identity of the user stored in a ledger data structure. And, in response to the first hash not matching the second hash, the method then includes broadcasting a pending status of the first digital identity to a relying party for the second digital identity, and storing a certification of the changed attribute, received from the relying party in response to the pending status, based on verification of the changed attribute by the relying party.
Abstract:
Systems and methods are provided for use in enabling, providing, and managing digital identities in association with mobile communication devices. One exemplary method includes capturing an image of a physical document comprising a biometric of a user associated with the physical document, and extracting the biometric from the image and converting it to a biometric template. The method also includes capturing a biometric of the user and comparing it to the biometric template. The method then includes, when the captured biometric matches the biometric template, transmitting a message to an identification provider comprising at least the image of the physical document and the biometric template, whereby the biometric template is verified against a repository, and binding data representative of the mobile communication device, a mobile application included therein, and the biometric template and/or the captured biometric of the user into a token.
Abstract:
Systems and methods are provided for use in providing digital identities for users. One exemplary method includes receiving, at a card device, an authentication request and a captured first biometric of the user, from a communication device associated with the user, and comparing the first biometric and a first biometric reference at the card device, when the first biometric reference is stored in at the card device. The method also includes capturing, at the card device, a second biometric of the user and comparing the second biometric to a second biometric reference stored at the card device. The method further includes compiling a response to the authentication request including a first indicator associated with the comparison of the first biometric to the first biometric reference and a second indicator associated with the comparison of the second biometric to the second biometric reference, and transmitting the response to the communication device.
Abstract:
Methods and systems for permitting sensitive cardholder data to be securely stored in a regular storage element of a smart transaction card. In an embodiment, a transaction card processor of the smart transaction card installs a security application compatible with the operating system of the smart transaction card and that includes a white box cardlet. The transaction card processor uses a code protection process of the white box cardlet to obfuscate biometric reference template data stored in the regular memory of a biometric sensor, next stores the obfuscated biometric reference template data in the regular memory, and then re-obfuscates the biometric reference template data at a predetermined time interval.
Abstract:
Methods and systems for authenticating both a browser-based user mobile device and the user in association with an online transaction. In an embodiment, the process includes receiving, by a cloud-based authentication service computer, a user authentication request from a user mobile device. A mobile transaction application determines that the user and the entity involved in the online transaction are enrolled in a cloud-based authentication service, identifies a user data structure and a user profile, determines that the received user authentication data and user mobile device identification data matches data stored in the user profile, and determines that a requirement of the entity is satisfied. The mobile transaction application then transmits a positive user authentication message to an entity computer.
Abstract:
An open, on-device Cardholder Verification Method (“CVM”) controller may receive CVM policies from issuers and store the policies in a database. The open, on-device CVM controller may then receive a request from a remote mobile device, and automatically determine at least one issuer associated with the request. Appropriate CVM policies may be retrieved and transmitted to the remote mobile device. An open, on-device CVM application executing on the mobile device may then receive a CVM authentication request, associated with a payment token, from a payment application. Responsive to the authentication request, a CVM policy may be accessed based on the payment token. It may then be arranged for an authenticator of the mobile device to authenticate a user in accordance with the CVM policy. When the user is authenticated, an authentication success indication may be sent from the open, on-device CVM application to the payment application.