Changelog

​

Bulk automatic entity import — child enrichments & monitoring scope

• childEnrichmentPolicy: all_active (default), by_root_type, or basic_only.
  • by_root_type: company rows run all active enrichments on shareholders except global_gueno_sanctions_enrichment; person rows create related entities with basic data only from the root provider snapshot.
• monitoringApplyToRelationships: when false, monitoring applies to main entities only (no watchlist on children). Default true when depth > 0 if omitted.

​

Marketplace enrichment — structured errors

​

Automatic / bulk entity creation — tax ID strictness

​

Transactions — optional exchangeRate fallback

​

POST /entities/{entityId}/refresh — unified scope and safe field sync

• refreshScope: basic_data | all_active | selected (+ providerCodes when selected).
• preserveName: true keeps the current display name; omitted = legacy sync from normalized fullName.
• preserveEntityData: only with refreshScope: "basic_data" — true gap-fills entityData, false replaces; omitted = do not touch profile.

​

GUENO_CROSS_ENTITY_DUPLICATED warning

• Appends warning GUENO_CROSS_ENTITY_DUPLICATED to session validation warnings.
• If the provider mapped approved, Gu1 sets status to in_review (metadata.guenoCrossEntityDuplicateEscalation).
• Non-omittable: cannot be sent in omitWarnings (400) and blocks omit auto-approve.

​

Gu1 Biometric (POST /api/kyc/biometric and /api/kyc/biometric/sessions)

​

decision always includes array + object feature pairs

• id_verification ↔ id_verifications[0]
• liveness ↔ liveness_checks[0]
• face_match ↔ face_matches[0]
• aml_screening ↔ aml_screenings[0]
• ip_analysis ↔ ip_analyses[0]

​

Per-run rules engine config on POST /entities/{entityId}/analyze

• partialCoverage: with multiple assigned matrices, data coverage is validated per matrix; matrices without data are skipped (matricesSkippedForCoverage / warnings on partial success).
• omitCoverage: skip data coverage gates entirely (main entity + shareholders). Precedence over partialCoverage when both are true.

​

ejemplar in extractedData

​

RENAPER double-check on KYC validations

​

Marketplace *_check product removed

• Removed: all *_check provider codes, POST /integration-execution/marketplace/check, rules triggers/actions check_completed / execute_check, and RBAC permissions checks:read / checks:execute.
• Use instead: matching *_enrichment codes with Execute enrichment.
• Backward compat: legacy create/import payloads with checks, executeAllActiveChecks, or *_check inside autoExecuteIntegrations.enrichments are silently ignored at parse time.

​

Stable batch failure codes and JSON endpoints

• Row failures now include stable code + message (catalog: Failure codes). CSV adds a code column (external_id,code,error / row_key,code,error / entity …,code,error_message).
• New JSON endpoints: GET /batch-import/transaction-jobs/{jobId}/failures, GET /batch-import/user-event-jobs/{jobId}/failures, GET /batch-import/entity-jobs/{jobId}/failures — include failures[], optional jobFailure for whole-job errors, entity skips[], truncated / failuresTotal (max 500 stored).
• CSV download: same routes with .csv suffix (failures.csv).
• Legacy rows with only free-text error are normalized on read when possible.

​

Assign risk matrices on entity update

• PATCH /entities/{id} (and PATCH /entities/by-external-id/{externalId}, PATCH /entities/by-tax-id/{taxId}): document riskMatrixIds (string[]) and riskMatrixId (string | string[] | null) — same normalization as create. Assigns matrices on the entity; does not run the rules engine (use Analyze entity or lifecycle triggers).
• Mintlify updated in /en/, /es/, /pt/ on Update entity and Update by external ID.

​

configRulesExecution on create transaction

• POST /transactions: optional body object configRulesExecution with notifications (boolean). When false, gu1 skips in-app notifications from rules evaluation (risk matrix / status). createAlert actions and investigations are unchanged.
• Default: omitting the object keeps prior behavior for most orgs (notifications effectively true). Paytime prod (3bc1f621-27d4-423e-9d64-86680bec2388) defaults to notifications: false when omitted.
• Legacy KYT POST /legacy/kyt/verifyTransaction: same field on the Gu2 body; Paytime prod default notifications: false when omitted (normalized before create).
• Applies to sync and async rules (asyncRules).

​

POST /transactions and batch create — linked counterparty fields

• originTaxId / destinationTaxId ← entities.tax_id
• originExternalId / destinationExternalId ← entities.external_id

​

POST /events/user — isNewDevice honors integrator value

• If you send isNewDevice: true or false, gu1 persists exactly that value (no server override).
• If you omit the field, gu1 infers it when deviceId + deviceDetails are present (device registry; true when the device is new or firstSeenAt is within the last 5 minutes); otherwise false.

​

Platform CSV: attributes.* and entityData.*

• Dotted headers (same approach as native transaction CSV): attributes.segment_tag, entityData.income, entityData.tradeName.
• entityData.<field> without person/company uses the row type bucket.
• Unprefixed columns (segment_tag) still map to attributes (backward compatible).
• See Import entities (CSV).

​

Import limits documented (en / es / pt)

• Bulk imports overview: matrix of max files per request, max rows by plan, and manual vs automatic entity import.
• Per-endpoint pages now include limits: Import entities (CSV), Import transactions, Import user events.
• CSV entity import uses plan limits (4k–100k). Runtime caps: GET /individual-organization/batch-upload-enabled.

​

Bulk entity import countries (manual vs automatic)

• Manual (manual): any valid platform ISO2 (batch or per-row country / country_code).
• Automatic (automatic): AR, BR, and CL (basic data by tax ID, including Chile ruts.info / BaseAPI enrichments).
• Applies to POST /batch-import/import/entities (platform CSV and custom CSV with mappingId).

​

POST /batch-import/import/entities — manual mode enrichments

• Manual multipart now matches the dashboard Manual hub mode: optional autoExecuteIntegrations, monitoring, and risk matrices — without the country basic-data pipeline (Nosis/CPF).
• CSV-only upload (no autoExecuteIntegrations) still creates minimal entities with no enrichments.
• Per-row CSV enrichment columns apply in manual mode; depth / shareholders remain automatic-only.

​

POST /batch-import/import/entities — manual default

• Omitting entityImportMode → manual (minimal entity; enrichments only when explicitly requested).
• Automatic with entityImportMode=automatic (+ optional autoExecuteIntegrations, depth, etc.).
• Manual mode requires suggested_name on every row (400 if missing).
• Template bulk-entities-template.csv: documented columns; demo row without active enrichments.
• 202 response includes effective importMode.

​

POST /batch-import/import/entities — platform format

• mappingId optional for platform CSV headers. Import default: manual (see next changelog entry on this date).

​

asyncRules on create transaction

• POST /transactions: optional query or body flag asyncRules (default false). When true and executeRules is not false, the transaction is created in the same request but rules run in the background via a job queue. The HTTP response returns immediately with empty rulesHit / rulesNoHit, plus asyncRules: true and rulesEvaluationStatus: "queued".
• Default unchanged: omitting asyncRules keeps synchronous rules execution and a full rulesExecutionSummary — existing clients behave exactly as before.
• Legacy KYT POST /legacy/kyt/verifyTransaction: same flag via query or Gu2 body field. Paytime prod (3bc1f621-27d4-423e-9d64-86680bec2388) defaults to async when the flag is omitted; use asyncRules=false to force synchronous rules for a single request.
• Not on batch endpoints. If Redis/queue is unavailable, API may return 503 ASYNC_RULES_QUEUE_UNAVAILABLE (transaction may already exist — check response body before retry).

​

RENAPER double-check on standalone KYC endpoints

• POST /api/kyc/face-match: optional doubleCheckRenaper (body or ?doubleCheckRenaper=true). After Gu1 face match approves, runs RENAPER biometric (validate-dni with selfie) and data (DNI + trámite). Requires documentNumber, gender, and personalNumber (or entity fallback for DNI/gender). Response adds responseDoubleChecks.renaper (including nested renaperBiometric when biometric check runs).
• POST /api/kyc/id-verification: same flag; after OCR approval runs RENAPER data check only (fields from extractedData). Failed checks set status to declined and add RENAPER codes to warnings.
• Org RENAPER credentials required (same as session KYC). Use HTTP timeout ≥ 60s for face-match with double-check.

​

KYT — separate status-change vs field-update triggers

• PATCH …/changeStatus now runs rules/matrices with trigger status_changed (trigger_transaction_status_changed), not updated.
• PATCH /transactions/{id} (metadata, deviceDetails, channel, reason) with executeRules=true still uses updated (trigger_transaction_updated).
• Migration: reconfigure rules that must run on status transitions to the new trigger (Rule Builder: On transaction status change; matrices: transaction_status_changed). Rules with only updated / Transaction updated no longer run on changeStatus.

​

Partial transaction update

• PATCH /transactions/{id} and PATCH /transactions/external/{externalId}: update metadata (shallow merge — omitted keys are preserved), deviceDetails (shallow merge into device_details), channel (nullable), and/or reason (enum). Requires transactions:edit.
• Query executeRules=true optionally re-runs KYT rules with trigger updated (trigger_transaction_updated) — not status-change rules.
• Emits audit transaction_updated and webhook transaction.updated with a changes map (includes deviceDetails when patched).

​

User events — has-events by external ID or tax ID

• GET /events/user/entity/has-events (new): boolean check without the internal entity UUID. Query params: entity_id, entity_external_id, or tax_id (at least one required). Lookup priority: entity_id → entity_external_id → tax_id; tax IDs are matched with normalization (non-alphanumeric stripped).
• Response still includes resolved entityId so you can call List by Entity when hasEvents is true.
• GET /events/user/entity/{entityId}/has-events remains supported (unchanged contract).

​

Session KYC — Device & IP analysis warnings

• GET /api/kyc/validations/:id (and sync/webhook paths): the top-level warnings array now merges risk codes from decision.ip_analyses[].warnings[] (and legacy decision.ip_analysis.warnings), alongside ID verification, liveness, face match, and AML.
• Eight provider codes are supported (e.g. PRIVATE_NETWORK_DETECTED, DUPLICATED_DEVICE_FINGERPRINT, IP_ADDRESS_IN_BLOCKLIST). See KYC Warning Risk Codes — Device & IP Analysis.
• The same codes are valid in omitWarnings on POST /api/kyc/validations when auto-approving in_review sessions.

​

ID Verification — richer extractedData

• POST /api/kyc/id-verification and audit list/get now persist and return a broader extractedData object: identity fields (personalNumber, taxNumber, placeOfBirth, …), providerStatus, warningMeta (e.g. duplicate session IDs), quality scores, extraFields, mrz, parsedAddress, barcodes when returned by the Gu1 ID Verification service.
• warnings remains a string array of risk codes for i18n; use warningMeta inside extractedData for structured duplicate-session metadata.
• External document image URLs and base64 are not returned; images you uploaded are available via ID Verification images.
• debugProviderResponse may appear only in non-production Gu1 API environments (sanitized verification payload, no images).

​

operational hours per entity (global)

• Entities: Optional root field operationalHours (timezone enum + weekly slots). Stored in entities.operational_hours. Documented on Create entity and related entity endpoints.
• Transactions: transaction_time_zone enum extended (Brazil zones). Optional timeZone is independent of entity operationalHours. transactedAt: stored as UTC; ISO with Z unchanged for existing clients; optional local datetime + timeZone converts to UTC when both are sent.
• Rules: New operators outside_entity_operational_hours and inside_entity_operational_hours on transactedAt with value origin or destination. Requires operationalHours on the linked entity.

​

timeZone on transactions

• Database: New nullable column time_zone on transactions with enum type transaction_time_zone (IANA values such as America/Argentina/Buenos_Aires, UTC, etc.). Existing rows remain null.
• API: Optional timeZone on POST /transactions and batch create; returned on GET /transactions/{id} and GET /transactions/external/{externalId} as string | null.

​

validateExistingEntity (transaction create)

• POST /transactions: optional validateExistingEntity (default false). When true, every origin/destination identifier you send must resolve to an existing person/company; otherwise 400 INVALID_ENTITY_REFERENCES and no row is created.
• Batch endpoints: default remains true. Use validateExistingEntity: false for permissive bulk import.
• Legacy KYT POST /legacy/kyt/verifyTransaction: same field in the Gu2 body.

​

excludeEnrichments on entity creation

​

New: Hosted Onboarding Page Documentation

​

What’s New

• ✅ Complete customization parameters guide (branding, colors, layout)
• ✅ Validation rules configuration (age verification, capture methods, duplicate detection)
• ✅ Document validation rules (QR/barcode, MRZ, expiration dates, liveness)
• ✅ Step-by-step integration guide with code examples
• ✅ Visual flow diagram showing the complete process
• ✅ Security best practices for session management
• ✅ Mobile-responsive design confirmation

• 📱 Mobile-responsive design for all devices
• 🎨 Full customization of colors, branding, and layout
• 🔒 Comprehensive security guidelines
• 📊 Visual sequence diagrams for clarity
• 🌐 Support channel information for configuration changes

​

Languages

• 🇺🇸 English
• 🇪🇸 Español
• 🇧🇷 Português

​

Impact

• Faster implementation for no-code solutions
• Clear guidance on customization options
• Enhanced security awareness
• Better understanding of the hosted page workflow

​

KYC Pages Refinement Based on Client Feedback

​

What’s New

• ✅ Added comprehensive comparison table: Automatic vs Manual creation
• ✅ Complete Risk Matrix configuration guide with dashboard instructions
• ✅ Clarified shareholders feature (KYB only, not KYC)
• ✅ Provider codes reference with usage examples
• ✅ Detailed credit management section with costs and workflows

• ✅ Webhooks vs manual polling explanation
• ✅ Full KYC vs Individual Verifications comparison table
• ✅ Comprehensive face matching security warning for banks/fintech
• ✅ Enhanced API endpoints table with use cases

• ✅ Complete sequence diagram showing full flow
• ✅ Sandbox vs Production clarification
• ✅ Duplicate entity handling with code examples
• ✅ Expanded integrationCode documentation

• ✅ Marked optional fields with examples (attributes, entityData)
• ✅ Minimal vs full entity creation examples

​

Languages

• 🇺🇸 English
• 🇪🇸 Español
• 🇧🇷 Português

​

Impact

• 14 client questions answered inline
• 12 documentation files updated
• 0 broken links
• Improved developer onboarding experience

​

Enhanced Multi-language Documentation

​

Changes

• Complete translation coverage for KYC, KYB, and Transaction Monitoring
• Consistent terminology across all languages
• Language-specific examples (CPF for Brazil, DNI for Spain, etc.)

​

Available Languages

• English (EN) - Primary
• Spanish (ES) - Complete
• Portuguese (PT) - Complete

​

gu1 Documentation Launch

​

Core Features

• Complete API reference for all endpoints
• Use case guides (KYC, KYB, Transaction Monitoring)
• Webhook integration guides
• Interactive tutorials
• Multi-language support

​

Components

• Person entities API
• Company entities API
• KYC validation workflows
• Transaction monitoring
• Rules engine
• Risk matrices
• Alerts and investigations