Sphere Custom Payment Processor Guide
10/15/2013 Blackbaud Sphere 9.4.3 Sphere Custom Payment Processor US 2013 Blackbaud, Inc. This publication, or any part thereof, may not be reproduced or transmitted in any form or by any means, electronic, or mechanical, including photocopying, recording, storage in an information retrieval system, or otherwise, without the prior written permission of Blackbaud, Inc. The information in this manual has been carefully checked and is believed to be accurate. Blackbaud, Inc., assumes no responsibility for any inaccuracies, errors, or omissions in this manual. In no event will Blackbaud, Inc., be liable for direct, indirect, special, incidental, or consequential damages resulting from any defect or omission in this manual, even if advised of the possibility of damages. In the interest of continuing product development, Blackbaud, Inc., reserves the right to make improvements in this manual and the products it describes at any time, without notice or obligation. All Blackbaud product names appearing herein are trademarks or registered trademarks of Blackbaud, Inc. All other products and company names mentioned herein are trademarks of their respective holder. Custom Payment Processor- 2013
Contents CUSTOM PAYMENT PROCESSOR 1 Payment Processor Overview 1 Accessing the Manage Payment Processors Feature 2 Creating and Modifying a Custom Payment Processor 5 Managing a Custom Payment Processor after it is Created 8 Testing a Custom Payment Processor 13 Payment Processor Specifications 14
chapter 1 Custom Payment Processor Payment Processor Overview 1 Accessing the Manage Payment Processors Feature 2 Creating and Modifying a Custom Payment Processor 5 Managing a Custom Payment Processor after it is Created 8 Testing a Custom Payment Processor 13 Payment Processor Specifications 14 This chapter includes detailed explanations on how to create a custom payment processor. Payment Processor Overview A payment processor communicates with a payment gateway and merchant banks when processing transactions (see figure below). When creating your Sphere account, Blackbaud establishes a default payment processor for the account that enables your organization to accept online payments from supporters. Sphere supports online transactions made by credit card or ACH, and processes all transactions via the account s default payment processor unless you otherwise specify. Note: As of January 1, 2014, Sphere's default payment processor only supports United States and Canadian currencies. For Sphere to process other currencies, you must use a custom payment processor.
2 CHAPTER 1 Before May 2009, changing a payment processor (or creating a custom payment processor) required that you contact your Sphere sales representative, and then a Blackbaud resource would complete the request. Now, you can create custom payment processors when you want, and determine which payment processor will be the default payment processor for all online transactions as well as associate initiatives and Virtual Accounts to specific custom payment processors. To create and manage custom payment processors, the Manage Payment Processor feature must be enabled in the account. When you create and use custom payment processors, you are responsible for establishing a relationship with a processor service and then a payment gateway. Additionally, you must set up the bank (merchant) account where the payment processor will send (or deposit) money collected from online transactions, and you are responsible for providing Blackbaud the information Sphere requires to communicate with the payment gateway. If you want Sphere to reconcile transactions sent to the payment gateway, you must also provide the login for the payment gateway. Note: To process American Express transactions, you must directly establish a merchant account with American Express. How It Works When a supporter submits a transaction from an initiative form, the payment gateway (for example, PayPal Payflow Pro) authenticates the Web site and sends the details of the transaction to a payment processor if authentication is successful. The payment processor communicates with the credit card issuing bank (such as Bank of America) to authorize the transaction. If the transaction is authorized, the payment processor will process funds to your organization s bank account. If you need to know what transactions the payment processor processed, you can generate (or request) reports from the payment processor service. Sphere enables you to create a payment processor report that shows activities regarding custom payment processors created or modified, and those associated with initiatives or Virtual Accounts. Payment Gateways and Processors Supported in Sphere For a list of payment gateways and processors supported, see Payment Processor in General Specifications. Accessing the Manage Payment Processors Feature When the Manage Payment Processors feature is enabled in the account, Sphere adds the Manage Payment Processors menu, Payment Processing Information for Initiatives, and Disbursement Information for Initiatives to the following locations: Access this Via Functional Access Rights Manage Payment Processor menu Control > Administration > Organization Setup > Manage Payment Processors Full Access No Access (this is the default) Payment Processing Information for Ini- Control > Administration > Organization Setup > Manage Users > Manage Functional Access > Spe- Note:View-only is not selectable, even if you create a custom functional access. Full Access No Access (this is the default)
CU STOM PAYMEN T PROCESSOR 3 tiatives Disbursement Information for Initiatives cial Functions Control > Administration > Organization Setup > Manage Users > Manage Functional Access > Special Functions Full Access View-only No Access (this is the default) Use Manage Payment Processor to create and manage custom payment processors. To access it, you must have functional access to Manage Payment Processors. If the account is structured by Virtual Accounts, you must be logged into the (System) Administrator Virtual Account. Additionally, if there are non-system functional access groups in the account or Virtual Account and users are assigned those functional accesses, the system will not automatically update the functional access for Manage Payment Processors. You must manually assign users functional access to Manage Payment Processors. Use Payment Processing Information for Initiatives to associate events with specific payment processors. You can associate an event with a payment processor at the event level or form level. Use Disbursement Information for Initiatives to associate a custom payment processor with a Virtual Account. Transactions for all events created in the Virtual Account will be processed by the payment processor you specify as the default payment processor for the Virtual Account. } Access the Manage Payment Processors feature Use this procedure to access the Manage Payment Processors feature in Sphere so that you can create and manage custom payment processors. Prerequisites Manage Payment Processor is enabled in the account You have Administrator (System) functional access to the account or Virtual Account You have functional access to Manage Payment Processors Starting point: You are logged into the account or Virtual Account as administrator. 1. Select Control > Administration > Organization Setup > Manage Payment Processors. The Manage Payment Processors page opens and displays the following: All custom payment processors created in the account. All custom payment processors we created for the account before May 2009. All Blackbaud payment processors associated with the account (the payment processor s name associated with the default contract for the account is preceded with an asterisk, for example, *VS/Pmntech/ Kintera). Note: If the account is structured by Virtual Accounts, the list will be filtered to only show the payment processor for the Virtual Accounts of the logged in user. } Enable users to access and manage a custom payment processor Use this procedure to enable users to access and manage a custom payment processor. By default, only users with Administrator (System) functional access can access and use the Manage Payment Processor feature. If you want all other System users to access and use Manage Payment Processor, you must create a custom functional
4 CHAPTER 1 access group, change the Manage Payment Processor functional access rights for the group, and then assign users the new functional access. Prerequisites Manage Payment Processor is enabled in the account You have Administrator (System) functional access to the account or Virtual Account You have functional access to Manage Payment Processors Starting point: You are logged into the account or Virtual Account as administrator. The Manage Users page is displayed. If not, select Control > Administration > Organization Setup > Manage Users. Enable non-system administrator users to create custom payment processors 1. Click Manage Functional Access. 2. In the resulting window, perform the following steps: a. Select the custom privilege (functional access) group or create a new custom group to which you want to grant privileges for managing custom payment processors. b. Expand Control > Administration > Organization Setup. c. Click the Manage Payment Processors folder. d. Change Access Right settings for the folder to Full Access. e. Click Save. Note: We recommend that only the core system administrator be a member of the Administrator (System) functional access group, and that all other users be members of custom privilege groups. This is because the Administrator functional access group has unlimited access to every feature and function in Sphere. With custom privilege groups, you can control who has access to new features when they are added to Sphere. Enable non-system administrator users to associate custom payment processors to events 1. Expand Special Functions. 2. Click the Payment Processing Information for Initiatives folder. 3. Change Access Right settings for the folder to Full Access. 4. Click Save. Enable non-system administrator users to change the Disbursement Location for events 1. With Special Functions expanded, click the Disbursement Information for Initiatives folder. 2. Change Access Right settings for the folder to Full Access. 3. Click Save.
CU STOM PAYMEN T PROCESSOR 5 Creating and Modifying a Custom Payment Processor Create a custom payment processor when you want to change the default payment processor already set up for the account. You can set the new payment processors as the default for new transactions, and you can also modify existing events to switch to the new payment processor so that new transactions from those events will be processed by the payment processor you specify. By default, the Manage Payment Processors functional access rights for the Administrator (System) functional access group is Full Access. For all others, it is No Access and cannot be changed. Note: If you want other System users to access Manage Payment Processors, you must create a custom functional access (privilege) group, change the functional access rights for Manage Payment Processors to Full Access, and then assign users this functional access. All custom payment processors you create are added to the payment processor list (see figure below). You can change existing settings by editing a custom payment processor. When you create or modify a custom payment processor, the system automatically sends an E-mail notification to Blackbaud, notifying us that a new payment processor was created or modified. Included in the notification is the payment processor s ID and name, and the name of the user who created (or modified) the payment processor. You can view change details for a custom payment processor via a user s Activity Log. Transaction Fees and Custom Payment Processors When you create a custom payment processor, you must negotiate transaction fees with the payment gateway and the payment processor. Blackbaud also applies an additional gateway interconnect fee to your Blackbaud Sphere Transaction Fee. If you use the Blackbaud payment processor, all custom payment processors will use the Blackbaud Sphere Transaction Fees from the account s default contract and an additional interconnect fee to your custom payment gateway. If your Sphere account has multiple contracts and payment processors with different transaction fees for each, you can only rename a payment processor. } Create a custom payment processor Use this procedure to create a custom payment processor. After creating a custom payment processor, you can select it for initiatives or Virtual Accounts and change the default payment processor already set up for the account. Note: Before you create a custom payment processor, make sure you have all of the login information you will need to provide to Sphere for the payment gateway. Prerequisites The Manage Payment Processors feature is enabled in the account You have Administrator (System) functional access to the account or Virtual Account You have functional access to Manage Payment Processors The merchant account where funds will be deposited is already established Starting point: You are logged into the account or Virtual Account as administrator. The Manage Payment Processor page is displayed. If not, select Control > Administration > Organization Setup > Manage Payment Processors.
6 CHAPTER 1 1. Click New. The Properties page for the new payment processor opens. 2. Complete the steps below. Step 1: Configure payment processor properties 1. For Name, enter a name for the custom payment processor. 2. For Description, briefly describe the payment processor. 3. The ID field is empty until you create a new payment processor. Then, it will display the payment processor s system-generated ID. You cannot change the payment processor ID after it is created. 4. For Status, select one of the following options: Click Active to enable the custom payment processor to process online transactions for all initiatives or specific initiative. Users will see, and can select, the custom payment processor when they create an initiative or set the default payment processor for a Virtual Account. Click Inactive if you no longer want a custom payment processor to be active. The payment processor will not be deleted from the database, but will not be used to process online transactions. You can always activate an inactive payment processor. You cannot deactivate all custom payment processors because there must always be an active payment processor to process online transactions. 5. For Merchant, select PayPal to specify the payment processor that will be used to process your online transactions. The transaction authentication credential you configure for each in Step 2 below will be different, as these services require users to provide different authentication information. Note: When you save a custom payment processor, the Merchant field changes to read-only. 6. Currency Type shows the currency type (U.S. Dollar, UK Pounds, and so on) set up for the account when the account was created. 7. Date Created shows the date and time when the custom payment processor was created, or will be empty when you are creating a new custom payment processor. 8. Date Update shows the date and time when the custom processor was last modified, or will be empty when you are creating a new custom payment processor. 9. Owner shows the name of the administrator on record for the account. It will be empty when you are creating a new custom payment processor. Step 2: Configure transaction authentication credentials When you select PayPal for Merchant in Step 1, you must provide authentication credentials that Sphere will send to the payment gateway. Because you are creating a custom payment processor, you should already have received this information from your payment processor service (PayPal Payflow Pro). Sphere requires it to communicate with the payment gateway. 1. For Partner, enter the information you were provided by the payment gateway service. 2. For Merchant Login, enter the login information you were provided by the payment gateway service. 3. For Password, enter the password information you were provided by the payment gateway. For security reasons, we mask the information as you enter it to protect the data. 4. For Repeat Password, reenter the password. The data will be encrypted for security purposes. 5. For User, enter the user name you will need to provide to Sphere. We need this information to reconcile your transactions, which entails comparing transactions sent from Sphere to the payment gateway
CU STOM PAYMEN T PROCESSOR 7 against transactions actually processed by the payment processor. The payment gateway service should have provided the user name information to your organization. Step 3: Configure Blackbaud reconciliation login Perform this step only if you want Sphere to reconcile transactions processed by the payment gateway. Sphere synchronizes with a payment gateway daily at 5:00am Pacific Standard Time. If your payment processor is PayPal Payflow Pro (or is compatible with the PayPal Payflow Pro payment gateway) and you provide us your PayPal user name (from step 2.1.e above) and password (in step 1 and 2 below), Sphere will also reconcile transactions with the PayPal Payflow Pro payment processor. 1. For User Password, enter the password the payment processor provided to your organization. 2. For Repeat User Password, reenter the password. Step 4: Configure payment methods 1. For Credit/Debit Cards, select the type of credit card to be processed by the payment processor Visa, MasterCard, American Express, or Discover to indicate how supporters will submit payments from an initiative form. 2. If the account is set up to process transactions in UK Pounds, for UK Pound Credit/Debit Cards select the card type Maestro, SOLO, or Switch/UK/Maestro. 3. Other Payment Methods is only displayed when you select PayPal in the Merchant field, and the account is provisioned to process transactions in UK Pounds. Select the check box for ACH if you will allow supporters to make payment with online checks. Step 5: Select Virtual Accounts Virtual Accounts lists all system and custom Virtual Accounts. The Virtual Account into which you are logged in is grayed out and always selected for (System) Administrator Virtual Account and (System) My Records, and for custom Virtual Accounts if the Virtual Account has access to the custom payment processor but the logged in user does not have access to the Virtual Account. You can select a custom Virtual Account if you see a selectable check box. 1. If appropriate, select the check box for any custom Virtual Account for which you want to make this payment processor accessible. Step 6: Save the new custom payment processor 1. Click Save. The Manage Payment Processors page opens and lists the new custom payment processor. Note: When you click Save, the system will check to make sure that the payment processor name you entered is unique and will notify you if the name is already in the database. Additionally, it will check to make the reconciliation credentials you specified for Blackbaud Reconciliation Login (Optional) is unique for all active and inactive payment processors. If there are conflicts, the payment processor will not be saved. Note: When you create a custom payment processor, the system automatically sends an E-mail notification to Blackbaud to inform us that a new payment processor was created. Included in the notification will be the account name, payment processor s ID and name, and the name of the user who created the payment processor.
8 CHAPTER 1 Managing a Custom Payment Processor after it is Created After you create a custom payment processor, you can: Modify the payment processor, including changing an active custom payment processor to inactive (and vice versa). Associate the payment processor with an event Associate a Virtual Account with the payment processor Activate or deactivate a custom payment processor Delete the payment processor Each Sphere account has a primary payment processor and can have up to two failover payment processors when you use the Blackbaud payment processor service to process online transactions. If the primary payment processor fails to process transactions (for example, the service is down), Sphere will attempt to process the transaction via the first failover payment processor, and then the second one if the first payment processor fails. If all payment processors fail, Sphere will place the transaction in a batch queue for later retry. When you create and use a custom payment processor, you are responsible for working with your payment processor service to set up failover payment processors. Modifying a Custom Payment Processor When you modify and save a custom payment processor, the system will automatically: Verify that the payment processor name you entered is unique and will notify you if the name is already in the database. Verify that the reconciliation credentials you specified for Blackbaud Reconciliation Login (Optional) is unique for all active and inactive payment processors. If there are conflicts, the payment processor will not be saved. Send an E-mail notification to Blackbaud to inform us that a new payment processor was created. Included in the notification will be the payment processor s ID and name, and the name of the user who created the payment processor. Verify that events are not associated with the payment processor if you change an active payment processor to inactive, and notify you accordingly. If the account is structured by Virtual Accounts, system will check all events in the account regardless of the Virtual Account of the logged in user. It will also check to make sure that the payment processor is not being used as a default payment processor for a Virtual Account. Associating an Event with a Custom Payment Processor When you create an event, you can associate it with a custom payment processor if you want online transactions from the event to be processed by a specific payment processor. You can also associate an existing event with a custom payment processor. To associate an event with a custom payment processor, the custom payment processors must already exist in the CRM database. When you display the list of payment processors from which you can select, the list shows the payment processor s ID and name (see figure below). Blackbaud payment processor names start with an asterisk (*), for example *500-ICS/FirstData/Sphere/USD.
CU STOM PAYMEN T PROCESSOR 9 When you associate an event with a custom payment processor, the custom payment processor will override the default payment processor set up for the account. Associate an event with a custom payment processor using Payment Processing Information for Initiatives. Activating and Deactivating a Custom Payment Processor You can activate or deactivate a custom payment processor at any time. However, you must always have an active default custom payment processor. The system will not allow you to deactivate all payment processors and will display a message when you attempt to do so. Deleting a Custom Payment Processor You can delete a payment processor if it is not used as the default payment processor for an account or Virtual Account, or if it is not associated with an initiative. Sphere verifies that you can delete a custom payment processor before allowing you to proceed. When you delete a custom payment processor, it is removed from the database and cannot be restored. To delete a custom payment processor, you must have functional access to Manage Payment Processors. } Modify a custom payment processor Use this procedure to change a custom payment processor s settings after it is created. Prerequisites A custom payment processor is created You have Administrator (System) functional access to the account or Virtual Account You have functional access to Manage Payment Processors Starting point: You are logged into the account or Virtual Account as administrator. The Manage Payment Processor page is displayed. If not, select Control > Administrator > Organization Setup > Manage Payment Processors. 1. Highlight the custom payment processor s name, and then select Edit Payment Processor. The Properties page for the custom payment processor opens. 2. Update all necessary fields.if you cannot select a field, it is because the system does not allow you to change it after you create and save a payment processor. 3. Click Save when done.the Manage Payment Processors page opens. Note: When you modify a custom payment processor, the system automatically sends an E-mail notification to Blackbaud contracts to inform them of the change. Included in the notification will be the payment processor s ID, name, and the name of the user who modified it.
10 CHAPTER 1 } Associate an initiative with a custom payment processor Use this procedure to associate an initiative (event or form) with a custom payment processor. All transactions from the initiative will be processed by the custom payment processor you specify. Prerequisites A custom payment processor is created You have Administrator (System) functional access to the account or Virtual Account You have functional access to Manage Payment Processors You have functional access to Payment Processing Information for Initiatives and Disbursement Information for Initiatives The initiative is already created Starting point: You are logged into the account or Virtual Account. The events page is displayed. If not, select Communities > Special Events >event type, or Communities > Form > form type. 1. Highlight the initiative s name and select Properties. The Properties window opens. 2. For Payment Processing and Disbursement Information, select the custom payment processor to which you want to associate the initiative. Note: If you do not see the Payment Processing and Disbursement Information field, it is because you do not have functional access to Payment Processing Information for Initiatives and Disbursement Information for Initiatives. The functional access rights for these fields must be Full Access in order for the field to be displayed in the Properties window. 3. ClickSave. } Select the default payment processor for Virtual Accounts Use this procedure to select the default payment processor for a Virtual Account (or all Virtual Accounts) that will be used as the default payment processor for initiatives created in Virtual Accounts. Prerequisites The account is structured by Virtual Accounts Custom payment processors are already created You have Administrator (System) functional access to the account or Virtual Account You have functional access to Payment Processing Information for Initiatives anddisbursement Information for Initiatives You have functional access to Manage Payment Processors Starting point: You are logged into the Administrator Virtual Account. The Manage Users page is displayed. If not, select Control > Administration > Organization Setup > Manage Users.
CU STOM PAYMEN T PROCESSOR 11 Set up a custom payment processor as default for a specific Virtual Account 1. Click Manage Virtual Accounts. The Virtual Accounts window opens. 2. For Virtual Accounts, select the Virtual Account (System or custom) to which the custom payment processor will apply. Note: All accounts must have a disbursement location and must have a Default Disbursement Location. Use the Disbursement Location field only if Blackbaud is the payment processor and you want to select the disbursement location where we will send a check for money collected from online transactions. If you are using a custom payment processor, you will need to work with the payment processor service regarding where they will deposit your funds. 3. For Payment Processor, select the payment processor that will be used as the default payment processor for the selected Virtual Account. Transactions from all events created from the Virtual Account will be processed by the payment processor you select. 4. Click Save. Set up a custom payment processor as default for all Virtual Accounts 1. In the Virtual Accounts window, perform the following steps: a. For Virtual Accounts, select Administrator Virtual Account (System). Note: When Administrator Virtual Account (System) is selected for Virtual Accounts, you will not be able to change the account s default Disbursement Location. b. For Payment Processor, select the payment processor that will be used as default for all Virtual Accounts and which will process all online transactions. 2. 1. Click Save. Note: This applies to Gift Entry, Import Center, and the Sphere Connect API. It also applies to events if you do not override the default payment processor. } Disable the default Sphere Payment Processor Use this procedure to disable the default Sphere Payment Processor so that no users can use it to process transactions. The default Sphere Payment Processor is active for all new Sphere clients, and you can disable it if you have a custom payment processor. Prerequisites You have Administrator (System) functional access and Administrator Virtual Account Access You have functional access to Manage Payment Processors A custom payment processor is already created Starting point: You are logged into the account or the Administrator Virtual Account. The Manage Users page is displayed. If not, select Control > Administration > Organization Setup > Manage Users.
12 CHAPTER 1 1. Click Manage Virtual Accounts. The Virtual Accounts window opens. 2. For Virtual Accounts, verify that Administrator Virtual Account (System) is selected. 3. For Payment Processor, select the custom payment processor you want to become the default payment processor. Blackbaud payment processor names start with an asterisk (*), for example *2- VS/Pmntech/Kintera. Note: If your account is not configured for Virtual Accounts, you must still follow these exact steps. 4. Click Save, and then close the Virtual Accounts window. 5. Select Control > Administration > Organization Setup > Manage Payment Processors. 6. Highlight the default Sphere payment processor you want to disable, and then select Edit Payment Processor. The Properties page opens. 7. For Status, click Inactive. 8. Click Save. The default Sphere Payment Processor will not be visible to all events and transactions, and your custom payment processor will become the new default payment processor. To reactivate the payment processor, change the Status field to Active. } Delete a custom payment processor Use this procedure to delete a custom payment processor. Prerequisites A custom payment processor is created You have Administrator (System) functional access to the account or Virtual Account You have functional access to Manage Payment Processors Starting point: You are logged into the account or Virtual Account as administrator. The Manage Payment Processor page is displayed. If not, select Control > Administrator > Organization Setup > Manage Payment Processors. 1. Select the check box for the payment processor you want to delete. 2. Click Delete. 3. Confirm that you want to delete the payment processor. The system will first check to make sure that active events are not associated with the custom payment processor. Additionally, if the account is structured by Virtual Accounts, the system will verify that the custom payment processor you are deleting is not the default payment processor for a Virtual Account. If you delete a custom payment processor from a Virtual Account, it will continue to be displayed in the administrator Virtual Account. 4. Verify that the payment processor is removed from the list of custom payment processors. Note: When you delete a custom payment processor, it is removed from the database and cannot be recovered. You cannot delete the Blackbaud payment processor or Blackbaud-owned payment processor.
CU STOM PAYMEN T PROCESSOR 13 Testing a Custom Payment Processor After you create a payment processor, test it to make sure that online transactions can be processed before you activate the initiative. Work with your payment processor service to receive a report of the test transactions. You should test transactions, and reversals of transactions, from events in Sphere with your custom payment processor before you go live with an event using the custom payment processor. In Sphere, you can create a Payment Processor History report to see all changes made to all custom payment processors created in the account, or create a report that shows payment gateway responses and other information regarding a payment so that you can verify the payment was successfully processed. } Test a custom payment processor Use this procedure to test a custom payment processor by: Creating a report that shows all changes made to all custom payment processors for the account. Displaying the payment, and payment gateway, information for a specific payment ID Prerequisites A custom payment processor is created You have Administrator (System) functional access to the account or Virtual Account You have functional access to Manage Payment Processors You have functional access to Report Center Events are linked to a custom payment processor Transactions have been sent to the payment gateway Starting point: You are logged into the account or Virtual Account. The Report Templates page is displayed. If not, select Control > Report Center. Creating a report for custom payment processor changes When you create a custom payment processor, you are responsible for making sure that it successfully processed your online transactions. The best test is to view reports generated by your custom payment processor service. This procedure explains how to view changes made for all payment processors in the account. 1. On the Report Templates tab, expand Billing. 2. Click Payment Processor History Report. The Report Templates tab refreshes and displays the Choose Data page. 3. Perform the following steps for Properties: a. In the Choose Data column, select the check box for all fields you want to show in the report. Several fields are checked by default and are listed under Selected Columns. If you want to remove a field from Selected Columns, uncheck it from Choose Data. b. Sort the Select Columns list to specify the order by which the fields will displayed in the payment
14 CHAPTER 1 processor report by clicking a field and then clicking the directional arrows to reposition it where you want. 4. Click Finish. A page opens to notify you that the report is being generated. When done, the Payment Processor History Report page opens and shows the transactions reported back from the payment gateway. Displaying the payment and payment gateway information for a specific payment ID This procedure explains how to create a report that shows payment gateway responses and other information regarding a payment so that you can verify the payment was successfully processed. 1. In the Report Templates tab, expand Configuration. 2. Click Payment Processor Report. The Payment Processor Report page opens. 3. For Enter Payment ID, enter the transaction ID. You can acquire this information from Contacts > Gifts and then select Payments. 4. Click Finish. Payment Processor Specifications Payment Processor and Custom Payment Processor Credit card payment gateway Cybersource ICS (when the payment gateway is hosted on Blackbaud servers) ACH payment gateway Credit card payment processor ACH payment processor PayPal Payflow Pro (when clients work directly with a payment gateway) Beanstream (when the payment gateway is hosted on Blackbaud servers) PayPal Payflow Pro (when clients work directly with a payment gateway) FirstData (when the payment processor and gateway are hosted on Blackbaud servers) Any payment processor that is compatible with PayPal Payflow Pro (when clients work directly with a payment processor) Beanstream (when the payment processor and gateway are hosted on Blackbaud servers) Any ACH payment processor that is compatible with PayPal Payflow Pro (when clients work directly with a payment payment gateway)
CU STOM PAYMEN T PROCESSOR 15 Number of payment gateways per account/currency Number of custom payment processors you can create per account Number of custom payment processors you can set up per Virtual Account Number of default custom payment processors you can set up per Virtual Account Number of payment processors that can be active at one time Number of payment processors you can associate with an initiative 1 Unlimited Unlimited 1 Unlimited for accounts 1 for each initiative 1
16 CHAPTER 1