Skip to main content



Chargent Flow API is a payment processing solution that helps businesses accept and process payments online using Salesforce Flow Builder for workflow automation.


There are six primary objects involved in Chargent Flow API requests and responses.

           Object           Definition
Chargent OrderChargent Orders contain information related to the order such as billing information, total amount, due balance, and charge amount. They are central objects to payments lifecycle management.
Payment GatewayPayment Gateways track all the configuration settings that Chargent will use to proccess the payments and send requests to the gateway.
Payment MethodPayment Methods are items that may be used to make or take payment.
TokensTokens are the strings used to represent the payment instrument account details at the gateway or other payment service provider. Payment tokens replace sensitive payment account data with a different data called a “token”. These token strings cannot be decrypted.
Chargent TransactionTransactions record the results of the requests made to the payment gateway on the Chargent Order. Transactions are also used to make additional requests in the payments lifecycle.
LogThe Chargent Log object retains the history of actions taken in Chargent.

Payments Lifecycle

Businesses have many different needs for payment processing workflows. The general sequence of operations to create a successful payment sale operation includes the following five steps:

  1. Create Payment Gateway
  2. Create Payment Method
  3. Create Chargent Order
  4. Create Payment Authorization
  5. Create Payment Capture

Many varitions on this workflow exist, and this sequence may also be followed with additional operations, such as Void and Refund. Additionally, a Sale operation combines an Authorization and Capture into a single payment operation.

Headless Requests

When the headless=true Flow variable is sent as input to the Flow Action, Chargent will not store response data in Salesforce.


Chargent supports two methods for headless requests.

Payment Method TokenizationPayment Method Tokenization is the exchange of payment data for a token representation provided by the payment gateway for PCI Compliance. This is an initial step in the payments lifecycle.
Payment SalePayment Sale will perform both a Payment Authorization and a Payment Capture in a single payment operation request.

Learn More

Learn more about Headless Requests