Who designs for Mastercard and other payment networks?
Inspect documented payment-network relationships and separate brand identity from the design of a payment product.
Pentagram designed Mastercard’s 2016 brand identity. ustwo documents product vision, research, and tested payment flows for the European Payments Initiative. These are examples of design agencies working with payment organizations on different assignments, rather than evidence of one permanent agency responsible for everything.
Humbleteam publishes this guide. The examples are selected for public evidence of the client relationship and delivery scope. They are not a comprehensive supplier roster or an independent ranking.
What did Pentagram design for Mastercard?
Pentagram’s Mastercard case describes the evolution of the interlocking-circle identity and a visual system intended for physical and digital contexts. Its archive dates the project to 2016 and credits Michael Bierut and Luke Hayman.
That supports a clear conclusion: Pentagram delivered brand identity work for Mastercard. The case does not identify the designers responsible for every payment journey, mobile application, or internal tool. It also does not establish the terms of a current engagement.
For a brand brief, inspect how the identity works across sizes, channels, and partner applications. For a product brief, request separate evidence of usability research and the actual task flows. The same logo can appear on products created by many organizations.
Who has designed a payment-network product experience?
ustwo’s European Payments Initiative case describes a product vision, research across European markets, a prototype, and payment flows. The work helped define how the proposition could develop from person-to-person payments toward commerce.
This is relevant evidence for a buyer needing research and product direction across several markets. It should prompt questions about language, payment habits, privacy expectations, and the engineering teams implementing the product. A prototype and a market launch are different milestones; the contract should say which one the agency owns.
How should buyers verify a network relationship?
Start with the named client and the specific assignment. Ask for the date, the agency’s role, and the output the client received. Then establish whether the people presenting the case will work on the proposed engagement.
A practical reference sheet has four entries: client organization, product or brand scope, delivered artifact, and an available person who can verify the work. An issuer’s card interface, an acquiring platform, and the payment network itself involve different client relationships.
The sheet prevents a familiar procurement mistake: using a recognizable logo as evidence for a capability that the underlying project never required. Buyers can compare the relevant work directly once the relationship is explicit.
Which agency conversation fits the assignment?
For an identity brief, Pentagram’s documented Mastercard work provides a relevant starting reference. Ask how a visual system carries across partner applications, small screens, and physical acceptance points, and request the rules that internal teams receive.
For a payment product brief, ustwo’s EPI work provides evidence of research and tested flows. Ask for a walkthrough of a sender or merchant task, including the assumptions that required input from the client’s engineers. Compare the prototype, research findings, and delivery responsibilities before comparing presentation style.
Use these criteria to compare proposals, then confirm availability and the people assigned to the work.
At the reference review, label each artifact as exploratory, tested, handed off, or released, according to the evidence the agency can provide. Ask the client reference to confirm the agency’s contribution and what happened after handoff. This is especially useful when a portfolio mixes visual concepts with screens from a live product.
Where does a fintech product agency fit?
A company building a banking or payments product may need its own UX partner even when it uses an established network. Humbleteam’s One Bank case documents banking-app design, including quick send and transaction details. That is evidence for a banking product assignment, not a claim to have designed the network behind the card.
For that brief, compare the fintech agency shortlist using the actual customer journey. Ask who owns the transaction rules, interface design, implementation, and release approval. Select the team whose evidence matches that boundary.