PayTo agreements
Evaluate supported agreement creation, lifecycle and eligible payment initiation flows.
Developer gateway
Build payment workflows with ShaBaas Pay
The ShaBaas Pay developer gateway helps approved Australian businesses and platforms evaluate payment APIs, webhooks, hosted checkout and sandbox resources. Detailed authentication, endpoint behaviour and implementation specifications belong on the canonical documentation domain. Production access, credentials, permissions and supported payment flows depend on onboarding and use-case review.
What developers can build
Which payment workflows can be evaluated?
Payment experiences
Connect payment links, hosted checkout or approved payment-session workflows to software.
Status and reporting
Use transaction status, reporting and webhooks where the current integration supports them.
Use the current documentation for exact APIs, authentication, fields, errors, sandbox behaviour and production permissions. This gateway intentionally does not duplicate technical specifications.
Choose an integration path
Which implementation is right for the product?
| Path | What it does | When to consider it |
|---|---|---|
| Dashboard and payment link | Creates and distributes a payment request | Fast setup or low-code collection |
| Hosted checkout | Uses a managed customer-facing payment page | Less front-end payment development |
| Payment-session API | Creates an approved checkout or payment experience from software | Product-controlled payment journey |
| API and webhooks | Connects payment actions and status to a platform workflow | Deeper state, reporting and reconciliation integration |
Integration lifecycle
How should a team prepare for production?
Review the use case
Document the customer, payment methods, fund flow and business records involved.
Onboard and access
Complete business review, permissions and any sandbox or credential requirements.
Build and test
Set up authentication, webhooks, idempotency, retries, failures and reconciliation tests.
Approve and monitor
Complete production review, alerting, support ownership and ongoing monitoring.
Reliability principles
Design for asynchronous payment operations
Idempotency
Prevent retries or duplicate requests from creating unintended payment actions.
Webhook verification
Verify events where supported and handle retries, duplicates and out-of-order delivery.
Timeout handling
Model pending and unknown outcomes and reconcile them rather than assuming failure or success.
Ledger matching
Keep a durable business reference connected to payment status, reporting and exceptions.
Review security and access controls before requesting credentials or production access.
Common integration contexts
Where developers may use the gateway
- Invoice and billing software
- SaaS and membership workflows
- Booking and education systems
- Professional-service platforms
- Approved platform payment flows
- Hosted payment journeys connected to a product
Frequently asked questions
Questions developers ask
Is there a ShaBaas Pay API?
ShaBaas Pay provides API capabilities for approved payment workflows. Review the current technical documentation for supported endpoints, permissions and production availability.
Is a sandbox available?
Consult the current developer documentation or contact ShaBaas Pay for sandbox access, credentials and supported test scenarios.
Are webhooks available?
Webhook or status-notification patterns may be available for approved integrations. Follow the current documentation for verification, retries and event handling.
Where is the canonical technical documentation?
Detailed authentication, endpoint, request, response and error documentation belongs on docs.shabaas.com.
Can developers use hosted checkout instead of building a payment UI?
Where supported, hosted checkout can provide the customer-facing payment experience while the product integrates the surrounding request and status workflow.
How should duplicate requests be handled?
Design idempotency and duplicate prevention into the server-side workflow using the current API documentation.
What is required for production access?
Production access depends on onboarding, permissions, use-case review, technical testing, security controls and approval for the intended integration.
Where should an integration request support?
Use the appropriate support or contact path at Contact ShaBaas Pay, with the business, environment, workflow and issue details.
Developer resources
Go to the canonical implementation material
Start with the documented integration path
Review the technical material, then bring the customer journey and fund flow to an integration discussion.