{"section":"known-issues","requestedLocale":"en","requestedSlug":"partial-loyalty-credit-input-wrong-behavior-checkout-ui-when-commercial-policy-has-0-decimal-places","locale":"en","slug":"partial-loyalty-credit-input-wrong-behavior-checkout-ui-when-commercial-policy-has-0-decimal-places","path":"docs/en/known-issues/Checkout/partial-loyalty-credit-input-wrong-behavior-checkout-ui-when-commercial-policy-has-0-decimal-places.md","branch":"main","content":"## Summary\n\nCustomers cannot set a partial loyalty credit amount in Checkout: the input field visually remains at 0 and accepts only a single digit, despite the API receiving the typed value. This occurs when the store’s commercial policy is configured with zero decimal digits. The formatting layer removes the decimal portion and keeps thousand separators, and the input parser then strips non-digits, resulting in an incorrect cent value length and UI desynchronization. Affects shoppers using loyalty credit with policies set to 0 decimals in Checkout UI.\n\n## Simulation\n\nPrerequisites:\n\n- Commercial policy with decimal digits configured as 0.\n- Loyalty/Gift Card partial usage enabled on Checkout UI.\n\nSteps:\n\n1. Log in to the innew account with the provided user and open the referenced orderFormId.\n2. Attempt to change the partial credit amount in the loyalty credit input.\n3. Observe that the UI input change into a inexpected way, and only one digit appears to be considered, while network requests show the API receiving the typed value.\n\n## Workaround\n\nIs there a workaround for this bug? If yes, describe it here. If not, write \"N/A\" or \"There is no workaround available.\". Do not remove this section if there is no workaround, please."}