Initiate claim
Initiates a new PIX key ownership or portability claim for the participant identified in the route. Claim deadlines are seven calendar days and claimer/donor ISPB equality is rejected by domain validation.
Authorizations
JWT bearer token issued by the identity provider.
Headers
Idempotency key, max 255 characters
Path Parameters
Claiming participant ISPB (8 numeric digits)
Body
PIX key ownership or portability claim to initiate (seven-day deadline; claimer and donor ISPB must differ)
Claim kind: OWNERSHIP (dispute the current owner) or PORTABILITY (move an existing key to this participant)
OWNERSHIP, PORTABILITY "OWNERSHIP"
Claimer account number, 1 to 20 digits, the key would be bound to. BACEN admits letters here; this rail does not, and the door states the narrower rule it applies.
^[0-9]{1,20}$"9988776"
Claimer account type: CACC, SVGS, TRAN, SLRY, or OTHR.
CACC, SVGS, TRAN, SLRY, OTHR "CACC"
Full legal name (CPF) or company name (CNPJ) of the claiming key owner, at most 150 characters (BACEN DICT 2.12.1 Person.Name).
1 - 150"João Silva"
Claimer account opening date, RFC 3339.
"2020-01-15T00:00:00Z"
Claimer tax identifier: 11 digits for a CPF, 14 alphanumeric characters for a CNPJ (IN RFB 2.229/2024). Its length selects the BACEN person type, and the check digits are verified by the service.
^([0-9]{11}|[0-9A-Z]{12}[0-9]{2})$"12345678901"
PIX key type: CPF, CNPJ, EMAIL, PHONE, or EVP. Not every (claimType, keyType) pair is accepted: OWNERSHIP is claimable on PHONE only; PORTABILITY is claimable on CPF, CNPJ, PHONE, or EMAIL; EVP is claimable on neither.
CPF, CNPJ, EMAIL, PHONE, EVP "PHONE"
PIX key value being claimed (format depends on keyType: CPF, CNPJ, EMAIL, PHONE, or EVP). At most 77 characters, the ceiling BACEN publishes on a DICT key; the per-type shape is applied by the service, since one schema pattern cannot depend on keyType.
1 - 77"+5511999999999"
Claimer account branch (1..4 digits), optional.
"0001"
Claimer trade name (legal-entity claimers), optional.
"Silva ME"
Response
Created
Claim record with its current status and deadlines
Claim kind: OWNERSHIP or PORTABILITY
"OWNERSHIP"
ISPB (8 numeric digits) of the participant initiating the claim
"12345678"
Donor-response deadline (RFC 3339, UTC). For a claim BACEN's own record backs (discovered or adopted), this IS BACEN's ExtendedClaim.ResolutionPeriodEnd, same value as resolutionPeriodEnd below. For a locally-initiated claim, this is always a local seven-day-from-initiation estimate that drives the deadline sweep — see resolutionPeriodEnd for BACEN's own authoritative value, populated once the initiation outbox handler decodes BACEN's createClaim response.
"2025-03-14T14:30:00Z"
Server-assigned claim UUID
"550e8400-e29b-41d4-a716-446655440000"
PIX key type: CPF, CNPJ, EMAIL, PHONE, or EVP
"PHONE"
PIX key value under claim
"+5511999999999"
Claim lifecycle state: OPEN, WAITING_RESOLUTION, CONFIRMED, CANCELLED, or COMPLETED
"OPEN"
BACEN's own operational envelope for its most recent interaction on this claim; omitted when no BACEN interaction has ever landed on it.
The id BACEN itself assigned to this claim on createClaim (ExtendedClaim.Id) — the address every BACEN-facing verb and both claim-recovery feeds use internally. Read-only, surfaced so an operator can correlate a BACEN support case or a DICT-side rejection back to this claim. Omitted until BACEN's createClaim response has landed: a locally initiated claim whose initiation outbox handler has not yet processed BACEN's reply carries no value here yet.
"550e8400-e29b-41d4-a716-446655440111"
Matches BACEN's ExtendedClaim.CancelReason vocabulary plus COURT_ORDER: the reason the claim was cancelled, once cancelled. On a claim we cancel ourselves (our own cancel verb) this is the reason our own operator submitted; on a claim discovered or adopted from BACEN's directory it is BACEN's own published value, verbatim. COURT_ORDER is the one value BACEN does not define at the pinned DICT 2.12.1: it is recorded locally on a court-ordered cancellation, and that cancellation reaches BACEN carrying USER_REQUESTED until the DICT reaches 2.13, which adds the value to ClaimOperationReason
USER_REQUESTED, ACCOUNT_CLOSURE, FRAUD, DEFAULT_OPERATION, RECONCILIATION, RFB_VALIDATION, PARTICIPANT_EXCLUSION, COURT_ORDER Matches BACEN's ExtendedClaim.CancelledBy vocabulary: the side that cancelled the claim, once cancelled. On a claim we cancel ourselves this is the side derived from the authenticated caller; on a claim discovered or adopted from BACEN's directory it is BACEN's own published value, verbatim
DONOR, CLAIMER Number of the account the claimed key would move to (ExtendedClaim.ClaimerAccount.AccountNumber). Answered on every claim projection, the list included
"9988776"
Type of the account the claimed key would move to (ExtendedClaim.ClaimerAccount.AccountType). Answered on every claim projection, the list included
CACC, SVGS, TRAN, SLRY, OTHR "CACC"
Branch of the account the claimed key would move to (ExtendedClaim.ClaimerAccount.Branch); optional at BACEN, so empty when the claimer lodged none. Answered on every claim projection, the list included
"0001"
Name of the claiming key owner (ExtendedClaim.Claimer.Name). Answered on every claim projection, the list included; not carried on a claim streaming fact
"João Silva"
Opening date of the account the claimed key would move to (ExtendedClaim.ClaimerAccount.OpeningDate, RFC 3339 UTC). Answered on every claim projection, the list included
"2020-01-15T00:00:00Z"
CPF/CNPJ of the claiming key owner (ExtendedClaim.Claimer.TaxIdNumber). Answered on every claim projection, the list included; not carried on a claim streaming fact
"11122233300"
Trade name of the claiming key owner (ExtendedClaim.Claimer.TradeName); legal-entity claimers only, empty for a natural person. Answered on every claim projection, the list included
"Silva ME"
BACEN's Person discriminator for the claiming key owner (ExtendedClaim.Claimer.Type). DERIVED from the tax id's length, never stored: 11 characters is the CPF branch, 14 the CNPJ branch — the same rule BACEN's own oneOf keys on. Empty when the tax id is absent or has no branch. Answered on every claim projection, the list included
NATURAL_PERSON, LEGAL_PERSON "NATURAL_PERSON"
BACEN's own completion-window end for a possession claim (ExtendedClaim.CompletionPeriodEnd, RFC 3339 UTC); BACEN publishes it for OWNERSHIP claims only and omits it for PORTABILITY. Also omitted whenever BACEN has not published this claim yet.
"2025-03-21T14:30:00Z"
Matches BACEN's ExtendedClaim.ConfirmReason vocabulary: the reason the donor confirmed with, once confirmed — unlike resolution this is NOT terminal-gated and is never cleared by a later transition. On a claim we confirm ourselves (our own respond verb) this is the reason our own operator submitted; on a claim discovered or adopted from BACEN's directory it is BACEN's own published value, verbatim
USER_REQUESTED, ACCOUNT_CLOSURE, FRAUD, DEFAULT_OPERATION, RECONCILIATION, RFB_VALIDATION, PARTICIPANT_EXCLUSION ISPB (8 numeric digits) of the current key owner (donor). It is the DICT that resolves the donor, not this rail: a claim lodged on a key held at another institution — the canonical portability case — carries NO donor until BACEN's createClaim response names one (ExtendedClaim.DonorParticipant), so this field is omitted while the donor is pending. A donor-side claim discovered from BACEN's directory always carries it.
"87654321"
BACEN's own last-transition instant for this claim (ExtendedClaim.LastModified, RFC 3339 UTC) — the version discriminator BACEN publishes, distinct from requestedAt (when WE lodged it) and from resolvedAt (when it ended). Present once BACEN's own record for this claim exists; omitted before that.
"2025-03-07T14:30:00Z"
Claim initiation timestamp (RFC 3339, UTC); omitted for a donor-side claim projected from BACEN, whose ExtendedClaim carries no creation time
"2025-03-07T14:30:00Z"
Terminal resolution reason (e.g. CANCELLED_BY_CLAIMER, CANCELLED_BY_CLAIMER_FRAUD, CANCELLED_BY_DONOR, CANCELLED_BY_DONOR_FRAUD, DEADLINE_EXPIRED, AUTO_COMPLETED, TRANSFER_COMPLETED); empty until the claim resolves — CONFIRMED is not terminal and never sets this field
""
BACEN's own resolution-window end for this claim (ExtendedClaim.ResolutionPeriodEnd, RFC 3339 UTC); present once BACEN's own record for this claim exists — discovered, adopted, or a locally-initiated claim whose createClaim response the initiation outbox handler has processed — omitted before that
"2025-03-14T14:30:00Z"
Resolution timestamp (RFC 3339, UTC); omitted while the claim is unresolved
""

