IDCanopy Developers
IDCanopy APIKYC

AIS Ident

Identification by account access: the user logs in to their own bank, the result confirms the account and matches the holder name

Universe:
Umbrella
Status:
live
Access:
Contact IDCanopy for credentials and product access.

Where AIS Ident fits

AIS Ident is the bank-based route to personal identification: use the account access and holder information available through the user's bank rather than starting with a document upload. It can support onboarding, mandate setup, payout checks and changes to a customer's bank details.

It belongs to KYC and also sits within open banking. Unlike AIS Data, it is about account access and identity matching, not balances or transaction history. See the KYC product overview for how bank-based identification fits alongside document and data-based verification.

What it answers

The end user logs in to their own bank and gives a one-time, read-only consent. AIS Ident confirms that this person can access this account. IBAN and bank come from the bank itself, not from user input. When you send the name you expect, it is matched against the holder name returned by the bank, and the response carries a decision you can act on.

Typical moments: before accepting a SEPA mandate, before a payout, when a customer changes their bank account. Fully online, no video call, no test transfer. Read-only: no balances, no transactions, money is never moved. The login stays at the bank; no bank credentials are stored.

More than 1,000 connected banks in Germany (as of August 2026).

Flow

Identify through bank-account access
Identify through bank-account accessYour backend to AIS Ident: POST /ais/initiate. AIS Ident to Your backend: Return redirectUrl. Your backend to User / browser: Open the hosted flow. User / browser to AIS Ident: Select bank; complete bank consent and SCA. AIS Ident to User / browser: Return to returnUrl (any outcome). Your backend to AIS Ident: POST /ais/status. AIS Ident to Your backend: Return status and identification resultUser / browserYour backendAIS Ident1. POST /ais/initiate2. Return redirectUrl3. Open the hosted flow4. Select bank; complete bank consent and SCA5. Return to returnUrl (any outcome)6. POST /ais/status7. Return status and identification result

Bank authentication happens at the bank, represented here within the hosted flow. Status lookup is shown; a configured webhook can deliver the final result instead. Browser return does not imply success. Identification results include account and name-match information, subject to the selected output mode.

Consent step (illustrative): the user grants read-only access to account details and the holder name

  1. Bank selection: the user picks their bank in the hosted flow (country pre-selects the country).
  2. Bank login: the user logs in at their own bank, on the bank website or in the banking app.
  3. Consent: one-time, read-only consent to the account details.
  4. SCA: the user confirms the consent with strong customer authentication at the bank.
  5. Data retrieval: for the account the user selects: IBAN, BIC, bank name, holder name(s), account type and the user's role on the account, as returned by the bank.
  6. Name match: the expected name is matched against every returned holder (typos, transliterations, reordered name parts).
  7. Result: account, nameMatch, ibanMatch, decision, xs2aReference and an auditTrail, via POST /ais/status and the webhook.

Output

OutputRequestContains
PII output (default)returnPii: truexs2aReference, IBAN, BIC, bank name, account holder name(s), match result, decision, audit trail
Standard outputreturnPii: falsexs2aReference, match result, IBAN match, decision, audit trail. No personal data.

Name matching: nameMatchLogic: fuzzy (default) handles typos, transliterations and reordered name parts and can return CLOSE_MATCH; exact returns only MATCH or NO_MATCH. Joint accounts: the expected name is matched against every holder.

The holder name is not guaranteed. Some banks return no holder name. Then nameMatch.result is NOT_AVAILABLE and the decision is REVIEW, never CONFIRMED.

Integration in four calls

Base URLs are in Environments.

1. Authenticate

curl -X POST "$UMBRELLA_BASE_URL/auth" \
  -H "Api-Key: $UMBRELLA_API_KEY" \
  -H "Customer-Id: $UMBRELLA_CUSTOMER_ID" \
  -H "Content-Type: application/x-www-form-urlencoded"

2. Start a session

curl -X POST "$UMBRELLA_BASE_URL/ais/initiate" \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "referenceId": "onboarding-000123",
    "returnUrl": "https://example.com/onboarding/return",
    "expectedName": { "firstName": "Erika", "lastName": "Mustermann" },
    "webhookUrl": "https://example.com/webhooks/ais"
  }'

3. Redirect the user

Send the user to redirectUrl. The session is valid for 30 minutes (expiresAt). The user returns to your returnUrl whether they finished, cancelled or failed.

4. Read the result

curl -X POST "$UMBRELLA_BASE_URL/ais/status" \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "referenceId": "onboarding-000123" }'

Or receive the same object on your webhookUrl when the session reaches a final status.

Decision

decisionWhen
CONFIRMEDSession completed, and the name and IBAN match where you supplied them.
REVIEWClose name match, or you sent a name and the bank returned none (nameMatch.result: NOT_AVAILABLE).
NOT_CONFIRMEDNo name match, IBAN mismatch, or the session ended without account data.

Status and reasons

statusMeaning
PENDINGThe user is still in the flow.
COMPLETEDAccount data retrieved; see account, nameMatch, decision.
ABORTEDThe user left the flow; see statusReason.
EXPIREDThe 30-minute session ran out.
FAILEDBank or technical failure; see statusReason.

statusReason: USER_CANCELLED, CONSENT_DENIED, SCA_FAILED, BANK_NOT_SUPPORTED, BANK_UNAVAILABLE, TIMEOUT.

Errors

StatusMeaning
400Invalid request payload, for example a missing required field.
401The bearer token is missing, invalid or expired.
403The authenticated customer does not have access to this product.
404Unknown referenceId (status call).
429Too many requests.
500Unexpected server issue.
503 / 504Temporarily unavailable or gateway timeout. Retry later.

Same error schemas as the rest of the Umbrella API.

Try it

Clickable demo: a fictional merchant starts the hosted flow with six test banks (holder, joint account, business account, no holder name, authorised user, bank down). Any login works; the test TAN is 123456.

Mock in the reference: in the Umbrella API reference, choose the server Mock. POST /ais/status answers with a canned result; add ?scenario= to pick another one:

scenarioResult
(none)COMPLETED, MATCH, CONFIRMED
reviewCOMPLETED, CLOSE_MATCH, REVIEW
standard-outputCOMPLETED with returnPii: false, no personal data
pendingPENDING
abortedABORTED, USER_CANCELLED

On this page