Reason when Checkout fails

[rivella50]

Hi there,

i wonder if the SumUp SDK is returning some sort of reason to this plugin when a checkout fails, and if yes, if that reason could be added into SumupPluginCheckoutResponse as a new field (and included in SumupPluginCheckoutResponse.fromMap(...))?
Best would be an enum with types like userAbortedPayment, wrongCurrency, amountTooSmall, etc.
At the moment the plugin only says that success is false which is quite a limited information and doesn't help much when trying to analyze problems around the payment process.

[sstasi95]

Hi,

Here you can find the SDK checkout response class documentation. Most of the interesting stuff is inside the additionalInfo dictionary, which is mapped in our SumupPluginCheckoutResponse, so all the informations should already be available in the response.

You can debug the example app in Xcode and put a breakpoint at line 80 of SwiftSumupPlugin.swift to see it yourself.

[rivella50]

I believe you, no problem.
But this means there is no chance to get the reason from a not successful checkout - which is quite weird in my opinion.
Does no one need this information? Either to show to the user as result or as a parameter for any sort of analysis.

[sstasi95]

Most of the errors are automatically shown to the user by the SDK, for example if you try to perform a checkout with an amount lower than the minimum allowed you will see an error screen, and the same happens for other errors. In this way the user should always have a visual feedback of the error, but I agree that an error code would be handy. The android SDK provides error codes.

[rivella50]

Ok that makes it a little bit better - at least for the user.
Regarding the error codes in the Android SDK: But your plugin doesn't map them neither...

[sstasi95]

Correct. See #26

[rivella50]

I've just filed an issue on the iOS SDK. Let's see what they say.