Every gateway you set up is stored as a record in Salesforce with details in the following fields. You should have a gateway record for every gateway account you use to process payments, including test accounts. Depending on your page layout and field-level security settings, some of the fields below may not be visible or editable.
See Supported Gateways for more information about the gateways supported by Chargent. Additionally, check out our Gateway Setup Overview documentation to learn more about creating your gateway records.
Field Descriptions #
Accounting Seed Integration: A checkbox field that indicates whether or not the Accounting Seed integration with Chargent is active in your Salesforce org. See Accounting Seed Integration for more information.
Active: A checkbox that indicates if a gateway record is available for use. You can set up multiple gateways, including separate test and live gateway accounts, and deactivate the test account after you’ve completed your testing. Inactive gateways can be reactivated for troubleshooting at a later time.
Allow “No-Hit” Transactions: A checkbox field that’s available when you enable ACH Validation. A “No-Hit” ACH Validation Response is neither positive nor negative. This indicates that ACH validation cannot be completed since the account is not listed in the reference database. For more information, see ACH Validation.
Allow Unlinked Refund: A checkbox field that indicates whether or not you allow Chargent users to send money in the form of a credit to bank accounts and credit cards. See Sending Unlinked Refunds for more information.
Approve Soft Rejects: A checkbox field that indicates if you want to allow soft rejects (aka soft declines). Learn more about Soft Declines in Understanding Response Statuses.
Available Card Types: A multi-select picklist that indicates which types of payment cards you accept using the Payment Request and Payment Console. When a card type is not selected, users will receive an error. Please note that not all gateways accept all available card types. Please reach out to your gateway to determine what card types are supported. The available values are as follows:
- Visa
- Mastercard
- Discover
- American Express
- MC Eurocard
- UK Maestro
- JCB Card
- Diners Club
Available Currencies: A multi-select picklist indicating which currencies you accept. Chargent includes over 150 available currencies out-of-the-box, and additional currencies can be added. For more information, see Currency Fields by Object. A few of the available values are as follows:
- United States dollar
- Australian dollar
- Belgian franc
- Canadian dollar
- Swiss franc
- German mark
- Euro
- French franc
- Luxembourg franc
- New Zealand dollar
- Pound sterling
- Russian ruble
- Singapore dollar
- Thai baht
…plus 139 more!
Available Payment Methods: A multi-select picklist indicating which payment methods you accept for payment. See Payment Methods Supported for more information. The available values are as follows:
- Credit Card
- eCheck
- Bank Account
- Bank Transfer
- Cash Transfer
Available PR Transaction Types: A multi-select picklist with three options. Please note that if no options are chosen, the transaction type will default to Charge Full Amount. For more information about Transaction Types, see Understanding Payments. The available values are as follows:
- Charge Full Amount: will send the total value as an authorization and capture.
- Authorize Full Amount: will send the total value as an authorization only.
- Authorize Minimum Amount: will send a $0.00, $0.01, or $1, whichever is allowed by the card network/gateway
AVS Forced Failure: A multi-select picklist where you can select which AVS response code should automatically trigger a declined transaction, regardless of the gateway configuration. For more information, see Address Verification System (AVS). The available values are as follows:
- A
- B
- E
- G
- N
- P
- R
- S
- U
- W
- X
- Y
- Z
Bank Account Type: A picklist field indicating which direct debit network you use for your gateway. The available values are as follows:
- ACH – US
- EFT (ACSS) – Canada
- BECS – Australia
- SEPA – Europe
Charge Amount Behavior: A picklist field that controls how the Charge Amount field on the Chargent Order record is populated when using the Payment Console. The available values are as follows:
- Use Opportunity/Order/Case Charge Amount
- Use Gateway Charge Amount (Fixed): Sets the value of the charge amount to the numeric value populated in the Static Charge Amount field.
- Allow User to Edit in Console
Created By: Populated with a lookup to the user that created the gateway record.
Credit Card / Bank Account Data Handling: A picklist field that allows you to choose how or if credit card data is stored in Salesforce. To minimize the scope of your PCI compliance, we recommend using tokenization and selecting ‘Clear When Token Present’. For more information about tokens, see Understanding Tokenization. The available values are described in Understanding Data Handling Rules.
Currency (OLD – do not use): A picklist field that is deprecated and is no longer in use. Please avoid referring to this field, especially in any custom solutions or automation.
Debug: A checkbox field that allows you to capture the complete XML or HTTPS request that is being sent to the server and response strings in a popup window when you click the appropriate button on your screen (Charge, Authorize, etc.). Debug can be useful for troubleshooting and verifying the values being sent to the payment gateway but should only be enabled temporarily.
Note: This feature should only be used by System Administrators or privileged users, as the gateway response may contain decrypted payment data.
Default Payment Method for PC: A checklist field that determines the default payment method type used when processing payments via the Payment Console. Available values include:
- Credit Card
- eCheck
- Bank Account
Default Payment Method for PR: A checklist field that determines the default payment method type used when processing payments via Payment Request. Available values include:
- Credit Card
- eCheck
- Bank Account
Duplicate Transaction Window: A number field only applicable to the Authorize.net gateway integration. This field specifies the duplicate transaction validation time frame in seconds. For more information, see Duplicate Window Setting. Acceptable values include:
- Empty: If the field does not contain a value, it is not set. The parameter isn’t sent, and Authorize.net will use the default setting of 120 seconds.
- 0: A value of zero disables the duplicate check.
- 1 – 28800: The time frame in seconds. 28800 seconds (8 hours) is the maximum time frame value. If a greater value is set, Authorize.net will process as 28800.
Enable Refund: A checkbox field that enables or disables the ability to process refunds using the gateway record.
Endpoint Override: A text field that determines the URL that your transactions are sent to. In most cases, this field can be left blank, in which case Chargent will determine the correct endpoint to send your transactions to. The endpoint chosen will depend on whether or not the Test Endpoint field is checked. There are three use cases where this field must be populated:
- You are using Authorize.net emulation: Populate your gateway’s endpoint URL to send transactions to your gateway instead of Authorize.net.
- You need to send live transactions from a Salesforce sandbox (not recommended): Populate the field with your gateway’s live endpoint. For security purposes, Chargent sends all transactions to your gateway’s test endpoint in Salesforce sandboxes, regardless of whether “Test Endpoint” is checked or not.
- You are using the Paymentus gateway integration: Paymentus provides all customers with a unique endpoint. This endpoint must be added to this field in order to process payments.
For Endpoint Override to work, the domain must first be added under Salesforce’s Remote Site Settings.
Ezidebit Pass Fees to Payer: A checkbox field that allows you to pass the transaction fees on to the payer via Payment Request and Payment Console and display those fees to the payer, as required by Ezidebit. For more information, see the Ezidebit Gateway Guide.
Gateway Name: A text field that denotes the name of the gateway. We recommend appending your gateway’s name with “Live” or “Test” to identify your gateway’s purpose easily. For example, a test gateway using Authorize.net might be called “Authorize.net Test”.
If your gateway is built with specific criteria or limitations, we recommend including the criteria in the gateway’s name. For example, if your live Authorize.net gateway only accepts credit card payments, name it “Authorize.net Live – Credit Card Only”.
Gateway Version: A picklist field only applicable to the Vantiv (Worldpay) gateway integration. This field determines the version of Vantiv used when processing payments via Chargent. For more information, see Gateway Version Update. Available values include:
- Vantiv v8
- Vantiv v12
Ignore AVS Results: A checkbox field only applicable to the Cybersource gateway integration. When enabled, Cybersource will not decline transactions that failed Address Verification System (AVS) checks, allowing you to accept soft declines related to AVS from Cybersource. Proceed with caution when enabling this checkbox, as it allows you to store potentially bad payment data at the gateway.
Inherit Chargent Currency: A checkbox field that functions only when Multiple Currencies are enabled in your Salesforce org. When checked, the currency sent to your gateway can be chosen based on the options in the Available Currencies picklist on your gateway record. For more information, see Currency Fields by Object.
Last Modified By: Populated with a lookup to the user that last modified the gateway record.
Micro Deposits Disabled: A checkbox field that indicates that micro-deposits have been turned off in your merchant account. Micro-deposits are small transactions, typically less than $1.00. Some gateways allow you to disable the ability to process micro-deposits. Please contact your gateway provider to find out if you can disable micro-deposits.
Note: This field does not disable the feature in your merchant account but optimizes the Chargent code when it has already been turned off in the merchant account.
Omit CC expiry: A checkbox field that controls whether or not the credit card expiration date is sent to the gateway. If enabled, the expiration date will not be sent when it is not required and a token is present.
Open Payment Platform Test Mode: A picklist field that allows you to choose the test mode for the ModusLink, PlanetPayment, and VerifPay gateways. The values are as follows:
- External
- Internal
Orbital Platform: A picklist field only applicable to the Chase Paymentech (Orbital) gateway integration. This gateway integration is not currently supported.
Owner: Populated with a lookup to the user that owns the gateway record. This is typically the user that created the record via the Setup Wizard.
PayFlow Use Recurring Profiles: A checkbox field only applicable to the PayFlow Pro gateway integration. When checked, Chargent will create Recurring Profiles to be used in payment transactions. When unchecked, Chargent will use the PayFlow Reference Transaction features for tokenization.
Payment Method Association Allowed: A checkbox field that indicates whether or not a Chargent payment method record can be associated with a Chargent Order. This field is automatically set based on the values in Use Tokenization and Credit Card / Bank Account Data Handling. For more information, see Payment Methods Tokenization.
Payment Method Creation Allowed: A checkbox field that indicates whether or not a Chargent payment method record will be created when using this gateway. This field is automatically set based on the values in Use Tokenization and Credit Card / Bank Account Data Handling. For more information, see Payment Methods Tokenization.
Record Type: Populated with the record type associated with your gateway. Each gateway has its own record type and page layout so that gateway-specific fields are only present on their respective gateway’s page layout.
Require AVS: A checkbox field that prevents a transaction from being submitted to the gateway without billing address fields being populated. Generally, Address Verification System (AVS) settings are controlled through your payment gateway; however, this field will prevent Chargent from sending the transactions if the address data is not populated in Salesforce.
Require Card Security Code: A checkbox field that denotes whether or not the Card Security Code (CSC, CVV, or CVC) is required when processing a charge using the Charge button. A pop-up requesting a CVC code will appear when you charge a transaction. If the Require Card Security Code is checked, you must enter a CVC in the pop-up; otherwise, you will receive a message saying it’s required. This functionality does not affect recurring charges.
Require CVV in Payment Console: A checkbox field that controls whether or not the Card Security Code (CSC, CVV, or CVC) is required when taking payments using the Payment Console. When this field is checked, the CVC is required.
SCA enabled: A checkbox field that controls whether or not Strong Customer Authentication (SCA) is enabled for the gateway. For more information about SCA, see Strong Customer Authentication (SCA).
Show Authorize Button: A checkbox field that controls whether the Authorize button is visible to your users when using the Payment Console.
Show Charge Button: A checkbox field that controls whether the Charge button is visible to your users when using the Payment Console.
Show Create/Update Token Button: A checkbox field that controls whether the Create Token or Update Token buttons are visible to your users when using the Payment Console. The Update Token button appears when updating an existing recurring Chargent order record; otherwise, the Create Token button will appear.
Show Setup Recurring Button: A checkbox field that controls whether the Setup Recurring button is visible to your users when using the Payment Console. For more information, see Show Setup Recurring Button Checkbox on the Gateway Record.
Static Charge Amount: A number field that defines the charge amount when using the Payment Console. This amount is only sent when the Charge Amount Behavior field is set to ‘Use Chargent Gateway Amount (Fixed)’.
Test Endpoint: A checkbox field that determines whether or not transactions are processed by the gateway’s test endpoint, which cannot be used for live transactions. We recommend testing with this field checked using test credentials until you are ready to capture live transactions.
Note: If Chargent is installed in a Salesforce Sandbox, all transactions are sent to the test endpoint for security purposes, regardless of whether or not this field is checked. For more information about testing in your sandbox org, see Testing in Sandbox.
Use PF Pro Reference Trx (deprecated): This field is deprecated and is no longer in use.
Use Tokenization: A checkbox field that controls whether or not tokenization is enabled for your gateway. Please ensure that your gateway supports tokenization before enabling this feature. We always recommend enabling tokenization if supported by your gateway. For more information, see Understanding Tokenization.
Verification Forced Failures: A multi-select picklist field that forces a Response Status of ‘Declined’ based on a specific security code verification response, regardless of the gateway configuration. The security code verification values are as follows:
- M
- N
- P
- S
- U
