Onboarding and eligibility
Business, customer, use-case and transaction review can apply before access or production activation.
Security and operational controls
ShaBaas Pay security for Australian businesses
ShaBaas Pay is an Australian payments technology provider that uses onboarding, access controls, payment authorisation, monitoring and third-party payment infrastructure to support eligible payment workflows. Security responsibilities are shared between ShaBaas Pay, its providers and the customer; exact controls, data handling and production access depend on the configured service and current terms.
Security boundaries
What does this page cover?
This page explains the security and operational questions a business should review before using payment technology. It does not create a certification, guarantee zero fraud or replace the applicable agreements, privacy notices, product documentation or customer security responsibilities.
Access and permissions
Credentials, user roles, system permissions and operational ownership should be controlled and reviewed.
Payment and data flows
Understand what ShaBaas Pay, payment partners, banks and the customer each handle in the configured flow.
A shared control model
How security fits the payment workflow
Business onboarding
Confirm the business, use case, customer journey, eligibility and operational contacts.
Payment authorisation
Use the configured bank, card, wallet or agreement flow with customer checks and applicable bank controls.
Monitoring and response
Review payment status, unusual outcomes, access events and exception signals through the available process.
Reconciliation and support
Match payment records, investigate exceptions and escalate issues to the relevant provider or support path.
Controls to review
Which security questions should a business ask?
Identity and due diligence
ShaBaas Pay may use specialist providers and trusted data sources to support identity verification, fraud prevention, customer due diligence and ongoing monitoring.
Authentication and permissions
Confirm how users, API credentials, privileged access and support contacts are created, restricted, rotated and removed.
Payment data boundaries
Clarify what data is handled by the business, ShaBaas Pay, a bank and approved payment infrastructure, including card and wallet dependencies.
Customer responsibilities
Protect credentials, verify payment requests, secure endpoints, train staff and maintain accurate refund, support and reconciliation procedures.
Operational readiness
What should be confirmed before go-live?
- Business and payer eligibility for the selected payment method
- Roles, credentials, permissions and support contacts
- Webhook or status verification and retry handling
- Pending, failed, held, returned and refund procedures
- Customer communication, phishing awareness and payment-request accuracy
- Reconciliation, audit records and escalation ownership
Payment availability and processing time may depend on the payer’s financial institution, payment method and applicable security, compliance or operational checks.
Policies and agreements
Review the governing information
Frequently asked questions
Questions about ShaBaas Pay security
How does ShaBaas Pay approach security?
ShaBaas Pay uses onboarding, access controls, payment authorisation, monitoring and approved payment infrastructure as part of the configured payment workflow.
Does ShaBaas Pay guarantee zero fraud or zero risk?
No. No payment system can remove every security risk. Businesses, customers, banks, providers and ShaBaas Pay each have responsibilities in the configured flow.
Does ShaBaas Pay store card details?
Card-data handling depends on the configured card-payment provider and implementation. Confirm the current payment boundary and merchant responsibilities before making a card-data claim.
Is ShaBaas Pay fully compliant?
ShaBaas Pay operates within applicable Australian regulatory requirements, but businesses should review the applicable terms, eligibility, privacy information and compliance responsibilities for their own use case.
What should a business do before production access?
Complete onboarding, confirm the payment flow, assign access and support owners, test exceptions and reconciliation, and review the applicable security and policy information.
Where can a business raise a security or support question?
Use Contact ShaBaas Pay and include the environment, workflow, affected record and urgency without sending unnecessary sensitive data.
Review security in the context of the payment flow
Bring the business model, data flow, customer journey and integration design to an onboarding discussion.