Take the payment where the invoice lives.Card and ACH, inside Salesforce.
Kugamon takes card and ACH payments inside Salesforce through Stripe, Authorize.Net, PayPal and eWay — ACH processed, not just recorded — with a payment terminal on orders and invoices, saved payment methods, applied payments and recurring charges.
Every record is a native Salesforce record.
Kugamon stores quotes, orders, invoices, payments, subscriptions and assets as native objects in your org, on the standard Product and Price Book. Your reports, your permissions, your Agentforce agents see them like any other Salesforce data.
Kugamon processes payments inside Salesforce. A Payment is a Salesforce record related to the Order or Invoice it pays, created by a Lightning terminal a rep uses on the record or by the customer on an online page, and settled through Stripe, Authorize.Net, PayPal or eWay. Card and ACH are both processed through the gateway; wires and checks are recorded against the invoice. Nothing about the money lives in a second system.
The practical consequence is that collections is reporting. Balance Due is a field on the Invoice. The account balance is a roll-up. A declined card is a Payment record with a status and the processor's message, the moment the processor answers. A past-due invoice has a number in its Age field. Every one of those is something a list view, a report or a Flow can see, and none of them require a sync from a billing platform.
Where the money comes in
From an Order once it is Approved or Released, and from an Invoice while it is Unsent or Sent. Internally, a rep opens the terminal on the record, charges a card or ACH, or records a wire or check. Externally, the customer opens the emailed Online Order or Online Invoice link and pays there. Either way the Payment lands on the same record with the same statuses, and a completed payment is applied to the Order or Invoice at once.
ACH and the fee question
Kugamon processes ACH through Authorize.Net (eCheck) and Stripe (ACH Direct Debit), which matters for B2B invoices because the fee structure is different. The gateways set the fees, not Kugamon, but at both the ACH fee is capped per transaction where the card fee is a percentage of the amount — so the larger the invoice, the larger the saving. Check Stripe's pricing page and Authorize.Net's pricing page for the current numbers before you decide.
Recurring charges versus recurring invoices
These are two different things and both exist. A recurring invoice schedule creates the invoices for a term — monthly, quarterly, yearly and so on — and the customer pays each one. A Recurring Charge is an automated payment subscription at the processor that charges the stored card on a schedule, independent of the invoices. If your customers pay each invoice, you need only the first; a Recurring Charge is for the case where the card should simply be charged. Because it is independent of one-time payments, Kugamon recommends canceling and re-creating it if a customer pays part of the balance another way.
What stays an admin's job
Processor connections and payment settings live in Kugamon Settings. The Site guest user permission set is a one-time assignment. Receipts and payment PDFs use Salesforce email templates. Dunning sequences and credit holds are Flows on the Payment and Invoice fields. Payment method storage is enabled by Kugamon Support on request. Payments are included in Quote to Cash and Subscription Billing.
What it does, in the order your reps use it.
Four gateways, one Payment record
- Native processor connections for Stripe, Authorize.Net, PayPal and eWay, configured in Kugamon Settings; run one processor or several, and the terminal skips the processor choice when there is only one
- Every transaction — card, ACH, wallet, manual — is a Salesforce Payment record with the processor, transaction ID, fee, net amount, card type and last four digits
- Apple Pay, Amazon Pay and Cash App are enabled from inside your Stripe account and show up on the Stripe-hosted online payment page
ACH processed, not just recorded
- Bank debits run through the gateway — Authorize.Net eCheck and Stripe ACH Direct Debit — the same way a card does, and the Payment record carries the processor's status
- Wires and checks are recorded as manual payments against the Order or Invoice, with the check number on the record
- Gateway fees are set by the gateway, not by Kugamon; ACH pricing at both gateways is capped per transaction while card pricing is not, so the saving grows with invoice size — read each gateway's pricing page before choosing
A terminal on the Order, the Invoice and the customer's screen
- Lightning payment terminal on Orders and Invoices: Charge for a card or ACH, Record Payment for a manual one, with the billing contact's details pre-filled
- Customers pay without a Salesforce login: the Online Order page with Accept & Pay, and the Online Invoice link, served through a Salesforce Site guest user
- Payments are accepted on Approved or Released Orders and on Unsent or Sent Invoices; Draft and Cancelled records cannot take money
Saved payment methods and recurring charges
- Store a payment method per contact — card, PayPal recurring or a native processor subscription — with one marked as default; storage is off by default and enabled by Kugamon Support
- A Recurring Charge, started from an Approved or Released Order, schedules an automated charge against the billing contact's card on any start day, at a daily, weekly, monthly or yearly frequency, for a set number of occurrences
- Recurring Charge records show the next payment date and carry Cancel, Suspend, Update and Bill-outstanding-amount controls that talk to the processor
Applied payments, refunds, voids and status you can report on
- One payment applied across many invoices; Applied Payment and Balance Due on each Invoice, and the balance rolled up to the Account
- Refund from the Payment record with an amount and a reason; Void an authorized or completed processor payment; Reverse a manual one; Refresh Payment re-reads the processor when you need certainty
- Statuses set by the processor's response — In Process, Scheduled/Pending, Authorized, Completed, Declined/Error/Expired, Voided, Reversed — with the processor's message in the memo, so a report or a Flow can act on a decline the moment it lands
We're not the only option, and we don't pretend to be.
Neutral, source-cited comparisons on architecture, cost and time to value — with each competitor's genuine strengths conceded.
Guides, docs and walkthroughs.
Which payment gateway is best for subscription billing in Salesforce?
Read →What is involuntary churn?
Read →Kugamon pricing
Read →Process a Card Payment via Payment Terminal
Watch on YouTube →Create Payment from an Order (Internal User) / Integrate Stripe with Salesforce
Watch on YouTube →Create Manual Payment from an Invoice — Checks, Wires & ACH
Watch on YouTube →Stripe, Authorize.Net, PayPal and eWay, through native processor connections set up in Kugamon Settings. An org can run one processor or several; when there is only one, the terminal skips the processor choice. Wallets such as Apple Pay, Amazon Pay and Cash App are enabled inside your Stripe account.
Processed. Bank debits run through Authorize.Net eCheck and Stripe ACH Direct Debit, and the Payment record carries the processor's status the same way a card payment does. Wires and checks, which no gateway handles, are recorded as manual payments against the Order or Invoice.
The Payment record stores the card type and the last four digits, along with the processor's transaction ID. Saving a payment method for reuse is a separate feature that is off by default and enabled by Kugamon Support; the stored payment method is what the Recurring Charge and the terminal use for later charges.
Yes. The Online Order page — with the acceptance button set to Accept & Pay — and the Online Invoice link are served through a Salesforce Site guest user, so the customer opens the emailed link, reviews the record and pays by card or ACH. The Site Guest User permission set has to be assigned for these pages to work.
Yes, with a Recurring Charge created from an Approved or Released Order. It schedules an automated recurring payment through the configured processor on a chosen start day, at a daily, weekly, monthly or yearly frequency, for a set number of occurrences, and its record shows the next payment date with Cancel, Suspend, Update and Bill-outstanding controls.
Payments are part of the Billing component, so they are included in Quote to Cash ($95 per user per month) and Subscription Billing ($125). The CPQ and Subscription Management editions cover quotes, orders and — for the latter — subscriptions and renewals; CPQ-only implementations have the shipment and invoice functions switched off.
What Salesforce admins say on AppExchange
Quoted verbatim from the Kugamon listing on AppExchange. Reviewer names and dates as published there. Read all 134, including the critical ones →
★★★★★A new bar for RevOps
“As someone who has set up Salesforce CPQ before, I found Kugamon to be much more straightforward and easier to use. It took us just a few weeks to get going, rather than the few months or even years required by other systems.”
★★★★★Easy to understand, easy to implement
“This SFDC-native platform is lightweight but powerful, bringing the entire sales process onto one pane of glass. No more disconnected Opportunities and Quotes/Orders, no more fractured approval processes, just more control over everything. Implementation is a breeze.”
★★★★★Clear & Intuitive
“The Kugamon team is incredibly responsive and handle support questions very quickly. It’s clear they genuinely value customer feedback and are always innovating.”
Configure, price, quote, sign, bill, collect, and renew.
All natively in Salesforce. Deploys in weeks, not months, usually without a systems integrator.