Frequently Asked Questions

A Canadian routing number must be created from the financial institution's Magnetic Ink Character Recognition (MICR) code. For example, if a bank's MICR code is BBBBB-AAA, then it's routing number in Forte's system would be 0AAABBBBB. The leading digit should always be zero. The three-digit code (AAA in our example) represents the financial institution, while the five-digit code (BBBBB) identifies the branch. For a directory of Canadian financial institutions, click here. For more information on the Canadian routing number system, click here.

When using SWP and SOAP/REST web services, a UTC time in ticks since 01/01/0001 00:00:00A may be required to compute the hash value. In cases such as with the integrated cart payment modules, the UTC time in tickets can be computed in seconds using PHP time() function since 01/01/1970 00:00:00AM UTC. The following code may be helpful in computing the UTC time in PHP:

$time = time() + 62135596800;
'UTC now ticks= echo ' . $time . '0000000';

In addition, you can use the following code to generate the UTC time in tickets value in PERL.

#!/usr/bin/perl
# generate UTC time stamp since 01/01/0001 in tics
my $time = (time + 62135596800) . "0000000";

To request a 60-day test account prior to enrollment of your production account, please email your sales organization a request with the following information:

• Contact Name
• Contact's Title
• Business Address 1
• Business Address 2
• Business City
• Business State
• Business Postal Code
• Business Phone
• Business Fax
• Business Email

If you are not currently working with the Forte Sales Team, please email your request to [email protected].

Upon submitting a transaction with a duplicate amount, Forte returns the following response:

U10:DUPLICATE TRANSACTION - Transaction has the same attributes as another transaction within the time set in the merchant configuration. The default is five minutes but can be disabled or changed upon request.

This issue can be resolved by either of the following methods:

• Adding an invoice number to the ConsumerOrderID (AGI: ecom_consumerorderid) field
• Sending different values in a combination of these fields: Merchant ID, Transaction Type, Amount, ConsumerOrderID (if present), Credit Card Account Number, or EFT TRN/DDA

Merchants who want to quickly and efficiently reverse transactions can do so using the Virtual Terminal's Reverse button. To do so, complete the following steps:

1. From the Virtual Terminal home screen, click . The Search Transaction screen displays.
2. Enter search criteria including reported transaction types (i.e., credit card, echeck, unsettled), date range, and transaction information and click . The search results display.
3. Scroll through the search results and click on the transaction you want to reverse. The Transaction Detail screen for that transaction displays.
   
4. Click . A browser message displays asking you to confirm the reversal.
5. Click OK to confirm the reversal.

The following table displays which shopping cart brands Forte supports:

If your FrankIT printer is connected using a serial-to-USB conversion cable, the driver for the converter may have to be downloaded and installed. Visit the manufacturer's website for the latest versions of these drivers.

Upon receipt of the signed request and the required documents, our Risk Department will review your merchant account to determine the reserve and/or the per transaction price increase required. These figures are typically based on the current approved limits as well as the return ratios, including charge-backs, and the financial stability of the company.

Timeouts generally occur because the entire transaction message is not making it to Forte's servers. Use the following troubleshooting techniques to address timeout errors:

Checking the Sent String

Check that the string your application is generating and sending. It should look something like the following:

pg_password=password&
pg_transaction_type=20&
pg_total_amount=10.00&
pg_billto_postal_name_company=Company&
ecom_billto_postal_name_first=Test&
ecom_billto_postal_name_last=Customer&
ecom_billto_postal_street_line1=2350+Date+Palm&
ecom_billto_postal_city=Cathedral+City&
ecom_billto_postal_stateprov=CA&
ecom_billto_postal_postalcode=92234&
ecom_payment_check_account_type=C&
ecom_payment_check_account=1234567891&
ecom_payment_check_trn=111000614&
pg_avs_method=00000&
ecom_walletid=walletid&
endofdata&

Note the ampersand at the end of the string. If the message is properly terminated and still times out, check for additional issues.

Wait Time Too Short on the Merchant Side

The merchant's system should wait at least 60 seconds for a response. The Forte platform will wait 60 seconds for a response from external vendors (credit card processors, verification services, etc.). During the busiest times, there may be some internal queue time as well, so Forte recommends a 90 second wait time. Through the average processing time is 2–3 seconds, an extended (maximum) timeout period will ensure the merchant loses no transactions in the worst case scenario.

Firewall Blocking at the Merchant's Site

This would need to be looked into by the merchant's IT staff. Generally the following ports need to be opened:

Direct Socket Integration

• Port 6050 and 6051 for testing
• Port 5050 and 5051 for production

Com Object, PHP Curl, T-SQL, or the POST Method

• Port 443

General Connectivity Problems

If the merchant's internet connection is not down, the merchant should be able to browse to other sites from the machine sending the transactions.

DNS Failures

DNS failures can be checked with the ping command. The Forte platform does not return pin packets but the first thing "ping www.paymentsgateway.net" will do is attempt to resolve the name via DNS. If it says something like "Pinging <site> [<IP addr>]" then DNS is not a factor. If it hangs, the program cannot resolve the name via DNS, which would indicate a connectivity or DNS issue.

If the merchant's timeouts are not explained by any of the above, more troubleshooting by Forte will be required. For each timed-out transaction (up to a maximum of ten), please submit the following information:

• Originating IP address (see www.WhatIsMyIP.com)
• Merchant ID
• Time of submission
• Name, Amount, and ecom_consumerorderid
• Exact networking error reported by the operating system (if known)
• Amount of time the merchant waited before timeout

Valid inputs for pg_schedule_quantity begin at zero. Specifying zero indicates a transaction is to be processed until canceled. Recurring transactions must have both pg_schedule_quantity and pg_schedule_frequency, but pg_schedule_recurring_amount and pg_schedule_start_date are optional. The following is an example message for a continuous monthly recurring EFT sale transaction:

pg_merchant_id=111111
pg_password=merchant's processing password
pg_transaction_type=20
pg_total_amount=100.00
ecom_billto_postal_name_first=John
ecom_billto_postal_name_last=Smith
ecom_payment_check_account_trn=021000021
ecom_payment_check_account=1234567
ecom_payment_check_account_type=C
pg_schedule_frequency=20
pg_schedule_quantity=0
endofdata

Complete the following steps:

1. Download the "PHP 5.0.5 zip package" and collection of PECL modules for PHP 5.0.5 from http://www.php.net/downloads.php#v5.
2. Extract the contents of php-5.0.0-Win32.zip into a folder. From this point forward, this will be referred to as the installation directory (e.g., C:\Program Files\PHP)
3. Extract the contents of the pecl-5.0.5-Win32.zip into the "ext" folder of the installation directory.
4. Configure the IIS Application Mappings to include php and .php3 extenstions call C:\Program Files\PHP\php-win.exe.
5. From the installation directory, copy php.ini-recommended to php.ini and modify it as follows:
   • extension_dir=./ext
   • cgi.forc_redirect=0
   • extension=php_curl.dll
6. Install or update a CA certificate bundle as detailed on the official cURL website: http://curl.netmirror.org/docs/sslcerts.html.
7. Include the following in the cURL code of php_curl.php between ob_start() {}:
   • curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, 1); // verifying the peer's certificate is completely optional.
   • curl_setopt($ch, CURLOPT_CAINFO, 'c:\php\ca-bundle.crt'); // specificy path to ca-bundle.crt in 3rd parameter.

NOTE: Messages delivery securely to Forte use SSL v3 and/or TLS v1.0 protocols.

Below is an example response:

pg_response_code=E10 pg_response_description=INVALID PASSWD pg_trace_number=76D30BF7-C574-4F9A-AA65-7DF9E58FA0B0 pg_merchant_id=2000 pg_transaction_type=13 pg_total_amount=110.00 ecom_billto_postal_name_first=John ecom_billto_postal_name_last=Smith endofdata * About to connect() to www.paymentsgateway.net port 443 * Trying 10.10.1.102... * connected * Connected to www.paymentsgateway.net (10.10.1.102) port 443 * successfully set certificate verify locations: * CAfile: c:\php\ca-bundle.crt CApath: none * SSL connection using RC4-MD5 * Server certificate: * subject: /C=US/ST=California/L=Palm Springs/O=ACH Direct, Inc./OU=Terms of use at www.verisign.com/OU=Terms of use at www.verisign.com/rpa (c)05/CN=www.paymentsgateway.net * start date: 2007-01-09 00:00:00 GMT * expire date: 2008-02-06 23:59:59 GMT * common name: www.paymentsgateway.net (matched) * issuer: /O=VeriSign Trust Network/OU=VeriSign, Inc./OU=VeriSign International Server CA - Class 3/OU=www.verisign.com/CPS Incorp.by Ref. LIABILITY LTD.(c)97 VeriSign * SSL certificate verify ok. > POST /cgi-bin/posttest.pl HTTP/1.1 Host: www.paymentsgateway.net Accept: */* Content-Length: 307 Content-Type: application/x-www-form-urlencoded pg_merchant_id=2000&pg_password=password&pg_transa ction_type=13&pg_total_amount=110.00&ecom_billto_p ostal_name_first=John&ecom_billto_postal_name_last =Smith&ecom_payment_card_type=VISA&ecom_payment_ca rd_number=4111111111111111&ecom_payment_card_expda te_month=12&ecom_payment_card_expdate_year=2020&en dofdata< HTTP/1.1 200 OK < Date: Wed, 26 Sep 2007 21:29:00 GMT < Server: Apache/2.2.3 (Debian) mod_ssl/2.2.3 OpenSSL/0.9.8c mod_perl/2.0.2 Perl/v5.8.8 < Transfer-Encoding: chunked < Content-Type: text/html; charset=UTF-8 < Set-Cookie: BIGipServerCGIPost=687999498.47873.0000; path=/ * Connection #0 to host www.paymentsgateway.net left intact * Closing connection #0

Forte loves working with a variety of merchants; however, we cannot process payments for businesses on our Prohibited Merchant list. We derive this list both from our banking partners and our own experience with losses in certain industries. The list below displays the types of businesses that Forte will not work with regardless of their use of services (e.g., payroll, service fees, etc.). If you have additional questions about this list, contact Forte Sales.

Prohibited Merchant List

• Greater than 36% APR on Consumer or Business Loans
• 30-Day Trial Membership Offer with Recurring Billing After Trial
• Adult-Related Businesses
• Advanced Fee Credit Cards
• Any Business Engaging in Illegal Activities
• Any Business with an “F” Better Business Bureau Rating
• Bitcoin Currency
• Check Cashing
• Debt Consolidation/Debt Management Programs/Credit Repair
• Discount Medical Benefits
• Early Termination Fees over $500.00
• Foreclosure Work-Outs/Defense
• Forensic Loan Audit
• Fantasy Sports
• Foreign Financial Institutions
• Foreign/Off-Shore Business (Only US and Canadian businesses allowed)
• Gambling Establishments and Associated Businesses and Websites
• ID Theft Protection
• Illegal Internet Gambling
• Import/Export Brokers or Intermediaries
• Individuals (i.e., not a business, agency, or organization)
• Investment Management/Hedge Funds Management
• Jewelry/Metals and Precious Gem Sales
• Loan Modification/Consulting
• Lottery
• Medical Discount Benefits Package
• Medical Marijuana Providers/Advocates
• Money Service/Transmitter Businesses
• Online Tobacco Sales, including Electronic Cigarettes
• Outbound Telemarketing
• Pawn Shops
• Payday Loan (Only ATM Verify allowed)
• Products with Unreasonable Guarantee
• Securities and Commodities
• Telemarketing
• Timeshares
• Travel Industries

To resolve a perpetual spinner when accessing the Virtual Terminal in Internet Explorer, enable the ActiveX Filtering option under the Tools menu by clicking on it. When enabled, IE displays a check mark next to the option (see the figure below). Alternatively, you can attempt to log in from another browser, such as Google Chrome.

To enable Compatibility Mode, complete the following steps:

1. Access the Compatibility View Settings window from the Tools menu in Internet Explorer.
   
2. Type the Virtual Terminal URL in the Add this website field if it is not automatically listed and click .
3. Click .

Currently, Microsoft Edge does not support the scripting requirements of Virtual Terminal and requires the user to revert back to Internet Explorer 11 and turn on compatibility mode. A message displays indicating when the user should do this:

To revert to Internet Explorer 11 and turn on compatibility mode, complete the following steps:

1. Go to the MS Edge Internet Options menu and select Open with Internet Explorer.
   
2. From the Internet Explorer 11 Tools menu, access the Compatibility View Settings window.
   
3. Type the Virtual Terminal URL in the Add this website field if it is not automatically listed and click .
4. Click .

Forte is dedicated to protecting the confidentiality and integrity of your customers' information by providing the highest levels of security. We are certified fully compliant with the PCI Data Security Standard. PCI covers twelve major categories of information security including network design, data storage, intrusion monitoring and the use of security-aware IT policies. Our compliance meets and exceeds these industry standards as an integral part of our commitment to end-to-end security.

All merchant communications uses high-grade 128-bit SSL to protect your information as it passes through the Internet.

We also encrypt all sensitive information before placing it onto any storage device. We encrypt sensitive information using RSA public/private 1024-bit key technology with a proprietary cryptographic server infrastructure. Our system uses a split-knowledge unlock procedure that ensures no single person within Forte has access to your customers' sensitive information.

Click here to see a listing of PCI-DSS compliance service providers as provided by Visa.

The NACHA file does not need to be balanced.

Enter your Merchant ID assigned by Forte in the Company Identification field. This value may be referenced from the new merchant's welcome letter or package. The Company Identification is an alphanumeric field found in both the batch header and batch control records:

• Batch Header (type '5'): positions 41-50
• Batch Control (type '8'): positions 45-54

Numeric text (i.e., 0–9 with no period) must be right justified with no padding and zero filling any empty positions. For example, the variable, COMPANY IDENTIFICATION must be formatted in this manner for the Forte platform to accept the file.

Alphabetic/alphameric text must be left justified with space padding for unused positions.

The Immediate Destination field is not necessary.

Click here to see a list of supported check and credit card readers.

Click here to download the necessary drivers for USB MagTek readers. The MagTek USB driver is necessary to use the APTM USB, CAPS4USB, IntelliPINUSB, MiniMICRUSB, or MICRImageUSB models with a Windows operating system. These devices can be installed on the same PC if required. After you unzip the files to a folder on your hard disk, attach the device to the PC. In order to install them on a 32-bit system, select the USB-332 folder; to install them on a 64-bit system, select the USB-64 folder.

Click here to download the MagTek MICR Configuration Tool with Device Loads. MICR readers can be configured using the MICRbase program. Included as part of the download are commonly used device loads for supported MagTek products.

To reconfigure your Magtek credit card swiper (Model #21040107 and #21040145) to factory defaults, complete the following steps:

1. Disconnect the Magtek swipe reader from the computer's USB port.
2. Click the link to download USB Swipe and Insert Reader from Magtek's website.
3. Run the setup wizard to install the downloaded program. Installation of source code is not required.
4. From the Start (All Programs) menu, navigate to the MagTek folder and click on MagTekUSBMSRDemo.
5. Connect the Magtek swipe reader to an available USB port on the computer. At the bottom of the USB MSR program window, a status message will be displayed that the reader has been connected.
6. From the File menu, select Open.
7. From the Open dialog box, double click on the following command file: "Change to Keyboard.txt."
8. In the yellow "Load From File" section, click the Download button. This will execute the commands in the file and reset your Magtek credit card swipe reader to keyboard emulation mode. Results will be displayed in the Communications Dialog text box.
9. From the peach "Send Message (Hex)" section to the right of the SendMsg button, enter the following text: 01 04 63.*
10. Click the SendMsg button. Results will be displayed in the Communication Dialog text box.
11. From the peach "Send Message (Hex)" section to the right of the SendMsg button, enter the following text: 01 05 0D.*
12. Click the SendMsg button. Results will be displayed in the Communication Dialog text box.
13. Upon execution of the steps above, disconnect the Magtek swipe reader from the computer's USB port.
14. Wait 30 seconds and reconnect the Magtek swipe reader to the computer's USB port. At the bottom of the USB MSR program window, a status message will be displayed that the credit card reader emulating a keyboard has been connected.
15. Close the Magtek USB MSR application.

*Readers purchased by Acclivity/MYOB merchants will use the following messages in lieu of those detailed in steps 9 and 11:

• Step 9: Use the following text: 01 04 73.
• Step 11: Use the following text: 01 05 09.

Refer to the Readme.txt for additional information on the Magtek USB MSR appliction.

1. Right click on the following link to download the device load to your desktop: https://www.paymentsgateway.net/code/Micr.zip.
2. From the context menu, choose Save target as and specify to save the file to the desktop using the default file name Micro/zip.
3. Using an industry-standard zip/unzip tool, preferable WinZip, extract 22533001.mic (not PN22533001.mic).
4. Click on the following link to download the MicrBase application from MagTek's website:http://www.magtek.com/support/software/downloads/sw/99510075.exe.
5. Choose to Save the file to your desktop, double click 95510075. This icon has a red background with white letters. From the next dialog box choose Unzip and the files will be extracted to the MICRBASE folder on the desktop. Click OK on the confirmation dialog box to continue and then click Close.
6. Move the 22533001.mic file from the desktop to the MICRBASE folder also on the desktop.
7. Open the MICRBASE folder and double click on the MICRBASE.exe application. This icon has a gray background with red letters. From the File menu choose Open, double click on the 22533001.mic file, and a Configure dialog box displays.
8. Click on the Com Setup button.
9. Click on Auto Detect RS232 Parameters and upon completion, the status indicator will display the following message: "MICR Detected." Click the Test button and the status indicator will display the following message: "Communication test passed."
10. Click OK.
11. Click DOWNload Configuration to MICR from the Configure dialog box. Once complete, click OK and close the MICRbase application.
12. As a sanity check, Forte recommends logging into the Virtual Terminal and attempting to swipe a credit card or check using the reader.

1. Download the excella.zip file: https://www.paymentsgateway.net/code/excella.zip.
2. Install the file by double clicking on the setup-204.exe file.
3. Plug in the Excella power and USB cords.
4. Select Searchfor a suitable driver for my device when the Found New Hardware wizard displays.
5. Browse to Excella.inf
6. Browse to the Excella Installation folder (i.e., C:\Program Files\MagTek\Excella Demo) and double click on ExcellaUSBConfig.exe.
7. Apply the following settings to your device:
   • Excella Device(s) in MICRDEV.INI file: Excella_USB
   • IP Address (PC Side): 192.168.99.5
   • IP Address (Device Side): 192.168.99.100
   • Subnet Mask: 255.255.255.0
8. Restart your system.
9. Verify settings by going to the micrdev.ini file located here:
   • C:\WINNT for Windows 2000/98
   • C:\WINNT for XP
10. The file should look like the following:

[DEVICE1]

Name=EXCELLA_ETHER
Transport=ETHERNET
ConnectionString=192.168.10.100
SimulatorFile=c:\program files\magtek\Excella Demo\Script\Device1.ini
ScriptFile=c:\program files\magtek\Excella Demo\Script\Script1.ini

[DEVICE2]

Device=Excella
Name=EXCELLA_USB
Transport=ETHERNET
ConnectionString=192.168.99.100
SimulatorFile=c:\program files\magtek\Excella Demo\Script\Device1.ini
ScriptFile=c:\program files\magtek\Excella Demo\Script\Script1.ini

*Verify the ConnectionString contains the correct IP Address(s); If ok, restart the computer.

11. Open Direct Billing v3.51 or higher.
12. Click the ARC Entry icon (to the right of the calendar icon)
13. Click the Connect to Image icon in the ARC Check Entry window and then the process icon.

If you are a merchant experiencing difficulties accepting HSA cards from your clients and Forte sends you your monthly credit card merchant services statement, click here to register to accept HSA cards. Upon completion, contact Forte to update your merchant credit card processing account. Contact information for Forte should be printed at the top of your monthly credit card merchant services statement.

A "SERV NOT ALLOWED" message usually indicates that the merchant account with the credit card processor may not be set up for a specific card type. Note this message is returned by Vital. Vital can inform you as to why the transactions were declined by contacting them directly.

To resolve this issue, verify the merchant ID/transaction ID (MID/TID) have been entered on your account at Forte by calling your Sales Representative. For support with Vital merchant accounts, contact Vital; otherwise, contact Forte's Customer Service Department at 469-675-9920 x1.

For the latest version of the ABA database, see the following third-party resources:

• Federal Reserve Financial Services (ACH participants, wire participants, both)
• Accuity (official registrar of ABA routing numbers in conjunction with NACHA publish the ACH Participant Directory)

No. With a less day hold, Forte is basically advancing the money into your account without confirmation that the funds are available in your customer’s accounts. Forte also has to wait the standard hold time to determine if the funds are available in your customer’s accounts. On less than a standard hold time, every return you receive from your customer’s accounts (e.g., NSF, Stop Payment, Unauthorized, etc.), Forte will have to debit your settlement account for the previously funded transactions that were rejected (PFs). This may cause reconciliation difficulties simply because you will be receiving funds for transactions that you're not sure have successfully cleared your customer's accounts.

You can go to a less day hold; however, any merchant who wants a less day hold on his/her merchant account is required to send in the following documentation:

• Most recent two years of audited financials or unaudited financials accompanied with corresponding business tax returns
• Most recent bank statement
• A signed request from an authorized signer on the merchant account stating the desired hold time with a detailed explanation and the CS rep you spoke to regarding the request.

Also, you may be required to provide an up front or fixed reserve and/or the possibility of a per transaction price increase.

The following pair (trn: 987654321, acct: 987654321) will always yield a declined U02:ACCOUNT NOT APPROVED response on test. To receive a TEST APPROVAL response, please use another account number such as 8484848484.

Generally prior bank authorization is not required to initiate debits or credits. Some situations (e.g., corporate credit card or debit transactions) may require entities notify their financial institution or else risk the item being returned.

Forte's system flags transactions as R51 when transaction items or volume exceed certain thresholds that Forte has established for a particular Merchant ID. Many times items that are initially flagged as an R51 are allowed to be processed if a Risk Manager can approve the items, but if a Risk Manager is not able to approve the transactions before the end-of-day process, the items will reject. Merchants who are concerned with the future items rejecting as R51 should contact Risk Management and let them know that they had some items reject as R51 and would like to have an account review. Risk will evaluate the thresholds that have been established for the merchant for a potential increase. In the meantime, the merchant should resubmit the items rejected R51 for processing. Optionally, Forte will resubmit the R51 transactions on their behalf. To speak with Risk Management, call 469-675-9920 x8603.

Depending on how Forte receives the transactions, various response codes may be returned for EFT account on the "known bad" list:

Real-Time Integrations (AGI, SWP, or Virtual Terminal) and ATMVerify Transactions via Batch File Transmission

Transaction will be declined with a U02: ACCOUNT NOT APPROVED error message.

Batch File Transmission (Direct Billing, Transporter, or any software uploading a file containing a transaction)

Transaction will be approved for processing and returned on the origination date with one of the following error messages:

• R02: ACCOUNT CLOSED
• R03: NO ACCOUNT/UNABLE TO LOCATE ACCOUNT
• R04: INVALID ACCOUND NUMBER
• R13:RDFI NOT QUALIFIED TO PARTICIPATE
• R28: ROUTING NUMBER CHECK DIGIT ERROR

Forte recommends building a file containing a small quantity of debit (i.e., charge) or credit (i.e., refund) transactions each valued at ≤ $2.00. Prior to the first formal transmittal, upload the file to the root ("/") of your user account on ftp.paymentsgateway.net and request [email protected] review your file. After this initial preparation, complete the following steps:

1. Formally upload the file for processing as described in the file specification.
2. Await settlement of transmitted items. To update your internal systems with the item's settlement details, use the following resources:
• Virtual Terminal online reporting
• Programmatic Web Services (Client, Merchant, SPOT, Transaction Detail API) or "S"ettlement files made available in the 'dl' folder.
3. For items settled or funded to your account, build a file containing reversal transactions
4. Repeat the prior three steps as needed.

Click here to download Batch Transmission sample batch files.

-----BEGIN PGP PUBLIC KEY BLOCK-----

mQGiBDnTWtgRBADRPX9RN8MZSlNRyoAKaxOYgTsKgauYNer1d3 X9Q7O0awzrKfES
CnhUw95LDvwaGjj58DjUZDrDkW2N5S1WjXpPJepqA28zxQyrWB tvxtqRVpcEewiD
6ZUO8S+YGrvMvpfUwLuKUWkjxEMbX6ofXxooO00t6UZk8hUah1 DQVXGlBwCg/92U
DUldiy/X92QNDtIetmP7m90EAMoIb45c+G/UhTQCfhq8U7RmrEpx0xxdvdHoV344
gZRzF5pNnh5zbyW3onQjpH+ti7v58hYzcy1yNuPJLcY+T5jBe0 eCQ1PrkYhLmfSS
iAAd5Be+YgCGcb0KX0ku87dMgHRhmgjM3a8YrmJ/yxEsAA84SPOAtDC0tYJHOIzv
Ob+8BAC10ZZEpIYvqBMfmH+0e4I/7riBDowzVY4n7SAIbA/4qHo4lmzCBjJ7vpg6
0fSUbbEpdOrHKIQHTzGCeFWLdxxNzXedQh/tZYYACYPkpFxiVyi8bZqsDrbBiRku
rDogLDM5uwF61fCJ1k/x7IlxeL3jORJygLqbjqK+qfUFE7mxWLQwUGF5bWVudHNH
YXRld2F5IDxQcm9jZXNzaW5nQFBheW1lbnRzR2F0ZXdheS5uZX Q+iQBOBBARAgAO
BQI501rYBAsDAgECGQEACgkQUaPpPpkZVFzGHACcCA8ZypVyeW iZnmFovsOVa+gc
YrUAn1HmqQhPiVlKFO9Wo6Wmv76GcOQQuQINBDnTWtgQCAD2Ql e3CH8IF3Kiutap
QvMF6PlTETlPtvFuuUs4INoBp1ajFOmPQFXz0AfGy0OplK33TG SGSfgMg71l6RfU
odNQ+PVZX9x2Uk89PY3bzpnhV5JZzf24rnRPxfx2vIPFRzBhzn zJZv8V+bv9kV7H
AarTW56NoKVyOtQa8L9GAFgr5fSI/VhOSdvNILSd5JEHNmszbDgNRR0PfIizHHxb
LY7288kjwEPwpVsYjY67VYy4XTjTNP18F1dDox0YbN4zISy1Kv 884bEpQBgRjXyE
pwpy1obEAxnIByl6ypUM2Zafq9AKUJsCRtMIPWakXUGfnHy9iU siGSa6q6Jew1Xp
Mgs7AAICB/4qadF3lHmqtLlAci1FXs4TRTKRCHOVvZJ1tVOFcIv58bdQSFB0 yYxu
zu5bINDc9FJmeHo/AyVO1c+ureVp8cYcjqbu/v77yBLQegNalEvkiQw5vbHqE637
VnbFgDztw9vQ6JBEHl3iYcfy14hc09QwtxMo7jYa2204jokZG5 1+ZfeMICeijZjf
yNPAIU3jWsUfBOgPWBtTR8xNbvyCoJjWRX/dvl70mcPCXomyN/r5EgfJtOB75VM6
OJ5U79bCdHIWhPnIZ+C5lxo7wsKbmkezTxUfMknD+K/lYyexVg7cczrCwUBUjrDw
MdKn4uTozixpB/2zoLpd/il/GHaggzaxiQBGBBgRAgAGBQI501rYAAoJEFGj6T6Z
GVRcowUAoKXG5vrlZec+4R/JdqXTTfHOFLWwAJ9XWtTpbTdbeTEyT7SQ1ItpULNp
4A==
=bA9r

-----END PGP PUBLIC KEY BLOCK-----

Yes, you can send debits and credits in the same file for both NACHA type files and our file specification v3.0 or greater.

Viewing files from the FTP server requires a zip application, preferably WinZip, which you can download for free here. Once you've downloaded the file, change the name of the extension to .zip. Double click on the file and the WinZip dialog will display. Enter the processing password listed on your welcome letter and view the now readable file.

Refer to the Batch Transmission File Specification and the sample files for help building and sending transaction files. The following methods can be used to deliver your batch transmission file(s) to Forte:

• Developing internal systems to communicate and perform file management tasks as detailed in the Batch Transmission File Specification.
• Using the Transporter tool
• Manually managing your file transfers using an FTP client that supports one of the following protocols:
  • secureFTP (sFTP)
  • FTP/SSL implicit
  • FTP/SSL explicit
• For merchants unable to use Transporter or who do not have access to a secure FTP client, Virtual Terminal may be used with the following steps:
  • Log into Virtual Terminal.
  • Navigate to the Transaction menu.
  • Select Upload.
  • When prompted, enter the User ID and Password as detailed in the "Logging In" section of the Batch Transmission File Specification.

This issue can be caused by improper file name format. Make sure that the file is named properly according to the Batch Transmission File Specification.

The cause of this issue may be from the Class 3 and Class 2 Verisign PCA root certificate included in various releases of the SDK and JRE that expired on January 7, 2004. To solve this issue, import the Verisign Class 3 and Class 2 PCA root certificates into the J2SE certificates file (<java-home>/lib/security/cacerts):

1. Download the most recent Verisign PCA root certificates from http://www.verisign.com/support/roots.html
2. Unzip the downloaded file into the current directory.
3. Import the new Class 3 and Class 2 PCA root certificates into the cacerts file.

For more detailed instructions, click here.

To process a transaction between two clients, two transaction messages must be submitted in either of the following scenarios:

• The first sale transaction charges customer A and the second credit transactions refunds customer B.
• The first sale transaction charges customer B and the second credit transaction refunds customer A.

When you have composed AGI transaction messages you wish to enter into the Forte system, you will need system sign-on credentials. This consists of a Merchant ID and a processing password that should have been included in the new merchant's approval letter or package. To resolve any Merchant ID and password issues, please contact our Customer Service Department at 800-337-3060 x1 or [email protected].

Use the following test plan in the sandbox environment with AGI/SPOT messaging:

• Navigate to Virtual Terminal's login page.
• Click Demo.
• Replace the MID/USER/PASSWORD values with information referenced on your merchant welcome letter.
• Click Login.
• Navigate to Gateway Key under the Gateway Settings menu.
• Set API Login ID and Secure Transaction Key values.
• Click Update.
• Note the API Login ID/Secure Transaction Key values and treat these values as you would a password.
• Use the sandbox web service(s) to create client and payment tokens.
• Use tokens created in the previous point and send a transaction message to the TEST environment (or Transaction Test web service) as described in the AGI Integration Guide.
• From the Virtual Terminal, perform a transaction search and review the transaction details to ensure the transaction data was properly received.
• From the Virtual Terminal, perform a client search and review the client details tabs to ensure client, payment method(s), and recurring schedules were properly created.
• Perform additional tests as required by QA test plans.
• Log out of the Virtual Terminal.

If the final response is positive, UNK, or the account is not found, the transaction will be approved. If the final response has negative reports, the transaction will be declined. Transactions with a UNK response cannot be declined. If you do decline transactions with a UNK response, you run the risk of being able to use Check Verification.

Use the following AVS testing data in the Sandbox testing environment only. AVS testing in the Sandbox environment can only simulate the following results:

• Y = Match: Street Address and 5-digit Zip Code both match
• N = No Match: Street Address, 5-digit Zip Code, and 9-digit Zip Code all do not match.

CVV testing in the Sandbox environment can only simulate the following following results:

• M = Match
• N = No Match

Typically, the merchant includes the service fee in the transaction by specifying the service_fee field and including the amount of the service fee in the total amount of the transaction, or the authorization_amount field. For example, if a taxi company charges a $100 fare with a $3.00 service fee, the transaction request would include the following parameters:

{
   "service_fee":3.00,
   "authorization_amount":103.00
}

NOTE: Forte must configure a location to allow service fees.

Merchants using the 3DCart integrated shopping cart with Secure Web Pay should configure SWP with the following permissions:

When troubleshooting signed SWP request messages, forward the following elements (with sensitive values like account numbers and passwords masked) to [email protected] along with a description of the issue for review:

"pg_api_login_id=r2A8X5V2fj&pg_return_url=https://swp.paymentsgateway.net/
Redirect/results.aspx&pg_utc_time=634444438190000000&pg_transaction_order_number=237938
&pg_continue_url=&pg_schedule_quantity=&pg_schedule_frequency=&pg_schedule_start_date=
&pg_payment_method_id=&pg_payment_command=insert&pg_client_id=&pg_client_command=insert
&pg_ts_hash=713234d8812be62ccf0747a8a55656f6&pg_transaction_type=10&pg_version_number=
2.0&pg_valid_transaction_type=10,20&pg_valid_amount=1.00-5.00&pg_payment_card_type=
VISA&pg_payment_card_name=ACHD TEST&pg_payment_card_number=4111111111111111&
pg_billto_postal_name_first=ACHD&pg_billto_postal_name_last=TEST&pg_consumer_id=33333333333
&pg_consumerorderid=123456789012345&pg_walletid=abc123&pg_merchant_data_1=1000&
pg_merchant_data_2=9.95&pg_schedule_transaction=0&pg_payment_card_expdate_month=09
&pg_payment_card_expdate_year=2020&pg_total_amount=2.75&pg_procurement_card=
&pg_original_autorization_code=&pg_original_trace_number="

pg_ts_hash_response=3f674aadc230ecdf9797b63fa2365771
pg_last4=1111
pg_response_type=A
pg_response_code=A01
pg_response_description=TEST APPROVAL
pg_trace_number=57a5403f-972d-463d-a7f4-5355ef44d9ee
pg_authorization_code=123456
pg_payment_method_id=25983
pg_client_id=27397
pg_payment_card_exp=202009
pg_utc_time=634444440212894244
pg_return_url=https://swp.paymentsgateway.net/Redirect/results.aspx
pg_transaction_order_number=237938
pg_continue_url=
pg_schedule_quantity=
pg_schedule_frequency=
pg_schedule_start_date=
pg_payment_command=insert
pg_client_command=insert
pg_transaction_type=10
pg_version_number=2.0
pg_valid_transaction_type=10,20
pg_valid_amount=1.00-5.00
pg_payment_card_type=VISA
pg_payment_card_name=ACHD TEST
pg_billto_postal_name_first=ACHD
pg_billto_postal_name_last=TEST
pg_consumer_id=33333333333
pg_consumerorderid=123456789012345
pg_walletid=abc123
pg_merchant_data_1=1000
pg_merchant_data_2=9.95
pg_schedule_transaction=0
pg_payment_card_expdate_month=09
pg_payment_card_expdate_year=2020
pg_total_amount=2.75
pg_procurement_card=
pg_original_autorization_code=
pg_original_trace_number=

Secure Web Pay Checkout request parameters may be passed in the browser as part of the URL string:

Live:

• https://swp.paymentsgateway.net/co/default.aspx?request_parameter_1=value&request_parameter_2=value&......&request_parameter_xx=value

Sandbox:

• https://sandbox.paymentsgateway.net/swp/co/default.aspx?request_parameter_1=value&request_parameter_2=value&......&request_parameter_xx=value

Most Popular Usage Examples:

• https://swp.paymentsgateway.net/co/default.aspx?pg_api_login_id=abcdefgh (live)
• https://sandbox.paymentsgateway.net/swp/co/default.aspx?pg_api_login_id=ijklmnop sandbox)

The wsdl below is generated in the ObjectFactory class:

createTransactionResponse(TransactionResponse), for complexType Transaction, element Response (Line 122),
createTransactionResponse(TransactionResponse), for complexType TransactionResponse (Line 172)

These two methods have a name conflict. As a workaround, use a JXB file to change the name of the complexType "Transaction" to "Trans" in the JXB file as shown below and save it (e.g., cust.xjb). To import the file, use the following command:

wsimport -s . -b cust.xjb https://sandbox.paymentsgateway.net/WS/Transaction.wsdl

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<jaxb:bindings version="2.0" xmlns:jaxb="http://java.sun.com/xml/ns/jaxb"
  xmlns:xjc="http://java.sun.com/xml/ns/jaxb/xjc" xmlns:xs="http://www.w3.org/2001/XMLSchema"
  xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
  <jaxb:bindings schemaLocation="https://sandbox.paymentsgateway.net/WS/Transaction.wsdl#types?schema1" node="/xs:schema">
          <jaxb:bindings node="//xs:complexType[@name='Transaction']">
                  <jaxb:class name="Trans"/>
           </jaxb:bindings>
  </jaxb:bindings>
</jaxb:bindings>

You can arrange for clients to be returned to a custom page after a transaction in one of the following two ways:

1. pg_continue_url: After any payment has been completed Passor Fail, Forte will direct the client to this URL after he/she clicks the Continue button. If the merchant has specified a valid return URL, this field is ignored.
   
   

   <html>
   <form method='post' action= 'https://swp.paymentsgateway.net/default.aspx'>
   <table cellSpacing='0' cellPadding='0' border='0'><tr><td align='right' width='300'></td>
      <td align='left' width='200'><input type='hidden' name='pg_api_login_id' value='b743eomgg5'/></td>
        </tr><tr><td align='right' width='300'></td>
      <td align='left' width='200'><input type='hidden' name='pg_continue_url' value='http://www.somewebsite.com/page.aspx'/></td>
        </tr><tr><td align='right' width='300'></td>
      <td align='left' width='200'><INPUT TYPE=SUBMIT value='Pay Now'>
      <br>
      </td>
        </tr>
   </table>
   </form>
   </html>

2. pg_return_url: This is the page Forte will return the customer to after a transaction has completed. This page should contain a server-side script to parse the data being posted to it; however, it can be a static HTML page as well. If this field is not set or is invalid, the entire transaction is done on the Payments Gateway. In order to be a valid return url, the value sent must match at least one of the values in the Virtual Terminal.
   
   

   <html>
   <form method='post' action= 'https://swp.paymentsgateway.net/default.aspx'>
   <table cellSpacing='0' cellPadding='0' border='0'><tr><td align='right' width='300'></td>
      <td align='left' width='200'><input type='hidden' name='pg_api_login_id' value='b743eomgg5'/></td>
        </tr><tr><td align='right' width='300'></td>
      <td align='left' width='200'><input type='hidden' name='pg_return_url' value='http://www.somewebsite.com/page.aspx'/></td>
        </tr><tr><td align='right' width='300'></td>
      <td align='left' width='200'><INPUT TYPE=SUBMIT value='Pay Now'>
      <br>
      </td>
        </tr>
   </table>
   </form>
   </html>

When debugging an application using web services, it's useful to look to the SOAP XML that is transmitting the request and response messages. A tool such as HTTP Analyzer (or a tool that you may already have in your library) can be used to view request and response messages. For your reference, the messages are encapsulated between <s:Envelop ... ...</s:Envelop> tags.

If additional troubleshooting is required, forward the messages (with sensitive field value masked) to [email protected] along with your merchant ID and a description of the issue.