Planned Backwards Compatibility Changes
  • 16 Feb 2024
  • 1 Minute To Read
  • Dark
    Light
  • PDF

Planned Backwards Compatibility Changes

  • Dark
    Light
  • PDF

Article Summary

ChangeEndpoint affectedReference IDBackwards compatible until
We are introducing limits to custom field definitions and custom field values. This limitation only applies to the number of custom fields values linked to an entity (the actual value it holds. I.e. “Zimbabwe”), and not to the number of custom fields definitions (the custom field you create. I.e. “Country of Residence”).For more information, see Custom Fields-March 2024
We will be issuing the Accounts Updated event when all the accounts have been updated. Previously the Account Updated event coincided with the completion of the end-of-day job. This unnecessarily prolonged the notification due to the inclusion of jobs unrelated to updating the accounts status. The completion of the daily job can be observed by querying the Background Process endpoints for the state of the CRON_JOBS job.For more information, see End of day processing.EOD-90January 2024
We are removing the hold check when posting card transactions where the state of the referenced authorization hold is other than Pending (Settled, Reversed, or Expired). Once posting a card transaction, the state of such a hold will not be changed and the transaction will be successfully posted.POST /cards/{cardReferenceToken}/financialtransactionsCARDS-1670July 2023
Whenever a credit transaction is reversed and funds are not available as part of the deposit account total balance, a reversal debit transaction will be executed using the technical overdraft of that account.POST /cards/{cardReferenceToken}/financialtransactions/{cardTransactionExternalReferenceId}:decreaseCARDS-1768July 2023

See Past Backwards Compatibility Changes for historic changes.


Was this article helpful?