BMO EFT Payments API
Initiates Canadian Electronic Funds Transfer (EFT) credit and debit payments with live status updates and batch support (up to 50 payments), for business system integration. OAuth 2.0 plus client API key.
BMO EFT Payments API is one of 11 APIs that BMO publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Payments, EFT, and Canada. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.
This API exposes 4 operations across 4 paths, organized into 4 resource areas, and defines 2 schemas. It is described by OpenAPI 3.0.3, at version 2.2.5.
Requests are made against a single base URL, https://sandbox-open-api.bmo.com/open-banking/commercial-sb.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
BMO EFT Payments API declares
2 security schemes
for authenticating requests.
An API key is passed in the header as x-api-key (api_key).
It supports OAuth 2.0 (OAuth) using the authorizationCode flow, exposing 2 scopes.
Paths & Operations 4
Across 4 paths, the API surfaces 4 operations — 4 POST. They span 4 resource areas: Send Payment Credit, Send Payment Debit, Obtain Payment Status, Obtain Service Agreement List. Each is listed below with its method, path, parameters, and response codes.
Payment credit initiation which receives PAIN.001 ISO request as input and return PAIN.002 ISO as response
Payment credit initiation which receives PAIN.008 ISO request as input and return PAIN.002 ISO as response
Payment List which receives CAMT.005 ISO request as input and return PAIN.002 ISO as response.
Service agreement search which receives CustomerEntityId (proprietary) as input and return CustomerAgreementInfoReport (proprietary) as response
Schemas 2
The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are Problem (5 properties), SECURE (1 property). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from BMO 10
Other APIs BMO publishes across the network.
This is an independent, third-party profile of BMO EFT 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.