JetPay Hosted Payment Page(HPP) Development and Integration Guide

Transcription

1 JetPay Hosted Payment Page(HPP) Development and Integration Guide - 1 -

2 JetPay Hosted Payment Page(HPP) Introduction What merchants qualify for use with JetPayHPP Process Overview Minimum Merchant Requirements Typical JetPayHPP integration at the point of hand off General Flow of Customer Activity After Hand-Off The JetPay Response For approved Credit Card and ACH For Declined CC and ACH Certification Testing a tandard Transaction Processing Test uite b CVV2 Test Cases c Address Verification Test Cases d Checking Account and avings Account Transactions (ACH) APPENDIX

3 Introduction The JetPay Hosted Payment Page or HPP was developed as a tool to assist merchants that ether can not or do not have the technical means to meet the rigors of PCI-D Compliance for collecting and transmitting credit card data. The HPP product is geared for any merchant that needs to take payments from statements, invoices, loan payment, services etc. HPP is NOT intended as a payment solution for online merchants that have shopping carts or online store fronts. The HPP product works by a redirect from the merchant s site to payment processing page sets hosted on JetPay s PCI compliant web servers. What merchants qualify for use with JetPayHPP? The HPP product is designed for any merchant that would like to offer online payments as a convenience to their customer base. These merchants generally include: Credit Unions Medical Offices Auto Loan Companies Municipalities (ee Addendum A for special information.) ervice Companies And many more. Process Overview The HPP product is designed for any merchant that would like to offer online payments as a convenience to their customer base. These merchants generally include: - 3 -

4 Minimum Merchant Requirements The following is the minimum requirements that each merchant using the HPP product must meet. Item L Certificate Receive Post Data Legal tice Merchant Configuration Document Description The merchant must possess a valid L Certificate issued by a registered certifying authority. The merchant may not use a self-signed certificate or a shared certificate. If the merchant elects to receive transaction data to store in their own servers for reporting, or other use the merchant s site must accept POT data and provide an HTTP address where the transaction date will be sent. Before the merchant can hand the customer to JetPay to process the payment, the merchant must inform the customer that they (the customer) are being redirected to make the payment. ee tice ample in Appendix B. Merchant must provide a completed Merchant Configuration Document. Failure to provide this document will result in a delay in completing the set up on JetPay s servers

5 1 Typical JetPayHPP integration at the point of hand off. After the customer has ether logged into the merchants site or has selected to make a payment the merchant will need to redirect the customer to the HPP product. In most cased this will be done by the merchant setting up a hidden form on the redirect page. While there are other methods to make this redirect the use of a hidden form is the simplest and most straight forward. ample of hidden form with required fields: <form name="redirect" method="post" action="url_for_jetpayhpp" /> <input type="submit" name="make Payment" value="submit" /> <input type="hidden" name="merchant_mid" value="" /> <input type="hidden" name="merchant_token" value="" /> <input type="hidden" name="merchant_type" value="" /> <input type="hidden" name="cid" value=" " /> </form> While the use of hidden form may be the simplest method, the developer may use any method as long as the information is provided as an HTTP POT or URLENCODE. The preferred method for generation and sending of the HTTP POT data would be the following: 1) At the point with in the merchant site where the customer is notified and must acknowledge that they are being redirected to JetPay the developer should set the action of the button or link to a separate server side page with in the merchants site. 2) The server side page should then generate the HTTP POT data and auto redirect to the JetPayHPP product. In the above information about the merchant mid, token, and type would not be visible on a simple page source lookup. ee table below for all required and optional fields that are available to the merchant for the post operation to JetPayHPP

6 Merchant Variables - Global Variable Value Description Required merchant_mid 12 Characters This is the Terminal ID (TID) as provide by Yes JetPay merchant_token 42 Characters This token will be provided to the merchant after the submission of the Merchant Configuration Document Yes merchant_type 1 Character Numeric Only This character is provided as part of the check sum used in conjunction with the merchant_token. Yes cid 24 Character The cid is a customer identifier assigned by the merchant for the customer used to connect the customer to the transaction Yes - 6 -

7 Variable Value Description Required pay_amount UD Currency Format The amount that is due from the customer, if known by the merchant. To be supplied in UD format (dollars and cents) Exp: customername 40 Character Alpha Only Customer Name billingaddress1 50 Character The first line of the customers billing address. billingaddress2 50 Character The second line of the customers billing address. billingcity 50 Character The second line of the customers billing address. billingtate 2 Character Alpha Abreviated state name of the customers billing address. Exp: TX = Texas billingzip 5 Character Numeric The U zip code of the customers billing address billingcountry 3 Character Alpha tandardized three(3) character Country Code. Exp: UA = United tates of America. ee Appendix A for full list. customer 50 Character Customers address customerphone 9 Character Numeric The customers phone number. Exp.=

8 customeraccountnumber 20 Character Account number of used by the merchant for the customer. This might also be used as the cid. merordernumber 20 Character Optional Order Number assigned by the merchant for this transaction*. merud1 42 Character This is a free that the merchant may include to provide other information about the customer, account, payment type etc.* merdata1 merdata10 50 Character merdata1 merdata10 are open fields for the merchant use. These fields can contain data, information that the merchant needs or wants to have returned to them with the transaction data.** customer 50 Character Customers address *These fields will be recorded in at JetPay and will be available with the transaction information in JetPay GetReporting ystem. **These fields are provided as convince to the merchant. data supplied in these fields will be recorded at JetPay. These fields are simple pass-through from the merchant back to the merchant. Once the HTTP POT has been generated and is complete with the required elements from the above table, the customer can be passed off to the JetPayHPP product. After the customer is handed off the merchant site will need to begin listing for a reply HTTP POT at the all their site address provided for APPROVED and DECLINED URL s. The APPROVED and DECLINE URL s should be outlined in the JPHPP Merchant etup document as referenced in the Merchant Requirements section. Testing URL for JetPayHPP te: Attempting to direct access this page will result in a warning message being displayed. Alerting that the incoming request could not be authenticated

9 Merchant Testing Variables Variable merchant_mid Value TETTERMINAL merchant_token abcdefg merchant_type 1 cid The first 24 characters of the merchant name. Do not include spaces or special characters

10 2 General Flow of Customer Activity after Hand-Off. While the customer is in the JetPayHPP ystem they will be moved through the following process. 1. Payment election Customer selects to make payment via Credit/Debit Card or Automated Clearing House. te: For a customer to select ACH as the payment method the merchant must be approved for ACH via the WEB. If the merchant is not approved for ACH the customer will only be presented with the Credit/Debit card option. 2. Account Information Customer will provided the Account Holder Name, Account Number and if selected by the merchant Last 4 of ocial ecurity Number. Also the payment amount will be presented if passed by the merchant in the hand off. If no amount an Amount field will be presented for the customer to enter the amount of the invoice, statement etc. 3. Payment Form Credit/Debit or ACH This is a standard form where the customer will provide the account details based on the option that was selected as the payment type. This page also reflects any fee amount that is to be charged for payment online and a calculated total of the payment amount and the fee. Also, the customer will be presented with standard terms and conditions that they must agree to or cancel the transaction. If the customer elects to cancel the transaction they will be returned to the cancel URL provided in the merchant setup document. 4. Conformation Page The customer must confirm that all information they have provided is accurate and correct. If something is in correct they have the option to change it at that time. 5. Approved or Declined Receipt Page This is a standard page showing the status of the payment they just attempted. Text on the page encourages the customer to print the page for their records. From this page the customer is release back to the merchant s site. te: At this time the JetPayHPP Product does not send conformation on behalf of the merchant for transactions. Between steps 4 and 5 the details of the transaction are posted back to the merchant s site to ether the Approved URL or the Declined URL

11 3 The JetPay Response After the transaction has been completed JetPay will return to the merchant the transaction data in the form of an HTTP POT, to a return URL provided by the merchant. This transaction data can include a number of different values based on the merchant s configuration as well as the information provided by the merchant. The table below outlines each returned variable and a description of the information. For approved Credit Card and ACH Returned Description tandard/ Variable Optional cid Customer ID as provided by Merchant cardnum Card number provided by the customer in the following format: ************#### CC card The type of card used be the customer for the transaction V=Visa M=Master Card D=Discover A=American Express CC chargetotal The total amount that was charged for this payment. This amount includes any fee incurred for online bill pay. transid Transaction ID actcode The Action Code for the transaction* te to obtain a full listing of Action Codes please contact JetPay Customer ervice at [email protected] and request the Action Code List. authcode The six(6) character authorization code for the transaction CC cvvmatch CVV or ecurity Code Matching information^ CC addressmatch Address Verification Match Code^ CC zipmatch Zjp Code Verification Match Code^ CC avsmatch Address Verification Match Code^^ CC cctoken Token for Credit Card Number and Expiration Date CC name Card Holder or Account Holders Name CC accountnumber The account number to which the payment is to be applied. This number is ether provided by the merchant or entered by the customer

12 ssn Last four(4) digits of the ocial ecurity Number of the account holder. tocagreement te that this is an optional field as not all merchant will request the collection of this information. However if the ssn is collected it will be provided in the return as well as accessible in JetPay GetReporting system as the value for UD2. Date time stamp of when the customer agreed to the terms and conditions of doing the payment online. merordernumbe r merud1 As provided by the merchant. O As provided by the merchant O te that if the merchant is a municipality or for other reasons elects split tender this field will not be available. merdata1-10 As provided by the merchant O

13 For Declined CC and ACH Returned Variable cid transid Description Customer ID as provided by Merchant Transaction ID The Action Code for the transaction* tandard/ Optional actcode name te to obtain a full listing of Action Codes please contact JetPay Customer ervice at [email protected] and request the Action Code List. Card Holder or Account Holders Name CC accountnumber The account number to which the payment is to be applied. This number is ether provided by the merchant or entered by the customer. te: The Account Number will be provided in the return as well as accessible in JetPay GetReporting system as the value for UD3. Last four(4) digits of the ocial ecurity Number of the account holder. ssn tocagreement te that this is an optional field as not all merchant will request the collection of this information. However if the ssn is collected it will be provided in the return as well as accessible in JetPay GetReporting system as the value for UD2. Date time stamp of when the customer agreed to the terms and conditions of doing the payment online. merordernumbe r As provided by the merchant. As provided by the merchant O merud1 te that if the merchant is a municipality or for other reasons elects split tender this field will not be available. O merdata1-10 As provided by the merchant O

14 4 Certification Testing JetPay certification testing is intended to prepare a merchant for processing transactions through JetPay. This document contains test suites and test cases that enable a merchant to prepare and submit test JetPay transactions and verify compliance with JetPay submission rules. 4a tandard Transaction Processing Test uite The following test cases consist of common JetPay transactions that many merchants will need to be able to perform. To certify, the merchant needs to submit those test cases that apply to the merchant's anticipated requirements. The following test cases will certify standard sales transactions. The credit card used for these test cases will follow the format, xxxx. Test Case Type PAN Exp Amount Expected Result Date TND001 ALE /13 $10.00 Approved TND002 ALE /11 $10.00 Expired Card TND003 ALE /13 $10.00 Invalid Card Number TND004 Through TND104 ALE /13 Amounts between Or $1.00 and $2.00 AUTHONLY ($1.01, $1.02, etc) Assorted responses both approved and declined. These test cases are always required. 4b CVV2 Test Cases The credit card companies support multiple methods for validating credit cards and verifying a cardholder's identity. JetPay supports CVV2, CVC2, and CID card validation, available from Visa, MasterCard, and American Express, as well as all the other major credit card brands. JetPay supports address verification ("AV") as implemented by Visa, MasterCard, and American Express (as well as Amex's name verification feature). With these two common features, a credit card's integrity can be validated and a cardholder's billing address can be verified. Even more importantly, these two features reduce transaction charges and help to protect a merchant against charge backs. The following test cases will certify CVV2 transactions. The credit card used for these test cases use the following format: xxxx. Test Case CVV201 CVV202 CVV203 Type PAN Exp Date Amount CVV2 Expected Result ALE Or /13 $ Approved, CVV Matches AUTHONLY ALE Or /13 $ Approved, CVV Doesn t Match AUTHONLY ALE Or /13 $ Approved, CVV not processed

15 AUTHONLY CVV204 AUTHONLY /13 $ Approved, CVV Matches CVV205 CVV206 ALE or /13 $ Declined, CVV t Processed AUTHONLY ALE or /13 $ Declined, CVV Matches AUTHONLY 4c Address Verification Test Cases The following test cases will certify address verification transactions using AV. The credit card used for these test cases is xxxx. Test AV if AV is activated on the Merchant Account. Test Case AV01 AV02 AV03 AV04 AV05 Type PAN Exp Date Amount Address Postal Code ALE Or /11 $ Fifth treet AUTHONLY ALE /11 $ Fifth treet Or AUTHONLY ALE /11 $ Fifth treet Or AUTHONLY ALE or /11 $ Fifth treet AUTHONLY ALE or /11 $ Fifth treet AUTHONLY Expected Result Approved, both address & zip match Approved, address match, zip not match Approved, zip match, address does not match Approved, address and zip do not match Approved, international non-av participant AV06 ALE or /11 $ Fifth treet AUTHONLY Declined, AV Unavailable

16 4d Checking Account and avings Account Transactions (ACH) Merchants may submit bank drafts to JetPay. JetPay can enable properly configured merchants to send checks and savings account drafts directly into their bank account. By submitting the ABA routing code listed on every check along with the bank account number and the accountholder's name, JetPay will route these bank drafts directly into the merchant's bank account. Refunds of bank drafts are also available. Bank accounts submitted through ACH require an ABA number, and account number, an accountholder's name, and an identifying check number. The following processes prescribe the test cases for ACH processing. For Approval Testing use routing code of , for Decline Testing use routing number of For the cardholder name, use "John Q. Public" or the name of your favorite tar Wars character. Test Type Account Check Amount Expected Result Case Number Number ACH01 CHECK $10.00 Approved ACH02 CHECK $10.00 Approved ACH03 CHECK $10.00 Approved ACH04 CHECK $10.00 Decline ACH05 CHECK $10.00 Decline

17 APPENDIX Visa AV Result Codes (Credit Card) Value A B C D F G I M N P R U Y Z Definition treet addresses match. The street addresses match but the postal/zip codes do not, or the request does not include the postal/zip code. treet addresses match. Postal code not verified due to incompatible formats.(acquirer sent both street address and postal code). treet address and postal code not verified due to incompatible formats.(acquirer sent both street address and postal code). treet address and postal codes match. treet address and postal ode match. Applies to U.K. Only. Address information not verified for international transaction. Address information not verified. treet address and postal code match. match. Acquirer sent postal/zip code only, or street address only, or both postal code and street address. Postal code match. Acquirer sent both postal code and street address, but street address not verified due to incompatible formats. Retry: ystem unavailable or timed out. Issuer ordinarily performs their own AV but was unavailable. Available for U.. issuers only. Address not verified for domestic transaction. Visa tried to perform check on issuer's behalf but no AV information was available on record, issuer is not an AV participant, or AV data was present in the request but issuer did not return an AV result. treet address and postal code match. Postal/ZIP matches; street does not match or street address not included in request

18 Master Card AV Result Codes (Credit Card) Value A N R U W X Y Z Definition Address matches, postal code does not. Neither address nor postal code matches. Retry: ystem unavailable or timed out. AV currently not supported. data from issuer/authorization ystem. For U.. addresses, nine-digit postal code matches, address does not, for address outside the U.. postal code matches, address does not. For U.. addresses, nine-digit postal code and address matches, for address outside the U.., postal code and address match. For U.. addresses, five-digit postal code and address matches. For U.. addresses, five-digit postal code matches, address does not

19 Country List ample three (3) character to full name country list in and associative array. $IO3166ThreeToName = array( 'AFG' => 'Afghanistan', 'ALB' => 'Albania', 'DZA' => 'Algeria', 'AM' => 'American amoa', 'AND' => 'Andorra', 'AGO' => 'Angola ', 'AIA' => 'Anguilla', 'ATA' => Antarctica, 'ATG' => Antigua and Barbuda', 'ARG' => Argentina Argentine ', 'ARM' => Armenia, 'ABW' => Aruba, 'AU' => Australia, 'AUT' => Austria, 'AZE' => Azerbaijan, 'BH' => Bahamas, 'BHR' => Bahrain, 'BGD' => Bangladesh, 'BRB' => Barbados, 'BLR' => Belarus, 'BEL' => Belgium, 'BLZ' => Belize, 'BEN' => Benin, 'BMU' => Bermuda, 'BTN' => Bhutan, 'BOL' => Bolivia, 'BIH' => Bosnia/Herzegovina', 'BWA' => Botswana ', 'BVT' => Bouvet Island', 'BRA' => Brazil, 'IOT' => British Indian Ocean Territory', 'VGB' => British Virgin Islands', 'BRN' => Brunei Darussalam', 'BGR' => Bulgaria, 'BFA' => Burkina Faso', 'BDI' => Burundi ', 'KHM' => Cambodia, 'CMR' => Cameroon ', 'CAN' => Canada, 'CPV' => Cape Verde', 'CYM' => Cayman Islands', 'CAF' => Central African ', 'TCD' => Chad, 'CHL' => Chile, 'CHN' => China, 'CXR' => Christmas Island', 'CCK' => Cocas (Keeling) Islands', 'COL' => Colombia, 'COM' => Comoros, 'COD' => Congo Democratic', 'COG' => Congo, 'COK' => Cook Islands', 'CRI' => Costa Rica', 'CIV' => Ivory Coast', 'CUB' => Cuba, 'CYP' => Cyprus, 'CZE' => Czech ', 'DNK' => Denmark, 'DJI' => Djibouti, 'DMA' => Dominica, 'DOM' => Dominican ', 'TL' => Timor-Leste', 'ECU' => Ecuador, 'EGY' => Egypt Arab',

20 'LV' => El alvador', 'GNQ' => Equatorial Guinea', 'ERI' => Eritrea, 'ET' => Estonia, 'ETH' => Ethiopia, 'FRO' => Faeroe Islands', 'FLK' => Falkland Islands', 'FJI' => Fiji, 'FIN' => Finland, 'FRA' => France, 'GUF' => French Guiana', 'PYF' => French Polynesia', 'ATF' => 'French outhern Territories', 'GAB' => 'Gabon Gabonese ', 'GMB' => 'Gambia the', 'GEO' => 'Georgia', 'DEU' => 'Germany', 'GHA' => 'Ghana', 'GIB' => 'Gibraltar', 'GRC' => 'Greece Hellenic ', 'GRL' => 'Greenland', 'GRD' => 'Grenada', 'GLP' => 'Guadeloupe Islands', 'GUM' => 'Guam', 'GTM' => 'Guatemala', 'GIN' => 'Guinea', 'GNB' => 'Guinea-Bissau', 'GUY' => 'Guyana', 'HTI' => 'Haiti', 'HMD' => 'Heard & McDonald Islands', 'VAT' => 'Holy ee (Vatican City)', 'HND' => 'Honduras', 'HKG' => 'Hong Kong', 'HRV' => 'Croatia', 'HUN' => 'Hungary', 'IL' => 'Iceland', 'IND' => 'India', 'IDN' => 'Indonesia', 'IRN' => 'Iran Islamic', 'IRQ' => 'Iraq', 'IRL' => 'Ireland', 'IR' => 'Israel', 'ITA' => 'Italy', 'JAM' => 'Jamaica', 'JPN' => 'Japan', 'JOR' => 'Jordan', 'KAZ' => 'Kazakhstan', 'KEN' => 'Kenya', 'KIR' => 'Kiribati', 'PRK' => 'Korea', 'KOR' => 'Korea', 'KWT' => 'Kuwait', 'KGZ' => 'Kyrgyz ', 'LAO' => 'Lao', 'LVA' => 'Latvia', 'LBN' => 'Lebanon', 'LO' => 'Lesotho', 'LBR' => 'Liberia', 'LBY' => 'Libya', 'LIE' => 'Liechtenstein', 'LTU' => 'Lithuania', 'LUX' => 'Luxembourg', 'MAC' => 'Macao', 'MKD' => 'Macedonia', 'MDG' => 'Madagascar', 'MWI' => 'Malawi', 'MY' => 'Malaysia', 'MDV' => 'Maldives', 'MLI' => 'Mali', 'MLT' => 'Malta', 'MHL' => 'Marshall Islands', 'MTQ' => 'Martinique',

21 'MRT' => 'Mauritania', 'MU' => 'Mauritius', 'MYT' => 'Mayotte', 'MEX' => 'Mexico', 'FM' => 'Micronesia', 'MDA' => 'Moldova', 'MCO' => 'Monaco', 'MNG' => 'Mongolia', 'MR' => 'Montserrat', 'MAR' => 'Morocco', 'MOZ' => 'Mozambique', 'MMR' => 'Myanmar', 'NAM' => 'Namibia', 'NRU' => 'Nauru', 'NPL' => 'Nepal', 'ANT' => 'Netherlands Antilles', 'NLD' => 'Netherlands', 'NCL' => 'New Caledonia', 'NZL' => 'New Zealand', 'NIC' => 'Nicaragua', 'NER' => 'Niger the', 'NGA' => 'Nigeria', 'NIU' => 'Niue', 'NFK' => 'rfolk Island', 'MNP' => 'rthern Mariana Islands', 'NOR' => 'rway', 'OMN' => 'Oman', 'PAK' => 'Pakistan', 'PLW' => 'Palau', 'PE' => 'Palestinian Territory', 'PAN' => 'Panama', 'PNG' => 'Papua New Guinea', 'PRY' => 'Paraguay', 'PER' => 'Peru', 'PHL' => 'Philippines', 'PCN' => 'Pitcairn Island', 'POL' => 'Poland Polish ', 'PRT' => 'Portugal', 'PRI' => 'Puerto Rico', 'QAT' => 'Qatar tate', 'REU' => 'Reunion', 'ROU' => 'Romania', 'RU' => 'Russia', 'RWA' => 'Rwanda', 'HN' => 't. Helena', 'KNA' => 't. Kitts & Nevis', 'LCA' => 't. Lucia', 'PM' => 't. Pierre & Miquelon', 'VCT' => 't. Vincent/Grenadines', 'WM' => 'amoa', 'MR' => 'an Marino', 'TP' => 'ao Tome', 'AU' => 'audi Arabia', 'EN' => 'enegal', 'YC' => 'eychelles', 'LE' => 'ierra Leone', 'GP' => 'ingapore', 'VK' => 'lovakia', 'VN' => 'lovenia', 'LB' => 'olomon Islands', 'OM' => 'omalia omali ', 'ZAF' => 'outh Africa', 'G' => 'outh Georgia', 'G' => 'outh andwich Islands', 'EP' => 'pain', 'LKA' => 'ri Lanka', 'DN' => 'udan', 'UR' => 'uriname', 'JM' => 'valbard & Jan Mayen Islands', 'WZ' => 'waziland', 'WE' => 'weden', 'CHE' => 'witzerland',

22 ); 'YR' => 'yrian', 'TWN' => 'Taiwan', 'TJK' => 'Tajikistan', 'TZA' => 'Tanzania', 'THA' => 'Thailand', 'TGO' => 'Togo Togolese ', 'TKL' => 'Tokelau', 'TON' => 'Tonga', 'TTO' => 'Trinidad & Tobago', 'TUN' => 'Tunisia', 'TUR' => 'Turkey', 'TKM' => 'Turkmenistan', 'TCA' => 'Turks & Caicos Islands', 'TUV' => 'Tuvalu', 'VIR' => 'Virgin Islands', 'UGA' => 'Uganda', 'UKR' => 'Ukraine', 'ARE' => 'United Arab Emirates', 'GBR' => 'United Kingdom', 'UMI' => 'U Minor Outlying Islands', 'UA' => 'United tates of America', 'URY' => 'Uruguay', 'UZB' => 'Uzbekistan', 'VUT' => 'Vanuatu', 'VEN' => 'Venezuela', 'VNM' => 'Viet Nam', 'WLF' => 'Wallis & Futuna Islands', 'EH' => 'Western ahara', 'YEM' => 'Yemen', 'YUG' => 'Yugoslavia', 'ZMB' => 'Zambia', 'ZWE' => 'Zimbabwe',

23 ADDUMDIUM A pecial Information Regarding Municipalities and other entities that by law may not impose a convince fee for payments. In some integrations where the merchant is a Municipality or other entity where by law, agreement or other directive may no be allowed to impose a convince fee for taking payments online. In these instances the JetpayHPP product has the ability to process the payment amount and the fee amount as separate transactions. This separation of the amounts provides the payment amount in full to the merchant. The interchange, processing fee s, transaction fee s etc will be collected by the processor, merchant services group, or IO that manages the account. For example if a municipality needs to collect a $50.00 water bill. The municipality must be able to collect exactly $ The municipality can not accept a lesser amount after fees, interchange etc. In this instance the JetPayHPP product will change the customer the $50.00 for the amount to be paid and a convince fee of $5.00 paid to the processor, merchant services group or iso to cover the fee s and interchange. In this integration method ONLY the transaction information for the payment amount will be reported back to the merchant. The transaction information for the fee will be reported to the processor, merchant service group or IO via JetPay s GetReporting system. Please contact JetPay Customer ervice if you have questions regarding this method