Transaction Status Batch Chunk Size Limit: This would be for transactions that are pending on a gateway and could potentially settle differently than what was originally returned. For example, you may have an ACH eCheck that is initially approved but then later declined for insufficient funds. This batch would allow your Transaction record to sync with your Gateway and Processor to update the record if the settled response is different.
This feature is available for certain gateways although we’re trying to get most of them updated.
Automatically create the PR (Payment Request) Record: If you have automated emails that go out and you want to include a link to a Payment Request, checking this box will automatically create a Payment Request record every time a Chargent order is created, so your other customization can access the link to each record.
Accept eCheck: In the first certification I mentioned the setup of electronic check (ACH / Direct Debit) in the gateway setup. You still need to enable it here in the Chargent Settings in order for it to be visible on your Payment Request or Recurring Billing.
Payment Confirmation and Error Text: You can customize the text shown when processing a payment using the Payment Console or when sending a Payment Request. This is an internal message to your Salesforce user to either confirm the charge or alert that there is an error. For Payment Requests it alerts that the request was successfully sent.
Default Currency: There are several places in Chargent and Salesforce that determine which currency to use.
- Default for Salesforce (this defaults if nothing is indicated on either of the below items)
- Default set in the Chargent Settings (this defaults if not indicated on the Chargent Order)
- Default for the Gateway record
- Record Settings (specifically tells you what currency to use for that record)
The Troubleshooting Tools tab can be helpful in determining why a Transaction record isn’t being updated, saved, or created. If you have customizations like Workflow Rules, or a processes in Process Builder, sometimes they can prevent records from being saved. The Troubleshooting Tools provides two buttons. One that allows you to test the insertion of a Transaction record and another to test the insertion of a Master record into Salesforce (typically a Chargent Order record). This can often tell you why the transaction record can’t be created and exactly what Workflow Rule or process is actually causing the problem.
I’m going to run through the customizations of the gateway, what you can enable, and what you can disable. If you went through the setup, and now you want to make changes to it you can follow the following steps to make changes.
Some possible reasons why you may want to make changes:
- You want to show that Authorize button, and you didn’t click it when you were going through the setup
- You want to enable other buttons on your Payment Request and Payment Console
- You’ve changed the types of currency, or you want to add currencies.
- You want to take away the option to allow for electronic check.
If you click on the App Launcher on the top left, and we do a search for Gateways, you can click on “Gateway” object.Click on the Authorize.net gateway which we added from the first session. If you click Edit, it will take you to a page that looks similar to the one you set to begin with. The difference is, on the very bottom, there is an option for Advanced Settings. In order to edit that gateway, we click on Advanced Settings. You will now be able to update the gateway record.
Some of the things you can see here
- Active means that the gateway is active. If you switch gateways and you want to deactivate it, you would just come here and uncheck it.
- Test Endpoint, In Sandbox, it automatically defaults to a test URL endpoint for testing however in Production or your Dev org you will need to check this box if you want to process test transactions.
- Use Tokenization is always recommended. Tokenization is a random string of characters returned by the Gateway which can be used for this customer solely, by only you, and only this gateway. With tokenization, you can greatly reduce your PCI compliance scope by not storing credit card numbers in Salesforce.
- Credit Card and Bank Account Data Handling you can set what happens when a transaction is sent, and how the sensitive credit card or check information is handled. Do you want it to only clear it when there’s a successful charge? Do you want to clear it after all transactions?We always recommend clearing it when a token is present. The token comes back, and it clears out or does not save the credit card details, so you’re not storing it in Salesforce.
- Available Payment Requests types If you send a Payment Request, the customer will get the link to either Charge or Authorize payment. Those options are:
- Charge the Full Amount.
- Authorize the Full Amount: When they fill in the Payment Request, it authorizes their credit card and makes sure it’s valid and the funds are available. It will hold the funds until the authorization falls. It doesn’t actually take the money from their credit card unless you Charge the Authorization.
- Authorize just the Minimum Amount that your gateway allows. Most of the time, it’s about $1.00. So, what it does is, it sends it to the gateway saying, “Just making sure that this is an active credit card, and we’re going to authorize this for $1.00.”
Other items you can update in the Gateway settings
- Add or remove the option for eCheck, ACH
- Check the “Show Authorize Button,”
- Add or remove the different buttons that are on the Payment Console/Payment Request
Be sure to click the save button to ensure your updates.
Customizing Chargent Anywhere
In order to customize the default settings for Chargent Anywhere, we need to create 4 custom fields. These fields are added to the same object where you will be adding Chargent Anywhere. You will need to copy the Field Name to use as the defaults.
- Account (if you don’t already have an Account Lookup on the object)
- Initial Charge Amount
- Recurring Charge Amount
The following items can be customized using Chargent Anywhere:
- Default Gateway
- Show Add Cash / Add Check button
- Change the Name of the Charge button
- Default Account Contact
- Default Initial and Recurring Charge Amounts
For Opportunities, we already have the lookup to the Account (AccountId), so we don’t have to create that. If you want to populate a specific contact from there, you can do that as well by creating that lookup field for the Contact. You can also set the default gateway if you use multiple gateways for different Salesforce users.
From the main page, click the gear icon and choose Setup. Navigate to Objects and Fields and select Object Manager. Select the object you want to add Chargent Anywhere to, and go to Fields Relationships. What we’re going to do here is create the other 3 custom fields.
Lets create a lookup field to the Contact first.
- Click “New
- Select Lookup Relationship and click Next
- Choose Contact from the dropdown and click “Next.”
It’s going to ask us which profile you want to assign that to. Go ahead and click “Next” as well as which Page Layout do you want to assign it to.
After you create the Contact, you want to create a custom currency field for the Initial Amount and another for Recurring Amounts, or reference existing fields you have on the object. When you are done creating all custom fields you want to copy the Field Name for use in customizing Chargent Anywhere.
The next thing we want to do is copy the Gateway Record ID. To get this, you can navigate to the Gateway record and copy the record ID from the URL. Once you’ve copied the Gateway ID we are ready to customize.
Navigate to any record that has Chargent Anywhere installed. For our demonstration we have it on the Opportunity Record. From the gear icon click Edit Page.
We’re going to go ahead and tap on the Chargent Anywhere component. Here we can copy in all the fields we added along with the Gateway Record ID. We can add the Field Name for Account, Contact, Initial Charge, and Recurring Amount.
You can also show the Add Cash or Add Check button. Finally, we have the ability to change the name of the Charge button as. If you don’t want it to say “Charge,” but instead want it to say Press Me, or Give Me the Money you could do that. Be sure to click Save and return to the Opportunity record.
Before we click on the Payment Console we want to make sure the Initial Amount and Recurring Amounts are populated. Go ahead and update the record with any amount and click Save.
Now, when we click on the Payment Console, you’re going to notice that the amount is now being populated from the record. If you go under Recurring, it’s also going to have the populated amount as well. You can select the contact record from the drop down if it’s not already populated on the Opportunity. The Payment Console will automatically pull in the mailing address from the Contact record.
Automated Collections is coming out soon in version 6.0. We’ve had several customers who have created their own versions of this. What this is going to do is help you collect money from failed transactions by retrying and sending automated emails based on a schedule you set.
As you know, sometimes the Recurring Billing can fail. One of those transactions may be declined for insufficient funds or various other reasons. You probably spend a lot of time trying to collect that money.
With the Automated Collections, you can schedule automated emails to be sent on a frequency based on the Automated Collections setup. We are going to go through how to enable it, and how to set it up. If you want a more in-depth check out our video presented by our Product Manager Don Snider.