Skip to main content
PayChoice is an Australian payment gateway. These docs cover everything an integrator needs: taking a payment, learning its outcome, storing cards and bank accounts as tokens, and running recurring billing.

​
Two ways to take a payment

PayChoice Widget

A hosted payment page you embed in an iframe. Card and bank details never touch your servers, which keeps your PCI scope small. Start here unless you have a reason not to.

Banking API

You collect the details and send them to the charge endpoint. For teams that already have a PCI-compliant payment form, or that charge stored tokens.
Whichever you choose, the outcome of every charge arrives the same way: a signed webhook notification to your endpoint.

​
Where to go next

Your first charge

Environments, credentials, API versions and a test transaction, in the order you’ll do them.

Webhooks

Register an endpoint, verify signatures, handle bank settlements and missed notifications.

Storing payment methods

Tokenise a card or bank account so you can charge it again without holding the details.

Recurring billing

Customers, memberships, subscriptions, payment schedules, invoices and dishonour fees.

​
Environments

All testing must be done against the sandbox. Anything sent to the live environment incurs real fees and charges.

​
Need help?

Email support@paychoice.com.au. The Postman collection has a runnable request for every endpoint in these docs.