EUR named virtual account endorsement

Request the EUR named virtual account endorsement when an account needs newly created EUR virtual accounts to use named receiving details.

Prerequisites

1. Complete onboarding for the account.
2. Complete the account’s standard KYC/KYB flow.
3. Store the Due account ID, such as acct_DqvgNSAuQv5OEK9v.
4. Use the account ID in the Due-Account-Id header when requesting the endorsement.

How EUR named virtual accounts work

EUR virtual accounts can be created without this endorsement. If the account does not have the EUR named virtual account endorsement, newly created EUR virtual accounts are created as non-named virtual accounts.

To create named EUR virtual accounts, request the eur_va_named_v1 endorsement for the account and wait until it is approved. EUR virtual accounts created after approval use named receiving details.

Request the endorsement

Call the endorsement endpoint with the eur_va_named_v1 code.

POST /v1/kyc/endorsements/eur_va_named_v1

curl --request POST \
  --url https://api.sandbox.due.network/v1/kyc/endorsements/eur_va_named_v1 \
  --header 'Authorization: Bearer <API_KEY>' \
  --header 'Due-Account-Id: acct_DqvgNSAuQv5OEK9v'

Replace:

Requirements examples

If the endorsement response creates a KYC/KYB submission, complete the requirements returned in the submission.requirements array. The exact requirements depend on the account type.

Individual requirements example

[
  {
    "kind": "static",
    "info": [
      { "key": "nationality", "type": "iso3166_1_alpha2" },
      { "key": "birthCountry", "type": "iso3166_1_alpha2" },
      { "key": "phone", "type": "e164" },
      { "key": "email", "type": "email" },
      {
        "key": "address",
        "type": "object",
        "fields": [
          { "key": "country", "type": "iso3166_1_alpha2" },
          { "key": "postCode", "type": "swift_x" },
          { "key": "town", "type": "swift_x" },
          { "key": "street", "type": "swift_x" }
        ]
      }
    ]
  }
]

Business requirements example

[
  {
    "kind": "static",
    "info": [
      { "key": "email", "type": "email" },
      { "key": "phone", "type": "e164" },
      { "key": "website", "type": "string" },
      { "key": "registrationNumber", "type": "string" },
      {
        "key": "address",
        "type": "object",
        "fields": [
          { "key": "country", "type": "iso3166_1_alpha2" },
          { "key": "postCode", "type": "swift_x" },
          { "key": "town", "type": "swift_x" },
          { "key": "street", "type": "swift_x" }
        ]
      }
    ]
  }
]

Wait for approval

After requesting the endorsement, listen for the endorsement.status_changed webhook event before creating EUR virtual accounts that should be named.

{
  "events": ["endorsement.status_changed"]
}

When the eur_va_named_v1 endorsement is approved, create the EUR virtual account. Only EUR virtual accounts created after the endorsement is approved are named.

Create the EUR virtual account

After the endorsement is approved, create the EUR virtual account through the regular virtual account creation flow.

If you create the EUR virtual account before approval, or without requesting this endorsement, the virtual account is created as non-named.

Dashboard and sandbox notes

For dashboard clients, this endorsement is not currently discoverable in the dashboard. Share and trigger the endorsement manually when a client needs EUR named virtual accounts.

Sandbox named behavior is not simulated for testing.