2. Scope

This guide covers Payblr’s client-facing EHI integration.

In this integration, Payblr forwards EHI messages to your configured endpoint, and your system return the required authorization response, acknowledgement, or cut-off result based on the message type.

This guide covers the following areas:

1. EHI authorization – Your system maintains the cardholder balance and makes authorization decisions for applicable transactions.

2. Transaction message forwarding – Payblr forwards EHI transaction messages to your configured endpoint.

3. EHI payload handling – Your system receives the EHI payload structure.

4. Request validation – Your system validates Payblr’s request before processing the transaction message.

5. Authorization responses – Your system returns approve, decline, or partial approval responses when required.

6. Reversals and advice messages – Your systems processes reversal, advice, and other transaction lifecycle messages.

7. Financial and presentment messages – Your system processes transaction events for posting, ledger handling, and reconciliation.

8. Cut-off messages – Your system processes cut-off traffic when CutOffId is present.

9. Transaction matching – Your system applies EHI transaction matching logic using the EHI fields.

10. Duplicate handling – Your system prevents duplicate transaction, balance, block/reserve, or ledger impact when duplicate or retried messages are received.

11. Timeout and retry behavior – Your system responds within the required processing window and handles retries safely.