Add VED (Venezuelan Bolívar Digital) and remove obsolete VEF/VES currency codes

[ginoijewels]

Description

Venezuela has undergone multiple currency redenominations. Magento currently
includes outdated Venezuelan currency codes that are no longer legal tender,
while the current official currency is missing entirely.

Current State in Magento

Code	Name	Status
VEF	Venezuelan Bolívar Fuerte	❌ Obsolete — discontinued August 2018
VES	Venezuelan Bolívar Soberano	❌ Obsolete — discontinued October 2021
VED	Venezuelan Bolívar Digital	✅ Current legal currency since October 2021

Request

1. Add VED (Venezuelan Bolívar Digital) to the list of supported
   currencies in Magento.
2. Deprecate or remove VEF and VES as they are no longer valid
   currencies under Venezuelan law.

References

• Banco Central de Venezuela official announcement:
  https://www.bcv.org.ve
• ISO 4217 currency code for VED:
  https://www.iso.org/iso-4217-currency-codes.html
• Venezuela redenominated its currency on October 1, 2021, removing six
  zeroes from VES to create VED. 1 VED = 1,000,000 VEF.

Impact

Merchants operating in Venezuela cannot correctly configure their store
currency. This causes silent failures in shipping carrier integrations and
payment gateways that rely on the current ISO currency code VED, as
Magento resolves exchange rate lookups to 0 when the requested code
does not exist in the system.

Suggested Change

In lib/internal/Magento/Framework/Locale/ or the equivalent currency
data source, update the Venezuelan currency entry:

• Remove: VEF, VES
• Add: VED — Venezuelan Bolívar Digital (ISO 4217)

Expected behavior

Magento should include VED (Venezuelan Bolívar Digital) as a supported
currency and remove the obsolete VEF and VES codes, which have not been
legal tender since 2018 and 2021 respectively.

Merchants operating in Venezuela should be able to select VED as their
store currency or configure exchange rates against it, just as they can
with any other current ISO 4217 currency.

Benefits

• Venezuelan merchants can correctly configure their store currency without
  workarounds.
• Shipping carrier and payment gateway integrations that rely on the current
  ISO code VED will resolve exchange rates correctly instead of silently
  returning zero.
• Removes confusion caused by two deprecated currency codes (VEF, VES)
  that no longer exist in the Venezuelan financial system.
• Brings Magento into compliance with the current ISO 4217 standard for
  Venezuelan currency.

Additional information

Venezuela has redenominated its currency twice since 2008:

• VEF (Bolívar Fuerte): valid until August 20, 2018
• VES (Bolívar Soberano): valid August 2018 – October 1, 2021
• VED (Bolívar Digital): current official currency since October 1, 2021
  (1 VED = 1,000,000 VEF)

Official source: Banco Central de Venezuela — https://www.bcv.org.ve
ISO 4217 reference: https://www.iso.org/iso-4217-currency-codes.html

This issue was discovered while integrating a Venezuelan shipping carrier
(Zoom International Services C.A.) with a Magento 2 store. The carrier API
returns prices in VES/VED but Magento only offers VEF in the currency
selector, causing exchange rate lookups to return 0 and breaking shipping
rate calculation at checkout.

Release note

Updated Venezuelan currency support: added VED (Bolívar Digital, current
ISO 4217 code), deprecated VEF and VES (obsolete codes no longer recognized
as legal tender in Venezuela).

[m2-assistant]

Hi @ginoijewels. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[github-jira-sync-bot]

✅ Jira issue https://jira.corp.adobe.com/browse/AC-16831 is successfully created for this GitHub issue.

[m2-assistant]

Hi @engcom-Bravo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Bravo]

Hi @ginoijewels,

Thanks for your reporting and collaboration.

Marking this as a Feature Request.

Thanks.