Herewith is an example of encoding to and from base64 using OpenSSL's C library. Code presented here is both binary safe, and portable (i.e. it should work on any Posix compliant system e.g. FreeBSD and Linux).
The MIT License (MIT)
Copyright (c) 2013 Barry Steyn
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Base64Decode cuts 2 characters off on this data:
eyJzdWIiOiIwMHVibHVvazVsVXloWVd3STVkNyIsIm5hbWUiOiJPbGVuYSBZYXJ1dGEiLCJ2ZXIiOjEsImlzcyI6Imh0dHBzOi8vZGV2LTY5Nzk4NzYyLm9rdGEuY29tIiwiYXVkIjoiMG9hYjF1dDkyeTRKY201MXo1ZDciLCJpYXQiOjE2OTU5MDMzNDgsImV4cCI6MTY5NTkwNjk0OCwianRpIjoiSUQudmJjeHJxOEljQW1SNkprb0E4OEdsaDE4THBvYUZTaURHZDJIT1prTUhnUSIsImFtciI6WyJwd2QiXSwiaWRwIjoiMDBvODVzdHcwY1R3bzNGYzk1ZDciLCJwcmVmZXJyZWRfdXNlcm5hbWUiOiJvbGVuYS55YXJ1dGFAYXZpZC5jb20iLCJhdXRoX3RpbWUiOjE2OTU5MDIxNjEsImF0X2hhc2giOiJfMHJZV0tzRUhwV3lRc1o4enVuMmtRIn0
The issue is in the OpenSSL library, most likely. I use OpenSSL 3.0.2 15 Mar 2022 (Library: OpenSSL 3.0.2 15 Mar 2022)
UPD:
It appeared that the encoded string must have '=' padding at the end which I did not receive from the external service.
Maybe it is worth adding some kind of normalization for b64message buffer to fix missing paddings.
I would add to the beginning of Base64Decode something similar to this: