← Back to Home All Posts

API Modernization

DDA API Migration: V2 to V3

An Urgent Priority for Aggregators to Enhance Stability & Performance

March 12, 2025 7 min read

Urgent: Why Migrate Now?

Critical Stability Vulnerability

API v2 has a major flaw: when the Cassandra database slows, v2 API threads hang while fetching enrichment data. This leads to 500 errors and significant customer impact, even for aggregators who don't use the data.

V3 Is the Standard

API v3 resolves this vulnerability. All other digital channels have already migrated. V2 is a frozen legacy version and will not receive future updates or fixes.

Benefits of Upgrading to V3

  • Eliminate Risk: Immediately fix the critical thread-hanging vulnerability causing 500 errors.
  • Align with Digital Channels: Achieve parity with the current, supported API version used across the firm.
  • Enhanced Capabilities: Support for Unique Location ID (ULID), standardized transaction types, and improved field consistency.
  • Smoother Integration: Cleaner, more consistent field names reduce future rework and simplify development.

Key API Changes: V2 vs. V3

Field Name Updates

Names have been updated for clarity and consistency.

v2: postingSequenceNumber

v3: monetarySequenceNumber

v2: expenseCategoryCode

v3: etuStdExpenseCategoryCode

New Mandatory Parameter

Required for GLB isolation.

v3: network-channel-group-code

ENUM Value Changes

Expense categories have been standardized and consolidated.

v2: FUNE (Fun & Entertainment)

v3: ENTT (Entertainment)

v2: TRSP (Transportation)

v3: Deleted (merged with Travel)

New Fields & Parameters

Added to support new features and filtering.

  • etuStdTransactionGroupName
  • totalPendingTransactionCount
  • feeSequenceNumber