Same information, different structures
Two suppliers may describe the same product with different field names, currencies, or status codes. Setting up a shared data model from the start prevents the rest of the application from having to know each supplier separately.
Continuing after a failed transaction
A request timing out does not always mean it was not processed on the other side. Retry behavior must be designed with care. Especially in booking and payment flows, an approach that prevents the same transaction from happening more than once is needed.
Visibility and logging
An error message that says only "transaction failed" does not give operations enough to work with. Context like transaction id, time, and the related system makes review easier. Access to logs and protection of sensitive data are part of this design.
When the contract changes
A supplier API can change over time. A follow-up method for field requirements, status codes, and version transitions is needed. An integration is not a job that ends on the day the connection is made.