Making Payments Work. Together!

Chargent relies on its partners for implementations, professional services, financial and ERP system integrations, and payment processing.

Implementation Partners

Our implementation partners have valuable experience working with Chargent, developing custom solutions, and ensuring that Chargent helps you achieve your business goals.

Contact us if you’d like help determining the best implementation partner for your needs.

Pyropetech LLC
SaltClick
EideBailly
redpath
KeyNode Solutions
Touchpoint Solutions
Veltig
Yurgosky
Cloud on Tap
Attain Partners
Cirrus Solutions
CommerceCX
Redpoint Solutions
Integrate2Cloud
The Fury Group
VantagePoint Consulting
InterPayments
Five9
Lyons
Vonage

Technology Partners

We’ve partnered with some of the best technology experts in the industry to create a seamless and secure experience when taking payments in Salesforce.

InterPayments
Five9
Lyons
Vonage

Gateway Integration
Partners

Chargent Payments for Salesforce includes pre-built integrations with 30+ payment gateways. To learn more about our Payment Gateway integrations, visit our Salesforce Payment Gateways page.

Adyen
AstroPay
Authorize.net
Barclaycard ePDQ
BluePay / Clover
BlueSnap
Braintree
Forte
Cybersource
eProcessing Network
eWAY
Ezidebit
Deluxe / iATS
Fat Zebra
Linked2Pay
Merchant e-Solutions
Merchant Warrior
ModusLink
Moneris Canada
NMI
Paya
Paymentus
PayPal Complete Payments PPCP
Payflow Pro
Paysafe
PayTrace
PayU
Realex
Rectangle Health
SecureCo
Stripe
TransactPro
USAePay
VeriPay
Worldpay / Vantiv

Government Reseller

Contact our government reseller, Carahsoft, if you need help getting up and running with Chargent in the public sector.

Partner With Chargent

At Chargent, we rely on our partners for implementations and professional services, integrations with financial and ERP systems, and to process payments. Chargent partners who refer a minimum of 1 new Chargent customer per year will receive the following benefits:

Technical / Product

  • 2 Free Platform Edition licenses to Chargent (for internal use or demo)
  • Priority Technical Support (phone / email)
  • Access to Chargent product team

Marketing / Sales

  • Logo and Listing Page on this site
  • Referral of Prospects from Chargent
  • Assistance in sales demo prep / joint demos
  • Co-Marketing Opportunities (Press Releases, Events, Advertising)
  • Ability to present at / sponsor the annual Chargent Payments Summit at Dreamforce

WORK TOGETHER

Become a
Chargent Partner.

Let’s talk about how we can work together help our customers take payments in Salesforce.


Salesforce Partner
Since 2008

We have been working with Salesforce to help customers make payments since 2008. Our partnership with Salesforce has helped us generate solutions for Sales Cloud, Service Cloud, Commerce Cloud, Salesforce Billing, and more. For more information, visit our AppExchange listings.

COMMON QUESTIONS OUR PARTNERS ASK

Questions?
We’ve got you.

We’ve compiled some of our partners’ most common questions below. If you don’t find your answers here, don’t worry! Our Knowledge Base has you covered. If you have any additional questions, feel free to contact us. We’re always happy to help.

No. Chargent is a Salesforce-native payments app. It connects Salesforce directly to the customer’s own payment gateway (for example, Cybersource), and the gateway connects to the processor and acquiring bank. Chargent handles the payment experience and records inside Salesforce. The gateway carries the transaction, and the processor moves the money. Payment data goes straight from Salesforce to the gateway with no third-party middleman.

Yes. The customer licenses Chargent and holds its own gateway and merchant account, which are separate agreements. An existing processor relationship doesn’t always include a gateway account. Gateway and processor underwriting can take a while for enterprise customers, so start those contracts early and track them as a timeline risk. You don’t need production credentials to begin; most projects build and test in a sandbox first.

Chargent connects to more than 30 payment gateways, including Adyen, Authorize.net, Braintree, Cybersource, Moneris, NMI, PayPal, Stripe, and Worldpay. For B2B Commerce checkouts, Chargent for Commerce Cloud currently supports Adyen, Braintree, Cybersource, Stripe, and PayTrace. Feature support (card, bank account, regions) varies by gateway. See the supported gateway list and the Gateway-Specific Guides.

Install the Chargent managed package in the Salesforce sandbox and connect it to a sandbox (test) account from the customer’s gateway. That account returns test approvals and declines. Each gateway has its own test credentials and test card or bank numbers; the setup guide for each gateway lists them. In a Salesforce sandbox, Chargent automatically routes transactions to the gateway’s test endpoint. If an ERP or other outside system will capture payments, have that team set up sandbox access too. See Testing in Sandbox.

Build on Chargent’s objects alongside standard Salesforce tools. The Chargent Order is the central record for a payment: it holds the amount and the stored payment method, it drives scheduled and recurring billing, and every gateway result is written to it as a transaction record. A Chargent Order can link to an account, a contact, or any other record you take payment against, including standard or custom invoice objects. Automate with Flow and triggers where you can. Use the Chargent API only when a system outside Salesforce has to start the payment.

Yes. At checkout, Chargent gets an authorization from the gateway and records it on the order in Salesforce. You can capture later from Salesforce, including capturing less than the authorized amount.

If the ERP captures on delivery instead, export the order with its authorization code and payment token, and have the ERP call the same gateway to capture. Confirm early which ERP fields will hold the authorization and token. Gateway tokens only work within the same gateway account, so if the ERP uses a different gateway, plan for development work on the ERP side.

Most card authorizations expire after about seven days; the exact window depends on the gateway and card network. For long fulfillment cycles or split shipments, plan to reauthorize rather than reuse the original authorization.

Build a callback from the ERP to Salesforce that records each capture as its own Chargent transaction. An order shipped in several pieces then shows every capture separately. Many projects launch authorization first and add this callback in a later phase. Refunds, voids and partial refunds can still run from Salesforce, where Chargent calls the gateway for you.

  • Take Payment is a prebuilt Lightning Web Component that’s ready in minutes. You can adjust its colors and text, and it runs on both Aura and LWR sites (LWR support was added in Chargent 8.15). For guest checkout, place Take Payment inside a Screen Flow and follow the guest user setup.
  • Chargent Custom Checkout is a pro-code option for developers who need full control of the payment UI to match brand guidelines.

Whichever you use, create the Chargent Order before you collect card details. Payment results can only be written back to an order record that already exists.

Yes, for signed-in users. Chargent stores reusable payment methods (cards and bank accounts) as gateway tokens; the card data itself is never stored in Salesforce. Buyers can choose a saved method or add a new one. Guest users can’t access saved payment methods and enter their details for each purchase.

  • Cards: supported on every Chargent gateway.
  • Bank Account Payments: ACH (US), EFT/ACSS (Canada), BECS (Australia), and SEPA (Europe) are supported on gateways that offer them. Cybersource, for example, supports US ACH. Check the Gateway-Specific Guides for the gateway in scope.
  • Checks and Cash: recorded against a payment in Salesforce from the Chargent Payment Console. They aren’t processed through the gateway.
  • Currencies: Chargent supports more than 150 currencies and works with Salesforce multi-currency. Which currencies and countries you can use depends on the gateway and merchant account, so confirm them for each project.