react-paypal-js
react-paypal-js copied to clipboard
[BUG]: AED Currency not working while integrating with braintree
Is there an existing issue for this?
- [X] I have searched the existing issues.
🐞 Describe the Bug
Hi all,
I integrated with braintree example and i set the currency AED. On official documentation of Braintree we checked it is accepting the currency AED. It was working fine, but from today morning it's stop working and when i click on the button I receive the below message. I am attaching the screenshot below
Any help will be appreciated
Thanks
** errorDetails : [{issue: "CURRENCY_NOT_SUPPORTED",…}] errorMessage : "The requested action could not be performed, semantically incorrect, or failed business validation. --- Currency code is not currently supported. Please refer https://developer.paypal.com/docs/integration/direct/rest/currency-codes/ for list of supported currency codes." errorName : "UNPROCESSABLE_ENTITY"**
😕 Current Behavior
No response
🤔 Expected Behavior
No response
🔬 Minimal Reproduction
No response
🌍 Environment
| Software | Version(s) |
| ---------------- | ---------- |
| react-paypal-js | |
| Browser | |
| Operating System | |
Relevant log output
No response
Code of Conduct
- [X] I agree to follow this project's Code of Conduct
➕ Anything else?
No response
You might want to look that: (To specify currencies in request URI and body parameters, use three-character ISO-4217 codes.
follow the link, https://en.wikipedia.org/wiki/ISO_4217#Active_codes
You might want to look that: (To specify currencies in request URI and body parameters, use three-character ISO-4217 codes.
follow the link, https://en.wikipedia.org/wiki/ISO_4217#Active_codes
I am using the same key as mentioned in the docs. AED for UAE currency
try to use numric key, 784 of iso code
try to use numric key, 784 of iso code
with numeric even though the button is not loading
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment!
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please create a new issue with up-to-date information. Thank you!