If transaction signing is enabled, the creation of new payments fails

[maephisto666]

In case you are ingesting data to an environment where Transaction Signing is enabled, the creation of the payments via the POST API call will fail returning a 401 error that will consequently trigger an exception.

The body of the response in this case is something like the following

{
    "challenges": [
        {
            "challengeType": "reauth",
            "acrValues": "txn-signature-silver txn-signature-gold",
            "scope": "confirmation:826ab759-4b09-4a04-9c32-2fca4c78fa9e"
        }
    ],
    "data": {
        "payment-order-id": "8faf435f-8924-40a9-958f-bfa5ae3811fb",
        "amount": "72605.20",
        "paymentAmount": "72605.20",
        "currency": "EUR",
        "counter-party-account": "GB50HPZT11731526136460",
        "counter-party-name": "Dominique Rogahn Sr.",
        "confirmation-type": "initiate-payment"
    }
}

It would be ideal to enable the support for transaction signing via bb-fuel, enabling bb-fuel to generate the required OTP for the payments to be ingested.