{"section":"known-issues","requestedLocale":"en","requestedSlug":"street-neighborhood-complement-and-reference-fields-are-not-requested-in-the-address-step-at-checkout","locale":"en","slug":"street-neighborhood-complement-and-reference-fields-are-not-requested-in-the-address-step-at-checkout","path":"docs/en/known-issues/Checkout/street-neighborhood-complement-and-reference-fields-are-not-requested-in-the-address-step-at-checkout.md","branch":"main","content":"## Summary\n\n\nWhen the address is entered via the postal code API and this data is updated in the shippingData before reaching the checkout. If our postal API doesn't return all the complete data, e.g. street, neighborhood, etc. They will be missing from shippingData. The problem is that when the customer uses the geolocation component in his checkout, he does not perform the missing validation of these fields, leaving the user to go to the payment step without filling in the data that is not complete.\n\n\n\n## Simulation\n\n\nMake the call to `api/checkout/pub/postal-code/BRA` informing the postal code `75345-000` before arriving at Checkout.\n\nUpdate the shippingData with the data that is returned from this API. When arriving at Checkout, the component will only ask to fill in the number and receiver field, thus allowing the user to go to the payment step with these missing data.\n\n\n\n## Workaround\n\n\nN/A"}