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 Endpoints API

The Merchant Endpoints API from Bancontact — 4 operation(s) for merchant endpoints.

Bancontact Merchant Endpoints 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 Endpoints. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 5 operations across 4 paths, and defines 20 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.

5 operations 4 paths 20 schemas 1 DELETE1 GET3 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 Endpoints 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 5

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

Merchant Endpoints 5
GET
/v3/payments/{id}
get a payment by id
merchant-get-payment 1 param → 200401403404429500503
DELETE
/v3/payments/{id}
cancel a payment
cancel_payment 1 param → 204401403404422429500503
POST
/v3/payments/search
search payments
search 2 params body → 200401403429500503
POST
/v3/payments
create a payment
create body → 201400401403404422429500
POST
/v3/payments/pos
create static qr payment
create_static_qr_payment body → 201400401403404422500503

Schemas 20

The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are get_payment_response (14 properties), static_qr_payment_create_request (11 properties), payment_create_response (10 properties), payment_create_request (9 properties). Each schema is shown below with its type and property counts.

currency
string
Currency code. Only EUR is supported [ISO 4217](http://en.wikipedia.org/wiki/ISO4217)
VoucherEligibleAmount
object
Defines an amount could be payed with proper voucher schemes
2 properties 2 required
PaymentSearchResponse
bulkId
string
Field used to reference a bulk batch, so the merchant can inform how the payments should be bulked. If it's not set here it will default to the one configured…
payment_create_request
object
Request to initiate/create a payment as a Merchant
9 properties 1 required
VoucherScheme
string
Voucher scheme (voucher type), has the form [alpha-3-country-code][identifier] currently known values: - BELMEALVOUCHER - BELECOVOUCHER - BELGIFTVOUCHER - BELC…
links
object
Provides information to navigate to our REST interfaces dynamically, by including hypermedia links to them. Note that for some links inclusion depends on the s…
6 properties 3 required
payment-search-query
object
4 properties
get_payment_response
object
Response containing information on the requested payment.
14 properties 8 required
payment_reference
string
Partner payment reference, used to reference the Bancontact Company payment in the partner's system
shopId
string
Id of the shop, where payment is created
link
object
1 property 1 required
payment_create_response
object
Object returned if the payment gets successfully created
10 properties 8 required
merchant-payment-status
string
| Status | Description | |--------|-------------| | PENDING | The merchant has created the payment and and is pending to proceed with identify step. | | IDENTI…
static_qr_payment_create_request
object
Request to initiate/create a static qr payment as a Merchant
11 properties 2 required
payment_description
string
Description of the payment that will be shown to the debtor, also used in the bank statement for reconciliation purposes. The characters used must comply with…
AbstractListResponsePayment
object
4 properties 4 required
error
object
error response received from server
4 properties 4 required
payment_creditor_response
object
Creditor account set to receive the payment
6 properties
posId
string
Merchant's point of sale identifier

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs Bancontact publishes across the network.

Bancontact Callback to Merchants API
Bancontact Merchant Acknowledge 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 Endpoints 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.