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 NextGenPSD2 API

Berlin Group NextGenPSD2 XS2A implementation (Implementation Guidelines 1.3.11) exposing Account Information Service and Payment Initiation Service endpoints to licensed third-party payment service providers under PSD2. Provides account lists, details, balances and transactions, card account equivalents, and payment initiation, status and cancellation, secured with eIDAS certificates and an OAuth 2.0 authorization-code flow carrying AIS and PIS scopes.

This API exposes 13 operations across 12 paths, organized into 2 resource areas, and defines 35 schemas. It is described by OpenAPI 3.0.1, at version 1.0.

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

13 operations 12 paths 35 schemas 1 DELETE11 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1.0
Base URL
https://api.memo.bank/nextgenpsd2
Authentication
OAuth 2.0
Resource Areas
2

Authentication & Security 1

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

Paths & Operations 13

Across 12 paths, the API surfaces 13 operations — 1 DELETE, 11 GET, 1 POST. They span 2 resource areas: AIS, PIS. 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
PIS 4

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

GET
/v1/{payment-service}/{payment-product}/{paymentId}
Get payment information
getPaymentInformation 4 params → 200
DELETE
/v1/{payment-service}/{payment-product}/{paymentId}
Cancel a payment.
cancelPayment 4 params → default
GET
/v1/{payment-service}/{payment-product}/{paymentId}/status
Get payment initiation status
getPaymentInitiationStatus 4 params → default
POST
/v1/{payment-service}/{payment-product}
Initiate a payment
initiatePayment 3 params body → default

Schemas 35

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

AccountBalancesResponse
object
2 properties 1 required
AccountReference
object
4 properties
Amount
object
2 properties 2 required
Balance
object
4 properties 4 required
AccountDetails
object
13 properties 12 required
AccountDetailsResponse
object
1 property 1 required
HrefType
object
1 property
LinksAccountDetails
object
2 properties 2 required
ReportExchangeRate
object
5 properties 5 required
TransactionDetailsResponse
object
1 property 1 required
TransactionExtras
object
1 property 1 required
Transactions
object
17 properties 7 required
AccountReport
object
3 properties
LinksAccountReport
object
3 properties 1 required
TransactionListResponse
object
3 properties
AccountListResponse
object
1 property 1 required
CardAccountBalancesResponse
object
3 properties 1 required
CardAccountDetails
object
13 properties 12 required
CardAccountDetailsResponse
object
1 property 1 required
Address
object
4 properties 1 required
CardAccountReport
object
3 properties 1 required
CardAccountTransactionListResponse
object
4 properties
CardTransaction
object
14 properties 9 required
LinksCardAccountReport
object
3 properties
CardAccountListResponse
object
1 property 1 required
PaymentInitiationCancelResponseMinus202
object
1 property 1 required
PaymentInitiationWithStatusResponse
object
8 properties 4 required
BulkPaymentInitiationWithStatusResponse
object
4 properties 3 required
PaymentInitiationBulkElementJson
object
6 properties 3 required
PaymentInitiationStatusResponseMinus200Json
object
3 properties 1 required
TppMessage
object
4 properties 2 required
PaymentInitiationJson
object
8 properties 4 required
BulkPaymentInitiationJson
object
3 properties 2 required
LinksPaymentInitiation
object
2 properties
PaymentInitationRequestResponseMinus201
object
5 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

memo-bank-nextgenpsd2-api-openapi.yml Raw ↑
Where this information came from

This is an independent, third-party profile of Memo Bank NextGenPSD2 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.