{"section":"known-issues","requestedLocale":"en","requestedSlug":"payment-rule-fields-not-reflected-in-admin-when-rule-is-created-via-api","locale":"en","slug":"payment-rule-fields-not-reflected-in-admin-when-rule-is-created-via-api","path":"docs/en/known-issues/Payments/payment-rule-fields-not-reflected-in-admin-when-rule-is-created-via-api.md","branch":"main","content":"## Summary\n\n\nWhen a payment rule is created via the Payments API, the Admin detail page for that rule does not display some selections (e.g., Issuer and Segment) as selected, even though the rule is correctly applied at checkout.\n\n\n#### Simulation\n\n\n\n-\n\nPrerequisite: Permission to create rules via API using **POST Insert a new payment rule** at /api/pvt/rules\n\n\n\n-\n\nSteps:\n\n\n\n1) Create a new rule via API, including Issuer configuration and Segment in the payload.\n\n\n\n2) Open Admin > Payments > Rules. Observe the rule “card” shows the configured Issuer/Segment as expected.\n\n\n\n3) Click into the rule detail page. Observe Issuer and Segment dropdowns are not preselected\n\n\n\n4) Validate functional behavior in checkout: a BIN matching the configured Issuer/Segment allows the configured installment length; a non-matching BIN does not show that installment option.\n\n\n\n#### Workaround\n\n\nOpen the rule in Admin, manually reselect Issuer and Segment in the UI, and Save, so the UI writes back the expected shape and fields become visible in the detail screen"}