1.2 ECA and EA Validations
- Payload - the Payload is validated for the correctness of every tag and its value.
- Account (EAC checks) - the account related validations for the upcoming debit/credit are performed. The account's statuses such as No_Credit, No_Debit, Inactive, or Dormant are checked. In case of a multicurrency account, the sub-account pertaining to the passed currency is resolved and used in transaction processing. The account related validations for the external transactions is performed based on the request (for Debit/Credit Indicator) and a response is sent to the external system.
- Customer - For every transaction, the customer is validated for Frozen, Bankrupt or Whereabouts Unknown.
- Balance and Limit - the account balance is validated for every debit transaction. While checking for account’s sufficient funds for the debit transaction to go through, in case the account does not have sufficient balance, TBS checks for Internal limit which includes Advance against Uncollected Funds, Daylight, Temporary Overdraft and External Limit which includes RTL and ELCM utilization.
Post a successful validation for the debit transaction, the amount is blocked in the account and a response is sent to the external system. Transactions from external system is carried out in two steps, direct EA call or by an ECA request followed by an EA request.
ECA Block
This stage is used to perform account related validations and balance checks for the upcoming external debit transactions. The various checks are -
- Account related validations for the debit
- Account balance check for the debit
- Post successful validation, amount blocked in the account
- Response sent to the external system
EA Transaction
Actual debit on accounts for transactions against ECA is performed on the account. On request, accounting debits the account based on the ECA approved amount. The requested amount is debited from the account by releasing the block. When an EA request comes with a credit; this is performed by validating the account and the customer, and the balance gets updated post successful completion of the transaction.
A direct EA call can also happen without an ECA request. In case of a direct EA request, account validation, customer validation, account balance check is done and on successful validation, the transaction is completed with a response to the external system. The API's of ECA and EA are designed to work based on coherence asynchronous cache events.
Parent topic: Transaction Balance Service