6. What Your System Receives

Your system receives a request from Payblr containing:

• The EHI payload.

• Payblr integration headers used for tracing and request validation.

6.1 Request body

The request body contains the EHI message payload.

Your system should be prepared to receive the full EHI message, including transaction, merchant, balance, fee, network, tokenization, authentication, matching, and lifecycle fields. Click here for an example of an Authorization Request body.

The payload may include:

6.2 Payblr integration headers

Payblr includes integration headers so your systems can trace and validate the request.

Your systems should log x-correlation-id together with the EHI transaction identifiers and the response returned to Payblr.

6.3 Payload handling expectations

Your system should be designed to process EHI messages safely and consistently.

• Process the full payload – Do not assume that only a small subset of fields will be present.

• Preserve field casing – Treat EHI field names as case-sensitive.

• Handle empty fields – Empty fields may be present and should not automatically be treated as errors.

• Ignore unexpected fields safely – Additional fields should not break your integration.

• Store key identifiers – Store transaction and lifecycle identifiers for matching, retries, and reconciliation.

• Use original EHI logic – Apply transaction matching and response logic based on the original EHI fields.

Note: Field capitalization and spelling matters. Your system should ignore unexpected fields safely when new EHI fields or values are introduced.