It is seen small, and often
A physical card is held at reading distance and inspected. A virtual card is glanced at, frequently, at whatever size the interface renders it, often a fraction of physical size, sometimes as a thumbnail in a list of payment methods.
This inverts the usual hierarchy. Fine detail, subtle texture and delicate type contribute nothing at that scale; they simply turn to mush. What survives is the overall shape of the composition, the strength of the colour relationship, and the legibility of one or two elements. A virtual card design should be checked at the smallest size the app actually renders before it is checked at full size.
The corollary is that a virtual card can afford to be simpler than its physical counterpart, and usually should be. There is no manufacturing constraint pushing back, the discipline has to come from the design.
You do not control the surroundings
Card art in a digital wallet is placed into an interface designed by someone else. It may be cropped, rounded, tinted, scaled, overlaid with text, or stacked partly behind another card. The operating system may render it against a light background today and a dark one tomorrow, because the cardholder changed a system setting.
Designs that rely on the background being a particular colour break in that environment. So do designs that place a critical element near an edge that gets cropped, or that use a near-white surface which disappears against a light interface.
- Works on light and dark
- The interface around the card changes. The card must hold its edges and remain legible against both.
- Survives cropping and rounding
- Keep anything load-bearing away from the edges and corners.
- Reads as a thumbnail
- Check the design at list-item size, not just at hero size.
- Distinguishable from siblings
- If you issue several products, they must be told apart instantly in a stacked wallet view.
- Follows the platform's own rules
- Wallet providers publish their own art requirements. Those specifications are the authority for wallet assets.
The elements are the same, the emphasis is not
A virtual card still carries a scheme mark, still shows card details somewhere, and still needs to be recognisably yours. But the chip and the contactless symbol are physical features, and how they are represented, if at all, is a design decision rather than a manufacturing requirement.
Card details are the bigger shift. In an app the number is usually revealed on demand rather than printed permanently, which frees the front almost entirely. That freedom is the main creative advantage of a virtual card, and it is routinely wasted by reproducing the plastic layout, complete with a decorative fake chip and a row of placeholder digits nobody needs.
The card is not the only place the card appears
Once a card design exists it propagates: onboarding screens, the app store listing, the marketing site, a push notification, an email confirming the card has shipped, a social post at launch. In most of these it appears as a rendered image rather than as the interface element itself.
Designing only the flat card art leaves every one of those to be improvised, usually at speed and usually by whoever needs it that afternoon. The result is a launch where the card looks slightly different in five places. Deciding early which presentations are needed, a straight-on view, an angled render, a version cropped for a small space, turns that into a small, finite set of assets rather than an open-ended stream of requests.
Motion, states and the rest of the surface
A virtual card exists in an interface with states: default, revealed details, frozen, expired, replaced. Each of those states is a design problem, and each is an opportunity, a frozen card that visibly reads as frozen is better product design than a badge in the corner.
Motion is available too, and is usually best used sparingly: a considered transition when details are revealed does more for the perceived quality of a product than an animated background. Where a design does use motion, it should degrade gracefully for cardholders who have reduced-motion settings enabled.
We deliver the card design and the assets for these presentations, ready for your app team to implement. If it helps, we will talk their spec through with them.
Contrast is a functional requirement
A card in an app is not decoration, cardholders read information from it, and some of them are doing so in bright sunlight, on a dimmed screen, or with reduced vision. Contrast between text and its background is what makes that possible, and it is the first thing sacrificed when a design is chosen from a large, well-lit monitor.
The specific traps are predictable: white type over a photograph, mid-grey type on a mid-grey field, or a gradient that provides adequate contrast at one end of the card and none at the other. Any type placed over a varying background needs to be checked at its worst point, not its best.
Colour alone should also not be the only thing distinguishing two products. If your standard and premium cards differ only in hue, a cardholder with a colour vision deficiency has no reliable way to tell them apart in a wallet list, and neither does anyone glancing at a small thumbnail.
Telling a range of products apart
Issuers accumulate products: a standard card, a premium tier, a business card, a currency-specific card, a replacement. In the app these appear together, often as a stack of near-identical rectangles, and the cardholder has to pick the right one before paying.
Designing the range as a system solves this in a way that decorating each card individually does not. A consistent structural element that changes deliberately between products, a colour field, a material impression, a clear tier name in a consistent position, lets someone identify a card at a glance without reading it.
- One consistent position for the tier name
- So the eye knows where to look across every product.
- A difference that survives greyscale
- If the products are indistinguishable without colour, they are not sufficiently distinct.
- Room for products you have not launched yet
- A system with three slots and five future products causes a redesign.
Keeping virtual and physical in one family
Where a programme has both, the two must clearly be the same product. That does not mean identical artwork, the constraints differ too much for that to work well. It means a shared system: the same mark, the same palette relationships, the same typographic voice, the same underlying layout logic expressed appropriately in each medium.
In practice this is easiest when both are designed together rather than one being derived from the other months later. A virtual card designed alongside its plastic sibling ends up better than a virtual card retrofitted to match one.