CloverConnector

Clover Connector and Clover Connector Listener wrapper for easy .NET event consumption of standard Clover API. This is an alternate access Ease of Use layer wrapping the standard Clover Connector API for designs that would prefer to consume an Event model API. Standard CloverConnector API calls are made to this object The single Message event can be subscribed to for a central message handler design. All messages raise the common Message event. Individual response events can be subscribed to in order to handle specific messages. All messages raise their own custom event.

Create an empty CloverEventConnector Attach an existing ICloverConnector object or create a new on to use this CloverEventConnector

Construct a CloverEventConnector from an existing CloverConnector object that has already been setup

Existing CloverConnector SDK object managed by the POS

Attach an existing CloverConnector to this CloverEventConnector as the one and only CloverConnector SDK object

Catch-all event signal raised by every ICloverConnectorListener handler in addition to their custom event to enable a central Message Handling pattern The Message event is raised after the custom event, and you may set the CloverEventArgs.handled flag if you wish to do either/or message processing

Device Activity message - UI screen has changed and is being shown

Device Activity message - UI screen is changing and current screen is being hidden

There was an error from the device or SDK layer, usually directly related to the last call

PreAuth call has completed with these details (success or failure)

Auth call has completed with these details (success or failure)

Tip Adjust call has completed with these details (success or failure)

Capture PreAuth call has completed with these details (success or failure)

Increment PreAuth call has completed with these details (success or failure)

The customer has signed for the payment, the POS needs to confirm the signature so the payment can continue (eg Cashier compares signature to card as appropriate)

The payment was detected as a possible duplicate or the device is offline, the POS needs to confirm the payment is acceptable to continue (eg Cashier confirms it isn't a duplicate payment and should be processed)

Closeout call has completed with these details (success or failure)

Sale call has completed with these details (success or failure)

Manual Refund call has completed with these details (success or failure)

Refund call has completed with these details (success or failure)

Customer added a tip to the order on the device screen

Void Payment call has completed with these details (success or failure)

Void Payment Refund call has completed with these details (success or failure)

A Clover Device was connected to the SDK and the SDK can see it

A Clover Device was connected to and initialized by the SDK and is ready to use

An attached Clover Device lost connection to the SDK and cannot be used (device power cycled, unplugged, network connection lost, etc.)

Vault Card call has completed with these details (success or failure)

List of Pending Payments on the device in need of transmitting to server (ie Payments taken and queued for later processing while device was offline / in forced offline mode)

Read Card Data call has completed with these details (success or failure)

Device wants a receipt printed for Manual Refund (ie in POS Print mode)

Device wants a receipt printed for Manual Refund Declined (ie in POS Print mode)

Device wants a receipt printed for a Payment (ie in POS Print mode)

Device wants a receipt printed for a Payment Declined (ie in POS Print mode)

Device wants a receipt printed for a Payment (ie in POS Print mode)

Device wants a receipt printed for a Refunded Payment (ie in POS Print mode)

Device wants a receipt printed for a Payment (ie in POS Print mode)

Print Job status details call has completed with these details (success or failure)

Custom Activity call has completed with these details (success or failure)

Response to a Retrieve Device Status with current status (Idle, Busy, etc.)

Custom Activity user code on the Device sent a custom message through the SDK to the POS

Reset Device call has completed with these details (success or failure)

Retrieve Payment call has completed with these payment details (success or failure)

Print Job Status call has completed with these details (success or failure)

Display Receipt Options call has completed with these details (success or failure)

InvalidStateTransition event has occurred on the device

Base class for all CloverConnectorListener event messages

The actual Clover ICloverConnectorLisener callback method that raised this event. Especially usful when using the central Message Handler pattern.

The ICloverConnector object associated with this ICloverConnectorListener event message (ie the device SDK object that sent this message)

Flag to allow user code to specify whether it handled this message already when consuming both specific API and the catch-all Message events. This value is always ignored by the SDK

All the possible Clover Connector Listener message names as a reference enum

Factory to create an instance of the CloverConnector.

Factory to create an instance of the CloverConnector

Object that conveys the required information used by the connector. Usually a USBCloverDeviceConfiguration (USB connection) or WebSocketCloverDeviceConfiguration (Network/SNPD connection) Initialized instance conforming to the ICloverConnector

Create a USB configured connection CloverConnector to a Clover Device running USB Pay Display (UsbPD) Convenience wrapper around creating a USBCloverDeviceConfiguration object and calling CloverConnectorFactory.createICloverConnector

Application ID for server reporting Point of Sale name for server reporting Station ID / serial number for server reporting Turn logging on or off

Create a WebSockect configured connection CloverConnector to a Clover Device running Secure Network Pay Display (SNPD) Convenience wrapper around creating a WebSocketCloverDeviceConfiguration object and calling CloverConnectorFactory.createICloverConnector

Clover Device Secure Network Pay Display (SNPD) network address, usually similar to "https://192.168.0.1:1234/remote_pay" Application ID for server reporting Point of Sale name for server reporting Station ID / serial number for server reporting Previous paired auth token to allow quick reconnection without initiating antoerh pairing. Blank value, invalid or expired token will initiate a new pairing Delegate method called with temporary pairing code to enter on device, like `6341` - display to user to enter on Clover Device to complete pairing Delegate method called with reconnection auth token when pairing has succeeded Delegate method called during pairing flow transitions Turn logging on or off

Used for generating a unique string of the length specified Uses the linear congruential generator (LCG) algorithm in conjunction with the .NET RNGCryptoServiceProvider class.

Generates the random string.

The length.

The main CloverConnector API for connecting to Clover Payment Devices, created via a CloverConnectorFactory transport setup call

A copy of the current CloverConnector MerchantInfo from the DeviceReady message

The Configured Transport's Title, indicating USB, WebSocket, etc. in a display friendly format

The Configured Transport's Summary, intended to be the web connection string or similar info as appropriate

SDK identification for reporting

set to true, so that when request responses are processed, the Clover Mini won't show default messages/ThankYou/Welcome screens. Set to false to allow the default message flow that is built into the CloverConnector.

Holds the current connection state

CloverConnector constructor

A CloverDeviceConfiguration object; TestDeviceConfiguration can be used for testing

Initialize the connector with a given configuration

Sale method, aka "purchase"

A SaleRequest object containing basic information needed for the transaction Status code, 0 for success, -1 for failure (need to use pre-defined constants)

If signature is captured during a Sale, this method accepts the signature as entered

If signature is captured during a Sale, this method rejects the signature as entered

Auth method to obtain an Auth. While a Pre-Auth can also be accomplished by setting the IsPreAuth flag to true, the PreAuthRequest is the preferred request type. PreAuth functionality was retained for backward compatibility

PreAuth method to obtain a PreAuth.

Capture a previous Auth. Note: Should only be called if request's PaymentID is from an AuthResponse

Increment a previous Auth. Note: Should only be called if request's PaymentID is from an AuthResponse

Adjust the tip for a previous Auth. Note: Should only be called if request's PaymentID is from an AuthResponse

Void a transaction, given a previously used order ID and/or payment ID TBD - defining a payment or order ID to be used with a void without requiring a response from Sale()

A VoidRequest object containing basic information needed to void the transaction Status code, 0 for success, -1 for failure (need to use pre-defined constants)

Refund a specific payment

Manual refund method, aka "naked credit"

A ManualRefundRequest object Status code, 0 for success, -1 for failure (need to use pre-defined constants)

Send a request to the server to closeout all orders.

Send a request to the mini to reset. This can be used if the device gets into a non-recoverable state.

Show a message on the Clover Mini screen

Return the device to the Welcome Screen

Show the thank you screen on the device

This method provides a way to control the default screen flow on the device, for instances where it makes sense to display some combination of message/thankyou/welcome screens with configurable timing between them

Vault Card information and payment token

Retrieve Card Data

Show the customer facing receipt option screen for the specified Payment.

Show the DisplayOrder on the device. Replaces the existing DisplayOrder on the device.

Remove the DisplayOrder from the device.

Request a list of pending payments from the device. Pending payments are payments taken offline that have not yet been sent to the server

Invoke the InputOption on the device

Display receipt options for a Credit, Refund, or Payment

The DisplayReceiptOptionsRequest details

Set the Loyalty API's current customer info

These are the methods to implement for intercepting messages that are sent from a Clover device.

Called when the Clover device transitions to a new screen or activity. The CloverDeviceEvent passed in will contain an event type, a description, and a list of available InputOptions.

The CloverDeviceEvent event.

Called when the Clover device transitions away from a screen or activity. The CloverDeviceEvent passed in will contain an event type and description. Note: The start and end events are not guaranteed to process in order. The event type should be used to make sure these events are paired.

The CloverDeviceEvent event.

Called when an error occurs while trying to send messages to the Clover device.

The CloverDeviceErrorEvent event.

Called in response to a PreAuth() request. Note: The boolean IsPreAuth flag in the PreAuthResponse indicates whether CapturePreAuth() can be called for the returned Payment. If the IsPreAuth flag is false and the IsAuth flag is true, then the payment gateway coerced the PreAuth() request to an Auth. The payment will need to be voided or it will be automatically captured at closeout.

The PreAuthResponse details.

Called in response to an Auth() request. Note: An Auth transaction may come back as a final Sale, depending on the payment gateway. The AuthResponse has a boolean IsAuth flag that indicates whether the Payment can still be tip-adjusted.

The AuthResponse to the transaction request.

Called in response to a tip adjustment for an Auth transaction. Contains the TipAmount if successful.

The TipAdjustAuthResponse to the transaction request.

Called in response to a CapturePreAuth() request. Contains the new Amount and TipAmount if successful.

The CapturePreAuthResponse to the transaction request.

Called in response to an IncrementPreAuth() request. Contains the authorization if successful.

The IncrementPreAuthResponse to the transaction

Called when the Clover device requests verification for a user's on-screen signature. The Payment and Signature will be passed in.

The VerifySignatureRequest.

Called when the Clover device encounters a Challenge at the payment gateway and requires confirmation. A Challenge is triggered by a potential duplicate Payment (DUPLICATE_CHALLENGE) or an offline Payment (OFFLINE_CHALLENGE). The device sends an OnConfirmPaymentRequest() asking the merchant to reply by sending either an AcceptPayment() or RejectPayment() call. Note: Duplicate Payment Challenges are raised when multiple Payments are made with the same card type and last four digits within the same hour. For this reason, we recommend that you do not programmatically call CloverConnector.RejectPayment() on all instances of DUPLICATE_CHALLENGE. For more information, see {@link https://docs.clover.com/build/working-with-challenges/|Working with Challenges}.

The ConfirmPaymentRequest for confirmation.

Called in response to a Closeout() request.

The CloseoutResponse details for the transaction request.

Called at the completion of a Sale() request. The SaleResponse contains a {@see com.clover.remote.client.messages.ResultCode} and a Success boolean. A successful Sale transaction will also have the Payment object, which can be for the full or partial amount of the Sale request. Note: A Sale transaction my come back as a tip-adjustable Auth, depending on the payment gateway. The SaleResponse has a boolean IsSale flag that indicates whether the Sale is final, or will be finalized during closeout.

The SaleResponse details for the transaction request.

Called in response to a ManualRefund() request. Contains a {@see com.clover.remote.client.messages.ResultCode} and a Success boolean. If successful, the ManualRefundResponse will have a Credit object associated with the relevant Payment information.

The ManualRefundResponse details for the transaction request.

Called in response to a RefundPayment() request. Contains a {@see com.clover.remote.client.messages.ResultCode} and a Success boolean. The response to a successful transaction will contain the Refund, which includes the original paymentId as a reference.

The RefundPaymentResponse details for the transaction request.

Called in response to a VoidPaymentRefund() request with results.

Called when a customer selects a tip amount on the Clover device's screen.

The TipAddedMessage.

Called in response to a VoidPayment() request. Contains a {@see com.clover.remote.client.messages.ResultCode} and a Success boolean. If successful, the response will also contain the paymentId for the voided Payment.

The VoidPaymentResponse details for the transaction request.

Called when the Clover device is initially connected, but not ready to communicate.

Called when the Clover device is ready to communicate and respond to requests.

The MerchantInfo details to associate with the device.

Called when the Clover device is disconnected from the CloverConnector or not responding.

Called in response to a VaultCard() request. Contains a {@see com.clover.remote.client.messages.ResultCode} and a Success boolean. If successful, the response will contain a VaultedCard object with a token value that's unique for the card and merchant. The token can be used for future Sale() and Auth() requests.

The VaultCardResponse details for the request.

Called in response to a RetrievePendingPayment() request.

The RetrievePendingPaymentsResponse details for the request.

Called in response to a ReadCardData() request. Contains card information (specifically Track 1 and Track 2 card data).

The ReadCardDataResponse details for the request.

Called when a user requests a paper receipt for a Manual Refund. Will only be called if DisablePrinting = true on the ManualRefund() request.

A callback that asks the POS to print a receipt for a ManualRefund. Contains a Credit object.

Called when a user requests a paper receipt for a declined Manual Refund. Will only be called if DisablePrinting = true on the ManualRefund() request.

The PrintManualRefundDeclineReceiptMessage.

Called when a user requests a paper receipt for a Payment. Will only be called if DisablePrinting = true on the Sale(), Auth(), or PreAuth() request.

The PrintPaymentReceiptMessage details.

Called when a user requests a paper receipt for a declined Payment. Will only be called if DisablePrinting = true on the Sale(), Auth(), or PreAuth() request.

The PrintPaymentDeclineReceiptMessage details.

Called when a user requests a merchant copy of a Payment receipt. Will only be called if DisablePrinting = true on the Sale(), Auth(), or PreAuth() request.

The PrintPaymentMerchantCopyReceiptMessage details.

Called when a user requests a paper receipt for a Payment Refund. Will only be called if DisablePrinting = true on the Sale(), Auth(), PreAuth() or ManualRefund() request.

The PrintRefundPaymentReceiptMessage details.

Called in response to a RetrievePrintJobStatus() request.

The PrintJobStatusResponse details for the request.

Called in response to a RetrievePrinters() request.

The RetrievePrintersResponse details for the request.

Called when a Custom Activity finishes normally.

The CustomActivityResponse.

Called in response to a RetrieveDeviceStatus() request.

The RetrieveDeviceStatusResponse details for the request.

Called when a Custom Activity sends a message to the POS.

The MessageFromActivity details.

Called in response to a ResetDevice() request.

The ResetDeviceResponse details for the request.

Called in response to a RetrievePayment() request.

The RetrievePaymentResponse details for the request.

Called in response to a RetrievePrintJobStatus() request.

The PrintJobStatusResponse details for the request.

Called in response to a DisplayReceiptOptions request.

The DisplayReceiptOptionsResponse details for the response.

Called to notify the Point of Sale that a call was invalid in the current context or an internal state change failed.

Called when Loyalty API sends customer identifying data for a loyalty data type subscribed to in CloverConnector.RegisterForCustomerProvidedData()

The CustomerProvidedDataEvent containing type and data payload, like PHONE, 555-1212 in type-specific custom encoding

This is a default implementation of the ICloverConnectorListener that can be used for quickly creating applications by simply overriding the appropriate listener method(s) needed for testing a particular remote call. Also see the CloverEventConnector for another option to receive events instead of overriding the class and receiving method calls

The CloverConnector API serves as the interface for connecting to a Clover device. This document defines the available methods.

Initializes the connection and starts communication with the Clover device. This method is called after the connector has been created and listeners have been added to it. It must be called before any other method (other than those that add or remove listeners).

Adds a Clover Connector listener.

The connection listener.

Removes a Clover Connector listener.

The connection listener.

Requests a Sale transaction (purchase).

A SaleRequest object containing basic information needed for the transaction.

If a signature is captured during a transaction, this method accepts the signature as entered.

The accepted VerifySignatureRequest the device passed to OnVerifySignatureRequest().

If a signature is captured during a transaction, this method rejects the signature as entered.

The rejected VerifySignatureRequest the device passed to OnVerifySignatureRequest().

If Payment confirmation is required during a transaction due to a Challenge, this method accepts the Payment. A Challenge may be triggered by a potential duplicate Payment or an offline Payment.

The Payment to accept.

If Payment confirmation is required during a transaction due to a Challenge, this method rejects the Payment. A Challenge may be triggered by a potential duplicate Payment or an offline Payment.

The Payment to accept. The Challenge that resulted in Payment rejection.

Requests an Auth transaction. The tip for an Auth can be adjusted through the TipAdjustAuth() call until the batch Closeout is processed.

The AuthRequest details.

Initiates a PreAuth transaction (a pre-authorization for a certain amount). This transaction lets the merchant know whether the account associated with a card has sufficient funds, without actually charging the card. When the merchant is ready to charge a final amount, the POS will call CapturePreAuth() to complete the Payment.

The PreAuthRequest details.

Marks a PreAuth Payment for capture by a Closeout process. After a PreAuth is captured, it is effectively the same as an Auth Payment. Note: Should only be called if the request's PaymentID is from a PreAuthResponse.

The CapturePreAuthRequest details.

Increments the amount of a previous PreAuth Payment. Note: Should only be called if the request's PaymentID is from a PreAuthResponse.

The IncrementPreAuthRequest details.

Adjusts the tip for a previous Auth transaction. This call can be made until the Auth Payment has been finalized by a Closeout. Note: Should only be called if the request's PaymentID is from an AuthResponse.

The TipAdjustAuthRequest details.

Voids a transaction.

A VoidRequest object containing basic information needed to void the transaction.

Refunds the full or partial amount of a Payment.

The RefundPaymentRequest details.

Initiates a Manual Refund transaction (a “Refund” or credit that is not associated with a previous Payment).

A ManualRefundRequest object with the request details.

Asks the Clover device to capture card information and request a payment token from the payment gateway. The payment token can be used for future Sale and Auth requests in place of the card details. Note: The merchant account must be configured to allow payment tokens.

The card entry methods allowed to capture the payment token. If this parameter is null, the default values (CARD_ENTRY_METHOD_MAG_STRIPE, CARD_ENTRY_METHOD_ICC_CONTACT, and CARD_ENTRY_METHOD_NFC_CONTACTLESS) will be used.

Requests card information (specifically Track 1 and Track 2 card data).

The ReadCardDataRequest details.

Sends a request to the Clover server to close out all transactions. Note: The merchant account must be configured to allow transaction closeout.

The CloseoutRequest details.

Sends a request to reset the Clover device back to the welcome screen. Can be used when the device is in an unknown or invalid state from the perspective of the POS. Note: This request could cause the POS to miss a transaction or other information. Use cautiously as a last resort.

Displays a string-based message on the Clover device's screen.

The string message to display.

Displays the welcome screen on the Clover device.

Displays the thank you screen on the Clover device.

Displays the customer-facing receipt options (print, email, etc.) for a Payment on the Clover device.

The request with payment IDs, etc., to locate the receipt

Opens the first cash drawer found connected to the Clover device. The reason for opening the cash drawer must be provided.

Request with text specifying the reason for opening the cash drawer.

Displays an Order and associated line items on the Clover device. Will replace an Order that is already displayed on the device screen.

The DisplayOrder to display.

Removes the DisplayOrder object from the Clover device's screen.

The DisplayOrder to remove.

Disposes the connection to the Clover device. After this is called, the connection to the device is severed, and the CloverConnector object is no longer usable. Instantiate a new CloverConnector object in order to call InitializeConnection().

Sends a keystroke to the Clover device that invokes an input option (OK, CANCEL, DONE, etc.) on the customer's behalf. InputOptions are on the CloverDeviceEvent passed to OnDeviceActivityStart().

The input option to invoke.

Sends a print request using the PrintRequest object. Used to print text, Bitmap image objects, and images from URLs using the specified printer.

The PrintRequest details.

Queries available printers attached to the Clover device using the RetrievePrintersRequest object.

The RetrievePrintersRequest details.

Queries the status of a print job using the PrintJobStatusRequest object.

The PrintJobStatusRequest details.

Retrieves a list of unprocessed Payments that were taken offline and are pending submission to the server.

Starts a Custom Activity on the Clover device. Note: The Custom Activity must already be set up and configured on the Clover device.

The CustomActivityRequest details.

Sends a message to a Custom Activity running on a Clover device.

The MessageToActivity details to send to the Custom Activity.

Sends a message requesting the current status of the Clover device.

The RetrieveDeviceStatusRequest details.

Requests the Payment information associated with the externalPaymentId passed in. Only valid for Payments made in the past 24 hours on the Clover device queried.

The RetrievePaymentRequest details.

Display receipt options for a Credit, Refund, or Payment

The DisplayReceiptOptionsRequest details

Set the Clover Loyalty API's current customer info

Set the current Log Level to filter log messages. Use constants from the LogLevel class for convenience.

CloverConnector Log Level convenience constants

Minimal logging, only the most critical messages will be logged

Moderate logging, basic flow information without logging excessive details

Detailed logging, flow of information and relevant details

Debug level logging of everything

Contains merchant information about the device

Contains the device information of the connected device

The merchant assigned name of the device

The serial number of the device

The model identifier of the device

Remote pay version supports message acks

Descriptive information about this SDK

Gets or sets the SDK name.

The SDK name.

Gets or sets the SDK version.

The SDK version.

If true then the requested operation succeeded

The result of the requested operation.

Optional information about result.

Detailed information about result.

Base Sale/Auth/Refund/PreAuth Transaction Request

The external reference id if associated with the payment

Present only the QR Code for Payment

Extended Sale/Auth Transaction Request

This should be used for a print call.

Create a PrintRequest to print a given Image - Parameters: - image: Image to print - printRequestId: Optional identifier to give to the print job, so it can later be queried - printDeviceId: Optional identifier to speciy which printer to use Create a PrintRequest to print an image at a given URL - Parameters: - imageURL: URL to the image to print - printRequestId: Optional identifier to give to the print job, so it can later be queried - printDeviceId: Optional identifier to speciy which printer to use Create a PrintRequest to print an array of strings to print - Parameters: - text: Array of strings to be printed - printRequestId: Optional identifier to give to the print job, so it can later be queried - printDeviceId: Optional identifier to speciy which printer to use Create an object used to inform the Clover Connector's `openCashDrawer()` function of required/additional information when requesting the cash drawer be opened - Parameters: - reason: string describing the reason to open the drawer

This request should be used for a Sale call.

If true then the cashback feature will not appear during the transaction

Amount paid in tips

Amount against which a tip should be applied

If true then offline payments can be accepted

If true then offline payments will be approved without a prompt. Currently must be true.

Gets or sets the tip amount.

Gets or sets the tip mode, which controls when the tip is either designated by the customer, provided by the system as part of the request, or ommitted completely from the transaction

If true then payments will be placed directly in the offline queue for processing when a valid connection exists to the gateway. This means that payments can be taken offline even with a healthy gateway connection, for purposes of keeping customer interaction with the payment device to the bare minimum. The merchant assumes all risk of potentially declined transactions when this feature is enabled.

Object passed in to an OnSaleResponse

Object passed in to VerifySignatureRequest. This must also be used to either accept or reject a signature as requested from the clover device.

This request should be used for Auth only, but is backward compatible for older implementations. If you are currently using an AuthRequest with IsPreAuth = true, please change your code to use PreAuthRequest/PreAuthResponse for all PreAuth transactions.

Amount paid in tips

Amount against which a tip should be applied

If true then offline payments can be accepted

If true then offline payments will be approved without a prompt. Currently must be true.

Object passed in to OnAuthResponse

This request should be used for PreAuth transactions. If you are currently using an AuthRequest with IsPreAuth = true, please change your code to use PreAuthRequest/PreAuthResponse for all PreAuth transactions.

Object passed in to OnPreAuthResponse

Initialize the values for this. @private

The payment from the sale

This request should be used for capturing payments obtained from a PreAuth response

Increments a previously made pre auth

The amount by which to increment the pre-auth.

The preauth to be incremented. This id should be pulled from the Payment.paymentId field in the PreAuthResponse.

The result of an attempt to increment a pre auth

The resulting Authorization

Object passed in to an OnVaultCardResponse

This request should be passed to initiate retrieval of card data

Retrieve Card Data

Object passed in to OnCapturePreAuthResponse

This request should be passed in to make a closeout request

Object passed in to OnCloseoutResponse

This request should be used to make a request to adjust the tip amount on a payment obtained from an Auth request or payment after a CapturePreAuth request

Object passed in to OnTipAdjustAuthResponse

Object passed in to ConfirmPaymentRequest. This must also be used to either accept or reject a payment as requested from the clover device.

Object passed in to request the voiding of a payment

Reason for void, must be one of the recognized categories, see VoidPaymentRequest consts for common options use VoidPaymentRequest.USER_CANCEL as default

If true, then do not print using the clover printer. Return print information.

Do not show the receipt options screen

Object passed in to OnVoidPaymentResopnse

Voiding a payment refund (card present flows like canada region)

Object passed in to OnVoidPaymentRefundResponse

This should be used to request a manual refund via the ManualRefund method

The object passed in to OnManualRefundResponse

This request should be used to make a payment request using the RefundPayment method

Object passed in to OnRefundPaymentResponse

Object passed in to OnAcceptPayment

Object passed in to OnRejectPayment

Pased in to OnTipAdded, when an on-screen tip is selected

Initialize the values for this. @private

Tip amount

The request used to show the receipt options screen

The response object for offline payments that have not been processed by the Clover device

List of payments taken offline and not yet processed

Callback to request the POS print a receipt for a ManualRefund

Callback to request the POS print a ManualRefund declined receipt

Callback to the POS to request a payment receipt be printed

Callback to the POS to request a payment declined receipt

Callback to the POS to request a merchant payment receipt be printed

Callback to the POS to request a payment refund receipt be printed

Request for the Clover device to start a Custom Activity