> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fluz.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Custom card art

> Submit your own branded card design for the cards Fluz issues to your customers, and get it approved by the bank and the network.

Programs that issue cards under their own brand run a **co-brand** design through Fluz. You supply the artwork and supporting documents; Fluz files them with our processor, sponsor bank, and the card network, and returns a card profile set ID that ties your design to the cards you create.

<Warning>
  Custom card art is reviewed and approved by parties outside Fluz — the sponsor bank and Visa or Mastercard. Plan for **6–8 weeks** from a complete submission to a production card profile. Do not build launch marketing around an unapproved design.
</Warning>

## Before you start

<Steps>
  <Step title="Confirm you need it" icon="❓">
    Cards issued on the standard Fluz design need no submission at all. You only need this process if your customers will see your brand on the card.
  </Step>

  <Step title="Pick your card types" icon="💳">
    Virtual, digital wallet (tokenized), and physical cards each have their own artwork requirements and their own approval steps. Submit only what you will actually issue — every extra type adds review time.
  </Step>

  <Step title="Check for reputational risk" icon="⚠️">
    Programs in crypto, cannabis, gaming, and similar verticals are subject to enhanced review, and the design itself is reviewed for anything that could be read as misleading or as an implied endorsement. See [specialized verticals →](/specialized-verticals)
  </Step>

  <Step title="Complete platform due diligence first" icon="📋">
    Card art review runs after your entity clears compliance and bank review. Starting the design in parallel is fine; submitting it before due diligence is not. [Due diligence →](/build-a-platform#due-diligence)
  </Step>
</Steps>

## What to submit

### Documents

| Document                            | Completed by | Notes                                                                                    |
| ----------------------------------- | ------------ | ---------------------------------------------------------------------------------------- |
| Co-brand card program questionnaire | Fluz         | We complete this using details you provide about the program, audience, and launch plan. |
| Bank vendor ownership form          | You          | Waived for publicly traded companies.                                                    |
| Digital wallet terms and conditions | You          | Required only if you are issuing tokenized cards to Apple Pay or Google Wallet.          |
| Marketing materials                 | You          | Landing pages, user flows, and any customer-facing collateral that shows the card.       |

### Artwork files

<Tabs>
  <Tab title="Virtual cards">
    | File                | Format | Specification                                                                             |
    | ------------------- | ------ | ----------------------------------------------------------------------------------------- |
    | Card image with PAN | PNG    | 1536 × 969 px, showing the full 16-digit sample PAN, CVV, and expiration date in position |

    Virtual card art must show a **full 16-digit PAN** — networks do not permit a truncated PAN on a virtual card face.
  </Tab>

  <Tab title="Digital wallet (tokenized)">
    | File                    | Format | Specification                                       |
    | ----------------------- | ------ | --------------------------------------------------- |
    | Card image, last 4 only | PNG    | 1536 × 969 px, displaying only the last four digits |
    | Card image, no PAN      | PNG    | 1536 × 969 px, no card number                       |
    | App icon                | PNG    | 100 × 100 px                                        |

    All three files are required. Wallet providers use them in different surfaces.
  </Tab>

  <Tab title="Physical cards">
    | File                | Format                  | Specification                  |
    | ------------------- | ----------------------- | ------------------------------ |
    | Front of card (FOC) | Adobe Illustrator (.ai) | Full 16-digit sample PAN       |
    | Back of card (BOC)  | Adobe Illustrator (.ai) | Full 16-digit sample PAN       |
    | Card carrier        | High-resolution PDF     | The mailer the card arrives on |

    <Note>
      Physical issuance is not enabled on every Fluz program. Confirm availability with your Fluz contact before you commission physical artwork.
    </Note>
  </Tab>
</Tabs>

### Sample PAN convention

Artwork proofs must use the network's reserved sample number so the file is never mistaken for a live account.

| Network    | Sample PAN must end in |
| ---------- | ---------------------- |
| Mastercard | `x3456`                |
| Visa       | `x9010`                |

## Network requirements

Both networks specify what has to appear on the card face and where. A file that omits any required element is rejected at network review, not at bank review — which costs you the full cycle.

<AccordionGroup>
  <Accordion title="Mastercard" icon="💳">
    | Element            | Requirement                                                                                            |
    | ------------------ | ------------------------------------------------------------------------------------------------------ |
    | Brand mark         | Mastercard symbol, Mastercard Premium brand mark, Maestro, or Cirrus. Minimum 3 mm from the card edge. |
    | Product identifier | 8.8 mm in size, at least 4 mm from the brand mark.                                                     |
    | PAN                | Full 16 digits.                                                                                        |
    | CVC/CVV            | 3 digits.                                                                                              |
    | Expiration date    | Required.                                                                                              |

    Additional design references are available in the [Mastercard Design Center library](https://www.mastercard.us/en-us/business/overview/support/design-center.html).
  </Accordion>

  <Accordion title="Visa" icon="💳">
    | Element                 | Requirement                                                                    |
    | ----------------------- | ------------------------------------------------------------------------------ |
    | Brand mark              | Minimum 3 mm from the card edge, rendered in Title Case.                       |
    | Cardholder name         | Required.                                                                      |
    | PAN                     | Full 16 digits.                                                                |
    | CVC/CVV                 | 3 digits.                                                                      |
    | Expiration date         | Required.                                                                      |
    | Virtual account marking | Optional. If used, "Visa Virtual Account" or "Virtual Account", in Title Case. |

    **Limited use cards.** If the card is restricted — card-not-present only, for example — that restriction has to be disclosed. Displaying "Limited Use" on the card face is optional, but where it does appear it must be clearly visible; otherwise the disclosure belongs in your cardholder materials or in-app. Fluz reviews your disclosure copy alongside the artwork.

    Visa programs carry one extra approval step (BMAS) that Mastercard programs do not. Budget an additional 1–2 weeks.
  </Accordion>
</AccordionGroup>

## Design rules

<Check>
  Design against a neutral background. Card art is rendered in surfaces you do not control — a design that depends on a specific backdrop will not survive them.
</Check>

<Check>
  Keep the PAN, CVV, expiration date, and cardholder name legible against whatever sits behind them. Contrast failures are the most common rejection we see.
</Check>

<Check>
  Hold all brand marks and required elements inside the safe area. Nothing may crowd or overlap the network brand mark.
</Check>

<Check>
  Use only marks you have the right to use. Third-party logos require documented permission from the mark holder.
</Check>

<Check>
  Avoid anything that implies a benefit, guarantee, or affiliation the program does not actually provide.
</Check>

## Approval timeline

Each stage runs in sequence, and a rejection at any stage sends the file back to the start of that stage.

<Steps>
  <Step title="Processor compliance review — 5 business days" icon="🔍">
    Basic KYB on the co-brand entity, confirming registration matches the submitted documents and surfacing reputational risk.
  </Step>

  <Step title="Bank review, entity — 5 business days" icon="🏛️">
    The sponsor bank runs its own KYB scan on the co-brand entity and its own reputational risk assessment.
  </Step>

  <Step title="Bank review, collateral — 10 business days" icon="🖼️">
    Card art, carrier, and marketing materials are reviewed separately from the entity. This is the longest single stage.
  </Step>

  <Step title="Network program approval — 5–10 business days" icon="🔗">
    Filed with the network: a PIF for Visa, an RPP for Mastercard.
  </Step>

  <Step title="Network art approval, Visa only — 5–10 business days" icon="🎨">
    Digital card art is submitted to Visa through BMAS. Mastercard programs skip this stage.
  </Step>

  <Step title="Card profile creation — 3 business days" icon="🆔">
    Once bank approval lands, a card profile set ID is created for your program. This is what guarantees your cards issue with your art.
  </Step>
</Steps>

**Additional setup, where applicable**

| Item                                     | Duration           | Prerequisite                                       |
| ---------------------------------------- | ------------------ | -------------------------------------------------- |
| Digital wallet fulfillment profile       | 5–10 business days | Bank and network approval of the digital card art  |
| Physical card profile                    | 2 business days    | Bank and network approval of the physical card art |
| Tokenization (Apple Pay / Google Wallet) | Up to 8 weeks      | Program approvals and wallet provider setup        |

<Note>
  Tokenization is the long pole. If push provisioning is part of your launch, start it as early as the approvals allow. See [digital wallet push provisioning →](/features/virtual-card-wallet-provisioning)
</Note>

## After approval

Your program is assigned a **card profile set ID**. Fluz attaches it to your platform credentials, so cards created on your program automatically carry your approved design — no change to your integration.

Any later change to an approved design is a new submission and runs the full bank and network cycle again. Colors, logos, layout, and disclosure copy are all in scope. Get the design right before you submit rather than iterating through review.

## Submit your card art

Send your artwork files, supporting documents, and marketing collateral to your Fluz contact, or email us directly and we will open the submission for you.

<Card title="Start a card art submission" icon="📨" horizontal href="mailto:humans@fluz.app?subject=Custom%20card%20art%20submission">
  Email [humans@fluz.app](mailto:humans@fluz.app) with your program name, the card types you are issuing, and your artwork files attached.
</Card>

Questions on a design before you commit to it? Reach your Fluz contact or write to [humans@fluz.app](mailto:humans@fluz.app) — a five-minute look at a draft is cheaper than a rejection six weeks in.