Configuring Payment Connector Vendors

Overview 

Many TargetX clients utilize Elavon Incorporated’s Converge (formerly known as VirtualMerchant) as a payment gateway for various admissions, student success, and advancement related activities. To help make the process of getting set-up on Converge as smooth as possible, we have provided a few guiding points below. However, make sure you get the most current information from your Converge representative directly in case anything below has changed!

TargetX Basics 

To set up Converge payments on the TargetX side please refer to the article  Configuring Payment Connectors.
As part of our CRM implementation, we will:

• Provide you with a link to the Salesforce documentation listing the IP address(es) to the Salesforce server(s) for Test and Production (You will be asked for this by Converge.)
• Work with you and Converge to attempt a test connection from TargetX CRM to uPay

Note: Salesforce does not recommend the use of IP Allowlisting for their servers. You can read more in the Salesforce article Introducing Hyperforce - General Information & FAQ. If your Salesforce org has transitioned to Hyperforce (expected by the end of 2024), and your payment connector requires IP Allowlists, then you may need to use the IP addresses outlined in the Salesforce article Hyperforce External IPs. 

Converge Tidbits 

Converge requires a secure key.  The secure key is a parameter that is attached to all notifications, not just payment notifications, that will validate the source of the transaction.  In most cases the key will already be configured, and this step can be ignored.  

1. Navigate to the CustomKey Visualforce Page
   • Go to Setup and search for Visualforce Pages.
   • Find CustomKey and click preview.
2. Enter the value desired as the custom key and save

Configuring your Converge Account 

TargetX has no access to your Converge account and cannot configure the account for you.  The instructions provided below are more-or-less accurate but might not pertain to your institution's exact requirements.  

To configure Converge you will need to contact their Customer Support line.  They can be reached at 866-548-6826.  They will ask you for the following information:

• Business/School Name
• What services will require online payment 
• The typical amount of the online fee
• A customer service number, for payees to call should their be a problem
• Your institution's Privacy Policy and Refund Policy

Elavon will provide you with an application form requesting, among other things, what bank account numbers to use, the web address (URL) of your payment site, and the person(s) responsible for managing the online fee payment process.  TargetX can help you with completing this form, but in many cases the answers will come from your own IT department or Elavon.

TargetX has no access to your Converge account and cannot create the account for you.  We can, however, assist with connecting your TargetX applications to Converge and testing the Converge payment processes once you and Elavon have configured it.

Next steps 

Contact Elavon Inc. at the number above and request either new Converge services, or an additional storefront if you are already using Converge.

Configuring the Converge Payment Connector

1. ​Login to the Converge site: https://demo.myvirtualmerchant.com/VirtualMerchantDemo/login.do
2. For the payment detail to be updated after a transaction has occurred, a custom field for the Payment Detail ID needs to be created.
3. Create the Payment Detail ID field:
4. Login to Converge’s website
5. Hover over Terminal. There will be a dropdown menu. Hover over Merchant > Payment Fields
6. Locate section titled Custom Fields. Click Add New Field.
7. Fill in the following field values:

• Name: paymentDetailId (case-sensitive; must match exactly)
• Display Name: Payment Detail Id
• Section: Custom Fields
• Field Type: Text
• Maximum Number of Characters: 255
• Show in Virtual Terminal: checked/true
• Shown On Receipt: checked/true
• Forward on Approval: checked/true
• Forward on Decline: checked/true

8. Click Add New Field.
9. Set the responseHandler site in Converge:
   1. Login to Converge’s website
   2. Hover over Terminal. There will be a dropdown menu. Hover over Advanced > System Setup.
   3. Locate section titled Export Options. Fill in the following field values:

• * unmentioned fields should have no values
• paymentDetailId, Approval URL, Declined URL, and Error URL: responseHandler set with secureKey attached to the end as a URL parameter
• Enable Export Script: checked/true

8. Click Update.

Converge Page Layout

If you are using the New Converge Gateway, you must update your Converge Page Layout with new fields:

1. Navigate to Setup and select Object Manager.
2. Click the Payment Connector object and select Page Layouts.
3. Click Converge Layout.
4. Drag the new fields onto the layout:
   1. Converge Merchant ID
   2. Converge Partner App ID
   3. Converge Vendor ID
   4. Post URL
   5. Post Verify URL
   6. Postback Verify URL

Note: The Converge PIN field has been deprecated and can be removed from the Page Layout.

Converge Remote Site Settings

You must add additional Remote Site Settings for sandbox and production:

1. Navigate to Setup and search for Remote Site Settings.
2. Click New Remote Site.
3. Enter the following information, depending on whether you use a sandbox or production org. You will need to create TWO remote sites for sandbox and TWO for production: 
   • Suggested Remote Site Name: Converge sandbox API
     • Remote Site URL: https://api.demo.convergepay.com
   • Suggested Remote Site Name: Converge sandbox
     • Remote Site URL: https://demo.convergepay.com
   • Suggested Remote Site Name: Converge production API
     • Remote Site URL: https://api.convergepay.com
   • Suggested Remote Site Name: Converge production
     • Remote Site URL: https://www.convergepay.com
4. Active: should be checked. 
5. Click Save.

Behavior of the CRM and payment gateway transaction: 

• Gateway: payment gateway vendor.
• Confirmation Page Location: location where the user lands on confirmation of payment.
• Receipt Page Location: location where the user lands on receipt of payment.
• Asynchronous Confirmations: does the CRM wait until the confirmation is completed by the payment gateway?
• Key Required: is a shared key required for this payment gateway?

Converge Required Fields 

• Gateway Account Name
• Converge Merchant ID
• Converge User ID
• Converge Pin (deprecated)
• Converge Partner App ID
• Converge Vendor ID
• Post URL
• Post Verify URL
• Postback Verify URL

Troubleshooting Payment Connector problems with Converge

Assign Page Layout  

1. Navigate to Setup and select Object Manager.
2. Click on the Payment Connector object. 
3. Navigate to the “Page Layout” section and select the Page Layout Assignment button. 
4. Select Edit Assignment. 
5. Scroll to the Cybersource column and select the column. 
6. In the Page Layout To Use list, select Cybersource Layout. 
7. Save your changes. 

Configure Payment Connector Record Types  

1. Navigate to Setup and search for Profiles. 
2. Click on the System Administrator profile. 
3. Navigate to the “Record Type Settings” section. 
4. Select Edit next to Payment Connectors. 
5. From the “Available Record Types”, select Cybersource and Add. 
6. ​Save your changes. 

​Create Payment Connector record  

1. Navigate to your Payment Connectors tab. 
2. Select New. 
3. Enter the following: 
   • Gateway Account Name = CyberSource Payment Gateway 
   • CyberSource Profile ID = <Profile ID from CyberSource> 
   • CyberSource Access Key = <Access Key from CyberSource> 
   • CyberSource Custom Key = <Custom Key from CyberSource> 
   • Sandbox = unchecked 
   • Server = https://secureacceptance.cybersource.com/pay (for production) 
   • CyberSource Locale Code = en-US 
   • Currency Code = USD 

Behavior of the CRM and payment gateway transaction 

• Gateway: payment gateway vendor.
• Confirmation Page Location: location where the user lands on confirmation of payment.
• Receipt Page Location: location where the user lands on receipt of payment.
• Asynchronous Confirmations: does the CRM wait until the confirmation is completed by the payment gateway?
• Key Required: is a shared key required for this payment gateway?

Cybersource Required Fields 

• Gateway Account Name
• Cybersource Profile ID
• Cybersource Access Key
• Cybersource Custom Key (this is provided by Cybersource)
• Server
• Cybersource Locale Code
• Currency Code

Transact Payments (CASHNet)

Transact Payments (CASHNet)

1. ​Navigate to Transact Payments (CASHNet) and log in.
2. Once logged in, navigate to the Home tab.
3. Click ‘Store Setup’ along the left side menu.
4. From the dropdown menu (you have to click the arrow), select the information provided to your institution. You will be redirected upon selection.
5. Click ‘Notifications’ along the left side menu.
6. Replace the ‘for successful transactions’ URL with the responseHandler site you configured earlier. Optionally, you can fill in the ‘for failed transactions’ field.
7. Click Save.
8. Click ‘Implement Store’ along the left side menu.
9. ​Click Continue.

Note: Ensure that the ?secureKey= parameter is appended to the Response URL in Transact Payments (CASHNet).

 
This means that the system MUST send all 10 of these parameters, in the exact order listed, with every payment transaction. By default, TargetX CRM will automatically include 4,5,6,7,8,10. You must specify the missing parameters and values in the proper Application formula field referenced above. 
 
In this sample, the actual formula would be: 
"userId=" & TargetX_SRMb__Contact__c & "&" & 
"fullName=" & TargetX_SRMb__Contact__r.FirstName & " " & TargetX_SRMb__Contact__r.LastName & "&" & 
"orderType=application_fee" & "&" & 
"retriesAllowed=0"