TransactionUpdate Callback

The Payment Device SDK fires transactionUpdate events as the customer progresses through the transaction. Each transaction update event describes the action that triggered the event, including EMV commands and data communication. The POS application can react to each event as needed, such as to update a display.

Methods to add or remove callback delegate in ChipDnaMobile:

void addTransactionUpdateListener(  
TransactionUpdateListener listener  
)

void removeTransactionUpdateListener(  
TransactionUpdateListener listener  
)

CardDetails Callback

When startTransaction() has been successfully called, the Payment Device SDK fires cardDetails events when the details are available. When getCardDetails() has been successfully called, the SDK fires a cardDetails event when the process is finished (instead of a transactionFinished event).

Methods to add or remove callback delegate in ChipDnaMobile:

void addCardDetailsListener(  
CardDetailsListener listener  
)  
void removeCardDetailsListener(  
CardDetailsListener listener  
)

RequestActivity Callback (Android-Specific)

For Android Tap to Pay transactions, the Payment Device SDK fires a requestActivity callback when it requires an Activity to handle NFC prompts for card reads. This is specific to Android implementations and is mandatory for Tap to Pay functionality.

Methods to add or remove callback delegate in ChipDnaMobile:

void addRequestActivityListener(
IRequestActivityListener listener
)

void removeRequestActivityListener(
IRequestActivityListener listener
)

void clearAllRequestActivityListener()

Parameters continueRequestedActivity(
Activity activity
)

The RequestActivityListener is specific to Android Tap to Pay implementations and is required to handle Activity management for NFC operations. The Activity must remain active until the CardTapped transaction update is received.

The activity must adhere to the EMVCo Contactless Symbol and supported Card Brand images requirements. See the Contactless Symbol Reproduction Requirements section for details.

TransactionFinished Callback

After startTransaction() has been successfully called, the Payment Device SDK fires a transactionFinished callback when the transaction is finished. If the transaction is finished after the cardDetails callback is triggered, the transcationFinished parameters contains a parameter which will include the transaction result Approved or Declined and a receipt can be issued for the completed transaction. If the transaction is finished before the cardDetails callback, the parameters contain only the Errors parameter indicating the transaction has been terminated.

Methods to add or remove callback delegate in ChipDnaMobile:

void addTransactionFinishedListener(  
TransactionFinishedListener listener  
)

void removeTransactionFinishedListener(  
TransactionFinishedListener listener  
)

Tap to Pay transactions are auto-confirmed by default. The confirmTransaction() method is not required for Tap to Pay transactions as they are automatically settled.

ProcessReceiptFinished Callback

When processReceipt() has been successfully called, the Payment Device SDK fires a onProcessedReceiptFinished callback with the result of the request.

Methods to add or remove callback delegate in ChipDnaMobile:

void addProcessReceiptFinishedListener(  
ProcessReceiptFinishedListener listener  
)

void removeProcessReceiptFinishedListener(  
ProcessReceiptFinishedListener listener  
)

SignatureVerification Callback

The Payment Device SDK fires a signatureVerification event, during a transaction, when the merchant needs to verify the cardholder signature. Call continueSignatureVerification() to set the signature verification result and continue the transaction. If digital signature is captured, the data should be sent to the SDK in a parameter in the continueSignatureVerification() method.

Methods to add or remove callback delegate in ChipDnaMobile:

void addSignatureVerificationListener(  
SignatureVerificationListener listener  
)

void removeSignatureVerificationListener(  
SignatureVerificationListener listener  
)

SignatureCapture Callback

The Payment Device SDK fires a SignatureCapture event during a transaction when a digital signature is required. Call continueSignatureCapture() to pass in digital signature data and continue the transaction.

Methods to add or remove callback delegate in ChipDnaMobile:

void addSignatureCaptureListener(  
	SignatureCaptureListener listener  
)  
void removeSignatureCaptureListener(  
	SignatureCaptureListener listener  
)

ApplicationSelection Callback

The Payment Device SDK fires an applicationSelection event during a transaction when a customer is required to select the card application they wish to use for the transaction. Call continueApplicationSelection to pass the customers selection and continue the transaction.

Methods to add or remove callback delegate in ChipDnaMobile:

void addApplicationSelectionListener(  
	ApplicationSelectionListener listener  
)  
void removeApplicationSelectionListener(  
	ApplicationSelectionListener listener  
)

UserNotification Callback

The Payment Device SDK fires a userNotification callback when a prompt is required to be shown to the customer. No integration call to the SDK is required to continue the transaction. The transaction will continue as normal.

Methods to add or remove callback delegate in ChipDnaMobile:

void addUserNotificationListener(  
	UserNotificationListener listener  
)  
void removeUserNotificationListener(  
	UserNotificationListener listener  
)