White-Label Orchestration Partnership
A unified payment orchestration platform — white-labelled under the ANZ Worldline brand — to consolidate GoPay, Cybersource, and MPGS into a single merchant experience with intelligent routing, unified reporting, and new revenue-driving capabilities.
Executive Summary
ANZ Worldline operates three payment gateways — GoPay, Cybersource, and MPGS — each with partial capabilities and no unified layer connecting them. Enterprise merchants face fragmented reporting, no cross-gateway failover, and missing features that are costing ANZ Worldline competitive deals. Yuno provides the orchestration infrastructure to close every gap under a single, ANZ-branded platform.
ANZ Worldline's enterprise merchants — billing over $1B AUD annually each — need a unified payment platform with intelligent routing, batch payments, scheduled recurring, and PayTo support. Yuno delivers all of this as an invisible infrastructure layer, fully branded as ANZ Worldline.
Current State Analysis
ANZ Worldline's three gateways each solve part of the puzzle, but no single platform covers all merchant needs. This fragmentation is driving enterprise merchants to competitors and preventing ANZ Worldline from offering a complete product.
| Capability | GoPay | Cybersource | MPGS | Gap Impact |
|---|---|---|---|---|
| Cross-gateway routing & failover | ✗ | ✗ | ✗ | No redundancy — if one gateway goes down, transactions fail |
| Unified reporting | ✗ | ✗ | ✗ | Merchants maintain multiple dashboards with no cross-gateway view |
| Batch / CSV payments | ✗ | ✗ | ✗ | Lost a top-2 Australian telco due to this gap |
| Scheduled recurring payments | ✗ | ✗ | ✗ | Cannot serve subscription-based enterprise merchants |
| PayTo / account-to-account | ✗ | ✗ | ✗ | ANZ bank and Worldline talking to same merchants requiring double integrations |
| eftpos local scheme support | ✓ | Not unified with scheme tokenization across gateways | ||
| Card scheme tokenization | ✓ | ✓ | Dual tokenization (scheme + eftpos) not available in one vault | |
| Virtual terminal / MOTO | ✓ | ✓ | ✓ | Available per-gateway but not unified across all three |
Key Risk
Enterprise merchants are evaluating alternatives. The loss of a top-2 Australian telco — due to the absence of batch payment processing — illustrates the urgency. Without a unified platform, ANZ Worldline risks further churn among its highest-value accounts.
Proposed Solution
Yuno sits between ANZ Worldline's merchants and its gateways as an invisible orchestration layer. Merchants interact with an ANZ-branded platform; Yuno powers everything underneath.
ANZ Worldline Merchants
ANZ-Branded Platform (Powered by Yuno)
Orchestration Engine
Payment Gateways & Methods
Capability Matrix
Every capability below directly addresses a requirement raised by the ANZ Worldline team. Each has been validated in our discovery sessions.
Route Visa to Cybersource, Mastercard to MPGS, with automatic failover between gateways on decline. Rules-based and AI-powered routing available.
ANZ Worldline sets master routing rules (hidden from merchants). Merchants get limited self-service controls — blocking certain card types, currencies, or regions — without seeing the underlying PSP routing.
Head merchant with unlimited sub-merchants. Role-based access control lets ANZ define what each merchant user can see and do — from full routing to reporting-only views.
ANZ Worldline branding on the dashboard, URL without any Yuno reference, white-labelled developer documentation. Your merchants never know Yuno powers the platform.
Cross-gateway approval rates, decline code analysis with MAC codes, raw provider responses, and custom report builder. Export via API, webhooks, or CSV — Power BI compatible.
Scheme tokens (Visa VTS, Mastercard MDES) and eftpos tokens unified in a single, PSP-agnostic vault. Tokens are portable across gateways — no re-tokenisation when switching routes.
Account-to-account payments via ANZ's New Payments Platform rails. Bridges the gap between ANZ bank and Worldline — a single merchant integration covers cards and PayTo.
Platform-initiated recurring payments with dunning logic and automated retry on decline. ANZ Worldline can offer subscription billing to enterprise merchants out of the box.
Enterprise and government merchants submit CSV files for bulk processing. This was the deciding capability gap that led to the loss of a top-2 Australian telco.
Dashboard-based card processing for call centres and customer support. Handles poor-connectivity scenarios where pay-by-link is not feasible — critical for government merchants.
Multi-provider authentication decoupled from gateways. If the first 3DS provider fails, the transaction retries with an alternative — and the liability shift carries through to fallback gateways.
API-level surcharging mapped to gateway surcharging endpoints. With the RBA's decision to ban surcharging on Visa and Mastercard, the platform supports the transition while maintaining surcharging rules for card brands where it still applies (Amex, Diners).
Single sign-on integration compatible with enterprise identity providers. ANZ Worldline merchants authenticate once — no separate credentials for the payment platform.
Per-user action logging for compliance. Role-based refund controls so you know exactly who did what. Queryable logs for dispute resolution and internal audits.
Commercial Structure
Two components — a per-transaction fee that decreases with volume and a monthly platform fee that scales with capacity. No hidden charges, no per-integration fees, no per-merchant fees.
| Monthly Volume | Per-Transaction (USD) |
|---|---|
| 0 – 1,000,000 | $0.025 |
| 1,000,001 – 5,000,000 | $0.020 |
| 5,000,001 – 10,000,000 | $0.015 |
| 10,000,001+ | $0.010 |
| Monthly Volume | Platform Fee (USD/mo) |
|---|---|
| Up to 500,000 | $12,000 |
| 500,001 – 1,000,000 | $24,000 |
| 1,000,001 – 3,000,000 | $36,000 |
| 3,000,001+ | $48,000 Capped |
Included at no additional cost: White-label dashboard, URL, and developer documentation. All new payment method integrations (eftpos, PayTo, Click to Pay, and future methods). Full data segregation on existing cloud infrastructure. Ongoing platform maintenance and feature updates.
Integration Timeline
A phased onboarding designed to get ANZ Worldline's first enterprise merchant processing through the platform as quickly as possible, with expansion capabilities added in parallel.
Phase 1 · Weeks 1–2
White-label branding configuration (colours, logos, ANZ URL). RBAC role definitions (ANZ admin vs. merchant roles). Cybersource and MPGS gateway connections (both already supported by Yuno). Data segregation on Yuno cloud infrastructure.
Phase 2 · Weeks 2–4
eftpos integration via AP+ (dependent on production credentials). GoPay/Worldline Direct gateway integration. White-labelled developer documentation. SSO configuration with ANZ Worldline's identity provider.
Phase 3 · Weeks 4–6
End-to-end transaction testing across all three gateways. Routing rule configuration (Visa to Cybersource, Mastercard to MPGS, with failover). Dual tokenisation validation (scheme + eftpos). User role and permissions testing across ANZ admin and merchant views.
Phase 4 · Weeks 6–8
First enterprise merchant onboarded (recommend one "friendly" merchant for controlled launch). Live transaction monitoring and approval rate optimisation. Reporting validation against gateway-native reports for accuracy.
Phase 5 · Months 3–6
PayTo / NPP integration (coordinated with ANZ bank counterparts — introductions via Mike Fowler). Click to Pay enablement. Batch payments and virtual terminal rollout. Additional enterprise merchant onboarding. Optional: dedicated Australian cloud infrastructure if volume warrants.
Partnership Model
A clean responsibility split ensures ANZ Worldline retains full control over merchant relationships while Yuno handles the platform infrastructure.
| Function | ANZ Worldline | Yuno |
|---|---|---|
| Merchant contracts & KYC/AML | ✓ Owns | — |
| Gateway acquiring relationships | ✓ Owns | — |
| Platform hosting & uptime | — | ✓ Owns |
| White-label UI / UX | Co-design & approval | ✓ Builds |
| Developer documentation | Co-review | ✓ Builds & maintains |
| L1 merchant support | ✓ Owns | — |
| L2/L3 platform support | — | ✓ Owns |
| New integration requests | Requests | ✓ Builds (no charge) |
| Routing rule configuration | ✓ Owns (master rules) | Advisory & enablement |
| Regulatory compliance (AU) | ✓ Leads | Supports & adapts platform |
APAC Team
Yuno's APAC team is based in Singapore, China, and India with dedicated engineering, product, and commercial resources in your time zone. Unlike competitors headquartered in the US or UK, your integration partner operates when you do — no overnight handoffs or week-long response cycles.
Next Steps
Aligned to ANZ Worldline's internal timeline for leadership review.
Djordje presents commercial proposal and orchestration solution to ANZ Worldline leadership team. Yuno available to support the presentation if helpful. Target: Mid–Late April.
Workshop covering PayTo roadmap, latency benchmarking with a traced lookalike transaction through the European gateway, and platform walkthrough. Available in-person in Sydney or Melbourne.
ANZ Worldline leadership confirms whether to proceed with orchestration and selects provider. Target: Late April.
Contract finalisation, sandbox access for ANZ engineering team, and Phase 1 platform setup begins. Yuno APAC team available for in-person workshop in Sydney/Melbourne. Target: May 2026.
Mike Fowler facilitates introductions to ANZ bank counterparts for PayTo integration coordination. Joint meeting with Yuno, ANZ Worldline, and ANZ bank teams to align on the unified merchant experience.