3. Client System Expectations

Your system should be prepared to receive and process the full EHI payload, including transaction, merchant, balance, fee, network, tokenization, authentication, matching, and lifecycle fields included in the message.

3.1 Client implementation expectations

Your system should process EHI messages using the field names and transaction logic.

This means your system should:

Your system should ignore unexpected fields safely instead of treating them as errors, because additional fields or values may be introduced across EHI versions.

3.2 Client maintains balances

In this model, your system maintains the cardholder balance and makes authorization decisions for applicable transactions.

Your system is responsible for determining whether a transaction should be approved, declined, or partially approved based on your balance logic, account status, transaction rules, fraud controls, and reconciliation requirements.

Your system should calculate the total transaction impact, including billing amount, fees, pads, reversals, and any applicable adjustments, before returning an authorization response.