Memo Bank website screenshot

Memo Bank

Memo Bank is an independent French commercial bank, accredited as a credit institution by the European Central Bank and supervised by the ACPR, that serves small and mid-sized companies with current accounts, loans, savings and an API-first payments platform. Its Premium Bank API is a REST/JSON contract authenticated with RS256-signed JWT/JWS request tokens, covering accounts, transactions, bi-directional virtual IBANs, SEPA credit transfers, SEPA Direct Debit collections and mandate signature requests, SWIFT/RTGS wire transfers, bulk payment batches, attachments and account assessments, with 34 webhook event types for asynchronous reconciliation. A Marketplace API adds an OAuth 2.0 layer so third-party developers can act on customer resources, a NextGenPSD2 API implements the Berlin Group AIS/PIS interface for licensed third-party providers, and a hosted MCP server exposes read-only banking data plus attachment upload to AI assistants.

Memo Bank publishes 15 APIs on the APIs.io network, including Account assessments API, Accounts API, AIS API, and 12 more. Tagged areas include Company, Fintech Insurtech, Banking, Business Banking, and Payments.

The Memo Bank catalog on APIs.io includes 1 event-driven AsyncAPI specification.

Memo Bank’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, pricing, signup flow, and 36 more developer resources.

66.4/100 strong ▬ flat Agent 42/100 agent native saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
AccessPaidSelf serve
3 APIs 1 MCP Servers
CompanyFintech InsurtechBankingBusiness BankingPaymentsSEPASEPA Direct Debitvirtual-ibanWire TransfersOpen BankingPSD2Berlin GroupWebhookMCPFrance

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Payments & Card Management
BC-1340
CollectionsPISTransfersWire Transfers
POST /v1/{payment-service}/{payment-product} POST /v2/transfers POST /v2/transfers/bulks POST /v2/wire_transfers

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Regulatory Posture applies to this provider. Its tags matched the Banking & Open Finance regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.
The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/memo-bank: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 15

Individual APIs this provider publishes, each with its own machine-readable definition.

Memo Bank Account assessments API

Account assessments allow you to assess SEPA counterparty accounts before initiating transactions with them. An assessment provides: * **Risk indicators**: Detection of fraudule...

Memo Bank Accounts API

Accounts are any bank account that your company owns: current account, ring-fenced account, settlement account, specially dedicated account, trust account, meal voucher account,...

Memo Bank AIS API

Account Information Service. Consent is given using the **OAuth2 as a pre-step** authentication flow described in NextGenPSD2 specifications. This means you don't have to manage...

Memo Bank Attachments API

Documents attached to transactions.

Memo Bank Collections API

Collections are SEPA direct debit collections, including SEPA CORE direct debits and SEPA B2B direct debits. To initiate a direct debit, a **mandate** signed by the debtor is re...

Memo Bank IBA Ns API

IBANs are identifiers for bank accounts. There are two types of IBANs at Memo Bank: * Main IBANs, which act as primary identifiers for a bank account. There is exactly one main ...

Memo Bank Mandate signature requests API

Mandate signature requests are a way to prepare and send collection mandates for signature. The mandate debtor receives an email with a link so they can complete and sign the ma...

Memo Bank O Auth2 API

OAuth2 token management endpoints.

Memo Bank PIS API

Payment Initiation Service. Payment initiation is done using the **integrated OAuth2** authentication flow described in NextGenPSD2 specifications. This means you first have to ...

Memo Bank Sandbox API

Sandbox only endpoints.

Memo Bank Transactions API

Transactions are any debit and credit operations on an account. Transactions lifecycle

Memo Bank Transfers API

Transfers are transfers within the SEPA-zone, including SEPA standard transfers, SEPA instant transfers and Target 2 transfers. They can be initiated asynchronously, one by one ...

Memo Bank Webhook API

# Events When something interesting happens on your Memo Bank workspace, such as a new transaction being created, Memo Bank can reach out to your application so that you can tak...

Memo Bank Webhooks API

Manage webhooks for your application. Webhooks allow you to receive real-time notifications when events occur on your Memo Bank workspace. Please refer to the [Webhook](https://...

Memo Bank Wire Transfers API

Wire transfers are transfers going through Swift. They allow you to send funds outside the SEPA network and to transfer money in foreign currencies. Initiating a wire transfer m...

Scroll for all 15

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Pricing Plans 1

Published pricing tiers and plan structures.

Rate Limits 1

Documented rate limits and quota policies.

Memo Bank Rate Limits

0 limits

RATE LIMITS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Memo Bank Authentication

http/oauth2/mutualTLS · 4 schemes

SECURITY

Memo Bank Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Memo Bank Vulnerability Disclosure

Hackerone · contact published

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Memo Bank Scopes

2 scopes · authorizationCode

2 scopes

SCOPES

Resources

Get Started 5

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Scroll for all 7

Build 4

SDKs, sample code, and the tooling you integrate with

Access & Security 5

Authentication, authorization, and security posture

Operate 6

Status, limits, changes, and where to get help

Commercial 4

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Other 4

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: memo-bank
name: Memo Bank
description: Memo Bank is an independent French commercial bank, accredited as a credit institution by the European Central
  Bank and supervised by the ACPR, that serves small and mid-sized companies with current accounts, loans, savings and an
  API-first payments platform. Its Premium Bank API is a REST/JSON contract authenticated with RS256-signed JWT/JWS request
  tokens, covering accounts, transactions, bi-directional virtual IBANs, SEPA credit transfers, SEPA Direct Debit collections
  and mandate signature requests, SWIFT/RTGS wire transfers, bulk payment batches, attachments and account assessments, with
  34 webhook event types for asynchronous reconciliation. A Marketplace API adds an OAuth 2.0 layer so third-party developers
  can act on customer resources, a NextGenPSD2 API implements the Berlin Group AIS/PIS interface for licensed third-party
  providers, and a hosted MCP server exposes read-only banking data plus attachment upload to AI assistants.
url: https://raw.githubusercontent.com/api-evangelist/memo-bank/refs/heads/main/apis.yml
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: paid
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Paid · Self-serve signup
  confidence: high
  source:
  - plans
  - authentication
  - scopes
  - rate-limits
  - security
  - sandbox
  generated: '2026-09-02'
  method: derived
image: https://media.memo.bank/home_hero_602cdab270/home_hero_602cdab270.jpg
x-type: company
x-source: serena-portfolio
specificationVersion: '0.23'
created: '2026-08-17'
modified: '2026-08-17'
tags:
- Company
- Fintech Insurtech
- Banking
- Business Banking
- Payments
- SEPA
- SEPA Direct Debit
- virtual-iban
- Wire Transfers
- Open Banking
- PSD2
- Berlin Group
- Webhook
- MCP
- France
tags_raw:
- Company
- Fintech Insurtech
- banking
- business-banking
- payments
- sepa
- sepa-direct-debit
- virtual-iban
- wire-transfers
- open-banking
- psd2
- berlin-group
- webhooks
- mcp
- france
apis:
- aid: memo-bank:memo-bank-account-assessments-api
  name: Memo Bank Account assessments API
  description: 'Account assessments allow you to assess SEPA counterparty accounts before initiating transactions with them.
    An assessment provides:


    * **Risk indicators**: Detection of fraudulent activity, suspicious patterns, and other risk signals.

    * **Identification matching**: Verify that the account name or other identifiers match the value known by the account
    holder.

    * **Account reachability**: Information about which payment schemes are supported by the account holder.


    Account assessments are processed asynchronously: you need to listen to `account_assessment_completed` and `account_assessment_failed`
    webhook  events to know when its time to retrieve the assessment results.


    This feature is subject to specific pricing, please reach out to your banker to get more information.'
  humanURL: https://docs.api.memo.bank/
  baseURL: https://api.memo.bank
  tags:
  - Account assessments
  properties:
  - type: OpenAPI
    url: openapi/memo-bank-account-assessments-api-openapi.yml
  - type: Documentation
    url: https://docs.api.memo.bank/
  - type: APIReference
    url: https://docs.api.memo.bank/version-2/
  - type: GettingStarted
    url: https://docs.api.memo.bank/topic/topic-getting-started
  - type: Webhooks
    url: asyncapi/memo-bank-webhooks.yml
  - type: ToolCrosswalk
    url: mcp/memo-bank-tool-crosswalk.yml
  - type: Documentation
    url: https://docs-marketplace.api.memo.bank/
  - type: GettingStarted
    url: https://docs-marketplace.api.memo.bank/topic/topic-getting-started
  - type: Documentation
    url: https://docs-nextgenpsd2.api.memo.bank/
  - type: OAuthScopes
    url: scopes/memo-bank-scopes.yml
- aid: memo-bank:memo-bank-accounts-api
  name: Memo Bank Accounts API
  description: 'Accounts are any bank account that your company owns: current account, ring-fenced account,  settlement account,
    specially dedicated account, trust account, meal voucher account,  booster account, etc. They boil down to a list of [transactions](#endpoint-transactions)
    and a balance.'
  humanURL: https://docs.api.memo.bank/
  baseURL: https://api.memo.bank
  tags:
  - Account
  tags_raw:
  - Accounts
  properties:
  - type: OpenAPI
    url: openapi/memo-bank-accounts-api-openapi.yml
  - type: Documentation
    url: https://docs.api.memo.bank/
  - type: APIReference
    url: https://docs.api.memo.bank/version-2/
  - type: GettingStarted
    url: https://docs.api.memo.bank/topic/topic-getting-started
  - type: Webhooks
    url: asyncapi/memo-bank-webhooks.yml
  - type: ToolCrosswalk
    url: mcp/memo-bank-tool-crosswalk.yml
  - type: Documentation
    url: https://docs-marketplace.api.memo.bank/
  - type: GettingStarted
    url: https://docs-marketplace.api.memo.bank/topic/topic-getting-started
  - type: Documentation
    url: https://docs-nextgenpsd2.api.memo.bank/
  - type: OAuthScopes
    url: scopes/memo-bank-scopes.yml
- aid: memo-bank:memo-bank-ais-api
  name: Memo Bank AIS API
  description: "Account Information Service.\n\n\nConsent is given using the **OAuth2 as a pre-step** authentication flow\
    \ described in NextGenPSD2 specifications.\nThis means you don't have to manage consents using the dedicated endpoints\
    \ (which are not implemented), \nbut only to redirect the PSU to our authorisation page (using `AIS` as OAuth2 scope).\n\
    After performing a strong customer authentication, the PSU will be redirected to your redirect URI with an \n**authorisation\
    \ code** that you can then exchange for an **access token**.\n\n\nThis **access token** will let you authenticate at the\
    \ XS2A interface to request the PSU accounts balances and \ntransactions history."
  humanURL: https://docs.api.memo.bank/
  baseURL: https://api.memo.bank
  tags:
  - AIS
  properties:
  - type: OpenAPI
    url: openapi/memo-bank-ais-api-openapi.yml
  - type: Documentation
    url: https://docs.api.memo.bank/
  - type: APIReference
    url: https://docs.api.memo.bank/version-2/
  - type: GettingStarted
    url: https://docs.api.memo.bank/topic/topic-getting-started
  - type: Webhooks
    url: asyncapi/memo-bank-webhooks.yml
  - type: ToolCrosswalk
    url: mcp/memo-bank-tool-crosswalk.yml
  - type: Documentation
    url: https://docs-marketplace.api.memo.bank/
  - type: GettingStarted
    url: https://docs-marketplace.api.memo.bank/topic/topic-getting-started
  - type: Documentation
    url: https://docs-nextgenpsd2.api.memo.bank/
  - type: OAuthScopes
    url: scopes/memo-bank-scopes.yml
- aid: memo-bank:memo-bank-attachments-api
  name: Memo Bank Attachments API
  description: Documents attached to transactions.
  humanURL: https://docs.api.memo.bank/
  baseURL: https://api.memo.bank
  tags:
  - Attachments
  properties:
  - type: OpenAPI
    url: openapi/memo-bank-attachments-api-openapi.yml
  - type: Documentation
    url: https://docs.api.memo.bank/
  - type: APIReference
    url: https://docs.api.memo.bank/version-2/
  - type: GettingStarted
    url: https://docs.api.memo.bank/topic/topic-getting-started
  - type: Webhooks
    url: asyncapi/memo-bank-webhooks.yml
  - type: ToolCrosswalk
    url: mcp/memo-bank-tool-crosswalk.yml
  - type: Documentation
    url: https://docs-marketplace.api.memo.bank/
  - type: GettingStarted
    url: https://docs-marketplace.api.memo.bank/topic/topic-getting-started
  - type: Documentation
    url: https://docs-nextgenpsd2.api.memo.bank/
  - type: OAuthScopes
    url: scopes/memo-bank-scopes.yml
- aid: memo-bank:memo-bank-collections-api
  name: Memo Bank Collections API
  description: "Collections are SEPA direct debit collections, including SEPA CORE direct debits and SEPA B2B direct debits.\
    \ \n\nTo initiate a direct debit, a **mandate** signed by the debtor is required.  You have the option to use our [signature\
    \ request](endpoint-mandate-signature-requests)  workflow, which handles this signature, or you can choose to manage it\
    \  yourself. Whichever method you select, you will only need to provide  the mandate information when setting up the direct\
    \ debit, not the signed  document itself.\n\nThey can be initiated asynchronously, one by one or in bulk. \n\nUnlike [transfers](#endpoint-transfers),\
    \ collections can only be scheduled for a date in the future.  As a result, their lifecycle is also simplified.\n\n<img\
    \ src=\"https://assets.memo.bank/memobankapi/collections-lifecycle-api-v3.png\" alt=\"Collections lifecycle\" width=\"\
    750\">"
  humanURL: https://docs.api.memo.bank/
  baseURL: https://api.memo.bank
  tags:
  - Collection
  tags_raw:
  - Collections
  properties:
  - type: OpenAPI
    url: openapi/memo-bank-collections-api-openapi.yml
  - type: Documentation
    url: https://docs.api.memo.bank/
  - type: APIReference
    url: https://docs.api.memo.bank/version-2/
  - type: GettingStarted
    url: https://docs.api.memo.bank/topic/topic-getting-started
  - type: Webhooks
    url: asyncapi/memo-bank-webhooks.yml
  - type: ToolCrosswalk
    url: mcp/memo-bank-tool-crosswalk.yml
  - type: Documentation
    url: https://docs-marketplace.api.memo.bank/
  - type: GettingStarted
    url: https://docs-marketplace.api.memo.bank/topic/topic-getting-started
  - type: Documentation
    url: https://docs-nextgenpsd2.api.memo.bank/
  - type: OAuthScopes
    url: scopes/memo-bank-scopes.yml
- aid: memo-bank:memo-bank-ibans-api
  name: Memo Bank IBA Ns API
  description: 'IBANs are identifiers for bank accounts. There are two types of IBANs at Memo Bank:

    * Main IBANs, which act as primary identifiers for a bank account.  There is exactly one main IBAN per bank account. You
    cannot delete it. When an account is closed, its main IBAN remains active only for  incoming transactions, which will
    be automatically rerouted to the  main account.

    * Virtual IBANs, which are aliases for the main IBAN. They can be created, deactivated, and reactivated at will. When
    the account they are attached to  is closed, they get reattached to the main account.


    All operations on IBANs are synchronous and effective immediately,  meaning that you can use a new IBAN to send or receive
    money right  after its creation.'
  humanURL: https://docs.api.memo.bank/
  baseURL: https://api.memo.bank
  tags:
  - IBANs
  properties:
  - type: OpenAPI
    url: openapi/memo-bank-ibans-api-openapi.yml
  - type: Documentation
    url: https://docs.api.memo.bank/
  - type: APIReference
    url: https://docs.api.memo.bank/version-2/
  - type: GettingStarted
    url: https://docs.api.memo.bank/topic/topic-getting-started
  - type: Webhooks
    url: asyncapi/memo-bank-webhooks.yml
  - type: ToolCrosswalk
    url: mcp/memo-bank-tool-crosswalk.yml
  - type: Documentation
    url: https://docs-marketplace.api.memo.bank/
  - type: GettingStarted
    url: https://docs-marketplace.api.memo.bank/topic/topic-getting-started
  - type: Documentation
    url: https://docs-nextgenpsd2.api.memo.bank/
  - type: OAuthScopes
    url: scopes/memo-bank-scopes.yml
- aid: memo-bank:memo-bank-mandate-signature-requests-api
  name: Memo Bank Mandate signature requests API
  description: Mandate signature requests are a way to prepare and send collection mandates for signature. The mandate debtor  receives
    an email with a link so they can complete and sign the mandate. Once it has been signed, the resulting  mandate becomes
    immediately available for making [collections](#endpoint-collections). Dedicated  [webhook events](#webhook-webhook) can
    be used to track mandate signature requests state changes.
  humanURL: https://docs.api.memo.bank/
  baseURL: https://api.memo.bank
  tags:
  - Mandate signature requests
  properties:
  - type: OpenAPI
    url: openapi/memo-bank-mandate-signature-requests-api-openapi.yml
  - type: Documentation
    url: https://docs.api.memo.bank/
  - type: APIReference
    url: https://docs.api.memo.bank/version-2/
  - type: GettingStarted
    url: https://docs.api.memo.bank/topic/topic-getting-started
  - type: Webhooks
    url: asyncapi/memo-bank-webhooks.yml
  - type: ToolCrosswalk
    url: mcp/memo-bank-tool-crosswalk.yml
  - type: Documentation
    url: https://docs-marketplace.api.memo.bank/
  - type: GettingStarted
    url: https://docs-marketplace.api.memo.bank/topic/topic-getting-started
  - type: Documentation
    url: https://docs-nextgenpsd2.api.memo.bank/
  - type: OAuthScopes
    url: scopes/memo-bank-scopes.yml
- aid: memo-bank:memo-bank-oauth2-api
  name: Memo Bank O Auth2 API
  description: OAuth2 token management endpoints.
  humanURL: https://docs.api.memo.bank/
  baseURL: https://api.memo.bank
  tags:
  - Authentication
  tags_raw:
  - OAuth2
  properties:
  - type: OpenAPI
    url: openapi/memo-bank-oauth2-api-openapi.yml
  - type: Documentation
    url: https://docs.api.memo.bank/
  - type: APIReference
    url: https://docs.api.memo.bank/version-2/
  - type: GettingStarted
    url: https://docs.api.memo.bank/topic/topic-getting-started
  - type: Webhooks
    url: asyncapi/memo-bank-webhooks.yml
  - type: ToolCrosswalk
    url: mcp/memo-bank-tool-crosswalk.yml
  - type: Documentation
    url: https://docs-marketplace.api.memo.bank/
  - type: GettingStarted
    url: https://docs-marketplace.api.memo.bank/topic/topic-getting-started
  - type: Documentation
    url: https://docs-nextgenpsd2.api.memo.bank/
  - type: OAuthScopes
    url: scopes/memo-bank-scopes.yml
- aid: memo-bank:memo-bank-pis-api
  name: Memo Bank PIS API
  description: "Payment Initiation Service.\n\n\nPayment initiation is done using the **integrated OAuth2** authentication\
    \ flow described in NextGenPSD2\nspecifications.\nThis means you first have to initiate a payment using the dedicated\
    \ endpoint, then redirect the PSU to our \nauthorisation page following the link present in the response (using `PIS:{paymentId}`\
    \ as OAuth2 scope).\nAfter performing a strong customer authentication, the PSU will be redirected to your redirect URI\
    \ with an\n**authorisation code** that you can then exchange for an **access token**.\n\n\nThis **access token** is only\
    \ needed to cancel a payment on behalf a PSU (this does not require a strong\ncustomer authentication). It is not needed\
    \ to retrieve the current status of a payment."
  humanURL: https://docs.api.memo.bank/
  baseURL: https://api.memo.bank
  tags:
  - PIS
  properties:
  - type: OpenAPI
    url: openapi/memo-bank-pis-api-openapi.yml
  - type: Documentation
    url: https://docs.api.memo.bank/
  - type: APIReference
    url: https://docs.api.memo.bank/version-2/
  - type: GettingStarted
    url: https://docs.api.memo.bank/topic/topic-getting-started
  - type: Webhooks
    url: asyncapi/memo-bank-webhooks.yml
  - type: ToolCrosswalk
    url: mcp/memo-bank-tool-crosswalk.yml
  - type: Documentation
    url: https://docs-marketplace.api.memo.bank/
  - type: GettingStarted
    url: https://docs-marketplace.api.memo.bank/topic/topic-getting-started
  - type: Documentation
    url: https://docs-nextgenpsd2.api.memo.bank/
  - type: OAuthScopes
    url: scopes/memo-bank-scopes.yml
- aid: memo-bank:memo-bank-sandbox-api
  name: Memo Bank Sandbox API
  description: Sandbox only endpoints.
  humanURL: https://docs.api.memo.bank/
  baseURL: https://api.memo.bank
  tags:
  - Sandbox
  properties:
  - type: OpenAPI
    url: openapi/memo-bank-sandbox-api-openapi.yml
  - type: Documentation
    url: https://docs.api.memo.bank/
  - type: APIReference
    url: https://docs.api.memo.bank/version-2/
  - type: GettingStarted
    url: https://docs.api.memo.bank/topic/topic-getting-started
  - type: Webhooks
    url: asyncapi/memo-bank-webhooks.yml
  - type: ToolCrosswalk
    url: mcp/memo-bank-tool-crosswalk.yml
  - type: Documentation
    url: https://docs-marketplace.api.memo.bank/
  - type: GettingStarted
    url: https://docs-marketplace.api.memo.bank/topic/topic-getting-started
  - type: Documentation
    url: https://docs-nextgenpsd2.api.memo.bank/
  - type: OAuthScopes
    url: scopes/memo-bank-scopes.yml
- aid: memo-bank:memo-bank-transactions-api
  name: Memo Bank Transactions API
  description: 'Transactions are any debit and credit operations on an account.


    <img src="https://assets.memo.bank/memobankapi/transactions-lifecycle-api-v2.png" alt="Transactions lifecycle" width="750">


    Note that the status of the transaction indicates whether or not it affects the account’s available balance. `debit` transactions
    impact the balance as soon as they reach the `authorized` state. `credit` transactions impact it only when their status
    turns to `confirmed`.'
  humanURL: https://docs.api.memo.bank/
  baseURL: https://api.memo.bank
  tags:
  - Transaction
  tags_raw:
  - Transactions
  properties:
  - type: OpenAPI
    url: openapi/memo-bank-transactions-api-openapi.yml
  - type: Documentation
    url: https://docs.api.memo.bank/
  - type: APIReference
    url: https://docs.api.memo.bank/version-2/
  - type: GettingStarted
    url: https://docs.api.memo.bank/topic/topic-getting-started
  - type: Webhooks
    url: asyncapi/memo-bank-webhooks.yml
  - type: ToolCrosswalk
    url: mcp/memo-bank-tool-crosswalk.yml
  - type: Documentation
    url: https://docs-marketplace.api.memo.bank/
  - type: GettingStarted
    url: https://docs-marketplace.api.memo.bank/topic/topic-getting-started
  - type: Documentation
    url: https://docs-nextgenpsd2.api.memo.bank/
  - type: OAuthScopes
    url: scopes/memo-bank-scopes.yml
- aid: memo-bank:memo-bank-transfers-api
  name: Memo Bank Transfers API
  description: 'Transfers are transfers within the SEPA-zone, including SEPA standard transfers, SEPA instant transfers and
    Target 2 transfers.


    They can be initiated asynchronously, one by one or in bulk.


    They have a similar lifecycle compared to [transactions](#endpoint-transactions)  but note that there are some minor differences
    for the `canceled`  and `failed` states.


    <img src="https://assets.memo.bank/memobankapi/transfers-lifecycle-api-v3.png" alt="Transfers lifecycle" width="750">'
  humanURL: https://docs.api.memo.bank/
  baseURL: https://api.memo.bank
  tags:
  - Transfers
  properties:
  - type: OpenAPI
    url: openapi/memo-bank-transfers-api-openapi.yml
  - type: Documentation
    url: https://docs.api.memo.bank/
  - type: APIReference
    url: https://docs.api.memo.bank/version-2/
  - type: GettingStarted
    url: https://docs.api.memo.bank/topic/topic-getting-started
  - type: Webhooks
    url: asyncapi/memo-bank-webhooks.yml
  - type: ToolCrosswalk
    url: mcp/memo-bank-tool-crosswalk.yml
  - type: Documentation
    url: https://docs-marketplace.api.memo.bank/
  - type: GettingStarted
    url: https://docs-marketplace.api.memo.bank/topic/topic-getting-started
  - type: Documentation
    url: https://docs-nextgenpsd2.api.memo.bank/
  - type: OAuthScopes
    url: scopes/memo-bank-scopes.yml
- aid: memo-bank:memo-bank-webhook-api
  name: Memo Bank Webhook API
  description: "# Events\n\nWhen something interesting happens on your Memo Bank workspace, such as a new transaction being\
    \ created, Memo Bank can reach out to your application so that you can take action (such as sending an e-mail alert about\
    \ the transaction to your user) automatically.\n\nThe first step is to add a webhook to your application in the [`API`](https://client.memo.bank/api)\
    \ section of your Memo Bank workspace. As part of this, you will have to provide a URL on your own servers. Memo Bank\
    \ will then send HTTPS requests to that URL when there is an activity on your Memo Bank workspace.\n\nNote that even if\
    \ webhooks are setup within an application, events will  be received even when they result from actions triggered on the\
    \ Memo Bank  webapp or any other application.\n# Consuming events\nIndividual events do not contain very much information\
    \ on their own. This is by design, as the API structure can remain extremely stable and avoid difficult webhook migrations\
    \ in the future as the Memo Bank API changes. If you need additional metadata, such as the amount of the transaction in\
    \ the above example, make a `GET` request to the API for that information. You can use the `resource_type` and `resource_id`\
    \ to determine what resource to fetch from the API.\n# Failures and retries\nIf your application returns anything other\
    \ than a 2xx HTTP status code,  if we do not receive a response before timing out or in the case of  a network failure,\
    \ we will retry the event up to 8 times with exponentially increasing backoffs.  In your webhook endpoint implementation,\
    \  we recommend you place  inbound Events into your application's own queuing system  (such as Kafka, Resque, etc) for\
    \ asynchronous event processing,  and returning a 200 response from your endpoint as quickly as possible.\n\nSince retries\
    \ may occur, your webhook endpoint must be idempotent. You should handle the possibility of receiving the same event multiple\
    \ times. We recommend using the event `id` field to detect and ignore duplicate events on your side.\n# Securing your\
    \ webhook endpoint (recommended)\nMemo Bank will include an `Authorization` header in each webhook request. Inside of\
    \ it, you will find `Bearer <token>` with the authentication token we provided when you created the webhook on the web\
    \ interface. We recommend that you check this header and reject requests with invalid token, indicating a malicious request\
    \ that would not have been issued by Memo Bank.\n\nWe also recommend that you restrict which IP addresses can call your\
    \  webhook. Here is the list of our IPv4 addresses:\n* Memo Bank Premium API (i.e. `api.memo.bank`):\n  * `34.38.96.206`\n\
    \  * `35.189.206.171`\n  * `35.241.129.224`\n  * `34.155.214.185`\n  * `34.155.206.98`\n  * `34.163.14.38`\n\n* Memo Bank\
    \ Premium Sandbox API (i.e. `api.sandbox.memo.bank`):\n  * `34.155.60.111`\n  * `34.163.27.39`"
  humanURL: https://docs.api.memo.bank/
  baseURL: https://api.memo.bank
  tags:
  - Webhook
  properties:
  - type: OpenAPI
    url: openapi/memo-bank-webhook-api-openapi.yml
  - type: Documentation
    url: https://docs.api.memo.bank/
  - type: APIReference
    url: https://docs.api.memo.bank/version-2/
  - type: GettingStarted
    url: https://docs.api.memo.bank/topic/topic-getting-started
  - type: Webhooks
    url: asyncapi/memo-bank-webhooks.yml
  - type: ToolCrosswalk
    url: mcp/memo-bank-tool-crosswalk.yml
  - type: Documentation
    url: https://docs-marketplace.api.memo.bank/
  - type: GettingStarted
    url: https://docs-marketplace.api.memo.bank/topic/topic-getting-started
  - type: Documentation
    url: https://docs-nextgenpsd2.api.memo.bank/
  - type: OAuthScopes
    url: scopes/memo-bank-scopes.yml
- aid: memo-bank:memo-bank-webhooks-api
  name: Memo Bank Webhooks API
  description: 'Manage webhooks for your application. Webhooks allow you to receive real-time notifications when events occur
    on your Memo Bank workspace.


    Please refer to the [Webhook](https://docs.api.memo.bank/group/webhook-webhook) section for more information.'
  humanURL: https://docs.api.memo.bank/
  baseURL: https://api.memo.bank
  tags:
  - Webhook
  tags_raw:
  - Webhooks
  properties:
  - type: OpenAPI
    url: openapi/memo-bank-webhooks-api-openapi.yml
  - type: Documentation
    url: https://docs.api.memo.bank/
  - type: APIReference
    url: https://docs.api.memo.bank/version-2/
  - type: GettingStarted
    url: https://docs.api.memo.bank/topic/topic-getting-started
  - type: Webhooks
    url: asyncapi/memo-bank-webhooks.yml
  - type: ToolCrosswalk
    url: mcp/memo-bank-tool-crosswalk.yml
  - type: Documentation
    url: https://docs-marketplace.api.memo.bank/
  - type: GettingStarted
    url: https://docs-marketplace.api.memo.bank/topic/topic-getting-started
  - type: Documentation
    url: https://docs-nextgenpsd2.api.memo.bank/
  - type: OAuthScopes
    url: scopes/memo-bank-scopes.yml
- aid: memo-bank:memo-bank-wire-transfers-api
  name: Memo Bank Wire Transfers API
  description: "Wire transfers are transfers going through Swift. They allow you to send funds outside the SEPA network and\
    \ to transfer money in foreign currencies.\n\nInitiating a wire transfer may require you to upload a supporting document.\
    \ In such case the transfer will have a `pending_attachment_required` status and you'll receive an event `wire_transfer_attachment_required`\
    \ on your webhook. \n\nIf no document is required but you still want to attach one to your transaction, use the [attachments](#endpoint-attachments)\
    \ endpoints.\n\n<img src=\"https://assets.memo.bank/memobankapi/wire-transfers-lifecycle-api-v1.png\" alt=\"Wire transfers\
    \ lifecycle\" width=\"750\">"
  humanURL: https://docs.api.memo.bank/
  baseURL: https://api.memo.bank
  tags:
  - Wire Transfers
  properties:
  - type: OpenAPI
    url: openapi/memo-bank-wire-transfers-api-openapi.yml
  - type: Documentation
    url: https://docs.api.memo.bank/
  - type: APIReference
    url: https://docs.api.memo.bank/version-2/
  - type: GettingStarted
    url: https://docs.api.memo.bank/topic/topic-getting-started
  - type: Webhooks
    url: asyncapi/memo-bank-webhooks.yml
  - type: ToolCrosswalk
    url: mcp/memo-bank-tool-crosswalk.yml
  - type: Documentation
    url: https://docs-marketplace.api.memo.bank/
  - type: GettingStarted
    url: https://docs-marketplace.api.memo.bank/topic/topic-getting-started
  - type: Documentation
    url: https://docs-nextgenpsd2.api.memo.bank/
  - type: OAuthScopes
    url: scopes/memo-bank-scopes.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: CapabilityMap
  url: capabilities/memo-bank-capability-edges.yml
  name: Memo Bank Business Capability Map
- type: Overlay
  url: overlays/memo-bank-premium-bank-api-overlay.yaml
- type: Overlay
  url: overlays/memo-bank-marketplace-api-overlay.yaml
- type: Overlay
  url: overlays/memo-bank-nextgenpsd2-api-overlay.yaml
- type: DomainSecurity
  url: security/memo-bank-domain-security.yml
- type: Website
  url: https://memo.bank/
- type: DeveloperPortal
  url: https://docs.api.memo.bank/
- type: Documentation
  url: https://docs.api.memo.bank/
- type: APIReference
  url: https://docs.api.memo.bank/version-2/
- type: GettingStarted
  url: https://docs.api.memo.bank/topic/topic-getting-started
- type: Support
  url: https://aide.memo.bank/
- type: Blog
  url: https://memo.bank/en/magazine/
- type: GitHubOrganization
  url: https://github.com/memobank
- type: Pricing
  url: https://memo.bank/en/pricing/
- type: SignUp
  url: https://memo.bank/en/sign-up/
- type: Login
  url: https://client.memo.bank/login
- type: TermsOfService
  url: https://memo.bank/en/agreement/
- type: PrivacyPolicy
  url: https://memo.bank/en/personal-data/
- type: Compliance
  url: https://memo.bank/en/about/security-operations/
- type: StatusPage
  url: https://status.memo.bank/
- type: ChangeLog
  url: https://docs.api.memo.bank/changes
- type: MCPServer
  url: mcp/memo-bank-mcp.yml
- type: LLMsTxt
  url: llms/memo-bank-llms.txt
- type: WellKnown
  url: well-known/memo-bank-well-known.yml
- type: Authentication
  url: authentication/memo-bank-authentication.yml
- type: OAuthScopes
  url: scopes/memo-bank-scopes.yml
- type: Conventions
  url: conventions/memo-bank-conventions.yml
- type: Idempotency
  url: conventions/memo-bank-conventions.yml
- type: RateLimits
  url: rate-limits/memo-bank-rate-limits.yml
- type: Plans
  url: plans/memo-bank-plans-pricing.yml
- type: Lifecycle
  url: lifecycle/memo-bank-lifecycle.yml
- type: Deprecation
  url: https://docs.api.memo.bank/topic/topic-versioning-and-backwards-compatibility
- type: Conformance
  url: conformance/memo-bank-conformance.yml
- type: ErrorCatalog
  url: errors/memo-bank-problem-types.yml
- type: DataModel
  url: data-model/memo-bank-data-model.yml
- type: Sandbox
  url: sandbox/memo-bank-sandbox.yml
- type: Webhooks
  url: asyncapi/memo-bank-webhooks.yml
- type: Packages
  url: packages/memo-bank-packages.yml
- type: AgentSkill
  url: skills/_index.yml
- type: ToolCrosswalk
  url: mcp/memo-bank-tool-crosswalk.yml
- type: ChangeLog
  url: changelog/memo-bank-changelog.yml
- type: DeclineCodes
  url: errors/memo-bank-decline-codes.yml
- type: VulnerabilityDisclosure
  url: security/memo-bank-vulnerability-disclosure.yml
x-enrichment:
  date: '2026-08-17'
  status: enriched
  artifacts_added: 26
  pass: local-v1

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/memo-bank"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/memo-bank/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/memo-bank/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.