{"section":"known-issues","requestedLocale":"en","requestedSlug":"checkout-ui-allows-payment-with-incomplete-invoice-address-in-pickup-flow-inconsistent-invoicedata","locale":"en","slug":"checkout-ui-allows-payment-with-incomplete-invoice-address-in-pickup-flow-inconsistent-invoicedata","path":"docs/en/known-issues/Checkout/checkout-ui-allows-payment-with-incomplete-invoice-address-in-pickup-flow-inconsistent-invoicedata.md","branch":"main","content":"## Summary\n\n\nCheckout may proceed to the Payment step with an incomplete invoice address (invoiceData) when the shipping method is pickup. The visible symptom is an invoice address missing mandatory fields (e.g., number), which later causes Anti-Fraud or payment processing to fail.\n\nThe evidence in the transaction is:\n\n    ClearSale Return a RestServiceException: \\{\"Message\":\"The request is invalid.\",\"ModelState\":\\{\"[0].billing.address.number\":[\"Invalid type. Expected String but got Null.\"],\"[0].shipping.address.number\":[\"Invalid type. Expected String but got Null.\"]\\}\\}\nThis affects shoppers in pickup scenarios, when an invoice-type address exists without a street number, and has been observed even when the store’s UI should require the number field.\n\n\n#### Simulation\n\n\nIt's not possible to simulate.\n\n\n#### Workaround\n\n\n\n- Update/fix the shopper’s invoice address directly in Master Data so that mandatory fields (including number) are present and consistent.\n- For unlish the transaction, open a ticket so the payment product support team can bypass the anti-fraud analysis"}