Migration
Please reference pos-getting-started for a description and examples of the initialization process in 3.x, eg. using “Payment.create()” vs. “new Payment” to create objects, and importing “com.verifone.payment_sdk.Payment” vs. “com.verifone.commerce.entities.Payment”.
Note
On CM5 and Trinity terminals, please set Device Manager > Transaction Options > Terminal.1 > UseDeveloperSDK to “0” in order to use the 3.x SDK.
API Changes
Status Session ID has moved to Commerce Event.
TransactionManager.getTransactionManager has moved to PaymentSdk.getTransactionManager().
TransactionManager.TearDown() has been removed and is no longer accessible as a TransactionManager API.
Migration from CommerceListener and PsdkStatusListener to CommerceListenerAdapter
CommerceListener and PsdkStatusListener are being deprecated and consolidated into a single listener CommerceListenerAdapter. The old and new listeners and the respective APIs should not be used in conjunction.
To use the new CommerceListener :
create CommerceListenerAdapter
Use the API PaymentSdk.initializeFromValues(…) with this listener.
Get the TransactionManager using PaymentSdk.getTransactionManager(…)
To Login to the terminal Create the login credentials and call TransactionManager.loginWithCredentials()
To start a session call TransactionManager.startSession2(…)
See also
login-logout.
start-session.
Note
Make sure to use the CommerceListenerAdapter with New APIs only. Using deprecated APIs in conjunction with CommerceListenerAdapter or the other way might lead to unexpected behaviour.
API Changes
PaymentSdk.initialize(PsdkStatusListener) API is replaced with PaymentSdk.initialize(…)
PaymentSdk.initializeFromFile(PsdkStatusListener,String) API is replaced with PaymentSdk.initializeFromFile(…)
PaymentSdk.displayConfiguration(PsdkStatusListener) API is replaced with PaymentSdk.displayConfiguration(…)
Was this helpful?