{"version":"2.1.271","anchor":"pricing-multiplier-markup-now-surfaced-as-a-config-warning-t","canonical_anchor":"pricing-multiplier-markup-now-surfaced-as-a-config-warning-t","heading":"Pricing multiplier markup now surfaced as a config warning to admins","tier":"notice","area":"Cost Reporting","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/pricing-multiplier-markup-now-surfaced-as-a-config-warning-t","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Pricing multiplier markup now surfaced as a config warning to admins\n\nGateway config now warns admins when a pricing multiplier above 1 is set as a markup\n\n**What**\n\nWhen a gateway's `pricing.multiplier` setting is greater than 1, config validation now emits an admin-facing warning. It notes that the value acts as a markup, that spend limits are counted at the marked-up rate, and that clients running a version before v2.1.270 ignore a multiplier above 1.\n\n**Why**\n\nThis helps admins understand that setting a multiplier above 1 changes how spend limits are calculated, and flags a compatibility gap for older clients that won't respect the markup.\n\n- Area: Cost Reporting\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}