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

# Deliver out of band (QR / deeplink)

> Render the presentation request in your own UI as a QR code or deeplink.

## When to use this

You don't have a user identifier, or you'd rather render the request in your own UI. The user responds by scanning a QR or tapping a deeplink with their wallet.

No second API call is needed: [Create a presentation request](/products/didx-me/guides/verifiers/create-presentation-request) already returned everything you need.

## What you have

From the presentation request response:

| Field                       | Use                                                                               |
| --------------------------- | --------------------------------------------------------------------------------- |
| `authorizationRequestUri`   | A plain link the user can paste or tap on a mobile device to open in their wallet |
| `authorizationRequestQrUri` | The same link in a form optimised for rendering as a QR code                      |

## QR code

Render `authorizationRequestQrUri` as a QR using any QR generator and display it wherever the user can scan it with their wallet.

## Deeplink

On mobile, render `authorizationRequestUri` as a regular link or button. Tapping it launches the user's wallet with the request pre-loaded.

## User experience

When the user scans or taps:

1. Their wallet opens and displays the presentation request.
2. The wallet shows credentials that match the request.
3. The user picks one (if multiple match) and chooses what to share.
4. Selective disclosure lets them withhold attributes that aren't `alwaysDisclosed`.
5. On confirmation, the response is sent back to the platform.

<Info>Users stay in control of what personal information they share, and can decline at any time.</Info>

## What happens next

Once the user responds, retrieve the result. See [Verify presentation](/products/didx-me/guides/verifiers/verify-presentation). For real-time apps, register a [webhook](/products/didx-me/guides/webhooks) instead.

<Tip>
  Already know the user's email or username? You can let the platform do the delivery; see [Deliver via
  identifier](/products/didx-me/guides/verifiers/deliver/via-identifier).
</Tip>