Magento

All references to First Data Global Gateway should be read as Payeezy as First Data Global Gateway is now Payeezy.

After an account is loaded into our system, a merchant receives an automated Web Service API Welcome Email from ‘[email protected]’. It outlines the steps needed to complete the activation process for your account. This email contains the following information required to log in:
> DBA Name
> Store Name – a 6 or 10 digit numeric value
> User-ID
> Temporary Password – call the Support Desk at 888-477-3611 to receive your password.
It is required to login to the site, process transaction reports, and perform administrative
functions.
> Virtual Terminal URL – https://secure.linkpt.net/lpc/servlet/LPCLogin

Login
Enter your ten (10) digit Store Number or User ID > Enter the Temporary Password > Click Login > Click Accept Agreement on the Global Gateway User Agreement

Note: Temporary passwords are valid for only thirty (30) minutes after they are issued.

Once logged in, a merchant can begin processing transactions.

The following checklist provides an overview enabling you to ensure that you have received the whole set when registering your application for the First Data Global Gateway:
1. Store ID – Your store ID, assigned by First Data.
2. User ID and Password – The user ID and password required for basic authorization with the Web Service API. The user ID is in the format WS._.1. For example, if your store ID is 111920, your user ID is WS111920._.1. This information is in the. WS._.1.auth.txt file.
3. Client Certificate p12 File – The client certificate stored in a p12 file, named in the format WS._.1.p12. For example, if your store ID is 111920, your p12 file is named WS111920._.1.p12. This file is used for authenticating the client with the First Data Global Gateway. For connecting with Java, you need a ks file, for example WS111920._.1.ks.
4. Client Certificate Installation Password – The password required for installing the p12 client certificate file. This information is in the WS._.1.p12.pw.txt file.
5. Client Certificate Private Key – The private key of the client certificate stored in a key file, named in the format WS.key. Depending on your choice of tools, this may be required for authenticating with the Web Service API.
6. Client Certificate Private Key Password – The password required for the private key, named in the format ckp_. For example, this might be
ckp_1193927132. Depending on your choice of tools, this may be required for authenticating with the Web Service API. This information is in the WS._.1.key.pw.txt file.
7. Client Certificate PEM File – The client certificate stored in a pem file, named in the format WS._.1.pem. For example, if your store ID is 111920, your pem file is named WS111920._.1.pem. This file is used for authenticating the client with the First Data Global Gateway. Depending on your choice of tools, this may be required for authenticating with the Web Service API instead of the p12 file.

Testing with valid test credit cards within the test environment. These cards will NOT work in PRODUCTION.

The following cards are valid test credit card numbers. They will only work within the First Data Payeezy Gateway test environment. Please do not use these sample cards within the production environment, as they cannot be used to validate the production gateway.

Credit/Signature Debit Cards 

TeleCheck