The Transactions tab lets you view every transaction record in Salesforce. Chargent automatically creates a transaction record for each type of action that elicits a response from your gateway. This page will help you familiarize yourself with the Transactions tab, including related functionality, considerations, and best practices.
Transaction Types #
These responses are categorized using the Type field on the transaction record:
- Authorization – Authorizations are used to place a hold on an amount or check if a credit card is valid for future capture. They can be initiated using either Payment Request or Payment Console.
- Charge – A charge represents an immediate payment (once verified and settled). Unlike an authorization, a charge does not need to be manually captured.
- Refund – A refund represents a payment that was credited. A refund is only possible for a transaction that has been previously settled (typically between 1 and 120 days).
- Void – A void represents a payment canceled prior to settlement (most commonly a charge from the same day) or an authorization that has not yet expired.
Transaction Records #
Every time Chargent contacts your payment gateway to process a transaction, it creates a transaction record in Salesforce to store the gateway’s response. You can view all the transactions for a Chargent Order from the Transactions related list on the Chargent Order record. Use the Transaction record to troubleshoot transaction-related issues, refund/void a transaction, or capture an authorization.
At the top of each transaction record, Chargent displays summary information:
- Order
- Type
- Amount
- Gateway Date
- Response Status
See Chargent Transaction Fields for descriptions of these fields and others containing all the details stored in your transaction records.
Note: Generally, making changes to existing transaction records is not recommended. Chargent references existing transactions when running a recurring billing schedule, so be careful not to edit recurring transactions.
Creating and Updating Transactions #
When using Chargent, you don’t have to worry about creating transaction records. Chargent automatically creates a new transaction record for each payment-related attempt, including payments created using Chargent Anywhere, the Take Payment component in your community site, or manually via the Chargent order record.
For more details, see Creating And Updating Transactions.
Duplicate Transactions #
Each payment gateway handles duplicate transactions differently. Some gateways decline a second transaction if the billing information and amount match a previous transaction within a specific time period. Other gateways allow it but may flag it as a potential duplicate.
Understanding Authorizations #
A credit card authorization holds a portion of the available balance on a card for future payment without pulling the funds at the time of authorization. Run an authorization if you want to hold a portion of the available balance on a card to capture in the future without pulling the funds at the time of authorization.
See Understanding Authorizations for directions on running authorizations.
Response Status is Declined or Error #
Chargent creates a transaction record for all charges, even those that were declined or in error. Some reasons a transaction might be declined include the card being expired or inactive, exceeding its limit, the bank deeming the card compromised or stolen, or an AVS mismatch. An “Error ” response status can occur if billing information is missing or incorrect.
See Understanding Response Statuses for more information.
Gateway Response Codes #
xamine the response from the gateway and resolve any issues.
For more information, see Understanding Response Codes.
Refunding or Voiding Transactions #
Refunds and voids are both designed to reverse a transaction. Whether you process a refund or void depends on whether the transaction has already settled. A void is designed to cancel a charge or authorization before it has settled, whereas a refund is designed to apply a credit to a transaction that has already settled. You can also use the Void button to cancel a refund if it was accidentally processed and has not yet settled.
See Refunding and Voiding Transactions for more details.
Understanding Unresolved Transactions #
When Chargent cannot update or save a transaction, a record is displayed on the Unresolved Transactions tab. Unresolved transactions can occur for various reasons, such as conflicts related to validation rules, triggers, or other Salesforce configurations. Ultimately, they exist to help you investigate and fix any automation or customizations that caused them.
See Understanding Unresolved Transactions to learn more.
Sending Credits And Unlinked Refunds #
Some gateways allow you to send credits to a checking account when a transaction is not a refund of a previous payment. You can also send funds to a credit card or bank account that is not a refund for a previous charge, a type of transaction called unlinked refunds.
For more information, see Sending Credits and Sending Unlinked Refunds.
Transaction Sync #
Since ACH transactions take time to settle, Transaction Sync will keep your ACH transactions up to date in Salesforce via the Transaction Sync Batch. Chargent can sync your ACH transactions from when they are initiated until they are settled.
See Transaction Sync for more information.
See Also #
Chargent Transaction Fields
Understanding Payments
Chargent Orders Tab
