For all payments made through Bancontact Bancontact Payconiq Acceptance Service, we ensure that funds are credited to your "Payout IBAN(s)" through means of a SEPA credit transfer. These payments are refered to as "Payouts".
Merchants can receive Payouts in two different ways:
- Bulked Payouts: all
SUCCEEDEDtransactions for the day are credited at once as a single-line item on your Payout IBAN. This payout is executed the working day after. - Individual Payouts: each individual
SUCCEEDEDtransaction is immediately credited as a single-line item on your Payout IBAN.
By default, all merchants are configured to have Bulked Payouts by default, except for our Invoice Product for which only Individual Payouts are supported.
Our Reconciliation API helps you reconcile and match the payouts credited in your account and with the transactions and refund operations they relate to. For more information refer to our Reconciliation Guide
Payment bulking can be done in two ways:
- Based on your product's Payout IBAN and Closing Time.
- Based on your product's Payout IBAN, Closing Time and a transaction Bulk ID.
The Closing Time is set by default to 00:00:00 (CET).
All SUCCEEDED transactions for the day (from the Closing Time to the Closing Time of the next day) are aggregated and credited into the merchant's Payout IBAN(s) on D+1. Transactions done on Friday, Saturday and Sunday follow the same logic, however payment execution may depend on the merchant's bank: in some instances Payouts may only be received on Monday or Tuesday.
All transactions are implemented by a credit transfer from the consumer's account to Bancontact Payconiq Company's Segregated account, from which they are further processed, depending on how the Payouts should be done (Bulked/Individual).
The remittance information (bank statement description) of Payouts has a maximum length of 140 charcaters, as standardized by the European Payments Council. In this section we will describe the remittance information structure as seen by:
- The merchant when receiving an individual payout
- The merchant when receiving a bulked payout
- The consumer when receiving a refund, when using our Refund API
Individual Payout will be used by default for the Invoice Product, which typically also requires structured remittance information. The content of the structured remittance information needs to be passed on over the Merchant API in the Reference element.
The information in the Reference element will be inpspected and depending on the type, will be added to the structured remittance of the SCT.
In case no Structured Reference is provided during transaction generation (cf.Invoices), the unstructured message in the individual payout will be composed as follows:
| Field Name | Description | Format |
|---|---|---|
Issuer | The entity that facilitates the Payment. | StringMax Length: 8 |
Delimiter | Field separator. | String: SpaceMax Length: 1 |
Payment ID | A unique identifier representing a Bancontact Payconiq Transaction. | StringMax Length: 24 |
Delimiter | Field separator. | String: SpaceMax Length: 1 |
Merchant Name | The name of the merchant where the Bancontact Payconiq Payment Transaction takes place. Padded with spaces if max length not reached. | StringMax Length: 23 |
Delimiter | Field separator. | String: SpaceMax Length: 1 |
Reference | A unique identifier referencing a Payconiq Payment Transaction in the merchant's system. . Padded with spaces if max length not reached. | StringMax Length: 31 |
Delimiter | Field separator. | String: SpaceMax Length: 1 |
Description | A description linked to a Bancontact Payconiq Transaction. Padded with spaces if max length not reached. | StringMax Length: 35 |
Payconiq f60454fd52e429d71964745d Online Kassa 4zyeYIKOw54Ybc9yenL5 Mars Bars The remittance information is formatted as a String.
| Field Name | Description | Value |
|---|---|---|
Timestamp | The start date of the bulk period YYYYMMDD | [0-9]{8} |
Delimiter | Field separator | - |
bulkPayoutId | A unique ID for this Bulk Payout | [0-9a-f]{24} |
Delimiter | Field separator | - |
BulkId | The transaction bulkID, as defined by the merchant NONE if no BulkID was defined | [0-9a-z]{1,35} |
Delimiter | Field separator | - |
BulkDescription | literal text to identify Bulk Payout | PQ-BulkRecon |
Delimiter | Field separator | - |
MerchantID | The identifier of the Merchant | [0-9a-f]{24} |
20250524-683241784f1c9078aa33d499-NONE-PQ-BulkRecon-62da9e5e8f5e0426fa2cf1b7
| Field Name | Description | Format |
|---|---|---|
Issuer | The entity that facilitates Bancontact Payconiq Payment. | StringMax Length: 8 |
Delimiter | Field separator. | String: SpaceMax Length: 1 |
RefundID | A unique identifier representing a Bancontact Payconiq Refund Transaction. | StringMax Length: 24 |
Delimiter | Field separator. | String: SpaceMax Length: 1 |
Creditor name | The name of the merchant where the Bancontact Payconiq Payment Transaction takes place. Padded with spaces if max length not reached. | StringMax Length: 23 |
Delimiter | Field separator. | String: SpaceMax Length: 1 |
Description | A description linked to a Bancontact Payconiq Refund Transaction. Padded with spaces if max length not reached. | StringMax Length: 31 |
Delimiter | Field separator. | String: SpaceMax Length: 1 |
Reference | A unique identifier referencing a Bancontact Payconiq Payment Transaction in the merchant's system. Padded with spaces if max length not reached. | StringMax Length: 35 |
Bancontact Payconiq 61f1204b4d07487d6ac57842 refund for Cookie Shop 8zyeAIKOt54Ybc3yfnL5 ref 2633686194