JKOPay Internship — Reimagining the Legacy Membership Card Feature
JKOPay Internship — Reimagining the Legacy Membership Card Feature
JKOPay Internship — Reimagining the Legacy Membership Card Feature
From early research to engineer handoff, I co-led the redesign of JKOPay’s five-year-old Membership Card feature — a real product currently in development.
From early research to engineer handoff, I co-led the redesign of JKOPay’s five-year-old Membership Card feature — a real product currently in development.
From early research to engineer handoff, I co-led the redesign of JKOPay’s five-year-old Membership Card feature — a real product currently in development.
Role
Role
Role
Product Designer
Product Designer
Product Designer
Timeline
Timeline
Timeline
July 2025 – Aug 2025
July 2025 – Aug 2025
July 2025 – Aug 2025
Tools
Tools
Tools
Figma, Mixpanel, SurveyCake, Slack, Jira, Confluence
Figma, Mixpanel, SurveyCake, Slack, Jira, Confluence
Figma, Mixpanel, SurveyCake, Slack, Jira, Confluence
1. Overview
1. Overview
I joined JKOPay’s Product Team in summer 2025 as a Product Design Intern, co-leading the end-to-end redesign of the Membership Card feature — a real product under development for public release.
I joined JKOPay’s Product Team in summer 2025 as a Product Design Intern, co-leading the end-to-end redesign of the Membership Card feature — a real product under development for public release.
Starting from early-stage exploration, I collaborated across design, product, and engineering to modernize a five-year-old legacy system within regulatory and technical constraints.
Starting from early-stage exploration, I collaborated across design, product, and engineering to modernize a five-year-old legacy system within regulatory and technical constraints.
As the project remains under NDA, this page outlines my contributions, workflow, and takeaways.
As the project remains under NDA, this page outlines my contributions, workflow, and takeaways.
1. Overview
I joined JKOPay’s Product Team in summer 2025 as a Product Design Intern, co-leading the end-to-end redesign of the Membership Card feature — a real product under development for public release.
Starting from early-stage exploration, I collaborated across design, product, and engineering to modernize a five-year-old legacy system within regulatory and technical constraints.
As the project remains under NDA, this page outlines my contributions, workflow, and takeaways.
2. Company & Team
2. Company & Team
2. Company & Team
01 About JKOPay
01 About JKOPay
01 About JKOPay
JKOPay is one of Taiwan’s leading digital payment platforms, operating across several business lines including payments, securities, investment funds, and blockchain services.
JKOPay is one of Taiwan’s leading digital payment platforms, operating across several business lines including payments, securities, investment funds, and blockchain services.
JKOPay is one of Taiwan’s leading digital payment platforms, operating across several business lines including payments, securities, investment funds, and blockchain services.
While the company has expanded into multiple financial sectors, the B2C payment app remains its core product, serving over 7 million users across Taiwan, Japan, Korea, and Hong Kong, with growing initiatives targeting the migrant worker market.
While the company has expanded into multiple financial sectors, the B2C payment app remains its core product, serving over 7 million users across Taiwan, Japan, Korea, and Hong Kong, with growing initiatives targeting the migrant worker market.
While the company has expanded into multiple financial sectors, the B2C payment app remains its core product, serving over 7 million users across Taiwan, Japan, Korea, and Hong Kong, with growing initiatives targeting the migrant worker market.
02 Team Structure
02 Team Structure
02 Team Structure
The Product Team consisted of 20+ Product Managers and 4 Product Designers. Historically, PMs handled light user research—including desk research and competitive analysis—while designers focused primarily on UI delivery. My internship became an opportunity to experiment with integrating user research into the design workflow, exploring how PMs and designers could collaborate more closely through actual studies, surveys, and usability testing.
The Product Team consisted of 20+ Product Managers and 4 Product Designers. Historically, PMs handled light user research—including desk research and competitive analysis—while designers focused primarily on UI delivery. My internship became an opportunity to experiment with integrating user research into the design workflow, exploring how PMs and designers could collaborate more closely through actual studies, surveys, and usability testing.
The Product Team consisted of 20+ Product Managers and 4 Product Designers. Historically, PMs handled light user research—including desk research and competitive analysis—while designers focused primarily on UI delivery. My internship became an opportunity to experiment with integrating user research into the design workflow, exploring how PMs and designers could collaborate more closely through actual studies, surveys, and usability testing.
3. Project Details
3. Project Details
01 Project Background
01 Project Background
The project focused on redesigning and expanding the Membership Card feature within JKOPay’s payment app.
The project focused on redesigning and expanding the Membership Card feature within JKOPay’s payment app.
Originally launched five years ago, the feature allowed users to store and use merchant loyalty cards. The new version aimed to modernize the interface and extend its functionality, enabling broader partnerships and a smoother user experience.
Originally launched five years ago, the feature allowed users to store and use merchant loyalty cards. The new version aimed to modernize the interface and extend its functionality, enabling broader partnerships and a smoother user experience.
However, this wasn’t a simple visual refresh — the redesign had to navigate regulatory constraints, legacy infrastructure, and complex logic, making the process as much about system thinking as about interface design.
However, this wasn’t a simple visual refresh — the redesign had to navigate regulatory constraints, legacy infrastructure, and complex logic, making the process as much about system thinking as about interface design.
02 Project Team & Collaboration
02 Project Team & Collaboration
The Membership Card redesign was a cross-functional initiative that required tight coordination between product, design, and engineering teams.
The Membership Card redesign was a cross-functional initiative that required tight coordination between product, design, and engineering teams.
Our core team led the project from research to delivery, supported by multiple cross-functional partners who contributed data, marketing, and legal expertise throughout the process.
Our core team led the project from research to delivery, supported by multiple cross-functional partners who contributed data, marketing, and legal expertise throughout the process.
As one of the project co-owners, I worked closely with my PM intern partner, our PD Lead, and Senior PM to align design and product directions, plan user studies, and ensure each iteration balanced business goals with technical feasibility.
As one of the project co-owners, I worked closely with my PM intern partner, our PD Lead, and Senior PM to align design and product directions, plan user studies, and ensure each iteration balanced business goals with technical feasibility.
03 Challenges
03 Challenges
This project wasn’t just a visual redesign — it was about finding harmony among three competing forces: Legal Compliance, Technical Constraints, and User Experience. Each decision required negotiation between what’s permitted, what’s possible, and what’s usable.
This project wasn’t just a visual redesign — it was about finding harmony among three competing forces: Legal Compliance, Technical Constraints, and User Experience. Each decision required negotiation between what’s permitted, what’s possible, and what’s usable.
Below are three key challenges I faced and how I addressed each:
Below are three key challenges I faced and how I addressed each:
01 Compliance vs. Experience
01 Compliance vs. Experience
Challenge
Challenge
Membership cards were subject to strict financial and data protection regulations, while each partner brand also had its own compliance rules — such as card number visibility, barcode format, and verification flow. These constraints affected both information hierarchy and interaction design.
Membership cards were subject to strict financial and data protection regulations, while each partner brand also had its own compliance rules — such as card number visibility, barcode format, and verification flow. These constraints affected both information hierarchy and interaction design.
How I addressed it
How I addressed it
Collaborated with the legal team to define what information could or could not be displayed
Added clear visual labels to indicate cards requiring different verification processes
Provided in-context explanations when card information (e.g., full number) could not be shown
Collaborated with the legal team to define what information could or could not be displayed
Added clear visual labels to indicate cards requiring different verification processes
Provided in-context explanations when card information (e.g., full number) could not be shown
Outcome
Outcome
Delivered transparent communication for users while ensuring the UI remained compliant and scalable for future partner integrations.
Delivered transparent communication for users while ensuring the UI remained compliant and scalable for future partner integrations.
02 Legacy Constraints & Scalability
02 Legacy Constraints & Scalability
Challenge
Challenge
The backend carried heavy technical debt — the old membership and another feature were tightly coupled, sharing the same database structure. This made it technically impossible to separate their logic within a short timeframe, limiting how new information architecture and flows could be implemented.
The backend carried heavy technical debt — the old membership and another feature were tightly coupled, sharing the same database structure. This made it technically impossible to separate their logic within a short timeframe, limiting how new information architecture and flows could be implemented.
How I addressed it
How I addressed it
Broke down the redesign into modular, gradually integrable flows to reduce delivery risks
Collaborated with engineers to reuse legacy APIs while reconstructing the UI logic for the new experience
Proposed multiple fallback and iteration options, balancing technical feasibility with the ideal user flow
Broke down the redesign into modular, gradually integrable flows to reduce delivery risks
Collaborated with engineers to reuse legacy APIs while reconstructing the UI logic for the new experience
Proposed multiple fallback and iteration options, balancing technical feasibility with the ideal user flow
Outcome
Outcome
Successfully aligned product, design, and engineering on a unified goal — prioritizing user experience while keeping technical scalability in mind. The new structure can now support future card integrations with minimal rework.
Successfully aligned product, design, and engineering on a unified goal — prioritizing user experience while keeping technical scalability in mind. The new structure can now support future card integrations with minimal rework.
03 Designing for Variability
03 Designing for Variability
Challenge
Challenge
The new system needed to support multiple languages, dynamic text scaling, and different flow logic for each card type. These factors created complex constraints for layout consistency, hierarchy, and error messaging.
The new system needed to support multiple languages, dynamic text scaling, and different flow logic for each card type. These factors created complex constraints for layout consistency, hierarchy, and error messaging.
How I addressed it
How I addressed it
Tested layout across multi-language, long-text, and accessibility font-size scenarios
Established a scalable design structure, grouping all flows into three core user actions — Add, Manage, and Use — to simplify the experience
Defined flexible component behavior to prevent truncation and maintain hierarchy clarity
Tested layout across multi-language, long-text, and accessibility font-size scenarios
Established a scalable design structure, grouping all flows into three core user actions — Add, Manage, and Use — to simplify the experience
Defined flexible component behavior to prevent truncation and maintain hierarchy clarity
Outcome
Outcome
Created a layout system that remained visually consistent and accessible across languages and devices, allowing engineers to maintain a single adaptable template for all card types.
Created a layout system that remained visually consistent and accessible across languages and devices, allowing engineers to maintain a single adaptable template for all card types.
04 My Contribution & Timeline
04 My Contribution & Timeline
This timeline highlights my contributions across the project lifecycle — from early research and wireframing to design delivery and handoff to the broader design team.
This timeline highlights my contributions across the project lifecycle — from early research and wireframing to design delivery and handoff to the broader design team.
3. Project Details
01 Project Background
The project focused on redesigning and expanding the Membership Card feature within JKOPay’s payment app.
Originally launched five years ago, the feature allowed users to store and use merchant loyalty cards. The new version aimed to modernize the interface and extend its functionality, enabling broader partnerships and a smoother user experience.
However, this wasn’t a simple visual refresh — the redesign had to navigate regulatory constraints, legacy infrastructure, and complex logic, making the process as much about system thinking as about interface design.
02 Project Team & Collaboration
The Membership Card redesign was a cross-functional initiative that required tight coordination between product, design, and engineering teams.
Our core team led the project from research to delivery, supported by multiple cross-functional partners who contributed data, marketing, and legal expertise throughout the process.
As one of the project co-owners, I worked closely with my PM intern partner, our PD Lead, and Senior PM to align design and product directions, plan user studies, and ensure each iteration balanced business goals with technical feasibility.
03 Challenges
This project wasn’t just a visual redesign — it was about finding harmony among three competing forces: Legal Compliance, Technical Constraints, and User Experience. Each decision required negotiation between what’s permitted, what’s possible, and what’s usable.
Below are three key challenges I faced and how I addressed each:
01 Compliance vs. Experience
Challenge
Membership cards were subject to strict financial and data protection regulations, while each partner brand also had its own compliance rules — such as card number visibility, barcode format, and verification flow. These constraints affected both information hierarchy and interaction design.
How I addressed it
Collaborated with the legal team to define what information could or could not be displayed
Added clear visual labels to indicate cards requiring different verification processes
Provided in-context explanations when card information (e.g., full number) could not be shown
Outcome
Delivered transparent communication for users while ensuring the UI remained compliant and scalable for future partner integrations.
02 Legacy Constraints & Scalability
Challenge
The backend carried heavy technical debt — the old membership and another feature were tightly coupled, sharing the same database structure. This made it technically impossible to separate their logic within a short timeframe, limiting how new information architecture and flows could be implemented.
How I addressed it
Broke down the redesign into modular, gradually integrable flows to reduce delivery risks
Collaborated with engineers to reuse legacy APIs while reconstructing the UI logic for the new experience
Proposed multiple fallback and iteration options, balancing technical feasibility with the ideal user flow
Outcome
Successfully aligned product, design, and engineering on a unified goal — prioritizing user experience while keeping technical scalability in mind. The new structure can now support future card integrations with minimal rework.
03 Designing for Variability
Challenge
The new system needed to support multiple languages, dynamic text scaling, and different flow logic for each card type. These factors created complex constraints for layout consistency, hierarchy, and error messaging.
How I addressed it
Tested layout across multi-language, long-text, and accessibility font-size scenarios
Established a scalable design structure, grouping all flows into three core user actions — Add, Manage, and Use — to simplify the experience
Defined flexible component behavior to prevent truncation and maintain hierarchy clarity
Outcome
Created a layout system that remained visually consistent and accessible across languages and devices, allowing engineers to maintain a single adaptable template for all card types.
04 My Contribution & Timeline
This timeline highlights my contributions across the project lifecycle — from early research and wireframing to design delivery and handoff to the broader design team.
Pictures
4. Reflection & Learning
4. Reflection & Learning
4. Reflection & Learning
This internship gave me a firsthand look at how large-scale product teams balance user experience, business goals, and technical constraints. It also reshaped how I collaborate, prioritize, and communicate as a designer.
This internship gave me a firsthand look at how large-scale product teams balance user experience, business goals, and technical constraints. It also reshaped how I collaborate, prioritize, and communicate as a designer.
This internship gave me a firsthand look at how large-scale product teams balance user experience, business goals, and technical constraints. It also reshaped how I collaborate, prioritize, and communicate as a designer.
Below are some key takeaways from this experience:
Below are some key takeaways from this experience:
Below are some key takeaways from this experience:
1
1
1
Aligning design decisions with business strategy
Aligning design decisions with business strategy
Aligning design decisions with business strategy
Working with PMs taught me how to think beyond interface details — to design with a clear sense of business impact and strategic trade-offs.
Working with PMs taught me how to think beyond interface details — to design with a clear sense of business impact and strategic trade-offs.
Working with PMs taught me how to think beyond interface details — to design with a clear sense of business impact and strategic trade-offs.
2
2
2
Realizing that asking for help is a form of strength
Realizing that asking for help is a form of strength
Realizing that asking for help is a form of strength
At first, I tried to complete every design on my own. After talking with my mentor, I learned that sharing ownership led to faster progress and a stronger outcome.
At first, I tried to complete every design on my own. After talking with my mentor, I learned that sharing ownership led to faster progress and a stronger outcome.
At first, I tried to complete every design on my own. After talking with my mentor, I learned that sharing ownership led to faster progress and a stronger outcome.
3
3
3
Adapting quickly when plans change
Adapting quickly when plans change
Adapting quickly when plans change
When our survey launch was delayed due to a PR crisis, I shifted gears — using desk and field research to refine hypotheses until we could gather user data.
When our survey launch was delayed due to a PR crisis, I shifted gears — using desk and field research to refine hypotheses until we could gather user data.
When our survey launch was delayed due to a PR crisis, I shifted gears — using desk and field research to refine hypotheses until we could gather user data.
4
4
4
Persuading through design rationale
Persuading through design rationale
Persuading through design rationale
Unlike my past redesign projects, this one involved creating something new. Presenting multiple versions and explaining their trade-offs helped me gain confidence in influencing decisions through design reasoning.
Unlike my past redesign projects, this one involved creating something new. Presenting multiple versions and explaining their trade-offs helped me gain confidence in influencing decisions through design reasoning.
Unlike my past redesign projects, this one involved creating something new. Presenting multiple versions and explaining their trade-offs helped me gain confidence in influencing decisions through design reasoning.
5
5
5
Understanding that communication is part of design
Understanding that communication is part of design
Understanding that communication is part of design
My mentor’s feedback reminded me that curiosity, structure, and documentation are as vital as visual skill — they’re what turn uncertainty into alignment.
My mentor’s feedback reminded me that curiosity, structure, and documentation are as vital as visual skill — they’re what turn uncertainty into alignment.
My mentor’s feedback reminded me that curiosity, structure, and documentation are as vital as visual skill — they’re what turn uncertainty into alignment.
Pictures✨
Pictures✨