-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to retrieve fee component of a payment. #15
Comments
We checked with our internal team and got a information that it was intentionally removed in our API for Amazon Pay version 2. We will introduce the parameter capturefee in SDK , once our backend API is enabled with response updated with field capturefee |
ThankYou for looking into it. Do you have a rough time frame for when it might be available? |
We checked with our internal team and currently there is no time frame to commit. We will keep updated once the task is prioritised by our internal team |
Thanks for the update. |
By any slim chance, is this likely to happen this year? |
So apparently the v1 API will no longer be usable after ~April 2025. Is there any chance we'll be able to retrieve the fee component of a sale before the old API which does provide this information is turned off? |
As per #14, the 'new' Amazon Pay API apparently provides no way to retrieve the fee that was charged to process a given payment.
This information was available via previous Amazon Pay APIs, and is seemingly still available via those APIs, for payments made via the new API. Given that I've seen multiple suggestions/warnings not to make use of both APIs concurrently for charging customers, It seems extremely odd that the only way to retrieve the fee information currently, is to use both APIs/SDKs - one for creating and checking the charge, and then a different one to retrieve the fee.
I opened issue #14 about this previously, and it was summarily closed by someone who either didn't read what I'd written or didn't comprehend what I was asking about.
The text was updated successfully, but these errors were encountered: