Vantiv Overview

Vantiv offers a fully integrated payment processing solution designed to simplify credit card transactions and drive profitable, lasting customer relationships. Vantiv maintains direct connections to the card brands, optimizing response times while minimizing data security risk. Vantiv is both the payment handler/gateway and the credit card processor.

Personify360’s integration with Vantiv supports the same types of online transactions that are currently supported, while delivering a handful of new features to improve the merchant and customer experience.

Vantiv supports the following types of transactions already supported by Personify360:

· Authorization Transaction

· AVS Authorization

· Authorization Reversal

· Capture (Settlement)

· Credit (Refund)

· Sale Transaction

· Void

· Chargeback

· CVV Authorization

As of 7.6.0, support for the following Vantiv features have been implemented in Personify360:

ALL of the features below, with the exception of tokenization, are OPTIONAL and must be enrolled in through Vanitv. You MUST enroll in tokenization through Vantiv in order for saved credit cards and reference transactions to work properly in e-Business.

· Credit Card Processing - Standard credit card transaction processing available with Personify360 integrations with other credit card processors. For more information on credit card processing, please see the Credit Card Processing section.

· E-Check Processing - Vantiv supports e-check payments for users who prefer to make payments with a check instead of using credit cards. Accepting alternative payment methods is a powerful way to help revenue, increase customer satisfaction, and reduce payment processing costs. For more information on e-Check processing, please see the e-Checks section.

· Automatic Account Updater - This feature automatically updates expiration date, card number, card type changes, etc. This information is tracked on the Credit Card Request Review screen. The auto-updater is a fully managed service requiring no code updates. Organizations must enroll for this feature. Credit cards with expiration dates in the past, credit card numbers that have been changed or expired tokens will be authorized and returned with updated account numbers, expiration dates and tokens. Additionally, as of 7.6.1, support has been added for processing expired credit cards. If the PROCESS_EXPIRED_CC merchant parameter is set to "Y", CCP610, FAR680, INV620, and INV200 will transmit credit card payments to Vantiv even if the credit card is expired. When Vantiv returns the authorization request response, if the organization is using Vantiv’s "Account Updater" service, the response file will include the updated credit card expiration date, as well as any other changes that may have been made to the credit card, such as change of name, change of credit card number or change of credit card type.

· Custom Billing Description - Vantiv allows the organization to provide a custom description by product to appear on the customer’s credit card statement if the product is purchased and paid for by credit card. This information is defined on the Custom Billing Description screen in Product Maintenance for advertising, certification, DCD, exhibition, facility, fundraising, inventoried, meeting, membership, miscellaneous, package, subscription, transcript, and umbrella products. This is stored in CCP_REQ_ANS on the authorization transaction. The Billing Description field displays on the Credit Card Request Review screen.

· Fraud Filters - Vantiv offers a couple fraud prevention filters to protect Personify360 clients and their constituents.

§ The pre-paid card filter immediately identifies pre-paid credit cards so merchants can avoid letting a customer make a purchase that requires recurring or future payments. Information that identifies the card as a prepaid card is stored in CCP_Req_Ans and the Prepaid Card checkbox displays on the Saved Credit Cards screen in CRM360 and the Credit Card Request Review screen. By default, Vantiv is defined to reject prepaid cards.

§ International filtering can be enabled to not allow any credit cards issued by banks outside the U.S. or to disallow credit cards issued by banks from countries specified by the organization. Information that identifies the source country for the card is stored in CCP_Req_Ans and the Country of Origin field displays on the Saved Credit Cards screen in CRM360 and the Credit Card Request Review screen.

· Capture of Credit Card and Credit Card Transaction Attributes

§ Affluence Indicator - This reporting feature allows organizations to gain greater insight on their constituents based on affluence level using information provided at time of charge authorization. This is a powerful tool for organizations that do a significant amount of fundraising. Affluence indicator identifies two conditions: high-income (MASS AFFLUENT) and high-income/high-spending (AFFLUENT). This is stored on credit card profile record and in CCP_Req_Ans (on the authorization transaction). The Affluence Level field displays on the Saved Credit Cards screen in CRM360 and the Credit Card Request Review screen.

§ Cardholder Type Indicator - Identifies whether the credit card is an unknown consumer, consumer, or commercial card.This is stored on credit card profile record and in CCP_Req_Ans (on the authorization transaction). The Cardholder Type field displays on the Saved Credit Cards screen in CRM360 and the Credit Card Request Review screen.

§ Source Country Indicator - Identifies the country where the bank that issued the credit card is located. This is stored on credit card profile record and in CCP_Req_Ans (on the authorization transaction). The Country of Origin field displays on the Saved Credit Cards screen in CRM360 and the Credit Card Request Review screen.

§ Prepaid Card Indicator - Identifies whether the card is a pre-paid card rather than a credit card. This is stored on credit card profile record and in CCP_Req_Ans (on the authorization transaction). Organizations have the option to not accept pre-paid cards. The system does not store balance remaining on card. The Prepaid Card checkbox displays on the Saved Credit Cards screen in CRM360 and the Credit Card Request Review screen.

The Cardholder Type, Prepaid Card, Country of Origin, and Affluence Level fields are only populated if you are using Vantiv as your payment handler and you have enabled these features. This data is written to the CCP_Req_Ans table without being validated and the system types and codes are provided for informational purposes only.

· Tokenization - For organizations that are currently using CyberSource or Payflow Pro, but want to integrate with Vantiv, you must convert existing credit card tokens into tokens that can be consumed by Vantiv. The tokenization service is REQUIRED for all clients using the Vantiv integration. You MUST enroll in tokenization through Vantiv in order for saved credit cards and reference transactions to work properly in e-Business. For more information, please see Token Migration to Vantiv Overview.

· Authorization Recycling - as of 7.6.1, this is a process by which Vantiv attempts to secure authorizations for declined credit card transactions over a period of 15-16 days. "Authorization Recycling" requires that credit-card transactions be submitted to Vantiv for bulk credit-card transaction processing. For more information, please see Vantiv Authorization Recycling.

To support these new features, the following CCP system types and codes have been added in 7.6.0 and 7.6.1:

· AFFLUENT

§ Affluent

§ Mass Affluent

· CARDHOLDER_TYPE

§ Consumer

§ Commercial

§ Unknown

· PAYMENT_HANDLER

§ Vantiv

· REQ_STATUS

§ Complete

§ New Request

· REQ_TYPE

§ Account Verification

§ Credit

§ New Customer Profile

§ Pre-Auth

§ Pre-Credit

§ Pre-Sale

§ Sale

§ Updated Customer Profile

§ Void-Auth (new in 7.6.1)

§ Void-Credit

§ Void-Pre-Sale

Integrating with Vantiv

To integrate with Vantiv:

1. Enroll with Vantiv. For more information, please contact Vantiv directly.

2. Send a list of your IP addresses to Vantiv so they can be white listed.

3. The user ID for services on the TRS and App servers need to be granted Admin access.

4. Setup new Vantiv merchant in Personify360. For more information, please see Vantiv Merchant Parameters.

5. Configure Vantiv interface parameters in Personify360. For more information, please see Vantiv Interface Parameters.

6. For organizations that are currently using CyberSource or Payflow Pro, you must convert existing credit card tokens into tokens that can be consumed by Vantiv. For more information, please see Vantiv Tokenization.

7. Update receipt types. You must decide if you want to update the payment handler on existing receipt types or create new receipt types. If you choose to keep existing receipt types, you can either manually update the payment handler or use a stored procedure.