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 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.They can be initiated asynchronously, one by one or in bulk. Unlike [transfers](#endpoint-transfers), collections can only be scheduled for a date in the future. As a result, their lifecycle is also simplified.
Memo Bank Collections 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 Collection. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a getting-started guide.
This API exposes 6 operations across 5 paths, and defines 9 schemas. It is described by OpenAPI 3.2.0, at version 2.0.
Requests are made against 2 base URLs: https://api.memo.bank, https://api.sandbox.memo.bank.
Metadata
The identity and technical contract details declared by the specification.
Paths & Operations 6
Across 5 paths, the API surfaces 6 operations — 1 DELETE, 3 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.
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…
Schemas 9
The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are Collection (16 properties), CreateCollection (9 properties), BulkCollections (6 properties), CollectionMandateDebtorAddress (5 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Memo Bank 12
Other APIs Memo Bank publishes across the network.
This is an independent, third-party profile of Memo Bank Collections 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.