What this section is for
Use Affiliates / Affiliates Config to maintain two independent PID-targeted configuration sets:
Payment Settingsstores a named minimum-deposit value in EUR for one or more PIDs.Sending Windowlimits how long affiliate events remain eligible after a player's first deposit.
These settings matter only when the project uses affiliate PID attribution. Limit write access to affiliate, marketing-operations, payments, or senior administrators.
Payment Settings
Each row contains:
Name- one or more
PIDs Min Deposit EURActive
The CRUD persistence and visible fields are verified. Live enforcement of Min Deposit EUR in the player deposit flow is not verified. Treat the value as stored configuration, not as proven payment enforcement, until the target brand's payment flow is tested and the runtime consumer is confirmed.
The model also supports Affiliate Keys, but the current form does not expose that field.
Sending Window
Each active rule targets one or more PIDs and can define:
| Setting | Runtime meaning |
|---|---|
Standard Limit | Day limit used for a regular player after first deposit. |
CPA Limit | Override used only when the player has a successful CPA-qualified FTD. |
| empty limit | No configured time limit for that branch. |
Active | Inactive rows are ignored. |
The window uses exact elapsed duration from the first recorded deposit timestamp. A limit of N days expires when at least N x 24 hours has elapsed; there is no calendar-day truncation or timezone boundary in this comparison.
If the sending-window check itself fails, the verified tracking flow fails open and continues rather than blocking the affiliate event. If multiple active records match the same PID, the current lookup has no deterministic order. Avoid duplicate active PID coverage.
How to configure safely
- Confirm the exact PID value used by the campaign.
- Decide whether the task belongs to Payment Settings or Sending Window.
- Use a unique name that identifies the partner or campaign.
- Avoid overlapping active records for the same PID.
- Save the rule and test with a controlled attributed player.
- For Payment Settings, verify the live deposit minimum independently because runtime enforcement is not yet source-proven.
- For Sending Window, test both an ordinary player and a successful CPA-qualified FTD when both limits are populated.
Access and troubleshooting
Payment Settings uses the Affiliates permission family. Sending Window uses cpaQualification. Menu visibility alone does not prove that a user can save changes, so verify the target role before editing these rules.
If a rule appears ineffective, check active state, exact PID spelling, first-deposit timestamp, CPA qualification outcome, duplicate matching records, and whether the relevant runtime consumer is actually enabled.