|
Is there technical documentation that I can reference? Please see this page.
When I completed the license agreement I was asked for a few different email addresses. Can you explain what these are for and if they all need to be unique? Please see this page.
I will be using only the non-registered customer system, in which the customer will enter their checking information directly into my order form. I have included the hidden field "ret_addr" in my form and I understand that this is the URL the customer is sent to after placing an order. My question is, what happens if the customer enters an invalid checking account number? In this case the customer receives a pre-defined error message stating that their checking information appears to be invalid. The customer is then invited to return to the order form to correct the information. Referring to the above question, what happens if the customer enters a valid account number, but is rejected by the national verification database? The customer receives a pre-defined message stating that their account information was not accepted by the national verification database. The customer is given specific information regarding their account and is invited to return to the order form to correct the information or to use a separate account. When a customer places an order from my order form, the information is then passed to a CGI on iTransact's secure server. What happens next? How do I know who the person is when returned to my page? Does iTransact pass info in the URL field? In order to keep a user session open, you can use the passback function. This function enables you to pass specific information to our CGI to identify the customer. This information is then passed back to your CGI as part of the URL, enabling you to keep a user session open. This is documented in the Passback information section. The "check_memo" field appears only on your "pre-registered" customer example form. May I use that field in my "non pre-registered" customer form as well, and be assured it will be printed on the check? Yes. The check_memo field can be used with any of the ordering options - and it will be printed on the check. Many of my customers are using the user name and passphrase option to place orders on my site. I know that I receive their name, address, etc. in the order confirmation email, but it would be nice if I could know that information immediately. Can this be done? Yes. The lookup function was built specifically for this purpose. Please see the information here. I'm setting up an order form on my site and I'm wondering if you have a listing of field names that are required and a list of those that are not required. Please see the Required & Non-Required Fields FAQ. What if I'd like to do recurring billing? If I have the customer pre-authorize monthly withdrawals, is it okay for me to initiate transactions on his/her behalf each month (such as via your merchant web page for manual check entry)? Yes, it is okay. The manual order entry form works perfectly for this. However, some merchants have built even more functionality into their recurring billings. Using a CGI, a merchant can generate monthly billings automatically. The CGI creates a form that is then submitted to our order CGI on a monthly basis. What about check numbers? If I do recurring billing, should I use the same check number each time? That could be confusing to my customer! You don't need to use check numbers. Many of our merchants who do recurring billing will use a check number for the first payment, but then will drop the check number for the remaining payments. As mentioned in the Required & Non-Required Fields FAQ, the check number is optional. Do you have other questions? If so, please go here. |
 Home | Services | Setup | Contact | Affiliates | Merchants | Demo | Prices | FAQs | About Us | Brochure | Legal | Search E-Mail| Phone: 801.298.1212 Copyright © iTransact, Inc.
|