What it does
Azupay helps Australian businesses receive bank payments through PayID, collect authorized payments through PayTo and send payouts. It offers a dashboard, partner connections and direct programming interfaces. Pricing is tailored and access requires business approval.
With PayID, the customer initiates the bank payment to the supplied identifier. PayTo first establishes an agreement that the customer approves in their banking app. The business can then initiate payments within that agreement. A checkout using both options lets a customer choose PayID when PayTo is unavailable or unsuitable.
For an integrated payment request, the programming interface (API) returns a checkout address to embed or open. The experience guides the payer, reports payment status through server notifications and returns the customer to the business.
Choose an implementation route
| Route | Practical use |
|---|---|
| Dashboard | Access PayID collections and payouts without a custom integration |
| Partner platform | Use a prebuilt connection from an Azupay partner |
| Direct integration | Configure the payment journey and automate the business workflow |
The pricing page directs businesses to a tailored quote and describes transaction fees. Include the intended collection and payout routes when requesting commercial terms.
The dashboard's Transactions area shows payment activity; Reports downloads transaction files. Payment Agreements tracks PayTo arrangements, while Balance Management provides settlement-account details and transfers back to the business's own account.
Testing access follows the initial business information and confidentiality agreement; production requires the commercial agreement, due diligence, successful testing and review of the customer experience. A custom checkout therefore needs that review included in its launch plan.
Strengths
- PayID requests can require an exact amount match and specify the type of identifier
- User roles control access to dashboard pages and actions
Watch out for
- Clients need an eligible Australian entity, registered office and matching bank account
Best for
- Australian businesses collecting one-off and recurring bank payments
- Platforms reconciling customer collections and payouts
- Enterprises integrating PayID and PayTo into existing workflows
Sources
- Azupay Australian collections, payouts and business controls (Oct 27, 2026)
- Azupay dashboard, partner and direct-integration commercial options (Oct 27, 2026)
- Azupay Australian entity and bank-account eligibility (Oct 27, 2026)
- Azupay test access and production approval requirements (Oct 27, 2026)
- Azupay dashboard navigation and role-dependent access (Oct 27, 2026)
- Azupay PayID requests and PayTo agreement-based collection (Oct 27, 2026)
- Azupay payment-request experience and configuration choices (Oct 27, 2026)
