What this surface does

This surface is the full create and edit workspace for reusable bonus definitions.

Even though the first create step opens as a modal from the list page, operators should treat the whole flow as one form surface because it controls both:

• the bonus record itself
• linked promotional content such as bonus banner and bonus page content

When to use create vs edit

• Use Create when you need a new reusable bonus definition with its own type, validity, and content.
• Use Edit when the bonus already exists and you need to change validity, activation logic, targeting, currency economics, or content.
• Use the header Duplicate shortcut only as a quick way to open the create modal from the edit page. In the current page flow it does not clone the current bonus automatically.

Form map

The full workspace is split into four operator-facing sections:

• General Covers the saved bonus type, status toggles, wagering type, schedule, activation timing, and type-specific settings.
• Settings Covers tags, coupon codes, redirect URL, game or category targeting, and include or exclude country rules.
• Currency Repeats reward-economics settings per currency code, with the visible keys controlled by the selected bonus type.
• Content Covers banner text, bonus-page content, linked assets, and links into CMS banner/page editing after save.

What operators should enter carefully

• Bonus Type is the main branch selector. It controls which currency keys and advanced fields the form shows later.
• Valid From, Valid Till, Time From, Time Till, and Valid Days together define the usable schedule.
• Activation fields such as Times to Activate Per Player, Activation Period to Check, Drop Start DateTime, and Activated Bonus Expiration Period should be reviewed together because they govern eligibility timing.
• Include Tags, Exclude Tags, Coupon Codes, Next Coupon Codes, and geographic restrictions shape who can reach the bonus.
• Free Spins Games is mandatory for freespins. The page blocks save if the game list is empty for that bonus type.
• Per-currency settings should be reviewed in the EUR base first before operators use auto-calculation for other currencies.
• Auto Payout should be treated as the main cashback-behavior switch for instant_cashback. If it is off, operators should not expect the bonus to behave like an automatically paid cashback configuration.
• Auto Payout Days and the payout-distribution editor should be reviewed together. If the distribution does not total 100%, the page highlights the issue and offers auto-balance.
• Banner and bonus-page content are part of the same workflow. Operators usually save the definition first, then open the linked CMS page or banner for translation polish.

Marketing-facing explanation for instant cashback payout settings

For marketing users, Auto Payout answers one practical question:

• should this instant_cashback bonus behave as an automatically paid cashback configuration

Use this as the working rule:

• Auto Payout = ON means the saved bonus can be used by automatic cashback/rakeback payout logic when the bonus is also active
• Auto Payout = OFF means the bonus stays an instant_cashback definition, but automatic payout jobs and the current manual rakeback bonus selector should not pick it as an auto-paid cashback setup

This flag matters together with Auto Payout Days:

• if Auto Payout is on, Auto Payout Days defines the payout timing window
• if Auto Payout Days is greater than zero, the page reveals the payout-distribution editor so operators can split the payout percentage across days
• if Auto Payout is off, Auto Payout Days and payout distribution lose most of their practical marketing meaning because the bonus is no longer being prepared as an auto-paid cashback setup

The distribution button switches between two materially different saved configurations:

• Equal Distribution stores no custom percentage map. At payout time the amount is divided equally by Auto Payout Days.
• Custom Distribution stores day_1, day_2, and subsequent percentage values. At payout time each day receives the configured share of the amount.
• New equal shares shown by the editor use round(100 / days, 1). Auto-Balance to 100% rescales every custom row proportionally and rounds each result to one decimal place.
• The warning that the total must equal 100% does not currently block Save. Marketing operators must correct the total before saving; payout processing follows the stored day values and does not repair an invalid custom total.
• Actual day amounts are rounded down to two decimal places, including crypto wallet currencies. The rounding remainder is not added to the last day, so the sum of created day amounts can be slightly lower than the original amount.

The split uses the player's wallet currency. It does not convert the campaign amount into a reporting currency before calculating each day. Where transaction/reporting metadata needs a primary-currency amount, the payout flow reads the current source and primary currency rates at processing time and stores a separate converted value. No historical rate timestamp or later remeasurement was found, so do not compare that reporting amount as if it were a booking-time FX value.

After changing Auto Payout Days in custom mode, touch a day value or use Auto-Balance to 100% before Save. The editor can recalculate the displayed rows without immediately copying that recalculated map into the saved form value.

One downstream effect is already visible in the product:

• the manual rakeback flow filters bonuses to instant_cashback bonuses where Auto Payout is enabled

So for marketing configuration, the safe interpretation is:

• enable Auto Payout when the campaign should be treated as an auto-paid cashback offer
• disable it when the bonus should remain an instant_cashback definition without entering the auto-paid cashback selection flow
• default/off behavior is stored as false: the saved auto_payout value defaults to false, and save only turns it on when the enabled value is submitted

Common caveats

• The create modal bootstraps promotionTitle, termCondition, and description from Bonus Name before the first save.
• New bonuses start with all weekdays enabled and a long validity window. Operators are expected to narrow that down where needed.
• Bonus Type is chosen during create. In the edit workspace it is shown as a saved chip, not as a mutable field.
• NoDeposit appears only for freespins and no_deposit variants.
• Period To Check NGR, Auto Payout, and Auto Payout Days appear only for instant_cashback.
• Auto Payout Days > 0 reveals the payout-distribution editor.
• Changing the day count in custom mode can replace a saved 0% day with the newly calculated equal share in the displayed editor because zero is treated as an absent value during that recalculation.
• The 100% distribution warning is advisory in the current form; Save accepts an invalid total.
• Auto Payout is not just cosmetic. In current product behavior it affects which instant_cashback bonuses can be selected in the manual rakeback flow, and scheduled rakeback calendar logic also looks for active bonuses with autoPayout: true.
• Save order on the edit page is not just one request. The save flow updates the core bonus, updates tags, then creates or updates linked CMS banner/page content, and finally publishes those linked content records.
• Update and Translate is a content helper path around the same save flow. It tries to translate linked banner and page content after updating them.
• Linked CMS page and banner routes become useful only after the bonus has been saved and has a stable bonusId.