Skip to navigation

Dracma biometrics on account opening

Use this flow when the facial check already happened in Dracma. You send the verification id with the holder (individual) or with each partner (company). The API reads that verification with your tenant’s Dracma credential and finishes biometrics in that call.

There is no capture link, no acceptance page, and no selfie upload. The id must be approved and carry the same CPF as the person. Each id approves one account opening.

The tenant needs an active Dracma credential. Without it, creation returns 422 dracma_not_configured.

Flow

alt [approved and same CPF] [rejected, pending, or different CPF] POST /v1/accreditations/pf or /pj with biometry GET /v1/verifications/{id} 201 with no link 422 and no account opening is created POST .../documents kind=account_opening_terms (optional) Individuals proceed to opening. Companies stay PENDING_REVIEW Your system CorpX API Dracma

The biometry object

On person (individual) or on every partners item (company). Everyone uses the same mode: Dracma does not mix with the default flow or with another provider (422 mixed_biometry_mode).

"biometry": {
"provider": "dracma",
"evidenceId": "ver_01h..."
}

evidenceId is the Dracma verification id, not a file. The provider in this guide is only dracma.

curl -X POST "https://api.corpx.com/v1/accreditations/pf" \
-H "Authorization: Bearer $TOKEN" \
-H "X-Tenant-Id: $TENANT" \
-H "Content-Type: application/json" \
-d '{
"person": {
"name": "Ana Silva",
"cpf": "12345678909",
"birthDate": "1990-01-15",
"email": "ana@example.com",
"phone": "+5511999998888",
"biometry": { "provider": "dracma", "evidenceId": "ver_01hxyz" }
},
"address": {
"zipCode": "01310100",
"street": "Avenida Paulista",
"number": "1000",
"neighborhood": "Bela Vista",
"city": "São Paulo",
"state": "SP",
"cityIbgeCode": "3550308"
}
}'

The 201 response has no biometryLink and no acceptanceLink. The person is already biometrically approved.

  • Individuals open like the default flow: no manual review, subject to the tenant’s existing auto-approve policy.
  • Companies stay in PENDING_REVIEW. The required company PDFs are unchanged.

The verification counts only when all three hold:

  • status approved (pending and review_required do not approve);
  • subject.cpf has the same 11 digits as the person;
  • that id is not already bound to another opening that has not failed.

A network failure at Dracma does not approve. Creation returns 503 dracma_unavailable and no live opening is left behind.

Account-opening terms (optional)

The terms PDF does not block the account. Send it whenever you want, for individuals or companies, until status is ACTIVE or FAILED — including after biometrics, while INTEGRATING.

curl -X POST "https://api.corpx.com/v1/accreditations/$ACR_ID/documents" \
-H "Authorization: Bearer $TOKEN" \
-H "X-Tenant-Id: $TENANT" \
-H "Content-Type: application/json" \
-d '{
"kind": "account_opening_terms",
"contentType": "application/pdf",
"sizeBytes": 120034
}'

PUT the PDF to the uploadUrl you get back. This kind does not appear in missingDocumentKinds.

Errors

HTTPerrorCodeWhen
422dracma_not_configuredThe tenant has no active Dracma credential
422verification_not_approvedThe verification is not approved, or Dracma did not find it
422verification_cpf_mismatchThe verification CPF is not the person’s, or no CPF came back
409verification_already_usedThis id already approves another opening that has not failed
422mixed_biometry_modeA company mixed Dracma with another mode
503dracma_unavailableDracma did not respond. Retry; nothing was approved