Designing PayTo at Amazon Australia — Modernising Real-Time Bank Payments at Scale

The first challenge was introducing PayTo as a credible payment option in a checkout ecosystem already familiar with card and PayID. Research showed that 78% of customers in usability sessions initially skipped PayTo because "bank account" implied manual BSB/account entry — a slow, error-prone experience they'd learned to avoid. The design needed to reframe PayTo as a faster alternative, not a legacy fallback.

I designed a contextual callout pattern that surfaced PayTo with a trust indicator (bank logo lockup + "Authorised by your bank") and a clear speed promise ("Approved in your banking app — under 60 seconds"). The payment tile used progressive disclosure to show the mandate summary before the customer committed, reducing second-guessing at the bank handoff screen. In A/B testing, this framing lifted PayTo selection rate by 34% over the baseline tile design.

PayTo mandates require the customer to provide either a PayID (mobile, email, or ABN) or a BSB + account number. The design challenge was creating a flow that felt lighter than traditional bank linking — customers are deeply sensitive to sharing account credentials in e-commerce contexts, even when the architecture is secure.

I introduced a dual-path input model: PayID (the preferred fast path) vs BSB/Account (the fallback). The PayID path reduces entry to a single field and shows instant bank resolution — the customer sees their bank's logo appear as they type their phone number, creating an immediate trust signal. For BSB entry, inline validation confirmed branch names in real time, reducing entry errors by 67% compared to the legacy form. The mandate preview screen — showing exactly what Amazon is authorised to debit — was the highest-impact addition to reduce authorisation abandonment.

The most critical — and riskiest — moment in the PayTo flow is the handoff to the customer's banking app for mandate approval. Amazon has no control over the bank's UI, but it entirely controls the in-between state: what the customer sees while waiting, what confidence signals they receive, and how Amazon recovers gracefully if the customer returns without completing.

I designed a dedicated "Waiting for bank approval" state with a real-time status indicator, a clear explanation of the next step ("Tap 'Approve' in your [Bank] app"), and a 120-second session window before graceful timeout. Crucially, I designed the deep-link architecture so customers on mobile would be surfaced the correct banking app directly — reducing "I couldn't find where to approve it" drop-off from 31% to 9% across the top 5 Australian banks. For desktop, a QR-to-mobile handoff pattern was introduced for the first time on Amazon AU checkout.

PayTo has a significantly richer error taxonomy than card payments — banks can return 18 distinct decline codes, each with different recoverability profiles. Showing a generic "Payment failed" message for a bank-initiated "Insufficient funds – but mandate still valid" scenario destroys both conversion and trust. I mapped every NPP error code to a customer-facing recovery path.

The error design system categorised failures into three tiers: Recoverable with retry (e.g., insufficient funds — show "Try again or add a card"); Requires action (e.g., mandate suspended — show step-by-step re-approval flow); and Terminal (e.g., account closed — gracefully route to alternate payment). Each error state carried a precise confidence-preserving message, a primary action CTA, and a secondary path to card payment. Post-launch analysis showed that 44% of PayTo declines converted via the recovery path, a rate 2.3× higher than the legacy direct debit error experience.

The real value of PayTo reveals itself on the second purchase. Unlike card payments that still require CVV entry or 3D Secure challenges, an active PayTo mandate means the customer's bank account is already linked and authorised — Amazon can debit directly within the agreed limits with no additional authentication steps. The design challenge was making this speed feel both effortless and safe.

On return visits, PayTo appears as a pre-selected payment method in checkout with the PayTo logo and masked account details. There's no re-entry, no redirect to a banking app, no waiting for approval — just confirm and pay. For Subscribe & Save and recurring orders, PayTo mandates process automatically without any customer action, turning what was previously a multi-step bank transfer into a seamless background payment. In usability testing, returning PayTo customers completed checkout in under 15 seconds — faster than saved credit cards and significantly faster than any other bank-originated payment method on Amazon AU. This frictionless repeat experience was a key driver behind the 467K customer adoption — once customers set up PayTo, they kept coming back to it.