Skip to main content

Documentation Index

Fetch the complete documentation index at: https://developer.tazapay.com/llms.txt

Use this file to discover all available pages before exploring further.

Release Type: Enhancement

​
Summary

Duplicate detection for entity creation now excludes rejected entities from comparison. If an entity was previously rejected, it is no longer considered when evaluating whether an incoming request is a duplicate. A new entity will be created instead.

​
How It Works

Previously, idempotency checks compared incoming requests against all existing entities, including those that had been rejected. This caused requests to be incorrectly matched against rejected entities, blocking new entity creation. With this change, rejected entities are excluded from the duplicate comparison. If no non-rejected entity matches the incoming request, it is treated as new and a fresh record is created.

​
Behavior

ScenarioBehavior
Incoming request matches an existing non-rejected entityReturns existing entity with HTTP 200 OK
Incoming request matches only rejected entitiesCreates a new entity

​
Affected Endpoints

  • POST /v3/entity — duplicate detection applied on creation
  • PUT /v3/entity/{id} — duplicate detection applied on update
  • POST /v3/entity/{id}/submit — duplicate detection applied on submission
  1. Entity API Documentation