Define the request
Set the amount, purpose and customer information needed for the payment workflow.
Collect payments without custom checkout
Payment links for Australian businesses
ShaBaas Pay lets a business create and share a payment link for an invoice, deposit, booking or service. Customers open the link and use the payment methods available for that business and flow, while payment status, references and receipts support follow-up. Availability, reuse, expiry and exception handling depend on the configured product.
A hosted payment request
What is a payment link?
A payment link is a hosted URL for a defined payment request. It can be shared through an invoice, email, SMS, chat, QR code or another supported channel, without requiring the business to build a custom checkout interface.
Share the link
Send the hosted URL through the channel that suits the customer and business process.
Track the outcome
Use available status, references and receipts to support communication and reconciliation.
From request to confirmation
How a ShaBaas Pay payment link works
Create
The business enters the payment details and creates a link through the available dashboard or system flow.
Share
The link is sent with enough context for the customer to understand the amount and purpose.
Authorise
The customer opens the hosted experience and selects an available payment method.
Follow up
The business uses confirmation, status, references and receipts to complete the operational workflow.
Payment method choice
Which payment methods can a link offer?
Depending on business configuration and the customer journey, a payment link may present Pay by Bank, PayID, PayTo where the specific flow supports it, cards, Apple Pay or Google Pay. Availability is not universal: confirm the configured methods, payer eligibility and supported payment flow before promising a particular option.
Bank-payment options
PayID and Pay by Bank can suit customer-initiated one-off payments. PayTo may suit an approved agreement workflow where supported.
Cards and wallets
Cards and digital wallets can remain available alongside bank payments where enabled for the business and checkout.
Common uses and controls
Use payment links with an operating process
Common use cases
Invoices, deposits, retainers, final balances, bookings, events, service payments and remote collections.
Customer experience
Show the business identity, amount, purpose, available methods and confirmation in a clear hosted journey.
Status and exceptions
Plan for completed, pending, failed or declined outcomes and any expiry or cancellation states supported by the product.
Fraud and accuracy
Confirm the recipient, amount and channel before sending. Customers should be alert to altered links, impersonation and phishing.
Payment links, invoices and hosted checkout
| Workflow | Best fit | Implementation |
|---|---|---|
| Payment link | One-off request or remote collection | Share a hosted URL |
| Invoice with a link | Payment request with billing context | Place the link in the invoice process |
| Hosted checkout | Branded online payment journey | Send or redirect customers to checkout |
| API-created session | Software-controlled workflow | Use approved APIs and webhooks |
Frequently asked questions
Questions about payment links
What is a payment link?
A payment link is a hosted URL for a defined payment request that a business can share with a customer without building a custom checkout.
Does the customer need an app?
It depends on the selected payment method. A customer can use the available hosted checkout or online-banking flow; a separate ShaBaas Pay app is not required for every method.
Can customers pay by bank, card or wallet?
Where enabled, a payment link can present Pay by Bank, PayID, PayTo for a supported flow, cards or digital wallets. The exact options depend on business configuration and the customer journey.
Can a payment link be used for an invoice?
Yes. A business can place a payment link in an invoice or send it with the invoice context so the customer can open the payment experience.
Can a link be reused?
Reuse and expiry behaviour depend on the configured product and link type. Confirm those rules before using one link for multiple customer or invoice records.
How does a business know when it has been paid?
Use the available payment status, transaction reference, confirmation and digital receipt information to match the result to the relevant customer or invoice.
What happens when a payment fails or remains pending?
Follow the configured status and exception process, communicate with the customer where needed and use another supported collection method only when the operating workflow allows it.
Related resources
Build the right collection journey
Give customers a clear way to pay
Discuss the invoice, deposit or service workflow you want to support and the methods customers should see.