Learning path

Enterprise and banking integration

Understand how enterprise systems connect and why banking integration requires additional controls.

By the end you'll understand

how enterprise systems connect —queues, EDI and financial messaging— and why banking integration demands extra controls and standards.

Prerequisites
basic (networking and transport)
Estimated duration
~40 min read
1
NET-001 Networks · Transfer

FTP vs SFTP: why plain FTP has no place in modern banking

Both move files. Only one encrypts what travels —credentials included—; and SFTP is not "secure FTP".

2
INT-002 Integration · B2B

EDI: how companies exchange documents without humans

The family of standards that moves orders and invoices from one ERP to another with no one typing. Older than APIs, and still moving global trade.

3
INT-001 Integration · Messaging

MQ vs Kafka: queues and streams, and when to use each

Queues that distribute work and logs that retain and replay events. Why IBM MQ and Kafka get compared so often yet optimize for different models.

4
FIN-001 Banking · Payments

SWIFT: how an international transfer actually travels

SWIFT doesn't move money: it moves the instruction. How correspondent banking does the rest, and why it's slow and costly.

5
FIN-002 Banking · Standards

ISO 20022: the world's new financial language

The standard now replacing SWIFT's MT messages: rich, structured data for payments. The global migration underway right now.