SALESFORCE-NATIVE PAYMENTS
Collect Salesforce payments on the record your team already has open
The simple way to collect payments inside Salesforce.
Book a demo
Salesforce payments can be collected from the object your team already works from, one-off or recurring, without leaving the record. Every payment result is written to Salesforce as a record, so reports, Flows and service consoles read payment activity the same way they read any other data. Eposly Payments is the layer that runs the collection.
Payment methods
Card in person and over the phone, cash, and one-time bank payments in the US.
Recurring collection
On a saved card, with the frequency and the stopping rule set when you set it up.
Customer service
Your agent answers a payment question from the record already in front of them.
Automation
A Flow starts when a payment succeeds or fails, in the builder your admin already uses.


Eposly is rated 5.0 from 26 verified reviews on the Salesforce AppExchange
THE PROBLEM
Why collect payments inside Salesforce?
Because the payment and the customer record end up in the same place, so you never move between systems to take a payment, check whether it succeeded, or follow one up.
When your payment processing sits outside Salesforce, your staff switch systems to take a payment, check its status or investigate a failed collection. Each switch is a small cost on its own. Together they decide how long your customer waits at the counter, and how confidently your agent answers a question on a call.
You switch systems
Taking a payment means leaving the Salesforce record for a separate application, then coming back.
Status is not on the record
Your customer service team cannot confirm whether a payment succeeded without opening another system.
Follow-up takes investigation
You have to find the payment details before you can follow up with the customer.
TAKE A PAYMENT
How does a team take a payment in Salesforce?
You start from the Salesforce record you are already working on, choose a supported payment method, and collect the agreed amount. For electronic payments, the payment provider handles processing.
-
0101Open the Salesforce record the payment belongs to.
-
0202Choose the payment method your customer is using.
-
0303Collect the agreed amount. Electronic payments are processed by the payment provider.
-
0404The result is written to Salesforce as a record against that customer.
-
0505Your reports, Flows and service console read that record like any other data.

RECURRING PAYMENTS
How do you automate a recurring payment in Salesforce?
You choose the customer and a saved card, then set the payment frequency and when collection should stop. Eposly collects each payment as it falls due, without you opening the record again.
Memberships, donations and payment plans all collect from the same customer repeatedly. Set the frequency anywhere from daily through to biannual, or use a rule such as every few days or the first Monday of the month.
Four schedule types decide when collection stops:
- An end date
- A count
- A balance
- Open-ended
You can take an initial payment and save the card in the same setup, and an expired card is blocked at setup rather than failing on the first collection.
Eposly pauses the schedule, records a reason, and includes the failed collection in a Salesforce report so you can follow it up.





PAYMENT GATEWAYS
Is Eposly a payment processor?
No. Eposly does not process payments itself. The payment provider does that. Eposly runs the collection inside Salesforce and records the result on your customer record.
The distinction matters when you are working out what you are buying and what you already have. The payment provider carries on doing what it already does. What changes is where the collection starts, and where the result ends up.
-
Eposly runs the collection on your Salesforce record
-
The payment provider processesand settles the funds
-
The result is written to Salesforce as a record
The provider processes
The payment provider processes the transaction and settles the funds.
Eposly collects and records
Eposly runs the collection on your Salesforce record and writes the result to it.
Card data stays tokenised
Saved cards are tokenised, so card numbers are not held in Salesforce.
What does Salesforce-native mean here?
It means the payment runs inside your platform rather than beside it: the same objects, the same automations, the same data model, the same security and the same audit model you already have. There is no middleware, no separate database and nothing to sync back afterwards.
PAYMENT METHODS
Which payment methods can you collect in Salesforce?
Card payments in person and over the phone, cash, and one-time bank payments in the US.
| Method | When you use it |
|---|---|
| Card, in person | Counter and front-desk payments on a terminal |
| Card, over the phone | Call-centre and card-not-present payments |
| Cash | Recorded in Salesforce alongside every other method |
| Bank payments, one-time, US ACH | Your customer enters their bank details, tokenised, with a mandate and a confirmation email |
| Digital wallets, one-time | Wallet and alternative payment methods, collected and recorded the same way as a card |
Saved cards are tokenised. Card surcharging is supported on card payments.
REPORTING AND AUTOMATION
Where do Salesforce payments appear for reporting and automation?
Each payment result is written to Salesforce as a record, so your reports, Flows and service consoles read it like any other data.

- See your completed and failed collections in a report.
- Answer a customer's payment question from the Salesforce record in front of you.
- Start a Flow when a payment succeeds or fails, using the same builder your admin already uses.
- Keep payment history alongside the rest of your customer's record.
Not sure which product fits? Compare Eposly Payments and Point of Sale
CHOOSE AN EPOSLY PRODUCT
Do you need Eposly Payments or Eposly Point of Sale?
Choose Payments when the amount you are collecting is already agreed. Choose Point of Sale when you also have to select and price what you are selling.
| Comparison category | Eposly Payments | Eposly Point of Sale |
|---|---|---|
| Your situation | The amount you need to collect is already agreed. | You still have to work out what you are selling and what it costs. |
| What you do | Collect a one-off or recurring payment on the Salesforce record. | Select and price products, create the order, complete checkout. |
| Where you see it | Service desks, clinics, call centres and membership organisations. | Counters, front desks and stores selling from a catalogue. |
PREREQUISITES
What do you need to run Eposly Payments?
Your existing Salesforce org, and a payment provider.
Your Salesforce org
Eposly Payments installs into the org you already have and runs on the records your team already uses.
A payment provider
Eposly does not process payments itself. Collection runs through a payment provider.
When this is not for you
If you need to select, configure and price what you are selling before collecting, Point of Sale is the right product. Payment links your customer follows themselves are not part of Payments today.
IN PRACTICE
What can you use Eposly Payments for?
If you run a service desk, a clinic, a call centre or a membership organisation, you use it to collect an amount that is already agreed, once or on a schedule, from the Salesforce record you are already working on.
You collect a donation while viewing the supporter record.
Your agent takes a payment during a customer conversation.
A permit or licence fee is collected on the case record that raised it.
A clinic takes an agreed deposit or co-pay on the patient record.
GO DEEPER
Where do you find more detail?
Three published articles cover the compliance, field and cash questions this page raises.
QUESTIONS
Frequently asked questions
Collect your payments inside Salesforce
See what the workflow looks like for your team, and how it fits the Salesforce setup you already have.
Book a demo