# Activate the EUR Account

> Coming soon, upon request — this feature is turned on for your tenant by the Aurea team. [Contact us](https://www.aureahub.com/contact)

Activate the user's EUR account, with a signature or with the consent they gave on the issuer's page.

## Overview

Send either `signature`, or `consentId` with `codeVerifier`. Either way the user's `status` becomes `active`. The order of calls: [Cards & EUR Account](https://docs.aureahub.com/docs/guide-cards.md) › The EUR Account.

## With a Signature

- `signature`: the `personal_sign` of [IBAN Signing Message](https://docs.aureahub.com/docs/cards-iban-message.md) by the user's wallet. Inside the card program session (`403` `CARD_PROGRAM_SESSION_EXPIRED`).
- The answer is the card program's, or `null` when the EUR account was already activated. Aurea also links the signing address — and the smart account — for payouts with the same signature (`eurAccountLinked` in [Local Status](https://docs.aureahub.com/docs/cards-local-status.md)).

## With the Consent Page

- `consentId`: the `code` your app received at `<redirectScheme>://eur-account-callback`; `codeVerifier`: the one [Authorization Link](https://docs.aureahub.com/docs/cards-iban-authorize.md) answered.
- Aurea keeps the user's consent for payouts, links the smart account and moves the IBAN to it, so that incoming euros arrive where the card spends. `{ "success": true }`; a smart account step that cannot be done yet is retried at the user's next consent.
- `503` until your tenant's EUR account access is set up; `422` until its consent page is.
- **Illustrative example.** The card program's answer is passed through unchanged and may carry fields not listed here: the example shows only the fields Aurea or its own app reads. Ignore the fields you do not know.

## Endpoint

### `POST /v1/gnosis/integrations/eur-account`

Authentication: bearer token required.

Activates the user's EUR account.

**Request body**

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `signature` | string | no | The signed IBAN message (with a signature) |
| `consentId` | string | no | The consent page's `code` (with the consent page) |
| `codeVerifier` | string | no | From Authorization Link (with the consent page) |

**Responses**

`200` Consent Page (illustrative)

```json
{
  "success": true
}
```

**Example request**

```bash
curl -X POST https://api.aureahub.com/v1/gnosis/integrations/eur-account \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"consentId": "CODE_FROM_THE_REDIRECT", "codeVerifier": "CODE_VERIFIER"}'
```

---

Web version: https://docs.aureahub.com/#cards-iban-activate