Payment Connector Release Notes

April 2023

Version 2304.0

• The Converge Payment Connector has been refactored to use the new Hosted Payments flow. For more information, see Configuring Payment Connectors.
• The following fields have been added to the Payment Connector Object as part of the Converge Hosted Payments setup: Converge Partner App ID, Converge Vendor ID, Post Verify URL, and Postback Verify URL. Visit the latest Upgrade Guides from the TargetX User Community to learn how to apply this new field.

February 2023 

VERSION 2302.0

• Administrators can configure custom parameters for WPM. For details, see Configuring Custom Parameters for your Payment Gateway.
• New fields/Visualforce Pages:

August 2022

• Documentation is available on updating Payment Connector records to work with Enhanced Domains. For more information, see Updating Payment Connectors for Enhanced Domains.

October 2021

VERSION 2110.0

• A new payment connector for RTS is now available. For more information, see Configuring Payment Connectors. 
• New fields:

December 2019

VERSION 1912.10

• Payment Connectors now use specific Access Keys for each Payment Connector record.

October 2019

VERSION 1910.2

• Administrators can pass custom parameters to Converge e.g. Student/applicant name. For additional information, please see Configuring Custom Parameters for your Payment Gateway.

August 2019

VERSION 1908.4

• TargetX Logs for Payments will now create logs when:
  • A User is directed to a Payment Vendor for Application Fee payments.
  • A Successful Application Fee payment is submitted for Touchnet.
  • A Credit Card FAILS authorization for TouchNet.
  • When Multiple payment attempts are detected for a purchase

July 2019

VERSION 1907.0

• TargetX Logging has been enhanced for Payment Connector error handling. 

May 2019

VERSION 1905.0

• This release includes new “stripped-down” layouts for every custom TargetX object in the Payment Connector package to facilitate restricting access to Salesforce pages in Communities.

February 2019

VERSION 1902.5

• A new Payment Connector for WPM is now available. For more information, see Configuring Payment Connectors.

April 2018

VERSION 1804.2

• Administrators now can customize a message for Nelnet payments to display after a user submits a payment. For more information,  see Customizing the message users receive after submitting a payment.
• Administrators can set the time before a user is redirected for Nelnet payments. For more information,  see Setting the 'redirect time' for Payments.
• New Objects/Fields:

March 2018

VERSION 1803.0

• Compatibility with Converge’s switch from myvirtualmerchant to api.converge.pay.com.

Fall 2017 

VERSION 17.40001

• Update for a custom implementation of Nelnet QuikPay.

August 2017

VERSION 17.30011

• The Custom Label for Touchnet will now alert a user to the potential of a duplicate payment regardless of the status of the new payment. For more information see Payment Connectior FAQ

Summer 2017

VERSION 17.30008

• Custom Response Parameters can now be mapped to fields on the Payment Detail record so that additional data can be recorded from the Payment Vendor; applies to Paypal, Cashnet, Campus Solutions, Nelnet, and Converge.
  • When a Payment Response Mapping record is filled out, the parameter value will be stored on the Payment Detail record when a payment is executed.
  • Targetx Logging will log messages related to response mapping references.​

• New Objects/Fields:

Spring 2017 SP

VERSION 17.20001

• For Touchnet payments, the Confirm payment​ button will no longer be available if an anomaly is detected with the payment (e.g., a successful payment has already been submitted).  In addition, Administrators now have the ability to define a custom message to display to the user when this occurs.

• Administrators now have the ability to pass custom data to Touchnet from the Online Application for Application Fees and Enrollment Deposits paid via the Online Application home page and Portal. The new workflows are as follows:

  • If the Application Custom Data field contains a valid Application field, the system will pass that Application's field value as the Ancillary ID to TouchNet
  • If the Application Custom Data field is empty or contains an invalid Application field, the system will send the default values (indicated below) as the Ancillary ID to TouchNet.
  • If Application Custom Data field contains a valid Application field, and that Application's field value is blank, the system will send the default values indicated below as the Ancillary ID to TouchNet.

Default Values:

<Application Type> Application for Admission

<Application Type> Enrollment Deposit

Spring 2017

VERSION 17.10001

• Implemented a new CyberSource Payment Connector into existing Payment Connector to provide an additional payment gateway for clients. 
• Updated code for Nelnet in order to store the necessary data in Salesforce.
• Added compatibility with Nelnet Commerce Manager Payment Connector.

Summer 2016 SP

VERSION 1.56

• The TouchNet Payment Gateway has been updated to allow client specific data to be passed via the External_Trans_id field. 

  • The payment parameter called External_Trans_Id can now be configured to accept data from a field on the Application object.
  • Administrators can specify the data that is stored in the External_Trans_Id field, on the Application object. 

• Design changes were made to address a Touchnet Issue with Ancillary ID in Payment Connector.  TouchNet integration allows its users to pass in any custom data that can be reflected in their transaction reports. In some cases, schools want to utilize this capability to pass in data that will help them to reconcile reports between TouchNet and their end. This enhancement will allow clients to control what custom data(ancillary ID) they can send to TouchNet in order to reconcile their transaction reports.