Everything you need to integrate the Premium API and go live
The API connects your systems to your Memo Bank accounts: balances, SEPA and Swift transfers, direct debits, virtual IBANs and IBAN checks before paying. Here is what your teams need to scope and run the integration.
The sooner you integrate the API, the sooner your payments scale
With the Premium API, payments are initiated directly from your software, with no manual steps, so your volumes can grow without adding work. Over the past 12 months, 60% of our clients’ payments went through our premium API.
No customer integration has taken more than 20 days so far. Start with your most critical payment flow, then add the others one by one.
From project to production in 3 steps
1. Map your payment flows
List the payments you send and collect, their volumes and the systems they come from. Pick the most critical flow to start with: it will be the first one to run through the API.
2. Set up your access and test in the sandbox
Create one application for the sandbox and one for production, with only the permissions each needs. Then test your first flow, error cases included, with simulated transactions and test IBANs.
3. Go live and monitor your payment flows
Switch the validated flow to production, then add the others one by one. Webhooks report events in real time, and the public changelog and API status page keep you informed of changes and incidents.
Reference material
API documentation
Authentication, idempotent requests, errors, versioning and rate limiting.
API reference
Every endpoint with its parameters, request bodies and responses.
Changelog
Every change to the API, with breaking changes flagged, available by email or RSS.
Sandbox
A separate environment to test your flows with simulated transactions and test IBANs.
API status and incidents
Current status, average latency and incident history.
Prototype with AI
Business teams can ask an AI assistant to explain the documentation and the endpoints; developers can use it to prototype faster.
The documentation has its own MCP server, which tools such as Cursor or VS Code can query. It only reads the documentation.
Map your payment flows and choose the right rail for each
SEPA Instant (SCT Inst)
Standard SEPA (SCT)
T2 (RTGS)
Swift transfers
SEPA Direct Debit
Prevent fraud and failed payments
Counterparty account checks
Account assessments allow you to assess SEPA counterparty accounts before initiating transactions with them. An assessment provides:
1. Risk indicators: Detection of fraudulent activity, suspicious patterns, and other risk signals.
2. Identification matching: Verify that the account name or other identifiers match the value known by the account holder.
3. Account reachability: Information about which payment schemes are supported by the account holder.
One API for your accounts, payments and collections
Send your payments
Collect payments
Reconcile your accounts
Track and secure every transaction
01REST API, with the OpenAPI specification in JSON and YAML.
02Every request authenticated by a JWT signed with your private key.
03An idempotency-key header on all endpoints, to eliminate all risk of duplicate when retrying requests.
04Webhooks for every event, retried if your system is unavailable.
05Detailed rejection reasons returned by the API, so your system can handle each failure case.
06Versioned API: new features never break your integration. Breaking changes only come with a new version.
Reliable and controlled, at any volume
Built to run your payments at scale
Availability and response times measured on our production API. Once your payment flows run through the API, its availability directly affects your ability to pay suppliers, collect from customers and reconcile on time. Response times matter when payments are triggered from your own product, in front of your users.
- 99.9% SLA on Payments Scale subscriptions
- 99.96% API uptime since 2023 (<10 Hours over 3 years)
- Average API latency of about 50 ms over recent months
Separation of duties, set at application level
Each application receives only the permissions it needs. Viewing accounts and initiating payments can rely on separate credentials.
Application setup, permission modes and security settings.
API recipes
Each recipe walks through one use case step by step with the endpoints and events involved.
SEPA Transfer lifecycle: initiation, monitoring, and completion
Initiate a bulk and follow its execution progress
Initiate and follow up mandate signature requests
React to incoming transactions
Manage SEPA Direct Debit failures and returns
Wire transfer lifecycle: initiation, monitoring, and completion
