Regional considerations

Integrate Terminal in Australia

Stripe supports Visa, Mastercard, American Express, and eftpos payments in Australia. All transactions must be made in Australian dollars (AUD). To accept Terminal charges in Australia, either your platform account or connected account must be in Australia.

Use locations

Create Locations for your business with addresses in Australia and associate your readers to them. This will ensure that they automatically download the configuration needed to properly process charges in Australia.

A valid address for a Location in Australia must contain the line1, city, state, postal_code, and country properties.

curl https://api.stripe.com/v1/terminal/locations \
  -u 
sk_test_4eC39HqLyjWDarjtT1zdp7dc
: \
  -d "display_name"="HQ" \
  -d "address[line1]"="1234 Victoria Street" \
  -d "address[city]"="Melbourne" \
  -d "address[state]"="Victoria" \
  -d "address[country]"="AU" \
  -d "address[postal_code]"="3000" \

Reader software version

BBPOS WisePad 3 readers operating in Australia must use the reader software version 4.01.00.41_Prod_APAC1_on_v23_490001 or later. Read about BBPOS WisePad 3 software updates for details.

eftpos payments

Eftpos is Australia’s local debit card network. More than 90% of eftpos cards are co-branded with either Visa or Mastercard, meaning you can process these cards over either network supported by the card.

Stripe processes co-branded eftpos cards over eftpos, Visa, or Mastercard depending on the least cost routing requirements and the type of transaction.

Availability

Eftpos is available to any business that uses Stripe in Australia, with the following exceptions:

• Massage treatment rooms (MCC 7297)
• Financial institutions – manual cash disbursements (MCC 6010)
• Financial institutions – merchandise and services (MCC 6012)
• Non-financial institutions – foreign currency, money orders and travellers’ cheques. (MCC 6051)
• Remote stored value load – merchant (MCC 6530)
• Stored value card purchase/load (MCC 6540)
• Wires, money orders (MCC 4829)

Cash out transactions, where the business disburses cash to a customer, aren’t supported on Terminal.

Integration requirements

To process in-person payments over the eftpos network, you need to make sure that your Terminal integration:

• Uses up-to-date Terminal SDKs

  If you use the Terminal iOS SDK, Android SDK, or React Native SDK, you need to use the following minimum SDK versions to accept eftpos payments:

  • iOS SDK 2.20.0, released on 3 May 2023
  • Android SDK 2.20.0, released on 11 May 2023
  • React Native SDK 0.0.1-beta.12, released on 1 June 2023

  You don’t need to make any changes if you use the Terminal Javascript SDK or server-driven integration.

• Uses automatic or manual_preferred capture type on your payments

  Eftpos only supports payments that are authorised and captured in a single step. Unlike networks such as Visa and Mastercard, eftpos doesn’t support placing a “hold” on a card and capturing the funds later. Only payments with automatic or manual_preferred capture type can be processed on eftpos.

  Capture type	Implementation	Result
  automatic	Set ​capture_method on the PaymentIntent to automatic.	All card payments will be authorised and captured in a single step.
  manual_preferred	Set ​capture_method on the nested payment_method_options.card_present attribute to manual_preferred.	eftpos card payments will be authorised and captured in a single step. Non-eftpos card payments will be authorised only. To capture the funds, make a separate request.
  manual	Set ​capture_method on the PaymentIntent to manual.	eftpos card payments will always decline. Non-eftpos card payments will be authorised only. To capture the funds, make a separate request.

Refund an eftpos payment

Eftpos supports online refunds through the API or Dashboard. The cardholder isn’t required to present their card again at the point of sale.

Routing multi-network debit cards

For co-branded, multi-network debit cards supporting both eftpos domestic debit and international card networks, Stripe uses the following default routing:

You can optionally request a preferred network routing choice on PaymentIntent creation, by setting the requested_priority on the nested payment_method_options.card_present.routing attribute.

Identify which network a payment was processed on

To identify which network a payment was processed on, inspect the network field on the Charge object associated with a successful PaymentIntent.

{
  "id": "ch_1Ff52K2eZvKYlo2CWe10i0s7",
  "object": "charge",
  ...
  "payment_method_details": {
    "card_present": {
      "brand": "visa",
      ...
      "network": "eftpos_au"
    },
    "type": "card_present"
  }
}