Abstract: Embodiments include a method for configuring a token transfer device for electronic transactions. The method can include requesting, by a token transfer device, one or more tokens having specified transaction exchange value; receiving, over a network, the one or more tokens; assigning, by the token transfer device, validation parameters indicating conditions under which the one or more tokens will be accepted in a transaction; determining, by the token transfer device, that one or more of the conditions have been met based on data provided by electronic components of the token transfer device; and initiating the transaction with a point of sale system.

Abstract: Embodiments include a method for configuring a token transfer device for electronic transactions. The method can include requesting, by a token transfer device, one or more tokens having specified transaction exchange value; receiving, over a network, the one or more tokens; assigning, by the token transfer device, validation parameters indicating conditions under which the one or more tokens will be accepted in a transaction; determining, by the token transfer device, that one or more of the conditions have been met based on data provided by electronic components of the token transfer device; and initiating the transaction with a point of sale system.

Abstract: A method for processing transactions within a token transfer device, such as a smartphone or other portable electronic device. The method includes storing a transaction token having a specified transaction resource value and an associated validation parameter in the memory of the token transfer device. A transaction communication interface initiates a transaction service with a token recipient terminal and invokes a token state manager. The token state manager determines an event corresponding to the specified validation parameter by determining a transaction resource network connect activity status and by determining condition register data associated with the validation parameter. The token state manager then issues a transaction modification call based on the determined event and the validation parameter.

Abstract: A method for processing transactions within a token transfer device, such as a smartphone or other portable electronic device. The method includes storing a transaction token having a specified transaction resource value and an associated validation parameter in the memory of the token transfer device. A transaction communication interface initiates a transaction service with a token recipient terminal and invokes a token state manager. The token state manager determines an event corresponding to the specified validation parameter by determining a transaction resource network connect activity status and by determining condition register data associated with the validation parameter. The token state manager then issues a transaction modification call based on the determined event and the validation parameter.

Abstract: A method for processing transactions within a token transfer device, such as a smartphone or other portable electronic device. The method includes storing a transaction token having a specified transaction resource value and an associated validation parameter in the memory of the token transfer device. A transaction communication interface initiates a transaction service with a token recipient terminal and invokes a token state manager. The token state manager determines an event corresponding to the specified validation parameter by determining a transaction resource network connect activity status and by determining condition register data associated with the validation parameter. The token state manager then issues a transaction modification call based on the determined event and the validation parameter.

Abstract: A program product and device for processing transactions within a token transfer device, such as a smartphone or other portable electronic device. The method includes storing a transaction token having a specified transaction resource value and an associated validation parameter in the memory of the token transfer device. A transaction communication interface initiates a transaction service with a token recipient terminal and invokes a token state manager. The token state manager determines an event corresponding to the specified validation parameter by determining a transaction resource network connect activity status and by determining condition register data associated with the validation parameter. The token state manager then issues a transaction modification call based on the determined event and the validation parameter.

Abstract: A program product and device for processing transactions within a token transfer device, such as a smartphone or other portable electronic device. The method includes storing a transaction token having a specified transaction resource value and an associated validation parameter in the memory of the token transfer device. A transaction communication interface initiates a transaction service with a token recipient terminal and invokes a token state manager. The token state manager determines an event corresponding to the specified validation parameter by determining a transaction resource network connect activity status and by determining condition register data associated with the validation parameter. The token state manager then issues a transaction modification call based on the determined event and the validation parameter.

Abstract: A method for processing transactions within a token transfer device, such as a smartphone or other portable electronic device. The method includes storing a transaction token having a specified transaction resource value and an associated validation parameter in the memory of the token transfer device. A transaction communication interface initiates a transaction service with a token recipient terminal and invokes a token state manager. The token state manager determines an event corresponding to the specified validation parameter by determining a transaction resource network connect activity status and by determining condition register data associated with the validation parameter. The token state manager then issues a transaction modification call based on the determined event and the validation parameter.

Abstract: A mediation processing node computer processor updates a message. A message is received for processing by a mediation processing node computer processor. It is deduced from a declared interface of the mediation processing node computer processor that one or more message values will be updated by the mediation processing node computer processor as a result of its processing. The interface of the mediation processing node computer processor is then used to obtain the one or more updated values and the updates are then applied to the message.

Abstract: An XML digital signature mechanism for providing message integrity. A sending party serializes a source XML document into a serialized byte array, calculates the source offset and length of the array of the signed part in the serialized byte array, and calculates a source hash value using the serialized array and the source offset and length. The serialized byte array is a non-canonicalized array. The array and source hash value used to sign a part or the whole of the serialized byte array is sent to a receiving party. The receiving party calculates the target offset and length of the signed part in the serialized byte array and calculates a target hash value of the signed part by using the array and the target offset and length. The receiving party compares the target hash value and the source hash value to verify the integrity of the target XML document.

Abstract: An XML digital signature mechanism for providing message integrity. A sending party serializes a source XML document into a serialized byte array, calculates the source offset and length of the array of the signed part in the serialized byte array, and calculates a source hash value using the serialized array and the source offset and length. The serialized byte array is a non-canonicalized array. The array and source hash value used to sign a part or the whole of the serialized byte array is sent to a receiving party. The receiving party calculates the target offset and length of the signed part in the serialized byte array and calculates a target hash value of the signed part by using the array and the target offset and length. The receiving party compares the target hash value and the source hash value to verify the integrity of the target XML document.

Abstract: A mechanism is presented for merging e-mail messages into a collated file. An e-mail message and its associated responses may be accessed and collated based on a selected pattern for responses. The set of e-mails may be collated into a single document with the responses associated with the particular message to which the response is directed. Using pattern matching operations in an iterative fashion, a response may be associated with the message that elicited the response whether the original message or a previous response. The form of association may be user selectable.

Abstract: A mediation processing node computer processor updates a message. A message is received for processing by a mediation processing node computer processor. It is deduced from a declared interface of the mediation processing node computer processor that one or more message values will be updated by the mediation processing node computer processor as a result of its processing. The interface of the mediation processing node computer processor is then used to obtain the one or more updated values and the updates are then applied to the message.

Abstract: The present invention is directed to a method and system of allowing the user-defined code to be written in such a way as to be independent on the underlying transport yet still send and receive information via transport-specific artifacts. As such, a user may not be required to develop unique code for each different transport. A developer may set user-defined transport-agnostic properties and associated values without concerning an underlying transport. A deployer will provide an external mapping of those user-defined transport-agnostic properties to one or more specific transports which are to be supported. The system may allow new or different transports to be supported by the user-defined code without requiring the developer to change the user-defined code. Only the mapping information decoupled from the user-defined properties may need to be changed for different transports.

Abstract: A mechanism is presented for merging e-mail messages into a collated file. An e-mail message and its associated responses may be accessed and collated based on a selected pattern for responses. The set of e-mails may be collated into a single document with the responses associated with the particular message to which the response is directed. Using pattern matching operations in an iterative fashion, a response may be associated with the message that elicited the response whether the original message or a previous response. The form of association may be user selectable.

Abstract: A mechanism is presented for merging e-mail messages into a collated file. An e-mail message and its associated responses may be accessed and collated based on a selected pattern for responses. The set of e-mails may be collated into a single document with the responses associated with the particular message to which the response is directed. Using pattern matching operations in an iterative fashion, a response may be associated with the message that elicited the response whether the original message or a previous response. The form of association may be user selectable.

Abstract: A mechanism for caching Web services requests and responses, including testing an incoming request against the cached requests and associated responses is provided. The requests are selectively tested against the cached data in accordance with a set of policies. If a request selected hits in the cache, the response is served up from the cache. Otherwise, the request is passed to the corresponding Web-services server/application. Additionally, a set of predetermined cache specifications for generating request identifiers may be provided. The identifier specification may be autonomically adjusted by determining cache hit/cache miss ratios over the set of identifier specifications and over a set of sample requests. The set of specifications may then be sorted to reflect the performance of the respective cache specification algorithms for the current mix of requests.

Abstract: A mechanism for caching Web services requests and responses, including testing an incoming request against the cached requests and associated responses is provided. The requests are selectively tested against the cached data in accordance with a set of policies. If a request selected hits in the cache, the response is served up from the cache. Otherwise, the request is passed to the corresponding Web-services server/application. Additionally, a set of predetermined cache specifications for generating request identifiers may be provided. The identifier specification may be autonomically adjusted by determining cache hit/cache miss ratios over the set of identifier specifications and over a set of sample requests. The set of specifications may then be sorted to reflect the performance of the respective cache specification algorithms for the current mix of requests.