> For the complete documentation index, see [llms.txt](https://docs.ur.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ur.app/design/cards/co-branded-debit-card-design.md).

# Co-branded debit card design

Design and submit your custom co-branded Mastercard debit card artwork.

A co-branded card puts your brand on a real UR virtual Mastercard, so your users see something that looks and feels like yours while UR handles issuing and settlement. If you plan to offer cards to your users, follow these steps to design the artwork, license your brand to UR, and submit the card for approval.

The card is virtual. Your users add it to Apple Pay, Google Pay, or a similar wallet and spend it from their phone; there is no physical card to print or ship. The artwork you create here is the face they see in those wallets and inside your app. Approval and compliance review take time, so start early and plan for it ahead of any launch date.

{% stepper %}
{% step %}
**Download and customize the template**

Start from the official Adobe Illustrator template. It is set up with the correct dimensions and safe areas, so your artwork lines up with how the card renders in the app.

{% file src="/files/ABg4DuX5ZQmA7UtJ0Zwo" %}

Choose either the dark or light color scheme as your base, then customize the card surface color to match your brand. Keep every design element inside the dashed safe area; anything outside it can be clipped or interfere with the card's functional zones.
{% endstep %}

{% step %}
**Export your design correctly**

Export a single flattened image that meets the format and compliance requirements. Getting this right avoids a rejection later in approval.

Your final card design must be:

* PNG format
* 1536 × 969 pixels
* The debit mark, included

Do not include any of the following, which either do not apply to a virtual card or are prohibited on Mastercard artwork:

* EMV chip faceplate or contacts
* Magnetic stripe
* Embossed elements
* Transparency overlays
* Holograms
* Rounded corners
* Shading or 3D effects
  {% endstep %}

{% step %}
**Authorize use of your brand**

UR needs your permission to display your brand on a Mastercard product. Provide the Copyright Registration documentation for your logo, then complete and sign the Trademark License Agreement below. This grants UR the limited right to reproduce your mark on the card.

{% file src="/files/fhmWVT0o9otGqxIqzU6W" %}
{% endstep %}

{% step %}
**Submit your design to UR for approval**

Send your exported artwork and signed agreement to UR through your dedicated integration channel. UR reviews the design against Mastercard brand standards and the card's functional constraints. Approval takes time, so submit early; UR will tell you if anything needs to change before the card can be issued.
{% endstep %}
{% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ur.app/design/cards/co-branded-debit-card-design.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.