Set up PayPal Payflow Pro Credit Card Payments

To set up credit card payment processing with the PayPal Payflow Pro service:

See also: Test Values for Payflow Pro Processing and Credit Card Error Logs

1. In the Administration Explorer tree view, open the Parameters folder for the organization, and click the Credit Card Payment tab in the details view.
2. Double-click Online Payments: Configure. The Online Payments Settings dialog box appears.
3. Select PayPal’s Payflow Pro in the Payment processing gateway list.
4. Click Properties. The PayPal Properties dialog box opens to the Connection tabbed page.
5. Enter the following settings on the Connection tabbed page:

• Vendor - Your library’s main account name. Obtain this setting from PayPal or your e-commerce partner.
• Username and Password - Obtain these settings from PayPal or your e-commerce partner. Once you have a username and password, you can set up others for the same account if you need to track manual transactions.
• Partner - Enter your partner’s code here (PayPal or your e-commerce provider).
• Timeout - Set the number of seconds that should elapse with no action before the payment connection times out. The default is 30 seconds.
• Server - Type payflowpro.paypal.com for live transactions, or
  pilot-payflowpro.paypal.com for testing purposes. See Test Values for Payflow Pro Processing for credit card values you can use for testing.

Note:
The payflowpro.paypal.com setting is typical, but may be different depending your bank.

6. Click the Settings tab, and enter the following information on the Settings tabbed page:

• Cancel SALE method - This setting determines the appropriate automatic action (VOID or CREDIT) to cancel a SALE transaction. A sale may be canceled when it has been approved but fails AVS (Address Verification) and/or CVV2 (Card Verification Value 2) verification, or when a Polaris database error occurs. If a processor batch-processes sales transactions at the end of the day, a VOID transaction may be used to prevent the canceled SALE from settling. The library is charged only one transaction fee. However, some processors are host-based and do not use the batch method; in this case, all SALE transactions are settled immediately and a CREDIT transaction must be used to cancel the SALE. For these processors, the library is charged two transaction fees (one for the SALE and one for the CREDIT).

Important:
You must contact your processor or PayPal e-commerce account provider to determine if the processor uses the batch method or if they are host-based. If the processor uses the batch method, you must also verify that SALE transactions can be voided. If so, you can select VOID for the Cancel SALE method and avoid paying two transaction fees. Most processors use the batch method. However, if the processor uses the host method, you must select CREDIT as the cancel sale method, and you will be charged two transaction fees when a sale is canceled. (Examples of host-based processors include PayPal and Global Payments Central.)

Tip:
Log files record errors, warnings, and information about credit card transactions.

• E-Mail credit card processing errors to - This option is highly recommended. Specify a staff e-mail address to receive automatic e-mail messages when a credit card transaction fails and staff intervention is required. The message includes details about the failure, so the staff member can then take action on the failed transaction, either contacting the patron or adjusting the Polaris patron record manually.

Example:
A patron's credit card is charged, but due to some type of error or processing rule, the transaction needs to be canceled or a partial credit needs to be applied. (This could be due to AVS or CVV2 failures or a database update error.) If the cancel or credit transaction fails, the patron credit card account is charged, but the transaction is not reflected in the Polaris patron record. A staff member needs to adjust the patron account.

• AVS - Address verification, a security measure that may be provided as part of your contract with your e-commerce partner. AVS matches the street address and Zip code on the Polaris payment form with the street address and Zip code in a credit card database that PayPal accesses. Select (check) this option to use AVS. Then select a level of verification. For the following options, Y indicates the value matches, N indicates the value does not match, and X indicates that the cardholder’s bank does not support the check:
  —Full indicates that the street address must be Y and the Zip code must be Y (YY) or the transaction is declined. There can be no N values and no X values. Earlier versions of Polaris automatically used this level.
  —Medium indicates that there can be no N values (YY, XY, YX, XX allowed).
  —Light declines transactions only when both values equal N. All other combinations are accepted.

Note:
Occasionally AVS is faulty and a billing address, though correct, fails to be matched. In this case the user receives a message and the transaction is voided. If you find this is a problem, you may want to set the checking level to Light or clear (uncheck) the AVS option. Also note that the billing address that is displayed when the payment form opens is taken from the address information in the Polaris patron record, and may be different from the patron’s credit card billing address. The billing address can be changed on the payment form. Once it is changed, it is not checked against the patron’s record again during the transaction.

• CVV2 - Card Validation Value 2, a security measure that may be provided as part of your PayPal contract with your e-commerce partner. This option requires the user to enter a code usually located on the back of the credit card. Select (check) this option to use CVV2.
• Pre-authorize SALE - Available only when you select AVS and/or CVV2 verification. Select this option to AUTHORIZE a transaction before submitting the SALE transaction. An AUTHORIZE transaction returns an approval/decline without actually charging the cardholder’s account for the full “sale.” Set the amount to a small dollar amount such as $1 (the default) to process the AVS and CVV2 information. If AVS or CVV2 fails, the cardholder is warned, and the actual charge is not placed on the credit card account. This eliminates the need for VOID/CREDIT processing of a SALE based on failed AVS or CVV2. If the AUTHORIZE transaction is approved and AVS/CVV2 passes all tests, then a SALE transaction is issued for the full amount. If a SALE is declined for the full amount, the new VOID or CREDIT option would be used to cancel the SALE transaction.

Note:
An AUTHORIZE transaction will still place a small hold (for example, $1) on the credit cardholder’s funds. Depending on the cardholder's bank, the hold may remain for 24 hours to a week. While this style of processing credit card payments can help reduce SALE issues based on AVS and CVV2 processing, it requires an additional transaction fee for every credit card payment.

7. Click the Supported Credit Cards tab.
8. Select (check) the types of credit cards your provider supports, and click OK. The PayPal properties dialog box closes.

Note:
You can set the credit card types at the system, library, or branch level. The Supported Credit Cards tabbed page indicates the organization from which the settings have been inherited. If you make a change at the branch level, the branch name is displayed on the tabbed page. To revert to the settings of a higher level organization, clear all the check boxes and click OK. Then open the tabbed page again. The settings of the higher level organization are displayed, and the name of the organization is displayed on the tabbed page.

9. To set up credit card payments from Polaris PowerPAC, follow these steps:

1. Click the PowerPAC tab on the Online Payments Settings dialog box, if it is not already selected.
2. Select (check) Allow online payments. The payment options become available.

Tip:
You can use this setting to prevent payments so small that they are offset by your e-commerce provider’s transaction fees.

3. Set the minimum fine amount you want to accept by credit card payment. The default value is the lowest possible value, $0.01. If the amount the patron owes falls below your setting, the Pay fines link is not displayed in the PAC.
4. To charge a processing fee for fine payments, specify the amount in the Processing fee box for online payments. The maximum value is $20.00.
5. If you want patrons to receive an automatic payment receipt, select (check) Send email receipt.
6. The e-mail receipt lists each fine covered by the transaction. The patron can specify an e-mail address on the payment form. The sender’s address is that specified in the PAC profile Email notification: Email address of sender.

Note:
The link for paying fines is on the Fines and Fees page of the patron account. Be sure the PowerPAC profile Navigation: Fines & fees is set to Yes for the organization. Enable patron account access - PowerPAC.

7. To display a privacy policy link on the processing fee, payment, and payment verification pages in Polaris PowerPAC, select (check) Display privacy policy. See Privacy and Refund Policy Display Options.
8. To display a refund policy link on the processing fee, payment, and payment verification pages in Polaris PowerPAC, select (check) Display refund policy. See Privacy and Refund Policy Display Options.
9. To accept credit card payments for donations, select (check) Allow donations.
10. To charge a processing fee for donations, specify the amount in the Processing fee box for donation payments. The maximum value is $20.00.
11. To allow donors to direct a donation toward a title purchase in a specific subject area, select (check) Allow patron to designate title purchase. This option places an appropriate control on the donations page, where the donor can specify a title purchase.

10. To set up credit card payments from the staff client, follow these steps:

1. Click the Staff Client tab on the Online Payments Settings dialog box.
2. Select (check) Allow online payments.
3. Set the minimum fine amount you want to accept by credit card payment.
4. To charge a processing fee for fine payments, specify the amount in the Processing fee box for online payments. The maximum value is $20.00.
5. To provide an automatic e-mail payment receipt to patrons, select (check) Send email receipt. The e-mail receipt is sent to the e-mail address in the patron record. If the patron record does not include an e-mail address, no e-mail receipt is sent. The staff member cannot specify an e-mail address during the payment process.
6. If staff workstations have credit card readers but you also want to allow manual data entry, select (check) Allow manual credit card data entry if card reader is attached.

11. To set up credit card payments from Polaris ExpressCheck, follow these steps:

1. Click the ExpressCheck tab on the Online Payments Settings dialog box.
2. Select (check) Allow online payments. The payment options become available.
3. Set the minimum fine amount you want to accept by credit card payment.
4. To charge a processing fee for fine payments, specify the amount in the Processing fee box for online payments. The maximum value is $20.00.
5. To provide an automatic e-mail payment receipt to patrons, select (check) Send email receipt. The e-mail receipt is sent to the e-mail address in the patron record. If the patron record does not include an e-mail address, no e-mail receipt is sent. The patron cannot specify an e-mail address during the payment process.
6. To display a privacy policy link on the processing fee, payment, and payment verification pages in Polaris ExpressCheck, select (check) Display privacy policy. See Privacy and Refund Policy Display Options.
7. To display a refund policy link on the processing fee, payment, and payment verification pages in Polaris ExpressCheck, select (check) Display refund policy. See Privacy and Refund Policy Display Options.

12. To set up credit card payments from Mobile PAC, follow these steps:

1. Click the Mobile PAC tab on the Online Payments Settings dialog box.
2. Select (check) Allow online payments. The payment options become available.

Note:
Credit card payments for fines and fees are allowed from Mobile PAC if both the patron’s registered branch and the Mobile PAC connection organization allow credit card payments.

Tip:
You can use this setting to prevent payments so small that they are offset by your e-commerce provider’s transaction fees.

3. Set the minimum fine amount you want to accept by credit card payment. The default value is the lowest possible value, $0.01. If the amount the patron owes falls below your setting, the Pay fines link is not displayed in Mobile PAC.
4. To charge a processing fee for fine payments, specify the amount in the Processing fee box for online payments. The maximum value is $20.00.
5. If you want patrons to receive an automatic payment receipt, select (check) Send email receipt. For fine receipts, the system uses the setting of the patron’s branch. For donations (see step h below), the system uses the setting of the donation’s receiving branch. The e-mail receipt lists each fine covered by the transaction. The patron can specify an e-mail address on the payment form. The sender’s address is that specified in the PAC profile Email notification: Email address of sender.
6. To display a privacy policy link on the processing fee, payment, and payment verification pages in Mobile PAC, select (check) Display privacy policy. See Privacy and Refund Policy Display Options.
7. To display a refund policy link on the processing fee, payment, and payment verification pages in Polaris Mobile PAC, select (check) Display refund policy.See Privacy and Refund Policy Display Options.
8. To accept credit card payments for donations, select (check) Allow donations.
9. To charge a processing fee for donations, specify the amount in the Processing fee box for donation payments. The maximum value is $20.00.
10. To allow donors to direct a donation toward a title purchase in a specific subject area, select (check) Allow patron to designate title purchase. This option places an appropriate control on the donations page, where the donor can specify a title purchase.

13. Click OK to save your settings.

Test Values for Payflow Pro Processing

Use the values in the following tables to test Payflow Pro credit card transactions.

Credit Card Numbers

Use the following credit card numbers for testing. Any other card number produces a general failure.

Credit Card Type	Account Number
American Express	378282246310005
American Express	371449635398431
Amex Corporate	378734493671000
Australian BankCard	5610591081018250
Diners Club	30569309025904
Diners Club	38520000023237
Discover	6011111111111117
Discover	6011000990139424
JCB	3530111333300000
JCB	3566002020360505
MasterCard	5555555555554444
MasterCard	5105105105105100
Visa	4111111111111111
Visa	4012888888881881
Visa	4222222222222

Result Codes Resulting From Amount Submitted

Amount	Result (RESPMSG)
$0 - $1000	0 (Approved)
$1001 - $2000	Certain amounts in this range return specific result codes. These can be generated by adding $1,000 to that result code. For example, for result 13 (Referral), submit the amount $1013. If the amount is in this range but does not correspond to a result code supported by this testing mechanism, result 12 (Declined) is returned.
$2001+	12 (Declined)

Testing AVS - Address (AVSADDR)

Submitted Value for STREET	Example STREET Value	AVSADDR Result
000-333	24285 Elm	Y
334-666	49354 Main	N
667 or higher or begins with a non-numeric character	79232 Maple	X

Testing AVS - Zip (AVSZIP)

Submitted Value for ZIP	Example ZIP Value	AVSZIP Result
00000-50000	00382	Y
5001-99999	94303	N
Any value (if street address is 667 or higher or begins with a non-numeric character)	STREET=79232 Maple, ZIP=20304	X

Testing CVV2MATCH

CVV2 Value	CVV2MATCH Value
000-300	Y
301-600	N
601 or higher	X

Credit Card Error Logs

Credit card log files track errors, warnings, and information about credit card transactions made with Payflow Pro. These are located in the following folders:

Staff client transactions -
C:\ProgramData\Polaris\[version]\Logs\Polaris_Errors_[machine]_[date].log

Polaris PowerPAC transactions -
C:\ProgramData\Polaris\[version]\Logs\POWERPAC\
PowerPAC_Errors_[machine]_[date].log

Mobile PAC transactions -
C:\ProgramData\Polaris\[version]\Logs\MOBILEPAC\
MobilePAC_Errors_[machine]_[date].log

Polaris ExpressCheck transactions -
C:\ProgramData\Polaris\[version]\Logs\ExpressCheck_Errors_[machine]_[date].log

If you set up automatic e-mail for errors that require staff intervention (see Set up PayPal Payflow Pro credit card payments), note that these are also included in the log files. Check the log files regularly to be sure that credit card processing is working properly.

Note:
The e-mail receipts sent to patrons for fine and Polaris Fusion payments also include a message if an error occurred that requires the patron to contact the library. Four language strings support this feature:
PACML_PAYMENT_EMAIL_FINESRECEIPT_1063
PACML_PAYMENT_EMAIL_FINESRECEIPT_1064
PACML_PAYMENT_EMAIL_FUSIONRECEIPT_CONTACT
PACML_PAYMENT_EMAIL_FUSIONRECEIPT_SUCCESS
You can view and edit the text in these language strings with Polaris WebAdmin (Language Editor). See the WebAdmin help file for more information.