Education services
Salesforce-native payments for education service counters
Take in-person service payments at education service counters, training providers, and certification bodies inside Salesforce, on the constituent record. This is transaction execution for discrete education service payments, not tuition, enrollment, or student finance.
Industry context
Education service desks take payments all day. The record should show every one.
Education service desks, training providers, and certification bodies take payments in person all day: parking and fines, transcripts and document replacement, ID cards, exam and certification fees, course and workshop fees. Each payment belongs to a known person, and the record of it should live with that person in Salesforce.
Parking and fines
Permit sales, parking fees, and fines taken at the counter with a receipt on the constituent record.
Transcripts and documents
Transcript requests, document replacement, and record fees captured on the learner record in Salesforce.
ID cards and access
Campus ID issuance, replacement fees, and access credentials taken as a Salesforce transaction.
Exam and certification fees
Certification, exam sitting, and re-sit fees processed inside Salesforce on the candidate record.
Course and workshop fees
Short-course, workshop, and training payments recorded on the learner record at the point of sale.
The challenge
Service payments live outside the record.
When the counter POS is a separate system from Salesforce, reconciliation, audit trail, and the person's own record all suffer. The payment happens, but the record does not carry the full story.
Counter POS never reaches the record
Service payments run on a separate counter POS. The constituent or learner record shows the payment happened but not the detail.
Manual reconciliation across systems
Finance reconciles across the POS, the SIS, and Salesforce by hand at the end of each day.
Split audit trails
The payment sits in the POS database, the case sits in Salesforce, and the audit story is split across two systems.
Partial view of the person
Staff see that a fee was paid on the record, but not how it was taken, by whom, on which drawer, or under which policy.
The Eposly approach
Execute the service payment on the record, in one flow
Eposly executes the service payment inside Salesforce, on the constituent or learner record. Card, cash, and other methods are taken through one transaction flow, and reconciliation, audit trail, and cash-drawer accountability are built into the transaction rather than bolted on after. Eposly owns transaction execution and complements the student information system, finance, and ERP rather than replacing them.
Constituent Record
Service Request
Fee Applied
Payment Taken
Receipt Issued
Transaction on Record
Audit Trail
Key capabilities
What counter staff need, on the constituent record
Cashiering, payments, cash drawer, and end-of-day controls, tied to every service request on the constituent or learner record in Salesforce.
In-person service payments on the record
Every counter payment is created on the constituent or learner record in Salesforce, with the fee, tender, and staff member captured in one step.
Card, cash, and mixed tender in one flow
One transaction flow across card, cash, and split tender. Payments settle to your PCI-compliant gateway; the record is created in Salesforce.
Cash-drawer accountability
Drawer opens, cash events, and shift accountability are recorded on the Salesforce transaction, tied to the cashier and the shift.
Reconciliation built into the transaction
End-of-day totals, mixed tender, voids, and refunds are structured inside Salesforce, so finance reconciles in one place.
Audit trail on the standard record
Every payment lives on the standard Salesforce object with the org's controls, permissions, and audit capabilities.
Complements SIS, finance, and ERP
Eposly owns transaction execution and sends clean data to the student information system, finance, and ERP. It does not replace them.
Scope
Where Eposly fits, and where it does not
Eposly is the Salesforce-native transaction execution layer for discrete, in-person education service payments. It is not a student information system, a finance platform, or a student-retail POS.
Where Eposly fits
- In-person service payments on the constituent record
- Transcripts, document replacement, and record fees
- ID card issuance and replacement fees
- Exam sitting, certification, and re-sit fees
- Course and workshop payments taken at the counter
- Parking permits, parking fees, and fines
Where Eposly does not fit
- Tuition billing and student finance
- Enrollment and admissions workflows
- Cafeteria sales, bookstores, and student retail
- Bursary, scholarship, or loan disbursement
- Financial aid and grant management
- General ledger and finance-system replacement
Customer proof
Rated 5.0 on the Salesforce AppExchange
Environments
Where Eposly runs in education
Eposly runs on core Salesforce, so it works across Sales Cloud, Service Cloud, Education Cloud, and Public Sector Solutions. There is no separate transaction database to reconcile.
University and college service counters
Registrar, bursar, and student services desks taking discrete in-person payments on the constituent record.
Certification bodies
Certification and re-certification fees taken on the candidate record, with a receipt on the Salesforce transaction.
Training providers
Short-course and workshop providers taking course, exam, and materials payments on the learner record.
Campus parking and safety offices
Parking permits, parking fees, and fines processed on the constituent record with drawer accountability.
Records and documents offices
Transcript requests, document replacement, and ID card issuance captured as Salesforce transactions.
Why Salesforce-native
Why Salesforce-native matters for education service payments
Auditability, cash accountability, and a complete record depend on where the transaction is executed. When the payment is part of the person's record, it must execute inside Salesforce. If the transaction happens outside Salesforce, the record is incomplete and reconciliation is manual.
Same objects, security, and audit model
The transaction lives on the standard Salesforce record with the org's controls, permissions, and audit capabilities.
No separate transaction database to reconcile
The payment is created in Salesforce as it happens, so there is nothing to reconcile back at end of day.
PCI-compliant gateways connected natively
The transaction flow connects to PCI-compliant payment gateways, so card data stays off the constituent record.
Related capabilities
Related capabilities
FAQ
Frequently asked questions
Trusted by Salesforce teams running assisted, in-person sales
California DMV
Omring
QLF Brands%20--%3e%3csvg%20version='1.1'%20id='Layer_1'%20xmlns='http://www.w3.org/2000/svg'%20xmlns:xlink='http://www.w3.org/1999/xlink'%20x='0px'%20y='0px'%20viewBox='0%200%20122.2%2054'%20style='enable-background:new%200%200%20122.2%2054;'%20xml:space='preserve'%20fill='%23333333'%3e%3cg%3e%3cpath%20d='M85.7,2.6H75.6L61.9,31.7L45.6,2.6H36c2.7,1.7,4.3,3.9,6.4,7.9l17.1,29.8L75.6,7.1v31.2c0,3.6-0.7,5.8-3.8,7.9h13.9%20c-3.1-2.1-3.8-4.3-3.8-7.9V10.5C81.9,6.9,82.6,4.7,85.7,2.6'/%3e%3cpath%20d='M111.2,40.5c-6.1-9.2-7.8-12.9-15.7-13.9c5.6-0.4,11.2-5.4,11.2-12.3c0-6.9-4.3-11.7-13.7-11.7h-1.6c7.2,1.7,8,8.8,8,12.3%20C99.6,20,97,26,88.3,26v0.3c7.1,0.4,10.5,6.9,15.1,14.2c3.8,6,6.9,11,13.3,11c2.1,0,4-0.6,5.5-1.5%20C115.8,49.3,113.7,44.2,111.2,40.5'/%3e%3cpath%20d='M18.1,2.6H0c3.1,2.1,3.8,4.3,3.8,7.9v27.8c0,3.6-0.7,5.8-3.8,7.9h18.9c15.6,0,21-12.1,21-21.8C39.8,11.3,31.9,2.6,18.1,2.6%20M16.5,44.5c-5,0-6.4-2.5-6.4-6.2v-34l0,0h8.2c9.5,0,14.3,7.4,14.3,20.1C32.5,37.5,28.6,44.5,16.5,44.5'/%3e%3cpath%20d='M42.2,38.1C42.2,38.1,42.2,38.1,42.2,38.1c-0.2,0.9-1.5,5.8-6.1,8.1c0,0,0,0,0,0h12.4C43.3,43.7,42.2,38.1,42.2,38.1'/%3e%3c/g%3e%3c/svg%3e)
David M Robinson
Pearl MorissetteCalifornia DMVOmringQLF BrandsDavid M RobinsonPearl MorissetteReady to take payments inside Salesforce?
See how this would work in your Salesforce setup.