Know who owns each step.
Map how orders, payment status and accounting move through your business.
Counter payments.
- Where do customers pay?
- Countertop, handheld or mobile service area.
- Which work must stay connected?
- POS, ordering, accounting and staff workflow.
- Which details should you bring?
- Current statement, pricing, contract terms and support needs.
Online payments.
- Where does checkout happen?
- Hosted checkout, embedded widget or commerce platform.
- Who controls the provider credentials?
- Your team, implementation partner or provider.
- What happens after payment?
- Order status, webhooks, reconciliation and support ownership.
Invoice payments.
- How do customers receive the request?
- Invoice, payment link or another customer-facing channel.
- Who tracks payment status?
- Name the team or system responsible for follow-up.
- Where does the result get recorded?
- Accounting handoff, payment status and follow-up owner.
Choose the next operating question.
Credential, transaction and support ownership depend on the selected provider and implementation agreement.
- 01
Channels
Where customers pay.
Review payment channels - 02
Acceptance
What takes the payment.
Payments - 03
POS and the day
Fit the POS to the workflow.
Map the POS workflow - 04
Integration
Define the handoff before you build.
Define integration ownership - 05
Provider and funds
Where the provider’s work begins.
Open the VirgoPay handoff - 06
Records
What is confirmed and recorded.
POS - 07
Growth
How customers find you.
Plan growth and crypto
A day at the counter
Set the owner and recovery path.
Start with how service runs across your team and locations, from first order to day close.
Define where service starts and who opens the order.
Owner: Your team owns the service entry point and staff role.
Recovery: Keep a manual intake path and name who resolves the block.
Decide who can adjust, split, cancel or transfer an order.
Owner: Your team sets permissions; OmniPay helps define the workflow.
Recovery: Keep the original order visible and name the approver.
Define where payment is accepted and which status returns to the order.
Owner: The provider owns the transaction; your team owns the order decision.
Recovery: Treat an unknown return as unresolved until its status is confirmed.
Name who checks totals and hands the day’s record to accounting.
Owner: Your team owns close and reconciliation.
Recovery: Separate exceptions from confirmed totals and assign follow-up.
Provider handoff
Need VirgoPay?
OmniPay validates the required contact fields. Funding and cash-out steps continue inside provider-owned VirgoPay.
OmniPay validates the required email and phone fields before the provider interface opens.
VirgoPay owns the payment steps.
Payment and platform ecosystem.
Payment networks, processors, POS platforms, and technology partners used in Canadian merchant workflows.
- 01
Current state
Describe where customers pay, what the team uses now and what needs to change.
- 02
Operating questions
Identify the workflow, system and responsibility decisions that need an owner.
- 03
Next conversation
OmniPay replies with the next questions. A review is not a quote, approval or provider commitment.