iBanFirst Payments API
Sending funds from one of your iBanFirst accounts to your own external bank account or a third-party recipient involves two steps:1. Generate the payment object with the 'Create payment' method. A unique id is assigned to each payment. 2. Use the 'Confirm Payment' method to send the payment for processing. When you confirm a payment, make sure you have sufficient funds in your account balance. **Caution:** Payments are automatically rolled to the next closest working days if not confirmed in the scheduled date of operation. If the balance of your account is not sufficient to cover the payment amount, funds may be locked-in by iBanFirst.
iBanFirst Payments API is one of 11 APIs that iBanFirst publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Payments. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, and authentication docs.
This API exposes 7 operations across 6 paths, and defines 15 schemas. It is described by OpenAPI 3.2.0, at version 1.6.0.
Requests are made against a single base URL, https://api-demo.ibanfirst.com/api.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
iBanFirst Payments API declares
1 security scheme
for authenticating requests.
An API key is passed in the header as X-WSSE (X-WSSE).
By default, every request must be authenticated.
X-WSSE— X-WSSE token-based authentication. The header value must be computed fresh for every request (tokens expire in ~5 minutes). Header value format: UsernameToken…
Paths & Operations 7
Across 6 paths, the API surfaces 7 operations — 1 DELETE, 3 GET, 1 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.
Sending funds from one of your iBanFirst accounts to your own external bank account or a third-party recipient involves two steps: 1. Generate the payment object with the 'Create…
Schemas 15
The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are PaymentVOP (18 properties), Payment (17 properties), Rate (7 properties), ErrorVOP (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 iBanFirst 10
Other APIs iBanFirst publishes across the network.
This is an independent, third-party profile of iBanFirst 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.