Agentic Payments Explained for Australian Retailers

Agentic payments let an AI agent pay for a shopper using payment credentials the shopper has approved. Card networks and payment providers control those credentials, while your store still handles the order and delivery. For Australian retailers, the deciding question is whether your gateway supports the specific programme on your merchant account.

What Agentic Payments Are

An AI agent-assisted payment is the payment step of a purchase made on the shopper’s behalf. Product discovery chooses the item. Checkout confirms the basket and delivery details. The payment provider then authorises the approved payment method for the agreed amount.

For example, a shopper asks an agent to reorder their usual coffee within a spending limit. The agent finds the correct pack, gets the delivered total and pays within that permission. If the total exceeds the limit, the purchase needs fresh approval. A product recommendation alone doesn’t authorise a payment.

The agentic checkout flow explains how those steps become one order. Agent Payments Protocol (AP2) is one open standard used to establish permission for agent payments. See the AP2 explanation for that separate subject.

Click to Pay and the Card-Network Groundwork

Click to Pay is the card networks’ shared online checkout experience for enrolled cards. It uses a common standard from EMVCo, the organisation that maintains card-payment specifications. Tokenisation replaces a card number with a payment credential whose use can be restricted.

Agent payment programmes build on this network tokenisation infrastructure. They add agent identity and shopper instructions to the payment flow. Mastercard describes Agent Pay tokens as agent-specific credentials, so enabling Click to Pay doesn’t automatically enable every agent payment.

Ask your gateway whether it already supports Click to Pay on your account. That capability is a useful starting point for discussing tokenised agent transactions. EMVCo’s Click to Pay overview explains the shared checkout standard.

How Mastercard Agent Pay Works in Australia

Mastercard Agent Pay registers and verifies an agent before it can transact on the network. The agent uses tokenised credentials under permissions and limits set by the shopper. Merchants and issuers receive information that identifies the purchase as an agent transaction.

Mastercard reports controlled Australian transactions using a Commonwealth Bank of Australia debit card and a Westpac credit card. The purchases covered Event Cinemas tickets and accommodation in Thredbo. IPSI processed the transactions, with Maincode’s Matilda acting as the AI system.

These examples demonstrate Australian transactions through a named payment chain. They don’t make Agent Pay an automatic setting for every Australian store. Use Mastercard’s Australian announcement to identify the participants, then ask your gateway about its acceptance path.

Visa Intelligent Commerce and PayPal

Visa Intelligent Commerce gives agents payment tokens and checks purchases against authenticated shopper instructions. A passkey authenticates the instruction. Visa’s network controls check the intended merchant and amount when the payment reaches authorisation.

Visa’s developer page lists Asia-Pacific availability but also describes development and deployment limits by market. Access to its sandbox doesn’t establish production access for an Australian merchant. Visa’s developer overview separates the services and their payment flow.

PayPal’s published services include Agent Ready and Store Sync. Agent Ready connects Braintree merchants to delegated payments in ChatGPT Apps and to Google’s AI shopping surfaces through Google Pay. Store Sync supplies catalogue data and cart operations, with orders passed into existing order systems.

PayPal also has an agent toolkit for developers building payment workflows. The toolkit is a development tool, while Agent Ready and Store Sync are merchant commerce services. PayPal requires merchants to request access through its AI team. Australian retailers need approval for their account and intended AI channel before activation. Its agentic commerce service guide gives that onboarding path.

Stripe Agentic Commerce and Your Payment Gateway

Stripe’s Agentic Commerce Suite shares product information with agents and supports agent checkout through one integration. Stripe built the Agentic Commerce Protocol (ACP) with OpenAI. Its Shared Payment Token passes an approved payment credential to the seller without exposing the underlying card number to the agent.

Stripe’s retail documentation lists the US, Canada and selected European countries for the suite. Australia is outside that published country list. An Australian Stripe payments account therefore doesn’t establish access to the suite. Stripe’s retail guide contains the supported countries.

A small business can prepare using the gateway it already has:

1. Enable supported wallets and Click to Pay through your existing checkout settings.
2. Keep product prices and stock accurate so an agent’s proposed order matches the checkout total.
3. Ask when the gateway’s agent transaction programme opens to Australian accounts.
4. Obtain its requirements for approval records, refunds and dispute handling before accepting agent orders.

In that gateway discussion, name the payment programmes you want to accept. Ask whether it accepts their tokens, preserves agent identity and exposes approval evidence alongside the order. Also establish whether agent payments settle into your existing merchant account or require a separate arrangement.

Checkout, Product and Commerce APIs Agents Call

A product application programming interface (API) lets an agent read items, prices and stock from a store’s systems. A checkout API builds the cart, sets delivery and submits the payment credential. The merchant’s checkout must recalculate the total before the purchase completes.

ACP and the Universal Commerce Protocol (UCP) describe commerce interactions between agents and sellers. A protocol defines how systems exchange requests. It doesn’t give every store an automatic public checkout API.

Shopify documents UCP shopping flows through its catalogue, cart and checkout tools. Its Checkout Model Context Protocol (MCP) tutorial creates a checkout session and sends the buyer to the merchant storefront to finish payment. Stripe documents ACP and UCP support through its commerce suite. PayPal documents both through Agent Ready and Braintree. Each route has its own account and channel requirements.

For a custom store, separate product access from permission to create an order. An agent that can read a feed must still receive a supported checkout route and an authorised payment credential.

How AI Shopping Agents Recommend How to Pay

An AI shopping agent can recommend a payment method from the methods the shopper has authorised and the store accepts. A saved card or wallet can reduce repeated entry. A buy now pay later (BNPL) method also needs the provider’s eligibility checks and the shopper’s approval of its terms.

Stripe documents Shared Payment Token support for network agent tokens and BNPL providers including Affirm and Klarna. That token capability doesn’t make every method available in every merchant country or channel. The checkout’s accepted methods and the shopper’s permission narrow the choice.

An agent must apply the shopper’s preferences, including a rule against borrowing or using a particular card. If the preferred method isn’t accepted, present another permitted method for approval. Don’t silently switch to credit to complete the order.

Card Data and PCI DSS When an Agent Pays

Tokenised agent payments can keep raw card numbers away from the agent and your store. With provider-hosted collection and isolated payment components, your exposure can stay close to a hosted checkout. The exact integration determines your Payment Card Industry Data Security Standard (PCI DSS) scope.

Typing a card number into ordinary chat changes that boundary. The chat system receives cardholder data, and retained conversations or logs can store it. Those systems then need the relevant PCI DSS controls. Encrypting the connection alone doesn’t remove them from scope.

Use a payment provider’s secure collection interface inside the experience or hand the shopper to hosted checkout. Keep card numbers out of conversation history and analytics. The PCI Security Standards Council’s messaging guidance explains the requirements for card data sent through chat.

Fraud, Chargebacks and Liability

A chargeback is a card issuer’s reversal of a merchant payment after the cardholder disputes it. The disputed revenue is withdrawn or held during the case. A chargeback fee is the processor’s or acquiring bank’s charge for handling that dispute, separate from the order value.

Agent payment programmes reduce some fraud paths through tokenised credentials and verified agent identity. Shopper-set spending limits restrict what the agent can authorise. Your store still needs to validate the order, use its gateway’s fraud controls and retain delivery evidence. A valid payment token doesn’t prove that the goods arrived or match their description.

Visa’s cardholder zero-liability protection concerns unauthorised charges against the shopper. It doesn’t promise that your store keeps every disputed payment. Mastercard’s Agent Pay material describes authenticated transactions and dispute support. It doesn’t grant a blanket merchant exemption from chargebacks. Your acquiring agreement and the applicable network dispute reason determine the store’s exposure.

Agent payment liability frameworks continue to change. Before enabling a programme, obtain the gateway’s written treatment of unauthorised purchases and agent mistakes. Identify which party carries each loss and which authentication conditions change that allocation.

Chargeback fees and response times

Stripe’s Australian standard pricing lists a $25 AUD dispute received fee and a separate $25 AUD fee for manually countering a dispute. Stripe returns the countered fee when you win. Its received fee stays payable under standard terms. Stripe’s Australian pricing gives the fee basis.

PayPal’s Australian merchant fee schedule lists a $15 AUD chargeback fee for payments received in Australian dollars. The fee doesn’t apply to transactions eligible for PayPal Seller Protection. That eligibility condition differs from simply winning a dispute. PayPal’s Australian fee schedule gives the chargeback terms.

Shopify Payments lists a $25 AUD Australian chargeback fee. Its help centre says the disputed amount and fee return when the merchant wins. Third-party gateways used on Shopify follow their own processes.

Stripe describes a full dispute lifecycle of two to three months, with a response window usually between seven and 21 days. Shopify also describes response windows of seven to 21 days and review periods up to 75 days. Your case’s notification sets the deadline. For PayPal, follow the deadline in the Resolution Centre for the specific claim or chargeback.

Managing an agent order dispute

Store the shopper’s approval with the order, including the authorised total and any spending limit. Retain the agent’s identity and the order conversation without payment card numbers. Keep the final order details and delivery tracking so staff can connect the approval to what was supplied.

When a dispute arrives, read its reason before preparing the response. Approval evidence helps answer an unauthorised-payment claim. Delivery tracking answers a different question. Submit the relevant evidence through the gateway before its deadline and retain the submission receipt.

Handle ordinary refunds through the original payment transaction and record the result against the order. An active chargeback needs the gateway’s dispute process to avoid refunding the same purchase twice. Track dispute rates separately for agent orders and other sales channels so repeated failures become visible.

Before your first agent order, assign a staff member to dispute notifications and run through where they can retrieve the approval record. An accepted payment is only one part of an order your store must be able to explain.