Managed experience
The checkout page presents the configured amount, business identity, purpose and payment methods.
Managed payment experience
Hosted checkout for Australian businesses
ShaBaas Pay hosted checkout gives eligible businesses a managed payment page that can present configured bank, card and wallet methods. It can reduce front-end payment development while onboarding, branding, available methods, settlement and integration options depend on the approved setup, customer flow and applicable exceptions.
A provider-hosted interface
What is hosted checkout?
Hosted checkout is a payment page managed by the payment provider. A business sends or redirects a customer to the page from a payment request, invoice, website or approved platform flow. It differs from a payment link, which is the URL or request distribution method, and from an embedded form that the business builds into its own interface.
Less front-end build
The business can use a hosted customer journey without owning the full payment interface.
Status and receipt
Confirmation, status and receipt information can return to the business workflow where configured.
From session to outcome
How the ShaBaas Pay checkout works
Create a request
The business creates a payment request or session through the available dashboard or approved API flow.
Customer opens checkout
The customer sees the amount, business and purpose before selecting an available method.
Customer authorises
The customer completes the configured bank, card or wallet authorisation process.
Business follows status
The result, receipt and any pending or failed state are handled in the operational workflow.
Available payment methods
Which methods can appear?
Depending on merchant configuration and the payment flow, hosted checkout may present Pay by Bank, PayID, PayTo where supported, cards, Apple Pay or Google Pay. Availability depends on the business, customer, bank, device and enabled product configuration; do not assume every method appears for every checkout.
Bank payments
Present eligible account-to-account options for customer-initiated payments or supported PayTo agreement journeys.
Cards and wallets
Keep cards and digital wallets available where activated through approved payment infrastructure for the merchant.
Choose the implementation
Hosted checkout, payment links or API?
| Option | Role | Best fit |
|---|---|---|
| Payment link | Distributes a hosted payment request | Invoices, deposits and remote collection |
| Hosted checkout | Provides the managed payment interface | Online payment journey without building the full form |
| API-created session | Creates a checkout or payment experience from software | Approved platform and software workflows |
Branding, status and security
Confirm which business name, logo, colour, description, redirect and branding controls are available before promising a custom experience. A managed checkout can reduce front-end scope, but it does not remove merchant responsibilities for accurate payment requests, customer communication, refunds, security and exception handling. Review security and onboarding controls.
Operational readiness
Which checkout states should be planned?
Customer action required
The customer has opened checkout but still needs to complete the selected method.
Processing or completed
Track the configured status and do not equate a redirect with final payment completion.
Failed, expired or cancelled
Define customer communication, retry, refund and exception handling for supported states.
Browser and device compatibility, bank approval, method configuration, redirect behaviour and integration permissions can affect the experience.
Frequently asked questions
Questions about hosted checkout
What is a hosted checkout?
A hosted checkout is a provider-managed payment page that a business sends or redirects a customer to, so the business does not need to build the full payment interface.
Does the business need to build a payment form?
No. Hosted checkout can provide the customer-facing payment interface, although the business still needs to configure the workflow, requests, redirects and operational handling.
Which payment methods can appear?
Depending on configuration, hosted checkout may present Pay by Bank, PayID, PayTo for a supported flow, cards or digital wallets. The exact methods depend on the business and customer journey.
Can the checkout use business branding?
Branding controls depend on the current product configuration. Confirm the available business name, logo, colour and customer-facing description before promising a specific presentation.
Is hosted checkout the same as a payment link?
No. Hosted checkout is the managed payment interface. A payment link is a way to distribute a payment request that may open that hosted experience.
How does the business receive payment status?
Use the configured return, confirmation, status, reporting or webhook workflow to match the payment outcome to the business record.
Can a platform create checkout sessions through an API?
Where supported, an approved platform can use an API to create or connect a hosted payment experience. Confirm the current developer documentation and permissions.
What happens when a customer closes checkout before paying?
The payment may remain incomplete or pending. The business should use the configured status and customer follow-up process rather than assuming payment success.
Related payment paths
Connect checkout to the wider workflow
Give customers a managed way to pay
Discuss the payment methods, branding, redirects and status workflow your business needs.