Your regulator's requirements, mapped to your licence
For Example Pay (UA non-bank payment provider, synthetic) · prepared on 12.11.2026 · public sources only · regulator: National Bank of Ukraine (NBU)
Every requirement below has its legal status, the date we read the source and a link to the official text. We show only what a regulator or the register published. We make no statement about your rules, your fraud levels or your position with the regulator.
1. Your licence and services, as the public register shows them
- Firm
- Example Pay (UA non-bank payment provider, synthetic)
- Licence (register wording)
- Payment institution licence (example wording)
- Licence type used for this map
- Non-bank payment service provider (payment institution or e-money institution, NBU licence)
- Services listed
- Money transfers without opening an account, Acquiring of payment instruments
- Register
- NBU: banks and other institutions, read on 12.11.2026
- Note
- Synthetic example. Open-banking providers also appear in the NBU open API (S4).
2. Requirements that apply to a firm with your licence
34 requirements. "Draft" means the text is published for discussion and is not law.
| ID | Requirement, in plain words | Legal status | Read on | Official source |
|---|---|---|---|---|
| UA-NBU-01 | Review every rule regularly, at least monthly, by back-testing (§16(10), §65-66) | Draft Draft of 17.07.2026, published for discussion; not adopted | 11.11.2026 | NBU draft resolution "On some issues of payment service providers' control over payment operations" |
| UA-NBU-02 | Metric 1: rules triggered vs operations actually stopped or cards blocked (§60(1)) | Draft Draft of 17.07.2026, published for discussion; not adopted | 11.11.2026 | NBU draft resolution "On some issues of payment service providers' control over payment operations" |
| UA-NBU-03 | Metric 2: share of prevented fraud value in all fraud value (UAH) (§60(2)) | Draft Draft of 17.07.2026, published for discussion; not adopted | 11.11.2026 | NBU draft resolution "On some issues of payment service providers' control over payment operations" |
| UA-NBU-04 | Set effectiveness thresholds in writing; low effectiveness triggers an immediate review (§62-64) | Draft Draft of 17.07.2026, published for discussion; not adopted | 11.11.2026 | NBU draft resolution "On some issues of payment service providers' control over payment operations" |
| UA-NBU-05 | Review outcome: keep, adjust, or cancel the rule (§68-69) | Draft Draft of 17.07.2026, published for discussion; not adopted | 11.11.2026 | NBU draft resolution "On some issues of payment service providers' control over payment operations" |
| UA-NBU-06 | Rule lifecycle: data, hypothesis, rule, back-test, refine, finalise, written approval, go-live (§56) | Draft Draft of 17.07.2026, published for discussion; not adopted | 11.11.2026 | NBU draft resolution "On some issues of payment service providers' control over payment operations" |
| UA-NBU-07 | A risk marker on every operation: low (automatic), medium (may stop for confirmation), high (stop until confirmed) (§49-52) | Draft Draft of 17.07.2026, published for discussion; not adopted | 11.11.2026 | NBU draft resolution "On some issues of payment service providers' control over payment operations" |
| UA-NBU-08 | Keep a list of users who need enhanced control, and use it (§31) | Draft Draft of 17.07.2026, published for discussion; not adopted | 11.11.2026 | NBU draft resolution "On some issues of payment service providers' control over payment operations" |
| UA-NBU-09 | Daily reconciliation of payment operations (§16, §18, §2) | Draft Draft of 17.07.2026, published for discussion; not adopted | 11.11.2026 | NBU draft resolution "On some issues of payment service providers' control over payment operations" |
| UA-NBU-10 | AI/ML risk models may build behaviour profiles (§48) | Draft Draft of 17.07.2026, published for discussion; not adopted | 11.11.2026 | NBU draft resolution "On some issues of payment service providers' control over payment operations" |
| UA-NBU-11 | The NBU will assess effectiveness: documents, rules and markers, interviews (§19) | Draft Draft of 17.07.2026, published for discussion; not adopted | 11.11.2026 | NBU draft resolution "On some issues of payment service providers' control over payment operations" |
| UA-NBU-S01 | Many accounts or cards per user, far above peers (Annex 2) | Draft Draft of 17.07.2026, published for discussion; not adopted | 11.11.2026 | NBU draft of 17.07.2026, annex 2: signs of atypical user behaviour (to be considered, §53(3); a provider may skip one with a written, justified judgement, §54) |
| UA-NBU-S02 | Concentration of one operation type (card-detail transfers, account transfers, odd purchase amounts) (Annex 2) | Draft Draft of 17.07.2026, published for discussion; not adopted | 11.11.2026 | NBU draft of 17.07.2026, annex 2: signs of atypical user behaviour (to be considered, §53(3); a provider may skip one with a written, justified judgement, §54) |
| UA-NBU-S03 | High frequency of one operation type, in or out (e.g. over 10 top-ups in under 60 minutes) (Annex 2) | Draft Draft of 17.07.2026, published for discussion; not adopted | 11.11.2026 | NBU draft of 17.07.2026, annex 2: signs of atypical user behaviour (to be considered, §53(3); a provider may skip one with a written, justified judgement, §54) |
| UA-NBU-S04 | Low balances despite high volumes (Annex 2) | Draft Draft of 17.07.2026, published for discussion; not adopted | 11.11.2026 | NBU draft of 17.07.2026, annex 2: signs of atypical user behaviour (to be considered, §53(3); a provider may skip one with a written, justified judgement, §54) |
| UA-NBU-S05 | Frequent large loan issue and repayment (Annex 2) | Draft Draft of 17.07.2026, published for discussion; not adopted | 11.11.2026 | NBU draft of 17.07.2026, annex 2: signs of atypical user behaviour (to be considered, §53(3); a provider may skip one with a written, justified judgement, §54) |
| UA-NBU-S06 | Money in, quickly out, minimal balance left (Annex 2) | Draft Draft of 17.07.2026, published for discussion; not adopted | 11.11.2026 | NBU draft of 17.07.2026, annex 2: signs of atypical user behaviour (to be considered, §53(3); a provider may skip one with a written, justified judgement, §54) |
| UA-NBU-S07 | Gambling (MCC 7995) winnings without deposits, plus card transfers (Annex 2) | Draft Draft of 17.07.2026, published for discussion; not adopted | 11.11.2026 | NBU draft of 17.07.2026, annex 2: signs of atypical user behaviour (to be considered, §53(3); a provider may skip one with a written, justified judgement, §54) |
| UA-NBU-S08 | Regular transfers to a personal account that look like business activity (Annex 2) | Draft Draft of 17.07.2026, published for discussion; not adopted | 11.11.2026 | NBU draft of 17.07.2026, annex 2: signs of atypical user behaviour (to be considered, §53(3); a provider may skip one with a written, justified judgement, §54) |
| UA-NBU-S09 | New merchant: volume above MCC peers right after onboarding, then closes (Annex 2) | Draft Draft of 17.07.2026, published for discussion; not adopted | 11.11.2026 | NBU draft of 17.07.2026, annex 2: signs of atypical user behaviour (to be considered, §53(3); a provider may skip one with a written, justified judgement, §54) |
| UA-NBU-S10 | Merchant account: inflows mirror outflows (transit) (Annex 2) | Draft Draft of 17.07.2026, published for discussion; not adopted | 11.11.2026 | NBU draft of 17.07.2026, annex 2: signs of atypical user behaviour (to be considered, §53(3); a provider may skip one with a written, justified judgement, §54) |
| UA-NBU-S11 | Payment purposes atypical for the merchant's MCC (Annex 2) | Draft Draft of 17.07.2026, published for discussion; not adopted | 11.11.2026 | NBU draft of 17.07.2026, annex 2: signs of atypical user behaviour (to be considered, §53(3); a provider may skip one with a written, justified judgement, §54) |
| UA-NBU-S12 | Frequent changes of contacts, device, apps, IMEI, OS, IP/MAC (Annex 2) | Draft Draft of 17.07.2026, published for discussion; not adopted | 11.11.2026 | NBU draft of 17.07.2026, annex 2: signs of atypical user behaviour (to be considered, §53(3); a provider may skip one with a written, justified judgement, §54) |
| UA-NBU-S13 | Same device fingerprint across unrelated users (Annex 2) | Draft Draft of 17.07.2026, published for discussion; not adopted | 11.11.2026 | NBU draft of 17.07.2026, annex 2: signs of atypical user behaviour (to be considered, §53(3); a provider may skip one with a written, justified judgement, §54) |
| UA-NBU-S14 | Impossible geography between operations (Annex 2) | Draft Draft of 17.07.2026, published for discussion; not adopted | 11.11.2026 | NBU draft of 17.07.2026, annex 2: signs of atypical user behaviour (to be considered, §53(3); a provider may skip one with a written, justified judgement, §54) |
| UA-NBU-S15 | One payer to many payees, far above peers (Annex 2) | Draft Draft of 17.07.2026, published for discussion; not adopted | 11.11.2026 | NBU draft of 17.07.2026, annex 2: signs of atypical user behaviour (to be considered, §53(3); a provider may skip one with a written, justified judgement, §54) |
| UA-NBU-S16 | Many payers to one payee, far above peers (Annex 2) | Draft Draft of 17.07.2026, published for discussion; not adopted | 11.11.2026 | NBU draft of 17.07.2026, annex 2: signs of atypical user behaviour (to be considered, §53(3); a provider may skip one with a written, justified judgement, §54) |
| UA-NBU116-01 | Updated remote verification of natural persons using credit-bureau data (Resolution 116) | In force In force since 10.10.2026; 3 months to align internal procedures (about 10.01.2027) | 11.11.2026 | NBU Resolution No. 116 of 07.10.2026 (financial-monitoring regulations for banks and non-bank institutions) |
| UA-NBU116-02 | Reports to the State Financial Monitoring Service only through the e-cabinet; registers with continuous numbering (Resolution 116) | In force In force since 10.10.2026; 3 months to align internal procedures (about 10.01.2027) | 11.11.2026 | NBU Resolution No. 116 of 07.10.2026 (financial-monitoring regulations for banks and non-bank institutions) |
| UA-NBU51-01 | The acquirer passes more payee (merchant) data to the issuer (Resolution 51) | In force In force since 20.05.2026; 6 months to comply (about 20.11.2026) | 11.11.2026 | NBU Resolution No. 51 of 14.05.2026 (issuing and acquiring payment instruments) |
| UA-NBU51-02 | The acquirer shows its full name before an online payment; receipts show the payee, commission, payment purpose and MCC (Resolution 51) | In force In force since 20.05.2026; 6 months to comply (about 20.11.2026) | 11.11.2026 | NBU Resolution No. 51 of 14.05.2026 (issuing and acquiring payment instruments) |
| UA-NBU51-03 | Acquiring for natural persons only for defined categories, with set data passed to the issuer (Resolution 51) | In force In force since 20.05.2026; 6 months to comply (about 20.11.2026) | 11.11.2026 | NBU Resolution No. 51 of 14.05.2026 (issuing and acquiring payment instruments) |
| UA-NBU54-01 | No more non-application of sanctions to non-bank PSPs doing acquiring without authorisation (Resolution 54) | In force Grace period ended 02.09.2026 | 11.11.2026 | NBU Resolution No. 54 of 27.05.2026 |
| UA-16013-01 | Criminal liability for passing, receiving, buying or giving access to payment instruments or payment data so that others commit fraud (Criminal Code art. 200-1 (one outlet says 201-1)) | Adopted by parliament, signature not confirmed Adopted by the Rada 28.10.2026; presidential signature not confirmed | 11.11.2026 | Bill 16013 (drop accounts), new Criminal Code article |
3. Our rule or check for each requirement
"Available" means it is in our latest release (v0.7.0). "Development branch" means built and tested by us, not released yet. A checklist question is something we ask in a review, not a product feature.
Released rule or check: 32 · Development branch: 0 · Checklist question: 2 · Nothing yet: 0
| ID | Requirement | Our rule or check | State |
|---|---|---|---|
| UA-NBU-01 | Review every rule regularly, at least monthly, by back-testing |
| Released rule or check |
| UA-NBU-02 | Metric 1: rules triggered vs operations actually stopped or cards blocked |
| Released rule or check |
| UA-NBU-03 | Metric 2: share of prevented fraud value in all fraud value (UAH) |
| Released rule or check |
| UA-NBU-04 | Set effectiveness thresholds in writing; low effectiveness triggers an immediate review |
| Released rule or check |
| UA-NBU-05 | Review outcome: keep, adjust, or cancel the rule |
| Released rule or check |
| UA-NBU-06 | Rule lifecycle: data, hypothesis, rule, back-test, refine, finalise, written approval, go-live |
| Released rule or check |
| UA-NBU-07 | A risk marker on every operation: low (automatic), medium (may stop for confirmation), high (stop until confirmed) |
| Released rule or check |
| UA-NBU-08 | Keep a list of users who need enhanced control, and use it |
| Released rule or check |
| UA-NBU-09 | Daily reconciliation of payment operations |
| Released rule or check |
| UA-NBU-10 | AI/ML risk models may build behaviour profiles |
| Released rule or check |
| UA-NBU-11 | The NBU will assess effectiveness: documents, rules and markers, interviews |
| Released rule or check |
| UA-NBU-S01 | Many accounts or cards per user, far above peers |
| Released rule or check |
| UA-NBU-S02 | Concentration of one operation type (card-detail transfers, account transfers, odd purchase amounts) |
| Released rule or check |
| UA-NBU-S03 | High frequency of one operation type, in or out (e.g. over 10 top-ups in under 60 minutes) |
| Released rule or check |
| UA-NBU-S04 | Low balances despite high volumes |
| Released rule or check |
| UA-NBU-S05 | Frequent large loan issue and repayment |
| Released rule or check |
| UA-NBU-S06 | Money in, quickly out, minimal balance left |
| Released rule or check |
| UA-NBU-S07 | Gambling (MCC 7995) winnings without deposits, plus card transfers |
| Released rule or check |
| UA-NBU-S08 | Regular transfers to a personal account that look like business activity |
| Released rule or check |
| UA-NBU-S09 | New merchant: volume above MCC peers right after onboarding, then closes |
| Released rule or check |
| UA-NBU-S10 | Merchant account: inflows mirror outflows (transit) |
| Released rule or check |
| UA-NBU-S11 | Payment purposes atypical for the merchant's MCC |
| Released rule or check |
| UA-NBU-S12 | Frequent changes of contacts, device, apps, IMEI, OS, IP/MAC |
| Released rule or check |
| UA-NBU-S13 | Same device fingerprint across unrelated users |
| Released rule or check |
| UA-NBU-S14 | Impossible geography between operations |
| Released rule or check |
| UA-NBU-S15 | One payer to many payees, far above peers |
| Released rule or check |
| UA-NBU-S16 | Many payers to one payee, far above peers |
| Released rule or check |
| UA-NBU116-01 | Updated remote verification of natural persons using credit-bureau data |
| Released rule or check |
| UA-NBU116-02 | Reports to the State Financial Monitoring Service only through the e-cabinet; registers with continuous numbering |
| Checklist question |
| UA-NBU51-01 | The acquirer passes more payee (merchant) data to the issuer |
| Released rule or check |
| UA-NBU51-02 | The acquirer shows its full name before an online payment; receipts show the payee, commission, payment purpose and MCC |
| Released rule or check |
| UA-NBU51-03 | Acquiring for natural persons only for defined categories, with set data passed to the issuer |
| Released rule or check |
| UA-NBU54-01 | No more non-application of sanctions to non-bank PSPs doing acquiring without authorisation |
| Checklist question |
| UA-16013-01 | Criminal liability for passing, receiving, buying or giving access to payment instruments or payment data so that others commit fraud |
| Released rule or check |
4. Changed in the last 90 days
From our regulatory watch of official sources (data of 12.11.2026). Title, date and link only.
5. One question for you
Which of these do your rules cover today, and how do you check it?
What did we get wrong?
If your current tools already cover a requirement, we will mark it so.