REST/JSON banking API for Memo Bank business customers, authenticated with RS256-signed JWT request tokens. Covers accounts and balances, transactions with typed transaction sources, virtual and standard IBANs, SEPA credit transfers (standard and instant), SEPA Direct Debit collections, mandate signature requests, SWIFT/RTGS wire transfers, bulk transfer and collection batches, transaction attachments, account assessments (IBAN/name verification), webhook management, and sandbox-only endpoints that simulate incoming transactions. 43 operations across 32 paths, plus an OpenAPI 3.1 webhooks block describing 34 event types.
This API exposes
43 operations
across 32 paths,
organized into 11 resource areas,
and defines 119 schemas.
It is described by OpenAPI 3.1.0, at version 2.0.
Requests are made against 2 base URLs: https://api.memo.bank, https://api.sandbox.memo.bank.
43 operations32 paths119 schemas6 DELETE22 GET1 PATCH14 POST
Metadata
The identity and technical contract details declared by the specification.
Specification
OpenAPI 3.1.0
API Version
2.0
Base URL
https://api.memo.bank
Resource Areas
11
Paths & Operations 43
Across 32 paths, the API surfaces 43 operations — 6 DELETE, 22 GET, 1 PATCH, 14 POST. They span 11 resource areas, including Account assessments, Accounts, Attachments, Collections, IBANs, Mandate signature requests, Sandbox, Transactions, and 3 more. Each is listed below with its method, path, parameters, and response codes.
Account assessments 2
Account assessments allow you to assess SEPA counterparty accounts before initiating transactions with them. An assessment provides: Risk indicators: Detection of fraudulent activ…
POST
/v2/account_assessments
Create an account assessment
createAccountAssessmentbody→ 200
GET
/v2/account_assessments/{id}
Get an account assessment
getAccountAssessment1 param→ 200
Accounts 2
Accounts are any bank account that your company owns: current account, ring-fenced account, settlement account, specially dedicated account, trust account, meal voucher account, b…
GET
/v2/accounts/{id}
Get an account
getAccount1 param→ 200
GET
/v2/accounts
List all accounts
listAccounts3 params→ 200
Attachments 4
Documents attached to transactions.
GET
/v2/attachments
List all attachments
listAttachments5 params→ 200
POST
/v2/attachments
Create an attachment
createAttachmentbody→ 201
GET
/v2/attachments/{id}
Get an attachment
getAttachment1 param→ 200
DELETE
/v2/attachments/{id}
Delete an attachment
deleteAttachment1 param→ 204
Collections 6
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 required…
GET
/v2/collections/{id}
Get a collection
getCollection1 param→ 200
DELETE
/v2/collections/{id}
Cancel a SEPA Direct Debit collection
cancelCollection1 param→ 200
POST
/v2/collections
Schedule a SEPA Direct Debit collection
createCollectionbody→ 200
POST
/v2/collections/bulks
Create bulk collections
createCollectionsBulkbody→ 200
GET
/v2/collections/bulks/{id}
Get a bulk and its current progress
getCollectionsBulk1 param→ 200
GET
/v2/collections/bulks/{id}/collections
Get the status of individual collection in a bulk
getCollectionsBulkItems5 params→ 200
IBANs 5
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…
GET
/v2/ibans
List all IBANs
listIbans5 params→ 200
POST
/v2/ibans
Create a virtual IBAN
createIbanbody→ 201
GET
/v2/ibans/{id}
Get an IBAN
getIban1 param→ 200
DELETE
/v2/ibans/{id}
Delete an IBAN
deleteIban1 param→ 204
PATCH
/v2/ibans/{id}
Update an IBAN
updateIban1 parambody→ 200
Mandate signature requests 5
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 mand…
GET
/v2/mandate_signature_requests
List the mandate signature requests
listMandateSignatureRequests4 params→ 200
POST
/v2/mandate_signature_requests
Create a new mandate signature request
createMandateSignatureRequestbody→ 200
GET
/v2/mandate_signature_requests/{id}
Get a mandate signature request
getMandateSignatureRequest1 param→ 200
DELETE
/v2/mandate_signature_requests/{id}
Delete a mandate signature request
deleteMandateSignatureRequest1 param→ 200
POST
/v2/mandate_signature_requests/{id}/renewals
Renew a mandate signature request
renewMandateSignatureRequest1 param→ 200
Sandbox 2
Sandbox only endpoints.
POST
/v2/sandbox/incoming_collections
Simulate an incoming SEPA collection
createIncomingCollectionbody→ 204
POST
/v2/sandbox/incoming_transfers
Simulate an incoming SEPA transfer
createIncomingTransferbody→ 204
Transactions 2
Transactions are any debit and credit operations on an account. Note that the status of the transaction indicates whether or not it affects the account’s available balance. debit…
GET
/v2/transactions/{id}
Get a transaction
getTransaction1 param→ 200
GET
/v2/transactions
List all transactions
listTransactions11 params→ 200
Transfers 7
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…
GET
/v2/transfers/{id}
Get a transfer
getTransfer1 param→ 200
DELETE
/v2/transfers/{id}
Cancel a SEPA transfer
cancelTransfer1 param→ 200
POST
/v2/transfers
Initiate a SEPA transfer
createTransferV2body→ 200
POST
/v2/transfers/bulks
Create bulk transfers
createTransfersBulkbody→ 200
GET
/v2/transfers/{id}/proof
Generate a proof of transfer
getProofOfTransfer1 param→ 200
GET
/v2/transfers/bulks/{id}
Get a bulk and its current progress
getTransfersBulk1 param→ 200
GET
/v2/transfers/bulks/{id}/transfers
Get the status of individual transfers in a bulk
getTransfersBulkItems5 params→ 200
Webhooks 4
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://do…
GET
/v2/webhooks
List all webhooks
listWebhooks3 params→ 200
POST
/v2/webhooks
Create a webhook
createWebhookbody→ 200
GET
/v2/webhooks/{id}
Get a webhook
getWebhook1 param→ 200
DELETE
/v2/webhooks/{id}
Delete a webhook
deleteWebhook1 param→ 204
Wire Transfers 4
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 may…
POST
/v2/wire_transfers
Initiate a wire transfer
createWireTransferbody→ 200
POST
/v2/wire_transfers/{id}/attachments
Create an attachment to a wire transfer
createWireTransferAttachment1 parambody→ 201
GET
/v2/wire_transfers/{id}/proof
Generate a proof of wire transfer
getProofOfWireTransfer1 param→ 200
GET
/v2/wire_transfers/{id}
Get a wire transfer
getWireTransfer1 param→ 200
Schemas 119
The contract defines 119 schemas that model the data the API accepts and returns. The most detailed are Transaction (19 properties), TransferV2 (18 properties), Collection (16 properties), WireTransfer (14 properties). Each schema is shown below with its type and property counts.
PendingAccountAssessment
object
3 required
CreateAccountAssessment
object
2 properties1 required
Identification
object
LeiIdentification
object
2 required
NameIdentification
object
2 required
SirenIdentification
object
2 required
AccountAssessment
object
Capability
object
3 properties3 required
CompletedAccountAssessment
object
8 required
FailedAccountAssessment
object
4 required
IdentificationMatch
object
LeiIdentificationMatch
object
3 required
NameIdentificationMatch
object
3 required
SirenIdentificationMatch
object
3 required
Account
object
8 properties8 required
AccountPage
object
5 properties3 required
Attachment
object
7 properties7 required
AttachmentPage
object
5 properties3 required
Collection
object
16 properties8 required
CollectionMandate
object
The SEPA Direct Debit collection mandate used.
2 properties2 required
CollectionMandateDebtor
object
The debtor associated with this mandate.This field is only required in case of a new mandate. If there is an existing mandate with this reference and scheme, a…
3 properties2 required
CollectionMandateDebtorAddress
object
The debtor's address. Mandatory only when the debtor's bank — more specifically, its BIC — is located in a non-EEA SEPA country or territory.
5 properties4 required
CreateCollection
object
9 properties4 required
CreateCollectionMandate
object
The SEPA Direct Debit collection mandate to be used.
5 properties2 required
BulkCollections
object
6 properties6 required
CreateBulkCollections
object
1 property1 required
CollectionPage
object
5 properties3 required
Iban
object
8 properties8 required
CreateIban
object
3 properties2 required
IbanPage
object
5 properties3 required
UpdateIban
object
4 properties
Address
object
Debtor's address.
4 properties4 required
EmailMandateSignatureRequest
object
8 required
MandateSignatureRequest
object
MandateSignatureRequestDebtor
object
Debtor information filled when the request was signed. This is available when the request is completed.
3 properties2 required
RedirectMandateSignatureRequest
object
10 required
CreateEmailMandateSignatureRequest
object
4 required
CreateMandateSignatureRequest
object
CreateMandateSignatureRequestDebtor
object
Debtor data used to prefill the signing form. All fields are optional; the debtor can still edit them before signing.
3 properties
CreateMandateSignatureRequestDebtorAddress
object
Debtor address used to prefill the signing form. All fields are optional.
4 properties
CreateRedirectMandateSignatureRequest
object
5 required
MandateSignatureRequestPage
object
5 properties3 required
CreateIncomingCollection
object
5 properties2 required
CreateIncomingCollectionMandate
object
The SEPA Direct Debit collection mandate. Allow you to provide mandate information that will be used for the transaction. If not provided, default values will…
2 properties
CreateIncomingCollectionMandateCreditor
object
The creditor associated with this mandate.
3 properties
CreateIncomingTransfer
object
6 properties2 required
BankAccountRemunerationSource
object
1 required
CardCreditSource
object
3 required
CardDebitSource
object
3 required
CardDeferredSource
object
1 required
CardWithdrawalSource
object
3 required
CollectionIncomingReturnSource
object
2 required
CollectionIncomingSource
object
1 required
CollectionOutgoingReturnFeesSource
object
3 required
CollectionOutgoingReturnSource
object
3 required
CollectionOutgoingSource
object
2 required
DebtPurchaseApplicationFeesSource
object
1 required
DebtPurchaseDisbursementSource
object
1 required
DebtPurchaseInterestsSource
object
1 required
DebtPurchaseRepaymentSource
object
1 required
DiverseOperationSource
object
1 required
InvestmentRedemptionOrderDTO
object
1 required
InvestmentSubscriptionOrderDTO
object
1 required
LoanApplicationFeesSource
object
1 required
LoanDisbursementSource
object
1 required
LoanGuaranteeFeeSource
object
1 required
LoanReimbursementSource
object
1 required
LoanRepaymentSource
object
1 required
MaintenanceTransferSource
object
1 required
MaintenanceWireTransferSource
object
1 required
OverdraftAgiosSource
object
1 required
OverdraftApplicationFeesSource
object
1 required
RtgsTransferIncomingReturnSource
object
4 required
RtgsTransferIncomingSource
object
2 required
RtgsTransferOutgoingReturnSource
object
4 required
RtgsTransferOutgoingSource
object
2 required
SubscriptionSource
object
1 required
SweepTransferIncomingSource
object
3 required
SweepTransferOutgoingSource
object
3 required
TermDepositClosureSourceDTO
object
1 required
TermDepositCreationSourceDTO
object
1 required
TermDepositInterestPaymentSourceDTO
object
1 required
TermDepositWithdrawalSourceDTO
object
1 required
Transaction
object
19 properties14 required
TransactionSource
object
Source of the transaction. We may add additional source types over time; your application should be able to handle such additions gracefully.
TransferIncomingReturnSource
object
3 required
TransferIncomingSource
object
2 required
TransferOutgoingReturnSource
object
4 required
TransferOutgoingSource
object
3 required
WireTransferIncomingSource
object
3 required
WireTransferOutgoingReturnSource
object
2 required
WireTransferOutgoingSource
object
4 required
TransactionPage
object
5 properties3 required
Transfer
object
11 properties9 required
CreateTransfer
object
8 properties4 required
TransferV2
object
18 properties8 required
CreateTransferV2
object
12 properties3 required
TransferBeneficiaryAddress
object
Address of the beneficiary. Will be used to create the beneficiary if one doesn't already exist with the same accountidentifier, will be ignored otherwise.
4 properties4 required
BulkTransfers
object
6 properties6 required
CreateBulkTransfers
object
1 property1 required
TransferV2Page
object
5 properties3 required
Event
object
5 properties5 required
Webhook
object
4 properties4 required
CreateWebhook
object
2 properties2 required
WebhookPage
object
5 properties3 required
AccountIdentifier
object
Account identifier of the beneficiary.
AccountNumberAndBic
object
3 required
AccountNumberAndRoutingCode
object
3 required
IbanAndBic
object
3 required
WireTransfer
object
14 properties8 required
CreateWireTransfer
object
9 properties6 required
TransferBeneficiary
object
Information regarding the beneficiary of this wire transfer.
6 properties5 required
IdentificationDiscriminator
object
2 properties1 required
AccountAssessmentDiscriminator
object
3 properties3 required
IdentificationMatchDiscriminator
object
2 properties2 required
MandateSignatureRequestDiscriminator
object
10 properties8 required
CreateMandateSignatureRequestDiscriminator
object
7 properties4 required
TransactionSourceDiscriminator
object
1 property1 required
AccountIdentifierDiscriminator
object
1 property1 required
Specification
The full machine-readable OpenAPI contract behind this narrative.
Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.
Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.
MCP tools for apis
4 tools reach this content
search_api_evangelistSearch every content type across the network at once.
find_relatedThe shared-tag relevance graph — what else covers this.
get_tagEverything one tag labels, across all content types.
guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
A second provider on the same verified email joins the account you already have.
Your account
ⓘWhere this information came from
This is an independent, third-party profile of Memo Bank Premium Bank 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.