Menu
Feedback
Start here
Tutorials
Developer portal

Known Issues
Support Rules
Troubleshooting

Frequently Asked Questions
Announcements
Known issues
Lack of phone number validation in the purchase APIs allowing invalid data in the orders
Lack of phone number validation in the purchase APIs allowing invalid data in the orders
ID: 680500
Backlog
Published on 10/18/2022
Last update on 11/25/2022

Summary

The validation of a phone number is restricted to the form where it's inserted or edited through the interface in the checkout profile step. Values inserted directly through the REST APIs to an orderForm or to an order, or which came from the customer profile (which, in their way, can be inserted through different ways) aren't validated by the platform.

Due to the nature of these flows, origins inserting invalid values can't be traced back.

Simulation

  • create a cart
  • advance until the payment step
  • change the "phone" property from the "clientProfileData" section from an orderForm through API to an invalid value
  • finish the purchase

The order will be created with the invalid phone number without further validations.

Workaround

The phone number should be validated on the client side, like in the user interface, their custom functions, or any middleware or backend that does these requests to the orderForm and order REST APIs or feeds the customer profile in the Profile System/Master Data services.

Contributors
2
Photo of the contributor
Photo of the contributor
+ 2 contributors
Contributors
2
Photo of the contributor
Photo of the contributor
+ 2 contributors
On this page
Still got questions?
Ask the community
Find solutions and share ideas in the VTEX community.
Join our community
Request support from VTEX
For personalized assistance, contact our experts.
Open a support ticket
GithubDeveloper portalCommunityFeedback