Abstract: A chip card payment processor interface component exposes a plurality of different interfaces for a plurality of different chip card payment processors. A chip card peripheral device interface component exposes a plurality of different chip card peripheral device interfaces for a plurality of different chip card peripheral devices. A payment services component can thus interact with the plurality of different chip card peripheral devices in conducting a transaction, and can also interact with a plurality of different chip card payment processors to authenticate and validate the transaction.

Abstract: Architecture that employs a software development kit and an add-in model to collect payment data and communicate with payment processors in a point-of-sale (POS) application to meet new requirements in new markets. Data gathered from an add-in and from the POS application can be combined and then communicated to the payment processor. The payment method can be determined and payment processing routed to different payment processors based on data and schema of data collected is also described. An add-in can also programmatically obtain information from the POS application information about a transaction and authorize a payment. A payment collecting/processing API is the interface between the POS application tender logic and payment collecting/processing logic and defines how a payment collecting/processing add-in interacts with the POS application.

Abstract: A chip card payment processor interface component exposes a plurality of different interfaces for a plurality of different chip card payment processors. A chip card peripheral device interface component exposes a plurality of different chip card peripheral device interfaces for a plurality of different chip card peripheral devices. A payment services component can thus interact with the plurality of different chip card peripheral devices in conducting a transaction, and can also interact with a plurality of different chip card payment processors to authenticate and validate the transaction.

Abstract: A point-of-sale (POS) module and associated methods are described for performing a transaction involving a check. The POS module interacts with one or more add-in modules. Each add-in module is associated with a particular method for processing a payment using a check. Accordingly, the POS module can accommodate multiple different workflows by plugging in appropriate add-in modules.

Abstract: A method and system for providing an extensible framework for a POS application is provided. A POS application may be extended using a payment format add-in, a workflow add-in, a financial services provider add-in, or a combination of add-ins. A payment format add-in provides support for a payment format not included in the payment formats built into the POS application. A workflow add-in provides a configurable workflow that can be used to extend a built-in payment format or a payment format add-in. A financial services provider add-in provides support for interacting with a financial services provider for which the POS application does not provide built-in support. Each add-in can implement, for example, logic for processing a payment transaction, a portion of a payment transaction, and configuring steps for processing a payment transaction.

Abstract: A method and system for providing an extensible framework for a POS application is provided. A POS application may be extended using a payment format add-in, a workflow add-in, a financial services provider add-in, or a combination of add-ins. A payment format add-in provides support for a payment format not included in the payment formats built into the POS application. A workflow add-in provides a configurable workflow that can be used to extend a built-in payment format or a payment format add-in. A financial services provider add-in provides support for interacting with a financial services provider for which the POS application does not provide built-in support. Each add-in can implement, for example, logic for processing a payment transaction, a portion of a payment transaction, and configuring steps for processing a payment transaction.

Abstract: A method and system for providing an extensible framework for a POS application is provided. A POS application may be extended using a payment format add-in, a workflow add-in, a financial services provider add-in, or a combination of add-ins. A payment format add-in provides support for a payment format not included in the payment formats built into the POS application. A workflow add-in provides a configurable workflow that can be used to extend a built-in payment format or a payment format add-in. A financial services provider add-in provides support for interacting with a financial services provider for which the POS application does not provide built-in support. Each add-in can implement, for example, logic for processing a payment transaction, a portion of a payment transaction, and configuring steps for processing a payment transaction.

Abstract: Architecture that employs a software development kit and an add-in model to collect payment data and communicate with payment processors in a point-of-sale (POS) application to meet new requirements in new markets. Data gathered from an add-in and from the POS application can be combined and then communicated to the payment processor. The payment method can be determined and payment processing routed to different payment processors based on data and schema of data collected is also described. An add-in can also programmatically obtain information from the POS application information about a transaction and authorize a payment. A payment collecting/processing API is the interface between the POS application tender logic and payment collecting/processing logic and defines how a payment collecting/processing add-in interacts with the POS application.

Abstract: A method and system for providing an extensible framework for a POS application is provided. A POS application may be extended using a payment format add-in, a workflow add-in, a financial services provider add-in, or a combination of add-ins. A payment format add-in provides support for a payment format not included in the payment formats built into the POS application. A workflow add-in provides a configurable workflow that can be used to extend a built-in payment format or a payment format add-in. A financial services provider add-in provides support for interacting with a financial services provider for which the POS application does not provide built-in support. Each add-in can implement, for example, logic for processing a payment transaction, a portion of a payment transaction, and configuring steps for processing a payment transaction.

Abstract: A point-of-sale (POS) module and associated methods are described for performing a transaction involving a check. The POS module interacts with one or more add-in modules. Each add-in module is associated with a particular method for processing a payment using a check. Accordingly, the POS module can accommodate multiple different workflows by plugging in appropriate add-in modules.