Documentação

English

Português
Español

English

Português
Español

Appearance

Parties (Originator / Debtor / Investor) ​

Access Prerequisites

  • Permission (module): viewCredits (list/view). Approving/rejecting KYC uses the same credit management permission of the tenant.
  • License/Feature: CREDIT_INVESTMENTS enabled in the tenant license (Vault).
  • Menu container: TOKENIZATION → group Tokenized Credit

What it is / when to use ​

The Parties screen registers and governs the participants of tokenized credit: Originators, Investors and Debtors. Each party carries a document (CPF/CNPJ), address, KYC status, BaaS account status and risk attributes (score, credit limit, defaults) that feed the Credit Policies.

Use this screen to review and approve/reject parties after KYC, before they can originate, invest or appear as debtor in an operation.

Prerequisites ​

  • Permission: viewCredits registered for the operator role (double permission — CPM enum on the backend + dynamic module in the DB).
  • License/Feature: CREDIT_INVESTMENTS enabled. If disabled, the group does not appear in the menu at all.
  • Dependencies on other screens: none; however, parties must exist and be approved before being used in Deals.

Step by step ​

  1. Access the menu Tokenized Credit → Parties.
  2. Filter by Type (Originator / Investor / Debtor / All) and Status.
  3. Use the search to locate by name/document.
  4. Open the party (row or ⋮ → View) to check KYC, address and risk attributes.
  5. For pending parties, use ⋮ → Approve or ⋮ → Reject (with confirmation).

Filters and columns ​

Filter/ColumnWhat it showsData source
NameCompany name / party nameParty.name
TypeORIGINATOR, INVESTOR or DEBTORParty.type (filter typeFilter)
DocumentCPF/CNPJParty.documentNumber + documentType
StatusPENDING_KYC, KYC_APPROVED, KYC_REJECTED, ACTIVE, SUSPENDED, PENDING_APPROVAL, APPROVED, REJECTEDParty.status (filter statusFilter)
KYC StatusKYC result of the partyParty.kycStatus
BaaS AccountStatus of the associated bank accountParty.baasAccountStatus
Created atRegistration dateParty.createdAt

Risk attributes visible in the detail view (not in the list, but used by Policies): riskScore, creditLimit, usedCredit, kycScore, defaultCount, totalDeals, totalVolume, riskRating.

Actions and modals ​

  • View: opens the party details (credit-parties/view/:id).
  • Edit: opens the form (credit-parties/edit/:id).
  • Create: registers a new party (credit-parties/create).
  • Approve: approveParty(id) after confirmation (bottom-sheet) — releases the party to operate.
  • Reject: rejectParty(id) after confirmation — blocks the party.

Approving/rejecting parties may trigger step-up (password + MFA, X-Step-Up-Token, 5-minute window) depending on the environment — identity reconfirmation, not 4-eyes approval.

Business rules / notes ​

Attention

  • Status governs usage. Originator/investor can only participate in an operation if approved; disbursement to the originator requires an active BaaS account and a compatible status.
  • Risk attributes feed the Policies. riskScore, defaultCount, creditLimit/usedCredit are read by Policies with PARTY scope on deal/receivable approval — keep them up to date.
  • Debtor (DEBTOR) is the one who pays the Charge; register them correctly so the receivable→charge link works.
  • Financial values: creditLimit, usedCredit and totalVolume represent amounts treated as BigNumber on the backend — do not round when setting limits.
  • Status APPROVED: downstream financial operations require the party to have approved status.