Configuring the Payment Gateway Connection

Transcription

1 Configuring the Payment Gateway Connection The following steps should provide guidance to setting up the payment gateway connection. Please be aware that in order to configure the payment gateway connection, it is often needed to have the connection credentials to the payment gateway. 1. To configure the connection to the Secure Payment Gateway log into the web server and open the Nodus Connection Manager from Start -> Programs -> Nodus Technologies -> Nodus Connection Manager 2. Choose or create a setup ID from the Setup ID dropdown field. a. If a new setup ID is created, it must exist within Credit Card Advantage in Dynamics GP. 3. The remaining fields are specific to the Payment Gateway that is in use, choose which of the gateways that will be used for the configuration. PayPal PayFlow Pro USAePay Authorize.Net CyberSource Paymentech Moneris PayFuse First Data PayPal (Classic) x3delta 4. Click the Save button to save the changes 5. After any changes are made on the Nodus Connection Manager, the epay application pool must be recycled for the changes to be applied to the website. Open the Internet Information Services (IIS) Manager by opening the Windows Run Window (Start Run) and entering Inetmgr.

2 6. From the IIS Manager, locate the Application Pool for the epay website from the Application Pools page a. If you do not know the Application Pool that epay is using, click the epay website from the IIS manager and choose the Basic Settings action on the right side of the page and the Application Pool should be shown in the Edit Site window. 7. Right-click the Application Pool and click the Recycle option from the menu to recycle the application pool. Any currently logged in users would need to begin their payment again. 8. If a new Setup ID was created, log into the epay website as an administrative user and browse to the Transaction Processing Options tab of the Site Settings page and configure the Setup ID for echeck or Credit Card to use the new setup. Page 2

3 9. To apply the changes for Scheduled Payments, restart the Nodus Scheduler Windows Service on the web server. a. From the web server, open the Nodus Scheduler Monitor from the Start menu as an administrator user by right clicking the shortcut and choosing the Run as Administrator option. (Start Programs Nodus Technologies Scheduler Nodus Scheduler Monitor) b. To stop the Scheduler, push the Stop button ( ) at the top of the page c. To restart the Scheduler push the Play button( ) at the top of the page Page 3

4 PayPal PayFlowPro Gateway Configuration Partner Vendor UserID Password UseToken PayFlowPro Choose the Credit Card that the PayPal PayFlowPro account is connected to Choose Credit for Credit Card Transactions Choose Check for echeck Transactions For Test Transactions: For Live Transactions: This is the partner that setup the PayFlowPro account. This is the same as the Partner field used to log into This is the Merchant Login used to identify the PayFlowPro account. This is the same as the Merchant Login used to log into The PayFlowPro account may utilize a User when logging into If no User is used when logging into the PayPal Manager, fill in this field with the same value as the Vendor field. This is the password associated with the User or Merchant Login to log into If using the Tokenization Option, set this field to True. Otherwise, leave it as false. Page 4

5 USAePay Gateway Configuration USAePay USAePay Choose Credit for Credit Card Transactions Choose Check for echeck Transactions Put Test or Live in this field if this Setup id being used for a test or live account respectively Server.Port 443 SourceKey TestMode This is the Source Key that is obtained from the settings of the USAePay gateway For a Test Source Key, set this value to True For a Live Source Key, set this value to False Page 5

6 Authorize.Net Gateway Configuration AuthorizeNet Authorize.Net Choose Credit for Credit Card Transactions Choose echeck for echeck Transactions For Test Transactions: For Live Transactions: Port 443 LoginID TransactionKey TestMode UseToken This is the login id used for the Authorize.net account This key can be obtained from the Authorize.Net Gateway. Contact the Authorize.net gateway provider for more details. For a test transactions, set this value to True For a live transactions, set this value to False If using the Tokenization Option, set this field to True. Otherwise, leave it as false. Page 6

7 CyberSource Gateway Configuration MerchantID Cybersource Choose the Credit Card that the Cybersource account is connected to Credit For Test Transactions: ics2test.ic3.com For Live Transactions: Ics2.ic3.com This is the merchant ID for the Cybersource account To use the Cybersource Gateway, it is necessary to obtain the secure CyberSource Keys from the Cybersource ecert Application. Contact the CyberSource partner for more information on obtaining these keys. Once the keys are obtained, they should be placed in the following folder: C:\Program Files (x86)\common Files\Nodus\CyberSource\keys Page 7

8 Paymentech Orbital Gateway Configuration Paymentech Paymentech Choose Credit for Credit Card Transactions Choose Check for echeck Transactions For Test Transactions: Orbitalvar1.paymentech.net For Live Transactions: Orbital1.paymentech.net Port 443 MerchantID BIN TerminalID UseToken This is the Merchant identifier used for the Paymentech Account This is the typically 6 digit bin number associated with the Paymentech Account This is the identifier for the Terminal ID used with the Paymentech Account If using the Tokenization Option, set this field to True. Otherwise, leave it as false. When using the Paymentech Gateway it is important to make sure that the Web Server s external IP has been registered with Paymentech for the specified account before processing transactions. Page 8

9 First Data Gateway Configuration Server.Url Username Password Result Origin First Data First Data Credit This is the Username for the First Data Gateway Account This is the password for the First Data Gateway Account LIVE ECI To use the First Data Gateway, please ensure that the First Data Certificate has been generated and placed in the following folder: C:\Program Files (x86)\common Files\Nodus\FirstData\Certificate For more information on generating the Certificates, please consult with the Credit Card Advantage User Gide. Page 9

10 PayFuse Gateway Configuration PayFuse PayFuse Credit Server.Port 443 UserName Password Mode Alias/CID This is the User identifier used for the PayFuse account This is the password used for the PayFuse account Y for Test, P for Live This is supplied by PayFuse Page 10

11 Moneris Gateway Configuration Moneris Moneris Credit For Test Transactions: For Live Transactions: Server.Port StoreID APIToken This is the Store identifier obtained from Moneris This is the API Token value obtained from Moneris Page 11

12 X3Delta Gateway Configuration X3Delta 3Delta EC-Linx Credit For Test Transactions: For Live Transactions: Server.Port 443 MerchantID UserID Password This is the Merchant Identifier associated with the x3delta account This is the User Identifier accociated with the x3delta account This is the password associated with the UserID Page 12

13 PayPal (Classic) Gateway Configuration The PayPal (Classic) gateway is not the PayPal PayFlowPro gateway, most PayPal accounts setup are generally PayPal PayFlowPro accounts. If the account being used is a PayPal PayflowPro account, please use the PayPal PayFlowPro Gatway Configuration section. PayPal PayPal Credit For Test Transactions: For Live Transactions: Server.Port 443 Password UserName Signature This is the Password associated with the PayPal account This is the Username associated with the PayPal account This is the unique value for processing transactions obtained from PayPal Page 13