> 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/user-experience/partner-positioning.md).

# Partner positioning of UR

Position UR as an embedded financial capability inside your product, not as an external service. This page covers how to introduce UR for acquisition and how to keep the account accessible afterward.

### Banner and marketing placement for introduction and acquisition

Use your introduction surfaces to acquire users into the account, in your brand's voice.

{% columns %}
{% column %}
Lead with the benefit to the user, whether that is faster payouts, better rates, or more control, and mention "real account with a Swiss IBAN" early for credibility. Position UR as an integrated part of your product rather than an external app, and write in your brand's voice, not UR's. Avoid "get the UR card" or "get the partner card" messaging, which sells the card instead of the account.
{% endcolumn %}

{% column %}

<figure><img src="/files/U83Gb0hrzM4zrCHbzs4M" alt=""><figcaption><p>Banner example</p></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

### Fixed entry points for UR account access

Beyond the introduction banner, provide persistent access to UR account features through a fixed entry point on your home screen. A fixed entry point lets your users reach their UR account to check balances and transactions without searching through menus.

{% columns %}
{% column %}
**User benefits:**

* Instant access to account balance
* Quick actions without navigation
* Less friction for frequent actions
  {% endcolumn %}

{% column %}
**Partner benefits:**

* Higher feature engagement
* Fewer support queries ("where's my account?")
* Better user retention
* A clear value proposition that stays visible
  {% endcolumn %}
  {% endcolumns %}

{% columns %}
{% column %}

<figure><img src="/files/CtH9Wgm7wlbWs6hX6sFS" alt=""><figcaption><p>Example of a fixed entry point</p></figcaption></figure>
{% endcolumn %}

{% column %}

<figure><img src="/files/dmSKglpUzCtpS6GQu7g8" alt=""><figcaption><p>Another example of a fixed entry point</p></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

{% hint style="info" icon="figma" %}
Figma reference:\
[**Fixed entry point**](https://www.figma.com/design/WKbdwKpCGPRaAN43tGXHiN/Partner-UX-Guide?node-id=1-3\&t=HrYv0jeJvqeSoQlT-1)
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ur.app/design/user-experience/partner-positioning.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.