Term | Description |
---|---|
Account Updater | A Chargent feature that automatically notifies your customers of upcoming credit card expirations. You can set up Account Updater in 3 steps to save your company time, effort, and money. |
Automated Clearing House (ACH) | A direct debit network for processing bank account transactions in the United States. Supported by many gateways using Chargent. |
Acquiring Bank | The financial institution that processes credit card or debit card payments on behalf of a merchant. |
Authorizations | A type of transaction you can run in Chargent that verifies if the credit or debit card is valid before charging an amount. See Understanding Authorizations for more details on using authorizations. |
Automated Clearing Settlement System (ACSS) | A direct debit network for processing bank account transactions in Canada. Supported by many gateways using Chargent. |
Automated Collections | A feature that automatically retries payment collection on missed and late payments. You can enable Automated Collections after installing Chargent. |
Address Verification System (AVS) | Address Verification System is used to prevent fraud and validate the ownership of a credit card by checking the billing address of a credit card with the data on file at the credit card issuing company. |
Bank Account Number (BAN) | Used in bank account transactions alongside the bank’s routing number to make a payment. |
Bank Account Transaction | Commonly referred to as an e-check or direct debit transaction, a bank account transaction is the transfer of funds using a bank account number and routing number. See Understanding Bank Account Payments. |
Billing Address | The address portion of the billing information that is often required to make a payment. See Billing Address Fields for more information. |
Billing Information | Typically refers to the credit card or bank account number, billing address, and any other information required to process a payment. |
Bank Identification Number (BIN) | Refers to the first six numbers that appear on a credit card. |
Bulk Electronic Clearing System (BECS) | A direct debit network for processing bank account transactions in Australia. Supported by many gateways using Chargent. |
Cash | Physical notes and coins used to make payments. Chargent allows you to track cash transactions without connecting to your gateway. See Entering Cash And Paper Checks. |
Chargent Custom Checkout (CCC) | Chargent Custom Checkout is the pro-code alternative to the Take Payment Component, allowing you to customize the look and feel of payment forms on your Experience Cloud site. |
Charge Amount | The amount populated on a Chargent order record to be charged or authorized. See Chargent Order Fields for a more detailed description. |
Chargent Anywhere | A lightning web component that allows you to process payments from any Salesforce tab. Configure Chargent Anywhere on any Salesforce object. |
Chargent Payment Console | Part of the Chargent Anywhere component. Allows you to set up single and recurring payments from any object. Set up the Chargent Payment Console to process payments securely without storing sensitive payment details. |
Context-Sensitive Help | Help links integrated into custom object tabs that display related content. Read more information about Context-Sensitive Help and how it is integrated in Chargent. |
Credits | An alternative to unlinked refunds are credits, allowing you to send funds to a checking account without being tied to a previous transaction. See Sending Credits for more information. Also known as Unreferenced Credits. |
Credit Card Transaction | A cashless payment made using a credit card. See Understanding Credit Card Payments. |
Card Verification Code (CVC) | The CVC, also known as CVN (Card Verification Number), CVV2 (Card Verification Value 2), CVC2 (Card Validation Code 2), or CID (Card Identification Number), is a code that appears on credit cards and is sometimes required for payment. For more information, see Card Verification Number (Security Code). |
Decline | Charges that did not process completely. See Understanding Response Statuses for more information. |
Direct Debit | Commonly used to refer to online Bank Account payments. See Understanding Bank Account Payments for more information. |
Direct Debit Network | The localized network in which bank account transactions are processed. Chargent supports the following Direct Debit Networks: ACH – US (aka echeck or electronic check) EFT (ACSS) – Canada (aka Electronic Funds Transfer) BECS – Australia SEPA – Europe |
E-Check | Short for Electronic Check. Commonly used to refer to online Bank Account payments. See Understanding Bank Account Payments for more information. |
Electronic Funds Transfer (EFT) | A direct debit term used for processing bank account transactions in Canada. Supported by many gateways using Chargent. |
Gateway | A payment gateway is like a virtual PoS terminal tasked with authenticating a digital payment request by the customer. Chargent supports over 30 gateways. |
Gateway Response | Transaction information returned from your gateway. This can be useful when determining why a transaction was declined or experienced an error. Responses can be different for each gateway. See Understanding Response Codes. |
Hard Decline | Hard declines refer to declines where the issuing bank could not authorize the payment, such as a card reported as stolen. See Understanding Response Statuses for more information. |
Issuing Bank | The financial organization that provided the customer’s payment method. |
Merchant Identifier (MID) | Assigned to a merchant account by a payment processor or gateway. Often used to authenticate your gateway in Salesforce. |
Omnichannel | A cross-channel business model designed to optimize the customer experience across every touchpoint. |
Org | An abbreviation for a Salesforce instance (organization). |
Primary Account Number (PAN) | A unique 12-19 digit credit card, debit, or prepaid card number. |
Paper Check | A paper check is a written, dated, and signed document that instructs a bank to transfer money from the payer’s account to the payee. Chargent allows you to track these payments without connecting to your gateway. See Entering Cash And Paper Checks. |
Payform | Allows users to access and pay their Payment Request. The payform is hosted on a Salesforce Site and is accessed via the Pay Link. |
Pay Link | This link will take you to the payment page for a Payment Request. Users may send this link directly to a payer. |
Payment Method | In general, a payment method is the means you offer to compensate for products or services such as credit card, bank account and routing number, PayPal, Venmo, or Apple Pay. In Chargent, Payment Methods is a feature that allows your customers to safely and conveniently save, select, and remove payment methods for current and future payments. Review more information about Payment Methods and begin using this vital feature. |
Payment Method Type | The various ways a customer can make a payment. Chargent supports many payment method types. See Supported Payment Method Types. |
Payment Processor | The organization that manages payment transactions between the bank and the merchant. In online transactions, the payment processor communicates with your payment gateway. |
Payment Source | A Chargent custom object and tab that’s replaced by the Payment Method custom object and tab. Click here for more information on Payment Methods. |
Payment Card Industry (PCI) Compliance | PCI compliance refers to the technical and operational standards that businesses follow to secure and protect credit card data provided by cardholders and transmitted through card processing transactions. PCI standards for compliance are developed and managed by the PCI Security Standards Council. |
Package Installation Manager (PIM) | The Package Installation Manager allows you to securely login (using Salesforce Identity Oauth), to the Salesforce instance where you want Chargent installed or upgraded. First, the PIM analyzes which, if any Chargent packages are installed, then guides you through installing the correct packages. It also ensures that the target Salesforce instance is aligned with some of the latest compliance features we have implemented, and ensures you get access to the best of Chargent. |
Recurring Billing | The Chargent feature for setting up a sequence of payments on a repeating frequency that you choose. Review more information about Recurring Billing and configure it for your business processes. |
Refund | The reimbursement of money for goods or services. A refund is processed after a payment has been settled. See Refunding and Voiding Transactions. |
Response Code | Your gateway sends information about transactions when they are completed. See Understanding Response Codes for more information. |
Settlement | Describes when funds are transferred from the cardholder’s account to the merchant’s. See Understanding Transaction Settlement for more information. |
Single Euro Payments Area (SEPA) | A direct debit network for processing bank account transactions in Europe. Supported by many gateways using Chargent. |
Soft Decline | Soft declines are rejections related to temporary issues, such as a temporary hold on an account. See Understanding Response Statuses for more information. |
Surcharging | A surcharge is any additional fee added to the cost of goods or services beyond the price originally quoted. Credit card processing fees are surcharges that businesses may pass on to their customers to offset the added cost. |
Take Payment | A component that enables Community Users to make payments in an Experience Cloud site. Sometimes referred to as the Take Payment component. |
Tokenization | Industry standard to ensure card holder data is kept secure by encrypting the data in a manner that cannot be decrypted. Chargent uses tokens so cardholder data is never stored in Salesforce and the token is only available to the payment gateway for a merchant. Read and watch more information on tokenization. |
Transaction Type | Chargent processes many kinds of transactions, including authorizations, charges, refunds, and voids. See Understanding Chargent Transactions for more details. |
Unlinked Refunds | Unlinked refunds are funds sent without a Chargent transaction for a previous charge. See Unlinked Refunds for more details on this type of transaction. |
Unresolved Transactions | An unresolved transaction is a transaction record that can’t be created or saved due to some Salesforce configuration. See Understanding Unresolved Transactions for information on handling them. |
UUID | Universally Unique Identifier. A 128-bit value used to identify an object or entity uniquely. |
Void | A payment that is canceled before settlement. Voiding a payment in Chargent prevents it from being processed. See Refunding and Voiding Transactions. |
See Also
Chargent Quick Start Guide
Understanding Chargent Architecture
Understanding Payments