Requesting support for instructionUUID in PaymentRequest v2

[kunambi]

Recently started working with this app and it seems very strong while also making the workflow very easy 👍🏾

However, reading through the code it seems that you're currently using PaymentRequest v1 instead of v2.

It shouldn't be too hard to switch between v1 and v2—one could check the existence for a instructionUUID-kwarg when initializing swish.SwishClient.

The major differences between v1 and v2 are explained on page 18 in MSS_UserGuide_2_0.pdf (you can find it at https://developer.swish.nu/documentation/environments#certificates, download the ZIP-files with the certificates)

One of the differences between v1 and v2 seems to be what the API returns, both to the calling SwishClient, but also the POST to the callbackURL (according to their docs).

TYIA

[cthart]

Any chance you can write the code and submit a PR?

[kunambi]

Hi,

The client of the project took a different route, and rather than implementing the payment solution directly through Swish they chose to use a Payment Solution Provider instead. We're currently not using this application any longer.