Appearance
Latest content updates
Stay informed about the latest improvements to the Treezor documentation. This page tracks major documentation changes and additions over the last 3 months.
Please note that these updates are not exhaustive. Are included:
- Major content additions and rewrites.
- New articles and endpoints (feature integration guides).
- Significant updates to the API References.
October 23, 2026
New Card Transactions – Retrieve enrichment data endpointAdded the GET /v1/cardtransactions/{cardtransactionId}/enrichment endpoint to retrieve the full enrichment payload for a card transaction, including merchant details, category, CO2 emissions data, and ESG information.
Links: Card Transactions article | /v1/cardtransactions/{cardtransactionId}/enrichment endpoint
Updated the Parent-Children relations page to mark it as legacy and indicate that the parentUserId, parentType, controllingPersonType, effectiveBeneficiary, and employeeType fields are scheduled for deprecation. Added a redirect to the Relationships system.
Links: Parent-Children relations article | Relationships article
The endpoint for reusing an identification made with a verification solution was documented as POST /v1/users/copy. The correct path is POST /v1/users/kycliveness/copy. This issue has been fixed.
Links: User verification Introduction article | /v1/users/kycliveness/copy endpoint
October 16, 2026
Update Account Statements – Quarterly, semestral, and annual statement periodsAdded support for quarterly, semestral, and annual account statements on the GET /core-connect/statements/{walletId}/raw and /computed endpoints. The month parameter is now conditional; provide year alone for an annual statement, or combine it with the new quarterly (1–4) or semestral (1–2) parameters. The requested period must be entirely in the past.
Links: Account documents article | /core-connect/statements/{walletId}/raw endpoint | /core-connect/statements/{walletId}/computed endpoint
Added support for quarterly, semestral, and annual operation simulation periods on the POST /simulation/operations endpoint. The existing date parameter is retained for monthly simulation; new year, quarterly, and semestral parameters allow simulation over longer periods. Uniqueness is verified month by month across the full requested period.
Links: Wallet simulation article | /simulation/operations endpoint
relationshipTypeOrder parameter on GET endpoint Added the relationshipTypeOrder query parameter to the GET /v1/users/{userId}/relationships endpoint. This parameter accepts a comma-separated list of relationshipTypeId values and returns matching relationships first, in the specified order. It cannot be combined with groupBy. New business error codes 174020, 174021, and 174022 are documented in the error codes reference.
Links: User Relationships article | Error codes article | /v1/users/{userId}/relationships endpoint
Updated the documentation for the PUT /v1/users/{userId}/relationships/{relationshipId} endpoint to clarify that only Beneficial Owner relationships (EFFECTIVE_BENEFICIARY_SHARES, type 2) can be updated. Any other relationshipTypeId value passed in the request body is silently ignored, and the relationship targeted by the path must be of type 2.
Links: User Relationships article | /v1/users/{userId}/relationships/{relationshipId} endpoint
October 9, 2026
Fix Cards – 3DS authentication result delayThe note on the 3DS authentication page incorrectly stated a 5-minute delay (configurable) to provide the authentication result to Treezor. The actual delay is 9 minutes and 30 seconds (fixed). This issue has been fixed.
Links: Transactions authentication article
Deprecated the GET /customization/templates/{templateName}/example endpoint. This endpoint will not be available in future versions.
Links: Templates article | Build Template Example endpoint
Added documentation for the 3 Tax Residence webhook events: taxResidence.create, taxResidence.update, and taxResidence.cancel. These webhooks are sent when a Tax Residence is created, modified, or deleted.
Links: Tax Residence events article
October 2, 2026
Fix API Reference – Scope correctionsFixed incorrect scope definitions across multiple endpoints in the API Reference. Some endpoints had scopes that were more permissive, more restrictive, or different from the actual API behavior. This issue has been fixed.
Links: API Endpoints endpoints
The user.relationship.create and user.relationship.cancel webhook payloads incorrectly documented relationTypeId and relationTypeName attributes. The correct attribute names are relationshipTypeId and relationshipTypeName. This issue has been fixed.
Links: User relationship events article
September 18, 2026
New Approval requests – Dedicated documentation pageAdded a dedicated Approval requests page with configuration screenshot and detailed workflow explanations.
Links: Approval requests article
Added Declaring sections with examples and use cases for COMPANY_REPRESENTATIVE, EMPLOYEE, and CHILD user relationships.
Links: User Relationships article
Added documentation for VoP reception KYC rules aligned with the new KYC lifecycle model.
Links: Beneficiaries – Received VoP article
Added 6 missing endpoints to the API Reference: SCA simulation endpoints and cross-device SCA flow endpoints.
Links: SCA endpoints
Restructured KYC articles to prioritize New KYC over Legacy. Added deprecation notices to legacy sections.
Links: KYC Introduction article | KYC Request article
Clarified userTypeId usage with concrete examples for business entities (EURL as type 1) and governmental organizations.
Links: Users Introduction article
August 28, 2026
New Acquiring – Additional Data fieldAdded documentation for the additionalData field, containing transaction information returned by HiPay for reconciliation purposes.
Links: Acquiring Introduction article
Added documentation for the Payment Initiation Service Provider (PISP) feature, allowing you to initiate payments from external bank accounts via Open Banking.
Links: Open Banking article
Added documentation for the Proof of Operation feature, allowing you to generate PDF documents for operations.
Links: Proof of Operation article
Added the PUT /v1/users/{userId}/user-relationships/{id} endpoint to update existing user relationships.
Links: User Relationships article | User Relationships endpoints
Updated the KYC onboarding workflow diagram to reflect the current process.
Links: KYC Request article
Added missing webhook_created_at and object_payload_signature fields to 10 transfer webhook payloads.
Links: Transfer Events article
July 31, 2026
New Cards – Card User Bulk CreationAdded documentation for the Card User Bulk Creation feature, allowing you to create users and cards in bulk from a CSV file.
Links: Creating Users and Cards from CSV article | Card User Bulk Creation endpoints
Added documentation for the Google OPC (Opaque Payment Card) flow, required for in-app provisioning with Google Pay. Migration deadline is December 31, 2026.
Links: Google OPC flow article
transactionId field Added the transactionId field to the Operation object, allowing you to retrieve the unique identifier of the transaction associated with a settled operation.
Links: Operations article | Operations endpoints
Added the GET /v1/users/kyc endpoint to search and retrieve KYC information for multiple users.
Links: User Verification article | User KYC Review endpoints
Deprecated the GET /core-connect/cardtransactions and GET /core-connect/cardtransactions/{cardId} endpoints. Use GET /v1/cardtransactions instead.
Links: Card Transactions article | Card Transactions endpoints
Clarified that SMS OTP enrollment is optional for card authentication. Only Out of Band (OOB) enrollment is mandatory to accept secure online payments.
Links: Card authentication methods enrollment article
The objectId field description incorrectly stated it returned the cardTransactionId for card transactions. It actually returns the paymentId. Use the /v1/cardtransactions endpoint with the paymentId to retrieve associated card transactions.
Links: Operations article | Operations endpoints
The sourceAmount and targetAmount fields in the /v1/quote endpoints were documented as string instead of number. This issue has been fixed.
Links: International transfers article | Foreign Currencies endpoints