{"section":"known-issues","requestedLocale":"en","requestedSlug":"payment-rule-requiresauthentication-attribute-is-ignored-by-gateway-cannot-be-enforcedoverridden-via-api","locale":"en","slug":"payment-rule-requiresauthentication-attribute-is-ignored-by-gateway-cannot-be-enforcedoverridden-via-api","path":"docs/en/known-issues/Payments/payment-rule-requiresauthentication-attribute-is-ignored-by-gateway-cannot-be-enforcedoverridden-via-api.md","branch":"main","content":"## Summary\n\n\nThe `requiresAuthentication` attribute in payment rules is ignored by the Payments Gateway/Orchestrator. Updating the field via API has no effect, and authentication behavior for the payment method remains unchanged.\n**Scope:** Affects payment rules where operators attempt to control authentication via the `requiresAuthentication` flag.\n**Impact:** Merchants cannot enable or disable authentication as intended, causing potential operational confusion or blocked configurations.\n\n\n#### Simulation\n\n\n\n- Pre-conditions: Have a payment rule configured (e.g., for a bank slip method).\n\n\n- Steps:\n1) Use the “Update payment rule by ID” API to set requiresAuthentication to true or false for a given rule.\n2) Immediately GET the same payment rule and observe requiresAuthentication remains null or unchanged.\n3) Place a test order using that payment method and note that authentication behavior is unaffected by the attempted change.\n\n\n- Expected vs Actual:\n• Expected: Changing requiresAuthentication on the rule affects whether the method requires authentication.\n• Actual: Field changes are ignored by gateway logic; behavior does not change.\n\n\n#### Workaround\n\n\nN/A"}