A clear answer.
A confident next step.
Practical guides for your payments, your team and the day-to-day work of running your business.
Real people. Practical help.
Start a support conversation or check an existing request. Tell us what happened and which part of BOS.PAY you’re using. Keep passwords, recovery phrases and full card details private. Our team will reply here; responses may not be immediate.
Your questions. Clear next steps.
18 guides
Set up your business for its first payment
From installing the app to checking your first sale, with a practical setup checklist.
Verification, sign-in and missing access
What to check when onboarding is blocked or a team member cannot see an option.
Accept a crypto payment at your counter
Create the sale, show the payment instructions and verify the result in BOS.PAY.
My customer paid, but the payment is pending
A checklist for locating a transfer without creating a duplicate payment.
Understand payment-request statuses
What Pending, Paid, Expired and Cancelled tell you—and what to check next.
Receiving wallets, networks and settlement
Check the destination for your crypto payments and trace a missing settlement.
Wrong network, wrong amount or a late payment
Preserve the payment evidence and establish what happened before taking another payment.
Create, share and follow a payment request
Use a payment link for remote customers and keep track of the original request.
Record card sales and understand the Nedbank partnership
Keep card sales in BOS.PAY while your card device handles the card transaction.
Record a cash sale and check the change
Keep a reliable cash record from the sale through to the end of the shift.
Review daily sales, shifts and reconciliation
Compare business records with cash counts and card-provider evidence.
Manage products and stock
Find products, review quantities and distinguish received stock from a stocktake.
Invite staff and troubleshoot permissions
Give each person their own access to the correct business.
Prepare an online checkout integration
What your developer should define and test before customers start paying.
Refund questions, duplicate sales and corrections
Separate returning money from correcting your business records.
Protect your account and report suspicious activity
Practical steps for suspicious messages, unexpected account changes and access concerns.
Contact support or raise a complaint
Send a clear account of the issue and the references needed to investigate.
Request account information or business records
Identify what you need, your relationship to the account and the relevant period.
Let’s get to the right details.
A payment reference, the status you see and what happened help us understand your enquiry.