Incremental authorisation method Payments.increment doesn't expose idempotencyKey
jkowald-gc opened this issue · 2 comments
jkowald-gc commented
Unlike
Payments.request (body, idempotencyKey)
and
Payments.capture(paymentId, body, idempotencyKey)
the
Payments.increment(paymentId, body)
method doesn't allow specification of an idempotency key. Since the body contains an incremental authorisation amount, the effect of a replayed transaction is to double-increment.
Additionally, and differently from the documentation, the returned payment object doesn't contain reference, metadata or a status field (example attached)
ioan-ghisoi-cko commented
Thanks for raising this. I'll add a fix ASAP.
ioan-ghisoi-cko commented
Fixed in 2.0.3