Abstract: Systems and methods for limiting functionality of a vehicle are described. In one example, vehicle feature modules may specify vehicle behaviors and vehicle operation is limited according to the specified behaviors. Vehicle actuators may be adjusted to limit vehicle operation according to the specified vehicle behaviors. The vehicle behaviors may apply to powertrain systems, navigation systems, climate control systems, lighting systems and other vehicle systems.

Abstract: An extensible key management system includes a developer services portal for accessing an application. The system may identify initiation via the developer services portal of an association of the application with an external API of a third party provider service and automatically obtain a sub-key for the external API from the third party provider service on behalf of a developer of the application. The sub-key may be obtained in accordance with authorization provided by a master key previously provided from the third party provider service. The system may map an association between the sub-key, the application and the external API and store the association. Upon receipt of a service call message resulting from a request from a user device executing the application, the system may identify and replace a developer API key included in the service call message with the sub-key based on the stored association.

Abstract: An extensible single point orchestration system receives service requests from applications. In dependence upon the service request a single third party provider service or multiple third party provider services is identified. When the single third party provider service is identified, the system dynamically adapts a core capability service, using a stored configuration entity, so as to set an appropriate message format and transmit a service call message to an external API of the identified single third party provider service. When multiple third party provider services are identified, the system dynamically adapts the core capability service, using another stored configuration entity, so as to set a respective appropriate message format for parallel data transmission of service call messages to each of the respective identified third party provider services and transmits the service call messages to respective external APIs of each of the third party provider services.

Abstract: An extensible single point orchestration system receives service requests from applications. In dependence upon the service request a single third party provider service or multiple third party provider services is identified. When the single third party provider service is identified, the system dynamically adapts a core capability service, using a stored configuration entity, so as to set an appropriate message format and transmit a service call message to an external API of the identified single third party provider service. When multiple third party provider services are identified, the system dynamically adapts the core capability service, using another stored configuration entity, so as to set a respective appropriate message format for parallel data transmission of service call messages to each of the respective identified third party provider services and transmits the service call messages to respective external APIs of each of the third party provider services.

Abstract: The invention concerns a method of making a payment transaction by a customer including steps of receiving, by a mobile device (402) of the customer, merchant data; transmitting, by the mobile device to a remote server (408), a payment transaction request including the merchant data; determining, by the remote server; the identity of the customer based on the request and the identity of the merchant based on the data; and implementing the payment transaction between bank accounts of the customer and the merchant.

Abstract: An extensible key management system includes a developer services portal for accessing an application. The system may identify initiation via the developer services portal of an association of the application with an external API of a third party provider service and automatically obtain a sub-key for the external API from the third party provider service on behalf of a developer of the application. The sub-key may be obtained in accordance with authorization provided by a master key previously provided from the third party provider service. The system may map an association between the sub-key, the application and the external API and store the association. Upon receipt of a service call message resulting from a request from a user device executing the application, the system may identify and replace a developer API key included in the service call message with the sub-key based on the stored association.

Abstract: An extensible single point orchestration system receives service requests from applications. In dependence upon the service request a single third party provider service or multiple third party provider services is identified. When the single third party provider service is identified, the system dynamically adapts a core capability service, using a stored configuration entity, so as to set an appropriate message format and transmit a service call message to an external API of the identified single third party provider service. When multiple third party provider services are identified, the system dynamically adapts the core capability service, using another stored configuration entity, so as to set a respective appropriate message format for parallel data transmission of service call messages to each of the respective identified third party provider services and transmits the service call messages to respective external APIs of each of the third party provider services.

Abstract: Display packaging for a product comprises first and second clear members disposed on top of each other, the first clear member including a bump-out to provide a cavity to receive the product within the cavity, the first and second clear members including peripheral edge portions; and a frame attached to the peripheral edge portions.

Abstract: An extensible key management system includes a developer services portal for accessing an application. The system may identify initiation via the developer services portal of an association of the application with an external API of a third party provider service and automatically obtain a sub-key for the external API from the third party provider service on behalf of a developer of the application. The sub-key may be obtained in accordance with authorization provided by a master key previously provided from the third party provider service. The system may map an association between the sub-key, the application and the external API and store the association. Upon receipt of a service call message resulting from a request from a user device executing the application, the system may identify and replace a developer API key included in the service call message with the sub-key based on the stored association.

Abstract: An extensible single point orchestration system receives service requests from applications. In dependence upon the service request a single third party provider service or multiple third party provider services is identified. When the single third party provider service is identified, the system dynamically adapts a core capability service, using a stored configuration entity, so as to set an appropriate message format and transmit a service call message to an external API of the identified single third party provider service. When multiple third party provider services are identified, the system dynamically adapts the core capability service, using another stored configuration entity, so as to set a respective appropriate message format for parallel data transmission of service call messages to each of the respective identified third party provider services and transmits the service call messages to respective external APIs of each of the third party provider services.

Abstract: The invention concerns a method of making a payment transaction by a customer including steps of receiving, by a mobile device (402) of the customer, merchant data; transmitting, by the mobile device to a remote server (408), a payment transaction request including the merchant data; determining, by the remote server; the identity of the customer based on the request and the identity of the merchant based on the data; and implementing the payment transaction between bank accounts of the customer and the merchant.

Abstract: The invention concerns a method of making a payment transaction by a customer including steps of receiving, by a mobile device (402) of the customer, merchant data; transmitting, by the mobile device to a remote server (408), a payment transaction request including the merchant data; determining, by the remote server, the identity of the customer based on the request and the identity of the merchant based on the data; and implementing the payment transaction between bank accounts of the customer and the merchant.

Abstract: The invention concerns a method of making an electronic payment by an electronic payment device comprising: transmitting from said electronic payment device (206) to an electronic receiving device (208, 210) a first money token (204) comprising at least data indicating an identifier of said first money token and an amount indicating a payment sum of said first money token, wherein said first money token further comprises an electronic watermark.

Abstract: The invention concerns a method of making a payment transaction by a customer including steps of receiving, by a mobile device (402) of the customer, merchant data; transmitting, by the mobile device to a remote server (408), a payment transaction request including the merchant data; determining, by the remote server, the identity of the customer based on the request and the identity of the merchant based on the data; and implementing the payment transaction between bank accounts of the customer and the merchant.

Abstract: Techniques for managing electronic payment instructions include providing a first bank with access to electronic payment instructions associated with a customer account of the first bank and providing a second bank with access to electronic payment instructions associated with a customer account of the second bank. An electronic payment instruction is received over a network from the customer of the first bank, the instruction is to pay, or receive payment from, the customer of the second bank. The electronic payment instruction is stored and sent to at least one of the first bank and the second bank to initiate payment between the customer account of the first bank and the customer account of the second bank.