Packages | |
package | api |
package | content |
package | entities |
package | payment |
package | triggers |
Classes | |
class | CommerceAppMessage |
class | CommerceEvent |
class | CommerceListener |
class | CommerceManager |
class | CommerceMessage |
class | CommerceResponse |
class | Status |
Provides the interface for all communication between the payment terminal and Android applications.
Sending Messages:
The developer must retrieve an instance of CommerceManager, and then open a session passing in the proper listener.
The developer must create an instance of the CommerceMessage object that represents the specific message they want to send, allowing any kind of communication with the companion as desired.
The developer will call send() on the CommerceMessage object, receiving an immediate status regarding the ability of the service to transmit the message.
The developer will receive the response on the registered broadcast receiver.
Receiving Messages:
Apps will receive messages from the terminal using a BroadcastReceiver. The broadcast receiver for messages from apps to the terminal must be configured with the following manifest parameters, per AndroidManifestReceiver. Additional receiver attributes are optional.
Following is a list of the objects that are necessary to integrate a POS application. This includes basket-related functionality, but will be expanded in the future to handle CP Application responses and transaction modifications.
This document is the confidential property of Verifone, Inc. Any reproduction or distribution of this document, in whole or in part, or the disclosure of any of the information contained herein, without the prior written consent of Verifone, Inc. is prohibited. This document and any supplemental material supplied as part of any review must be returned to Verifone, Inc. upon request. Notice: This document may go through material revisions over time. While the Company will make every effort to keep readers updated as changes occur, care must be taken by the reader to make sure they are reading the latest version. Version numbers appear in the title page and revision history page of this document. All rights reserved. Verifone, the Verifone logo are either trademarks or registered trademarks of Verifone in the United States and/or other countries. All other trademarks or brand names are properties of their respective holders.