Explore/Learning paths/Path
Learning path · 5 steps

EBICS, SFTP, SWIFT and APIs: Understanding the Layers

"I keep hearing EBICS, SFTP, SWIFT, API — I want to know what's actually different between them."

  1. 1
    Problem

    Separate the four layers people conflate: application, communication channel, interface style, and message standard.

    ARTICLE

    TMS, EBICS, API, ISO 20022: Four Layers, Not Four Alternatives

  2. 2
    Mechanism

    See what a bank API adds on top of file based channels, explained without code.

    ARTICLE

    Treasury API Guide: A Non-Technical Treasurer's Complete Manual

    ARTICLE

    Treasury API Cheat Sheet

  3. 3
    Example

    Compare the options as they are sold today: open banking, premium bank APIs, and where each one fits.

    ARTICLE

    Bank APIs for Treasury

  4. 4
    Tool

    Turn your own banks, countries and flows into the questions each layer raises.

    TOOL

    Connectivity Requirements Builder

    Start from your banks, countries, accounts, payments and reporting, and get the questions for the bank, IT and the vendor.

  5. 5
    Checklist

    Place one real connection on the map and list what is still unclear before you change anything.

    TOOL

    Map Your Bank Connection — "To Clarify" list

    Fill in channel, format and owners for one bank. Whatever you leave as "I don't know" becomes the list to clarify.

Done with this path? Next
Learning path

Understand the TMS–Bank Connection

"I want to understand the connection between my TMS and my bank."

Learning path

Read Your Bank Statement Files: MT940 and camt.053

"I want to understand what's actually in a bank statement file, and how to read it."

Get the next path when it's out.

New paths, tools and articles by email. No spam, unsubscribe anytime.

SubscribeAll paths