An idempotence parameter is missing in the Payment.create () function / request ( https://en.wikipedia.org/wiki/Idempotence ). This could, for example, be an internal ID for a refund. It is now not possible to prevent the payment from being sent multiple times in the case of a retry. Can this be added?
Bitqist-B-V-Violet-Leopard If you use the same X-Bunq-Client-Request-Id, the second call should be rejected.
Does not seem to work. For payment id 136606273 and 136606521, exactly the same value X- Bunq Client-Request-Id was given without the 2nd payment being rejected.
Bitqist-B-V-Violet-Leopard can you report this, including both Request-Ids to support. They might be able to see more details. The API should block non-unique request IDs for your user (I’m assuming you’re not using different users/keys). 🙂
Sander Pretty sure that has been broken for a while now, I've reported it before at some point. Right now I can change my client to use the exact same ID and it works fine:
Sander Support says its out of their scope and that I should post the bug on together to get a response from the developers. In our opinion this is a major bug and hence should be fixed asap.
Bitqist-B-V-Violet-Leopard After your first post I've immediately contacted our contact person at bunq and he said the team was checking it out. I agree this sounds like a pretty nasty bug. But I'm sure they'll check it out as soon as possible. I'm not sure why support said it is out of their scope. But it has been reported anyway. 🙂
As Sander is well mentioning , our team is aware of this and they're currently working on a fix. As soon as we have any news we'll make sure to update this post 👍
Have a good evening 🌈
Raul- Together Sander, can you give us an update on the progress?
Bitqist-BV-Violet-Leopard I am not a bunq employee. So unfortunately I can't. bunq will update this topic automatically if there is an update. 🙂
Has this bug been fixed? We are now 5 months further. It seems to me that it should be quite high on the price list.