Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Return pspReference and refusalReason in onPaymentCompleted callback

See original GitHub issue

Is your feature request related to a problem? Please describe. My payment workflow implementation relies on pspReference field returned by /payments request when payment completes. Since adyen-web starting from v 5.0.0 has simplified workflow which performs /payments request under the hood, I cannot obtain pspReference any more. The same for refusalReason field when resultCode is Refused.

Describe the solution you’d like onPaymentCompleted callback should return pspReference along with the resultCode field as it was in previous versions. It should return refusalReason as well when resultCode is Refused.

Issue Analytics

State:
Created 2 years ago
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

ahimikcommented, Dec 22, 2021

I’ve checked it again and it seems like metadata problem is fixed now:

Checkout API (all versions)
Fixed
We fixed an issue where the 3D Secure 2 flow could break when receiving an unsupported screen.colorDepth value on Google Chrome v83 or v84.
We fixed an issue where metadata was not being sent back in the notification webhook.

Since the bug is fixed I’ll follow your suggestions and use merchantOrderReference instead of pspReference and show some generic message in a case of payment rejection. Thank you.

0reactions

ribeiroguilhermecommented, Dec 27, 2021

You are welcome @ahimik 👍

Top Results From Across the Web

Refusal reasons - Adyen Docs

refusalReasonCode refusalReason Description 2 Refused The transaction was refused. 3 Referral Referrals. 8 Invalid Card Number The specified card number is incorrect or invalid.