How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

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 consents using the dedicated endpoints (which are not implemented), but only to redirect the PSU to our authorisation page (using `AIS` as OAuth2 scope).After performing a strong customer authentication, the PSU will be redirected to your redirect URI with an **authorisation code** that you can then exchange for an **access token**.This **access token** will let you authenticate at the XS2A interface to request the PSU accounts balances and transactions history.

Memo Bank AIS API is one of 15 APIs that Memo Bank publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include AIS. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a getting-started guide.

This API exposes 9 operations across 9 paths, and defines 25 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: https://api.memo.bank/nextgenpsd2, https://api.beta.sandbox.memo.bank/nextgenpsd2.

9 operations 9 paths 25 schemas 9 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.memo.bank
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

Memo Bank AIS API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OAuth2) using the authorizationCode flow, exposing 2 scopes.

Paths & Operations 9

Across 9 paths, the API surfaces 9 operations — 9 GET. Each is listed below with its method, path, parameters, and response codes.

AIS 9

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 conse…

GET
/v1/accounts/{accountId}/balances
Read account balance
readAccountBalance 2 params → default
GET
/v1/accounts/{accountId}
Read account details
readAccountDetails 3 params → default
GET
/v1/accounts/{accountId}/transactions/{transactionId}
Read transaction details of an account
readAccountTransactionDetails 3 params → default
GET
/v1/accounts/{accountId}/transactions
Read transactions list of an account
readAccountTransactionsList 7 params → default
GET
/v1/accounts
Read accounts list
readAccountsList 2 params → default
GET
/v1/card-accounts/{accountId}/balances
Read card account balance
readCardAccountBalance 2 params → default
GET
/v1/card-accounts/{accountId}
Read card account details
readCardAccountDetails 2 params → default
GET
/v1/card-accounts/{accountId}/transactions
Read transactions list of a card account
readCardAccountTransactionsList 6 params → default
GET
/v1/card-accounts
Read card accounts list
readCardAccountsList 1 param → default

Schemas 25

The contract defines 25 schemas that model the data the API accepts and returns. The most detailed are Transactions (17 properties), CardTransaction (14 properties), CardAccountDetails (13 properties), AccountDetails (13 properties). Each schema is shown below with its type and property counts.

TransactionDetailsResponse
object
1 property 1 required
Amount
object
2 properties 2 required
AccountReference
object
4 properties
LinksAccountReport
object
3 properties 1 required
LinksCardAccountReport
object
3 properties
AccountDetailsResponse
object
1 property 1 required
Transactions
object
17 properties 7 required
ReportExchangeRate
object
5 properties 5 required
CardAccountTransactionListResponse
object
4 properties
AccountReport
object
3 properties
CardTransaction
object
14 properties 9 required
Address
object
4 properties 1 required
TransactionListResponse
object
3 properties
Balance
object
4 properties 4 required
TransactionExtras
object
1 property 1 required
AccountBalancesResponse
object
2 properties 1 required
CardAccountReport
object
3 properties 1 required
LinksAccountDetails
object
2 properties 2 required
AccountDetails
object
13 properties 12 required
CardAccountListResponse
object
1 property 1 required
CardAccountDetails
object
13 properties 12 required
CardAccountDetailsResponse
object
1 property 1 required
CardAccountBalancesResponse
object
3 properties 1 required
AccountListResponse
object
1 property 1 required
HrefType
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

memo-bank-ais-api-openapi.yml Raw ↑

Other APIs Memo Bank publishes across the network.

Memo Bank Account assessments API
Memo Bank Accounts API
Memo Bank Attachments API
Memo Bank Collections API
Memo Bank IBA Ns API
Memo Bank Mandate signature requests API
Memo Bank O Auth2 API
Memo Bank PIS API
Memo Bank Sandbox API
Memo Bank Transactions API
Memo Bank Transfers API
Memo Bank Webhook API
Where this information came from

This is an independent, third-party profile of Memo Bank AIS API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.