Add SaleToAcquirerDataSerializer deserialisation

[scriptease]

Description
Adds missing deserialization of SaleToAcquirerData for SaleToPOIResponses, e.g. when using the payment provider Twint in Switzerland

Tested scenarios

• Base 64 Encodeded SaleToAcquirerData was parsed correctly.

Fixed issue: #1037

[jillingk]

Hi @scriptease,

Thanks a lot for taking the time to contribute! Quick question, what kind of request did Twint send to get a SaleToAcquirerData object back in the response? I'm asking because I haven't seen this field in a response before so I just wanted to double check we actually do need to deserialize this.

Your PR looks all good though! Maybe a unit test would be nice, but I can help you with that as well.

Best, Jilling
Adyen

[scriptease]

It happened in live/production so I don't think I can share the whole response here, however the base64 and the decoded version is just meta data with a applicationInfo.

      "SaleData" : {
        "SaleTransactionID" : {
          "TransactionID" : "...",
          "TimeStamp" : "2023-04-15T14:13:07.000Z"
        },
        "SaleToAcquirerData" : "ewogICJhcHBsaWNhdGlvbkluZm8iOiB7CiAgICAiYWR5ZW5MaWJyYXJ5IjogewogICAgICAibmFtZSI6ICJhZHllbi1qYXZhLWFwaS1saWJyYXJ5IiwKICAgICAgInZlcnNpb24iOiAiMTcuMC4wIgogICAgfQogIH0KfQ=="
      },

{
  "applicationInfo": {
    "adyenLibrary": {
      "name": "adyen-java-api-library",
      "version": "17.0.0"
    }
  }
}

But in my option the model should be transitive in any way, so that a SaleToPOIResponse can be serialized and deserialized without an exception caused by the missing inverse operation in SaleToAcquirerDataSerializer.

In our own unit test the twint response can now be deserialized, serialized and are equal to the original afterwards.

[scriptease]

I just wanted to double check we actually do need to deserialize this.

We could also ignore it using @ Expose while parsing the json, but without the fix it throws a json processing exception which prohibited us from processing payments, so we already created our own bugfix release and deployed it.

I created the ticket & pr mostly for fellow developers that might run into a similar edge case, I never heard about twint before investigating the issue.

[jillingk]

Okay makes sense to me, I'll approve it. I think in the past we would not encounter these responses, hence why we didn't have this yet. Thanks again for the quick PR!