How can I set up a continuous recurring transaction for my client?
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
When I attempt to write data to the SSL socket using Java, I get an exception. What's going on?
The javax.net.ssl.SSLHandshakeException:sun.security.validator.ValidatorException: No trusted certificate found exception can be caused by 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):
- Download the most recent Verisign PCA root certificates from http://www.verisign.com/support/roots.html
- Unzip the downloaded file into the current directory.
- Import the new Class 3 and Class 2 PCA root certificates into the cacerts file.
For more detailed instructions, click here.
How do I process a transaction between two clients?
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.
How do I resolve invalid Merchant ID and Password issues?
When you compose the AGI transaction message you want to submit to Forte, you will need account sign-on credentials to authenticate your request. This consists of a Merchant ID and a processing password that should have been included in your approval letter or package.
To resolve any Merchant ID and password issues, please contact our Customer Service Department.
What's a good sample Quality Assurance Test Plan for AGI/SPOT messaging?
Use the following test plan in Sandbox 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 username and password.
- Use the Sandbox web services to create client and payment tokens.
- Use the client and payment tokens you created in Step 9 to 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 Virtual Terminal.