Payment-state complexity
Customer action, bank processing, webhooks and exceptions can happen at different times.
For software platforms and SaaS
Payment infrastructure for Australian platforms and SaaS
ShaBaas Pay helps eligible Australian platforms add bank-payment and multi-method payment experiences through hosted flows or APIs. Platforms can use payment status, webhooks and reporting to connect the payment journey to their own product, subject to onboarding, permissions, supported fund flows and the current technical implementation.
The platform problem
Why do platforms need payment infrastructure?
Building bank-payment connections is only one part of the job. Product teams must handle customer authorisation, asynchronous states, exceptions, reconciliation, support and the relationship between payment records and the platform ledger. A hosted or API-led payment layer can help connect those responsibilities to the product workflow.
Reconciliation
Platform records need durable references, status handling and an exception path.
Time to market
Hosted flows, links and APIs offer different trade-offs between speed and user-experience control.
Implementation options
Which payment pattern fits the platform?
| Platform need | Potential fit | Decision point |
|---|---|---|
| One-off customer-initiated bank payment | PayID or Pay by Bank | Confirm payer-bank coverage and status workflow |
| Authorised one-off or repeat bank payment | PayTo | Confirm agreement, lifecycle and fund-flow support |
| Multi-method checkout | Hosted checkout | Balance time to market with experience control |
| No-code or low-code collection | Payment links | Define link ownership, expiry and reconciliation |
| Platform-controlled workflow | APIs and webhooks | Design idempotency, events, retries and monitoring |
Platform integration workflow
How should a platform prepare for launch?
Define the fund flow
Document who pays, who receives, what the platform records and which supported payment methods are needed.
Complete review
Work through onboarding, commercial terms, permissions and use-case approval.
Choose hosted or API
Select links, hosted checkout or deeper API and webhook integration based on product and engineering needs.
Test and monitor
Exercise payment states, reconciliation, support alerts and production-readiness checks before launch.
Reliability and responsibility
Design the payment-state model
States to distinguish
Created, pending customer action, authorised, processing, completed, failed, rejected, cancelled, expired and refunded where relevant and supported.
Webhook reliability
Verify signed events where supported, handle retries and duplicates, tolerate out-of-order delivery and run reconciliation checks.
Merchant onboarding
Describe only the verified onboarding model. Do not assume instant sub-merchant onboarding, automated KYC or marketplace settlement.
Security and support
Define platform responsibilities, ShaBaas Pay responsibilities, escalation paths and controls without giving legal advice.
Hosted implementation or API?
Hosted checkout or links can reduce time to market and payment-UI responsibility. APIs can provide more product control and deeper status integration. Choose based on engineering capacity, user-experience needs, payment-state complexity and reporting requirements.
Approved platform contexts
Where this approach may fit
- SaaS billing and approved recurring workflows
- Membership and education platforms
- Professional-service and invoice software
- Booking and service platforms
- Products that need payment status in their own ledger
- Platforms using hosted payment experiences or APIs
Marketplace split payments, sub-merchant settlement and multi-party payouts require a separate fund-flow review and are not implied by this page.
Frequently asked questions
Questions platform operators ask
What types of platforms can use ShaBaas Pay?
Eligible SaaS, membership, education, booking, professional-service and invoice platforms can assess ShaBaas Pay where the customer journey, fund flow and supported payment methods fit.
Can a platform start with hosted checkout?
Where supported, hosted checkout can provide the customer-facing payment experience while the platform integrates the surrounding workflow and status handling.
Are APIs and webhooks available?
APIs and webhook or status-notification patterns may be available for approved integrations. Confirm the current developer documentation, permissions and event behaviour.
Can platforms offer PayTo and PayID?
Depending on the approved flow, a platform can assess PayTo for authorised agreements and PayID for customer-initiated bank payments, subject to customer, bank and provider support.
Does ShaBaas Pay support cards and wallets?
Cards and digital wallets may be available in configured multi-method payment experiences. Confirm the exact methods enabled for the platform and customer journey.
Is a sandbox available?
Ask ShaBaas Pay or consult the current developer documentation for sandbox access, credentials and supported test scenarios.
What onboarding is required?
Onboarding depends on the platform, use case, permissions, fund flow, technical implementation, security controls and production approval.
Does ShaBaas Pay support marketplace split payments?
The fund flow must be reviewed before making that claim. This page does not imply marketplace split payments, sub-merchant settlement or multi-party payouts.
Platform resources
Continue the integration review
Connect the payment journey to the platform
Bring the customer flow, fund flow, state model and reporting requirements to an integration discussion.