When using the Simple API, the caller needs to pass buffers in order to retrieve output. As the length of the output varies, we need to choose a buffer that is large enough for the resulting content. Based on different data scenarios we came up with the following recommendations regarding buffer sizes.
If an output buffer is not large enough to write the output into it, a corresponding message is written to the message buffer. Therefore make sure to always provide a message buffer.
| Output Type | Size | Output Format | Recommended Output Buffer Size * |
|---|---|---|---|
Payment Part & Receipt |
DIN_LANG, A5, A4 |
100 kb (100000 bytes) |
|
Payment Part & Receipt |
DIN_LANG |
PNG |
150 kb (150000 bytes) for 150 DPI
300 kb (300000 bytes) for 300 DPI
1000 kb (1000000 bytes) for 600 DPI |
Payment Part & Receipt |
A5 |
PNG |
200 kb (200000 bytes) for 150 DPI
400 kb (400000 bytes) for 300 DPI
1000 kb (1000000 bytes) for 600 DPI |
Payment Part & Receipt |
A4 |
PNG |
250 kb (250000 bytes) for 150 DPI
450 kb (450000 bytes) for 300 DPI
1000 kb (1000000 bytes) for 600 DPI |
Payment Part & Receipt |
DIN_LANG |
JPEG |
750 kb (750000 bytes) for 150 DPI |
Payment Part & Receipt |
A5 |
JPEG |
800 kb (800000 bytes) for 150 DPI |
Payment Part & Receipt |
A4 |
JPEG |
1 mb (1000000 bytes) for 150 DPI |
QR Code |
~500 pixels |
PNG |
25 kb (25000 bytes) |
SPC |
- |
TXT |
2 kb (2000 bytes) |
IBAN, QR Reference, Creditor Reference (for utility functions) |
- |
TXT |
0.5 kb (500 bytes) |
May be larger and if size matters here, also slightly smaller. In this case you would need to determine the size for your specific use case (output size, format, data).