ReconId Update in iPOS Transact API

ReconId Update in iPOS Transact API

The iPOS Transact API now supports the updated ReconId field naming convention, replacing the legacy reconciliationId field to align with the SPIn system naming standards and improve transaction consistency across integrations.

What’s New

  • Renamed the reconciliationId field to ReconId in the iPOS Transact API
  • Increased ReconId field length support from 10 to 30 characters
  • Added support for ReconId mapping in transaction requests
  • Unified field naming across transaction flows
  • Added validation and trimming support for ReconId values exceeding the supported length

Where It Works

  • iPOS Transact API
    • Credit Card Sale Transactions
    • Pre-Authorization Transactions
    • Ticket Transactions
    • Refund

Behavior

ConditionResult
ReconId is providedValue is passed in the transaction request
ReconId exceeds the supported lengthValue is trimmed before processing
ReconId is empty or unavailableDefault invoice or batch number is used based on processor configuration
Special characters in ReconIdNot supported in transaction mapping
Existing transaction processingBehavior remains unchanged

Supported Scenarios

  • Sale transactions with ReconId
  • Pre-Authorization transactions with ReconId
  • Ticket transactions using ReconId mapping
  • Transactions without ReconId fallback handling
  • ReconId trimming for longer values

This enhancement improves the consistency of transaction reconciliation and ensures standardized ReconId handling across supported transaction flows.

Developer Documentation

For complete API details, including request and response structures, refer to:

iPOS Transact API
Bug Fixes