1. Manuals
  2. Brands
  3. iTransact Manuals
  4. Gateway
  5. iTransact
  6. User manual

iTransact User Manual

Payment gateway
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
iTransact Gateway User's Guide

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the iTransact and is the answer not in the manual?

Questions and answers

Summary of Contents for iTransact iTransact

  • Page 1 Gateway User's Guide...
  • Page 2 Gateway User's Guide...

  • Page 4: Table Of Contents

    Table of Contents 1. Version and Legal Information ................... 1 2. Credit Card Merchant Accounts .................. 2 Which Credit Card Processing Platforms/Networks Is The Gateway Compatible With? What Information Is Required To Enable Credit Card Processing? ........2 FIRST DATA - Canada/NABANCO/FDMS SOUTH ........2 FIRST DATA - CARDNET ................
  • Page 5 Gateway User's Guide REQUEST_VALIDATION Errors ............. 175 REQUEST_FORMAT Errors ..............175 7. Deposits ......................176 How Long Do Deposits Take? ................176 Credit Card Deposits ................176 Check Deposits ..................176 8. Gateway Glossary ....................177 Glossary of Terms ................... 177...

  • Page 6: List Of Figures

    List of Figures 4.1. Control Panel Example ................... 6 4.2. Standard Virtual Terminal Welcome Section Example ..........7 4.3. Standard Virtual Terminal Order Section Example ............7 4.4. Standard Virtual Terminal Payment Section Example ........... 9 4.5. Standard Virtual Terminal Recurring Section Example ..........11 4.6.
  • Page 7 Gateway User's Guide 4.54. Form Wizard Instructions Example ............... 72 4.55. Form Wizard Items Example ................72 4.56. Standard Form Example ..................73 4.57. BuyNow Wizard Example ................... 75 4.58. Form Wizard Instructions Example ............... 76 4.59. BuyNow Wizard Items Example ................76 4.60.
  • Page 8 Gateway User's Guide 4.112. Exchange Setup Interface Example ..............138 4.113. Main Check Setup Interface Example ..............140 4.114. EFT Setup Interface Example ................141 viii...

  • Page 9: List Of Tables

    List of Tables 4.1. Background Example ................... 44 4.2. Background Color Example .................. 44 4.3. Font Color Example ..................... 44 4.4. Active Link Example ................... 44 4.5. Link Example ..................... 45 4.6. Visited Link Example ..................45 4.7. MerText Example ....................45 4.8.
  • Page 10 Gateway User's Guide 5.31. MerchantUpdates Email Example ............... 162 5.32. Account Suspension Email Example ..............162 5.33. Account Closure Email Example ................ 163 5.34. Account Re-Activation Email Example ..............163...

  • Page 11: Version And Legal Information

    Chapter 1. Version and Legal Information iTransact Gateway User's Guide iTransact Gateway User's Guide Version: 2.12 Date: 2/2/12 Copyright: iTransact, 2012...

  • Page 12: Credit Card Merchant Accounts

    Chapter 2. Credit Card Merchant Accounts Which Credit Card Processing Platforms/Networks Is The Gateway Compatible With? What Information Is Re- quired To Enable Credit Card Processing? Our software is certified on most of the main credit card processing networks. If you do not have a mer- chant account, please contact your sales rep.

  • Page 13: Ndc/Global Atlanta East

    Credit Card Merchant Accounts Required Information • Client/ISO/Bank Number (4 Digits) • Merchant Number (12 Digits) • Terminal Number (3 Digits) NDC/GLOBAL ATLANTA EAST Account MUST be Terminal-Based Required Information • Bank ID Number (6 Digits) • Terminal Number (7 - 13 Digits) ELAVON/NOVA VAR Type: PaymentClearing Account Settlement Type MUST be Manual - Not Auto...
  • Page 14 Credit Card Merchant Accounts Required Information • Terminal ID/V# (7 or 8 Digits) • Merchant Number (12 Digits) • Bank ID Number / BIN (6 Digits) • Terminal Number (4 Digits) • Store Number (4 Digits) • Agent Number (6 Digits) •...

  • Page 15: Transaction Formats

    Chapter 3. Transaction Formats Should I Use The HTML Connection Method Or The XML Connection Method? You can communicate with the gateway via an HTML form post or via an XML query request. Full functionality of the software's features can be utilized in either case. Why Should I Use The HTML Connection Method? The HTML Connection Method utilizes an HTTPS form post to pass information securely from your or- der form to our transaction servers.

  • Page 16: The Control Panel

    Chapter 4. The Control Panel What Are The Features Of The Control Panel? How Do I Log In? The Control Panel is an excellent interface that allows a merchant the ability to manage and use all as- pects of the Gateway Software account. A merchant can log into and access the Control Panel. To log in, a merchant will need to provide their five digit gateway ID and the then current gateway password.

  • Page 17: Standard Virtual Terminal Welcome Section Example

    The Control Panel to their online store front websites. However, some merchants use it as their credit card processing sys- tem at their brick and mortar store fronts. This simple interface enables a merchant to process a custom- er's credit card manually without having to incur the expense of purchasing a credit card swipe terminal. This interface can also be used in conjunction with a manual USB magnetic card reader that will auto- matically populate the fields for a merchant.
  • Page 18 The Control Panel Some of the entry fields in this area are required and others are optional (See Standard Virtual Terminal Order Section Example). A merchant can choose to enter up to ten separate items plus shipping and tax amounts, or can submit a single item which is a total of the amount to be billed to the customer. To ac- cess items 6-10, please use the scroll bar on the left side of the "Total"...

  • Page 19: Standard Virtual Terminal Payment Section Example

    The Control Panel transaction in this interface. If the Include Shipping checkbox is selected, there must be a value in this field. • Include Tax Checkbox - This should be selected if a merchant would like tax to be a separate line item.
  • Page 20 The Control Panel dashes or spaces. • Exp. Date - The expiration month and year should be selected in this area. • Approval Code - The value for this field can only be obtained directly from the Credit Card Merchant Account Processor's Voice Approval phone service. This feature should only be used if a "call authorization center"...

  • Page 21: Standard Virtual Terminal Recurring Section Example

    The Control Panel Recurring Information Section If your transaction needs to be set as a recurring transaction, click the "Toggle" button to display the ap- pripriate entry fields. Figure 4.5. Standard Virtual Terminal Recurring Section Example Recurring Fields • Recipe Name - This drop down menu displays all of a merchant's pre-built recipes, which will provide the rules and schedule by which a transaction will re-bill when set with at least one remain- ing repetition.
  • Page 22 The Control Panel • Billing Information - All fields here are required unless otherwise indicated. • First Name - This should be the customer's first name. • Last Name - This should be the customer's last name. • Address - This should be the cardholder's street address as listed with the account issuer. •...

  • Page 23: Classic Virtual Terminal Welcome Section Example

    The Control Panel To submit a transaction through this interface, enter the correct data into the required fields and any of the desired optional fields. Be sure to double check the credit card number as well as the amount of the charge.

  • Page 24: Classic Virtual Terminal Transaction Information Section Example

    The Control Panel Figure 4.9. Classic Virtual Terminal Transaction Information Section Example At the top of this interface, there are links to the Recurring Transaction virtual terminal and the Swipe Card interface. The top of the form also identifies the merchant and displays the five digit gateway ID. •...

  • Page 25: Classic Virtual Terminal Payment Section Example

    The Control Panel • Phone Number - This should be a contact phone number for the customer. • Email Address - This should be the customer's email address. The transaction confirmation email will be sent to this address. • Item Description - A merchant should enter the name of the product that a customer is purchas- ing in this field.
  • Page 26 The Control Panel This section allows a merchant to enter either credit card information or checking account information. After the appropriate fields are filled out, a merchant can submit the payment by clicking on the "Pro- cess Payment" button. • Credit Card Information - A merchant can use these fields if the customer would like to pay with credit card.

  • Page 27: Classic Virtual Terminal Shipping Section Example

    The Control Panel is never paid to the merchant. • Checking Account Information - These fields will be enabled if a merchant selects the Check Pay- ment Method radio button. • ABA Number - This is the nine digit ABA Routing number for a customer's bank. These are generally the first nine numbers listed in the line of numbers across the bottom of a check.

  • Page 28: Swipe Virtual Terminal Welcome Example

    The Control Panel Submitting a Transaction Through The Virtual Terminal Interface (Classic) To submit a transaction through this interface, enter the correct data into the required fields and any of the desired optional fields. Be sure to double check the credit card number as well as the amount of the charge.

  • Page 29: Swipe Virtual Terminal Transaction Information Example

    The Control Panel Initial Transaction Information Section Figure 4.14. Swipe Virtual Terminal Transaction Information Example Some of the entry fields in this area are required and others are optional. A merchant can choose to enter up to three separate items plus shipping and tax amounts, or can submit a single item which is a total of the amount to be billed to the customer.
  • Page 30 The Control Panel • Item Description - A merchant should enter the name of the product that a customer is purchasing in this field. This information will be recorded in the merchant's Transaction Listing in the Control Panel and in the Merchant/Customer confirmation emails. Some merchants choose to enter all of the items in a single line item - either with each item detailed, or with a generic description like "Pur- chased Items".

  • Page 31: Swipe Virtual Terminal Entry Section Example

    The Control Panel Swipe Card Entry Section By clicking the button and then swiping the credit card through a compatible USB-Connected magnetic card swipe reader, this section will be automatically populated by the encrypted data embedded in the magnetic strip on the back of the card. Figure 4.15.

  • Page 32: Approval Page Example

    The Control Panel • City - This should be the cardholder's city as listed with the account issuer. • State - This should be the state abbreviation of the cardholder as listed with the account issuer. • ZIP - This should be the cardholder's postal code as listed with the account issuer. •...

  • Page 33: Swipe Express Welcome Section Example

    The Control Panel Swipe Card Interface (Express) The Express Swipe Card entry area allows a merchant to enter minimal information and swipe a credit card to attempt a transaction. This interface is to be used by merchants who are using a compatible USB- Connected magnetic card swipe reader.

  • Page 34: Approval Page Example

    The Control Panel • Order Total - The value of this field should be the total amount being charged to the customer. For an AVSOnly credit card transaction, this value should be 0.00. • Email - If a merchant fills in this field with the customer's email address, an receipt will be emailed directly to the customer.

  • Page 35: The Account Settings - How Do I Modify My Information

    The Control Panel The Account Settings - How Do I Modify My Information? The Account Settings interface is used to update contact information, anti-fraud features, email settings, and general transaction functions. Please remember, any changes to data in this interface require the user to click the "UPDATE" button at the bottom of the Account Settings interface.

  • Page 36: Account Settings General Section Example

    The Control Panel 3) Must include at least two different character groups (lowercase letters, uppercase letters, digits, punctuation) 4) Cannot include the same character repeated three times (like aaa or 555) or a sequence of three characters (like xyz or 789) 5) Cannot include dictionary words, including common names.

  • Page 37: Account Settings Advanced Features Section Example

    The Control Panel several individuals to receive these emails, please have your Network Administrator/Email Manager setup a multi-recipient alias address and use that to populate these fields. This interface also allows mer- chants to opt-in to the failure emails and the MerchantUpdates email list. Here is a more in depth ex- planation of each of these settings: •...

  • Page 38: Account Settings Test Section Example

    The Control Panel select the appropriate time. "MANUAL" should be selected by merchants who want to settle each of their own batches using the "Settle Now" tool in the Settlement Options area of the Control Panel. • The Order Form UID Value - This is the preferred option to be used as the value for the "vendor_id"...

  • Page 39: Account Settings Fraud Controls Example

    The Control Panel The Fraud Control Settings These settings are provided as additional protection against potential fraud. Each of these features are optional. A merchant may use as many of these features as they desire. None of these features can com- pletely prevent all types of fraud, but these are some of the most powerful anti-fraud options available on any gateway software available today.

  • Page 40: Ip Filter Settings Example

    The Control Panel Figure 4.29. IP Filter Settings Example • Restrict Order By IP - This feature allows a merchant to allow HTML-based transactions only from specific IP addresses. This is activated and used by merchants who will be making all of their customers' order submissions from their own server directly to our system.
  • Page 41 The Control Panel played to the user with a dynamically generated image containing random characters after order sub- mission. The user must enter these characters correctly to complete the transaction submission. If a merchant is logged into an open session of the Control Panel, and submits a transaction through their website, it will not prompt the merchant for the entry.
  • Page 42 The Control Panel processor based on information located in the bank's AVS database (which may or may not match the bank's statement database). However, the gateway system will perform the Auto-Void according to the requirements set by the merchant. These settings may be modified by the mer- chant at any time.

  • Page 43: Account Settings Card Section Example

    Void If CVV Not Entered - With this setting a customer's transaction will be voided if the bank indicates that a CVV code should exist on the card, but was not entered. • Note - The iTransact gateway does not perform CVV auto-voids for American Express trans- actions. Card Processing Settings This area will only display if the Card Setup has been completed.

  • Page 44: Account Settings Check Section Example

    • Background Image - This needs to be the absolute URL of an image. You can upload this image to the secure server by submitting a ticket at http://support.itransact.com. • Header Border Color - This can be a six digit hexadecimal value or you can use the color bar tool to select the desired color.

  • Page 45: The Merchant Toolkit - What Information Should I Give To My Web Designer

    The Control Panel A helpful color bar tool is displayed when a merchant clicks into one of the color entry fields. This al- lows a merchant to click on the desired color and it will automatically populate the corresponding field. Figure 4.33.
  • Page 46 The Control Panel Transaction Testing...

  • Page 47: Html Toolkit Example

    The Control Panel A merchant can run tests on the order forms and shopping carts being used for their account. Please ref- erence THIS area of this documentation for full details. Recurring Transactions A merchant can use the gateway's Recurring Transaction system to bill customers according to a sub- scription or according to a set schedule.

  • Page 48: Html Order Form Template Section Example

    The Control Panel • Form Post and Input Field Details - This link opens a window which includes the list of required and optional fields for the Standard Form-Based order page, a Split Form-Based order page, and a Buy-Now Form-Based order page. •...

  • Page 49: Html Form Functions Section Example

    The Control Panel • Credit Card Templates - These links open demonstrations of Standard Form-based order pages that only accept credit cards. One example includes a form that allows for a separate shipping ad- dress. Please remember that the credit card banks can not verify alternative shipping addresses. •...
  • Page 50 The Control Panel from the gateway via the "query_string" or via the HTML Post. • The Passback Function - This feature allows a merchant the ability request and receive information that was submitted as a part of the order form post submission. This feature can be used to access any of the data that can not be retrieved via the Lookup Function.
  • Page 51 The Control Panel cc_name - Returns the name of the card type used. "Visa", for example. total - Returns the transaction total. test_mode - Returns "1" if your account is in test mode or "0" if it is not in test mode. when - Time/date stamp in format of "20010509134443"...

  • Page 52: Advanced Html Features Section Example

    The Control Panel cure server. Otherwise your customer's will receive a security warning. • When using ret_mode with the "post" option, your ret_addr URL may be on a secure (https) or non-secure (http) server. In either case, the page will be displayed securely as an emulated page in the secure server environment.

  • Page 53: Customizable Html Section Example

    The Control Panel tion pages. The JavaScript must be copied completely and must exist within your order form between the HTML tags of <HEAD> and </HEAD>. Please modify the POST URL so that it re- flects this: • PGP Signature Verification - To utilize this feature, a merchant's server must have PGP installed. This feature allows a merchant to verify that any Passback and Lookup values received in the URL string were sent by the gateway processing server.

  • Page 54: Background Color Example

    Table 4.1. Background Example <INPUT type="hidden" name="background" value="https://secure.itransact.com/images/background/yourimage.gif"> Follow the instructions listed in the Toolkit to upload the necessary images. • bgcolor (This tag allows you to designate the background color of the final checkout page.) Table 4.2.

  • Page 55: Link Example

    The Control Panel <INPUT type="hidden" name="alink" value="red"> • link (This tag allows you to designate the color of a link.) Table 4.5. Link Example <INPUT type="hidden" name="link" value="blue"> • vlink (This tag allows you to designate the color of a visited link.) Table 4.6.
  • Page 56 The Control Panel • show_items (This tag allows you to display the order items, quantities, and costs of the items be- ing purchased on final checkout page.) Table 4.10. Show_Items Example <input type="hidden" name="show_items" value="1"> • Header Graphic Commands - This line allows you to call an order form that displays your company's logo across the top of the final check out page.

  • Page 57: The Transaction Listing - How Can I View My Transactions

    The Control Panel • If using PHP, a merchant may use the CURL Library functions found at ht- tp://www.php.net/manual/en/ref.curl.php. • The XML Connection method is not activated on a gateway account by default. If a merchant desires to use the XML Connection method, an XML activation request needs to be sent to the sales rep. Also, be sure to enable the XML API in the Account Setting section of the Control Panel.
  • Page 58 The Control Panel • Download Data Options - By selecting CSV or XML in the drop down menu and clicking the "GO" button, a file will download that includes the details of all of transactions in the opened date range. •...
  • Page 59 The Control Panel Review the Transaction Detail "Error Message" field for the specific reason for failure. See the section to review the possible "Response" values. • AVS - This column is blank for check or EFT transactions. The value is the response received from the processing network to indicate whether the address and ZIP Code matched the credit card's ac- count address on file in the bank's AVS database or not.
  • Page 60 The Control Panel G - Global Non-AVS participant. Non-U.S. Card issuing bank does not support AVS. I - Address information not verified for non-US transaction. M - Address and postal code match for non-US transaction. N - Neither the Address nor ZIP Match. P - Postal code match for non-US transaction.

  • Page 61: Cvv Responses

    The Control Panel Visa A - Address matches, ZIP Code does not. E - Transaction is ineligible for address verification. G - Global non-participant. Foreign card. Cannot verify address. N - Neither the ZIP nor the address matches. R - Issuer's authorization system is unavailable. Try again later. S - AVS not supported at this time.

  • Page 62: Advanced Transaction Listing Example

    The Control Panel • LAST NAME - This value is the customer's last name as submitted with the transaction informa- tion. • AUTH # - This is the authorization code issued by the credit card issuing bank for approved transac- tions.
  • Page 63 The Control Panel...
  • Page 64 The Control Panel Transaction Details This search section searches using card information. These are the explanations of search criteria: • Type - Use this drop down to view a certain kind of transaction (i.e. Order, Credit, Void, Postauth). This defaults to "All" and allows for a search for any transaction type. •...
  • Page 65 The Control Panel • City - This will search for transactions submitted from a specific city. • State - This allows for transactions to be searched for using the state as the criteria. • Zip - This searches transactions generated using a specific ZIP Code. •...

  • Page 66: The Transaction Detail Window - How Can I View My Customer's Information

    The Control Panel • Email - A merchant can search for all transactions submitted with a specific email address. • Ext Cust ID - This can be used to search for a specific transaction that was submitted with the "cust_id" field. Transaction Date Information This section is the cornerstone of the entire search mechanism.
  • Page 67 The Control Panel The Transaction Information Section This section includes the same information displayed about a transaction in the Transaction Listing (see the section detailing this). This is the definition of each of those fields: • DATE AND TIME - This value is the date and time of the original transaction attempt. •...
  • Page 68 The Control Panel • ACTION - This field identifies what type of transaction was submitted. • STATUS - The field identifies whether a transaction was successful or not. Potential values are lis- ted below: • Ok - Valid Transaction • Incomplete - Generally indicates transaction is currently in process.

  • Page 69: Options Window Example

    The Control Panel Figure 4.43. Options Window Example...
  • Page 70 The Control Panel...

  • Page 71: Recurring Detail Window Example

    The Control Panel The features displayed are the options available for a successful sale transaction. In addition to these, the Postauth option is available on Pre-Authorized transactions. Here is what these features do: • Void - This feature can be used to cancel sale, resubmit, postauth, or refund/credit transactions. Voids may only be issued prior to the batch settlement for the open batch that the original transac- tion is processed in.
  • Page 72 The Control Panel Please review THIS for information about this feature. The Customer Information Section The Customer Information displays the information that was entered concerning the cardholder at the time of the transaction. This is the definition of each of those fields: •...
  • Page 73 The Control Panel tempt. The Transaction Data Section This area provides information about how a transaction was submitted and the status of the transaction. • Last Four - These are the last four digits of the credit card number. This is not listed for check or EFT transactions.

  • Page 74: The Batch Settlement Options Window

    The Control Panel • Item Explanation - Displays item number. • Cost - This value is the price of each quantity of an item. This value is multiplied by the "Qty" value to populate the "Tot" field. • Desc - This value is the description of the item submitted with the transaction. •...
  • Page 75 The Control Panel The Credit Card Settle Now Tool This allows a merchant to run settlement at any time without the assistance of Gateway Service Techni- cians. When the "GO" button is selected, the account will begin the settlement request for the account. Batch settlements may take a few minutes depending on the number of transactions in the open batch and network traffic.

  • Page 76: The Form Wizard - How Can I Generate An Order Form For My Site Quickly

    Settle Now tool. The NACHA Download Tool If you are authorized by your bank and iTransact to use the NACHA payment system, your NACHA formatted files will be available to download in this interface. The interface creates a plain text (.txt) file with your NACHA data.

  • Page 77: Form Wizard Example

    The Control Panel Figure 4.48. Form Wizard Example Generating Split Forms The Split Form format is used by merchants who do not have their own secure servers. This enables a customer to enter non-secure information on the merchant's server and enter the secure billing informa- tion on the gateway's secure server.

  • Page 78: Split Form Wizard Example

    The Control Panel Access the Form Wizard. Chose the Secure "Split" Form option. A new window will open. Figure 4.49. Split Form Wizard Example Enter your UID. This number is listed in your Account Settings. Enter the correct address for the Return URL. This will be the address of the page or script that a customer will be directed to after a successful transaction.

  • Page 79: Form Wizard Instructions Example

    The Control Panel 11. A dialogue box will open displaying instructions for the rest of the Form Wizard (See Form Wizard Instructions Example). Figure 4.50. Form Wizard Instructions Example 12. Immediately, a second window, the Order Form Items page, will open (See Form Wizard Items Ex- ample).

  • Page 80: Split Form Example

    The Control Panel • Format B - This style allows for the purchase of multiple quantities of an item by entering the quantity value into a textbox. • Format C - This style allows a customer to select the item by clicking the checkbox and choos- ing the quantity from a drop-down menu.

  • Page 81: Standard Form Wizard Example

    The Control Panel 17. Right-click with the mouse on the form page and view the source of the page. Copy and save that source, edit/modify it as needed, and upload the page into your website. Generating Standard Forms Standard Forms should only be used by merchants who have their own secure servers and meet CISP/ PCI standards.

  • Page 82: Form Wizard Instructions Example

    The Control Panel Select the appropriate check marks for the payment types to display on the payment page. A mer- chant should only select a payment type for which they are approved to accept. Select the appropriate check marks for Credit Card Acceptance Options. None of these features are required.

  • Page 83: Standard Form Example

    The Control Panel 13. The "A B C" layout options determine the way an item will display on an order form page. A mer- chant may use the same format for each item, or any combination of formats on a form. Here are examples of each: •...
  • Page 84 The Control Panel 17. Right-click with the mouse on the form page and view the source of the page. Copy and save that source, edit/modify it as needed, and upload the page into your website's secure server. Generating BuyNow Buttons...

  • Page 85: Buynow Wizard Example

    The Control Panel BuyNow buttons are used by merchants who do not have their own secure servers. This enables a cus- tomer to choose an item on the merchant's server and enter the secure billing information on the gate- way's secure server. Building a BuyNow button using the Form Wizard is an easy process. By filling out the fields in the wizard, it will generate a button, or an entire form, that can be added to a merchant's site.

  • Page 86: Form Wizard Instructions Example

    The Control Panel required. If a merchant would like to display an entry field for a shipping address, the "Allow Separate Ship- ping Address" must be checked. This feature is optional. 10. If a merchant would like to display an entry field for a CVV security code, the "Allow CVV Entry" must be checked.

  • Page 87: Buynow Example

    The Control Panel 14. In the "Name" field, enter the item (in this example, that value is ITEM 1). 15. In the "Cost" field, enter the cost of the item (in this example, the cost is $5). 16. In the Description field, enter a message about the item (in this example, the description is "This item is fantastic!").

  • Page 88: The Auction Payme Interface - Can I Use My Account For Auction Sales

    The Control Panel The Auction PayMe Interface - Can I Use My Account For Auction Sales? For merchants who sell items at online auctions sites, one of the biggest frustrations is receiving pay- ment from the winning bidder in a prompt manner. The Auction PayMe system solves the problem. With very little effort, a merchant can obtain instant check or credit card payments from bid winners us- ing the Auction PayMe secure transaction services--even if they don't have their own web site.

  • Page 89: Auction Payme Request Email Example

    The Control Panel • Bid Amount - This value should be the amount of the winning bid (enetered without "$"). • Type of Payments to Accept - These checkboxes will indicate to the gateway which payment fields will display when a customer access the Auction PayMe page. •...

  • Page 90: Payment Success Page Example

    The Control Panel The payment will be attempted, email confirmations will be sent, and the customer will be shown a suc- cess message if the transaction is successful. Figure 4.64. Payment Success Page Example The Recurring Transaction Window - How Does The Recurring Billing System Work? The window can be accessed from the Recurring Transaction link in the Control Panel, the "List Re- cipes"...
  • Page 91 The Control Panel Considerations • A Recurring Recipe is the schedule which contains the instructions as to when a recurring transac- tion is billed. The Recurring Repetitions/Remaining Repetitions is the number of times that a trans- action follows the recipe. Once a transaction is set as a Recurring Transaction, it will continue to fol- low the recipe until the number of repetitions cycles down to or is manually set to zero.

  • Page 92: Recurring Recipe Builder Example

    The Control Panel the form that will automatically create future recurring charges, based on the details that you provide. In addition, you may also modify previously submitted transactions and mark them as re- curring. This is done via the Transaction Listing. •...
  • Page 93 The Control Panel...
  • Page 94 The Control Panel Recipe Name When selecting a recipe name, please remember that it will be case-sensitive (must be lowercase) and can be only one word. Any alpha-numeric characters can be used. You should make it easy to remem- ber. For instance, you may want to name a recipe "1stofmonth" if it's designed to bill on the first day of the month.
  • Page 95 The Control Panel tempt fails, that transaction will be put "on hold" automatically to prevent future billing attempts so that account information can be updated (either by the merchant or the customer). If this is enabled, the re- curring postback will include the "on hold" parameter to notify if this has been triggered due to a failure. The Allow Customer Update Function This feature is available for credit card transactions only.

  • Page 96: Transaction Listing Example

    The Control Panel <RecurringData> <RecurRecipe>monthly13</RecurRecipe> <RecurReps>6</RecurReps> <!-- Optional (For Split Recurring) --> <RecurTotal>100.00</RecurTotal> <!-- Optional (For Split Recurring) --> <RecurDesc>test2</RecurDesc> <!-- Optional (For Split Recurring) --> </RecurringData> Manual Recurring Activation This manual activation method can be used for transactions that were submitted via HTML or XML. Once a sale transaction has been processed successfully, it can be set as a recurring transaction by fol- lowing these simple steps: Log into the Control Panel and open the Transaction Listing for the day when the original transac-...

  • Page 97: Transaction Detail Example

    The Control Panel In the Transaction Detail Screen, click on the "GO" button in the "RECUR" column. Figure 4.69. Transaction Detail Example...

  • Page 98: Recurring Detail Example: Non-Recurring Transaction

    The Control Panel In the Recurring Detail window, enter the number of repetitions (number of times a transaction needs to rebill) and choose the Recurring Recipe Name from the drop down menu. If you need to change the amount to be billed or the items, uncheck the "Use Original Order Items" box and edit- ing and additional line tools will display.

  • Page 99: Recurring Virtual Terminal Welcome Section Example

    The Control Panel Recurring Activation In The Virtual Terminal The Recurring Transaction Virtual Terminal Interface can be accessed by opening the Standard Virtual Terminal interface. Choosing this interface allows for the entry of multiple Order Items, as well as sep- arate shipping and tax charges.

  • Page 100: Recurring Virtual Terminal Transaction Information Section Example

    The Control Panel This Initial Transaction Information section is where a merchant enters the general customer information when generating the initial charge. This same general information will be default information for future recurring transactions (unless the user information is modified in the Recurring Transaction Detail inter- face).

  • Page 101: Standard Virtual Terminal Payment Section Example

    The Control Panel • Item Total - This value is arrived at when the Virtual Terminal automatically multiplies the value of the Item Qty and the Item Price for a single item. • Total - This amount is the sum of the Item Totals for all items purchased. •...
  • Page 102 The Control Panel To begin to enter payment information, a merchant must select the radio button for the custom- er's payment method (either Check or Credit Card). This radio button will enable the appropriate/re- quired fields for the payment type and disable the others. •...

  • Page 103: Standard Virtual Terminal Recurring Section Example

    The Control Panel are generally the first nine numbers listed in the line of numbers across the bottom of a check. • Account Number - This is the customer's checking account number as it appears on a check. • Account Type - (For EFT Transactions Only) A merchant needs to use the selection tool to indicate whether the customer's checking account is a Personal or a Business checking account.

  • Page 104: Standard Virtual Terminal Information Section Example

    The Control Panel repetitions by one until it reaches zero. • Recurring Total - If the amount that is to recur is the same as the total amount listed in the Initial Transaction Information, please leave this blank. This feature can be used in conjunc- tion with Recurring Recipes designated by the merchant as a "Split Amount"...

  • Page 105: Approval Page Example

    The Control Panel • Address - This should be the cardholder's street address as listed with the account issuer. • City - This should be the cardholder's city as listed with the account issuer. • State - This should be the state abbreviation of the cardholder as listed with the account issuer. •...

  • Page 106: Transaction Listing Example

    The Control Panel Modifying Recurring Transaction Information Through The Transaction Listing Recurring information can be modified so that future recurring attempts will be made using updated in- formation. Updating the data for a recurring transaction does not change information applied to the ori- ginating transaction itself, only future transactions.

  • Page 107: Transaction Detail Example

    The Control Panel In the Transaction Detail screen, click on the "GO" button in the "RECUR" column (to change the recipe being used and/or the remaining repetitions) or click on the "GO" button in either the "Edit Recurring User Info" section (to update the customer's billing or address information) or the "Edit Recurring Item Info"...
  • Page 108 The Control Panel The Recurring Information Area When a transaction is set to be a recurring transaction this area will display. • Start Date - The day of when a transaction was set as a recurring transaction. This date may or may not coincide with the date of the original transaction.

  • Page 109: Recurring Detail Example: Recurring Transaction

    The Control Panel tempts on the specific transaction. • Edit Recurring User Info - This "GO" button opens the interface where the cardholder's in- formation can be modified for future recurring transactions. • Edit Recurring Item Info - This "GO" button opens the window that allows a merchant to modify the amount and description of recurring transactions.

  • Page 110: Recurring User Info Editing Interface Example

    The Control Panel if a transaction has ever been a recurring transaction - even if the transaction is no longer re- curring. Be sure to click the "GO" button in the "UPDATE" column. • A merchant can modify both of these fields to modify a recurring transaction. Be sure to click the "GO"...
  • Page 111 The Control Panel Click into the field that needs to be modified, delete the value, and enter the new value. Remember, any changes to any of the fields in the "CARD INFO" section require that the credit card number is entered - even if the card number is the same card number currently on file.

  • Page 112: Recurring User Info Changed Example

    The Control Panel Figure 4.83. Recurring User Info Changed Example Either click the "Go Back" button to edit any other data or click the "Submit Changes" but- ton to update the information, at which point the success page will display (See Figure 4.18).

  • Page 113: Recurring Items Editing Interface Example

    The Control Panel • When changing the transaction information in the "Edit Recurring Item Info" interface, the Items Editing window is opened (See Figure 4.19). Figure 4.85. Recurring Items Editing Interface Example...

  • Page 114: Recurring Items Changed Example

    The Control Panel To delete an item, click the checkbox in the "Delete" column and enter a new item (including Description, Quantity and Price) - OR - Modify the current item by clicking in- to the field and changing the value. The "Clear"...

  • Page 115: Xmltrans2.Cgi Recurupdate Example

    The Control Panel Modifying Recurring Transaction Information Using XML The RecurUpdate This request allows you to modify the number of remaining repetitions for a recurring transaction. Table 4.20. XMLTrans2.cgi RecurUpdate Example <?xml version="1.0"?> <ItransactInterface> <VendorIdentification> <-- Can also be API Credentials --> <VendorId>XXXXX</VendorId>...

  • Page 116: Xmltrans2.Cgi Recurupdateresponse Example

    The Control Panel </OrderItems> <!-- To use the Total element the original transaction can only have one item associated with it --> <Total>5.00</Total> </RecurUpdate> </ItransactInterface> The RecurUpdateResponse This request will return the following response: Table 4.21. XMLTrans2.cgi RecurUpdateResponse Example <?xml version="1.0" standalone="yes"?> <ItransactInterface>...

  • Page 117: Transaction Listing Example

    The Control Panel Table 4.23. XMLTrans2.cgi RecurDetailsResponse Example <?xml version="1.0" standalone="yes"?> <ItransactInterface> <RecurDetailsResponse> <Status>ok</Status> <ErrorCategory></ErrorCategory> <ErrorMessage></ErrorMessage> <TimeStamp>20040621154341</TimeStamp> <TestMode>0</TestMode> <RecurDetails> <RemReps>10</RemReps> <RecipeName>daily</RecipeName> <RecurTotal>1.00</RecurTotal> </RecurDetails> </RecurDetailsResponse> </ItransactInterface> Placing Recurring Transactions On Hold and Off Hold Placing a transaction on a temporary hold to prevent billings is simple. Log into the Control Panel and open the Transaction Listing for the day when the original transac- tion was processed.

  • Page 118: Transaction Detail Example

    The Control Panel In the Transaction Detail screen, click on the "No" link in the "On Hold" row of the Recurring In- formation area. Figure 4.89. Transaction Detail Example...

  • Page 119: Recurring Detail Example: Recurring Transaction

    The Control Panel A window will pop up to verify that you want to place the transaction on hold. Click "OK". The setting will change from "No" to "Yes". This will temporarily prevent future recurrings (if done anytime prior to 11:59 PM Mountain time on the day before the next scheduled transaction) for as long as you deem necessary.

  • Page 120: Transaction Listing Example

    The Control Panel The transaction can be taken off hold following the same steps as above (but by clicking on the "Yes" and toggling it to "No"). Canceling Recurring Transactions Taking a transaction out of the recurring cycle is easy to do. Log into the Control Panel and open the Transaction Listing for the day when the original transac- tion was processed.

  • Page 121: Transaction Detail Access Window Example

    The Control Panel From the Transaction Detail request screen, click the "Get Detail" button. Figure 4.92. Transaction Detail Access Window Example In the Transaction Detail screen, click on the "GO" button in the "RECUR" column. Figure 4.93. Transaction Detail Example...

  • Page 122: Recurring Detail Example: Recurring Transaction

    The Control Panel On this page, click "Edit Setup". Figure 4.94. Recurring Detail Example: Recurring Transaction...

  • Page 123: Recurring Setup Edit Page Example: Recurring Transaction

    The Control Panel The Recurring Setup Edit page will open. into the "REPETITIONS" field, delete the value, enter a zero in that field and click the "GO" button in the "UPDATE" column. This will stop future recur- rings (if done anytime prior to 11:59 PM Mountain time on the day before the next scheduled trans- action).

  • Page 124: Recurring Transaction Recipe Window Example

    The Control Panel Setting Scheduled Transactions Using a scheduled recipe allows you to run all of the transactions linked to a recipe at a date that can be controlled and scheduled manually using the scheduling tool. Merchants can access the scheduling tool in the Recurring Recipe List (See Figure 4.26).

  • Page 125: Scheduling Tool Example

    The Control Panel The Scheduling Tool window will open (See Figure 4.27). Figure 4.97. Scheduling Tool Example...

  • Page 126: Scheduling Tool Example

    The Control Panel Click on the "Show Calendar" button to open the scheduling calendar (See Figure 4.28). Figure 4.98. Scheduling Calendar Tool Example Scroll to the correct month and year and then click on the appropriate day of the month and the "Date"...

  • Page 127: The Chargeback Interface - What If I Get A Chargeback

    The Control Panel Figure 4.100. Successful Schedule Example The ChargeBack Interface - What If I Get A Chargeback? This interface is used to locate a transaction if a credit card number and the approximate date of the transaction are known. This is normally used by merchants in a "chargeback" situation, when a card- holder has disputed a charge.

  • Page 128: The Post-A-Credit Interface - How Can I Generate A Refund

    The Control Panel transactions using that card number on or near the date selected. The Post-A-Credit Interface - How Can I Generate A Refund? This interface is used to generate a refund or payment to a cardholder's account that was not originally charged through the gateway account.
  • Page 129 The Control Panel Entering a credit transaction requires entering all of the correct information in the Post-A-Credit inter- face: • Credit Amount - This is the amount that will be withdrawn from the merchant's account and will deposit into the customer's account. •...

  • Page 130: The Card Setup Interface - How Do I Add My Merchant Account To My Gateway Account

    The Control Panel the merchant has the email delivery selected), and this information will listed in the Transaction Listing. The Card Setup Interface - How Do I Add My Merchant Account To My Gateway Account? This interface needs to be used by any merchant who needs to accept credit cards. Until this interface has been completed, a merchant will not be able to accept credit cards.
  • Page 131 The Control Panel Each of the options require you to provide the following information: • Merchant Account Contact Information - The contact information for the merchant account ser- vice provider should be listed here. • Address Verification Buttons - The selected button will set the level of verification for the Address Verification System.

  • Page 132: Fdr Canada Card Interface Example

    Void If CVV Not Entered - With this setting a customer's transaction will be voided if the bank indicates that a CVV code should exist on the card, but was not entered. • Note - The iTransact gateway does not perform CVV auto-voids for American Express transac- tions. •...
  • Page 133 The Control Panel This is an explanation of each of the unique fields in the form:...

  • Page 134: First Data Cardnet Setup Interface Example

    The Control Panel • Merchant Number - The 11-digit merchant identification number assigned by First Data. • Terminal ID - This 2-digit number is optional, but designates the device. The default for the gateway software is "99" • American Express SE Number - The serial exchange number assigned by AMEX to indicate a merchant has the authority to accept this card type.
  • Page 135 The Control Panel...

  • Page 136: First Data Nabanco Setup Interface Example

    The Control Panel This is an explanation of each of the unique fields in the form: • CardNet Merchant Number - The 12-digit merchant identification number assigned by First Data. • CardNet Terminal ID - This 6-digit number is required. •...
  • Page 137 The Control Panel This is an explanation of each of the unique fields in the form:...

  • Page 138: Fdr Omaha Setup Interface Example

    The Control Panel • Merchant Number - The 11-digit merchant identification number assigned by First Data. • Terminal ID - This 2-digit number is optional, but designates the device. The default for the gateway software is "99" • American Express SE Number - The serial exchange number assigned by AMEX to indicate a merchant has the authority to accept this card type.
  • Page 139 The Control Panel...

  • Page 140: Paymentech Setup Interface Example

    The Control Panel This is an explanation of each of the unique fields in the form: • Merchant Number - The 12, 15, or 16-digit merchant identification number assigned by First Data. • Device ID - This 4-digit number is optional. The default value is "0001". •...
  • Page 141 The Control Panel...

  • Page 142: Ndc Setup Interface Example

    The Control Panel This is an explanation of each of the unique fields in the form: • Merchant Number - The 12-digit merchant identification number assigned by Paymentech. • Client/ISO/Bank Number - The 4-digit number that identifies the merchant service provider that established the Paymentech merchant account for a merchant.
  • Page 143 The Control Panel This is an explanation of each of the unique fields in the form:...

  • Page 144: Elavon/Nova Setup Interface Example

    The Control Panel • NDC Bank ID - The 6-digit number that identifies the merchant service provider that established the NDC merchant account for a merchant. • NDC Terminal ID - This number assigned by NDC can be up to 12-digits and identifies the merchant.
  • Page 145 The Control Panel This is an explanation of each of the unique fields in the form:...

  • Page 146: Visanet Setup Interface Example

    The Control Panel • Bank ID Number/BIN - The 6-digit number that identifies the merchant service provider that established the Elavon merchant account for a merchant. • Terminal ID - This 16-digit number is assigned by Elavon and identifies the merchant. After those fields are completed, the merchant must click the submit button and the information will be entered into the gateway system.
  • Page 147 The Control Panel This is an explanation of each of the unique fields in the form: • Terminal ID/V Number - The 7 or 8-digit number that identifies the merchant with Visanet (not to be confused with the 4-digit Terminal Number). •...
  • Page 148 The Control Panel the merchant service agreement with the processor as the merchant's Customer Service Phone number. • Time Zone - This should be the 3-digit numeric code listed on the Visanet VAR sheet as the "Time Zone Differential". • Merchant Number - The 12-digit merchant identification number assigned by Visanet.
  • Page 149 The Control Panel This is an explanation of each of the unique fields in the form: • Terminal ID/V Number - The 7 or 8-digit number that identifies the merchant with Visanet (not to be confused with the 4-digit Terminal Number). •...

  • Page 150: The Check Setup Interface - How Do I Accept Payments From Checking Accounts

    The Control Panel the merchant service agreement with the processor as the merchant's Customer Service Phone number. • Time Zone - This should be the 3-digit numeric code listed on the Visanet VAR sheet as the "Time Zone Differential". • Merchant Number - The 12-digit merchant identification number assigned by Visanet.
  • Page 151 The Control Panel EFT Setup This simple interface will allow a merchant to begin the process to accept EFT payments. • Click on the link to open this window: Figure 4.114. EFT Setup Interface Example...
  • Page 152 The Control Panel • Enter the correct contact information into the fields and click the "Submit Securely" button. At that point a "Thank You" window will open. • An email is sent to the EFT Bank relaying the information entered on the form. An email will be sent from the EFT bank with the final instructions to complete the EFT application process.

  • Page 153: Gateway Emails

    Chapter 5. Gateway Emails What Emails Are Sent By The Gateway? The gateway system uses emails as the primary source of communication. Many different types of emails are generated for different purposes. Account Activation Email An Account Activation email will be sent to a merchant once the credit card processing has been activ- ated on the gateway software account.

  • Page 154: Customer Credit Card Sale Confirmation Email Example

    Last Four Digits: 3263 Transaction ID: 999999999 IP Address: 0.0.0.0 AVS Response: Y AVS response descriptions are listed here: https://secure.itransact.com/support/avs.html Description_______________________________________Amount__Quantity__Subtotal Item 1____________________________________________25.00_____1_______25.00 Transaction total: $25.00 The value of any of the "email_text" fields get printed here!!!! Customer Credit Card Sale Confirmation Email The email below can be turned off in the Control Panel's Account Settings interface.

  • Page 155: Merchant Checking Account Sale Confirmation Email Example

    Gateway Emails Merchant Checking Account Sale Confirmation Email Table 5.4. Merchant Checking Account Sale Confirmation Email Example To: "MERCHANT" <Merchantemail@Merchantdomain.com> From: "Check Transaction Processing" Reply-To: "Customer2 Name2" <Customer2@Customeremail.com> Subject: Customer2 Name2, $150.00 XID: 99999999 Approval: 6/28/2002 17:18:11 **************************************************************** MERCHANT, The following transaction was processed. CUSTOMER INFORMATION: ----------------------------------------------- Customer Name: Customer2 Name2...

  • Page 156: Merchant Void Transaction Confirmation Email Example

    Gateway Emails Sincerely, MERCHANT Void Transaction Confirmations The gateway system sends a merchant an email each time a void transaction is processed. By default, a corresponding email is also sent to the customer (unless the merchant has de-activated the settings ex- plained in THIS section of the documentation).

  • Page 157: Merchant Credit/Refund Transaction Confirmation Email Example

    Gateway Emails Card Type: MasterCard Name: Customer3 Name3 Address: 515 Center St City, St. ZIP: Centerville, NY 14225 Country: USA Telephone: 716 555 1055 E-Mail Address: Customer3@Customeremail.com Original Transaction ID: 88888877 Current Transaction ID: 88888888 Amount: $150.00 Date & Time: 6/1/2002 09:11:20 Credit/Refund Transaction Confirmations The gateway system sends a merchant an email each time a credit/refund transaction is processed.

  • Page 158: Merchant Preauth Transaction Confirmation Email Example

    Telephone: 209-555-5555 E-Mail Address: Customer5@Customeremail.com Approval Code: 991676 CVV2 Response: Card Type: Visa Transaction ID: 777777777 IP Address: 0.0.0.0 AVS Response: Y AVS response descriptions are listed here: https://secure.itransact.com/support/avs.html Description_______________________________________Amount_Quantity__Subtotal Item 1____________________________________________295.00___1_______295.00 Transaction total: $295.00 Customer Preauth Transaction Confirmation Email...

  • Page 159: Customer Preauth Transaction Confirmation Email Example

    Gateway Emails Table 5.11. Customer Preauth Transaction Confirmation Email Example To: "Customer5 Name5" <Customer5@Customeremail.com> From: "MERCHANT Transaction Processing" <Merchantemail@Merchantdomain.com> Reply-To: "MERCHANT" <Merchantemail@Merchantdomain.com> Subject: MERCHANT Transaction Confirmation, XID: 777777777 **************************************************************** Customer5 Name5, Thank you! The following preauth transaction was processed. This email will serve as your receipt. For questions, please contact Merchantemail@Merchantdomain.com.

  • Page 160: Customer Postauth Transaction Confirmation Email Example

    Gateway Emails AVS Response: AVS response descriptions are listed here: https://XXXXXXXXXX/support/avs.html Description_______________________________________Amount_Quantity__Subtotal Item 1____________________________________________295.00___1_______295.00 Transaction total: $295.00 Customer Postauth Transaction Confirmation Email The email below can be turned off in the Control Panel's Account Settings interface. Table 5.13. Customer Postauth Transaction Confirmation Email Example To: "Customer5 Name5"...

  • Page 161: Approval

    E-Mail Address: Customer6@Customeremail.com Approval Code: 461097 CVV2 Response: Card Type: Visa Transaction ID: 6565656565 IP Address: 0.0.0.0 AVS Response: AVS response descriptions are listed here: https://secure.itransact.com/support/avs.html Description_______________________________________Amount__Quantity_Subtotal Item 1____________________________________________459.00_____1_______459.00 Item 2_____________________________________________49.95_____1________49.95 Item 3_____________________________________________13.95_____1________13.95 Shipping___________________________________________25.00_____1________25.00 Transaction total: $547.90 Customer Force Transaction Confirmation Email The email below can be turned off in the Control Panel's Account Settings interface.

  • Page 162: Approval

    CVV2 Response: Card Type: MasterCard Last Four Digits: 4321 Transaction ID: 9222222222 IP Address: 0.0.0.0 AVS Response: Y AVS response descriptions are listed here: https://secure.itransact.com/support/avs.html RECURRING TRANSACTION INFORMATION: ----------------------------------------------- Start Date: 12/1/2004 Recipe Name: monthly02 Originating XID: 121211111 Recurring Amount: 675.00...

  • Page 163: Customer Recurring Credit Card Transaction Confirmation Email Example

    Gateway Emails Table 5.17. Customer Recurring Credit Card Transaction Confirmation Email Example To: "Customer8 Name8" <Customer8@Customeremail.com> From: "MERCHANT Recurring Transaction Processing" <Merchantemail@Merchantdomain.com> Reply-To: "MERCHANT" <Merchantemail@Merchantdomain.com> Subject: MERCHANT Recurring Transaction Confirmation, XID: 9222222222 **************************************************************** Customer8 Name8, Thank you! The following recurring transaction was processed. This email will serve as your receipt.

  • Page 164: Merchant Recurring Check Transaction Confirmation Email Example

    Remaining Reps: 986 Definition: Repeat every month on the 2nd day Description_______________________Amount__Quantity__Subtotal Monthly Fee_______________________675.00____1_______675.00 Transaction total: $675.00 If you would like to update your billing information use the link below. https://secure.itransact.com/customers/billing_update/edit/MDEsMzA3MDYzMDksMjAxMDAxMTIwOT TRANSACTION HISTORY ----------------------------------------------- 12/1/2004 121211111 order ok 675.00 1/2/2005 1222222222 order ok 675.00...

  • Page 165: Customer Recurring Check Transaction Confirmation Email Example

    Gateway Emails Customer Name: Customer9 Name9 Address: PO Box 123 City, St. ZIP: South Towne, TX 12345 Country: USA Telephone: 555-123-8448 E-Mail Address: Customer9@Customeremail.com Last Four Digits: Check Number: Check Memo: Transaction ID: 12312312 IP Address: 0.0.0.0 RECURRING TRANSACTION INFORMATION: ----------------------------------------------- Start Date: 12/5/2005 Recipe Name: monthly05...

  • Page 166: Transaction Failure Notifications

    Gateway Emails Definition: Repeat every month on the 5th day Description________________________Amount___Quantity__Subtotal Monthly Fee________________________2370.00___1________2370.00 Additional Support__________________275.00___1_________275.00 Transaction total: $2645.00 Sincerely, MERCHANT If you have questions regarding this recurring transaction, please contact us by replying to this email. TRANSACTION HISTORY 12/5/2005 4564560 order ok 2645.00 1/5/2006 5564560 order ok 2645.00 2/5/2006...
  • Page 167 Telephone: 555-444-3333 E-Mail Address: Customer2@Customeremail.com Card Type: MasterCard Transaction ID: 6789123 IP Address: 0.0.0.0 AVS Response: AVS response descriptions are listed here: https://secure.itransact.com/avs.html RECURRING TRANSACTION INFORMATION: ----------------------------------------------- Start Date: 12/1/2004 Recipe Name: monthly02 Originating XID: 456789 Remaining Reps: 999 Definition: Repeat every month on the 2nd day Description___________________Amount___Quantity__Subtotal Monthly Service_______________250.00______1______250.00...

  • Page 168: Credit Card Settlement Notifications

    Gateway Emails Address: 123 Main St City, St. ZIP: South Park, CA 90007 Country: USA Telephone: 555-555-3210 E-Mail Address: Customer8@Customeremail.com RECURRING TRANSACTION INFORMATION: ----------------------------------------------- Start Date: 12/1/2004 Recipe Name: monthly02 Originating XID: 121211111 Recurring Amount: 675.00 Remaining Reps: 986 Definition: Repeat every month on the 2nd day Description_______________________Amount__Quantity__Subtotal Monthly Fee_______________________675.00____1_______675.00 Transaction total: $675.00...

  • Page 169: Auction Payme Communications

    Gateway Emails Table 5.25. Settlement Email Example From: To: <undisclosed-recipients:> Sent: Friday, June 30, 2006 1:56 PM Subject: Check Stats for Merchant XXXXX on 6/27/2006 **************************************************************** Check Summary Report -- 6/27/2006 _Name____Check_Number__Date___Check_Total__Check_Charge__Fax_Chrg__Total_Charge V_CustomerI____1___________6/27/2006__10.00________0.25__________0.00______0.25 V_CustomerII___2___________6/27/2006___5.00________0.00__________0.00______0.00 V_CustomerIII__3___________6/27/2006__20.00________4.50__________0.00______4.50 Number of Checks: 3 Valid Checks: 3 Deposit Total: 35.00 Processing Charge: 4.75 FAX Charge: 0.00...

  • Page 170: Auction Payme Customer Transaction Confirmation Example

    Gateway Emails From: "Credit Card Transaction Processing" Date: June 12 2004 12:39:05 PM MDT To: "Auctionseller001" <Auctionseller001@Merchantemail.com> Subject: Winning Bidder , $65.00 MasterCard XID: 2323232323 Approval: 000000 6/12/2004 12:40:52 Reply-To: "Winning Bidder" <Winningbidder@Customeremail.com> **************************************************************** Auctionseller001, The following transaction was processed. CUSTOMER INFORMATION: ----------------------------------------------- Customer Name: Winning Bidder...

  • Page 171: Gateway Notifications

    Gateway Emails Address: 123 Main St City, St. ZIP: BHs, Ca 90210 Country: USA Telephone: 888.555.1234 E-Mail Address: Winningbidder@Customeremail.com SHIPPING INFORMATION: ----------------------------------------------- Name: Winning Bidder Address: 123 Main St City, St. ZIP: BHs, Ca 90210 Country: USA Description________________________Amount__Quantity___Subtotal eBay Item: 999999999999_____________65.00____1__________65.00 eBay Buyer ID: Auctionbuyer001_______0.00____1___________0.00 Transaction total: $65.00 Sincerely,...

  • Page 172: Merchantupdates Email Example

    DESCRIPTION OF WORK: We will be adding the ability to change recurring Check/EFT account information through the Customer Edit feature. _______________________________________________ MerchantUpdates mailing list http://secure.itransact.com/mailman/listinfo/merchantupdates Account Suspension Email Table 5.32. Account Suspension Email Example From: Date: July 12, 2006 1:07:56 PM MDT To: Merchant@merchantemail.com...

  • Page 173: Account Closure Email Example

    Gateway Emails account. If this has been suspended in error, please notify us by submitting a request at http://XXXXXXXX. Please contact us with any questions. The reason for the change was: Merchant Request Account Closure Email Table 5.33. Account Closure Email Example From: Date: July 12, 2006 1:09:16 PM MDT To: Merchant@merchantemail.com...

  • Page 174: Transaction Failure Responses

    Chapter 6. Transaction Failure Responses What Are The Potential Failure Responses On Credit Card Transactions? Transactions can potentially fail one of many reasons. Most failure responses are generated by the credit card processing networks and the credit card issuing banks. The information below includes the re- sponse as it's received from the processor and how the gateway interprets and displays that message.
  • Page 175 Transaction Failure Responses • Response - PICK UP CARD Message - Code: NBE005 The credit card processing network has recognized this card as lost or stolen. The transaction has been cancelled. • Response - CALL Message - Code: NBE006 The processing network has responded with a CALL error. Please do not resubmit your transaction.
  • Page 176 Transaction Failure Responses Message - Code: NBE017 The processing network no longer has an authorization for this transac- tion. The transaction cannot be voided. • Response - INVALID M Message - Code: NBE018 The credit card processing network has responded with an "Invalid Mer- chant Number"...
  • Page 177 Transaction Failure Responses transaction. • Response - INVLD EXP Message - Code: NBE030 You have entered an invalid expiration date. Please return to the form and verify the information entered. • Response - ISSUER UNAVAIL Message - Code: NBE032 Your card issuer cannot validate your request. Please use another card and resubmit your transaction.
  • Page 178 Transaction Failure Responses Message - Code: NBE042 ATM cards cannot be used. The card used must display the Visa, Master- card, American Express or Discover symbol. • Response - LOST Message - Code: NBE043 The credit card processing network has recognized this card as lost or stolen.
  • Page 179 Transaction Failure Responses card, American Express or Discover symbol. • Response - NO ACCOUNT Message - Code: NBE055 The credit card processing network has responded with a No Account message. Please check your input and try your transaction again. We apologize for the inconveni- ence.

  • Page 180: Navs Errors

    Transaction Failure Responses • Response - MAXIMUM ATTEMPTS Message - Code: NBE069 We were unable to obtain a response from the credit card processing net- work. Please try your transaction later. We apologize for the inconvenience. • Response - DINERS NOT ALLOW Message - Code: NBE070 This transaction cannot be processed.
  • Page 181 Transaction Failure Responses Message - Code: NAVS001 The address and zip entered do not match the address and zip listed on your credit card account. Your transaction will be voided. • Response - address Message - Code: NAVS002 The zip code entered does not match the zip code listed on your credit card account.

  • Page 182: Nbf Errors

    Transaction Failure Responses Message - Code: NAVS013 The address and/or zip code listed on your account could not be veri- fied. We received an AVS error response. Your transaction will be voided. • Response - postal Message - Code: NAVS014 The address entered does not match the address on your credit card ac- count.
  • Page 183 Transaction Failure Responses Message - Code: NBF010 This transaction cannot be voided. You will need to issue a credit instead. • Response - CaughtIOException:Read timed out Message - Code: NBF011 The Elavon/Nova processing network is not responding to our request for authorization.

  • Page 184: Ncvv Errors

    Transaction Failure Responses • Response - suspended for maintenance Message - Code: NBF023 Our servers are currently undergoing scheduled maintenance. Please try back later. • Response - temporarily disabled Message - Code: NBF024 Transaction processing is currently disabled for maintenance. Please try back later •...

  • Page 185: Thr Errors

    Transaction Failure Responses Message - Code: NCVV005 You indicated that CVV2 was not available, however the issuer indic- ates it should be present. Your Transaction Will Be Voided THR Errors There is only one THR error. When "THR001" is displayed, this indicates that a merchant has enabled the Restrict Order Usage feature and it has been engaged by a declined transaction attempt.

  • Page 186: Deposits

    Chapter 7. Deposits How Long Do Deposits Take? Credit Card Deposits Funds from credit card transactions are deposited into a merchant's checking account approximately 2-3 business days after the credit card transaction settles. Check Deposits EFT Deposits Funds from EFT transactions are deposited into a merchant's checking account approximately 5-7 busi- ness days after it is transacted.

  • Page 187: Gateway Glossary

    Chapter 8. Gateway Glossary Glossary of Terms Below is a glossary of gateway terms • Authorization - Receiving an approval for a credit card transaction from a card issuing bank through a response from a credit card processing network. • Authorization Code - Alpha-numeric response received from the processing network indicating a credit card transaction approval.
  • Page 188 NACHA Processing - The gateway can create direct NACHA formatted file. To use this system, a merchant must meet necessary requirements with their bank and iTransact must run a through a veri- fication process before a merchant can utilize the system. To inquire, pleases submit a ticket at ht- tp://support.itransact.com.

  • Page 189: Sec Code Information

    Gateway Glossary formation. • SEC Codes - This is the standard entry class used for EFT processing. • Secure Server - Technology that is required to be used for websites that want to accept payments. Merchants may use their own secure servers or they can use the gateway's secure servers if they util- ize the Split Form method.
  • Page 190 Gateway Glossary • WEB - Internet (Initiated and authorized via the web through a secure system, can be a single entry or recurring debit, 60 day return timeframe may apply) • ARC - Accounts Receivable (Used for check conversion of one-time payments received via US Mail or a drop box, 60 day return timeframe may apply) •...

This manual is also suitable for:

Gateway

Table of Contents