Supported Payment Methods
/
eftpos Australia

eftpos Australia

Overview

Cards dominate the eCommerce landscape in Australia, representing a combined 78% of transaction value, spread across digital wallets (39%), credit (19%), and debit and pre-paid cards (20%). Consumer preference for debit is served in large part by eftpos, Australia's domestic debit network, with eftpos cards representing 21% of card share in the country. 1

Support

Payments APIModular APIs
placeholder imageplaceholder image

Routing

When your customer makes a payment with a card supporting both eftpos and another card brand, you may choose to route the payment request to the card brand that offers you the lower cost of acceptance. Begin by determining the brands supported on your customer's card, and then direct the transaction to your preferred card brand.

Card brand lookup

Use our Card BIN API to determine the brands supported by any card. If the card is co-branded, then the API response will contain multiple values under the brand array:

{
    "type": "pan",
    "brand": [
        "eftposAU",
        "visa"
    ],
    "bin": "400000",
    "binLength": 6,
    "fundingType": "debit",
    "issuerName": "BANK OF AUSTRALIA",
    "countryCode": "AU",
    "currency": "AUD",
    "dccAllowed": true,
    "anonymousPrepaid": "notPrepaidOrNonAnonymous",
    "category": "consumer",
    "multipleAccountAccess": "notSupported"
}

Transaction routing

When performing a 3DS authentication or a payment authorization, you can include instruction.routing.preferredCardBrand with a value of either eftposAU or the relevant international card brand (eg visa or mastercard) to route the transaction to the network of the card brand supplied. This overrides the default routing configuration for your Access Worldpay entity.

"routing": {
  "preferredCardBrand": "eftposAU"
}

Note: If your entity is set up to only process eftpos, or if eftpos is configured as the default brand, then you do not need to supply the instruction.routing.preferredCardBrand object for your transactions to be routed to eftpos.

instruction.routing.preferredCardBrand is currently supported on our modular 3DS and Card Payments APIs.

3DS authentication

Use our modular 3DS API to authenticate your customer. Pass the data returned in the successful authentication outcome in your customer initiated transactions.

SCA exemptions

SCA exemptions are not supported by eftpos Australia.

Taking payment

Settlement

eftpos Australia only support the authorization and settlement steps combined within a single request. This is sometimes referred to as "single message." You must therefore set instruction.requestAutoSettlement.enabled to true for all of your payment requests.

Note: Zero value payments are not supported with eftpos. A nominal amount may be sent with our Card Verification API. In this case, the transaction will appear on your cardholder's statement, but will be automatically cancelled by our Card Verification API meaning that no charge will be made.

Customer Initiated Transactions (CIT)

Submit CITs using either:

eftpos transaction processing rules

  • You must submit cvc for all guest checkout CITs (where customerAgreement is not present).
  • You must set instruction.requestAutoSettlement.enabled to true.

Merchant Initiated Transactions (MIT)

eftpos supports the following MIT types:

  • subscriptions ("customerAgreement.type": "subscription")

eftpos does not support schemeReference, so this field should not be supplied in MIT requests.

As with your CITs, you must set instruction.requestAutoSettlement.enabled to true for MIT requests.

Footnotes

1: Worldpay's Global Payment Report, 2025