Chargent Support Center

As of 12/11/2019 Chargent is retiring Desk and moving to a new ticketing system for support. Please click the Open A Ticket link below to create a new case or search our knowledge base below.

Transactions aren't saved to Salesforce but show up in the Gateway

This is generally caused by Salesforce being unable to save a Transaction record.
Transactions are a child object to the Chargent Order in Salesforce. The user running the transaction needs the ability to edit and save the record in order to record a Transaction on it.
If this is happening in your Salesforce org:
  1. Error logs would be going to the Chargent Admin Email Address configured in the Chargent Settings tab. You can also setup your profile to receive notifications for Apex Errors
  2. Error logs are saved in the Chargent Email Notification custom object.
  3. There are troubleshooting tools in the Chargent Settings tab you can use to simulate attempting to save a Transaction record.
  4. For those on Chargent v5.30 or newer you will see the Unresolved Transaction object under your tabs.  This will show you all Unresolved Transaction's and the reason for the error.

Things to check in your configuration:
  • Required fields that do not have the required value
  • Validation Rules that are being triggered
    Note: One way to check this is to click edit and then save
  • Triggers whose order of operations could be interfering
  • Process builder errors that could cause failures to update the record
  • Setup > Apex Jobs to see if there are any errors
  • Some other issue that prevents saving a record (it is locked for editing by another user, etc.)
In general we recommend limiting any validations or requirements on the records where you are running financial transactions. In addition, process builder and triggers need to be extensively tested prior to deployment, since they can interfere with transactions being saved successfully.

Related Articles

Contact Support
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
Invalid characters found