{"section":"known-issues","requestedLocale":"en","requestedSlug":"inconsistency-in-single-installment-payment-condition-behavior-at-checkout","locale":"en","slug":"inconsistency-in-single-installment-payment-condition-behavior-at-checkout","path":"docs/en/known-issues/Payments/inconsistency-in-single-installment-payment-condition-behavior-at-checkout.md","branch":"main","content":"## Summary\n\nWhen configuring payment conditions that include a single installment option, the checkout UI does not consistently reflect the installment configuration that will actually be applied by the Payments Gateway.\n\nIn scenarios where multiple payment rules are eligible, the gateway always applies the most restrictive rule, regardless of the installment option selected by the shopper in the checkout UI.\n\nThe Payments Gateway considers a rule to be “more restrictive” **only** based on the following attributes:\n\n- **Issuer / issuer country**\n- **Cobrand**\n- **Card level**\n- **BIN ranges**\n- **Sales channel**\n\nAs a result, the checkout UI may display installment options that do not match the rule ultimately applied, or may display only the full amount while the transaction is processed with a single-installment payment condition.\n\nScenario 1 – Two payment conditions (single payment and single installment)\nConfiguration\n\nTwo active payment conditions for the same payment method:\n\nPayment Condition A (Rule): Single payment (1x full amount), no restrictions\n\nPayment Condition B (Rule): Single installment (10x, non–single payment), with additional restrictions, such as:\n\n- Issuer / issuer country\n- BIN bank / BIN ranges\n- Cobrand\n- Card level\n- Sales channel\n\nExpected behavior\n\nThe checkout UI displays:\n\nSingle installment option\n\nRegardless of the option selected in the UI (including selecting single payment), the transaction is processed using Condition B, since it is the most restrictive rule matched by the card BIN and the other attributes listed above.\n\nThis is the current and expected behavior of the Payments Gateway, as rule prioritization is based on restriction level, not on the UI selection.\n\nScenario 2 – Single payment condition with one installment option\nConfiguration\n\nA single payment condition configured with:\n\nOnly one installment option, different from single payment\n\nExpected behavior\n\na. The checkout UI displays only the single payment option\nb. Upon completing the purchase, the transaction is processed using the configured single-installment payment condition\n\nThe installment option is correctly returned in the paymentData response (visible via DevTools → Network).\n\nThe installment option is not displayed in the checkout installment dropdown.\n\nOnly the total amount (single payment) is shown to the shopper.\n\nAfter completing the purchase, the transaction correctly reflects the configured single-installment option.\n\n## Simulation\n\n- Configure payment conditions according to Scenario 1 or Scenario 2.\n- Go to the checkout page and add any product to the cart.\n- Complete the purchase and verify the payment rule applied to the transaction.\n\n## Workaround\n\n**Scenario 1** - workaround is to align the restriction level between the single payment and the single installment conditions.\n\nInstead of having:\n\nPayment Condition A → 1x (full amount), no restrictions\n\nPayment Condition B → 10x, with additional restrictions (Issuer / issuer country, BIN bank / BIN ranges, Cobrand, Card level, Sales channel, etc.)\n\nThe merchant can configure:\n\nPayment Condition A → 1x (full amount), with the same restrictions applied in Condition B\n\nPayment Condition B → 10x, with those same restrictions\n\n**Scenario 2** - There is no workaround."}