Collect where the invoice lives.Card and ACH through the gateway. Wire and check recorded against the same record.

Lead-to-Cash in Kugamon takes the payment on the same record that carries the invoice. A terminal on the Order and the Invoice, an online checkout on the customer's link, saved payment methods and recurring charges all run through Stripe, Authorize.Net, PayPal or eWay, and every result — completed, declined, refunded, voided — is a Payment record in Salesforce with the balance updated the moment it lands.

What happens at each step

The payment terminal

Payments are taken against Approved or Released Orders and Unsent or Sent Invoices, from the Account, the Order, the Invoice or the Payments tab. The Lightning terminal fills the billing contact from the Contact record, charges the card or bank account through the configured processor, and writes the Payment. Manual payments — wire, check, anything that arrives outside the gateway — are recorded on the same terminal with a check number if there is one, and apply to the balance the same way. Payment PDFs and receipt emails go out from the record.

The customer's side is the Online Order or Online Invoice link. It needs no Salesforce login; the Site Guest User permission set enables it. The admin chooses whether the Order's button reads Accept or Accept & Pay, and can add a checkout to the Invoice PDF as well, so a customer can pay from the document itself.

Gateways: Stripe, Authorize.Net, PayPal and eWay

Processor connections are configured in Kugamon Settings, and if the org uses one processor the terminal skips the selection step. Cards run through any of the four. ACH and bank debit are processed, not merely recorded, through Authorize.Net eCheck and Stripe ACH Direct Debit — which matters for B2B because ACH fees at both gateways are a capped percentage where card fees are not, so the saving grows with invoice size. Apple Pay, Amazon Pay and Cash App are enabled from the Stripe dashboard for orgs on Stripe.

Every gateway callout goes from your org to the processor and back, with the result stored on the Payment; no Kugamon-hosted service sits in between, and Kugamon has no access to your data. The security page covers the controls, and the payment gateways article walks through choosing one.

Payment profiles, recurring charges and applied payments

Payment Methods store a card, a PayPal recurring profile or a native subscription with the processor, with a default per account; storage is off by default and turned on by Kugamon Support. Recurring Charges schedule an automated recurring payment against the Order's billing contact from an Approved or Released Order — starting on a chosen day, on any frequency from daily to yearly, for a set number of occurrences — with master controls to cancel, suspend, update or bill an outstanding amount. Kugamon recommends creating them from the Recurring Charge button on the Order; the New button on the tab is for migrating subscriptions created elsewhere.

Applied Payments handle the other direction: one payment across many invoices. A customer who pays a lump sum has it applied to the open invoices, each invoice's Applied Payment Amount and Balance Due are updated, and the account balance rolls up from there.

Receivables you can report on

Because the Invoice and the Payment are Salesforce objects, receivables are a report, not an export. Age shows days past due, Balance Due shows what is open, the account carries a balance roll-up, and Payment Status is the processor's own answer. A Flow on those fields can open a task at 15 days past due, email the billing contact at 30, or set the account's credit status on hold — the involuntary churn and dunning article lays out a sequence that works. Statuses are settled: Completed applies, Voided and Reversed un-apply, and In Process payments older than an hour are abandoned and can be deleted.

When Kugamon is not the right choice

Kugamon connects to four processors. If you need a gateway outside Stripe, Authorize.Net, PayPal and eWay, or dozens of them across regions, Zuora's gateway coverage is wider. If you process consumer-scale card volume with real-time fraud scoring as the core problem, a dedicated payments platform is the better tool and Kugamon is the wrong shape. And Kugamon is not an accounts-receivable subledger or a general ledger: it collects the payment, applies it and reports the balance; your accounting system books it.

For a Salesforce team that wants the invoice and the payment on one record, this workflow is included in Quote to Cash at $95 and Subscription Billing at $125 per user per month, and the payments page has the gateway details.