Custom parameters are supported for the following payment gateways when used in the Online Application:
Note: Custom Parameters only apply to Online Application payments.
If you are using Transact Payments (Cashnet) or OPC as your Payment Provider, you can configure Custom Parameters for your Payment Gateway. A custom field is created, either as a formula field or text field, to store the custom values in the following format:
param1=value1¶m2=value2¶m3=value3
Example:
If you were using a formula field and wished to send over the Deposit Amount and Percent Complete as custom parameters, your formula field would be written as follows:
'Amount=' +Text(TargetX_SRMb__Deposit_Amount__c) & '&PercentComplete=' +Text(TargetX_App__Percent_Complete__c)
The output on a record would display as follows:
If you are using Converge as your Payment Provider, you can configure Custom Parameters for your Payment Gateway. A custom field is created, either as a formula field or text field, to store the custom values in the following format:
PARAM_NAME1=VALUE1&PARAM_NAME2=VALUE2&PARAM3=VALUE3
Example:
If you were using a formula field and wished to send over the User ID and Full Name as custom parameters, your formula field would be written as follows:
"userId=" & TargetX_SRMb__Contact__c & "&" & "fullName=" & TargetX_SRMb__Contact__r.FirstName & " " & TargetX_SRMb__Contact__r.LastName & "&" & "orderType=enrollment_fee" & "&" & "retriesAllowed=0"
The output on a record would display as follows:
If using a Data Type of Formula (highly recommended)
If using a Data Type of Text
Save your changes. These parameters will now be sent to the Converge Payment Gateway.
As you create your Payment Custom Parameters formula field, there are specific characters that should NOT be included in your text output. These characters are limited to the ‘&’ and ‘=’ characters. While these characters are used as concatenate (&) and equals (=) in your formula syntax, they should not be used as return values in your formula. Below are a couple of examples of correct vs. incorrect syntax.
Note: There is a limit of 100 characters for Touchnet Ancillary data.
Custom response parameters can be mapped to fields on the Payment Detail record for Paypal, Transact Payments (Cashnet), Campus Solutions, Nelnet, and Converge. Administrators can configure additional information to be returned from these Payment Vendors, such as the credit card type. Custom fields are mapped to the Payment Detail record and, when a payment is executed, the parameter value is stored on the corresponding Payment Detail.
Administrators will need to configure permissions to the Site User profile(s) which use Payments.
Object: Payment Response Mapping |
||
---|---|---|
Fieldname |
Read |
Edit |
Parameter |
✓ |
|
Payment Connector |
✓ |
|
Payment Detail Field |
✓ |
|
Payment Response Mapping Name |
✓ |
|
A custom field will store the data returned from the Payment Vendor.
The Payment Response Mapping record maps the payment connector response parameters to the correct Payment Detail record fields.
Select a Payment Connector.
Note: You can NOT map to ‘reserved fields’ as they are already in use by TargetX. Reserved fields are:
Save.
Using WPM as your Payment Provider, you can configure Custom Parameters for your Payment Gateway.
Note: If you don't see a Custom Parameter section, contact your System Administrator.
Note: You can not use customfield1 or customfield2 as these are already used.
TargetX Logs will be created if the system can’t retrieve the custom parameter. Logs will display the data before submitting the payment. For example, the Confirmed checkbox gets updated only after a payment has been processed. So, the TX Log would indicate the value Confirmed = False upon creation.
Note: A limit of 105 characters can be passed to the payment gateway. If the value exceeds 105 characters, the payment page won't load.