Win more appointment-driven merchants
Lead with a workflow conversation around bookings, deposits, balances, payment links, and customer experience—not only pricing.
Why this matters to an ISO
Sell more than rates to appointment-driven merchants.
Acuity Scheduling already sits inside the merchant’s daily workflow. PayLync gives your organization a payments value-add that can complement that environment instead of forcing a rip-and-replace conversation.
Protect payment volume
Where the supported workflow fits, keep more eligible payment activity closer to the processing relationship you already manage.
Differentiate your agents
Give sales teams a software story they can use with Acuity Scheduling merchants and similar prospects.
Add software economics
Create a path to partner software revenue alongside your existing processing economics, subject to your PayLync agreement.
Partner architecture
Your merchant. Their software. Your payment relationship.
PayLync sits between the supported booking workflow and the enabled payment setup, giving the merchant a clearer path to payment while helping the ISO stay relevant in the operating workflow.
Acuity Scheduling
The merchant keeps using its existing booking and appointment workflow.
Booking / appointment contextCustomers & servicesDeposits / balances
PayLync
Turn supported merchant context into a connected payment experience.
Deposit or balance requestsCustomer payment linksPayment status visibility
Your processing setup
Gateway pricing, settlement, support ownership, and enabled payment methods stay aligned to the approved merchant setup.
Gateway ratesMerchant onboardingPortfolio support
*Exact Acuity Scheduling records, permissions, data flow, payment methods, and update behavior depend on the supported connector and merchant configuration approved during onboarding.
Give your agents a better pitch
Turn the integration into a repeatable ISO sales motion.
Help agents uncover a workflow problem first, then position PayLync around the way the merchant already operates.
Start with the merchant workflow.
Identify whether the prospect uses Acuity Scheduling and where payment collection creates friction—during deposits, balance collection, remote requests, or booking follow-up.
Agent opener: “How are you collecting payment today when a Acuity Scheduling booking is ready—does your team have to jump between systems?”
Sell the connection, not another app.
Explain that PayLync is designed to complement the supported Acuity Scheduling workflow and the merchant’s enabled payment setup.
Agent pitch: “You can keep Acuity Scheduling. PayLync adds the supported payment step around the workflow your team already uses.”
Demo one representative transaction.
Use an actual merchant scenario to show the payment request, customer experience, transaction result, exceptions, and staff follow-up.
Demo focus: “Booking context → payment request → customer pays → transaction result → staff follow-up.”
Repeat across similar merchants.
Once the workflow is validated, turn it into a repeatable playbook for additional eligible Acuity Scheduling merchants in your portfolio.
Portfolio motion: “Segment Acuity Scheduling merchants → qualify workflow → demo → onboard → measure adoption.”
Merchant deployment
From qualified lead to live payment workflow.
Keep implementation disciplined so your sales promise matches the merchant’s supported configuration.
Qualify the merchant
Confirm Acuity Scheduling usage, the payment problem, users or locations, and the business records needed for the intended workflow.
Review the setup
Review the Acuity Scheduling records, permissions, locations, and users needed for the supported payment workflow.
Configure & test
Connect the merchant account, enable the approved payment methods, and run a representative transaction from start to finish.
Launch & expand
Document who handles payment follow-up, refunds, exceptions, reconciliation, and future account changes.
✓Booking context✓Deposit or balance requests✓Customer payment links✓Enabled payment methods✓Payment status visibility✓Booking-merchant retention
A better ISO payment offering for merchants using Acuity Scheduling
Plan the connection before launch
Your PayLync payment setupPayment methodsEnabled for you by account
Processing pricingYour gateway rates
Review your payment options →
Acuity Scheduling connection reviewSoftware accessYour active plan
Integration scopeConfirmed at setup
We review the complete workflow with you instead of publishing a one-size-fits-all rate claim.
01Payment methods02Gateway pricing03Settlement timing
04Connector access05Record updates06Support ownership
Portfolio economics
Make software part of your merchant retention strategy.
For qualified partners, PayLync can create software economics alongside payment residuals. Your actual buy rate, retail price, processing terms, and eligibility depend on your partner agreement.
Illustrative portfolio100 merchants
Illustrative software margin$20per merchant / month
Illustrative monthly software revenue$2,000before processing residuals
Illustrative example only. Not a published PayLync offer. Actual partner economics vary by agreement, merchant setup, product eligibility, and processing relationship.
See a PayLync workflow
Walk through a typical payment request and discuss how it would fit your Acuity Scheduling setup.
Help Acuity Scheduling merchants get more from your payment offering
Let the merchant continue using Acuity Scheduling while PayLync handles the supported customer payment step.
Connect eligible appointments, bookings, customers, services, deposits, or balances to PayLync so more payment activity can stay within the processing relationship you manage.
Carry supported booking, customer, service, deposit, or balance context from Acuity Scheduling into PayLync for a cleaner collection experience.
Position PayLync as an additional solution for similar merchants using Acuity Scheduling, subject to connector and account eligibility.
How to bring PayLync to merchants using Acuity Scheduling
Connected payment journey
Start the handoff
Identify a merchant using Acuity Scheduling, confirm the supported appointments, bookings, customers, services, deposits, or balances and payment use case, then match the merchant to the appropriate PayLync setup.
Review the outcome
After configuration, run a representative booking payment from Acuity Scheduling through PayLync, confirm the customer experience and transaction result, and document the merchant's ongoing support and reconciliation process.
Workflow touchpoints
✓Booking context
✓Deposit or balance requests
✓Customer payment links
✓Enabled payment methods
✓Payment status visibility
✓Booking-merchant retention
Before you bring a merchant live
Use a checklist your onboarding team can actually follow.
These are the core items an ISO should validate before making the supported Acuity Scheduling payment workflow live.
Active Acuity Scheduling merchant
Merchant has access to the business records required for the intended workflow.
PayLync merchant account
Intended gateway and supported payment methods are enabled.
Authorized merchant user
A merchant contact can approve the supported connection and testing.
ISO onboarding owner
Your team knows who coordinates setup, test transaction, and launch support.
Test transaction completed
Validate the customer experience, transaction result, exceptions, and follow-up.
Support ownership documented
Define who handles refunds, payment questions, reconciliation, and future changes.
ISO Questions
What your sales and onboarding teams will want to know.
It gives your organization another way to solve a payment workflow need inside software the merchant already uses. Where the connector and account setup support it, this can strengthen the merchant relationship and create additional processing opportunities without requiring the merchant to replace Acuity Scheduling.
No. The goal is to complement the supported Acuity Scheduling workflow with PayLync payments. The merchant continues using its existing software while PayLync handles the approved payment step.
PayLync supports partner-led configurations, but the exact gateway, pricing, settlement, and commercial terms depend on the merchant account and your PayLync partner agreement. Review those items before launch rather than assuming a one-size-fits-all configuration.
The exact records and permissions depend on the supported connector and merchant configuration. Potential context may include appointments, bookings, customers, services, deposits, or balances. Confirm the exact scope during onboarding.
The merchant can use the card, ACH, or other payment methods enabled for its PayLync merchant and gateway configuration. Availability depends on the account and processing setup.
Build your Acuity Scheduling merchant playbook
Give appointment-driven merchants another reason to stay with your ISO.
Walk through a representative Acuity Scheduling merchant workflow with PayLync, validate the supported payment experience, and turn it into a repeatable sales motion for your portfolio.