2024
Global Payments
Problem/Brief
With millions of transactions daily, AMA needed to upgrade its payment system to support its ongoing growth and evolving customer expectations.
Collaborators
Sinéad Errity
Ryan Reddekopp
Louis Bessam
Roles
Team lead & UX Designer
UX Designer
UX Designer
The Situation
For over a century, AMA has been a trusted provider of services ranging from roadside assistance to insurance, registries, travel, and banking. However, as the organization expanded,
it became increasingly clear that its payment infrastructure was holding it back.
In 2023, AMA transitioned to Stripe — a more scalable and flexible solution. This shift was part of a larger initiative to streamline payment processing across all business units through a new web application, OmniPay, which would serve agents using the OmniPOS, guidewire and TravelLinq POS systems
OmniPay needed to support:
Credit
Debit
AMA Gift cards
OmniPay provides agents with a centralized experience and enhances service delivery.
Alongside OmniPay Go, a mobile app that enables roadside assistance drivers to process payments seamlessly on the road, we introduced the ability for members to save multiple credit cards, accessible across all lines of business—whether in person or online. This upgrade also paved the way for modernizing memberships by transitioning toward subscription-based options. As we implemented OmniPay, it became clear that integrating it with OmniPOS was essential. This integration brought significant improvements, increasing efficiency and high user satisfaction.
Transitioning to a new payment provider under a tight timeline meant that operational stability was paramount.
Critical Requirements
With AMA handling transactions across multiple lines of business throughout Alberta, a seamless transition from our old payment provider to Stripe was critical to:
Prevent financial losses
Avoid customer frustration
Minimize disruptions
The project faced a tight deadline due to an expiring contract. It needed to deliver a modular, secure solution that could:
Compliment our diverse POS systems
Provide a reliable experience for both agents and customers
The Approach
-
User & Stakeholder Interviews:
Interviewed finance and business units (registries, travel, insurance, membership, roadside assistance), along with agents from all lines of business.
Uncovered essential business rules and pain points across departments.
Key Findings:
Finance Requirements:
Needed credit card service fees on registry transactions, requiring an additional payment flow step.
Solution: A flexible design that integrates this step where needed, while keeping the flow simple for others.
Agent Challenges:
Agents had difficulty accurately entering transaction numbers, critical for reporting and reconciliation.
Solution: Added verification checks for character count and tooltips for guidance, reducing input errors.
These insights informed our design, allowing us to create a solution that guides agents efficiently, minimizes errors, and aligns with business needs.
Stakeholder Interview Analysis & Heuristic Review -
With the insights from our research, we moved into brainstorming and planning. Our main goals for the user flows were to:
Make agents’ workflows smoother
Align with AMA’s business goals
Improve efficiency and user satisfaction
I created a design overview document to get the design team on the same page. It helped the team stay focused by covering:
Our key objectives
Project constraints
The must-have features
This helped to set clear expectations for the team to work from. We then prioritized the critical functionalities like:
Payments
Refunds
Error handling
These were essential for the launch, while we flagged other features for future updates to keep things scalable.
-
"The design phase started with high-fidelity mockups and interactive prototypes in Figma. Key design features included:
Toasts for non-persistent messages: These brief notifications, like success messages, kept agents informed without disrupting their workflow. Agents could move on to the next customer quickly, with minimal delays.
OmniPay was built as a stand-alone application, ensuring:
A consistent look and feel based on the Product Design Pigment design system
A modular structure for easy future expansion and seamless integration with AMA’s digital tools
Throughout the process, we regularly reviewed user flows to balance complexity—such as fee inputs or transaction details—with simplicity, allowing agents to complete tasks with minimal effort.
-
Working with a contracted development team came with its challenges. Since we couldn’t create new components within the project timeline, we had to adapt our designs to fit existing elements in AMA’s component library. Key strategies included:
Adapting designs: We modified designs to fit existing components instead of creating new ones.
Using tools like Jira and Slack: We set up a regular feedback loop to discuss necessary design adjustments.
Handling technical constraints: When required to use a Material Design component instead of our custom component, we collaborated with developers to ensure it met user needs, even if it meant some aesthetic compromises."
-
Our launch followed a phased approach:
Initial pilot: Began with one department at one center
Province-wide rollout: Expanded two weeks later
This pilot helped us:
Gather early feedback
Refine key elements before the full launch
We coordinated with AMA’s learning department to:
Provide training materials to ensure a smooth transition for agents
To minimize risks, we:
Kept legacy system access as a fallback until the Stripe transition was complete
Ensured business continuity and boosted agents' confidence in the new system
-
Post-launch, monitoring and agent feedback revealed issues with incorrect fees and customer charges due to agents working across four systems for a single registry transaction. We knew that integrating Stripe with OmniPOS would address these challenges. To ensure the best outcome, we followed a thorough design process:
User research to understand pain points
User flows to create a streamlined experience
High-fidelity mock-ups to visualize the solution
The integration automated fee calculations, drastically reducing errors and simplifying the workflow. Agents praised the upgrade, saying, 'This is the best upgrade they've ever done to OmniPOS!
22.5
minutes saved per day, per agent
28.3
hours saved, province wide, daily.
99.4
percent error reduction
23.3
hours saved daily for cash-out processes
Impact & Reflection
The OmniPay project was a transformative effort for AMA, empowering agents to process payments with enhanced accuracy, reduced errors, and significant time savings. By centralizing payment processing, OmniPay eliminated the need for individual POS integrations across business units, streamlining workflows and reducing potential errors. The system's modular design also supported multiple payment scenarios, such as refunds and contactless transactions, ensuring adaptability to various workflows and future payment technologies.
Transaction errors dropped from 5,000 per week to just 3, and time savings reached approximately 28.3 hours daily across the province for registry transactions alone, with an additional 23.3 hours saved for daily cash-out processes.
Reflecting on this journey, I am proud of how our team navigated the challenges of a tight timeline, adapted to technical constraints, and delivered a solution aligned with business needs and user goals. This experience deepened my understanding of the importance of user-centred design, and it strengthened my commitment to creating solutions that seamlessly balance technical requirements with an intuitive user experience.