Clear payment request
Present the intended amount, purpose and payment identifier so the customer can check the displayed business details.
Payment method
PayID is an easy-to-use identifier linked to an eligible bank account that can support one-off, customer-initiated bank payments. ShaBaas Pay can help businesses present PayID within a broader payment workflow, with references and status supporting follow-up. Availability, payment timing and bank-review outcomes depend on the payer, financial institution and supported flow.
Understand the method
PayID lets a payer use an identifier such as a mobile number or email address linked to a bank account instead of entering traditional account details. It is not the bank account itself and it is different from PayTo, which uses a customer-authorised agreement for eligible future payments.
Present the intended amount, purpose and payment identifier so the customer can check the displayed business details.
The customer uses participating online banking to select or enter the PayID and authorise the payment.
Status, references and digital receipts can support follow-up and reconciliation where available.
A practical payment journey
The business shares a PayID or a payment journey that presents the bank-payment option.
The customer enters or selects the identifier in online banking and checks the displayed account or business details.
The customer confirms the payment through their financial institution’s normal security process.
Confirmation, references and receipts support communication, exception handling and reconciliation.
Fit and workflow
ShaBaas Pay can position PayID within a payment link or hosted checkout so a customer can choose from the methods available to the business and payment flow. The customer follows the enabled payment journey and may use online banking to complete the payment. Available methods depend on business configuration.
Plan the operating model
Agree how invoice numbers, payer details, payment references, status and receipts will be recorded and matched in the accounting process.
PayID payments are typically sent quickly, but a financial institution may hold or review a payment. Actual confirmation and fund availability can vary.
The payer must use a participating financial institution and the selected business flow must be supported for the transaction.
PayID is generally customer-initiated. PayTo uses an authorised agreement and may suit approved one-off, ad hoc or regular collections.
ShaBaas Pay offers Business PayID collections for eligible Australian businesses. Customers pay using participating online banking, while the business uses the available collection status and references to reconcile receipts. Business onboarding and applicable identity checks are required before live activation.
Confirm the identifier assigned to your business and the name displayed to payers during setup. A PayID registered directly through a bank and a ShaBaas Pay Business PayID collection are different operating arrangements. Successful standard Pay by Bank payments cost AUD $0.29 incl. GST below $100, or AUD $0.99 incl. GST from $100 to $1,000 inclusive. The standard maximum is AUD $1,000 per transaction; additional limits may apply.
Create a test workspace, then confirm your collection flow and merchant payout arrangements with ShaBaas Pay. Availability and timing depend on participating institutions, account eligibility and security checks.
Keep the invoice number, expected amount and the collection reference or identifier returned by your enabled flow.
A created or pending collection is not a completed payment. Check the dashboard or the documented PayID status API for the collection outcome.
Match the confirmed amount and available payment reference to the invoice or customer record. Use webhook notifications where configured, alongside status checks for exception handling.
For example, if an invoice expects $120 and a confirmed receipt is $100, record the amount difference and investigate it before marking the invoice fully paid. This is a synthetic accounting example, not a guarantee of automatic partial-payment matching.
Use the fields actually available in your integration. Confirm export formats and accounting connections before relying on them; no automatic accounting sync is implied. A collected payment and payout to the merchant bank account are separate records. See PayID API documentation and integration resources.
Frequently asked questions
PayID is an easy-to-use identifier linked to an eligible bank account that can help a business receive customer-initiated bank payments through participating online banking.
No. PayID identifies an account for a customer-initiated payment. PayTo uses a customer-authorised agreement for eligible one-off, ad hoc or regular payments.
No separate ShaBaas Pay app is required for a PayID payment. The customer uses participating online banking, subject to the payer bank and supported flow.
PayID payments are typically sent quickly, including through Osko where supported, but timing and fund availability can vary if a financial institution applies additional security checks.
Yes. A financial institution may hold or review a payment for security reasons, so businesses should plan follow-up for pending or delayed outcomes.
Use the available payment status, transaction reference, payer details and digital receipt information to match the payment to the invoice or customer record.
PayTo may be a better fit when the business needs a customer-authorised agreement for an approved one-off, ad hoc or regular collection, subject to customer, bank and provider support.
Yes. Business PayID collections are available for eligible Australian businesses after onboarding. Customers initiate payment through participating online banking. Confirm the assigned identifier, displayed recipient name, collection flow and payout arrangements during setup.
No. Confirmation records the collection outcome. Payout to the merchant bank account is a separate step, with its own timing and status.
Related resources
Bring the invoice pattern, customer journey and reconciliation process to a fit discussion.