Abstract

A method includes receiving, at a native application, access credential data and providing the access credential data from the native application to a headless browser. The method also includes initiating a secured connection from the headless browser to a remote server that hosts a website. The remote server supports access to secured data without relying on an application programming interface. The method also includes sending, by the headless browser via the secured connection, the access credential data to the remote server. The method also includes receiving first web page data of the website from the remote server via the secured connection and parsing the first web page data to identify user-specific data. The method further includes receiving, by the headless browser via the secured connection, at least a portion of the secured data.

IPC Classes  ?

• H04W 12/08 - Access security
• G06Q 40/02 - Banking, e.g. interest calculation or account maintenance
• H04B 1/3827 - Portable transceivers
• H04L 9/40 - Network security protocols
• H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
• H04W 12/06 - Authentication
• H04W 12/086 - Access security using security domains

Abstract

Systems, methods, and computer-readable storage devices to enable virtual API technology embodied in an SDK for use within a mobile application, a mobile payment wallet, or a mobile operating system.

IPC Classes  ?

• H04L 9/40 - Network security protocols
• G06F 16/953 - Querying, e.g. by the use of web search engines
• G06F 16/957 - Browsing optimisation, e.g. caching or content distillation
• G06Q 20/36 - Payment architectures, schemes or protocols characterised by the use of specific devices using electronic wallets or electronic money safes
• H04L 67/01 - Protocols
• H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

Systems, methods, and computer-readable storage devices to enable secured data access from a mobile device executing a native mobile application and a headless browser are disclosed.

IPC Classes  ?

• G06F 9/54 - Interprogram communication
• G06Q 20/10 - Payment architectures specially adapted for electronic funds transfer [EFT] systemsPayment architectures specially adapted for home banking systems
• G06Q 40/02 - Banking, e.g. interest calculation or account maintenance
• H04L 67/141 - Setup of application sessions
• G06F 16/957 - Browsing optimisation, e.g. caching or content distillation
• H04L 67/10 - Protocols in which an application is distributed across nodes in the network
• H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
• H04L 67/125 - Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
• H04L 67/04 - Protocols specially adapted for terminals or networks with limited capabilitiesProtocols specially adapted for terminal portability
• G06Q 20/40 - Authorisation, e.g. identification of payer or payee, verification of customer or shop credentialsReview and approval of payers, e.g. check of credit lines or negative lists
• G06Q 20/32 - Payment architectures, schemes or protocols characterised by the use of specific devices using wireless devices
• G06F 40/221 - Parsing markup language streams
• H04L 67/53 - Network services using third party service providers
• H04L 67/566 - Grouping or aggregating service requests, e.g. for unified processing

Abstract

A method includes receiving, at a native application, access credential data and providing the access credential data from the native application to a headless browser. The method also includes initiating a secured connection from the headless browser to a remote server that hosts a website. The remote server supports access to secured data without relying on an application programming interface. The method also includes sending, by the headless browser via the secured connection, the access credential data to the remote server. The method also includes receiving first web page data of the website from the remote server via the secured connection and parsing the first web page data to identify user-specific data. The method further includes receiving, by the headless browser via the secured connection, at least a portion of the secured data.

IPC Classes  ?

• H04W 12/08 - Access security
• G06Q 40/02 - Banking, e.g. interest calculation or account maintenance
• H04B 1/3827 - Portable transceivers
• H04L 9/40 - Network security protocols
• H04W 12/06 - Authentication
• H04W 12/086 - Access security using security domains
• H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

Systems, methods, and computer-readable storage devices to enable virtual API technology embodied in an SDK for use within a mobile application, a mobile payment wallet, or a mobile operating system.

IPC Classes  ?

• H04L 9/40 - Network security protocols
• G06F 16/953 - Querying, e.g. by the use of web search engines
• G06F 16/957 - Browsing optimisation, e.g. caching or content distillation
• G06Q 20/36 - Payment architectures, schemes or protocols characterised by the use of specific devices using electronic wallets or electronic money safes
• H04L 67/01 - Protocols
• H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

Systems, methods, and computer-readable storage devices to enable secured data access from a mobile device executing a native mobile application that operates in connection with a server executing a headless browser are disclosed.

IPC Classes  ?

• H04W 12/30 - Security of mobile devicesSecurity of mobile applications
• H04W 12/08 - Access security
• H04L 29/06 - Communication control; Communication processing characterised by a protocol
• G06F 16/955 - Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
• G06F 9/54 - Interprogram communication
• H04W 12/03 - Protecting confidentiality, e.g. by encryption
• H04W 12/06 - Authentication

Abstract

Systems, methods, and computer-readable storage devices to enable secured data access from a mobile device executing a native mobile application that operates in connection with a server executing a headless browser are disclosed.

IPC Classes  ?

• H04W 12/00 - Security arrangementsAuthenticationProtecting privacy or anonymity
• H04W 12/06 - Authentication
• H04W 12/08 - Access security

Abstract

Systems, methods, and computer-readable storage devices to enable secured data access from a mobile device executing a native mobile application that operates in connection with a server executing a headless browser are disclosed.

IPC Classes  ?

• H04W 12/00 - Security arrangementsAuthenticationProtecting privacy or anonymity
• H04W 12/06 - Authentication
• H04W 12/08 - Access security

Abstract

Systems, methods, and computer-readable storage devices that enable secured data access from a mobile device executing a native mobile application and a headless browser. The technology includes interactions between an API, a secure connection, a headless browser, that utilize one or more of web site data, fingerprint data file locations and additional web page data.

IPC Classes  ?

• G06F 9/54 - Interprogram communication
• G06Q 20/10 - Payment architectures specially adapted for electronic funds transfer [EFT] systemsPayment architectures specially adapted for home banking systems
• G06Q 40/02 - Banking, e.g. interest calculation or account maintenance
• H04L 67/141 - Setup of application sessions
• G06F 16/957 - Browsing optimisation, e.g. caching or content distillation
• H04L 67/10 - Protocols in which an application is distributed across nodes in the network
• H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
• H04L 67/125 - Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
• H04L 67/04 - Protocols specially adapted for terminals or networks with limited capabilitiesProtocols specially adapted for terminal portability
• G06Q 20/40 - Authorisation, e.g. identification of payer or payee, verification of customer or shop credentialsReview and approval of payers, e.g. check of credit lines or negative lists
• G06Q 20/32 - Payment architectures, schemes or protocols characterised by the use of specific devices using wireless devices
• G06F 40/221 - Parsing markup language streams
• H04L 67/53 - Network services using third party service providers
• H04L 67/566 - Grouping or aggregating service requests, e.g. for unified processing
• G06F 40/106 - Display of layout of documentsPreviewing

Abstract

Systems, methods, and computer-readable storage devices to enable secured data access from a mobile device executing a native mobile application that operates in connection with a server executing a headless browser are disclosed.

IPC Classes  ?

• H04W 12/00 - Security arrangementsAuthenticationProtecting privacy or anonymity
• H04W 12/30 - Security of mobile devicesSecurity of mobile applications
• H04W 12/08 - Access security
• H04L 29/06 - Communication control; Communication processing characterised by a protocol
• G06F 16/955 - Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
• G06F 9/54 - Interprogram communication
• H04W 12/03 - Protecting confidentiality, e.g. by encryption
• H04W 12/06 - Authentication

Abstract

Systems, methods, and computer-readable storage devices to enable virtual API technology embodied in an SDK for use within a mobile application, a mobile payment wallet, or a mobile operating system.

IPC Classes  ?

• H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
• G06F 16/957 - Browsing optimisation, e.g. caching or content distillation
• H04L 67/01 - Protocols
• H04L 9/40 - Network security protocols
• G06Q 20/36 - Payment architectures, schemes or protocols characterised by the use of specific devices using electronic wallets or electronic money safes
• G06F 16/953 - Querying, e.g. by the use of web search engines

Abstract

A method includes receiving, at a native application, access credential data and providing the access credential data from the native application to a headless browser. The method also includes initiating a secured connection from the headless browser to a remote server that hosts a website. The remote server supports access to secured data without relying on an application programming interface. The method also includes sending, by the headless browser via the secured connection, the access credential data to the remote server. The method also includes receiving first web page data of the website from the remote server via the secured connection and parsing the first web page data to identify user-specific data. The method further includes receiving, by the headless browser via the secured connection, at least a portion of the secured data.

IPC Classes  ?

• H04W 12/08 - Access security
• H04L 9/40 - Network security protocols
• G06Q 40/02 - Banking, e.g. interest calculation or account maintenance
• H04W 12/06 - Authentication
• H04W 12/086 - Access security using security domains
• H04B 1/3827 - Portable transceivers
• H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

Embodiments describe receiving a user input identifying a name associated with the website. A directory server receives a request for application programming interface (API) fingerprint data associated with the name. In response to receiving, from the directory server, a response indicating that no API fingerprint data has been found for the name, a secured connection is initiated via the wireless transceiver from a headless browser of the native application to the remote server. First web page data of the website is received from the remote server via the secured connection and the first web page data parsed to identify first locations of one or more elements of the website. A first application programming interface (API) fingerprint data is generated indicating a mapping between the one or more elements of the website and the native application and the first API fingerprint data is sent to the directory server.

IPC Classes  ?

• G06F 9/54 - Interprogram communication
• G06Q 20/10 - Payment architectures specially adapted for electronic funds transfer [EFT] systemsPayment architectures specially adapted for home banking systems
• G06Q 40/02 - Banking, e.g. interest calculation or account maintenance
• H04L 29/08 - Transmission control procedure, e.g. data link level control procedure
• G06F 16/957 - Browsing optimisation, e.g. caching or content distillation
• G06Q 20/40 - Authorisation, e.g. identification of payer or payee, verification of customer or shop credentialsReview and approval of payers, e.g. check of credit lines or negative lists
• G06Q 20/32 - Payment architectures, schemes or protocols characterised by the use of specific devices using wireless devices
• G06F 40/221 - Parsing markup language streams
• G06F 40/106 - Display of layout of documentsPreviewing

Abstract

A method includes receiving, at a native application, access credential data and providing the access credential data from the native application to a headless browser. The method also includes initiating a secured connection from the headless browser to a remote server that hosts a website. The remote server supports access to secured data without relying on an application programming interface. The method also includes sending, by the headless browser via the secured connection, the access credential data to the remote server. The method also includes receiving first web page data of the website from the remote server via the secured connection and parsing the first web page data to identify user-specific data. The method further includes receiving, by the headless browser via the secured connection, at least a portion of the secured data.

IPC Classes  ?

• H04W 12/08 - Access security
• H04L 29/06 - Communication control; Communication processing characterised by a protocol
• G06Q 40/02 - Banking, e.g. interest calculation or account maintenance
• H04W 12/06 - Authentication
• H04B 1/3827 - Portable transceivers
• H04L 29/08 - Transmission control procedure, e.g. data link level control procedure

Abstract

Systems, methods, and computer-readable storage devices to enable secured data access from a mobile device executing a native mobile application and a headless browser are disclosed. In a particular aspect, a mobile device includes a wireless transceiver, a processor, a display device, and a memory storing instructions executable by the processor to perform operations. The operations enable read and write access to secured data by the mobile device.

IPC Classes  ?

• H04W 12/08 - Access security
• H04L 29/06 - Communication control; Communication processing characterised by a protocol
• H04W 12/06 - Authentication
• G06Q 40/02 - Banking, e.g. interest calculation or account maintenance
• H04B 1/3827 - Portable transceivers
• H04L 29/08 - Transmission control procedure, e.g. data link level control procedure