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

Bancontact Merchant Acknowledge API

The Merchant Acknowledge API from Bancontact — 1 operation(s) for merchant acknowledge.

Bancontact Merchant Acknowledge API is one of 8 APIs that Bancontact publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Merchant Acknowledge. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 1 operation across 1 path, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 3.6.5.

Requests are made against 2 base URLs: https://merchant.api.preprod.bancontact.net, https://merchant.api.bancontact.net.

1 operations 1 paths 4 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.6.5
Base URL
https://merchant.api.bancontact.net
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

Bancontact Merchant Acknowledge API declares 2 security schemes for authenticating requests. An API key is passed in the header as Authorization (api_key_payment_profile). An API key is passed in the header as Signature (JWS-Request-Signature-Payment). By default, every request must be authenticated.

  • api_key_payment_profile — Bearer authentication with API Key generated by API Manager. Used to get/create payments for a specific Merchant Profile or create refunds for a specific payme…
  • JWS-Request-Signature-Payment — [Detached JWS signature of response payload](https://tools.ietf.org/html/rfc7797). Bancontact Company hosts the certificates in [JWK format](https://tools.ietf…

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.

Merchant Acknowledge 1
POST
/v3/payments/{id}/acknowledge
Merchant acknowledges payment status callback was received
merchant-acknowledge 1 param body → 202400401403404422500503

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are error (4 properties), merchant-acknowledge (3 properties). Each schema is shown below with its type and property counts.

merchant-acknowledge
object
3 properties 2 required
payment_amount
integer
Amount in cents requested
currency
string
Currency code. Only EUR is supported [ISO 4217](http://en.wikipedia.org/wiki/ISO4217)
error
object
error response received from server
4 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bancontact-merchant-acknowledge-api-openapi.yml Raw ↑

Other APIs Bancontact publishes across the network.

Bancontact Callback to Merchants API
Bancontact Merchant Endpoints API
Bancontact Payments API
Bancontact Payout List API
Bancontact Payout Payments API
Bancontact Payout Refunds API
Bancontact Refunds API
Where this information came from

This is an independent, third-party profile of Bancontact Merchant Acknowledge 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.