Skip to content

Payment V3 API (3.6.3)

APIs intended to support the merchant/partner's payment flow on creation, cancellation, search and refunds.

History

3.6.3 (2025-08-26)

  • Added JWS-Request-Signature-Payment for all payment call.

3.6.2 (2025-08-22)

  • Modified description by adding the SEPA requirements allowed character sets.
  • Modified reference by adding the SEPA requirements allowed character sets.
Download OpenAPI description
merchant-payment.openapi.json
merchant-payment.openapi.yaml
Languages
Servers
Mock server

https://docs.payconiq.be/_mock/apis/merchant-payment.openapi/

PREPROD merchant API

https://merchant.api.preprod.bancontact.net/

PROD merchant API

https://merchant.api.bancontact.net/

Merchant Endpoints

Operations

Callback to Merchants

Operations

Merchant Acknowledge

Operations

Refunds

Operations

get debtor's refund IBAN

Request

This endpoint returns the debtor IBAN that the merchant can use to transfer the money directly. This process does not handle any money flow with the debtor.

The token/api-key necessary to call this endpoint must contain:

  • subjectType : "INTEGRATOR:{CCV_ID}" or "MERCHANT:{ID}"
  • resource: "PAYMENTPROFILE:{profileId}",
  • authority: MERCHANT_REFUND
  • Refunds are not allowed for P2P and PAYMENT_REQUEST
  • The payment specified should be in the SUCCEEDED state
  • The endpoint can be called multiple times by the Merchant, there's no restriction for that
Security
api_key_payment_profile or JWS-Request-Signature-Payment
Path
idstring= 24 charactersrequired

id of the payment for which to get the debtor's IBAN needed to refund

curl -i -X GET \
  'https://docs.payconiq.be/_mock/apis/merchant-payment.openapi/v3/payments/{id}/debtor/refundIban' \
  -H 'Authorization: YOUR_API_KEY_HERE'

Responses

The IBAN of the debtor used in the specified payment

Bodyapplication/json
ibanstringrequired

Debtor's IBAN

Response
application/json
{
  "iban": "BE12 3456 7890 1234"
}