Core object of EFToolkit is now BatchEngine, with a dispinterface called _BatchEngine. Both VB and VC++ developers will have to change their code if they want to use the new features. The old Engine object is still supported.
You can now unite multiple batches into one entity called a BatchSet. After you submit all the batches you want, you can commit or roll back the whole set in a single operation. It helps avoid situations when a database application expects to send multiple batches, some of them go through and some do not. See BatchSet object.
Version 2 of EFToolkit does more than just tell whether a transaction is valid or not. It provides information about what is invalid. See WhatsInvalid, InvalidityMessage properties.
All Credit Card numbers conform to certain rules, as established by the major processors. EFToolkit can now check a Credit Card number for you. This helps prevent typos. See VerifyCardNumbers, IsCardNumberValid properties.
EFToolkit can generate e-mail receipts for your customers, if you provide their e-mail addresses. See GenerateBillingEmail, GenerateReturnEmail, Email.
To help EFTechnologies track application usage, EFToolkit now lets you provide a code which will identify your software package. See AppID, AppName, AppVersion properties.
Most Internet operations now generate a comprehensive trace of their internal workings. This will help our support staff identify connectivity and/or setup problems. See EnableTracing and Trace properties.
Handshake has evolved from a simple connectivity check into an inquiry about company's registration information. See properties of Handshake2 object.
Internet operations now report elapsed time and the amount of data that was transmitted and received. See Performance monitoring.