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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Enable Banking

Enable Banking Payments API

The Payments API from Enable Banking — 3 operation(s) for payments.

Documentation Provider Profile APIs.io OpenAPI GitHub

Enable Banking Payments API is one of 4 APIs that Enable Banking publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 4 JSON Schema definitions.

Tagged areas include Payments. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a getting-started guide, a JSON-LD context, pricing, an engineering blog, and 4 JSON Schemas.

This API exposes 4 operations across 3 paths, and defines 43 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0-3030f99c.

Requests are made against 2 base URLs: https://api.enablebanking.com, https://api.tilisy.com.

4 operations 3 paths 43 schemas 1 DELETE2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0-3030f99c
Base URL
https://api.enablebanking.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Enable Banking Payments API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — In order to get access to this API you need to: - Generate a private RSA key and a self-signed certificate; - Upload the certificate to enablebanking.com and g…

Paths & Operations 4

Across 3 paths, the API surfaces 4 operations — 1 DELETE, 2 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Payments 4
POST
/payments
Create payment
create_payment_payments_post body → 200400401403404408422429
GET
/payments/{payment_id}
Get payment
get_payment_payments__payment_id__get 1 param → 200400401403404408422429
DELETE
/payments/{payment_id}
Delete payment
delete_payment_payments__payment_id__delete 1 param → 200400401403404408422429
GET
/payments/{payment_id}/transactions/{transaction_id}
Get payment transaction
get_payment_transaction_payments__payment_id__transactions__transaction_id__get 2 params → 200400401403404408422429

Schemas 43

The contract defines 43 schemas that model the data the API accepts and returns. The most detailed are CreditTransferTransactionDetails (14 properties), CreditTransferTransaction (12 properties), CreatePaymentRequest (11 properties), PostalAddress (10 properties). Each schema is shown below with its type and property counts.

StatusReasonInformation
object
2 properties 2 required
PSUType
string
PaymentRequestResource
object
9 properties 1 required
PostalAddress
object
10 properties
ContactDetails
object
2 properties
RequestedExecutionDate
string
Date at which the initiating party requests the clearing agent to process the payment. API: This date can be used in the following cases: - the single requeste…
PaymentRequestResourceDetails
object
9 properties
ErrorCode
string
ChargeBearerCode
string
PurposeCode
string
FinancialInstitutionIdentification
object
3 properties
PaymentTypeInformation
object
4 properties
RegulatoryReportingDetails
object
3 properties 1 required
CreditTransferTransactionDetails
object
Details of the payment instruction executed (to be executed) by the ASPSP
14 properties 2 required
ClearingSystemMemberIdentification
object
2 properties
ErrorResponse
object
4 properties 1 required
PartyIdentification
object
5 properties
PaymentInformationId
string
Reference assigned by a sending party to unambiguously identify the payment information block within the message.
PriorityCode
string
FrequencyCode
string
ReferenceNumber
string
This field specifies the reference assigned by the sender to unambiguously identify the message.
CategoryPurposeCode
string
PaymentType
string
SuccessResponse
object
1 property
GenericIdentification
object
3 properties 2 required
CreatePaymentRequest
object
11 properties 6 required
GetPaymentTransactionResponse
object
2 properties 2 required
AmountType
object
2 properties 2 required
ServiceLevelCode
string
ExecutionRule
string
RegulatoryAuthority
object
2 properties 2 required
RegulatoryReporting
object
2 properties 1 required
PaymentIdentification
object
2 properties
ASPSP
object
2 properties 2 required
CreatePaymentResponse
object
4 properties 4 required
UnstructuredRemittanceInformation
array
Payment details. For credit transfers may contain free text, reference number or both at the same time (in case Extended Remittance Information is supported).…
GetPaymentResponse
object
8 properties 7 required
SchemeName
string
CreditTransferTransaction
object
Payment instruction to be executed by the ASPSP
12 properties 2 required
Beneficiary
object
4 properties 1 required
EndDate
string
The last applicable day of execution for a given standing order. If not given, the standing order is considered as endless.
AddressType
string
PaymentStatus
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

enable-banking-payments-api-openapi.yml Raw ↑

Other APIs Enable Banking publishes across the network.

Enable Banking Accounts data API
AE Profile APIs.io
Enable Banking Misc API
AE Profile APIs.io
Enable Banking User sessions API
AE Profile APIs.io
#Payments
← Back to E APIs
API Details
ID
enable-banking:enable-banking-payments-api
Base URL
https://api.enablebanking.com
Docs
https://enablebanking.com/docs/api/reference/
Provider
Enable Banking
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

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.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=enable-banking-payments-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/enable-banking-payments-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

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 Enable Banking Payments 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.