How to confirm you are using Native Mode on EFSnet, yet manage your own data

Your application code uses the native methods in the EFSnet Interface Specification such as CreditCardCharge, CreditCardAuthorize and so on.  Also, your application stores transaction data such as account numbers, expiration dates, and so on to facilitate authorization, settlement and reporting, per PCI-DSS or PA-DSS security standards.

One good way to determine if your application code manages its own data is to evaluate how you perform a refund using EFSnet.  If you use the CreditCardCredit method, you are managing your own transaction data.  If you use the CreditCardRefund data, you are expecting EFSnet to do it.

YOUR RECOMMENDED SOLUTION

YOUR ALTERNATE SOLUTION

Your recommended solution is

Datawire Common XML interface offering on the Datawire IPN

Your alternate solution is

Datawire IPN using the appropriate Buypass/Atlanta host specification for your business requirements

Availability of this solution

Late 2008

Availability of this solution

Immediate

Advantages of this solution

The Common XML interface will provide a single transaction structure and set of methods for interaction with both primary First Data USA platforms (Buypass and Nashville), including a Web services access method and the entire Datawire IPN feature set

This might be an option if

The timeframe of Common XML availability does not suit your organization, or you need specific features not planned in the Common XML interface

Effort to migrate

Small to moderate; the XML and Web service interfaces will be similar to those found on EFSnet, but some re-coding may be required and Datawire integration programming will be necessary

Effort to migrate

Moderate; the Datawire and host specification interfaces will need to be built, tested and certified

For more information

E-mail: Securetransport.integration@firstdata.com

For more information

E-mail: Securetransport.integration@firstdata.com