1const e=JSON.parse(`{"center":{"title":"á¨á¥áá ááá¨á","subtitle":"á¨4pay.online á®áá¶á á¥áá´áµ á¥áá°áá á« áá¨á±á¦ á¥á«áá³áá± ááá áá á¥áá°áá«á°ááᣠáá¼ á¥áá°áá ááá áµá£ á¥á á¨áµáá¹á á°áá£á«áµ áááá³áµ á¥áá°áá«ááááµá¢","searchPlaceholder":"áááá½áá á½áá°-áá³á¦á½á ááááᣠááá³á \\"terminal\\"ᣠ\\"netting\\"ᣠ\\"reconciliation\\"","emptyState":"ááá á áá°áááᢠáá áá
áá áááá¨á áááá© ááá á¨á³á½ á«ááµá áááá áááá½ áááá áááá±á¢","allSections":"ááá áááá½","readMore":"á°á¨á᪠á«áá¥á¡","relatedTitle":"á°ááá
á½ááá½","onThisPage":"á áá
áá½ áá","resultsCount":"á¨á°áá á½ááá½á¦ {{count}}"},"ui":{"helpButton":"á¨ááá á¥áá","drawerTitle":"á¥áá","whenToUse":"áá¼ á¥áá°áá ááá áµ","concepts":"ááá á½áá°-áá³á¦á½","example":"áá³á","tips":"ááá®á½","related":"á°ááá
","openHelpCenter":"á¨á¥áá ááá¨áá áááµ","close":"áá","dismissTip":"áááá á áµáááµ","learnMore":"á°á¨á᪠ááá","sectionHelp":"ááá
ááá á¥ááá áááµ","notFound":"á½áá á áá°ááá","openArticle":"á½ááá áááµ","pageHelp":"á¨áá½ á¥áá"},"sections":{"overview":{"title":"á á ááá á¥áá³","summary":"á áµááá± ááµá¥ á«ááá áááᥠá á ááµ á¥áá³á¦ á¨á¦áá³ á᪠áá³á¦á½á£ á¨áá¥ááµ áá°áµá£ áªááá¶á½ á¥á á¨áá³á¥ á°á¥á°á (ledger)ᢠá¨áá³á¦á½á áá
á³á ááá³ ááá¨á³áµ á¥á á¨á°áᨠááá« áááááµ áá°áá
ááá¡á¢","whenToUse":"áá
ááááµ á°áááµ á¥á« ááá» áá¥á¥ á²áá ááááá \\"áááᥠáµááµ áá á¥á á¨áµ áá\\" á¥á«á áá á¨ááááªá« ááá á¦á³ ááᢠááá³á¥ á£ááá«áá½á£ ááááááµ á áµá°á³á³áªáá½ á¥á ááµáá á áá ááᦠá᪠áá³á¥ ááá°á½á£ á¨á°áá áá ááá« á áá á ááá á áá ááááµá£ áá°áá°á áá áªáááµ ááá (export)ᣠá¨áá³á¥ á°á¥á°á (ledger) áá ááµá³á¨á
ᢠááá á¦áá³áá½áá áá¥áá¶á½á á¨áá¨áµ áá¥áµ ááá á°áá á áá³á«áá¢","concepts":["á¦áá³ (Wallet) â á á°áᨠáááᬠááµá¥ á«á á¨áµáá
áµ áá³á¥á¤ \\"á᪠áá³á¦á½\\" áá½ áá¥á«áá³áá± á«ááá á°á áá á᪠áá³á¥ á«á³á«á","áá¥ááµ (Transaction) â áá á ááááᦠááá« ááá á (acquiring)ᣠááá« áááá (payout)ᣠááá á¨ááá´ áááá (á°ááá½á£ captureᣠvoid)","á°á¥á°á (Ledger â á¨áá³á¥ áááá) â á¨ááá á¨áááᥠá¥áá
áµáá´áá½ á£á áááµ-áá¤áµ áááá¥á¤ áááµá³á¨á
á¨á¥áááµ ááá á²ááᣠá¥ááá¶á½á áá ááá«áá½ áá¥á» áááá","á¨á¥ááá¼áá áá¥áá¶á½ â á¨ááªáᶠááá«áá½ áá á¨á°á«á«á á¨á¦á-á¼áá ááááá½ (ETHᣠTRONᣠááá°)","áááá£áá½ (Subscriptions) â áá°á°ááá ááá«áá½ á¨áá°á¨á á°á¨á³á³á ááá«","áªááá¶á½ â áá°áá°á áá á¨áá¥áá¶á½á á᪠áá³á¦á½ á¤ááµáááµá¤ á¨á¤ááµáááµ áá¥áµ áá ááá"],"example":"á ááµ á°áá á 15,000 RUB ááá« á áá°á¨áááá á¥á áááá«áᢠ\\"áá¥áá¶á½\\" á áááá±á£ á ááá á áá á áá£áªá« á«áµááᣠááááá á«ááᣠá¥á ááá³áá áááµá¹á¢ ááá«á á°á¨ááá á°áá áá á«áá¨áᣠá¨\\"á°á¥á°á\\" áááᥠáá á«áµá³ááᦠáá á á á¦áá³á áá á¥áá° á£á áááµ-áá¤áµ ááá¸á£á¨á
á áá áµá¢ ááááá áªáááµ ááµá¨áᣠ\\"áªáá
1á¶á½\\" á áááá± á¥á áááá ááááá½á á¤ááµáááµ á«áµááá¢","tips":["á¨ááµá°áµ áµáá°áá á \\"áá¥áá¶á½\\" áááá©á£ ááá áá á¥ááá³áá á \\"á°á¥á°á\\" ááµá¥ á«á¨ááá¡ â áááá áá á²áá á¨áá¥ááµ áá¹ ááá°á á°á¨á áá","\\"á¨á°á¥á°á á¥ááá¶á½\\" á¨áá³á¥ áááá¦á½á áááá«á â á á¥ááá á¥á ááá½ áá©ááµ á²áá á¥á» áá°áá¥á©","\\"á¨á°á¥á°á áá ááá«áá½\\" á áá³á¥ á¨á°á ááá áµáá®á½á á«ááá£á á¥á á¥á«áá³áá±á áá¤áµ á³á«áá áá°á á ááµá³á¨á
á á«áá¥áá","áá³ááá«áá½ áááááá½ á¨áµáááµ ááµá°á¶á½á áá°á áµá£á â á¨ááá« ááá á¨ááá« áá¤áµ á¥á¨á á á á¨áá áááµá¹áá¸á"]},"acceptance":{"title":"ááá« ááá á","summary":"ááµá¨á©á áá° ááá« ááá á« áá¥á¥ á¨áá«á°ááá ááᦠá°ááááá½á£ ááá¶á½á£ á¨ááá« á áááá½á£ á¨á°ááá¡ á«áá¶á½á£ á¨á á
á«á¢ á
áá¥á®á½á£ á¥á Smart Routingᢠá¥áá
ááá«áá½ á¥áá´áµá á áá á á©á á¥áá°áá á© á«áá
á«áá¢","whenToUse":"á á²áµ á¨ááá« áá´ á²á«áááᣠá á á
á«á¢áá½ áá«á¨á routing á²á«áá
á©á£ ááá ááá«áá½ ááá á á°á³á³á° ááááµ á¥á¨áá± á¥áá°áá á²áá¨áá© áá°áá
ááá¡á¢ áonboarding á áµá°á³á³áªáá½á£ áááá´ á´ááá«á á£ááá«á£ á¥á áááá¨á (conversion) áááááµ ááá á¡áµá á áá ááᢠá°ááááá½á á¨áá¨áµ ááá á¨ááµá°á³á°á áá¥áµ áá áááá¢","concepts":["á°áááá (Terminal) â á¨á°á«á«á á¨ááá« áá´á á á
á«á¢ áá á«á á¨ááá« ááá á« áá¥á¥á¤ ááá á¨áááá ááá","ááá¶á½á á¨ááá« á áááá½ â á«á áá
á°áµ áá¨áá ááá© á¨áá½á ááá áá¥áá½á á¨ááá« á áááá½","á¨á°ááá¡ á«áá¶á½ â áá°á°ááá ááá«áá½ á¨á°áááá¡ (tokenized) á¨á¨áá á«áá¶á½","á¨á á
á«á¢ á
áá¥á®á½ (Provider configs) â áááá« á á
á«á¢áá½á á£áá®á½ á¨ááá¢á« áá¨ááá«áá½á á¨áááááµ áááªá«áá½","Smart Routing â á á á
á«á¢áá½ áá«á¨á á¨ááá«áá½ routingᦠá¨áá á áá³á¢ (rules editor)ᣠá¨ááááµ á¤áááµ (route health)ᣠáµáá°áᣠsimulatorᣠá¥á ML routing","Fiscalization â á á¥á«áá³áá± á¨áá ááá ááµáááµ áá á¨áµ á¨ááµá«á á°á¨á°áá½á ááá£áµ áááá"],"example":"á¨RF á«ááµ ááá«áá½ á á á
á«á¢ A á á©á á¥áá²áá±á£ á«áá°á³á« á°áá áá° á á
á«á¢ B á¥áá²ááá± áááááᢠá \\"Routing Editor\\" ááµá¥ áá ááá á©á¦ ááá³ \\"RF á«ááµ\\" -> á á
á«á¢ Aᣠfallback -> á á
á«á¢ Bᢠá \\"Routing Simulator\\" ááµá¥ á£á áá¨á« ááá« áá á£á
áªáá á«á¨ááá¡á£ á¨áá«á á \\"Routing Health\\" ááµá¥ á¨á°á³á« ááááá½á áµáá» áá¨á³á°áá¢","tips":["á á²áµ á¨routing áá á¨áá°áá á ááµá£ á simulator ááµá¥ á«á³áááµ â á¥ááá°á áááᥠá¨áá³á°á á ááµ á¨ááá á¨áá ááááµ á«á«á","\\"Routing Health\\" á°áá áá½ áµá ááµááµ ááá¨áá¨á á¨áááá«á¸á á ááµ á¨á á
á«á¢ áá³á¨áá á«á³á«á","á¨áá á¨routing áá¾á½ (áµáá°áᣠsimulatorᣠconnectorsᣠML) ᨠsmart_routing_advanced ááá á²áá áááá","á¨á á
á«á¢ á
áá¥á®á½ áµá± áááá½á á«á¨áá»á â á¨áááááµ ááá½ á á¥áááµ á²áá¨á© á¥á» áááá©áá¸á"]},"crypto":{"title":"ááªáᶠáááá¬áá½á á¥ááá¼áá","summary":"á¨á¦á-á¼áá áááᥠáá ááµá«áµá¦ á¨ááªáᶠá¦áá³áá½á á᪠áá³á¦á»á¸áᣠáµáá°áᣠá¨á°ááá áááᥠpools á¥á á¨áááᥠáµá¥á°á£ (sweeps)ᣠá°á¨á-á°á®á treasuryᣠsmart contractsᣠmulti-signature safesᣠá¥á á¨á áá³á¨ áá¨á¥ ááµáµá
1á¢","whenToUse":"ááµá¨á© ááªáᶠáááᬠá²áá á ááá á²áá áá°áá
ááá¡á¦ á¨á¦áá³ á᪠áá³á¥ ááá°á½á£ á¨á°ááá á áµá«á»áá½ áááᥠáá á«áá (sweep)ᣠá¨á áá³á¨ áá¨á¥ á¤áááµ (ETHᣠTRON) áááááᣠááá smart contracts áááááᢠá¨á°áá á áá¾á½ use_crypto_tools áá¥áµ áá áááᤠsmart contractsᣠmulti-sigᣠblockchain healthᣠá¥á ZolT á áµá°á³á°á«á áá¸áá¢","concepts":["á¨ááªáᶠá¦áá³áá½á á᪠áá³á¦á½ â á¨áµáá
á± á áµá«á»áá½á á¨áá£á tokens á¥á stablecoins á᪠áá³á¦á½ (ETHᣠTRXᣠUSDTᣠUSDCᣠZOLT)","Deposit Pool á¥á Sweeps â á¨á°ááá á áµá«á»áá½ pool á¥á á¨á°áá á áááá¦á½á áá° treasury á áµá«á»áá½ á á«áµ-á°á áá°á¥á°á¥","Tier Treasury â á áá¨áá» á°á¨ááá½ (hot/cold) á¥á á á á°á ááá½ (Risk Config) áá«á¨á á¨áááᥠáµáááµ","Smart contracts á¥á Multi-Sig Safes â á¨á°á°áá© contracts á¥á á¥á áá¨ááá« ááá«áµáááá¸á ááááá½ multi-signature safes","Blockchain Health â á¨nodes á¥á á áá³á¨ áá¨á¦á½ ááá³á¦ synchronizationᣠlatencyᣠavailability","HethWallet á¥á ZolT Dashboard â á¨á°áá á ááªáᶠá¦áá³ á¥á ááá
áá fiat tokens á tokenize áááµá¨á á«á dashboard"],"example":"á áá«á³ USDT á°ááá áááá¦á½ áá° á°ááá á áµá«á»áá½ á°áá°ááᢠ\\"Sweeps\\" á áááá± á¥á á á áá \\"Tier Treasury\\" ááá½ áá á¨áµ áááá¥á áá° treasury á áµá«á» áá°á¥á°á¥ áááá©á¢ á¨áá« á ááµá£ á¨TRON á áá³á¨ áá¨á¥ synchronized áááá á¥á fees áá°á á áááá¸áá á \\"Blockchain Health\\" ááµá¥ á«á¨ááá¡á£ á áá ááá« sweep áááá¨áµ áá»ááá¢","tips":["Multi-signature ááááá½ á áá«á³ áá«ááá½á áá ááá â ááá ááááá½ á¥áµá¨áá°á á°á¡ áµá¨áµ ááµá°ááá á¥áá°á°á ááá á ááá á©","áµáá
á¨á¦á-á¼áá áááá á¨ááá¸áá á ááµ \\"Blockchain Health\\" á áááµá¹á¦ synced á«ááá node ááá á¨fee áá᪠áá¥ááµá áá«ááá ááá ááªáá áá«á³áµá áá½áá","\\"Risk Config\\" á á á«á£áª ááááá½á áááááá á¨áá«áµááá áá°á¦á½á á«áááá â á¨compliance á¡áµá áá á«áµá°á£á¥á©","á risk engine á¨áá°á¨á áááááá½ á \\"Risk and compliance\\" ááá ááµá¥ (Frozen Operations) ááµá°ááá³áᣠá¥áá
á áá°áá"]},"coreBanking":{"title":"Core banking","summary":"áá£áá áµáá
á¶á½ á¨Core Banking áááᦠá¨á°áá á áá³á¦á½á£ á°ááá áááá¦á½á£ á¥áµá®á½á£ treasuryᣠKYCᣠá¨áá¥á¥á áªáááµá£ ááµá°áááá½á£ á¨á«ááµ ááá£áµá£ á¨áááµ áááááµ (trade finance)ᣠá¥á interbankᢠá¥áá²áá á¨BaaS á¥á Open Banking (PSD2) á ááááá¶á½á á«á«áµá³áá¢","whenToUse":"ááá á¨áá³á¨á á\\"bank\\" ááááµ áµáá
á¶á½ á¥á áááµá¨á á áµá°á³á³áª á¥á» ááᢠá¨á°áá á á£áá á°á«á°áá½ áá³á¦á½á áááµá°á³á°áᣠá°ááá áááá¦á½áá á¥áµá®á½á ááááááµá£ KYC ááá ááá
ᣠá¥á á¨áá¥á¥á áªáááµ ááááááµ áá°áá
ááá£áᢠá¥á«áá³áá± áá½ á á«á± áá¥áµ á°á¨ááá (view_accountsᣠview_depositsᣠview_loansᣠááá°)á¢","concepts":["áá³á¦á½á ááááá½ â á¨á£áá© á¨á°áá á áá³á¦á½ á¥á á á¥áá± áá á«á á¥áá
áµáá´áá½á£ Chart of Accountsᣠá¥á General Ledger","á°ááá áááá¦á½á á¥áµá®á½ â áááᥠááá°á£á°á¥á áááµááᥠá¨áááµ áµááµ áá á«á ááá¶á½","Treasury á¥á exchange control â á¨áá³á½ áááᥠá áµá°á³á°áᣠáá°á¦á½á£ exchange control","KYC á¥á á¨áá¥á¥á áªáááµ â á¨á°áá á áá¨ááá« á¥á áá°áá£á£áªá áªááá¶á½ áááá¨áµ","Islamic Banking â á AAOIFI á°á¨ááá½ áá á¨áµ áááµ-á áᣠááá¶á½","BaaS á¥á Open Banking â áá£á ááá«áá½á£ chart of accounts áá ááµá£ BaaS á áµá°á³á°áᣠá¥á á PSD2 áá á¨áµ á consents á á©á á¨TPP áá³á¨á»"],"example":"á¨á°áá á á£áá áááá á á«á 1,000,000 RUB áá á°áá á«áá á¨áá á°ááá áááᥠáá¨áá³áᢠá \\"Deposits\\" ááµá¥ á¨áá áᣠáá á¥á á°áá áá á¨á°ááá áá ááá á©á¤ áµááá± á°áá³á áá¤á¶á½á á general ledger ááµá¥ á«áµááá£áᢠá áá áá á¨áµ áááµ ááá¹ á²á°áá± á á«áµ-á°á ááá¸á£á¨ááá¢","tips":["ááá á¨áá³á¨á á\\"bank\\" ááááµ áµáá
á¶á½ á¥á» áá â á«áá©áµá£ á¨áá£áªá áµáá
áµ ááááµ áááµá¹","á¨Open Banking áá¾á½ (TPP áá³á¨á» á¥á consents) áááµá¨á á áµá°á³á³áª á¨áá³á© á¥áá áá°áá á á£áá á áá°áá â áá
á¨PSD2 á¨áá¥á¥á á áááá½ áá","á¥á«áá³áá± á°áá£á á¨á°áᨠáá¥áµ á áµá°ááᣠá°ááá·áᦠá áá
á°á-áá¥áµ (least-privilege) áá á¨áµ ááµá¡áá¸á","Islamic Banking á AAOIFI áá á¨áµ áááµ-á áᣠáá´áá½á áá ááá â á¨ááá²á á°ááá áááá¦á½á á¥áµá®á½ áá á á³á°á£áá"]},"dcls":{"title":"dCLS â FX settlement","summary":"á payment-versus-payment (PvP) áá
1á
áá á¨á°áá á¨á° á¨netting áá á«á á¨FX settlement áááᢠá áááá¹ á á á«áµ áááá½ á°á¨áááᦠá¨á áá³á¨ áá¨á¥ á°á³á³á (My)ᣠá¨á áá³á¨ áá¨á¥ ááµáµá (Network)ᣠtoken issuer (Minter)ᣠá¥á dCLS operator (Admin)á¢","whenToUse":"ááá á¨áá³á¨á á dCLS á áá³á¨ áá¨á¥ ááµá¥ ááá³á°á á¥á» ááᦠá¨á¸á°á áááᥠá«áá á°á³á³á áµáá
áµá£ token issuer (org type=dcls_minter)ᣠá¥á á¨á áá³á¨ áá¨á¥ operatorᢠFX áááªá« áááµáá£áµá£ á¨settlement áá°áµá ááá¨á³á°áᣠtokens mint ááá burn áááµá¨áᣠreserves áááááµ ááá áááá£áµá£ á¥á â áoperator â netting ááá«ááµá settlement ááá¨ááá áá°áá
ááá¡á¢","concepts":["PvP (payment versus payment) â ááá±á áááá½ áááá¬á«á¸áá á á ááµ áá á¨ááá áá áµ settlementᣠá ááµ ááá á áááµá¨áµ á á°áá á«áµááá³á","Netting á¥á windows â á á ááµ settlement window ááµá¥ á¨á°áá«á áá´á³áá½á áá«á«áµá¦ á¨á¥á ááµá°áááá½ ááá
á ááµ á°á£á« (net) áá´á³ ááá«á","á°á³á³á á¥á FX áááªá« â á¨á áá³á¨ áá¨á¥ ááá á¥á áááᬠááááᥠá«áá á¥á«áᤠá \\"My\\" ááá ááµá¥ á°á³á³áá áááªá«áá¹áᣠsettlements áᣠá¥á á¨á áá queues á á«á«á","Mint / Burn â á reserves á¨á°á°áá fiat tokens ááá£áµá ááááµá¤ áá°á³á³ááᣠáissuer á¥á áoperator queues á á","Reserves á¥á audit â á¨á°á°á¡ tokens áµááᤠoperator á \\"Reserves Audit\\" ááµá¥ áááµá¸áá","á¨dCLS áááá½ â á¨á á«áµ á¨áá¾á½ áµá¥áµá¦á½ á áá±á¦ á¨ZolT contractsᣠá¨4pay.online backendᣠAdmin Areaᣠá¥á á¨HethWallet á°áá á <-> á á¥á¨á áá áµááá±á ááá°áá³á"],"example":"áááµ á°á³á³ááá½ RUB áCNY ááááᥠáááááᢠá¥á«áá³áá± á \\"My FX Instructions\\" ááµá¥ FX áááªá« á«áµáá£áᢠá \\"Netting Monitor\\" ááµá¥ operator á°áá«á áá´á³áá½á á«á«áᣠnetting window áááá«áᣠá¥á á¨gross ááµá°áááá½ ááá
á°á£á« (net) á áá ááá«áᢠreserves á á \\"Reserves Audit\\" ááµá¥ á«áµá³á¨á á ááᣠoperator settlement á á \\"Settlement\\" ááµá¥ á«á¨ááááᣠá¥á ááá±á áááá½ áááá¬á«á¸áá á á ááµ áá ááá ááá¢","tips":["á¨áá½ á³áááµ á ááá áá á¨á°áá á¨á° ááᦠá°á³á³áᣠissuerᣠá¥á operator á¨á°áá«á© áµá¥áµá¦á½á á«á«á â á¨4pay.online ááµá¨á á áµá°á³á³áª áááá á á«ááᣠdCLS áoperator á°á°á¥á·á","Netting á¨ááµá°áááá½á á¥ááµ áááá³áᦠáááªá« á áµááááá áá°áµ ááµá¥ á¥áá²ááµá
settlement windows á áááá¨á±","á¨settlement á ááµ operator reserves á ááµá³á¨á
á áá áµ â á á á áµáá á«á tokens ááá£áµ á ááááµá","á¨marketplace á¨ááᣠP2P FX á¨\\"Financial products\\" ááá á¨á°áᨠá°áá£á ááᣠá¨dCLS operator áá½ á áá°áá"]},"risk":{"title":"Risk á¥á compliance","summary":"á á°áá á¥á á¨áá¥á¥á á°áá¢ááµá áááá£á á áá£áªá«áá½á¦ áá°á¦á½á blacklistsᣠregistry ááµá³á¨á
ᣠá¨compliance reporting hubᣠá¥á audit logsá¢","whenToUse":"á¥áá° complianceᣠá¨áááááµ ááµáµá ááá á¨ááµá¥ áá¥á¥á ááá áá°áá
ááá¡á¦ áá°á¦á½áá ááá½á ááááᣠá¨á á
á«á¢ registries áá ááµá³á¨á
ᣠá¨áá¥á¥á áªáááµ áááááµá ááµáá£áµá£ á¨á³áá° áááá áááááᣠááá á audit log ááµá¥ á¨á°á áá áµááá¶á½á áá¨á³á°áᢠáá¾á½ á¥áá° view_af_rulesᣠview_registriesᣠview_aml_alertsᣠview_audit_log á£á áá¥á¶á½ á°á¨ááááá¢","concepts":["áá ááá«áá½á blacklists â á¨anti-fraud ááá½ á¨á°á á«áá áá°á¦á½ á¥á á¨á°á¨áá¨á á«áá¶á½á£ á áµá«á»áá½á áááá®á½ áááá®á½","ááµá³á¨á
(Reconciliation) â á¨ááµá¨á ááá¥á á¨á á
á«á¢á á£áá registries áá ááááµá¦ dashboardᣠáááᣠimports á¥á exportsᣠá¨áááá á¨á°áá£á áá
á®á½","Frozen Operations â áá¥á
áááá á risk engine á¨áááá ááááá½ queue","Compliance Hub â á¨áªáá
1áµ ááá¨áᦠtemplatesᣠáªáááµ áááá¨áµá£ schedulesᣠá¥á áá° á°áá£á£áªá á¨ááµá¨á» á»ááá½","AAOIFI Compliance â á¨á¢áµááá á¨áááááµ á°á¨ááá½ áá á°áá¢ááµá ááá£á á (view_islamic_banking áá¥áµ)","Audit Logs â ááááá«áá½ á¨á°á áá áµááá¶á½á á¨áµáááµ ááµá°á¶á½ log"],"example":"á áá áá¨á¨á» á¨á á
á«á¢á registry á¨ááµá¨á ááᥠá 3 ááááá½ ááá«á«áᢠ\\"Reconciliation\\" -> \\"Search\\" á áááá±á£ á«áá°ááá± áááá¦á½á á«ááᣠá¥á áá©áá± á¨áµ á¥áá³á áááµá â á registry ááá á áá¤á¶á½ ááµá¥á¢ áááá«á±á á¨áá± á ááᣠáá©áá¶á½ á á«áµ-á°á á¥áá²áá á¨á°á«á á°á°ááá ááµá³á¨á
á«áááá¢","tips":["á¨áááá ááááá½ á áá¥ááµ ááááá á áá£á¸á â áááá¨áµ á¨á°áá áá áááᥠá¥á á¨settlement áá ááááµá á«ááá«á","á¨áá¥á¥á áá°á¦á½ á á¥á
á ááá áááá«áµ á¥áá³á«ááá¡ á¨áªáááµ schedules á á¨ááµá¨á» á»ááá½á á áµááµáá á«ááá","audit log á áááá« ááµá¥ á áµááá ááᦠáá áá¼ á
áá¥á®á½á á¥áá°áá¨á¨ ááá áááá á¥áá³á¨ááá á«á³á«á","Blacklists á¥á áá°á¦á½ á áá¨áá¨á áá á«á â áá
á³á á«áµááá¸áᣠá áá ááá« anti-fraud á¨á°á³á³á° ááá á«á³ááá ááá á«áá³á"]},"workflow":{"title":"Workflows","summary":"á¨áááµ áá°áµ á áµá°á³á°á (BPM) áááᦠprocess definitionsᣠtasksᣠcasesᣠdecision tablesᣠááá½á£ á¥á onboardingᢠá®áµ á³áááá© áá½á°áá½áá á¨ááµá°ááá áááá¶á½á á á«áµ-á°á á¥áá²á«á°áá á«áµá½ááá³áá¢","whenToUse":"á¨á°ááá½ áá½á°á
ááááµá£ á¨á°áá á onboardingᣠá¨á¥á«á ááµá°áááµ á«á á á«áµ-á°á áá°áµ áááá á²ááá áá°áá
ááá¡á¢ ááá°áµ analyst á¥á ááµáá
áµ á áµá°á³á³áª á áá ááᢠááá áá°áá á á¨áá¨á á²áá view_workflows áá¥áµ áá áááá¢","concepts":["Definition â á¨áá°áµ á°á¨ááá½ ááµáᦠá¨áµááá¶á½á£ ááá³áá½á ááááá½ á
á°á á°á¨á°á","Tasks á¥á cases â á áá°á« áá°áµ ááµá¥ á«á á¨á°áá© á¨á¥á« á áá¶á½ á¥á á¥áá±á á¨áá«á°á«á cases","Decision tables á¥á ááá½ â áá°áµ á¨áá¨áááá áµ \\"ááá³ á¨ááᣠá¨áá« áµáááµ\\" á¨á°áá á¨á° á áááá®","Onboarding â á á²áµ á°áá á ááá áµáá
áµ ááááááµ ááá áá°áµ","Dashboard á¥á áµáá°á â á¨áá áá°á¶á½á£ ááááá½á á¨áá áááá« áááá½ áá ááá«"],"example":"á¨500,000 RUB á áá á°ááá¾á½ á á áµá°á³á³áª áá½á°á
á áá£á¸áᢠá \\"Definitions\\" ááµá¥ áá°á±á áááá¹á¦ á°á¨á \\"á¨áá á áá°á»\\" -> decision table \\"áá á > 500000\\" -> á°á¨á \\"á¨á áµá°á³á³áª áá½á°á
\\" -> \\"á áá»á¸á\\"ᢠá¨áá°á© instances á \\"Tasks\\" ááµá¥ áá³á«áᣠá¥á á«áá áá-áá°á¦á½á á \\"Analytics\\" ááµá¥ á«á«áá¢","tips":["á á¥ááµ á°á¨ááá½ ááá áá°áµ áááá© á¥á á²á¨áá ááµá¥áµá¥ááµ á«áá â áµáá
ááµáá½ áá¨á á áµá¸á᪠áá¸á","á°áááá á áááá®á áá° decision tables á¥á ááá½ á«ááá³á
á±á¦ á¨á á
áá á¨áá°áµ ááµá á¥áá°áá á¨ááµá«áµ ááá
áááá¨á ááá áá¸á","á dashboard áá \\"á¨á°á£á á\\" tasks á áááá¨á± â á¥ááá áá á«áá°áá°á á£áá¤áµ ááá á¨áá°á ááᥠá«áááá³á","Onboarding ááá áá°áµ ááᦠá¨áá® á¨áááá£áµ ááá
á¥áá° ááá» áá¥á¥ áá ááá áµ"]},"administration":{"title":"á áµá°á³á°á","summary":"á¨á°á³á³ááá½á á¨ááµá¨á ááᥠá áµá°á³á°áᦠá áá®á½á£ á°áá áá½á£ áµáá
á¶á½á£ ááá°á¦á½á£ á᪠áá³á¦á½á billingᣠá¨áá£áá» ááᥠ(áááá¬áá½á£ FX ratesᣠstatuses)ᣠá¨API á®áá¶áᣠtask schedulesᣠá¨á£áá áá£áªá«áá½á£ á¥á á¨á áááááµ ááááá«áá½á¢","whenToUse"
1:"á¨ááµá¨á á áµá°á³á³áªáá½á á áá®á½ áá³á¦á½áᣠá¨áá áá´ááᣠá¨áá£áá» ááá¥áᣠá¥á á¨á áááááµ ááááá½á áááµá°á³á°á áá°áá
ááá£áᦠáµáá
áµ ááá áᣠAPI key ááá£áµá£ á¨áááᬠá°ááá½á ááááᣠcache áá½á³áµá¢ á¥á áá¾á½ á áµá°á³á°á«á áá¸á (adminOnly)ᤠá°áá á á¨á°áá°á áµá¥áµá¥ á«á«áᣠááá³á \\"Organizations\\" á¥á»á¢","concepts":["á áá®á½á£ á°áá áá½á£ áµáá
á¶á½á£ ááá°á¦á½ â á¨ááµá¨á© á¨áá áá´áᦠáá á á¨áµáá áµáá
áµ ááµá¥ á á¨áµáá¹ áá¥á¶á½ áá á«á","á¨áµáá
áµ á᪠áá³á¦á½á billing â á áµáá
áµ á᪠áá³á¦á½ á¥á áááµá¨á á ááááá¶á½ invoicing","á¨áá£áá» ááᥠâ áááá¬áá½á£ FX ratesᣠá¥á á¨áááá¨á» statusesᤠá ááµá¨á© áá á¨á°áá« áá
á","á¨API á®áá¶á á¥á schedules â á¨API keys á¥á á¨á°á«á á¨á áµá°ááᣠtasks á áµá°á³á°á","á¨á£áá áá£áªá«áá½ â áá áá á£áá (Absolut) ááááá½","á¨á áááááµ ááááá«áá½ â cache á áµá°á³á°áᣠá¨á«ááµ BIN ááá¥á£ á¨á°á áá áµáá½"],"example":"á á²áµ ááá´ á¥á¨á°ááá ááᢠá \\"Organizations\\" ááµá¥ á¨áááááá ááááµ áµáá
áµ ááá á©á£ á¨á áá áá á«ááááµá£ ááá ááá°á¦á½áá áá¥á¶á½á áááµá¡á¢ á¨áá« á \\"API console\\" ááµá¥ ááá
á°áµ API key á«áá¡á£ á¥á á \\"FX rates\\" ááµá¥ á¨ááá¨áªá« á°ááá½á áµááááááµ á«á¨ááá¡á¢","tips":["áá¥á¶á½á á áá
á°á-áá¥áµ (least-privilege) áá á¨áµ ááµá¡ â ááµá¨á© á¥á«áµ á«áá (granular) permissions á¨áá°ááá ááá
áá","FX rates á¥á áááá¬áá½ á¨á°áá« áá£áá» áá¸áᦠá¥áá
á«á áµá
á°áµ áááá ááá¨á®á½ ááá«áᣠáµááá
á¥á´á¶á½á á á¥ááá áááá©","á«á áµáá
áµ á°áá á á áá
ááá \\"Organizations\\" á¥á» á«á«á â áá
á¨á°á á á á£á
᪠á¥áá á¨áá³á¨á» ááµááµ á áá°áá","cache áá½á³áµá á á¥ááá áá°áá¥á©á¦ á ááá á¨ááµá¨á á°á áááá½ á¨áá³á¨áá ááᥠááá«á"]},"settings":{"title":"á
áá¥á®á½","summary":"á¨ááá á¨áµáá
áµ á
áá¥á®á½á¦ á£á áááµ-á°á¨á áá¨ááá« (2FA)ᣠá¨referral áá®áá«áᣠá¨áá á¥á
á¶á½ (pricing plans)ᣠá¨Copilot AI á
áá¥á®á½á£ hosted payment pagesᣠá¨áµáááµ áááªá«áá½á£ á¥á á¨GDPR ááᥠá£áá¤áµ á¥á«ááá½á¢","whenToUse":"ááá³á¥á 2FA áááááµá£ referral code ááá°áá áᣠá¨hosted payment page ááá áááááᣠááá â á¥áá° á áµá°á³á³áª â á¨áµáááµ áááªá«áá½á£ pricing plans áááááµá GDPR á¥á«á áááµá°áááµ áá°áá
ááá¡á¢ á áá³ááµ áá¾á½ áááá á°á áááá½ ááááᣠááá¹ áá áµá°á³á³áª á¥á»á¢","concepts":["á£á áááµ-á°á¨á áá¨ááá« (2FA) â á°á¨á᪠á¨ááá¢á« á¥á áᤠáá¥á«áá³áá± á°á áá áááá","á¨Referral áá®áá«á â á á°áá á referral code áá°áá á á¥á á á áµá°á³á³áª referrals ááµá°á³á°á","Pricing plans á¥á billing â á ááµá¨á© áá ááµáá
á¶á½ á¨á áááááµ ááá½","Copilot AI â ááµáá
á± á¨á°á°áá³ AI á¨á³áµ á
áá¥á®á½","Hosted Payment Pages â hosted payment pages áááá (áááᣠá£á
áª)ᤠmanage_settings áá¥áµ áá ááá","á¨ááᥠá£áá¤áµ á¥á«ááá½ (GDPR) â á¨áá ááᥠáá³á¨á» ááá á°áá á¥á«ááá½á ááµá°áááµ"],"example":"á á²áµ á°á«á°á áá° á®áá¶á áá³á¨á» á ááá·áᢠá¨áá«á°áááµ á¨ááááªá« ááá \\"á£á áááµ-á°á¨á áá¨ááá«\\" á á¨áá°á 2FA ááááµ ááᢠáµáá
á± á referral link á á©á á¨áá£á£ á áµá°á³á³áªá referral code á á \\"Apply Referral\\" ááµá¥ áá°áá¥á«áᣠá¥á á¨ááá« áá½ áá
1áá á \\"Hosted Payment Pages\\" ááµá¥ á«áá
á«áá¢","tips":["á¨ááááªá« ááá¢á«á á áá áá²á«áá 2FA á«áá â ááá³á¥á á¥á áá á
áá áµáá
á± áá á¨á³á á¥á á áá","á¨áµáááµ á
áá¥á®á½á pricing plans áá áµá°á³á³áª á¥á» áá³á«áᦠá á°ááá ááááµ áááá©áá¸áᣠáááá ááá«á","GDPR á¥á«ááá½ á¨áá¥á¥á áá-áá°á¦á½ á áá¸á â ááµá°ááá³á¸áá á á³ááá©","á¨hosted payment page ááá¦á½á á¨áá© á«á«áᣠáµááá
á¨áá°áá á ááµ áá¤á±á á«á¨ááá¡"]},"smartRouting":{"title":"á¥áá
ááááá","summary":"á¨áá á¨ááá« áááááᦠá á á
á«á¢ áá á¨ááᣠáµáá°áᣠá°áá¦á½á á á³áªá«á ááá«áá½ áá á¨áá«ááµ á áµáá³áᣠá¨á á«á«á¥ á áµá°á³á°á á¥á á áá´á á¨ááááµ ááá«á¢ á¨á°áá áá á¥áá áá³á¥ á¨áááªá« ááµáá®á½á á¨áá«áá»á½áá á¥áá ááá¢","whenToUse":"áá á¨á³á ááááá á ááá áá áµ áá ááá£áᦠá á ááµ á á
á«á¢ ááᣠááá á¥áá°áá°á áááá
ᣠá°áá¥á á¨áá°áá á© á ááµ áááá°á½á£ á á«á«á¥ ááááááµ ááá á¨áááªá« ááµáá®á½á áááá»á¸áᢠá¨Smart Routing Advanced áá±á áááááᤠá¥á± á°áá Provider Quality áá áááᦠá«á á á
á«á¢ á°á¨ááá½ á¨áá«áááá©á áµ áá á¨áµ á¨ááá¢","concepts":["á¨ááááá áµáá°á â á á á
á«á¢á á á á
á£á« ááá£á£ ááµá
á¥á ááª","á áµáá³á â á°áá¦á½á á¨áá°áá á«á¸á á ááµ á á³áªá«á ááá«áá½ áá á«áá³á","á á«á«á¦á½ â á¨á á
á«á¢ áá
á°á¶á½á áááááµ á¥á áááá","á¨ML ááááá â á¨áá á°áá¦á½ ááá
áá´á áááá±á áááá£á","á¥áá áá³á¥ â á¨á°áá á áá¥á¨á¶á½ á¥á
á á¥áá³ á¥á á¨áááªá« ááµáá®á½ áá½á½á"],"example":"á¨á«ááµ ááᣠá á ááµ áááµ áá°áᢠáµáá°áá á á
á«á¢á á¨á¦áµáµ áá¨á« á áá±á á¥áá°áá«á á á«á³á«áᢠáµá«áá©á áá° á°ááá á á
á«á¢ á¨áá«áá¨áá á°áᥠá á áµáá³á© á áá±á¤ á¨áá« á áá á¥á» á á¥á©áµá¢","tips":["á á áµáá³á á«ááá á°áᥠá á°áá áá½ á¥ááá°á áááᥠáá ááá¨á«á","áá±á á Provider Quality áá ááá á¨á³áᦠá¥á± á«á á ááá áá á áá ááááá","áá á¨á³á á¨ááááµ á áá³áá á¨Health áá½ á ááá« ááá á ááµá¥ ááá«á â á«á áá±á áá á«á","á¨ML ááááá á¨á³áªá ááá«áᦠá á
á«á¢áá½ á¨á°áá¨á© á áá áá´á áá ááááá"]},"pfpCrowdfunding":{"title":"ááá£á áá°á£á°á¥","summary":"á¨á¥á á£ááá¥á¶á½ áááᥠáá°á£á°á¥á¦ ááá»áá½á£ á¨á£ááá¥á¶á½ áááá¥á£ á¨áᢠáááá á¥á á¨áááµááá® áµáá°áᢠá³á½á¦áá± áááá ááá»áá½ á á ááµ áá á«á³á«áá¢","whenToUse":"áµáá
á± á ááµá¨á© á á©á á¨á£ááá¥á¶á½ áááᥠá²á«á°á£áµá¥ ááá£áᦠááá» ááµáááᣠáá á¥áá³áᣠáá¨áµá£ áᢠáá¨ááá ááá áµáá°á áá°á£á°á¥á¢ á¨Participatory Finance áá±áá á¨view_pfp_crowdfunding áá¥áµ áááááá¢","concepts":["ááá»áá½ â á¨áá°á£á°á¥ áá¥á£ áá°á¥ ááᣠá³ááá á²áá á¨ááááµ á°áᥠá¥á á¨ááá® á£áªá«áá½","á£ááá¥á¶á½ â ááᣠáá á«á
á á¥á á áá ááá³ á¥áá³áá£","ááááá½ â ááµáá» á£áá¤á¶á½ á¨á ááµ ááá á°á¨á³á³á á¨áᢠááá«áá½","á¨áááµááá® áµáá°á â áµáááááµá£ á ááááá á¨á°á°á á°á á á¥áá
áµáá´","ááµá«á£ â á¨ááá»á áááᥠáá¡ á¥áµáªá°á¨áµ á°ááᶠáááá£á"],"example":"ááá»á á¨áá°á¡ á ááµ á³áááµ áá°á á¥á áá¡á á á³á«á¢ «ááááá½á» ááá±á£ áá á¨á±áá á°ááá¾á½á á áµááá¡á£ áááá¡á á£ááá¥áµ á á£ááá¥áµ ááµá¹á¤ á¨áá« á áá á¥á» á¥á
áá á áµááá©á¦ á á
áá ááá¸áá á¥á á ááááµáá¢","tips":["á¨ááµááá á ááµ á¨áááá áááá¡á ááµá¹á¦ á¥á
á á á
áá ááá£á á¥á á ááááµá","á á á¥ááá¹ á¨áá¥á¥á á¥ááá¶á½ á á ááµ á£ááá¥áµ áá á£áªá« áá á¨áá","á«áá°áá ááá»á ááµá¨á© á áá ááááá â á¨ááááµ á°áá¡á á áµááµá á áµááá¡","ááµá¨á© á ááá áá áá¥á á ááááᦠááá£áá» á¥á» áá°áá"]},"pfpEthical":{"title":"á¥á ááá£á«á áááááµ","summary":"á«á áááµ áááááµá á¨áá« á
áá¾á½á¦ á
á¥á¨áµ á¥á« áá
á á«áµá£ á¨áᢠáµáá» á¨áááá± ááá½á£ á á á£ááµ áá«á¨á á¥áµáᣠá¨áá
á á¨á°á¥ á£áá á áááááµá áá
á á«á á°á½áá áááªá«á¢","whenToUse"
1:"áµáá
á± á¨á
á¥á¨áµ á¥á« áá
á á«áµá£ á«á áááµ ááá¶á½ ááá á¨áá£á¢áá½ áá
á á¨á°á¥ áá á²á á« ááá£áᦠáá
á á ááááᣠá¨RBF áá ááá«á¨áᣠá¨á°á°á¡ á¥áµá®á½á áááá¨áµ ááá á¨á°á½áá áªáááµ áááááµá¢ á¨Participatory Finance áá±áá á¨view_pfp_ethical áá¥áµ áááááá¢","concepts":["á
á¥á¨áµ á¥á« áá
á á«áµ â á¨á á£ááµ áµáá»á£ á¨ááá± áá¤áµ ááááá á¨ááá« á°áá¦á½","á¨RBF ááá½ â á¨áááµ ááá
á¨áᢠáµáá» ááááµá£ á¥áµá¨ áááá» á£áªá« áµá¨áµ","á¨P2P á¥áµá â á ááµá¨á© á á£ááµ áá«á¨á á¥áµá","á¨áá
á á¨á°á¥ á£áá â á¨áá¨á³á á«áááá½á á¨áá ᣠá¡áµáá½","á¨á°á½áá á³á½á¦ááµ â á¨ááá« áá
á á«á áá¤áµá¦ á¨á¥á« ááµáá½á£ á°á áááá½","á¨á¸áªá áááá â ááá¶á½á á¨áááááá½ á áá»á ááá°á½"],"example":"á°áá áá á¨á¥á« ááµá¬á áááᥠááááá áá á¨áááµ á¥áµá á ááµááááᢠá¨RBF áá ááá«á¨áᦠá£áªá«á á¥áµáªá°á¨áµ áµá¨áµ á¨áááá áá¢á áµáá» áááá³áᢠáá á á°áá°áá áá ááµá¥ ááá á¥áá°áá á áá´á áááµá¹ â á áá ááá« áµáá»áá á«ááá°á¥ áááá³áá¢","tips":["á RBF á¨áᢠáµáá»á áááá» á£áªá« á¨á°á³á°á© áá¸áᦠáá¢á á²á«ááµ áá á ááá á áááá","á¨áá
á á© áµáá á áµááááµ áá¨ááááᣠáªá³á«á áá á ááá® áµáá» á¥á»","á¨á¸áªá á°áµááááµ ááá± á¨ááá£á± á ááµ ááá°á»áᦠáá©áá± á áááá áá³á«á","á áᥠááááá¥á®á½ (ROSCAᣠáá»á¨á«á£ á ááá« áá¨ááá) ááá±á á°á¨á á á°á¨á ááá¥á°á á¨ááá«á¸á á ááµ á«á¨ááá£á"]},"pfpGovernance":{"title":"á¨áá« á áµá°á³á°á","summary":"á¨áá« áá³ááá½á áááá£á¸áᦠá¨áá
á á¨á°á¥ áá³á¦á½á áµáá
á á°á£á¥á£ á¨á ááµ áá°á¶á½á£ á á á£ááµ áá«á¨á á¨áá« á¥áµáᣠá¨áá¥á¥á áªáááµá á¨ááá á á ááá áá°á¦á½á¢","whenToUse":"áá³ááá á ááµ á¦áá¬á°á á³ááá áá
á á¨á°á¡ á²ááµá ááá£áᦠá¨á ááµ áá°áµ ááááµá£ áá³á¥ ááµáá
áá
á¨á¥á£ á¨áá« á¥áµá áá³á¦á½á áááá¨áµ ááá áá°áá£á£áª áªáááµ ááµá¨áᢠá¨Participatory Finance áá±á áááááá¢","concepts":["áá³á¦á½á áµáá
â á¨áµáá
áá´á (á ááµ á á£á á ááµ áµáá
ááá á áµáá») á¥á áááá° áá£á¤","á¨á ááµ áá°á¶á½ â á¨áá« á ááµá á áá
á á¨á°á¥ á¥á«ááá½ áá¨ááá","á¨áá« á¥áµá â á«á áá áááᥠá á á£ááµ áá«á¨á áá® áµáá ááá«á¨áµ","DAO â á¨á«á³á¸á á¨áá³á á°áᥠá«áá¸á áá
á á¨á°á¦á½","áá¥á¥á â áµá á¨áá« áááááµ áªáááµ","á
áá¥á®á½ â áááá áá á¨áá á© á¨á¢áá¨áµáµáááµ áá°á¦á½á á°áá½"],"example":"áá
á á¨á°á¡ ááá³á á áá±á á«á¨ááááᢠáá áá á¨áµáá
áá°á¥ áá á«áá áá°áµ ááá±á£ á¥á«ááá½á á°á¥áµá¡á£ áááá° áá£á¤áá á á¥á â á¨áá« á áá á¥á» áá°á±á ááᦠá¥á«ááá¹ á áµáá
áá¤áµ ááá¸ááá¢","tips":["áááá° áá£á¤á á¨áµáá
áá´á áá°á± á¨áá¨áá± á ááµ áááá£áᤠá áá á ááá¨á©á","á¨áá« á¥áµá á á²áµ áááᥠá ááá¥ááᦠá¨ááá á ááá½ áµáá áááá áá® áá","á¨á
áá¥á®á½ á¨ááá¡ á¨á¢áá¨áµáµáááµ áá°á¦á½ á ááá ááá»áá½ áá áá áá á«á","á¨á
1á¥á¥á áªáááµ á¨á¥ááá°á áá¨á áááá£á â á¨ááá£áµá á ááµ á«áµá°á«áá"]},"islamicFinance":{"title":"á¥áµááá áááááµ","summary":"á á¸áªá á°áá¦á½ á¨á£áá ááá¶á½á¦ áá«á áᣠá¢áá«á£ áá³á¨á£á áá»á¨á«á£ á¨á£áá©á á¥áµááá ááá ááááá á AAOIFI áááááá½ á¦á²áµá¢","whenToUse":"á á¥áµááá áá´á á¨áá á© á¨Â«á£áá» ááááµ áµáá
á¶á½ ááá£áᦠáááá ááááᣠá¨áááµ ááá½á ááµá°á³á°áᣠá¨á¸áªá á¦á²áµ áááááµá¢ á¨Islamic Finance áá±áá á¨view_islamic_banking áá¥áµ áááááᤠá¨áá á¨á° áááµ áááááµá á áá áá±á áá ááá á¨á³áá¢","concepts":["áá«á á â á¨áááµ ááá
á á°ááḠáµáá áá¸á¥","á¢áá« â á áá á ááááµ á¨áá ááá
áªá«á","áá³á¨á£ â áµáá á ááá«áµ á¨á á°á« á áµá°á³á°á","áá»á¨á« â á¨áµáá» á½áááᦠáµáá á áµááááµá£ áªá³á« á ááá® áµáá» á¥á»","ááá áááá â áááá¬áá½á£ áááá á¨á£áá© áááµ áááªá«áá½","AAOIFI â á¨á¥áµááá áááááµ á°áááµ á¨áá³á¥á á¦á²áµ áááááá½"],"example":"á°áá áá á«á áááµ á¥áµá áá£áªá« ááááµ áááááᢠáá«á áá á°á ááᦠá£áá© áá£áªá«áá ááᶠá á°ááḠáµááá á ááá« ááááá¥á áá¸á¥áá³áᢠáµáá á áá á°áá á áááá¨áµ áááá«áµ á áá°ááá¢","tips":["áµáá á áá á°áááᦠá áááá¨áµ áááá«áµ á¥áá°áá áá£á á áá½áá","á áá»á¨á« áªá³á« á ááá® áµáá» á¥á» áá¨ááááᣠáµáá á áá ááááµ á¢á¨áááá","ááá á¨áá³á¨á áá±á ááááá¸á á¨Â«á£áá» ááááµ áµáá
á¶á½ á¥á» áá","á¨áá á¨á° áááµ áááááµ áá
á áá±á á¥áá° á¥ááááµ ááááá"]},"tokenization":{"title":"á¨áá¥á¨áµ á¶ááááá½á","summary":"á¥áá° á¶áá á¨áá¡ á¥ááá°á áá¥á¨á¶á½á¦ á¨áá¥á¨áµ áááá¥á áááµá£ á¨á°ááµ áá¨ááá«á£ á¨áµáá» ááá£áµá£ á¨á£áá¤á¶á½ áááá¥á á¨áᢠááááá¢","whenToUse":"áµáá
á± á¤áµá£ áá£áªá« ááá áá áá¥á¨áµ áá° áµáá» ááá® áá£ááá¥á¶á½ á²á¸á¥ ááá£áᦠáá¥á¨á±á ááááá¥á£ á°áá¶á½á áá¨ááá¥á£ á¶áá ááá£áµá áᢠáá¨áááᢠá¨RWA Tokenization áá±á áááááá¢","concepts":["á¨áá¥á¨áµ áááᥠâ áááá«á£ áááµá£ á°áá¶á½á á¨áá¨ááá« ááá³","áá¨ááᥠâ á¨ááá£áµ á ááµ á£áá¤áµááµáá áááµá áá¨ááá¥","á¶áá ááá£áµ â á¨áµáá» á¥ááµá á¨á ááµ áµáá» áá","á£áá¤á¶á½ â áá áá á«á
á áµáá» á¥áá°á«á","á¨áᢠáááá â áá£áá¤á¶á½ á áµáá»á¸á áá á ááá«","á¦áá¶á½ â áá£ááá¥á¶á½ á¨áááá¡ á¨áá³ áá£áªá«áá½"],"example":"áááá á°ááᶠá°á¨ááá§áᢠá¨áµáá» á¥ááµáá á¨á áá±á áá á áµááá¡á¦ á¨áᣠá áá á ááá¨á©áᣠáááá«á±á á£ááá¥á¶á½ áá
áá á áááá áá á¨ááááµá¢ á¨áªá«á áá¢áá áá£áá¤á¶á½ á áá°á á ááá« á á¨áááá¢","tips":["á¨áµáá» á¥ááµá áá á ááá£áµ áá áááááᦠá¨á°á¸á¡ á áá á ááá¨á©á","á¨áá¥á¨áµ á°áá¶á½ á áá áá¨áá» áááá£á â á ááá á³ááá¨á ááá«á","á¨áµáá» áááá¡á ááµá¨á© ááááᤠá á°áá°ááµ áá ááá£áµ á¨á°áᨠá¨á¥ááá¼áá áá±á ááááá","áá¢á á ááá« áá á£áá áµáá» áá¨ááááᣠá áᢠáá á£áá á áá°áá"]},"infraFinance":{"title":"á¨áá á¨á° áááµ áááááµ","summary":"á¨áá á¨á° áááµ áá®ááá¶á½ á á᪠á³á½á¦ááµá¦ á¨áá¥á¨áµá£ á¨á¦ááµá á¨á±á©á áááµááá®á£ á¨á©áá ááá« ááááá¥áá áá£ááá¥á¶á½ áªáá
1á¶á½á¢","whenToUse":"á¨á¨á
á áá áá®áááµ á ááªáá½ ááá£áᦠáááµááá®á áááá¨áµá£ á¨ááá¥ááá á¨á©áá ááá« áá¨ááá¥á áá£ááá¥á¶á½ á¨áá áªáááµ áááááµá¢ á¨Infrastructure Finance áá±á áááááᤠá¥á± á°áá Islamic Finance áá áááá¢","concepts":["áááµááá® â áá¥á¨á¶á½á£ á¨áá¡ á¦áá¶á½á á±á©á á á ááµ á¥áá³","á±á©á â á¨á¦ááµ á¥áµááá á á»á¦ á¨áááµ ááá
á¨áá¥á¨á± á¨ááá áá¢","á¨á©áá ááááá¥á â áá£ááá¥á¶á½ á¨ááá¥á ááá«áá½ ááá áá á","á¨á£ááá¥áµ áªáááµ â áá°áá¨á á áá á¨áááµááá® ááá³ ááá£áµ"],"example":"á¨á©áá ááá« á á ááµ á³áááµ ááµá¥ áá°áá³áᢠá á³á½á¦áá± áá ááá á¨á£ááá¥á¶á½á áá¥á ááµá¹á£ á¨áá« á¨áááá áªáááµ á áááᦠá¨áááµááá®á ááá³ á¥áá° áá¨ááá« áá° á£ááá¥á¶á½ ááá³áá¢","tips":["áá±á á Islamic Finance áá ááá á¨á³áᦠá«á á¥á± ááá áá á áá ááááá","á±á©á á¨áá¥á¨á± áᢠáá¨ááá á¥áá á¥áá° áááµ á áá°áá â áá
áªááá±áá áááá«á","áªááá± á ááá£áµ áá á«ááá á¨áááµááá® ááá³ á«á³á«á"]},"programmableMoney":{"title":"áá®áá«á á¨áá°á¨á ááá«áá½","summary":"ááá³ á²áá á¨ááá¸á ááá«áá½á¦ á áá«ááá½ á¨áá« áá½á°á
ᣠá¨áá á¨áá¨á ááá ááá£áµ ááá á¨áá áá°á¥ ááµá¨áµá¢","whenToUse":"áááᥠáá²á«áá á³ááá á ááá³ ááá£áµ á²ááá áµ ááá£áᦠááááá½á áá°á¥á°á¥á£ á¨áá ááá áá¨ááá« áá á á
ááá á¥áµá¨ áá áááá¨áµá¢ á¨Programmable Money áá±á áááááá¢","concepts":["ááá³ â ááá«á á¥áá²áá¸á áá ááá á¥áá³áá áµ","áá«ááá½ â áá½á°áá¸á á¨áá«áµáááá¸á á á£ááµá á¥áá³á¸á","á¨áá ááá â ááá³áá á¨áá«áµáᣠáá¨á","á¨áá áá°á¥ â á«áµ-á°á á¨ááá¸áá« ááá á°ááµ"],"example":"á¥á«á á¨á°á¨á¨á á áá áá°áá«á ááá«á¢ «á¨á¦áµáµ áá«ááá½ á¨ááá± áá½á°á
» á áá ááá³ ááá« áá á©á¦ áááá¡ á°áááᣠáá ááááá¹ á²áá á¥á» ááá£áá¢","tips":["ááá³á áááá¡ á¨áá«á á ááµ áááá£áᤠá áá á ááá¨áá","áá«ááá½á á á°á á£á£á áá¨á¡á¦ á¨á áá± áá¨ááµ ááá«áá á«ááá","á áá áá°á¥ á¨ááá¸á ááá« á«áµ-á°á áá á«á â á¨á°ááµ áááá ááµá¹"]},"otherProducts":{"title":"ááá½ ááá¶á½","summary":"á¨á°áᨠáá±á á¨ááááá ááá¶á½á¦ á¨áµá¦á³ á«áá¶á½á£ á¨á á á áµá«ááµ ááá¶á½á áá
áᣠá¨ááá á¤áµ áµááµáá á¨Â«á¼áá®ááµáµÂ» á¨ááá«á¨á áááá¢","whenToUse":"áá±á á³ááá áááá ááá¶á½ ááá£áᦠá¨áµá¦á³ á«ááµ á¥á
á ááá£áµá£ áááµ áááá ááá á¨Â«á¼áá®ááµáµÂ» ááá áááá£áµá¢","concepts":["á¨áµá¦á³ á«áá¶á½ â áµá ááᣠá®á¶á½á áá á
ááá á¥á
á ááµá«á£ á«áá¸á á¥á
áá½","áá
áá á á á áµá«ááµ â ááá¶á½á á¨áᢠáááá á«áµ-á°á ááá«áµ","á¨ááá á¤áµ áµááµá â á áááᬠá¥á
á á᪠áá³á¥","á¨Â«á¼áá®ááµáµÂ» ááá â áá
á á¨á°á¥áᣠá¨ááá«á¨á áá¨á¥áá á¨áá« áááááµá á¨áá«ááá á áá¥"],"example":"áá áá á¨áµá¦á³ á«ááµ á¥á
á á«áµááááᢠáµá áááá á¥ááµá á áµááá¡á¦ áá á
ááá á¨á¥á
á áá á ááµá«á£ áá«ááᣠáµááá
áááá¡ á«ááá ááá£á± á áá³á«áá¢","tips":["á¨á¥á
á ááµá«á£ áá á áá áá«ááᦠáááᥠá«á ᨠááá£á± á áá³á«á","á¨áááá á¥á
á áá²á«áá áááá« ááá á áááá"]},"partners":{"title":"á áá®á½","summary":"ááµá¨á© á¦áµáµ á°á¨á á ááᦠá¨ááµá¨á á áµá°á³á³áªá£ á¨áµáá
á± áá á°áá áᣠá¥á á áá â á¨á°áá áá½á á°áá áᢠáá
ááá á¨á áá© á¨áááá áá áá°á áµá£áᦠá¨á áá®á½ ááááᣠá«á³ááá»á¸áᣠá¨ááá« á áááá½á á¨áá¢áá½ á¨á°ááá¡ á«áá¶á½á¢","whenToUse"
1:"á á²áµ á áá á²ááá ááá á á¥á± áµá á ááµ ááá á²áááá¢","concepts":["á áá á¨á«á¢á á°á áá á áá°ááᤠá¨áµáá
áµá á á«á ááᢠááµá¨á© áá¨ááá á á áá ááá« ááá«áá¢","á«á³ááᣠá áááá½á á«áá¶á½ á¨á¥á«áá³áá± á áá áá¸áᦠá¨áµáá
áµ á á ááá á«á³áá á¨ááá¢","á¥ááá
áá¾á½ á¨á«á³á¸á ááá¶á½ á áá¸áᦠview_productsᣠview_linksᣠmanage_cardsá¢","ááá áµá ááá« ááá á á áá°ááᦠá°ááááá½á áááá¶á½ á «ááá« ááá á» ááµá¥ áá¸áá¢"],"example":"áµáá
áµ á¨ááµáá áá áá°á¥áá á¥áá° á áá á«ááááᣠá á«á³áá «ááá³á áááá£Â» áá¨áá«áᣠá¨áá«á á¨ááá« á ááá áá á«áá¢","tips":["á¥á áá¥áá½ á²áá© á á áá áµá ááááá¢","á ááá á«á± ááá á á«á¨ááááᦠááááªá« á¨á áá©á ááá« ááá á áááá¨á±á¢","á ááá ááá á¥áá°ááá¨ááµ á¨áááááá á ááµ á¨á áá©á á°áá£áááµ á«á¨ááá¡á¤ á ááá á á«á± ááá á á«á¨ááááá¢"]},"erm":{"title":"á¨áµáá
áµ áµááµ","summary":"á¨áµáá
á± á¨áµááµ áá°á á á ááµ á¦á³á¦ á°áá¥á¯áá á᪠áááá á«áá á¨áµááµ áááá¥á£ á°áááá á¨áááµ á«áá³á£ á¨áµááµ ááááµá£ ááá á¨áµááµ á ááá«á¾á½á£ á¨á°áá£á áªá³á« ááµá°á¶á½á£ áá¥á¥á®á½ á¨ááááá»á¸á ááᣠá¥á ááµáá¶á½á¢","whenToUse":"á¥áá° á¨áµááµ á áµá°á³á³áªá£ á¨ááµá¥ áá¥á¥á ááá ááá áááááµ á«áá á¥á« á áµáá»á áá°áá
ááá¡á¦ áµááµ ááááá¡á áááááᣠá¨ááááµ á á áááá áá¨á³á°áᣠáá°á£á° á ááá«á½ ááá½ ááµá¡á£ á¨á°áá£á áªá³á« ááááá¡á£ áá¥á¥á áááµáᣠááá áµááµá á¥áá³á áááá á á áá¨á á¥á«á áá áááµáᢠáá¾á¹ á¥áá° view_ermᣠassess_risksᣠmanage_erm_kriᣠregister_loss_events á¥á approve_risk_acceptance á£á áá¥á¶á½ ááá°á£áá¢","concepts":["á¨áµááµ áááᥠâ á¥á«áá³áá± áµááµ á¨ááá³á (á¨áá
ᣠááᣠá¨á°ááá°á£ á¨á°áá áᣠá¨á°ááᣠááá á«ááá áµ)ᣠá£áá¤á±á£ ááµá¡á á¨áá«ááá£á¸á ááááá½ áá","á°áá¥á¯áá á᪠â áááµ á¨áááá á½ááá½á¦ á¨áá¥á¥á®á½ á ááµá á ááᢠá ááá± áá«á¨á á«áá áá©ááµ áá¥á¥á®á¹ á á¥áááµ á¨áá«áá¡áµ áá","á¨áµááµ ááµáªááµ â á°áááá áááááᣠá¨3x3 á¥áµá¨ 6x6ᦠá¨ááµáá á¨á°á½áá á°á¨ááá½ áá¥á á¨áá±á á
áá¥á®á½ ááá£á á¥áá á á®áµ á¨á°á¸áá¨á¨ 5x5 á áá°áá","á¨áµááµ ááááµ â áµáá
á± á¨áá«ááá áá»á»áá á ááá á á áááᤠá¥á°áµ ááááµ áá á¥áá áªáááµ á áá°áá","ááá á¨áµááµ á ááá«á¾á½ (KRI) â á¨áªá³á«á á ááµ á¥áá á áá á¨áá«áµá áá
á á á¨ááá´/á¢á«/áá á°áá½ á«áá¸á á¨ááá© ááµááá¶á½","á¨áªá³á« ááµá°á¶á½ â á¨á°á¨á°á° á¨á°áá£á áµááµá£ á á£áá II ááµá¦á½ á¨á°áá°á ᣠá¨á á
ááᣠá¨á°ááá°á á¨á°á£á« áá á áá","áá¥á¥á®á½á ááááá½ â áµáá±á á¨ááá³á áááµá ááᣠá¥áá´áµ ááá°ááᣠá¨áµáá¹áá á¨áááá ááµááá¶á½ áá¸ááá","ááµáá¶á½ â áá¥á¥á á¨ááá á«á áµ á¦á³á£ á¨ááá¨á³ á¥áµá¨ áá á¨á³á áµáááµ á¨á°á°á¨á°á¨","AI á«ááá£áᣠá°á áááµáá â á AI á¨á°áá á¨á áá á¥áá° á¨áá
ááá£áᣠá«áá°á¨ááá á á 30 áááµ ááá á«ááá"],"example":"áµá á«áá°á³á© ááá«áá½ á¨áááá á ááá«á½ ááááµ á°á¨á³á³á áááµ áá° á¢á« ááá¨á«áᢠá ááá«á¹á áááá±á£ áááªá«áá¹áá á¨á°á«á«ááá áµááµ áááá¨á±á£ á¨áá«á á áµááµ á«áá± áá á«ááá á᪠áááá á«á¨ááá¡á¢ ááªá áá¥á¥ á¨á³ááá ááááµ á áá ááᤠáµááá
á¨áááµá áá
áµ áá¨áá³áᣠá£áá¤áµá á¨áá¨á¨á» áá áááµá£áᣠáá¥á¡á ááá¨áµ á«áá áµáá áá¥á¥á á«á«áááá¢","tips":["ááá±áá á½ááá½ áááááᦠá°áá¥á¯á áááá á¥á» á«áá áµááµ áá¥á¥á®á¹ á¥á¨á á© áµáááá ááá á ááááá","á¨ááµáªáá±á áá á á¨áá±á á
áá¥á®á½ á«áá¥á¡ â áµáá
áµ 3x3 ááá 6x6 ááááá áá áá áá½ááᤠá á®áµ á¨á°á¸áá¨á¨ 5x5 á¥á«áá³áá±á áµááµ á á°á³á³á° á¦á³ á«áµááá áá","á¨AI á¨ááá½ 30 áá á áá¸áᦠáááá¨á·á¸áᣠáááá¡ ááá«á¸á á«áá áá³á¦á½ ááá á¥áá²áá á áá°ááµ","áá á áá á¢áááµá á¥áá³ á¨áªá³á« ááµá°áµá ááááá¡ â áµáááá¹ á¥áá° áá á á«á
á á áµááá áá","áá½á á«áá°áá°á áá¥á¥á áá
áµ áá á¥áá áá¥á¥á á áá°ááᦠá¨áá°á ááá áá¥á©á á ááááµ á«áá©áµ"]}},"pages":{"setupWizard":{"title":"Setup Wizard","summary":"Setup Wizard áááááªá« processing ááááªá« á°á¨á-á -á°á¨á wizard ááᢠá á¥ááµ áá« áá¾á½ áá á á«áµ á¨á°á«á«á á á«ááµá (partner-merchantᣠprovider walletᣠpartner walletᣠterminal) á á
á°á á°á¨á°á ááá¥á«á á¥á á á áá«á multi-currency á«áááᣠá áá¨á¨á»á áá áá© á¨áá°á¡ ááá credentials á«áá£áᢠwizard á áá ááá« á á°áá«á© áááá½ á á¥á
á¥áá²á«áá
á© á¨áá ááááµ áá á¨field validation á¥á á¨á á«ááµ á á«áµ-á°á áááááµ áá á á ááµ áá¥á°á á°áá°ááµ á¥áá
á°á°á¥áµá§áá¢","whenToUse"
1:"á á²áµ ááá´ á¨áá® áááááµá ááá« ááá á ááá áááá á²ááá wizard á áááá±á¦ á¨á áá© áááá®á½ (emailᣠá¨á©á£áá« áµá) á¥á á¨ááá« á á
á«á¢ credentials (Merchant IDᣠAPI keys) á áááµá¢ áá
á¨ááááªá« ááá áá£á á áá«á¸áá ááá«áá
á á¥á á¦áá³áá½áá terminal á á¥á
áá¥á» ááá á áááááá á°á«á°á áá ááá³ ááᢠwizard á¨production ááµááá á ááµ á¨áá¨á« á á«á£á¢á á áá¥ááµ ááááááµ á¥áá° áá¹ ááááµá á áá ááá¢","concepts":["á¨Wizard á°á¨ááá½ â welcome (á á ááá á¥áá³) -> partner (partner-merchant) -> provider (provider + wallet) -> partner-wallet (partner wallet) -> terminal (terminal) -> multi-currency (á áá«á) -> completion (áá ááá«)ᢠá¨áá á«áá progress bar á¨á°á áááᣠá¨á ááᣠá¥á á¨ááá¡ á°á¨ááá½á á«á°áááá¢","\\"Partner\\" á°á¨á â merchant ááá¥á«áᦠEmail (loginᣠá
áá¸á± áá¨ááá£á)ᣠá¨á©á£áá« áµáᣠPassword (á á«áµ-á°á á¨á°áá ᨠ12 áááᣠá¢á«ááµ 8ᤠá¨áá³á¨áµá á¥áá°áá-á¨áááá¨áµ á áá«á®á½ á ááµ)ᣠá¥á \\"Enable Partner Area access\\" checkbox (á áá£áª á¨á á« â á áá© áá° á¨áá á á«á£á¢ ááá£áµ áá½áá)á¢","\\"Provider\\" á°á¨á â á á«á£á¢ ááá¨á¥ (á áá£áª Testᣠááááá ááá¨á«á / Production)ᣠá¨áááá© á¨ááá« á á
á«á¢ ááááá ááá¨á¥á£ á provider schema áá á¨áµ credentials ááµáá£áµá£ á¥á á¨ááá« áá´áá½á áááá¨áµ (bank_cardᣠsbpᣠapple_payᣠgoogle_payᣠcrypto)ᢠgeneral á áá áá áµá provider wallet ááá á«áᢠá¥áá
á¨á°áá¨á á á á«á£á¢ á ááá á°á¨á³á á á«ááµ ááá¨á³áá¢","\\"Partner wallet\\" á°á¨á â áááᣠáááᥠInternal Walletᦠáááᬠá¥á» ááá¨á£á (áá£áª á¨provider áááᬠáá)ᣠáµá áááá general ááᣠááááµ internalᢠá¨á¥á± áá backend á¨á áááááµ á¦áá³áá½á FEE (á¨fees áá á«ááá«) á¥á HOLD (á processing áá
áµ áááᥠáááµ) á á«áµ-á°á ááá¥á«áá¢","\\"Terminal\\" á°á¨á â á áá©áᣠprovider áᣠá¥á á¦áá³áá½á á«ááááᢠááááµá¦ payment (ááá« ááá á) ááá payout (ááá« áááá) â á á ááµ terminal á ááµ á¥á»á¢ áá
á°áá á¨áá°á áá áá½ ááááá (áá£áª 100 á¥á 500,000 á áááᬠáá á áá¶á½á£ á á¥áá
á á áá¶á½ ááá£á) á¥á á¨á áá feeᦠáá¶á (áá£áª 1.5%) á¥á áá áááá¢","\\"Multi-currency\\" á°á¨á (á áá«á) â á backend áá ááµáá
á± multi_currency_enabled flag á¨áá áá³á«áᢠá ááá áááá¬áá½á áá áááᣠá¨pricing plan áááᬠáá°á¥á á«á¨á¥á«áᣠá¨adapter warnings á«á³á«á (á¨áµáá¹ áááá¬áá½ routed á¥áá³ááá)ᣠá¥á á²á¨ááᥠchart of accounts á¥á áá£áª 0.5% FX markups ááá¥á«áᢠá°á¨áá áááá áá½ááá¢","Completion â á¨á°áá á© áááá á á«ááµá IDs á«áá¸á cardsᣠá¨áá
á á á°á¨á᪠á¨á áá© credentials á«áá á¥áá (á¨Partner Area linkᣠLoginᣠPassword) á¨á
á á áá«á®á½ ááᢠPassword á ááµ áá á¥á» áá³á«áᢠá¨áá
áá° Dashboard áááµ ááá áá²á«áá áá á áá áááá áá½ááá¢"],"example":"áá³áᦠá áá¨á« á á«á£á¢ á Sber á á©á á«áá¶á½á áááá á á¨ááµáá áá á±á
áááááµá¢ \\"Partner\\" á°á¨áᦠemail [email protected]ᣠáµá \\"My Store LLC\\" á«áµáá¡á£ á¨á°áá á¨áá password ááá áᣠá¨Partner Area checkbox á áá«áᢠ\\"Provider\\" á°á¨áᦠá á«á£á¢ Testᣠá¨áááá© provider á á«ááᣠMerchant IDᣠAPI Usernameᣠá¥á API Password áááᣠbank_card á¨ááá« áá´ á«áááá± â áµááá± provider wallet general á RUB ááá¥á«áᢠ\\"Partner wallet\\" á°á¨áᦠáááᬠRUB (á á«áµ-á°á á°ááá·á)ᣠá¥á FEE á¥á HOLD á¨ááá á¦áá³ áá ááá á«áᢠ\\"Terminal\\" á°á¨áᦠááááµ paymentᣠáá
á°á 100 RUBᣠá¨áá°á 500,000 RUBᣠfee 1.5% + 0 ááᢠmulti-currency á ááááᢠá áá¨á¨á»á áá« áá½ á¨Partner Area linkᣠLoginᣠá¥á Password á ááµá°á áá áá© ááµá¡á¢","tips":["á áá¨á¨á»á áá« áá½ áá á«áá á¨á áá password á ááµ áá á¥á» áá³á«á â áá° Dashboard á¨áááµá á ááµ áá
á³áµáá á«á¨ááá¡ (\\"Copy all\\" á áá«á á¨Partner Area linkᣠLoginᣠá¥á Password á á á¥á® á«áµá°áááá)á¢","á á«á£á¢ (Test ááá Production) á \\"Provider\\" á°á¨á á ááµ áá á°ááᦠáááá á á«ááµ â á¦áá³áá½á terminal â á ááá³ áá°áá á«áᢠprovider wallet á¨ááá áá á ááµ áááµá¹áµá¤ ááá¥á³ áµá«áá ááᶠá¨á°áᨠprod terminal á«áµááááá¢","á \\"Terminal\\" á°á¨á áá á«á á¨áá°á¥ áá áá½ á á¥áá
á á áá¶á½ (kopecksᣠcents) ááá£áᤠáá° áá áááᬠááá¨á© á¨field á á³á½ áá³á«áᢠá¨áá°á áá á á¨áá
á°áá á á¥á¥á
á¨áá áᥠááá á áá áµá£ á¥á á¨fee áá¶á á¨0 á¥áµá¨ 100 ááá á áá áµá£ á áá ááá« form á ááá ááá¢","wizard á¥áá°áá ááµá¬áµ á°á
ááá± á¨á°á á á ááᦠá áá ááá provider walletᣠááá á¥áá°áá
á«á áááªá«áá½ á«áá terminal á áµááµá á«áᣠáµááá± duplicate error á¨ááááá ááá
áá£á©á á á«á á¥áá°áá áá áááᢠ\\"Add another partner\\" á áá«á wizard á áá° ááááªá« áááá³áá¢","\\"Multi-currency\\" á°á¨á ááá³á áá½áá â áá
áµá
á°áµ á áá°ááᦠá áµáá
á± backend flag ááá£á á«áᢠá¨Adapter warnings (\\"no adapter\\"ᣠ\\"does not route\\") áá¨á á°áª áá¸á á¥á á¨áááᬠááá«á á á«áá±áá¢"]},"systemSettings":{"title":"á¨áµáááµ á
áá¥á®á½","summary":"á \\"Administration\\" ááá ááµá¥ á«á á¨ááµá¨á ááá á áá á
áá¥á®á½ áá½á¢ á á²áµ áá°áá á© áµáá
á¶á½ á¨áá°áá á© áá£áª á¥á´á¶á½á á«ááááᢠá á áá áµá
1ªáµ ááµá¥ á áá¹ áá á ááµ á¥áá á¥á» ááá·á â \\"Fee Configuration\\" â áá
á áá° pricing plans áá½ á«áá«áᣠá¥áá«á á á
ááá á¨fee ááá
á áááá«áá¢","whenToUse":"áá á²áµ áµáá
á¶á½ á¨ááµá¨á©á áá£áª á£á
᪠ááá°á½ ááá áááááµ á²ááá áááá áááá± â á ááááµ á¨SaaS fee á¥áá´áµ á¥áá°áá°áᢠáá³á¨á»á áá áµá°á³á³áªáá½ á¥á» ááᦠá¨á áµá°á³á³áª áá á¨ááááµá£ áá¹ \\"Available to administrators only\\" ááµá áááá« á«á³á«á á¥á ááá á
áá¥á á á«á³ááᢠááµá³áá»á¦ á
áá¥á®á¹ á¨ááá¡ á áá á¨á°áá á© áµáá
á¶á½á á¥á» ááá«áᤠáá£á áµáá
á¶á½á á ááá©áá¢","concepts":["áá áµá°á³á³áªáá½ á¥á» áá³á¨á» â áá¹ áááá (isAdmin) áááµá»áᢠá¨á áµá°á³á³áª áá¥áµ á¨ááá á°á áá á¨á
áá¥á®á½ ááá
áá ááµá áááá« áá³ááá³áᣠá¥á ááá á°áá£á á°á°á¥ááá¢","áá á²áµ áµáá
á¶á½ áá£áª á¥á´á¶á½ â á¨áá¹ ááá áá³á¥á¦ á¥áá
á¨á°ááá áááªá«áá½ á¨á ááá áµáá
á¶á½ á áááá©á ááá áá á¨á°ááá¡ á áá áááá á©áµ ááá» á¥á´á¶á½ áááá (á¨áá á«áá áá¨á á°áª banner áá
áá á áá¥á³ áááá»á)á¢","Fee Configuration â á áá¹ áá á«áá á¥á¸á á°á¨á£á á¥ááᢠfees áá°á á²á á¥áá
á áá¥á³ ááµá°á«á¨á áá áᤠá áá á¥áá© á¨SaaS fee áááá áá° pricing plans áááá©á á«á¥á«á«áá¢","\\"Go to Pricing Plans\\" á áá«á â á°á áááá áá° /pricing-plans áá½ áááµá³áᣠfees á¨áááá©á áµá¢ áá
á áá¹ áá á«áá á¥á¸á áµáááµ ááá¢","Pricing plans fees ááááªá« á¦á³ â á á¥áá© á½áá áá á¨áµá£ á¥á«áá³áá± á¥á
áµ á¨á«á±á á¨fee ááá
á á¨multi-currency áµáá áá áááá»áᢠáááµá fee á á ááµ ááá á áá áá¥á á³ááá á á°áᨠá¥á
áµ ááµá¥ áááááá¢"],"example":"á á²áµ á°á«á°á á°áá£á á°á°á áᦠ\\"ááááááá¸á á°áá áá½ á¨ááµá¨á fee á«áááá¢\\" á á áµá°á³á³áª áá \\"Administration -> System settings\\" á áá¨áá³áᢠá¨áá á°áá«á áá¨á á°áª banner á«á«áᦠá
áá¥á®á¹ áá£áª á¥á´á¶á½á á«áááá á¥á á¨ááá¡ á áá áá°áá á© áµáá
á¶á½ áá°áá á«áᢠá¨á³á½ \\"Fee Configuration\\" card á²áá á¨SaaS fee áááá á áá á pricing plans á á©á á¥áá°ááµá°áááµ á«á¥á«á«áᣠá¥á«áá³áá± á¨á«á±á á¨fee ááá
á á¨multi-currency áµáá áá áááá»áᢠá°á«á°áá \\"Go to Pricing Plans\\" á á á
á«á°áááᣠáá° /pricing-plans áá½ áá°áá³áᣠá¥á á¥áá« á¨áááá á¨fee áááªá«áá½ á«áá á¥á
áµ ááá¥á«á ááá á«áµá°á«áááᢠfee á áá¥á³ á \\"System settings\\" áá½ áááááµ á áá á á«áµáááá â áá
á¨ááá¢á« áá¥á¥á áá¥á«áªá« á¥á» ááá¢","tips":["á áá
áá½ áá á¨fee áá¤áµ fields (áá¶áᣠááᣠáá
á°áᣠá¨áá°á) á áááá â á á áá áµáªáµ á¥áá
á¨ááᢠfee áááá á«á± áá° \\"Pricing plans\\" ááá á°ááá¯áᤠá¨áµáááµ á
áá¥á®á½ áá½ á á áá«á á á©á á¥áá« á¥á» ááá«áá¢","áá°áá á«áµá³áá±á¦ ááá¦á½ á¨á°ááá¡ á áá áá°áá á© áµáá
á¶á½ á¥á» áá°áá á«áᢠá áµááµá á¨áá áµáá
áµ ááá½á áááá¨áᣠá¨ááá á áá áá£áª á
áá¥á®á½ ááá
á áá¥á³ á«áµá°á«áááµá¢","á¨á
áá¥á®á½ ááá
\\"Available to administrators only\\" ááµá áááá« á«á© â áá³á¥á á¨á áµá°á³á³áª áá á¨áááᢠá ááá½ áááá½ á á©á áááá á¨ááá¨á ááá
áááá½á á¨áá«áµá°á³áµá á°á áá³á¨á» áá ááá¢","á pricing plans ááµá¥ á«áá fee á¥á áááá¬áá½á áá°ááá á¥á áá¥á«áá³áá± á¥á
áµ á¨á°áᨠááᢠá¥á
áµ á¨ááµá°á«á¨áá á ááµá£ á¨áá«áµáááááµá áµáá
á¶á½ á¨áá«áááááá áµáááá á¥á
áµ á¥á¨á¨áá± áá
1áá á«á¨ááá¡ â á¥áá
áá á \\"áá á
áá ááµá¨á© á ááµ áá¥á\\" á¨ááá¢"]},"terminals":{"title":"Terminals","summary":"terminal áááᥠáááá á ááá ááááá á¨ááµá¨á© áá° á°áᨠprovider (á£ááᣠSBP gatewayᣠááªáᶠá áá³á¨ áá¨á¥) á¨á°ááᨠá¨áááááµ áá¥á¥ ááᢠ\\"Terminals\\" ááá á¨ááá á¥áá°áá
á«á ááááá¶á½ registry ááᦠá¥áá
ááá á«áᣠáááá«áᣠá¥á áááá/áá ááᣠá¥á routing engine á¨áµáá terminal á¥á«áá³áá±á áá¥ááµ á¥áá°áá°á« áááá¨á¥ á¥ááá
á á
áá¥á®á½ áá áááá¢","whenToUse":"ááá á á²áµ á¨ááá« provider ááá«ááá ááá áá áá ááá« ááá á/áááá ááá«áá
á á°á«á°á ááᦠáááá¬á£ á¨áááá ááááµ (ááá á ááá áááá)ᣠá¨áá á áá°á¦á½á£ feesᣠprovider credentialsᣠá¥á á¨ááá á« ááá½á áááááµá¢ á½áá á«áá áµá á»áá ááá«á á¨áá«á áá áµ (\\"Active\\" á ááá³áµ ááá weight á 0 ááµá¨á)ᣠá°áá³á³á áá
á á¨áá«á£áá áµá£ ááá á¨á°áᨠterminal á ID á¨áá«ááá áµá ááᢠáááá© á áááµ tabs á°á¨áááᦠ\\"Regular terminals\\" (á¨á ááµ á áá áá á¨á°á«á«á) á¥á \\"Shared terminals\\" (áááááá á áá á¨ááá)ᢠá¨á á«á£á¢ áá£áªá« (prod/test/all) á¥á á ID ááá á áᢠ\\"Routing Editor\\" á áá«á áá° á¨á°áᨠrouting rules editor ááá«áá¢","concepts":["Provider á¥á á¨áááá ááááµ â provider (ááá³á tbankᣠalfabank_sbpᣠethereum) ááá«á á á¨áµáá á£áá/gateway á¥áá°áááµ áááµááᤠááááµ payment (ááá á) ááá payout (áááá) á¨áá¥ááµ ááááµ áá ááááµ á áá áµá£ á áá ááá« terminal á ááµááá","Priority vs Weight â á¥ááá
á¨á°áá«á© ááá®á½ áá¸áᢠPriorityᦠáá
á°á á¥á´áµ = ááµá ááá°á»á (0 á¨áá°á áá)ᢠWeight (0-100)ᦠá áµááµá á¨á°áµáá terminals áá«á¨áᣠá¨áá°á weight = á¥á áá ááá¨á£áᤠweight=100 á¨weight=50 áááµ á¥á¥á ááá¨á£áᤠweight=0 terminal á á¨routing áá á áá á«ááá","á¨áá á áá°á¦á½ á á¥áá
á á áá¶á½ â min_amount á¥á max_amount á kopecks/cents áááááᣠá rubles á áá°ááᢠ100 rubles = 10000ᣠ1 ááá®á rubles = 100000000ᢠáá¥ááµ á¨áá«ááá min_amount <= amount <= max_amount á¨áá á¥á» áá","provider_wallet_name â á¨áá´á³ fieldᢠá provider á á©á á«áá á¨á¦áá³ ááá« ááᢠá£á¶ á¨á°á°áᣠterminal á routing áá
áµ á ááá³ á¨ááá« áááµááᣠá¥á ááá«áá½ á á¥á± á á©á á ááá±á","Provider parameters (provider_params) â áá°áᨠá»áá credentials á¥á á
áá¥á®á½ (keysᣠlogin/passwordᣠterminal_keyᣠreturnUrl/failUrlᣠá¨ááá« áµáááµ ááááµá£ fiscalization)ᢠá form builder ááá á¥áá° JSON ááááᤠáá¥á providers \\"Apply template\\" á áá«á á á","Inspector parameters (inspector_paramsᣠLimitsV2) â áá¥ááµá á¨ááµá«áµ á ááµ á¨áá°á© á¨ááá á« ááá½á áá°á¦á½á¦ á á«ááµ ááá áá£áªá«á£ á¨ááá« áµáááµ (Visa/MC/MIR)ᣠá¨áááµ áá á áá°á¦á½á£ ááá°á¢ á¥áá²áá áá°áá á á¨áá³á¨áá á¨ááµá
ááá¥ááµ áááá»á","Regular vs shared terminal â terminal partner_id ááá shared=true ááá¨á ááá£áᣠááá±á á áá°ááᢠshared terminal áááááá á áá á«áááááᤠregular á¨á°áá°á áá á áá á¥á»","The acceptance run before live traffic is a mandatory set of scenarios on a test terminal: success, decline, timeout, refund, partial capture. A skipped scenario surfaces on real money, and it is most often the timeout.","Cardholder authentication is switched on at the terminal and changes the payment path: the operation gains a confirmation step at the bank, so the share of abandoned payments rising after you enable it is expected rather than a fault.","á¨ááªáᶠááá á« ááá²á áµáá
á± á«ááááᣠááá áá á°áááá áá½á¨á áá½ááᢠá«áá°á© á°ááááá á áá áᣠá áááá¬á á á áá áµááááᥠáµááá½ ááá«áá½ á áá¥á³ áá° á¦áá³á£ áá°á áá¹ á°áá á á ááµ áá á áµá«á» ááá± áá½ááá¢"],"example":"á°áá£áᦠáá áá \\"Romashka\\" (ID 42) á T-Bank á á©á á¨RF á«áá¶á½ ááá á« áááááµá¢ \\"Create terminal\\" á á á
á«áµááᢠPartnerᦠRomashka (IDᦠ42)ᢠProviderᦠtbankᢠá á«á£á¢á¦ prodᢠááááµá¦ Paymentᢠáááá¬á¦ RUBᢠPriorityᦠ0 (ááááªá« áááµá¹)ᢠWeightᦠ100ᢠ\\"Active\\" á áááµá¹á¢ á \\"Amount limits\\" á¥áá min_amount = 10000 (áá
á 100 rubles áá) á¥á max_amount = 100000000 (áá
á 1 ááá®á rubles áá) á«ááá â ááá±á áá áá½ á kopecksᢠá \\"Wallet settings\\" ááµá¥ ááááµ internal ááá¨á¡ á¥á \\"Provider wallet\\" (provider_wallet_name) á ááááµáá á«á¨ááá¡á£ ááá³á general â á«á á¥á± terminal á áá°á«áᢠá \\"Provider parameters\\" á¥áá ááµá¥ átbank \\"Apply template\\" á á á
á«áµáá á¥á terminal_key á¥á terminal_pass á«áµáá¡á£ á áµááá á¨ááá returnUrl/failUrlᢠá«áµááá¡ â terminal á áááá© ááµá¥ á á á¨ááá´ \\"Active\\" badgeᣠprod badgeᣠá¥á ááááµ payment áá³á«áᢠá áá á¨á áá 42 á RUB á¨
1100 rub á¥áµá¨ 1 ááá®á rub ááá«áá½ áá°áá
á»áá ááá© áá½ááá¢","tips":["áá áá½ á kopecks/cents áá¸áᣠá rubles á áá°ááᢠá á£á á¨á°ááá° áµá
á°áµá¦ \\"á¥áµá¨ 10,000 rubles\\" á¥áá á°áµá á áµááá 1000000 ááµáá£áµá£ á á¥ááá± \\"á¥áµá¨ 10,000 rubles\\" = 1000000 kopecksᢠá¨áá®áá½á á¥ááµ á°ááá áááµá¹á¦ rubles á á 100 á«á£á","provider_wallet_name árouting á¨áá´á³ ááᢠá£á¶ á¥á´áµ á ááµááᥠáá áµá
á°áµ á á«ááááᣠááá áá terminal á ááá« áá
áµ á ááá³ ááááá â ááá«áá½ á ááá±áᣠá¥á áááá«á± ááá½ á áá°áá","á»ááá ááá«á ááá¥ááµá£ terminal á á áá°ááᦠ\\"Active\\" á á«áá± ááá weight á 0 á«áµáá â ááá±á á áá«á®á½ á
áá¥á®á½á á³á«á¡ á¨routing á«ááá³á","á¨routing áá£áªá«áá½ á
á°á á°á¨á°á á°áµá°á«ááá (envᣠpriorityᣠcurrencyᣠpartner_id -> activity -> á¨ááá« áµáááµ ááááµ -> á¨áááá ááááµ -> route -> á¨áá á áá°á¦á½ -> weight != 0 -> á áá°ááµ áá¨á«áá½ á«áá°á áá terminal -> provider_wallet_name á¨á°ááá -> traffic level -> inspector limit checks -> á weight á¨áááá° ááá«)ᢠterminal \\"á¥á¨á°áá¨á á«ááá\\"ᣠá áá
á°áá°ááµ áááµá¹á¦ á¨áááá¬á£ á¨á á«á£á¢á£ ááá á¨áááá ááááµ á áááááµ á á£á á¨á°ááá± áááá«á¶á½ áá¸á","á¨áá á« form á browser ááµá¥ draft á á«áµ-á°á á«áµááá£áᦠá¥áá°áá á²á¨ááµ á«áá°á ááááá áá
á áááááµ á«ááá£áᢠáá°áá³á³á terminal duplicate á áá«á áá áá (á card áá á«áá á¨á
á icon) â á¨ID á áµá°áá áááá fields á«áµá°áááá","Shared á¥á regular terminals á á°áá«á© áá¾á½ ááµá°á«á¨ááᢠá áá á ááá°á á á°áá³á³á áá terminal á shared ááµá¨á á áá½áá â á áá±á ááá¨á¡","Promoting a terminal to production is done by a separate wizard: it reproduces the verified test configuration with an explicit list of changed fields, rather than by copying by hand."]},"providerConfigs":{"title":"Provider Configurations","summary":"á \\"Payment acceptance\\" ááá ááµá¥ á¨áµáá¹ á¨ááá« providers (acquirersᣠá£áá®á½á£ wallets) á¨áµááá± áá á¥áá°á°ááá á¥á á¥á«áá³áá± á¥áá´áµ á¥áá°á°ááᨠá¨áá«á³á á¨áá£áá» áá½á¢ read-only á¥áá³ ááᦠá¨provider áááªá«áá½á á¥áá
ááááá áá½áá ááá áá á áá
áá½ áá ááá¨á á áá½ááá¢","whenToUse":"á áµááá± ááµá¥ á á á
áá á¨áµáá¹ providers á¥áá³áᣠá¨á°áᨠprovider áá
ᶠá¥áá°ááᣠá á¨áµáá¹ áááá¬áá½á áá¨áµáá¹ á¨áááá áááá¶á½ á¥áá°áá°á«á£ á¥á áá¥á± á¨áµáá¹ á´ááá«á áááªá«áá½ (config) á¥áá°á°ááá á áá¥ááµ ááá°á½ á²ááá áá¹á áááá±á¢ ááµáá á°á«á°áá½á£ integratorsᣠááá analysts \\"ááá« ááá á áá
provider áá°/á ááá°á\\" á²áá¨áá© ááá routing á²á«ááá á áá ááᢠááᥠá¨backend á GET /providers/config á á©á áá³á£á á¥á ácachedᤠá¥áá
ááµá°á«á¨á á áá»ááá¢","concepts":["Provider â á¨á°ááá á¨ááá« á áá áµá (acquirerᣠá£ááᣠe-wallet)ᣠááá³á sber ááá stripeᢠáá
á¨card/á¨áµá ááá áá","StatusᦠEnabled / Disabled (á¨enabled field) â á á¨ááá´ \\"Enabled\\" badge provider áá áááá á¥á ááááá½á ááµá¬áµ á¥áá°áá½á á«á³á«áᤠáá \\"Disabled\\" árouting ááá«á á ááááá±á á«á³á«á","áááá¬áá½ â provider á¨áá°á«á£á¸á áááá¬áá½ áááá (ááá³á RUBᣠUSDᣠEUR)ᤠá¥áá° badges áá³á«áᢠáááá© á£á¶ á¨áá á°á¨á \\"-\\" áá³á«á","áááá¶á½ (Types) â provider á¨áá°ááá¸á á¨áááá/á»áá áááá¶á½ (á¥áá° á°áá«á badges áá³á«á)ᢠá£á¶ á¨áá â á°á¨á","Configuration (config) â á¨provider áááªá«áá½ á«áá á´ááá«á JSON objectᤠprovider á¨áá¨á¡ á áá á áááá®á½ ááá ááµá¥ á¥á» áá³á«áᣠá indentation á¥á scrolling á°ááá¿á","á¨á¥áá³ ááá³áá½á¦ Grid â á¨provider cardsᣠá¥á Table â á¨Provider / Status / Currencies / Types ááá¶á½ á¨á³áá ááááᢠá tabs ááá«á¨á«áᤠááá¡ á ááµ áá","National schemes â a country's card system, instant payment scheme or QR standard â live here as ordinary providers with their own parameter set. The catalogue shows that a scheme is connected and which currencies it serves; the participant credentials themselves are set in terminal parameters, not here.","Cardholder authentication under the 3-D Secure scheme is a property of the channel rather than a separate provider: it shows in the configuration as a parameter and is switched on at the terminal."],"example":"á°á«á°á \\"Payment acceptance\\" -> \\"Provider Configurations\\" á áá¨áá³áᢠ\\"Grid\\" tab á áá£áª áá ááᦠááá³á 8 á¨provider cards á«á«áᢠ\\"sber\\" card á á¨ááá´ \\"Enabled\\" badgeᣠáááᬠRUBᣠáááá¶á½ bank_cardᣠsbp á ááµá¢ card á á á
á«á°ááá â á á°áá«á áµáá á áá°áááᣠá¥á á¨á³á½ áá áá
á JSON (ááá³á endpointsᣠterminal ááá«áá½á£ áááªá«áá½) á«áá á¨áááá®á½ ááá áá¨áá³áᢠá°áá³á³á©á card á¥áá°áá á á
ááµá¨á áááá áá-á«á°áááá á¥á áááá áá°á¥ááᢠá á¨á
á áááá ááµá¥ provider á áá¥ááµ áááááµá£ áá° \\"Table\\" tab áááá«á á¥á \\"Status\\" áááµ ááááᣠprovider \\"stripe\\" áá \\"Disabled\\" áááá á«áµá°ááá â áááµá ááá«áá½ á áá á á¥á± á á©á á ááá±áᢠá áá¹ header ááµá¥ á«ááá refresh á áá«á á áá ááᣠáá
á³á ááᥠá¨server á¥áá°áá áá áááá¢","tips":["áá
ááá¨áµ áá½ á¥áá áááµá°á«á¨á á áá°ááᦠprovider ááááµ/áá¥ááµá£ áááá¬áá½á ááá config á á¨áá
ááá¨á á áá½áá â ááá¦á½ á backend
1/á ááá½ áááá½ áá°á¨ááᢠá¥áá
\\"Save\\" ááá \\"Create\\" á áá«á®á½ á áááá","áá \\"Disabled\\" badge á¨á¨á¸á ááá«áá½á á²áá¨áá© ááááªá« á¨áááµá¹áµ ááᦠá¨á°á á provider á¨routing áááµáá","á \\"Currencies\\" ááá \\"Types\\" ááá¶á½ ááµá¥ á°á¨á \\"-\\" áááá© á API ááá½ ááµá¥ á£á¶ áááá á«áááá³áᣠáµá
á°áµ á áá°ááᢠáá
áµáááá ááá³ áá","ááᥠá á áááá½ á á©á ácached (5 á°áá áá°á)ᣠáµááá
á¨backend ááá¦á½ á áá á header ááµá¥ á«ááá refresh á áá«á áá«áᣠá áá ááá« á«áá ááµá áá«á© áá½áá","á \\"Configuration\\" ááá ááµá¥ á«áá JSON áµá± á´ááá«á áááªá«áá½á (ááá«áá½á£ endpoints) ááá áá½áá â áá« áá¹á áá¶áµá°á áááá½ á²á«á³á© áá ááá","If payments over a scheme fail while the provider is enabled, look in the terminal parameters: the catalogue shows the channel exists, not that it is fully configured."]},"routingEditor":{"title":"Routing Editor","summary":"á¨terminal cascade ááµáá á áá³á¢á¦ áá¹ á¨á°áá¨á á áá áá¥ááµ á á¨áµáá á¨ááá« provider terminals á¥á á áá á
á°á á°á¨á°á á¥áá°áááµ á«á³á«áᢠcascade á priority áááá£áᣠá¥á á á ááµ priority ááµá¥ áµá«áá á weight áá°á«á«áᢠá¥áá
á¨á¥á«áá³áá±á terminal priorityᣠweightᣠactivityᣠá¥á áá£áªá« ááá½ (AF rules) á«áá
á«áá¢","whenToUse":"á¨á°áᨠá áá ááá«áá½ ááá á°ááá¾á½ á terminals á¥áá´áµ á¥áá°áá°á«á© áááá ááá ááá°á½ á²ááá áááá áááá±á¦ áá terminal á¥á fallbacks áááááµá£ áµá«ááá á á áá«á³ terminals áá¨áááᣠá½áá á«áá áµá terminal ááá«á áá¥ááµá£ ááá ááá áá á áááᣠá ááá« áµáááµá£ á á£ááᣠá á«ááµ ááááµá£ á¥á á áá á ááá°á¥á¢ á¥áá° á¨áááááªá« á«áá³á á áá ááᦠáá¹ á«á walletᣠá£á¶ weightᣠá¥á á¨á°á á terminals áá²á«áá á«á°áááᢠááµáá á°á«á°áá½á£ risk managersᣠá¥á onboarding á£ááá«áá½ áá£áªá« ááá¢","concepts":["Route â á¨á á«áµ áááªá«áá½ á¥áá¨áµá¦ partner + currency + operation type + environmentᢠá°áá³á³á route á«áá¸á ááá terminals á ááµ cascade ááá°áá³áᢠá áá¹ á ááµ áá á«á áá£áªá«áá½ áá
áá route á«ááááᤠá«á á¨á°áá¨á á áá cascade á áá³ááá¢","Priority â terminals á¨ááá¨á©á áµ á
á°á á°á¨á°áᢠáá
á°á á¥á´áµ ááµá ááá¨á«á (0 áá áá)ᢠá°áá³á³á priority á«áá¸á terminals á á ááµ á¡áµá áá£áá«áᤠá áá¹ áá á¡áµá P0 \\"First choice\\" á°á¥á á¨áá¨á¨á»á \\"Fallback\\" áá°á¨ááá¢","Weight â á á ááµ priority á¡áµá ááµá¥ á¨áµá«áá áµáá»á¢ áµáááµ á¨weight áá á á°áá£á£á á¨áááá° ááᦠá weights 3 á¥á 1ᣠá¨ááááªá«á terminal 75% áá°á á«áááᣠááá°áá 25% áá°áᢠcard weight á áá¶ááá á«á³á«áᢠWeight 0 á ááµá áááá« ááá áá (terminal áµá«áá á á«ááá)á¢","Cascade á¥á Failed â á á ááµ á¡áµá ááµá¥ á«á ááá terminals ááááá á«áá°áá á ááá á¨áááá á¨ááᣠprocessing áá° áá£á© á¨áá°á priority áá¥á á«áá á¡áµá ááá³áᢠááá á¡áµáá½ á«ááᣠáá¥áá± ááµá
áá°á¨áá (á°áá³á label á cascade áá¨á¨á» áá áááá£á)á¢","Active á¥á shared terminals â Active toggle terminal á á«ááá/á«á ááᤠá¨á°á á á²á á°á°ááá á DISABLED label áá³á«áᢠShared terminals á ááááá á áá routes ááµá¥ áá³á°áá á¥á á icon á¥á shared badge á á°áá«áá¢","AF áá£áªá« ááá½ (inspector_params) â á terminal á°á¨á á JSON á
áá¸áµ á limits:v2:evaluate field áµá á«á á¨ááá á« ááá³áá½á¢ ááá³áá½á¦ reject (ááá³á á¥áááµ á¨áá ááµá
ááµá¨á)ᣠallow (á¥áááµ á¨áá á¥á» ááá á)ᣠor (á¢á«ááµ á ááµ ááá³ á¥áááµ á¨áá ááµá
ááµá¨á)ᣠand (ááá á¥áááµ á¨áá ááµá
ááµá¨á)ᢠááá½ á card áá á shield icon áá³á«áá¢"],"example":"á°áá£áᦠáá áá ID 42ᣠá prod áá á RUB á¨RF ááá« ááá á á ááááµ á provider A terminal á á©á áááµ á áá áµá£ á²á¨á½áá á terminal B á á©áᤠá¥á á¨áá á«áá¶á½ ááá á á¨áá£á¸ááᢠá°á¨ááá½á¦ 1) á áá£áªá«áá½ Partner = \\"... (IDᦠ42)\\"ᣠCurrency = RUBᣠType = PaymentᣠEnvironment = prodᣠRoute tag = Default (á«á tags) ááá¨á¡á¢ 2) á terminal A card áá á¨áá ááá áááá±á£ Settings tabᦠPriority = 0ᣠWeight = 1ᣠActive = onᢠ3) á terminal BᦠPriority = 10 (á¨á³á½ á á°áᨠá¡áµá ááµá¥ áááµáá â fallback áááá)ᢠ4) á ááá±á terminalsᣠFilter Rules tabᦠ\\"Russia only\\" template á á á
á«áµáá â reject áá á¨ááá³ country_code_3 != RUS á¥á á¨ááµá
áááá« áá ááá£áᢠ5) á¨áá á¥áá±á«áá badge á¨ááá¦á½ á¥ááµ áá áá³á«áᤠcascade á áááµá¹ (P0 â \\"First choice\\"ᣠá¨ááµá± áµá \\"Failed â\\" áá° á¡áµá B ááá«á) á¥á \\"Save all\\" á á á
á«áµááᢠá á ááµ á¡áµá (á°áá³á³á Priority) weights 3 á¥á 1 á«áááᣠáµá«áá á¨\\"áá/fallback\\" á¥á
áµ ááá
75/25 áá°á áá¨áááá¢","tips":["ááá¦á½ áá²á«áá á áá°áá á©áᢠá¨priorityᣠweightᣠactivityᣠá¥á ááá½ ááµá°á«á¨á«áá½ á¥áá° \\"pending\\" áá¨áá»áᤠá á¥áá±á«áá badge ááµá¥ á«áá counter á¥áá³á¸áá á«á³á«áᢠ\\"Save all\\" á¥áµá¨áá«á áµá¨áµ ááá á áá»ááᤠ\\"Reset\\" áááá á«áá°ááá¡ ááµá°á«á¨á«áá½á áá°áááá¢","á¨priority áá¥á®á½ áµááá á«áµá³áá±á¦ áá
á°á áááµ ááµá áááµ ááᢠá á áá«á³ terminals áá á°áá³á³á Priority á¥áá±á áµá«áá á weight á¨á°á¨áá á ááµ á¡áµá á«á°ááá¸ááᤠá¥ááá°á fallback áááááµá£ fallback terminal á¨áá°á Priority ááá¨á ááá£áá¢","route tag á áá£áª \\"Default (á«á tags)\\" áá á¥á á«á route tags terminals á¥á» á«á³á«áᢠá¨áá á á
terminal á cascade ááµá¥ á¨áá â áááá£áµ route tag á ááᦠáá£áªá«áá áá° ááááá tag áááá© (tag áááá© á¨á áá partner/currency/type/environment terminals á á«áµ-á°á áááá£á)á¢","á cards áá ááµá áááá«áá½á áááá¨á±á¦ icon á¥á labels NO WALLET (á¨á°á«á«á provider wallet á¨áá) á¥á weight 0 áááµ terminal á á°áá£á ááááá½á á á«á°á«á áááµ ááᤠá¨á½áá counter á á¡áµá header ááµá¥ áá³á«áá¢","Filter Rules tab JSON editor ááᢠá syntax áµá
á°áµ field á áá áá°ááá á¥á \\"Invalid JSON\\" áá³á«áᤠá¥áá°áá
á«á áá á áµááá á áááá¥áᢠá¨ááá templates (áááᣠá¨ááá« áµáááµá£ á£ááᣠá¨á«ááµ ááááµá£ á¨áá á áá°á¦á½á£ á¨á°á£áá© á¥á aggregate ááá½) áá
1áá á¥á á¥á´á¶á¹á ááµá°á«á¨á ááá ááᣠ\\"Clear rules\\" á°áá á¨terminal áá£áªá«áá½á áá á«áµááá³áᢠá ááá½ ááµá¥ á«á áá áá½ á á¥áá
á á áá¶á½ (kopecks) áááááᦠ10,000,000 = 100,000 rubá¢","Shared terminals á ááá á áá®á½ cascades ááµá¥ áá³á«áᢠpriorityᣠweightᣠááá ááá»á¸áá á ááá¨á á á ááµ áá á áá«á³ á áá®á½á ááá«á â á¨ááµááᥠá ááµ áá
áá á«áµá³áá±á¢"]},"routingConnectors":{"title":"Routing connectors","summary":"áá
á¨áµááá± áá á¨á°ááá á¥á áááá« routing á¨ááá áááá á¨ááá« providers (connectors) á¨áá£áá» á«á³áá ááᢠáá¹ á¨ááá áá áá á¨provider áµáá½ áááá á«á³á«áᤠááá¨áµ á¥áá ááááá á áá°áá â á¥áá
connectors ááá áᣠááµá°á«á¨áᣠááá áá°á¨á á áá½ááá¢","whenToUse":"á¨á°áᨠá¨ááá« provider á¥áá°áá°áá á áá¥ááµ ááá°á½ á²ááá áá
áá áá½ áááá± (ááá³á á á²áµ terminal á¨áááááµ á ááµ ááá á¨ááá´ á¥á«á á²áá¨áá©)ᢠconnector á¥áá³á ááá¨ááᥠá¥á áµáááá á¨áµáá á á»á»á ááá¨áµ ááµááᣠáá
á°áµá£ á¥á á½á«á á°á«á°áá½ á°áµáá ááᢠterminals á¥á routing rules á«á³á¸áá áááá á ááá½ áá¾á½ áá°á¨áá â áá
áá£áá» á¥á» ááá¢","concepts":["Connector (provider) â áá° áá«á á¨ááá« providerᣠá£ááᣠááá e-wallet á¶ááµáá adapterᤠáááá© á´ááá«á ááá«áá (name á¥áá° string) á«á³á«áᣠááá³á adyenᣠstripeᣠsberbank","Total Providers â á áµááá± ááµá¥ á«á á á ááá á¨connectors á¥ááµ á¨áá«á³á counter card (á¨á«á³áá á¨á°ááá± ááá áµáá½)","Filtered â á¨ááá string á¨á°á°áá ᨠá áá áµááµ providers á¥áá°ááá© á¨áá«á³á counter cardᤠá«á ááá á¨Total áá áááá³á","á¨ááá field (Search providers) â á provider áµá áá substring áá£áªá«á£ case-insensitiveᤠá²á°áá¡ áááá©á á á¥ááá°á áá á«á á£á","á áá°á áá§á°á â connectors á áµá á¨ááááªá« áá°á (AᣠBᣠC...) á cards áá§á°ááᤠá¥á«áá³áá± á¡áµá áá°ááá á ááµá¡ á«á providers á¥ááµ á¨áá«á³á á°áá«á badge á°áá¥ááá³á","Provider badge â á¥á«áá³áá± áµá á¥áá° á¨á°áᨠlabel áá³á«áᤠáá
áá³á« á¥á» áá (áá£áª cursorᣠlabels á¨ááá«áᣠá á
á²á°á¨á ááá áµáááµ á¨áá)"],"example":"ááá´ ááá«áá½ á provider Adyen á á©á ááá á á¥áá°áá½á áá áááᢠá°á«á°áá Acceptance -> Routing connectors á áá¨áá³á á¥á adyen á á ááá field ááµá¥ áá°áá£áᢠáááá© áá²á«áá áá á£áᦠFiltered card 1 á«á³á«áᣠá¥á adyen badge á áá°á A á¡áµá ááµá¥ áá³á«áᢠáµááá
connector á áµááá± ááµá¥ á áᣠá¥á á á°áá³á áá½ terminal áááá ááá á áá½ááᢠáá ááá á«áµáá¡ á áá Filtered 0 á«á³á¨ á¥á ááá badge á«ááᨠâ provider á á áá áááá ááµá¥ á¨ááá¢","tips":["áá¹ read-only ááᦠcreateᣠeditᣠááá delete á áá«á®á½ á¨ááᣠenabled/disabled statuses á¨ááᣠá¥á á ááá ááá á ááá« áá´ áá£áªá«áá½ á¨áá â ááááá ááá á¥á»á¢ á¥áá
á
áá¥á®á½ á áááá","provider á áááá© ááµá¥ ááááµ adapter á ááµá¨á© á¥áá°áá°áá á«áááá³áᣠááá áá ááá®áááµá keys á«áá á¨áá°á« terminal á áµááµá áááá©á á á«á¨ááá¥á â áá
á terminals áá½ ááá°á»á","ááá á áµá ááµá¥ á ááááá á¦á³ substring á á«ááá³áᣠá ááááªá«á á¥á» á áá°ááᤠáá
á á¥áá²á
ááá³ áááá© á ááááªá« áá°á á ááµá á°á§áµááᣠáµááá
áá á á¨ááá áá¤áµ ááááªá« á²á³á á£áá°á á á á¨áá°á á¡áµá ááµá¥ áááµá
áá½áá","á¨provider áµáá½ á´ááá«á áá¸á (Latinᣠlowercase)ᢠá²ááá á marketing brand áµá á³ááá á áµáááµ ááá« ááá©á¤ á áá¤áµ case á áá°áá áá"]},"riskConfig":{"title":"Risk configuration (crypto)ᦠrisk engine áááá","summary":"áá
á¨ááªáᶠáááá risk scoring engine ááááá áá á form áá½ ááᢠá¥áá
á¨áá¥ááµá á¨áá¨á¨á» risk score á¨áµáá¹ áááá½ á¥áá°áá«áá
á©á£ scoring á²á¨á½á áµááá± á¥áá´áµ á¥áá°áá°á«á£ á¥á á¨áµáá provider á¨counterparty á áµá«á»á risk á¥áá°ááááá á«ááááá¢","whenToUse"
1:"The page is for AML/compliance and crypto risk staff. Open it to rebalance the risk score components (for example, to increase the weight of transaction screening), switch the failure behaviour, or change the address KYT scoring provider. Only the platform administrator saves the config; a client gets the page read-only (Read only badge): fields are disabled, there is no save button, and in its place a line names who changes the weights.","concepts":["Score weights â á basis points (bps) á¨á°ááá á¨áá¨á¨á» risk score á¶áµáµ áááá½á¦ kytᣠafᣠvelocityᢠá¨á¶áµá±á áµáá á áµááá 10000 bps (100%) ááá á áá áµá¢","kyt (Know Your Transaction) â á¨áá¥áá±á/counterparty á áµá«á»á á¨ááá°á½ ááá¨á¨á»á score á áµá°áá½á¦á¢ af (anti-fraud) â á¨anti-fraud áááá¶á½ á áµá°áá½á¦á¢ velocity â á¨ááááá½ áµáááá½á á¥áá«á¬ á áµá°áá½á¦ (áµááµá áµááµ áá)á¢","Basis points (bps) â á¨weights áááªá« á ááµá¦ 100 bps = 1%ᣠ10000 bps = 100%ᢠá¨á¥á«áá³áá± field áµá áá° áá¶á ááá¨á© áá³á«á (ááá³á 2500 bps -> 25.00%)ᣠá¥á á¨á³á½ áá ááá« badgeᦠá 10000 á á¨ááá´á£ á ááááá áá á¥á´áµ ááá¢","Fail mode â scoring á«áá°á ááá á¨áµááá± á£á
áªá¢ fail_closed scoring á²á¨á½á ááááá á«áá³áᤠfail_open á«á³ááááᢠáá£áªá fail_closed ááá¢","Address provider (á¨á áµá«á» KYT scoring provider) â \\"á¨counterparty á áµá«á» áá á«á
á á á°áá áá\\" áááá á¥á«á á¨áááá°áᦠá¨áááá¦á½á£ á¨darknetᣠá¨mixers áá á«áá áááááµá¢ áá
á¨á«áµá á¨á°ááá á áµá«á»áá½ ááá á áá°áá â á« á¨á°áᨠá
áá¥á ááᢠáááá© á backend á°ááá·á (á¨áááá° module ááµáá£áµá á¨áá¨ááá whitelist)ᦠInternalAmlᣠChainalysisKytᣠCipherTraceᣠEllipticᣠTrmᢠáá» áá¤áµ á ááá ááá¢","InternalAml áá£áªá provider ááᢠáá° ááµá£áá AML á«áµá°ááááᣠá¥á á¥á± á¥áµá¨á á áµá¨áµ scoring áá® score á¥á á£á¶ á¨category áááá áá SUCCESS áááá³áᢠáá
á á¨\\"á áµá«á»á áá¹á
áá\\" á¨ááá engine ááá á áá½ááᦠááááá á áµá«á» áá
á°ááá risk tier á«áááᣠá¥á áá°á» á ááá°á¨á á áµááá á¥áá°á°á³á« áá°á» áá³á«áᢠá risk áá á á°áá á¨á° routing áá á¨áá°áááá á ááµ ááµá£ááá AML á«á¥á© ááá áá«á provider ááá¨á¡á¢","Permissions and read-only mode â only the platform administrator writes the config; the client-side manage_aml_alerts permission has nothing to do with that write (it opens the frozen operations queue). A client sees the form with a Read only badge, all fields disabled and no Save button."],"example":"á°áá£áᦠá risk score ááµá¥ á¨áá¥ááµ áá°á»áá½á áá áá áá¨áᢠáá¹á áá¨áá³á á¥á á¨á ááá weights á«á«áᣠááá³á kyt=3000ᣠaf=3000ᣠvelocity=4000 (áá ááá« badge á á¨ááá´á£ 10000 basis points = 100%)ᢠáá° kyt=5000 (field áá²á«áá 50.00% á«á³á«á)ᣠaf=3000ᣠvelocity=2000 áááá¯á¸ááᢠáµáá© á 10000 á¥áµá¨áᨠáµá¨áµ badge á á¨ááá´ ááá«áᢠááá³á kyt=5000ᣠaf=3000ᣠvelocity=3000 á¥áµá°á áá® áµáá© 11000 áááá â badge áá° áá áááá£áᣠ\\"must equal 10000\\" label áá³á«áᣠá¥á Save á áá«á disabled ááááᢠáµáá©á áá° 10000 á«áá£áᣠfail_mode = fail_closed ááááᣠprovider áááá£á (á áá£áª InternalAml) á¥á Save á á á
á«á°áááᢠá á°á³á« áá \\"Risk config saved\\" áá³ááá« áá³á«áá¢","tips":["á¨weights áµáá á áµááá 10000 bps á¥áµá¨ááá áµá¨áµ ááµááᥠá áá½áá â Save á áá«á disabled ááᣠá¥á submit áá¨á« áá \\"Weights must sum to 10000 bps (100%)\\" áµá
á°áµ áá³á«áᢠáááá áá ááá« badge á áááµá¹á¦ á á¨ááá´ ááá á áá áµá¢","Weights á¥áá° áá áá¥á á bps ááá£áᣠá¥áá° áá¶á á áá°ááᢠ25% áááááµ 2500 á«áµáá¡á£ 25 á áá°ááᢠá¨á¥á«áá³áá± field áµá á«ááá á¨áá¶á ááá á¥áá° áááªá« áá ááá¢","á¨fail_mode ááá« á á°á
áááµá á availability áá«á¨á áááµ (trade-off) ááᦠfail_closed á°á
ááá± á¨á°á á á áá (scoring á²á¨á½á á«áá³á) ááá áá ááá ááááá½á áá«áá áá½ááᤠfail_open áá°á±á á á«ááá¥á ááá áá ááááá½á á«á áá risk áááá á«á³áááᢠá á¥ááá áááá©áµá¢","provider á¨áááá© á¥á» ááá¨á£áᦠbackend á áµááá á ááµáµ modules ááá ááᣠáááá áá ááµá
á«á°áááᢠá field ááµá¥ á¨ááá³áá
á¥á´áµ á«á© â á« á¨áµáá
áµá á¨á áá á
áá¥á ááᣠá¨á°ááá á config á¨á°á«áá¢","form á áá«áá áµ áá á¨á ááá á¥á´á¶á½ á¨server áá³á£áᢠá áá¹ header ááµá¥ á«áá refresh á áá«á config á á¥áá°áá á«áá£áᤠá«áá°ááá¡ ááµá°á«á¨á«áá½ á áá°á± áá° server ááá³ áááá³áá¢"]},"cryptoWallets":{"title":"á¨ááªáᶠá¦áá³áá½á treasury","summary":"á¨ááµá¨á©á á¨á«á± á¥ááá¼áá á¦áá³áá½ áááá£á á áááᦠhot walletsᣠá¨á°ááá á áµá«á» poolᣠsweep ááááá½á£ á¥á á risk tier treasury walletsᢠá¥áá
á°á«á°á á áµá«á»áá½áᣠá᪠áá³á¦á½áᣠstatusesᣠá¥á á Ethereum á¥á TRON á áá³á¨ áá¨á¦á½ á prod á¥á test á á«á£á¢áá½ ááµá¥ á¨áááᥠá¥áá
áµáá´ á³áªá á«á«áá¢","whenToUse"
1:"á¨ááµá¨á©á ááªáᶠáá á¨á° áááµ ááá³ ááá°á½ á²ááá áááá áá ááᦠá hot wallets áá áµááµ áááᥠá áᣠá¨áµáá¹ á¨á°ááá á áµá«á»áá½ áá°áá áá½ á°á°á¥á°ááᣠá¨á°ááá á áµá«á»áá½ áá° treasury sweep ááááá½ á¥áá´áµ á¥á¨áá± ááᣠá¥á ááá¥áá¶á½ á á gas á á ááᢠááá átreasuryᣠááááááµ ááµáµáᣠá¥á áá´ááá«á áµáá á°á«á°áá½ á«áá ááᢠtreasury wallet ááá á áááµá¨á á áµá°á³á³áª ááá manage_treasury áá¥áµ ááá¸á á°á«á°áá½ á¥á» ááááᢠprivate key ááá³áµ áá áááá á ááááᤠááµá¨á© ááááᣠá áµá°á³á³áªááá á¨áá®á£ «decrypt disabled» á¥á áááá³áá¢","concepts":["Crypto wallets â a card list of the platform's hot wallets. For each: network (ethereum/tron), environment (prod/test), address with a link to the blockchain explorer (etherscan/tronscan, and for test â sepolia/shasta), three balances (USDT, ZOLT for Ethereum only, Gas â ETH or TRX), and a link to the private key (private_key_ref). There is no \\"Create\\" button on this page: crypto wallets are provisioned by the platform administrator, and the page shows this note in place of the button.","Deposit Pool â áááᣠááá« ááá á« á¨á°á°á¡ HD á áµá«á»áá½ registryᢠá¨á áµá«á» statusesᦠavailable (áá»)ᣠallocated (ááááá á¨á°áá°á )ᣠused (á¨á°á áá)ᣠretired (á¨á°áá±)ᣠfrozen (á¨áááá)ᢠá áá á¨á¡ áááááᣠá¨áá¥ááµ ááá« (tx_id)ᣠá¥á á¨ááá°á¢á« áá (allocated_at) á«á³á«áá¢","Sweep ááááá½ â á á°ááá á áµá«á» á¨á°áá á áááá¦á½á áá° treasury wallet ááµá°áááᢠáá¥á«áá³áá± ááááᦠááá á áµá«á»á£ ááá á áµá«á»á£ á¨áááᬠáá áá áᣠtierᣠrisk score (risk_score á¨low/medium/high á°á¨á áá)ᣠstatusᣠá¨áá¥ááµ hashᣠá¥á á¨áµá¥á°á£ ááᢠStatusesᦠpendingᣠprocessingᣠsweptᣠcompletedᣠfailedᣠfrozená¢","Tier Treasury â á risk tier á¨á°á¨áá treasury walletsᦠlowᣠmediumᣠhighᢠáááᥠá sweep áááá risk score áá á áááµá¨áµ áá° tiers ááá«áᢠá áá á¨á¡á¦ tierᣠá áµá«á»á£ á áá³á¨ áá¨á¥á£ á á«á£á¢á£ á¨áááᬠáá á᪠áá³á¥á£ statusᢠ\\"Provision\\" á áá«á á á²áµ treasury wallet ááá¥á«áá¢","á¨á á«á£á¢á á áá³á¨ áá¨á¥ áá£áªá«áá½ â á ááá áá¾á½ áá á¨á á«á£á¢ toggle (prod / test / all) á¥á á¨á áá³á¨ áá¨á¥ á½áá field (ááá³á ethereum ááá tron) ááááᤠdeposit pool á¥á sweep ááááá½ status áá£áªá« á«áááᢠá᪠áá³á¦á½á áá áá½ áá°áᨠáááᬠᨠdecimal places á¥ááµá á¨áááµ á ááµáá£áµ á¨á¥áá
á á áá¶á½ áá° ááá ᥠá¨áá½á á
áá½ á á«áµ-á°á ááá¨á«áá¢","Private key and the ban on revealing it â on the wallet card the private key stays hidden: only the reference identifier (private_key_ref) is visible, and only it can be copied. The key-icon button is still there, but reveal
1ing is blocked on the platform side: the /encryption/_decrypt service answers everyone without exception, the administrator included, with a \\"decrypt disabled\\" refusal, and an error message appears on the screen instead of the key. The ban is not exposed as a setting: it can be lifted only by a reviewed code change."],"example":"á°áá á USDT á TRON á áá³á¨ áá¨á¥ áá á áµááá ᢠááµá¨á© á¨deposit pool á áµá«á» á°á£á¸á â á \\"Deposit Pool\\" áá½ áá áá
á áµá«á» á allocated status á¨ááááá á¨áá¥ááµ ááá« áá áá³á«áᢠáááá¡ á¨á°á¨áá á áá sweep áááá áááá«áᦠá \\"Sweep operations\\" áá½ áá áá¤áµ áá³á«á â ááá (á¨á°áá áá á¨á°ááá á áµá«á»)ᣠááá (treasury wallet)ᣠáá áᣠááá³á 1,250 USDTᣠrisk score (á¥áá á 0.18 · low)ᣠá¥á á¨pending áá° processing á¨áá«á áá° swept/completed á¨áá¥ááµ hash áá á¨ááá¨á statusᢠáááá¡ á \\"Tier Treasury\\" áá½ áá á áá³á low-tier treasury wallet ááµá¥ áááµááᦠá¨low wallet á᪠áá³á¥ á áá
áá á á áµááᢠrisk score high á¢áá áá®á£ áááá¡ áá°áᨠáá¥á¥á áá° high-tier wallet ááá« áá áá¢","tips":["áááá á¨á á«á£á¢ toggle á áááµá¹á¦ á áá£áª ááá±á prod á¥á test áá³á«áᢠTest wallets áá° sepolia/shasta áá ááá á¥á á¥ááá°á áááᥠá áááá â á᪠áá³á¦á½á á²á«áµá³áá á¨production (prod) áá á á³á°á£ááá¢","á hot wallets áá Gas á᪠áá³á¥ (ETH ááá TRX) á áááá¨á±á¦ á á á gas á¥á¦áµá£ sweep ááááá½á ááµá°áááá½ á ááá±á á¥á á pending status á \\"á°á°á
áá\\" ááá áá° failed ááá³áá¢","Do not expect the key-icon button to show you the private key: the platform rejects the decryption request with a \\"decrypt disabled\\" answer, and a refusal message appears on the screen. The refusal reaches everyone, the platform administrator included â it is not a matter of missing rights. Only the reference identifier (private_key_ref) can be copied from the card; the key itself cannot be obtained from the cabinet under any rights, and revealing it comes back through a reviewed code change, not through a settings toggle.","Provisioning treasury wallets (Provision) on the \\"Tier Treasury\\" page is available to an administrator and to a staff member with the manage_treasury right; the environment field accepts strictly prod or test, otherwise the request is not sent. That right does not extend to the custody wallets on the \\"Crypto Intake Mode\\" page: there Provision works only for the platform administrator, while a client or a partner gets a 403 refusal with the admin_only code regardless of the rights of their role â ask support to have them provisioned, the full set is created for the organization at once. Crypto wallets themselves are not created from the cabinet: the platform administrator provisions them via the API, so the crypto wallets page shows a note about who provisions them instead of a \\"Create\\" button.","ZOLT á᪠áá³á¥ áEthereum á áá³á¨ áá¨á¥ á¥á» áá³á«áᤠáTRON áá
áááµ á°á¨á á«á³á«á â áá
á¨á°ááá° ááᣠá¨ááᥠáµá
á°áµ á áá°ááá¢"]},"reconciliation":{"description":"á¨Admin Area áá£áá» á½áá","title":"ááµá³á¨á
á registries","summary":"\\"Reconciliation\\" ááá á 4pay.online áµáááµ ááµá¥ á«á áá¥áá¶á½á á¨ááá« providers á¥á á£áá®á½ statements (registries) áá á«ááá³áᣠá statuses á¥á áá áá½ ááµá¥ áá©áá¶á½á á«áááᣠá¥á á¥áá²áá·á¸á á«áµá½ááᢠ\\"á¨á°á£á á\\" á¥á ááµá
á¨á°á°á¨á áá¥áá¶á½á á¨ááááá áµ á¥á statuses á á á¥á
á¨áá«áµá°á«ááá áµá ááá¢","whenToUse"
1:"ááá áááá³á ááµá³á¨á
áoperationsᣠááááááµ ááµáµáᣠá¥á ááµáá á°á«á°áá½ ááᦠprovider á¨á°á°á© ááá«áá½á áááá á«áá registry ááá ááá«áᣠá¥á á¨ááµá¥ áµááá± á°áá³á³á áá¥áá¶á½ á á°áá³á³á status á¥á á á°áá³á³á áá á á¥áá³ááµ áááµá»áᢠá²á ááᦠá¨á£áá/provider registry á°á¨á° á¥á á¨4pay.online ááᥠáá ááááµ á áá áµá¤ á°áá á ááá« á provider á°á¨ááá á á¥á± á á©á á áááá¸á£á¨áá á«ááá«á (áá¥áá± \\"á°á°á
áá\\")ᤠáá¨á
á áá á«áá°á ááá á created/Charging statuses ááµá¥ á«á áá¥áá¶á½á ááááµá ááµá°áááµ á«áµááááᤠá¨áá¥ááµá á¨áá¨á¨á» status á á¥á
áááááµ ááá á¨ááá´ áá³ááá« á¥áá°áá ááá á«áµááááᢠááá á \\"Risk\\" á¡áµá ááµá¥ ááá¢","concepts":["á¨Reconciliation dashboard (/reconciliation) â á á ááá á¥áá³ áá½á¢ á¨prod/test á á«á£á¢ toggle á¥á áá (Last hour / 24 hours / 7 days / 30 days)ᢠcounters á«á³á«áᦠtotal recentᣠsuccessful (charged)ᣠsuccess rateᣠá¥á á¨\\"á¨á°á£á á\\" á¥ááµá¢ á¨á°áá© á¥áá®á½ failed áá¥áá¶á½á á¥á á statuses charging (áá°á¥ 30 á°áá)ᣠcreatedᣠá¥á new (áá°á¥ 60 á°áá) á¨á°á£á ááµá á«á°áááᢠá áµáááᦠáµá³á²áµá²ááµ ááá³á áá¸á â API á á ááµ áá áá
á¢á á 100 áááá¦á½á áááá³áᣠáµááá
á áµáá
áá á áá¶ááá¹ á ááá«á½ áá¸áá¢","á¨áá¥ááµ ááá (/reconciliation/search) â á ááááµ áááᦠá idᣠá outertxid (á provider á á©á á«á ááá«)ᣠá statusᣠááá \\"stuck\\" (á¨created/Charging/payment_suspended/payout_suspended áµá¥áµá¥)ᢠá status á¥á stuck ááá áá£áªá«áá½ ááááᦠstatuses (tags)ᣠproviders (tags)ᣠá¨áá ááá (datetime-local fields)ᢠáá°áá á¥á«áá³áá± áá¥ááµ áµááá¶á½ ááááᦠ\\"Details\\"ᣠ\\"Set status\\" (charged/rejected/failed/refunded)ᣠ\\"Renotify\\" (áá° ááá´ webhook á¥áá°áá ááá)ᣠ\\"Update from provider\\" (á¨provider á¨á ááá status áá á¨á
)ᢠbulk ááá« á á (áááá áá¨á¥ / áááá á á¥á)ᢠáá áá á 100 áááá¦á½ á¨á°áá°á ááá¢","Registry ááµá³á¨á
(/reconciliation/registry) â á¨ááá ááᢠproviderᣠparsing áá
á (ááá \\"Auto-detect\\")ᣠá á«á£á¢ áááá£áᣠá¥á CSV/TXT ááá áá°á
ááᢠáµááá± áááá á parse ᣠá¨ááµá¡ ááá«áá½á áááµá³á (providerId = outtertxid)ᣠá°áá³á áá¥áá¶á½á á¨4pay.online á 50 batches áá áááᣠá¥á á«áá»á½á«áᢠáá¤á± á tabs á°á¨áááᦠSummaryᣠMatchedᣠStatus mismatch (statusMismatch)ᣠNot in 4pay.online (missingInSurelle)ᣠNot in registry (missingInRegistry)ᢠá¨ááá»á¸á á ááµ statuses á normalize ᦠcharged/success/successful/completed/approved/1 áá° \\"charged\\"ᣠá¥á rejected/failed/error/declined/0 áá° \\"rejected\\" á á«á ᢠStatus áá©áá¶á½ á ááµ á á ááµ (\\"Fix\\" á áá«á) ááá á á ááµ áá (\\"Fix all\\" â á¨registry status bulk áááááµ) ááµá°á«á¨á áá½ááᢠáá¤á± áá° CSV á export ᢠáá áá½ á á¥áá
á á áá¶á½ (kopecks) á°á¨áá½á°á á áá³á« á 100 á á«ááá á¢","Registry áá
á®á½ (/reconciliation/configs) â áá¥á«áá³áá± provider á
áá¸áµ á¨ááá parsing ááá½á¢ áá
á á«ááááᦠnameᣠproviderᣠá¨áááµ mapping (providerIdᣠamountᣠdateᣠstatus á¥á á á áá«á rrnᣠcardNumberᣠdescription)ᣠá¥á CSV áááªá«áá½ â delimiter (á®á / semicolon / tab)ᣠá¨á°ááá header á¨áµáá½ á¥ááµá£ á¨áá á
áá¸áµá£ á¥á encoding (utf-8 ááá windows-1251)ᢠPresets á°á«áµá°ááᦠMTS BankᣠBank 131ᣠMKBᣠFortaᣠCoreFayᢠáá
á á«áá°áá¨á backend ááá¶á¹á á á«áµ-á°á áááá¨áµ áááá«áá¢","Registry ááá®á½ (/reconciliation/source-configs) â á¨ááá¡ registries á á«áµ-á°á á¨á¨áµ á¥áá°ááá¡á¢ á¨ááá ááááµá¦ email (IMAP â hostᣠport áá£áª 993ᣠloginᣠpasswordᣠfolder INBOX)ᣠftp/sftp (hostᣠport 21ᣠloginᣠpasswordᣠpath)ᣠááá manual (á á¥á
ááá ááµáá)ᢠschedule (cron expression)ᣠá¨áá áá áááááµá£ á¥á parsing áá
á áá«á«á áá½ááᢠá¨áá¨á¨á» ááá£áµ ááá áá¤áµ á á¨á³á°áá (success/error)á¢","Registry á°áá£á®á½ (/reconciliation/recipient-configs) â á¨ááá¡ registry áªáá
1á¶á½á ááá á¥á á¥áá´áµ á¥áá°ááá©á¢ á¨á°áá£á ááááµá¦ partner / provider / internal / customᢠá¨ááµá¨á» áá´á¦ email (to/cc ááááᣠsubject á¥á body templates ᨠ{{date_from}} á«á ááµá«á¸ áá) ááá ftpᢠá¨á
áá¸áµ á
áá¥á®á½á¦ csv/xlsxᣠdelimiterᣠencodingᣠá¨ááá áµá templateᣠá¨áµáá á¨áµá áá«á°áµ ááá á ááá«á°áµá¢ á¨áá¥ááµ ááá« áá£áªá«áá½á¦ partnersᣠterminalsᣠá¨áááá áááá¶á½ (payment/payout)ᣠproviderᣠstatusesᣠá¨áá áááᣠáá
á°á/á¨áá°á áá áᢠSchedule (cron) á¥á á¨áá áá (áá£áª Europe/Moscow)ᢠ\\"reconciled only\\" flag (only_reconciled)ᢠá áá áááá á áá«á á á (export ááá¥á«á)ᢠá¨imports á¥á exports á³áªá á Imports (/reconciliation/imports) á¥á Exports (/reconciliation/exports) áá¾á½ áá á á«ááᦠá¨import statuses pending/processing/completed/failed á¨matched/unmatched/mismatch counters ááᤠá¨export statuses pending/processing/sent/failed áááá á¨ááá¨áµá á¨á¨á¸ááá á¥áá°áá á¨ááá á½áá³ ááá¢"],"example":"Provider Bank 131 áááá 17 á¨áááµ registry bank131_2026-07-17.csv 1,200 á¨áµáá½ á«áá áᨠ(delimiter \\";\\"ᣠencoding utf-8)ᢠ\\"Registry reconciliation\\" á áá¨áá³áᣠprovider bank131ᣠáá
á \\"Bank 131\\"ᣠá á«á£á¢ prod áááá£áᣠá¥á áááá áá°á
áá â áµááá± \\"Loadedᦠ1200 transactions\\" ááªááá³áᢠ\\"Run reconciliation\\" á á á
á«á°áááᦠáµááá± á¨transaction_id áááµ 1,200 ááá«áá½á áááµá³áᣠá¨4pay.online á 50 batches áá áááᣠá¥á á«áá»á½á«áᢠá \\"Summary\\" tab áá á«á«áᦠmatched 1,180ᣠstatus mismatch 12ᣠnot in 4pay.online 5ᣠnot in registry 3ᢠ\\"Status mismatch\\" tab á áá¨áá³áᦠá12 áá¥áá¶á½ registry \\"charged\\" á«á³á«áᣠá áµááá± ááµá¥ áá \\"Charging\\" áá¸á (á°á°á
áááᣠá¨provider webhook á áá°á¨á°á)ᢠ\\"Fix all (12)\\" á á á
á«á°ááá â áµááá± status á¸áá áá° charged bulk á«ááááᣠá¥á á°áá áá½ áµáááááá á¨ááá« áá¤áµ ááá ááᢠá ááµá±á \\"not in 4pay.online\\" áá¥áá¶á½ á á¥á
á outertxid áááµá»á â áááá£áµ á áá á á«á£á¢ á°á¨ááááá ááá á¨á°áᨠááá´ áá¸áᢠáá¤á±á á \\"Export\\" á áá«á áá° reconciliation_2026-07-17_18-30.csv áarchive á export á¢","tips":["ááµá³á¨á
á outertxid (á¨provider ááá«) áá°á«áᢠá áá
á ááµá¥ providerId áááµ á á°á³á³á° á¨á°ááá ááá ááá á£á¶ á¨á°parseᣠ\\"no valid identifiers\\" áµá
á°áµ á«ááá á¥á ááá áá° \\"Not in 4pay.online\\" áááµááᢠááááªá« á áá
á© ááµá¥ á«á ááá¶á½á delimiter á¨áµááááá ááá á
áá¸áµ áá áááá³á¸áá á«á¨ááá¡á¤ á²á á«á á© \\"Auto-detect\\" á áá ááá¢","encoding á áááá¨á±á¦ á¨á©á²á« á£áá®á½ á¥ááá áá áááá½á á windows-1251 ááá«áᣠutf-8 á áá°ááᢠá¨á°á³á³á° encoding á statuses á¥á áá áá½ ááµá¥ á¨á°á áḠááá á¥á á¨áá¸áµ áá©áá¶á½ á«áµá¨áµááᢠencoding á registry áá
á ááµá¥ áááááá¢","áá áá½ á á¥áá
á á áá¶á½ (kopecks) á¥áá° strings ááá»á¸á«á â 100 rubles \\"10000\\" ááᢠá¨áá á áá©ááµ (amountMismatch) á á áá«á á á«áµ-á°á á ááµá°á«á¨áá ááá áá á á¥á
áááá áá áááᦠá¨provider feeᣠá¨áá á°ááá½á£ ááá á¨á°áᨠáµááááááµ ááá áá½áá (áááªáᶠâ á¥áµá¨ 18 á ááá½)ᢠ\\"Fix all\\" á áá«á ástatus áá©áá¶á½ á¥á» áá°á«áá¢","á¨prod/test á á«á£á¢ toggle á¥á á dashboard á¥á ááá áá ááá½ áá á«ááá 100-áááᥠáá°á¥ á«áµá³áá± â á¨dashboard áá¥á®á½ á ááá«á½ áá¸áᢠ\\"Set status\\"ᣠ\\"Fix all\\"ᣠrenotifyᣠá¥á \\"Update from provider\\" áµááá¶á½ á¥ááá°á ááᥠáááá«á á¥á ááá´áá½á á«á³áááᣠáµááá
á á¥ááá áá°áá¥á¯á¸áᤠá¥á«áá³áá± á á¥á
á¨status ááᥠáµá ááá© ááµá³áá» áá á áááá£á (registry ááµá³á¨á
/ á á¥á
ááá¥)á¢"]},"compliance":{"title":"Complianceᦠáªááá¶á½á£ templatesᣠschedules","summary":"\\"Compliance\\" ááá (Compliance Reports) á¨áµáá
á±á á¨áá¥á¥á áªáááµ ááááá¨áµ áá£áªá« ááᦠáá°áá«á© á¨áá áááá½ built-in á¨áªáá
1áµ templatesᣠáá°áá¨á áá á á¥á
áªáááµ áááá¨áµá£ á¨á°ááá© áªááá¶á½ á³áªá á¨integrity áá¨ááá« ááᣠá¥á áá á«áµ-á°á ááµá¬áµ schedules á¥á á¨á°á ááá áááá½á á¨ááµá¨á» á»ááá½á¢ ááá á¨Risk á¡áµá ááá¢","whenToUse":"áá°áá£á£áª áªáááµ áááááµ á²ááá áááá áááá± (ááá³á NBRB á BelarusᣠCBRᣠááá MiCA/FATF/VARA/MAS á á«ááµ) ááá á¨áµáá¹ áªááá¶á½ á áµááµá á¥áá°á°ááá© áááá°á½á¢ á á¥á
áááá¨áµ áá ááµ áá \\"á¥áá
á á áá\\" á¥á«ááá½ á°áµáá ááᢠSchedules á°áá³á³á áªáááµ á áááµá® (ááááᣠá©á¥ ááá³áᣠááá°) á«á á á¥á
áµáááµ áá
á¨á¥ á²ááá áµ á«áµááááᢠá¨ááµá¨á» á»ááá½ á compliance officers á¥á á áµá°á³á³áªáá½ áááá«á á¨á°á ááá áááá½ á emailᣠSFTPᣠáá° S3ᣠááá á webhook á á«áµ-á°á á¥áá²áá¡á¢ á¨ááá» áá¹ (Hub) áá£á á á ááá á¥áá³ áá°á£áᦠáµááµ templates á¥áá°áááᣠá áµááµ á¨áá áááá½á£ á¨áá¨á¨á»áá¹ á ááµáµ áªááá¶á½ áµáá± á á°á³á« ááá³ á¥áá°á°á áááᣠá¥á áµáá± á áµá
á°áµá¢","concepts":["Template â á¨áá¥á¥á áªáááµ templateᦠá¨áá áááᣠá°áá£á£áªá£ ááµá¥á£ á¨áá¤áµ á
áá¸áµá£ á¥á áá£áª áµáááá½ á ááᢠTemplates built-in áá¸á á¥á á á¥á
á ááá á©áᤠá á«á³áá áá½ áá á á£á«á ᣠá¥á áááá¨áµ á \\"Generate report\\" á áá«á áááá«áᢠááµá¦á½á¦ settlementᣠamlᣠcapitalᣠtaxᣠcross_borderᣠreservesᣠparticipantsá¢","á¨áªáááµ á
áá¸áµ (Format) â ááá á¨á export á
áá½á¦ csvᣠjsonᣠxmlᣠxbrlᣠxlsxᣠpdfᣠá¥áá²áá áá© goaml_xml (ágoAML FATF)ᣠivms101_json (Travel Rule áááªáᶠááµá°áááá½)ᣠiso20022_xml (á¨ááá« á°á¨á)ᣠá¥á cbr_xml_1c (áCBR export)ᢠá
áá¸á± á template á«á± ááµá¥ áááááá¢","á¨á°ááᨠáªáááµá status â ááá template á¨á°áᨠááµá¬áµá¢ Statusesᦠqueuedᣠrunningᣠcompletedᣠfailedᢠááá ácompleted status áªáááµ á¥á» á áááµ áá½ááᢠá¥á«áá³áá± áªáá
1áµ á¨ááá±á SHA-256 hash á«á¨áá»á â áááá integrity áá¨ááá« á¨á£áµ á á»á«á¢","áá (Period) â á¨áªáááµ ááᥠá¨áá°á á°á¥á áµ á¨áá ááá°áµá¢ áá á¥á
áááá¨áµ á \\"Period start\\" á¥á \\"Period end\\" fields (ááá á°ááµ) áááááᢠCustom params â á°á¨á᪠á¨áµááµ áááªá«áá½á áááµá°ááá á JSON á
áá¸áµ á áá«á fieldᣠááá³á {\\"include_partner_breakdown\\": true}á¢","Schedule â áªáááµ á á«áµ-á°á áááµá¬áµ ááᦠtemplate ID á áá á
á³áᣠáµáááá½ (dailyᣠweeklyᣠmonthlyᣠquarterlyᣠannuallyᣠááá cron á¨\\"0 7 * * *\\" á«á á¨áááá° expression áá) á¥á á¨áá ááµá®áµ (period_window) á ááᦠlast_periodᣠlast_7dᣠlast_30dᣠlast_monthᣠcurrent_quarterᣠcurrent_yearᢠáµááá± áá£á©á á¨ááµá¬á áá (Next run) á«á± á«á°áá á¥á Enabled flag (on/off) á«á¨áá»áá¢","Delivery Channel â á¨á°á ááá áááá½á áá´áµ á¥áá°ááá©á¦ emailᣠsftpᣠs3ᣠwebhookᣠááá in_app (á áµááá± ááµá¥ á¥á»)ᢠá»áá á¨encryption ááááµ á ááᦠnoneᣠpgpᣠageᣠááá smimeᤠá¨none áá áááááá á²ááá¡ á¨á°áá£á© public key áááá½ á áá áµá¢ á¨á»áá á
áá¥á®á½ (config) á JSON áá°á£áᤠá áá
á© ááµá¥ áµá± fields á áá£á¥ áá á á¸ááá á¢","Reporting and ongoing monitoring are different things. Reports for a period are produced here; continuous transaction monitoring and sanctions screening run in the risk engine and the suspicious operations queue, and only their outcome lands here.","Licence monitoring rests on this same section: the evidence pack for a supervisory inspection is assembled from generated reports, while the list of current licences comes from the organisation card."],"example":"á°áá£áᦠáBelarus á¥áá«á á£áá ááá áááá settlement áªáááµ áááááµá¢ á°á¨á 1. \\"Compliance\\" áááá áááá± á¥á á ááá» áá½ \\"Belarus regulatory pack\\" á á á
á«áµáá (ááá áá° \\"Template catalog\\" áá°á á áá ááá áá£áªá« BY ááá¨á¡)ᢠá°á¨á 2. á¨áááááá NBRB template á«áá (á ááá \\"NBRB\\" á áµá ááá ID ááµáá£áµ áá½áá) á¥á \\"Generate report\\" á á á
á«áµááᢠá°á¨á 3. á áááá« áá½ áá áµááááá template ááá¨á¡á á«á¨ááá¡ â á¨áá áááᣠá
áá¸á±á£ á¥á áµáááá¹ á¨selector áµá áá³á«áᢠPeriod start = 2026-06-01 00:00 á¥á Period end = 2026-06-30 23:59 á«áááᣠá áµááá á¨áá áááªá«áá½á á JSON á«ááᣠá¥á \\"Generate report\\" á á á
á«áµááᢠáªááá± synchronously á ááá«á ᣠá¥á áá²á«áá áá° áááá®á½ áá½ áá°áá³áᢠá°á¨á 4. status completed á¨áá â \\"Download\\" á á á
á«áµáá (á¨ááá áµá á¥áá° template_ID.format á áá£á áá ) á¥á á áá«áµáá¡á áµ áá SHA-256 á á«á¨ááá¡á¢ áá
áá á á¨áá© á á¥á
ááááµá¨áᣠá \\"Compliance Schedules\\" tab ááµá¥ schedule ááá á©á¦ template IDᣠáµáááá½ = monthlyᣠperiod_window = last_month áááá¹ â áµááá± áªááá±á á«á± á«áµá¬á³á á¥á áá£á©á á¨ááµá¬á áá á«á³á«áá¢","tips":["á¨download á áá«á ácompleted status áªááá¶á½ á¥á» áá ááᢠáªáááµ failed á¨áá áááá®á¹á áááá± â á \\"Summary & integrity\\" á¥áá ááµá¥ á¨áµá
á°áµ áááá«áµ áá Failure field ááá«áᤠáááªá«áá¹á á«áµá°á«áá á¥á áááá¨áµá á¥áá°áá á«áµá¬á±á¢","Custom params field (á áááá¨áµ) á¥á Config (á delivery channel) áµáááá JSON áá áááᢠá syntax áµá
á°áµ form \\"Invalid JSON\\" ááµá áááá« á«á³á«á á¥á á¥á«ááá á áááá â quotes á¥á brackets á áááµá¹á¢","Schedules á¥á delivery channels á«á áá¨ááá« á¥á«á á á°á¨áá ᦠtrash icon á á á
ááµá¨á áááá¡á áá²á«áá áá°áááᢠá¨áá°á« schedule á áááá°á¨á áá áááá¢","cron áµáááá½ á«áá schedule á²áá¥á©á£ \\"Cron expression\\" field áá¥á» áá³á«á á¥á á¨áá´á³ áá (áá³áᦠ\\"0 7 * * *\\" â á á¨áá 07:00)ᢠáááá½ áµáááá¾á½ cron expression á á«áµááááá¢","áencrypted delivery (pgp/age/smime)ᣠá¨á°áá£á©á public key á \\"Recipient public key\\" field ááµá¥ ááµáá£áµáá á«á¨ááá¡ â á«á á¥á± encrypted á»áá ááµá«áµ á áá½ááᢠá á»áá áá
á ááµá¥ á«á ááµá¥á á¥á´á¶á½ á á¥áá³ áá á á¸ááá ᣠáµááá
á«áµááá¡ á áá á á½áá á á«á©áá¸ááá¢","á ááá» áá½ áá á¨\\"Recent completed\\" á¥á \\"Failed\\" counters á¨áá¨á¨á»áá¹ 5 áªáá
1á¶á½ á¥á» á á°áá â áá
áá£á á¨á¤áááµ á ááá«á½ á¥áá áá áµá³á²áµá²ááµ á áá°ááᤠáá á³áªá©á á \\"Generated reports\\" ááµá¥ áááá¨á±á£ á¨áá ááá áá°á¥ áá° 50/100/200/500 áááá¦á½ áá³á°á áá½ááá¢","Verify sanctions screening from its own logs: the absence of a report in this section does not mean screening is not running."]},"ledger":{"title":"Ledgerᣠá¥ááá¶á½á£ áá ááá«áá½","summary":"ááá á¨ááµá¨á©á general ledger á«á³á«á â á á¦áá³áá½ (áá³á¦á½) áá á«á áááá á¨áááᥠá¥áá
áµáá´áá½ á¨ááááᥠááááᢠá¨á¶áµáµ áá¾á½ á«áá ááᦠá¨áááᥠáááá á«á±á£ á á¥á
á¨á᪠áá³á¥ á¥ááá¶á½á£ á¥á á á°ááµá£ á ááᣠá¥á á áá á¨á°á ááá áµáá®á½á¢","whenToUse":"á¨á°áᨠá¦áá³ á᪠áá³á¥ á¥áá´áµ á¥áá°á°áá¨á¨ ááá°á½á£ áá°áᨠáá¥ááµ (tx_id) á¥áá
áµáá´áá½á ááááµá£ á¨á᪠áá³á¥ áá©ááµ áááááᣠááá á á¥á
á¥áááµ ááááᥠá²ááá áááá áááá±á¢ ledger ááááᥠá¨á¥áááµ ááá ááᦠá¨á¦áá³ á᪠áá³á¦á½ á áµááá á¨áááá¦á¹ áµáá á áá£á ᢠ\\"Ledger\\" áá½ view_ledger áá¥áµ áá áááᤠá¥áááµ ááá á á á°á¨á᪠á 2FA code (TOTP) áá¨ááá« áá áááᢠAuditors á¥á áá³á¥ ááá ááá®á á¨áµáá½á á³á« áµáá®á á¨áá áµáá®á½á áááµá³á¨á
\\"Aggregates\\" á áá áááá¢","concepts":["á¨Ledger áááᥠâ áá á á¨áááá á¨áµáᦠá¦áá³á (account_id)ᣠááááµ á«áá áá á (+ á¨ááá£á£ - á¨ááá£)ᣠáááá¬á£ ááᣠá¥á áá° áá¥ááµ (tx_id) á¥á ááµá°áµ (event_id) linksᢠáááá¦á½ á ááµá°á«á¨áá ááá á á á°á¨áá á¢","á¨áááá ááááµ (reason.operation) â hold (áááᥠáááµ)ᣠtransfer (á á¦áá³áá½ áá«á¨á ááµá°ááá)ᣠrollback (á¨ááµá áááá ááááµ)ᣠrevenue (á¨ááµá¨á áá¢/fee)ᣠcorrection (á á¥á
á¥áááµ)ᢠáááá á á¥ááá
áááá¶á½ áá£áªá« á ááá¢","áá áá½ á á¥áá
á á áá¶á½ â áááᥠá áááᬠáµáá¹ ááááá®á½ (kopecksᣠcentsᣠsatoshis) áá¨áá»áᢠᨠdecimal places á¥ááµ (decimals) á á á«á£á¢ + á áá³á¨ áá¨á¥ + áááᬠá¥áá¨áµ áá ááá°á¨á³áᤠá áááá¹ á«á± áá° á¨á°ááá° á
áá½ á ááá«á¸áá (ááá³á 10000 -> 100.00 RUB)á¢","á á«á£á¢ prod/test (env) â á¥ááá°á á¥á áá¨á« á¦áá³áá½ á°áá«áá°ááᢠá áá£áªá«áá½ ááµá¥ á«áá á¨á á«á£á¢ toggle production á¥á»á£ test á¥á» áááá¦á½áᣠááá áááá á á ááµ áá á¥áá²á«á© á«áµá½ááá³áá¢","á¥áááµ (Correction) â á¨ááá á¦áá³ á᪠áá³á¥á á¨áá«á³áµá (+) ááá á¨ááááµ (-) á á¥á
áááá¥á¢ á 2FA code (TOTP) á¨áá´á³ áá¨ááá« á£áá á¨á°áᨠform á áá á«á á¥á á¥áá° correction ááááµ áááá á áááá ááµá¥ áááµááá¢","áá ááá«áá½ (hourly/daily/monthly) â á á¦áá³ á¥á áááᬠáá°ááµá£ áááᣠááá á¨áá áá½ á áµááµá á¨á° á°á áµáá®á½á¢ á á áµá°ááᣠáá°áµ á áááá ᤠáá¹ áµááµ ááá áááá¦á½ á¥áá°á á ááá á¥á áá£á© áµááµ áá¼ á¥áá°áá°á¨á á«á³á«áá¢"],"example":"á°áá á 500 RUB áá° á¦áá³á¸á #4521 á áááµá¨á±á á«ááá«áᢠ\\"Ledger\\" áá½á áááá±á£ á account_id áá£áªá« 4521 á«áµáá¡á£ áááᬠRUBᣠá á«á£á¢ prodᢠáááá¦á½á á«á«áᦠholdᣠá¨áá« transferᢠá¨500 RUB áᢠá¨áá â áááá¡ á á¥áááµ á áá°á¨áááᢠá¨provider áá á¨áá¨áá© á áá áááá¡á á á¥á
ááááá á°áá°áᢠáá° \\"Corrections\\" -> \\"Create\\" ááá³á á¥á ááááᦠá¦áá³ 4521ᣠáá á 500.00 (á ááá³á = á᪠áá³á¥ áááª)ᣠáááᬠRUBᣠá áµá°á«á¨áµ \\"ááá°á¨áá ááá« á«á³á£ ticket #123\\"ᣠá¥á á áµááá á¨áá ááá tx_idᢠform 500.00 RUB = 50000 á¥áá
á á áá¶á½ (2 á ááá½) áááá á«á³á«áᢠá¨authenticator áá°áá áªá«á 6-á áá code á«áµáá¡ á¥á á«áµááá¡á¢ á¥áá° correction áááá á á²áµ áááᥠá áááá ááµá¥ áá³á«áᣠá¥á á¨á¦áá³ á᪠áá³á¥ á 500 RUB á«áµááᢠá \\"Aggregates\\" -> daily tab á á©á á¨á¦áá³á á¨áááµ áµáá á áµá°á«á¨áá á«á¨ááá£áá¢","tips":["á¨áá á ááááµ áááá áááµááᦠá ááá³á áá á á᪠áá³á¥á á«á³áµááᣠá áá³á áááá³áᢠá¥áááµ á¨ááµááᥠá ááµ preview á¥áá (á á¨ááá´ background = á¨ááá£á£ áá = á¨ááá£) á¥á \\"á¨á᪠áá³á¥ áááª/á
áá½\\" label á áááµá¹á¢","ᨠdecimal places á¥ááµ (decimals) á¨á¦áá³á ááᥠá á³á£á ᣠáµááá
ááááªá« áµáááááá wallet_id á¥á áááᬠáááá¹ â á áá ááá« áá° á¥áá
á á áá¶á½ ááá¨á© á¨á°á³á³á° ááááᢠdecimals badge á¥á á form áµá á«ááá \\"1 currency = N minor units\\" ááµáá áááµá¹á¢","á¥áááµ á¥áá° draft á ááá áµ á áá½ááᦠá¨ááááᥠá¨áááá áááᥠááᢠá¨á°á³á³á° á¥áááµ á á°áá«á ááááµ á counter-correction á¥á» á áµá°á«á¨áá ᢠáááá á áµá°á«á¨á±á á¥á á«á tx_id á ááá â áá
áááá¡á á¨áááá«á± áá á«ááááá¢","á áááá á ááµ áá á«áá á¨ááá á³á¥á á áµááµá ᨠá°á«á áááá¦á½á á á á«á£á¢ (locally) á« á£á«á (á tx_idᣠevent_idᣠunique_idᣠaccount_idᣠcurrency)ᣠá¨á°áá© tx_id/account_id/currency/environment fields áá ááá¥á á¨server áá áááᢠá á°áᨠáá³á¥ áá áµáááá áá¤áµ áááááµá£ á¨á á
áá ááá ááá
account_id field á áá ááá¢","áá ááá«áá½ áá²á«áá á á áááá ᦠáá áá á°ááµ/áá á á²áµ ááááá½ áá á áµáá®á½ ááµá¥ áááá© áá½ááᢠá áµá³á²áµá²ááµ card áá á«ááá \\"next recalculation\\" áá áááµá¹á¤ áá¥ááá°á áá ááµá³á¨á
á¨áá ááá«áá½ ááá
á raw áááá á áá© á¢"]},"currencies":{"title":"áááá¬áá½á FX rates","summary":"á¨ááµá¨á©á á¨áááᬠáá£áá» (codeᣠnameᣠᨠdecimal places á¥ááµ) á¥á á áááᬠá¥áá¶á½ áá«á¨á á«á á¨áááᥠá°ááá½á á¨ááá á¨á
áá¥á áááᣠproviderᣠá á«á£á¢á£ á¥á ᨠá°á á á ᢠáá á ááá»áᢠáá
multi-currency ááááá½á á¨áá á ááá¨á á¨á áá© á áµ á¨áá£áá» ááᥠááá¢","whenToUse"
1:"á ááááá½ ááµá¥ á¨áá áá á ááµ á á²áµ áááᬠ(fiat ááá crypto) áá° áµááá± áá¨á á²áááᣠááá á áááµ áááá¬áá½ áá«á¨á á¨áááᥠá°áá áááááµ/áááá á²ááá áááá áááá±á¢ á¨áááᬠáá£áá» áá«á áá áµá°á³á³áª á¥á» áááá (\\"Add currency\\" á áá«á á¨admin áá áá áá³á«á)ᢠá°ááá½ ásettlements á¥á ááá¨á áááááµ á£áá¸á á°á«á°áá½ á á³á«á á¥á á áá£á ᢠáááá©á áá¨áµ áá° ááá áá³á¨á» ááá áááááá ááááá¢","concepts":["á¨áááᬠcard â code (USD)ᣠᨠISO áá¥á code (#840)ᣠá¥á \\"Decimal places\\" (exponent) á«á³á«áᦠáááá¬á á¨áá¥á¥ á áá áµááµ á ááá½ á ááµ (2 áruble/dollarᣠ0 áyenᣠá¥áµá¨ 18 ácrypto)ᢠáµá á¨ááµá¨á© built-in áá£áá» á ááá","á¨Add-currency form â fieldsᦠCode (á¨áá´á³á£ á Latin ááá£á á¥á á á«áµ-á°á uppercase ááááᣠá¥áµá¨ 10 ááá)ᣠName (á¨áá´á³)ᣠNumeric code (ISOᣠááá³á 840 áUSDᤠá áá«á)ᣠDecimal places (á¨áá´á³á£ á¨0 á¥áµá¨ 18ᣠáá£áª 2)","á¨FX rate card â á¥áá±á á¥áá° \\"1 USD -> 1 RUB\\"ᣠá¨á°áá á¥á´á±á á«á± (á¥áµá¨ 6 decimal places)ᣠproviderᣠá¨áááᥠááá«á£ á á«á£á¢á£ á¥á ᨠá°á á á ᢠáá \\"Active from\\" / \\"Active to\\" á«á³á«á","á¨á á«á£á¢ toggle (prod/test) â á°ááá½ á á á«á£á¢ á°áá«áá°ááᢠá á°ááá½ áá½ á ááµ áá á¥áá° áá£áªá« áá°á«á (áá£áª prod)ᣠá¥á á áá á« form ááµá¥ á¨á°ááá á á«á£á¢ á«áááá (áá£áª test)ᢠTest á¥á production á°ááá½ á á á°á£ á áá","á¨á°áá provider (fx_provider) â á¨á°áá áááᦠinternal á¥á´áµ (á°áá á ááµá¨á© ááµá¥ á á¥á
ááááá) á¨á°ááá áá«á providers áááá ááᢠfield á¨áá´á³ áá","Nominal á¥á ᨠá°á á á ᢠáá â \\"Nominal from\\"/\\"Nominal to\\" (áá£áª 1) á°áá á¨á á°á¥á áµá á áá¶á½ á¥ááµ á«ááááᤠ\\"Active from\\"/\\"Active to\\" á¨á°ááá á°á á á ᢠááµ á UTC á«ááááᣠá¥á á¨áá¨á¨á» áá á¨áá´á³ áá á¥á á¨á
áá áá á á¥á¥á
áááᶠááá á áá áµ"],"example":"á°áá£áᦠá test á á«á£á¢ ááµá¥ dollar -> ruble á°áá ááµáá£áµá¢ \\"Currency rates\\" á áááá±á£ \\"Add rate\\" á á á
á«áµááᢠáááᦠProvider â internalᤠEnvironment â testᤠCurrency from â USDᤠCurrency to â RUBᤠRate â 90ᤠNominal from â 1ᤠNominal to â 1ᤠActive from â á¨á áá áá/á°ááµ (á á«áµ-á°á á°ááá·á)ᤠActive to â á ááµ áá áá°ááµ (á¥áá²áá á°ááá·á)ᢠá«áµááá¡á¢ \\"1 USD -> 1 RUB\\" card á áááá© ááµá¥ á á¥á´áµ 90.000000ᣠá¨test á á«á£á¢ badgeᣠá¥á ᨠá°á á á ᢠáá áá áá³á«áᢠááááá á°áá á«áµáááᣠááá³á 90.55ᣠá¥áá° áá áá¥á ááµáá£áµ á áá»áá â á¨á°áá á¥á´á± á¥áá° integer á¥á» á áá áá (á á¥áá
á á áá¶á½)ᣠáµááá
áááááááµ á \\"Nominal from\\"/\\"Nominal to\\" fields á ááá»á (ááá³á á°ááá á 100 á áá¶á½ nominal á«ááá)ᢠnominals á¨1 á²áá«á©á£ card á á°á¨á᪠\\"Effective rate\\" á«á³á«áá¢","tips":["á°áá á¥áá° áá áá¥á ááá£áᢠform á¥á validation á á¥áá
á á áá¶á½ integer á¥á´áµ á¥á» á áá áá (á¥áá° 1.25 á«á ááááá á backend ááµá
áá°á¨áá)ᢠááááá á°áá ááááá½á£ á \\"Rate\\" field ááµá¥ decimal point á³ááá \\"Nominal from\\" á¥á \\"Nominal to\\" fields á áá áá","á á«á£á¢áá áááá¨á±á¢ á áá¹ á ááµ áá áááá© á á ááµ á á«á£á¢ á á£á«á (áá£áª prod)ᣠform áá á áá£áª á test á°áá ááá¥á«áᢠá test á¨áᣠá°áá á prod á áá³áá â á áá ᨠáá á©áµá áááᥠ\\"á«áá©\\" toggle á áááµá¹","ááá ááá½ á UTC áá¸áᢠ\\"Active from\\"/\\"Active to\\" fields á¥áá° UTC á áµá°ááá³á (áá
á form ááá ááµá¥ á áá¥á³ á°ááá¿á)ᢠá¨áá¨á¨á» áá á¨áá´á³ áá á¥á á¨á
áá áá á á¥á¥á
áááᶠááá á áá áµá£ á áá ááá« ááµááᥠá á¨á½áá","á¨ááááá½ á ááµ áááᬠá«ááᢠᨠISO áá¥á code á¥á ᨠdecimal places á¥ááµ (exponent) á¨áá áá½á áµáááá parsing ááá«áᦠáruble á¥á dollar 2 ááᣠáyen 0ᣠáááªáᶠáááá¬áá½ á¨á áá ᢠá exponent ááµá¥ áµá
á°áµ á¨áá áá½á áá³á«á ááá¨á á« áá£á ᢠáááá¬áá½á áá¨á áá áµá°á³á³áª á¥á» áááá"]},"fiscalization":{"title":"Fiscalization áá
á®á½","summary":"áá¥á«áá³áá± á áá áá° fiscal data operator (OFD) áááááµ á¨á ááá ááá â á¨áµáá
á± áááá®á½á£ á¨áá¥á áµáááµá£ á¥á áá£áª VAT á°ááᣠá¥á á¨OFD credentialsᢠá á¥ááá
á
áá¥á®á½ áá á¨áµ ááµá¨á© á ááá« áá á¨áááᥠá°á¨á°áá½á á« ááá«á á¥á á áá«á ᢠá ááµ áá
á á á áá«á³ á¨á áá© terminals á á áá áá½ááá¢","whenToUse"
1:"á áá á á ᥠáá½ fiscal á°á¨á°áá½á ááµá áµ á²ááá áááá áááá± (á RF ááá« ááá á á¨Federal Law 54-FZ ááµáááµ)ᢠá¥áá
á á²áµ OFD áá
á ááá¥á«áᣠáááá®á½áá credentials á« á« á«áá³á ᣠáááááµá áááµá»á (\\"Ready\\" status)ᣠá¥á áá£á®á½á á«áµá°á«ááá ááá áá°áááᢠáááá© áááá á á ááµ á áá á á á ᣠá ᦠááááªá« á áá áááá£áᣠá¨áá« áá
á®á¹á á«á«áá¢","concepts":["OFD Adapter â á°á¨á°áá½ á¨á áá© á áµ á áááááµá¢ á¶áµáµ á áá«á®á½á¦ ATOLᣠOrange Dataᣠá¥á Stub (Test)ᢠStub á« á á¥ááá°á fiscalization á¨áá¨á« stub á²áá áá¥á± credentials á á á á¨áá ᤠáATOL á¥á Orange Data login/password á«áµááááᣠá¥á Orange Data á á°á¨á᪠API Key á á ááá á¢","Ready / Credentials â \\"Ready for fiscalization\\" status á¨OFD credentials á² áá á á á¨ááá´ á á á«á (has_credentials = Configured)ᢠá¨áá³á¨á» áááá®á½ á«áá°ááá áá
á© á á¢á« \\"Not configured (missing credentials)\\" á° á á á á· á á¥á á°á¨á°áá½ á á áá© á á¢","Company Information â INN (10 ááá 12 á ááá½)ᣠá¨á©á£áá« áµáᣠá¨á©á£áá« e-mailᣠsettlement address (payment_addressᣠá¨site/point URL)ᣠGroup Code (áATOL ᨠá ᣠ᪠᫠á¡áµá code)ᢠáá
ááᥠáá° á°á¨á°á á á ᣠá á¢","Taxation System â áá°á¨á°á á ááá»á ᦠOSN (general)ᣠUSN IncomeᣠUSN Income minus ExpensesᣠENVDᣠESNᣠPatentá¢","Default VAT â á°áá á áá á«áá° á á á áá° á°á¨á°á áá¥áá½ á á°á«á ᦠNo VATᣠ0%ᣠ10%ᣠ20%ᣠá¥á á¨á° á° á 10/110 á¥á 20/120á¢","Test Mode â á Settings á¥áá ááµá¥ checkboxᦠá¨production ááá
á¨OFD test endpoints á áá ááᢠá¥ááá°á á°á¨á°áá½á áá á á á á ááááªá« áááá áá
áµ á áá ááá¢","Terminals â áµááµ á¨á áá© terminals á¨áá
áá
á áá á¥áá° á° á« á« á á¨á á« á³ á counterᢠfiscalization ááá³á (inline / external / provider / none) á¨á á« á á á terminal á á«á± á
áá¥á®á½ ááµá¥ ááá¢"],"example":"á áá \\"Romashka LLC\\" (INN 7701234567ᣠOSN) á ATOL á á©á á°á¨á°áá½á á á ᣠᵠá«áµáááááᢠ\\"Create\\" á á á
á«áµááᣠá áá©á ááá¨á¡á£ adapter ATOLᣠá¨áá
á áµá á«áµáá¡ (ááá³á \\"ATOL main\\")ᣠá¥á Active á áááµá¹á¢ á \\"Company Information\\" á¥áá ááµá¥ INN 7701234567ᣠáµá \\"Romashka LLC\\"ᣠe-mailᣠá¥á settlement address áááᢠá \\"Tax Settings\\" ááµá¥ á¨áá¥á áµáááµ OSN á¥á default VAT 20% ááá¨á¡á¢ adapter Stub áµáááá \\"OFD Credentials\\" á¥áá áá³á«á â á¨OFD login á¥á password á«áµáá¡á¢ á«áµááá¡á¢ á card á¥á á áááá áá½ áá status áá° á á¨ááá´ \\"Ready\\" á ááá£á ᣠCredentials = Configuredᢠáá¥á á á áá© terminal á
áá¥á®á½ ááµá¥ fiscalization ááá³á á« á á á ᣠá¥á á¨áá
á© Terminals counter 1 ááááá¢","tips":["á áá á¥áµá¨á á ᨠᥠáµá¨áµ áááá© á£á¶ áá â áá
áµá
á°áµ á áá°ááᢠá áá¹ á ááµ áá á¨dropdown á áá á á ᨠᥠáá á«á¨ááá¡ (áááᦠ\\"Please select a partner to view their fiscalization configs\\")ᢠááá á áµááµá ᨠᰠ᫠á áá
á®á½á á áµáᣠINNᣠá¥á adapter name ᫠ᣠ᫠á á¢","Adapter = Stub á á¥áááµ fiscalize á á« á° á á á â á¨áá¨á« stub ááᢠááá¥á³ áµá« ATOL ááá Orange Data ááá¨á¡ á¥á credentials á á á áµ á á ᥠᨠᱠᣠá áá ááá« áá
á© á \\"Not Ready\\" status á á á« á á¢","áOrange Dataᣠá¨login á¥á password á á°á¨á᪠API Key á«áµáááá â field á form ááµá¥ á¨á ᳠ᨠá áá
adapter á² á ᨠᥠá¥á» ááá¢","INN 10 ááá 12 á ááá½á á á á á á (field á 12 ááá á¨á° á á° á ) â 10 áááá á á«ááµá£ 12 á á á áµ ááá°á¦á½á¢ áµáááááá±á áááµá¹á¦ áááá© áá° á°á¨á°á á á ᣠá á¢","áá
á á áµ á á áµ á¨áá á á á áµ áá á¥á áá¨ááá« á á ááá ᢠterminals á¨áá
á© áá ᨠᰠ᫠᫠á (Terminals counter á¨0 á¨á á á ᥠ)ᣠááááªá« áá
áá¥ááá« terminals fiscalization á¥áá°áá ᨠᥠὠá
1«á¨ááá¡á¢","Active checkbox áá
᩠ᥠá
á á á ᥠá á° á á á á á ᣠá á« á ᤠTest Mode á¨OFD production ááá test endpoints ᥠá á° á á á á á á ᣠá á« á ᢠá¥ááá
á¨á°áá«á© toggles áá¸áᣠá ᳠ᰠᣠá á á¢"]},"partners":{"title":"Partners (merchants)","summary":"\\"Partners (merchants)\\" ááá á ááµá¨á© á á©á ááá« á¨á á á á ᨠὠá á½ á® áá¥á¦á½á á¨á°ááá á°á³á³ááá½ registry ááᢠá¥áá
á áá®á½ ááá á«áᣠá áááá áá£áªá«áá½ á á á á ᣠAPI credentials (public/secret) á ᰠᣠḠá á ᣠá¥á áá°áá© á¨ááá« áá´áá½ áá³á¨á» á á á á« á á¢","whenToUse":"ááá á á²áµ ááá´ áá° ááµá¨á© áá á« á á á ᣠcredentials áá ᰠᥠᣠá¨á¦áá³áá»á¸ááá áá¥áá¶á»á¸áá á¥áá
áµáá´ áá á ᵠὠᣠááá á¨áá£á á áá á
áá¥á®á½á áá á á á ááµááᣠáá
á°áµá£ ááá account á°á«á°á ááᢠmanage_partners áá¥áµ á«áá¸á á°á áááá½ ááá á áµá°á³á³áªáá½ á¥á» á áá®á½á ááá áá ááµá°á«á¨á áá½ááᤠá á áá card áá á«áá \\"Ledger\\" tab á¨view_ledger áá¥áµ áá á¥á» ááááá¢","concepts":["Login á¥á name â login á¨á áá© áá© á¨ááá¢á« ááá« áá (á¥ááá áá e-mail)ᣠá¥á name á¨á ᳠ᨠá ᨠá ᥠᥠáµá ááᢠlogin á @heth.me á« á á á áá© á á«áµ-á°á Heth.me á°á³á³á á° á° á á á á á á« á ᣠá áá ááá« á°á« merchantá¢","Password (pass) â á áá á« áá á¨áá´á³á¢ á² á« áµ á° á« á á ᣠá¨á ááá á á á« á \\"New password\\" field á£á¶ á á° á á ᦠpassword á¨á á ᨠá á á¥ááᵠᨠá ᣠá¥á» ááá¢","Status flags â is_active (active/disabledᣠá áá£áª on)ᣠneed_confirm (ááááá½ áá¨ááá« á á ááá ᣠá áá£áª off)ᣠá¥á partner_area_enabled (áá° Partner Area áá³á¨á»á£ á áá£áª off)á¢","Organization (organization_id) â á¨á áá© áᰠᣠá ᤠᵠáµáá
áµ linkᤠááááá áá£á«áµ á¥á á¨ááá« áá´ á
áá¥á®á½á á á á ᨠᵠá á á
á á á¢","params (JSON) á¥á credentials â á¨á áá© á¨á áááááµ áááªá«áá½á¢ á¥áá
áAPI public key á¥á secret á ᨠá á» á ᦠá card áá secret áááá ᰠḠá á á á¥á á á á á á½ á ᣠá¥á á¨á° á á á á«ááµ (binded_card) á PCI DSS ááá½ áá á¨áµ áá³á«á â á¨ááááªá«áá¹ 6 (BIN) á¥á á¨áá¨á¨á»áá¹ 4 á ááá½ á¥á»á¢","form_settings (JSON) á¥á á¨áá´ toggles â á¨ááá« form á
áá¥á®á½á¢ áá¹ áááá®á½ QR providers Alipay QR á¥á WeChat Pay QR á¥á dCLS á°á³áµá (dcls_participant) á á«ááááᣠá¥á«áá³áá± á \\"Inherit from organization / Enabled / Disabled\\" ááá³á¢"],"example":"á á²áµ á±á
áááááµá¢ \\"Create\\" á á á
á«áµááᣠáááᦠlogin [email protected]ᣠáµá \\"Example Store\\"ᣠpasswordᣠá¨áááá© áµáá
á±á ááá¨á¡á¢ \\"Active\\" checkbox á áá«áᣠ\\"Partner Area access\\" á á« á á ᢠá«áµááá¡ â á¨á áá card á ᨠá á³ á ᢠá card áá \\"Generate Secret\\" á á á
á«áµááᦠáµááá± API secret á á ááµ áá á¨ááµá áááá« \\"á áá á«áµááá¡áµá£ á¥áá°áá á á á³ á á \\" áá á«á³á«á â á á á± áµ á¥á á¨public key áá á merchant á ᵠᡠᵠᢠááᶠá áááá© ááµá¥ \\"shop\\" á á ááá á á° á ᡠᣠáá° \\"Merchants\\" tab á á á ᩠ᣠá¥á áá¥á¡á á¨header counter áá á«á«áᣠááá³á \\"Partners (1 / 340)\\"ᢠcard á á²á¨áá±á£ á \\"Recent transactions\\" tab áá á¨prod á¥á test á á«á£á¢áá½ á¥áµá¨ 10 ááááá½á á«á«áᣠá¥á á \\"Wallets\\" á¥áá ááµá¥ á¨á áá©á á᪠áá³á¦á½ á ááá±á á á«á£á¢áá½á¢","tips":["ááá±á JSON fields (params á¥á form_settings) á áµ á© áµ á ᨠá á ᣠá ᦠá syntax áµá
á°áµ invali
1d JSON ááá¥ááµ á á³ á« á á¥á áµá
á°á± á¥áµá¨á ᵠᰠ᫠ᨠá áµá¨áµ form á á á á ᥠá á¢","API secret á \\"Generate Secret\\" á áá«á á á áá card áá á á á á ᨠᵠá á
áµ á ááµ áá á¥á» á á³ á« á ᢠáá²á«áá á«ááµá á ᡠᵠᣠá¥áá°áá á á á ᨠᵠá á á ᥠá á³ á ᤠá preview card áá secret áááá ᰠḠá á á á¥á á á á á½ á áá½ááá¢","áAlipay/WeChat á¥á dCLS \\"Inherit from organization\\" ááá³ á áá© ááá½ á
áá¥á á¥áá°ááá á¥á á¨áµáá
á± áá ᥠá á° á á° á á á áááµ ááᢠááá
á¨á°áᨠá áá á£á
᪠á á» á á²ááá á¥á» \\"Enabled\\"/\\"Disabled\\" á«ááá â á áá ááá« á á á ᵠᵠᣠá á á áµ á á¡ á¢","áááá© á áá½ á áá½ (á 100 áááá¦á½ á áµ) á¨infinite scroll áá á á« á á ᣠ\\"All / Heth.me / Merchants\\" tabs á¥á á¨áµáá
áµ áá£áªá« áá á áµááµá ᨠᰠ᫠á áááá¦á½á á á° á ᥠ᫠á ᢠá login ááá áá áá° server á á á³ á ᣠáµááá
á áµ á á á á ááá á scroll á¥á» ᨠá á á« áµ ááá
login ááµáá£áµ á á» á á á¢","á áááá© cards áá á«á \\"Edit\\" á¥á \\"Delete\\" á áá«á®á½ áá áµá°á³á³áª á¥á» áá³á«áᤠá edit form ááµá¥ á áµ á á áµ á á°á¨á᪠áá¨ááá« á á ááá ᢠ\\"Create\\" á áá«á á«áá© áá¥á¶á½áá (manage_partners) á áµááµáá áááµá¹á¢"]},"organizations":{"title":"áµáá
á¶á½á£ á á£ááµá£ áááá½","summary":"áµáá
á¶á½á (á¨á°áá á workspaces â á áá®á½áᣠterminalsᣠá¦áá³áá½á á¨á ᧠ᵠá \\"tenants\\") á¨á á ᥠ᩠á áµ á¥á áµá¥ ᥠ᫠Ḡá á á¨á á« áµ á° á³ áµ á© á áµ á¨á áµá°á³á°á áááᦠá°á«á°áá½á áá¨áᣠáááá½á á á ᰠᥠᣠáá¥á¶á½á á áµ á ᵠᣠá¥á áá° á°áá© terminals áá³á¨á» á á« á« á ᢠáµáá
áµ á°á« (Fintech) ááá áá° bank ááá³ (BaaS) á¨pricing plan á¥á á¨áá¥á¥á licenses áá á á á ᥠáá½ááá¢","whenToUse":"áá°áá á á á²áµ workspace ááá áᣠá
áá¥á®á¹á ááµá°á«á¨á (nameᣠá á«á£á¢á£ brandingᣠá¨ááá« formᣠQR providers)ᣠáµáá
áµá á archiving ááá«á á¨á áááááµ á á ᣠᵠᣠááá á¨á°áá«á© á¨áá³á¨á» á°á¨ááá½ á«áá¸á á°á«á°áá½á á¡áµá á á á ᣠᵠá²ááá áááá áááá±á¢ ááµááá¶á½ áá¥á¶á½ á ááá áá á á ᰠᨠ᳠á ᦠá¨ááµá¨á á áµá°á³á³áª (isAdmin) áááá á«á«á á¥á á« á° á á á ᣠá¨á°áá á-á£áá¤áµ á¨á«á±á áµáá
á¶á½ á¥á» á«áµá°á³áµá«áᣠá¥á ááá½ á á£ááµ á ᰠᰠᣠḠá áá¥á¶á½ ááµá¥ á á° á« á (manage_settingsᣠmanage_membersᣠinvite_members)á¢","concepts":["Organization (tenant) â á¨á°áá áá á¨áá°á-á°á¨á á® á á´ á á ᦠá áá®á½áᣠterminalsᣠá¦áá³áá½á á ᧠ᵠá á ᢠá¥á«áá³áá± name (á¢á«ááµ 3 ááá)ᣠslug (a-zᣠ0-9ᣠá¥á hyphen á¥á»á£ á¨name á á«áµ-á°á á Cyrillic transliteration á á á á« á )ᣠá á«á£á¢ (test/prod)ᣠdescriptionᣠlogoᣠá¥á brand color á áá","á¨áµáá
áµ ááááµá¦ Fintech ááá BaaS (Bank) â á°á« áµáá
áµ á \\"Convert to bank\\" áµáááµ á ááµ áá áá° bank á á á ᥠáá½ááᢠábankᣠdata region (data_region)ᣠBaaS planᣠá¨áá¥á¥á license (áááá© á ááá áá á á ᰠᨠ᳠á )ᣠBICᣠá¥á á¨bank license áá¥áá áá á á á á» á ","BaaS plan â Starter (á¥áµá¨ 10,000 áá³á¦á½á£ áá á¨á³á features)ᣠGrowth (á¥áµá¨ 100,000ᣠá¨á° á« á á )ᣠEnterprise (á« á á° á á° á ᣠááá features)ᢠá \\"Manage plan\\" á á áµá°á³á³áª á¥á» á á ᨠ᫠á ᤠáµááá± á«á± á plan á
á°á á°á¨á°á áá á áááµá¨áµ upgrade ááá downgrade áááá£á","á¨á á£á áááá½ (7 áá¸á)ᦠownerᣠadminᣠfinanceᣠoperatorᣠsupportᣠouther_admin (áá«á admin)ᣠviewerᢠááá áá°á á á¨áá¥á¶á½ áµá¥áµá¥ á á«áµ-á°á á«ááááᢠowner á² á« á á á á ᨠᥠá áá½ááᣠáá
á ᰠᨠá á áá½ááᣠá¥á á á á áµ á áá½áá","áá¥á¶á½ (permissions) â á¨á á£á card 6 ááá checkboxes á«á³á«áᦠmanage membersᣠinvite membersᣠmanage settingsᣠview partnersᣠview terminalsᣠview transactionsᢠá¨áá
á á á°á¨á᪠á¨á°áᨠ\\"Can invite\\" flag (can_invite)ᢠá áá
áá½ áá checkboxes read-only áá¸á â á¨ááá á á ᨠ᳠á á¥á á¨áá ááᥠáá á á¥á¨á á á ᨠ᫠á ","á¨Terminal á ᫠᫠ᣠ(terminal_ids) â á\\"External admin\\" áá (outher_admin) á¥á» á á³ á« á ᦠá¥áá°áá
á«á á á£á á á á á á© á á terminals áá á¥á» áá³á¨á» á« á á á ᣠáá á
áá áµáá
á± á áá°áá","Archiving ᨠá áµ á á áµ ááá
â áµáá
áµ á á ᰠᨠá á ááá áá á archive (á á áá«á áááá«áµ áá)ᦠread-only á á á á ᢠá¨ááµá¨á á áµá°á³á³áª á¥á» un-archive á á« á° á á áá½ááᣠá¥á á áá°á± á á²áµ owner á á ᰠᥠá áá áµ","dCLS Participant á¥á QR providers â á áµáá
á± á
áá¥á®á½ ááµá¥ checkboxesᦠdCLS Participant áá° FX SettlementᣠNetting Bridgeᣠá¥á Treasury áá³á¨á» á ᨠá á³ á ᤠQR providers (AlipayᣠWeChat PayᣠUnionPayᣠLINE PayᣠPayPayᣠKakaoPay) á HethWallet ááµá¥ áá áá®á½ á áá£áª á¨áµáá¹ QR codes ᥠá á° á á á áááµáá","Break-glass access into an organisation's scope is a separate procedure with a time limit and a mandatory justification. Every action taken under it is flagged in the audit log, so it belongs to incident response rather than day-to-day work."],"example":"á°áá á \\"Romashka LLC\\" áá° ááµá¨á© á¥á¨áᣠááᢠá áµá°á³á³áªá \\"Create\\" á á á
á«á°áááᣠname \\"Romashka Pay\\" á á«áµáá£á â áµááá± slug \\"romashka-pey\\" á á á«áµ-á°á á« á á á« á ᤠá¨á°áá á áááá owner á á á á ᣠá ᣠtest á á«á£á¢á á á á á ᣠá¥á á á áá«á logo URL á¥á brand color \\"#004D40\\" á á á á á» á ᢠá«áµá á á á áá Fintech áµáá
áµ card á á³ á« á ᢠáá¥á á áµá°á³á³áªá \\"Members\\" á (á card áá á«áá á¨á°áá½ icon) á ᨠá á³ á ᣠ\\"Invite\\" á á á
á« á° á á á ᣠᨠá ᳠ᥠᣠá á á« áá email á«áµáá£áᣠá¥á \\"Finance\\" ááá á á á ᣠá â áá¥á¶á¹ (view transactionsᣠbalancesᣠexportᣠááá°) á á«áµ-á°á á á á á á ᢠᨠá á á ᣠlink áá° email á á á³ á ᢠááá¶á£ á á áµ terminals á¥á» áá á« á á á á á® á áµ á« á á° á ᣠá á£á á \\"External admin\\" áá á ᳠ᨠá á á¥á á¥ááá« áááµ terminals á Terminal IDs field ááµá¥ á á ᨠᣠá â áá³á¨á» áá¥áá± á¥á» á á ᰠᣠá ᢠá°áá áá áá° banking áááµ á² á« áµ á ᣠowner \\"Convert to bank\\" á á á
á« á° á á á ᣠdata regionᣠGrowth planᣠá¥á á¨áá¥á¥á license á á á ᣠá â áµáá
á± \\"BaaS\\" badge á¥á plan á« á á á á¢","tips":["slug á á á¥á
á¥áµá¨ á áµ á á© áµ áµá¨áµ name á á¥á» á ᨠᰠá á ᦠslug á á«áµá á¥áᰠᰠᵠᰠ᫠ᨠá áµ auto-fill á á á á ᢠslug á¨áá´á³ ááᣠá¢á«ááµ 3 áááᣠLatin/á ááá½/hyphen","á á«á£á¢ (test/prod) á áµááá á
áá¥á ááᦠcards á á á«á£á¢ badge á á á ᨠ᳠á ᣠá¥á á header ááµá¥ á«áá áá£áªá« á¨á á á á á á á«á£á¢ áµáá
á¶á½á á¥á» á¥áá² á« á³ á© á«áµá½ááá³áᢠproduction áµáá
áµá á ᵠ᩠ᨠᵠᥠᥠᨠᵠá test á áµ á á á© ","á á áµá°á³á³áª á² á á á ᣠowner (á°áá á) á á ᨠᥠá áá áµ â á«á á áá± \\"Save\\" á áá«á áá á á á á á ᢠá¨ááááªá« áµáá
á±á á¨á á ᥠá á°áá á á«áµá á á á áá á á«áµ-á°á áá° setup wizard á á á° á³ á ","á¨á á£áá áá á á ᨠá áá¥á¶á»á¸áá áá²á«áá á á á²á± áá áá£áª áµá¥áµá¥ á á° á« á â ᨠá á ᰠᥠá¨áá¥áµ áá©áá¶á½ á áá
áá½ áá á á ᵠᰠ᫠ᨠá á (checkboxes read-only áá¸á)ᢠ\\"Owner\\" áá á á ᰠᣠᣠá á á
᳠ᣠá¥á á á áµ á á áµ á á áááá¹ á á©á á á á á á ","Terminal IDs field á¥á áµááá (á á á á á© á á terminals áá á¥á» áá³á¨á») á\\"External admin\\" áá á¥á» á á³ á« á ᤠáááá½ áááá½ á¨áá","\\"Add\\" ááá Client ID (á áµááµá ᨠá á ᨠá°áá á UUID) á áµ á ᣠᵠá á á á á ᣠ\\"Invite\\" áá áá° á á²áµ á°á áá email á á á« á â ááá±á ááá³áá½ á ᳠ᰠᣠá á ᢠᨠarchive áµáá
áµ á ᵠᰠ᫠ᨠá á áá½ááᤠun-archiving áááµá¨á á áµá°á³á³áª á¥á» á á á á á¥á á á²áµ owner á á ᰠᥠá á á á á ","Close break-glass access as soon as the investigation ends: access left open looks worse in an inspection than the incident it was opened for."]},"dclsNetwork":{"title":"dCLSᦠá áá³á¨ áá¨á¥á£ á°á³á³ááá½á£ minters","summary":"ááá á¨dCLS á áá³á¨ áá¨á¥ ááá³á á«á³á«á â á á£áá®á½á ááá¶á½ áá«á¨á ááááᬠááááá½ settlement ááá (PvP settlement)ᢠá¥áá
á á áá³á¨ áá¨á¡ ááµá¥ áá á¥áá³á (á°á³á³ááá½)ᣠá¨áµáá¹ fiat tokens á¥áá° á° á° á¡ á¥á ᥠá á° á° á° á á ᣠnetting windows á¥á settlement batches á¥áá´áµ ᥠá á° á á« á ᱠᣠá¥á â á minter áµáá
á¶á½ â ᨠá á á ᣠstatus á mint/burn token á¥á«ááá»á¸áá á« á« á á¢","whenToUse"
1:"á¨dCLS á áá³á¨ áá¨á¥ á¤áááµá ááá°á½ á²ááá á á á ᱠᵠᦠáµáᵠᨠḠᰠá á°á³á³ááá½á£ á ᣠ᩠netting window á á¼ á¥áá°ááᣠá¨áá¨á¨á»á settlement á¥áá´áµ á¥áá° á ᰠᣠtokens ᨠᰠᰠá á ᥠá á° á á ᢠ\\"network\\" ááá áá áá³á¨ áá¨á¥ á°á³á³ááá½ á¥á ádCLS operator á¥á» á á á á (á°á« á¨ááµá¨á á áµá°á³á³áª á á« á á )ᢠ\\"minter\\" á¥áá ᨠḠᰠá profile ᣠá Ḡá dcls_minter ááááµ áµáá
á¶á½ á á³ á« á â á á á ᣠá á¥á á¨on-chain mint/burn á¥á«ááá½á á áá»á¸á á á ᨠ᳠ᰠá á¢","concepts":["Network Overview â á á áá± áá á á«áµ metricsᦠᨠḠᰠá á°á³á³ááá½ á¥ááµ (á¥á á á
áá)ᣠáá° á ᣠ᩠netting window countdownᣠá áá¨á¨á»á window ááµá¥ á«á settlements á¥ááµá£ á¥á á¨áá¨á¨á»á window netting ratioᢠá¨á³á½ â áá° á°á³á³ááá½á£ tokensᣠbatchesᣠá¥á windows ᨠá ᪠á á½ á cardsá¢","Participants â ᨠḠᰠá á£áá®á½á ááá¶á½ á áá á¨á¥á¦ ááá áµáᣠá¨áá áááᣠsettlement modeᣠETH á áµá«á»á£ statusᣠᨠá á½ á° á
ááᢠááá (á áµáᣠá áá áááᣠááá á ETH á áµá«á») á¥á á settlement mode áá£áªá« á áᢠpublic whitelist ááᥠá¥á» á á³ á« á â KYB áááá®á½ á¥áá
á á á³ á© á á¢","Settlement mode (settlement_mode) â á°á³á³á áá´á³áá½á á¥áá´áµ ᥠá á° á ᨠá á ᦠledger (á ááµá¨á© á¨ááµá¥ áá³á¥ á á©á)ᣠonchain (á blockchain settlement)ᣠááá bothᢠá¨á°á³á³á statusesᦠapprovedᣠpending_kybᣠkyb_submittedᣠunder_reviewᣠrejectedᣠsuspendedᣠrevokedá¢","Tokens & Reserves â á¨factory á¨FiatTokens cardsᦠsymbolᣠnameᣠchainᣠcategoryᣠtotal supplyᣠbacking ratio á¥áá° áá¶áᣠá¥á fully-backed flag (fully backed / under-backed)ᢠááᥠá á ᥠ᳠á¨contracts á á á ᣠá á¢","Netting Windows / Settlement Batches â á£á 4-á°ááµ windows á¨netting ratio áá (á bilateral matching á°áá«á áá´á³áá½ áµááµ á¥ááµ á á ᵠᥠá á° á° á« á« á± ) á¥á ᨠᰠᨠá á áááªá«áá½ á¥ááµá¤ á ááµ batch áá áᵠᨠᰠá á á á window á á á á³ á á¥á ᨠledger vs on-chain áµá¥ ᥠá á¥á ᨠᵠá
á° áµ á¥ááµ á«á³á«áᢠá ááá±á áááá®á½ ᨠᨠᵠá á ᰠᥠá á ᨠᣠá ᦠ25 / 50 / 100 / 200á¢","Minter â átoken issuer áµáá
áµ á á«áµ áá¾á½á¦ onboarding status (profileᣠKYBᣠMINTER_ROLE grant TXᣠsetMinterCap TX)ᣠKYB á áµ á ᣠᵠᣠᨠḠᰠá mint/burn á¥á«ááá½ queueᣠá¥á ᨠᰠá Ḡá ááááá½ á³áªáᢠá¥á«ááá½ á Safe signature áá° blockchain á á á ᣠá ᣠá¨áá« minter á¨áá¥ááµ hash á á á¥á
á«áµáá£áá¢"],"example":"ᨠᰠ᳠᳠á á£áá á°á«á°á \\"Network Overview\\" á á ᨠá á³ á á¥á á«á«áᦠ\\"Approved participantsᦠ12 (of 15)\\"ᣠ\\"Next netting windowᦠin 01:47:12\\"ᣠ\\"Settled in the last windowᦠ340\\"ᣠ\\"Netting ratioᦠ82.50%\\"ᢠáá° \\"Participants\\" á á á³ á ᣠá settlement mode áá£áªá« \\"On-chain\\" á á á á ᣠá ᣠá¥á \\"Kyrgyz\\" á á ááá á á° á ᣠá â á áá á¨á¡ á approved statusᣠá¨áá ááá KGᣠá¥á ETH á áµá«á» á« á á counterparty á«á³á«áᢠá¨áá« á \\"Netting Windows\\" ááµá¥ á á° á¡ á 100 á«áááá á¥á á áá áá Errors 0 áááá á á áµ á» á ᢠá á°ááᣠminter áµáá
áµ á \\"Pending Instructions\\" ááá ááµá¥ áRUB token 500000 ᨠḠᰠá mint á¥á«á á«á«áᣠᰠá á³ á Safe áá¥ááµá á á á á á ᣠ\\"Record TX\\" á á á
á« á° á á á ᣠhash 0x... á¥á á¨block áá¥á á«áµáá£á â á¥á«áá áá° executed status á á á á³ á á³ á á¥á á \\"History\\" ááµá¥ á á³ á« á á¢","tips":["\\"network\\" ááá observability á¥á» ááᢠá¥áá
á°á³á³ááá½á á á½ á
1° á
ááá statuses á á ᨠá á áá½ááᤠoperator dCLS profile status á¥á á á á ᣠá á á á á« á ᢠᨠá á á á
á°á³á³á á«á᳠ᨠâ ááááªá« ᨠsettlement mode áá£áªá« á¥á á¨ááá string á á á ᵠṠᣠá áá á¨á¡á ᫠ᣠ᫠á á¢","under-backed flag (ᥠá á± á« á á token card) backing ratio ᨠá á á á³á½ áááá á«áááá³á â áá
reserves á áá ᨠ᳠ᰠá ááááµ á¥áá áá²á«áá áµá
á°áµ á áá°ááᢠá¥á´á¶á½ á á ᥠ᳠á¨contracts á á á ᣠá ᣠáµááá
tokens á á á production á áá³á¨ áá¨á¥ áá á« á á° á á á á¡ á£á¶ token áááá á á á áá½ááá¢","á minter áá½ áá á«áá \\"Submit KYB\\" á áá«á profile á pending_kyb status á² á á á¥á» áá áá â á ááá½ statuses (kyb_submittedᣠunder_reviewᣠapprovedᣠrejected) package á á áµ á
á° áµ á¥áá°áá á á á áµ á ᣠᵠdisabled ááᢠá°áá¶á¹ á«á³á¸á ᨠá á á á á¹ áá á á« á á ᣠá¥á áµááá± operator á á¥á» á« á³ á á á á¢","áá¥ááµ á² á á á á¡ (Record TX)ᣠhash á Safe ᨠᰠá ᨠá á áá á á¥á
á á ᣠá ᦠᨠá á á á á á
áá¸áµ 0x á¨64 hex ááá áá ááᣠá¥á á¨block áá¥á á áá«á ááᢠá hash ááµá¥ áµá
á°áµ áá° á° á³ á³ á° link á á á« á â ᨠá ᨠá á ᥠá á ááµ á¥á´á±á á blockchain explorer á«á¨ááá¡á¢"]},"workflow":{"title":"Workflow / BPM â ᨠá á áµ áá°á¶á½á ááá½ builder","summary":"Workflow / BPM ááá á Admin Area ááµá¥ ᨠᰠá á ᣠᨠá á áµ áá°áµ engine ááᢠáá°áµá á á áµ á á á³ á (ááá³á á¨á°áá á onboarding ááá á¨ááá« áááá) á¥áᰠᨠᰠᨠá á á½ ááµá ᣠá ᥠᱠinstances ááµá¬áµ ᣠá á° á« á° á á½ á¨á¥á
tasks á á ᰠᥠᣠá¥á áá³ á á á½ á á decision tables á¥á business rules á á«áµ-á°á ááµá¨á â á®áµ á³ á« áµ á° á« á á â á«áµá½ááá³áá¢","whenToUse":"ááá á¨ááµá¨á©á end-to-end áá°á¶á½ áá á« á á
á© á áá ᨠ᳠ᰠá áoperationsᣠcomplianceᣠá¥á product á°á«á°áá½ ááᦠá¨á°áá á onboarding á¥á áá¨ááá« (KYC)ᣠᨠá á½ á° á
áááá¶á½á£ anti-fraud á¨ááá« áá°á»áá½á£ ᨠᰠá á á½ ááµá°áááµá¢ á² á á á á á á ᱠᵠᦠá á²áµ áá°áµá á¥áá° ááµá á á á ὠᤠá áá áµááµ áá°á¶á½ ᥠá á° á á° á© á¥á ᨠᵠᥠá á° á ᣠá á áá¨áµá¤ á¨á¥á
task áá° áµá« á á ᰠᵠᤠᨠá á³ á á áááá® (á¨áá á á ᰠᦠὠᣠrisk ááá½) á« á developers á á ᨠá ᢠdashboard (Workflow Operations Center) ááµ á ᶠὠá á¥á SLA á° á ᢠá áµ á áá ᨠ᳠ᰠá á ᰠᨠá operator á áá ááá¢","concepts":["Definition â ᨠá á° áµ template ááµáᢠversion (v1ᣠv2...) á¥á status á ááᦠdraft (ᥠᨠᰠᵠᰠ᫠ᨠá )ᣠpublished (ᨠ᳠ᰠá ᣠá ᥠᱠinstances á á° á© áá½áá)ᣠarchivedᢠá á° á draft á áá° áµá« ááá³ á« á á á³ á
á³ á á¢","Instance â á definition ᨠᰠá ᨠᨠá á° áµ ááµá¬áµ á¨á«á± variables áµá¥áµá¥ ááᢠStatusesᦠrunningᣠcompletedᣠfailedᣠcancelledᣠsuspendedᢠInstance ᨠᰠá á Ḡáááá«áµ áá á á á á á¥á á ᰠᨠá áá½ááá¢","Task â á°á«á°á á ᨠá á á á« á á áµ á¨á¥á
á°á¨á (human task)ᢠStatusesᦠpendingᣠclaimedᣠcompletedᣠfailedᣠescalatedᢠtask ᨠᡠᵠá áá á¥á deadline (due_at) á ááᤠá°á«á°áá ááááªá« á á áµ á° á á (claim)ᣠá¨áá« á form_schema áá á¨áµ form ᥠᨠá á á
1« á á á
á á á á¢","BPMN editor â ᨠá áµ á ááµá builderᦠá¨palette nodes áá° canvas á á á° á³ á ᢠNodesᦠevents (StartᣠEndᣠTimer)ᣠtasks (ServiceᣠHumanᣠScriptᣠLoopᣠMulti-Instance)ᣠgateways (XOR â á ááµ á
á á á« á ᣠAND â á áµ á ᩠ᣠOR â á áá«á³)ᣠsub-processᢠá nodes áá«á¨á links ááá³ á¥á default á
á á á« á á á ᫠Ḡá áá½ááá¢","Decision Table (DMN) â á á« áµ - á° á áá³á \\"input -> output\\" á áá á¨á¥á¢ Input á¥á output ááá¶á½ á¥á rule á¨áµ á á½ á á á á» á ᢠhit policy áá¤á± ᥠá ᴠᵠᥠá á° á á ᨠᥠáááµááᦠUNIQUEᣠFIRSTᣠPRIORITYᣠANYᣠCOLLECT á¥á á° á á á® á¹ (SUM/MIN/MAX/COUNT)ᣠRULE_ORDERᣠOUTPUT_ORDERᢠá áá á¨á¥ á test cases áµá¥áµá¥ áá á á á á á á¥á á á° á« áá½áá (simulate)á¢","Business Rule â á¨\\"conditions -> actions\\" á
á á½ ááᢠContextᦠpaymentᣠkycᣠworkflowᣠcustomᢠConditions á logical AND á á á á á ᤠoperatorsᦠeqᣠneqᣠgtᣠgteᣠltᣠlteᣠinᣠnot_inᣠcontainsᣠmatchesᣠexistsᣠnot_existsᣠbetweenᢠActionsᦠsetᣠincrementᣠdecrementᣠappendᣠremoveᣠcallᣠraise_eventᢠpriorityᣠstop_on_match flag (á á á á ᪠᫠á á ᥠá áµ á á á )ᣠá¥á enabled á áá¢","The dead letter queue collects instances that have exhausted every retry. It is not an engine failure but the place where a process waits for a person: an instance is either restarted once the cause is fixed or closed by hand.","An error boundary in the process diagram catches a step failure and routes the instance down a fallback branch. Without one, any step error stops the whole process."],"example":"á°áá£áᦠá¨ááá« risk áá°á»áá½á á á«áµ-á°á ááµá¨áᢠ\\"Business Rules\\" á á ᨠá á³ á ᣠNew Rule á á á
á« á° á á á ᢠName = \\"Large payment â manual review\\"ᣠContext = paymentᣠPriority = 100 á á á á» á ᢠááá³ á« á á á ᦠField = amountᣠOperator = gtᣠValue = 100000ᢠaction á« á á á ᦠType = setᣠField = requires_reviewᣠValue = trueᢠEnabled á á« á á á á á¥á á« áµ á á ᣠá ᢠáá° áµá« ᨠá áµ á ᣠᵠá á ááµá£ Test Rules á á ᨠá á³ á ᣠáá° facts field JSON {\\"amount\\": 150000} á á«áµáá£áᣠRun á á á
á« á° á á á â á á á Matchedᦠ1 rule á¥á requires_reviewᦠtrue á« á á ᨠáá¤áµ facts á« á³ á« á ᢠáá¥á á BPMN editor ááµá¥ áá°á±á á á³ á á ᦠStart -> Service Task (risk áµááµ) -> XOR gateway ᨠrequires_review == true ááá³ áá áá° Human Task \\"Payment review\\" (team = compliance) á¨á á ᫠ᣠá áá ááá« á á ᥠ᳠áá° Endᢠdefinition á á« áµ á á ᢠá Workflow Operations Center dashboard ááᣠá á° á ᨠá áá (ááá³á Last 24h) KPIs á«á«áᦠRunningᣠCompleted Today ᨠá á á á á
á ᶠá ááᣠFailedᣠá¥á SLA Complianceᤠcompliance officer áá° Tasklist á á á³ á ᣠá pending ᫠ᣠ᫠á ᣠtask á á á áµ á³ á (Claim)ᣠá¥á form á á á á á áµ á« á á á
á á (Complete)á¢","tips":["Instances ᨠá á° á© áµ á á³ á° á definition á¥á» ááᢠdefinition á draft status ᥠᵠ᫠á ᣠáá° instances ᨠá á á á áá«á á á á á á â ááááªá« Publish á« áµ á á ᢠᨠá ᰠ᫠ᨠ᳠ᰠá á ᨠá áµ á á ááá
á á á²áµ version ááá¦á½á ááµá¨á á°á
ááá± á¨á° á á á ááá¢","á business rules ááµá¥ Value field á¥áá° JSON á parse ᦠábetween á¥á in operators array á ᫠ᬠᥠ᫠ᬠᵠá«áµáá¡á£ ááá³á [100, 500] ááá [\\"RU\\",\\"KZ\\"]ᢠá°á« string á¥áá° string á á á« á ᢠᨠá á á áµ á á ááµ áááá ááá á Test Rules ᫠ᵠ᪠ᱠâ ᨠᰠᨠ᳠stop_on_match ᨠá á© áµ á ááá½ á áá»á¸á ᣠá á° á á á ááá³ á á« á á ᥠáá½ááá¢","á decision table ááµá¥ hit policy á á ᢠ᫠á áá°ááᦠUNIQUE á áµááá á ááµ á¨áµ á á¨input áá ᥠá á² á á áµ á á á á á (á áá ááá« áµá
á°áµ)ᣠFIRST ᨠá á ᨠá á á ᪠᫠áá á á áµ á³ á ᣠPRIORITY á ᨠᵠá priority á á áµ á³ á ᣠCOLLECT_SUM/MIN/MAX/COUNT áááá ᨠᰠá á á± á¨áµ á á½ á á« á á á á á ᢠᨠᰠ᳠᳠ᰠpolicy ááá« á áá áµ á á á á á á á áµ á á áá á¨á¥ á á á á á ᮠᨠᰠ᳠᳠ᰠáá¤áµ á ᰠᣠá ᢠá áá á¨á¡á á evaluate á¥á simulate á á áµ á¹ á¢","á¨á¥á
task á á«áµ-á°á á á á Ḡá ᦠá°á«á°áá ááááªá« Claim á ᵠᨠá á áá áµá£ á¥á ᨠᰠá á° á° task á¥á» Complete á áá«á á« á á á ᢠdue field á¥á escalated status á á á á ᨠᱠâ á« á á á¥á ᨠᰠᣠᣠᱠtasks á dashboard áá SLA Compliance metric á á á á© á (á á¨ááá´ >= 95%ᣠá¢á« >= 80%ᣠá¨áá« á á³ á½ áá)á¢","dashboard á á«áµ-á°á á á á á á (summary á ᨠ30 ᰠᨠá ᱠᣠcharts á á° á á á ááµ áá) á¥á á á° á ᨠdefinition á¥á áá á ᣠ᫠ᵠáá½áá (1h/6h/24h/7d/30d)ᢠRecent Issues á¥áá á¥á Top Bottlenecks ááá ᨠá ᨠὠá instances á á¥á á á£á ᨠá á ᩠ᨠá á° áµ nodes á á á ᥠá áµ á¥áá² á« á á á« á á á á¢","Check the dead letter queue regularly: instances there do not escalate on their own and pile up silently."]},"hostedPages":{"title":"Hosted Payment Pages","summary":"ááá á¨4pay.online \\"hosted\\" á¨ááá« forms á á« á á
á« á â á 4pay.online link ᨠá ᨠá ᱠᣠá¨á«áµáá á áááá½ á³ á« á á á á á á¨ááá« áá¾á½á¢ á¥áá
brandingᣠáááᣠthemeᣠᨠform fields áµá¥áµá¥á á
á°á á°á¨á°áᣠá¥á á á á³ á á á« webhook á« á á á á ᤠá¥á«áá³áá± áá
á ᨠᵠá á
áµ (org) áá ᨠᰠ᫠᫠á ááá¢","whenToUse"
1:"á¨á«á± checkout á á á á á¨á°áá á áµáá
áµ á¨ááá« form á á á« á á á á°á«á°áá½á¢ config á á ᥠ᫠á ᣠáááá fields á« á á
á« á ᣠ᫠ᵠá á â á¥á á merchant á ᰠᥠᨠá á½ á ᨠá á á á¨ááá« áá½ link á« á á á ᢠááá á Settings ááµá¥ ááᢠá¨á«ááµ ááᥠá¥áá
á á á á á á (á payment widget á á á ᣠá ᣠá¨PCI ááµáááµ)ᢠá ááµ áµáá
áµ á áá«á³ configs á á ᨠá áá½áá â ááá³á á á° á á« á© á á á« á á½ ááá ááááὠᨠᰠá á© á á¾ á½ á¢","concepts":["Slug â ᨠconfig á áá áá© ááá« (ááá³á checkout-ru)ᣠᨠá á¹ public link áááᤠá á á á« áá á á á á á á¥á ᨠá á« á á á á á ᵠᰠ᫠ᨠá á (field á° á á á á )","á¨Config statuses â draft / published á¥á ᨠᰠá ᨠinactive flagᤠᨠá á¹ link ᨠá á° á« á á á³ á° á config ᨠᰠᰠá access_token áá á¥á» áá","Branding â Logo URL (https)ᣠPrimary colorᣠá¥á Accent color á #RRGGBB á
áá¸áµá¤ accent color á form áá á¨\\"Pay\\" á áá«á á á á á á á ᣠá á« á ","Form (form_config) â Variant (default / compact / minimal / express)ᣠTheme (light / dark)ᣠInput style (underline / regular / monolith)ᣠá¥á Locale (áááᣠááá³á en)ᤠá¨ááá« form áááá ááá á« á á á á ","Form fields â á¶áµáµ ᨠá á á á© áá¥áá½á¦ EmailᣠBilling addressᣠá¥á Footerᤠá ᥠ᫠á á³ á á± á³ á á áµ á á ᨠ᫠á (show_email / show_billing_address / show_footer) á¥á á
á°á á°á¨á°á á á á / á á³ á½ á ᵠᶠὠá á ᨠ᫠á ᤠá¨á«ááµ fields á° áµ á° á« á á á áááá á á³ á« á ","Webhook â á á á³ á á á« Webhook URL (https) á¥á Webhook secret (HMAC secret)ᤠsecret write-only áá â á á á ᣠá ááá áá á á á¹ á á á á á áµ á á¥á á« áµ á á á¡ á á á á form ááµá¥ á á á³ á á ","Versions á¥á á á° á â ᥠ᫠á á³ á á± á á° á ᨠversion á ᥠá (v1ᣠv2 ...) á« á³ áµ á á¥á ᨠlink public access_token á ᫠ὠᨠᨠá á« á ᤠᨠversion á³áªá á \\"Versions\\" modal ááµá¥ áá° á á° á version ᨠá á á áµ á½áá³ áá á á á á "],"example":"á°áá£áᦠá á© á² á« á merchant á á© á² á ᣠá dark theme á¨ááá« áá½ á á á á ᵠᢠ1) admin ᨠᵠá á
á± á organization_id (UUID) á« áµ á ᣠá \\"Open\\" á á á
á« á° á á á (á á° á á á á°á áá org á á«áµ-á°á á á á á )ᢠ2) \\"New config\\" á á á
á« á° á á á ᣠSlug = checkout-ruᣠDescription = \\"Payment for RF\\"ᣠLogo URLᣠPrimary color = #004D40ᣠAccent color = #FFB300ᣠLocale = ruᣠVariant = compactᣠTheme = darkᣠInput style = regular á« á á á á ᢠ3) á \\"Form fields\\" á¥áá ááµá¥ Billing address á á« á á á ᣠEmail á¥á Footer á á á á á ᣠá¥á Email á á á á á áµ áµ áá° á á á ᪠᫠᫠á á á³ á
á³ á â á á á á« á á \\"Preview\\" áá²á«áá áá¤á±á á« á³ á« á ᢠ4) Webhook URL á¥á Webhook secret á á« á á á á ᢠ5) \\"Save\\" -> config á draft status á á á á« á ᢠ6) á á á á á© ááµá¥ \\"Publish\\" á á á
á« á° á á á â v1 badge á á³ á« á á¥á á¥áá° {host}/api/v1/{org_id}/hosted_page_configs/checkout-ru/render?token=... á« á public link á á á á« á ᣠá á
á icon á° á ᵠᶠá merchant á ᰠᥠáá½ááᢠááá¶á£ á¨config á ᵠᰠ᫠ᨠ᫠á¥á áá \\"Publish\\" v2 á¥á á á²áµ link token á« á á á« á á¢","tips":["slug ᨠᰠá á ᨠá á á á á ᨠá á áá½áá â á á ᵠᰠ᫠ᨠá áá field á° á á á á ᤠáµá ᨠpublic link ááá áµ á á á á áµ á áµ á á á« áµ á¡ ","public link ᨠá ᳠ᨠá ᨠá á° á á á á á¥á» ááᦠconfig á draft status ᥠᵠ᫠á ááá access_token ᥠᵠᨠá á á ᣠlink á á á³ á á á¥á á á¹ á á ᨠá áµ á ᢠᥠ᫠á á³ á á± á á²áµ á á° á token á ᫠ὠᨠᨠá á« á â á á® á á link á áµ á« áµ á« á á á ᣠá¥á ᨠᰠá á á á á¥áá°áá á merchant á á° á áµ á áá áµ (token TTL á á ᣠ᪠24 á° á áµ / 86400 ᰠᨠá áµ áá)","Webhook secret á ááµ áá á á ᣠá á¥áá°áá á á á³ á á (write-onlyᣠpassword field)ᢠá á ᵠᰠ᫠ᨠá áá áááá á£á¶ áá â á£á¶ ᨠᰠᰠá ᣠá áµááµá ᨠᰠá á á á secret á á á° á« á ᤠsecret á á á á ᨠá á á²áµ á¥á´áµ á«áµáá¡","á¨á«ááµ fields (numberᣠexpiryᣠCVV) á¥áá
á á á á á© á á¥á áááá á form áá á á â á payment widget á PCI DSS áá
1µáááµ áá á¨áµ á á á ᣠá ᢠá builder ááµá¥ EmailᣠBilling addressᣠá¥á Footer á¥á» á á á á ","á form áá á« á á \\"Notes\\" field \\"not saved\\" ᰠᥠá á° á á á á· á á¥á read-only áá â á á á á áá¨á á áµ á á á á áµ ","á¨version á á á áµ config á ᨠᰠá ᨠá version snapshot ááᥠá á á á á á ᨠá á á á á¥á stylingᣠfieldsᣠá á á á ᣠá¥á branding á á á á á³ á ᣠááá áá webhook secret á á á (á snapshot ááµá¥ á¨áá)ᢠᨠá á á áµ á á á á áµááá ᨠá á config á á¥áá°áá á« áµ á "]},"copilot":{"title":"4pay Copilot settings â operator AI assistant","summary":"This section configures the AI backend for 4pay Copilot, the built-in Admin Area operator assistant. Each organization connects its own AI backend (provider and model); the access key is stored in HashiCorp Vault and cannot be read back through the interface.","whenToUse":"Open this section to connect or switch the organization's AI provider, pick a model, check the configuration status, and manage the assistant's access. An organization administrator sets this up before operators start using Copilot.","concepts":["AI backend â the provider and model serving Copilot requests. An organization uses its own backend (BYO-key) or the platform one.","Vault â the secrets store (HashiCorp Vault): the provider API key is written there and never read back through the UI.","Consent â the organization's consent to AI data processing; it defines which data the assistant may access (scope-based, GDPR Art. 7).","Kill switch â emergency shutdown of Copilot (global, per region, per feature, or per organization) during an incident.","Sanitization â masking sensitive data (PAN, CVV, secrets) before sending it to the AI.","Explainability is an AI-regulation requirement: the assistant must show which data and which rule produced its conclusion. An answer without a basis cannot serve as justification for an operator's action.","Proactive insights are built from the same data the assistant is permitted to see under consent. Narrowing consent narrows the insights â that is a direct consequence of the setting, not a fault.","The assistant does not act silently: anything that changes data requires operator confirmation. The confirmation is the human decision; the assistant's proposal is material for it.","A chat session is bounded by the same consent as everything else: the assistant sees exactly what it is permitted to, which explains why answers differ between organisations."],"example":"Task: connect the organization's AI backend. You open \\"4pay Copilot settings\\", choose the backend type and model, paste the API key (it goes to Vault and is no longer shown), and save â the configuration status changes to \\"configured\\". Operators then see the Copilot widget and can ask about transactions and operations within the granted permissions; proactive insights and confirm-required actions follow the same scope.","tips":["The API key is shown only on entry â it is not read back from Vault; to rotate it, enter a new one.","Check consent and scope before enabling: the assistant only sees data that consent was granted for.","The kill switch disables Copilot immediately â use it if you suspect a leak or incorrect answers.","Record a decision taken on the assistant's prompt the same way as one taken independently: responsibility for it stays with the operator.","Do not confirm an assistant's action without reading what it proposes to change: confirmation moves responsibility to you."]},"goLive":{"title":"Go-live: moving a contour to production","summary":"The wizard moves a setup certified on test into production: it certifies the mandatory scenarios, dry-runs routing, creates the production terminal as a copy of the test one, and drives a staged rollout by cascade weight. This is the last mile of every integration â before the wizard it was done by copying configuration by hand.","whenToUse"
1:"Every time an integration certified on test has to take production traffic: a new payment provider, an entire partner contour, a freshly connected national rail. The wizard does not replace configuration â it carries over what is already configured and certified, so it runs after the processing setup wizard or the rail wizard.","concepts":["Subject of the move â a provider channel or a partner contour. The sequence is identical; a contour is moved channel by channel, starting with the primary one.","Certification â the mandatory scenario set on test: success, decline, timeout, refund, partial capture and reconciliation against the provider report. An unchecked scenario blocks the next step: these are exactly the branches that break in production.","Dry run â POST /routing/simulate against production rules. It shows the decision tree and answers whether the channel is reachable at all, before anything is created.","Move diff â the explicit list of what differs between the production and the test terminal: environment, cascade weight and the active flag. Everything else is copied as is, because the gap between test and prod is the root cause of failures in this operation.","Rollout stage â a traffic share expressed as terminal weight in the cascade, plus an observation window. The channel enters production with a share rather than a switch: at 10% a failure affects a tenth of the operations, not all of them.","Rollback thresholds â the maximum decline rate and latency, defined before the rollout starts. Disabling a terminal takes effect immediately and traffic moves to the remaining channels of the cascade."],"example":"A new acquirer is connected and its test terminal accepts payments. You walk the wizard: tick the six certification scenarios, run the simulation â the decision tree shows the channel is reachable for RUB and the payment type. You create the production terminal: the diff shows env test -> prod, weight 100 -> 10, active false. The first stage is 10% for a day, then 30%, 60%, 100%. A day later the quality report shows a 1.8% decline rate against a 5% threshold â you raise the stage.","tips":["Thresholds invented during an incident are always laxer than the ones you need. Set them at the rollout step, while there is no pressure.","Do not move several channels of the same partner at once: when declines rise it becomes impossible to tell which channel is at fault.","The immediate shutdown button lives in the wizard on the rollback step â you do not have to hunt for the terminal in the general list mid-incident.","Unless «activate now» is ticked, the wizard creates the production terminal disabled: convenient for preparing everything ahead and switching it on in an agreed window."]},"railOnboarding":{"title":"National payment rail onboarding","summary":"The wizard configures a connection to a national payment system: NSPK and cross-border SBP, the digital ruble, Aani and UAEFTS in the UAE, ACSS PAD in Canada. Six rails share one setup path and differ only in reference data, so there is a single wizard with a rail catalogue.","whenToUse":"When entering a national market where settlement runs through the local payment system rather than card schemes. A pilot in Russia depends on SBP and NSPK, in the UAE on Aani and UAEFTS, in Canada on ACSS PAD â so the wizard usually runs before the first production operation on that market.","concepts":["Participation mode â direct membership in the payment system or operating through a sponsor bank. It determines whose participant identifiers go into the connection details.","Admission pre-check â membership, participant identifiers and licences. A rail will not work until the participant is registered with its operator, and no configuration in the console substitutes for that.","Adapter â the platform module implementing a specific rail protocol. Its name is shown in the summary: you will need it when investigating an incident with support.","Operating window â the hours the rail works. It matters for RTGS systems: outside the window operations are queued rather than declined.","Payer mandate â the consent for direct debit. Required only by rails such as ACSS PAD; for the others the mandate step is not shown at all.","The rail terminal is created disabled in the test environment: a trial operation comes before production traffic, and the move to production is a separate wizard."],"example":"You are launching acceptance in Canada. You pick ACSS PAD and the sponsor-bank mode. You confirm admission: Payments Canada membership through the sponsor, compliance with the H1 rules, participant identifier. You fill in adapter details, partner, CAD, the acceptance direction, limits and window. The wizard shows the mandate step and states plainly that the platform has no mandate registry: storage and revocation happen outside the console. The terminal is created â next come the trial operation and the go-live wizard.","tips":["Keep keys and certificates in Vault and pass them by reference rather than by value in the credentials field.","Every rail lists what stays outside automation â read it before you start: ISO 8583 certification, the EAEU corridor and the mandate registry are there.","Run the wizard once per rail
1: admissions, windows and currencies differ, and a shared setup would lead to wrong connection details."]},"waqfEndowment":{"title":"Waqf endowment creation","summary":"The wizard establishes a waqf â a perpetual charitable endowment whose principal is locked forever and where only income is distributed to beneficiaries. Before the wizard the core object of this product line could not be created from the console at all.","whenToUse":"When creating a new endowment, cash or property. An existing fund â accrued income, distributions, pausing â is managed on the waqf page rather than here: the wizard establishes but does not edit.","concepts":["Principal â the transferred assets. Locked in perpetuity and never spent: only accrued income is distributed.","Beneficiaries and shares â addresses and purpose (charity, education, health, general). Shares must total exactly 100%: the fund does not retain an undistributed remainder.","Guardian (mutawalli) â the only party who can pause distribution. A fund without a guardian cannot be paused.","Minor units â the principal is sent to the backend as an integer number of minor currency units, so the wizard shows the conversion before you confirm.","Irreversibility â creation cannot be undone technically or contractually. That is why the last step asks you to retype the amount: it is the only guard against establishing the wrong fund."],"example":"A founder contributes AED 1,000,000 for scholarships. You choose a cash waqf, enter the amount and currency â the wizard shows 100,000,000 minor units. You add two beneficiaries: an education fund at 60% and a charity at 40%, totalling 100%. You name a guardian, tick the signed deed and the Shariah opinion. On confirmation you retype the amount â the fund is created and the contract deployed.","tips":["Verify beneficiary addresses before confirming: income sent to a wrong address is as irreversible as the creation itself.","If beneficiaries may have to change, plan the replacement procedure in advance â it is governed by the deed, not by platform settings.","With no income a distribution simply does not run: the cycle is skipped and the principal is untouched."]},"zoltDashboard":{"title":"ZolT â the gold token","summary":"The section shows the state of the ZolT stack: tokens issued, vault holdings, backing ratio, contract state and the redemption queue. ZolT is a backed token â every unit is backed by gold held by a custodian, so a gap between issuance and holdings is a reputational problem rather than a technical one.","whenToUse":"For daily backing supervision, quarterly reserve attestation, redemption request handling and any operation on roles and vaults. The initial stack launch is a separate ZolT go-live wizard.","concepts":["Backing ratio â confirmed vault holdings divided by tokens issued. Below one it means unbacked issuance.","Vault â a legally documented storage location at a custodian, with a capacity limit and insurance cover. Reserves are counted across vaults included in the calculation.","Contract roles â issuance, audit, pause, blacklist, upgrade and oracle. Each role is granted to its own address; combining them on one address defeats the separation of duties.","Emergency pause â halting all contract operations. Used on suspicion of key compromise or of an issuance error.","Blacklist â blocking an address on sanctions or AML grounds. Funds of a blocked address stay inaccessible until the block is explicitly lifted."],"example":"Morning check: 12,500 tokens issued, confirmed holdings across three vaults total 12,500 units, ratio 1.00. A week after a new delivery is accepted the ratio reads 1.02 â excess backing, issuance trails delivery. That is fine; the opposite is the alarming case.","tips":["Contract write operations require the administrator key and on-chain confirmation: schedule them into an agreed window rather than doing them ad hoc.","An emergency pause halts redemptions too â warn holders in advance if the pause is planned.","Investigate a backing gap before signing the attestation report: a published discrepancy cannot be withdrawn."]},"workflowDecisions":{"title":"Decision tables and rules (DMN)","summary":"The section maintains decision tables: condition sets by which the platform makes automatic decisions â approve an application, send an operation to manual review, pick a tariff. Here they are created, published, simulated on historical data and compared across versions in an experiment.","whenToUse"
1:"When a decision has to follow transparent rules rather than code: application scoring, manual-review thresholds, case routing. Also before changing a live rule â to simulate the new version before publishing.","concepts":["Decision table â a set of «conditions -> result» rows. Row order matters: the first matching row wins unless the table is set to collect all matches.","Publication â promoting a table version to live. Until published a table is a draft and affects no decisions.","Simulation â running a table over historical data with no consequences. It shows how the new version would have decided cases that already happened.","Experiment â comparing the live version with a candidate on live traffic. Part of the real operations is decided by the candidate, so consequences occur in reality, not in a model.","Decision audit â the log of rules that fired per case. The primary tool for answering «why were we declined».","A connector call from a decision table reaches out to an external service at the moment of decision. Its unavailability stops the decision, so the call must have a timeout and a fallback."],"example":"You raise the manual-review threshold from 100,000 to 150,000. You create a new table version and simulate it over last month's operations: manual reviews drop from 12% to 7%, and none of the confirmed fraud operations would have been auto-approved. You publish the version.","tips":["Always simulate before publishing: a table not tested against history is a hypothesis, not a rule.","An experiment runs on live operations: define stop conditions and a deadline up front, otherwise a bad candidate keeps running until somebody notices.","Keep rules few and coarse: a hundred small overlapping rows make system behaviour unpredictable for the operators themselves.","Define the fallback in advance: without one, an unavailable external service turns into a halt on every decision of that type."]},"dclsMintBurn":{"title":"dCLS â fiat token issuance and redemption","summary":"The section performs minting and burning of fiat tokens by dCLS network participants. Issuance is backed by reserves on the minter account: a token appears in the network only after a confirmed reserve top-up, and burning releases the reserve back.","whenToUse":"When topping up the working token balance ahead of a settlement window and when withdrawing funds from the network. Operations are initiated by the minter and confirmed by multisig, so the section is used together with the signing officers.","concepts":["Reserve â the fiat backing of issued tokens. The reserve-to-issuance ratio is checked before confirmation: issuing beyond the reserve is not allowed.","Multisig â issuance executes only after the required number of signatures. This is not a formality: a single signature would mean one employee can create money.","Confirmation queue â the state between initiation and execution. Until signatures are collected the operation affects neither the reserve nor the network.","Burn â the reverse operation: tokens are destroyed and the reserve is released. An amount burned by mistake can only be restored by a new issuance, that is by a new set of signatures."],"example":"Ahead of a settlement window the minter issues 5,000,000 token units against a topped-up reserve. The operation enters the queue, the second and third signers confirm it, tokens appear in the network. After the window the unused balance is burned and the reserve returns to the account.","tips":["Check the reserve-to-issuance ratio before initiating: an operation rejected at signing is time lost before the window.","Do not leave signature collection to the settlement window itself: signers may be unavailable and the window will not wait.","Issuance and burning are irreversible: «burn the excess, then issue it back» costs two signature rounds, not one action."]},"dclsSettlementOps":{"title":"dCLS â settlement operations and failure handling","summary":"The section drives network settlement windows: running the current window, retrying failed batches and handling a failed settlement. Settlement is payment-versus-payment: either both sides receive their currencies or nobody does.","whenToUse"
1:"For a routine window run, for retrying a batch once the cause of failure is fixed, and for handling a failed settlement when positions have to be returned to participants.","concepts":["Settlement window â the interval over which mutual obligations are netted. The netting ratio shows how much less funding was needed compared with settling every trade separately.","Batch â a set of instructions executed as one unit. Partial execution is not allowed: it would leave one side without its counter-payment.","Failed settlement â a window where not all obligations are covered. It requires an unwind: positions return to participants and obligations move to the next window.","Unwind â the position return operation. It is irreversible and affects every participant of the window, so it is performed only once the cause is known: insufficient collateral at a specific participant, or an execution failure."],"example":"A window closes as a failed settlement: one participant lacked collateral on the USD/AED pair. You check its position and limit, unwind the window â positions return to everyone and obligations move on. The participant tops up collateral and the next window settles normally.","tips":["Record the cause before unwinding: an unwind without a known cause repeats in the next window.","Retrying a batch makes sense only after the cause is fixed â otherwise it reproduces the same failure and wastes the window.","Warn the window participants about an unwind: for them these are cancelled settlements, not a technical detail."]},"cooperatives":{"title":"Cooperatives","summary":"The section maintains cooperatives: membership, share contributions, votes and the lifecycle from creation to dissolution. A cooperative decides by general meeting, so the console records decisions already taken rather than replacing them.","whenToUse":"When registering a new cooperative, admitting or excluding members, running votes, and at dissolution. Cooperative products are configured by a separate wizard.","concepts":["Share â a member's contribution granting a vote and a claim in distributions. Its return on exit and at dissolution follows the charter.","Vote â a general meeting decision recorded with quorum and ballots. Operations requiring a meeting decision rely on its minutes.","Dissolution â terminating the cooperative. Irreversible and affecting every member's share, so it runs strictly after obligations are settled.","Order of settlement at dissolution â third-party obligations first, then return of shares, then distribution of the remainder."],"example":"The general meeting resolved to dissolve. You check outstanding member loans, open deposits and open votes, record the minutes with quorum, settle in order, produce the closing document pack and terminate the cooperative.","tips":["Dissolving with open obligations leaves members' funds locked â the pre-check is mandatory, not advisory.","Enter the meeting date and quorum from the minutes: a mismatch makes the decision contestable.","A single member leaving is not a dissolution: returning their share per the charter is enough."]},"rpaBot":{"title":"RPA â automating routine operations","summary":"An RPA bot performs repetitive actions in external systems on the operator's behalf: download a register from a bank portal, export a provider report, fill in a form. The section registers the bot, sets its schedule and the credentials it works under.","whenToUse":"When an operation is done by hand every day, has no API, and its content does not change between runs. If the system has an API, an integration is more reliable than a robot depending on someone else's markup.","concepts":["Bot â a scripted sequence of actions in an external system, bound to an account. Credentials live in Vault, not in the script.","Schedule â when the bot runs. Align it with the external system's availability: bank portals are often down for maintenance at night.","Monitoring â the run log with outcomes. A silent bot is more dangerous than a crashed one: the work is not done and nobody knows.","Limits â a robot reproduces human actions and breaks when the external interface changes. That is expected behaviour, not a platform fault."],"example":"An acquirer register is downloaded manually every morning. You register a bot: account, download steps, schedule at 06:30 on weekdays, target folder. From there the file is picked up by automatic reconciliation â the operator only handles discrepancies.","t
1ips":["Give the bot its own account: a shared one makes it impossible to tell who performed an action.","Check the behaviour when the external system is unavailable â retry or skip â before putting the bot on a schedule.","A robot is a stopgap until an API exists, not a permanent architecture; deploy it so that replacing it with an integration does not require reworking the process."]},"tradeFinanceInstrument":{"title":"Letter of credit issuance","summary":"The wizard drives a credit through draft, approval and issuance. Under UCP 600 an issued letter of credit is an irrevocable bank undertaking: it cannot be withdrawn unilaterally, only amended by agreement of the parties, and the applicant's margin cover is already blocked by then.","whenToUse":"When the bank undertakes payment on a foreign-trade deal. Amendments to an issued instrument and document examination are handled on the trade finance page.","concepts":["Credit type â the form of the undertaking. Confirmed adds a second bank's undertaking, transferable allows assigning the claim, back-to-back is opened against the first credit, revolving serves a series of similar shipments.","Document list â what the bank pays against. A mismatch between deal terms and the document list means the bank must pay on a formally compliant presentation, even if the goods are wrong.","Margin cover â the share of the amount blocked at the applicant. Blocking happens on accounts outside the wizard: here the arrangement is recorded for documents and pre-approval review.","Dual control â approval by a separate officer before issuance. The backend rejects issuing an unapproved credit, so the step cannot be bypassed.","The amount goes in minor units as an integer: the platform accepts neither fractional values nor zero."],"example":"A UAE importer buys equipment in China for USD 250,000. You open an irrevocable credit: applicant AE, beneficiary CN, expiry in 90 days, Incoterms CIF, loading and discharge ports. Documents: commercial invoice, bill of lading, packing list, certificate of origin. Cover 100% on the blocking account. After the compliance check you create the draft, a colleague approves, you issue â the instrument goes under presentation-deadline control.","tips":["Reconcile the document list against delivery terms before approval: after issuance the list changes only by amendment agreed with the beneficiary.","Bank guarantees and documentary collection are not part of this wizard â they live in other platform resources.","The platform stores no dedicated fields for advising and confirming banks: record them in the deal documents."]},"merchantOffboarding":{"title":"Merchant offboarding","summary":"The wizard closes a merchant account in the order that keeps money and obligations consistent: stop acceptance first, then close the refund window, settle finally, and only then revoke access and close.","whenToUse":"When ending the relationship with a merchant at the client's request, on a contract breach, or by a compliance decision. The operation is rare, so the operator meets it as if for the first time â the wizard holds the order instead of memory.","concepts":["Step order is the substance of the process. Revoking access before the final settlement leaves the client's money locked in the system and invites a regulatory claim over holding client funds.","Orphaned organisations â organisations left without an owner once the client is deleted. The pre-check lists them by name: they will be archived along with the client.","Refund window â the period during which refunds are still possible on completed operations. While it is open, part of the balance is retained.","Blocking items â conditions that make closure unavailable: open disputes, live terminals, active subscriptions, an unfinished settlement. The wizard does not let you bypass them.","Typing the client name is the final guard: closure is irreversible, and a returning client goes through onboarding again."],"example":"A client leaves by its own decision. You pick the reason and stop date, run the pre-check â two organisations will be left without an owner. You disable terminals, cancel subscriptions, wait for the refund window to close, run the final reconciliation and pay out the balance. You export the operations register for the client, notify the partner and providers, type the client name and close the account.","tips":["Do not close an account with an open dispute: it may still require a debit, and there will be nothing left to debit.","An uncancelled subscription keeps charging after closure â the most common complaint after offboarding.","The data retention period is set by the client's jurisdiction: deleting early breaches regulatory requirements."]},"payoutCorridorLaunch":{"title":"Payout corridor launch","summary":"The wizard configures an outbound direction: payout terminal, beneficiary requisite format per country, FX rules, limits and the manual review threshold. An outbound transfer has no chargeback â a requisite error means
1stuck funds and a manual investigation with the receiving bank.","whenToUse":"When opening a new payout direction â a new country, currency or credit method. The rail provides the channel and the corridor is configured on top of it: rail wizard first, this one second.","concepts":["Requisite format â account number rules and mandatory fields for the destination country. The wizard verifies them on a control account before the corridor is published.","Rate source and rate age â a stale rate is more dangerous than a missing one: the payout leaves at a price the market no longer has. The maximum age defines when an operation must request a fresh rate.","Tolerance â how far the actual rate may diverge from the expected one before the operation stops.","Manual review threshold â the amount above which a payout goes to a human decision. Sanctions screening of the beneficiary runs regardless of the threshold.","A corridor is a single-direction setup. The platform has no batch payout register: operations go through the API one by one."],"example":"You open payouts to India in INR by bank transfer. You set partner, provider and wallet, then verify a control account â 9 to 18 digits plus an IFSC code. The rate comes from the platform reference with a 50 basis point markup, 1% tolerance and a 15-minute maximum age. You set per-transaction limits and a daily volume, manual review above 500,000. You configure register export and reconciliation, create the corridor and run a trial payout.","tips":["Verify the requisite format on a real control account rather than an invented one: receiving banks treat spaces and case differently.","The corridor is created disabled in the test environment: a trial payout must pass before production traffic.","Register export and reconciliation are configured by their own wizards â do not create a third copy of the same rules inside the corridor."]},"distributionRun":{"title":"Investor income distribution","summary":"The wizard computes the distribution register and runs the payout batch for a campaign. The batch executes in bulk: an error means money sent to the wrong people in the wrong amounts, and it comes back only at the recipients' goodwill.","whenToUse":"When distributing income for a reporting period on an investment campaign. Distribution schedules and per-recipient statuses live on the PFP dashboard.","concepts":["The distributable base is computed outside the platform and entered as a final figure: the model has no source for it.","Shares are computed against the included recipients' total, not the original hundred per cent: otherwise an excluded recipient would quietly move their part into the remainder.","Deductions â platform fee, recognised expenses, organiser share and reserve â reduce the base before shares are computed.","The platform does not withhold tax at source: the distribution model has no such field. The wizard computes it for reference; withholding happens outside the platform.","The rounding remainder deliberately stays with the campaign: shares are whole minor units and fractions are not smeared across recipients."],"example":"A campaign closes the quarter with 4,000,000 minor units of income. Platform fee 200 basis points, expenses 50,000, organiser share 500 basis points. That leaves 3,670,000 to distribute. Twelve investors hold 3% to 22%; one is excluded on a sanctions flag, and their share is redistributed among the included rather than dropped into the remainder. The register balances, the approver signs off, the batch goes out.","tips":["Check the payout account balance before the run: a batch that stops midway is unpicked recipient by recipient.","A minimum payout threshold avoids transfers that cost more than they carry.","The reference tax figure is for reconciliation with accounting â do not mistake it for a completed withholding."]},"rbfContract":{"title":"Revenue-based financing contract","summary":"The wizard handles an RBF contract in two modes â new agreement and revision of an active one â and models the repayment schedule before activation. Activation fixes both parties' obligations and starts collecting the revenue share.","whenToUse"
1:"When funding against a share of future revenue and when changing the terms of a contract already being performed. Recorded revenue is managed on the contracts page.","concepts":["Revenue share and repayment multiple together define the economics: the multiple sets the repayment cap, the share sets how fast it accrues.","Repayment cap is the funded amount times the multiple. The contract closes on reaching the cap, not on the calendar.","An open-ended tail is when the cap is not reached within the maximum term at the given revenue. The wizard shows it during modelling so the terms are fixed before signing, not after.","A minimum payment protects against the contract never amortising when revenue falls; it also makes a bad month harder on the client.","Money fields are sent as strings: the controller declares them as strings and a JSON number returns 422."],"example":"Funding of 500,000 at an 8% revenue share and a 1.4 multiple gives a 700,000 cap. At a baseline revenue of 90,000 a month the share yields 7,200, so the cap needs 97 months against a 36-month limit â modelling shows a tail in all three scenarios. Raising the share to 20% and adding a minimum payment closes the base case in 39 months and the optimistic one in 30.","tips":["Look at the pessimistic scenario: it shows what the contract becomes in a bad year.","A revision changes the terms of a contract being performed: attach an old-versus-new comparison to the parties' consent.","Activation cannot be undone unilaterally â before it the contract is a draft and edits freely."]},"decisionExperiment":{"title":"Decision rule experiment","summary":"The wizard runs an A/B of the live decision rule version against a candidate on live traffic â with guardrails that must be present: a control group, a traffic share below one hundred per cent, an automatic stop condition and a deadline.","whenToUse":"When historical simulation is not enough and versions must be compared on real operations. Results and termination live on the experiments page.","concepts":["The control group is the live version. Without it there is nothing to compare against: you get a description of the candidate, not a comparison.","Traffic share is the portion of operations decided by the candidate. One hundred per cent means no control, so the wizard rejects it.","Excluded segments keep large amounts and sensitive clients out: there the cost of a wrong decision outweighs any statistical gain.","The stop condition and the deadline are set before launch: thresholds invented during an incident are always laxer than the ones needed.","An experiment has no rollback â only termination. A declined payment or missed fraud has already happened by the time you stop it."],"example":"The candidate relaxes the manual review threshold. You set 10% traffic, exclude operations above 500,000 and clients with open disputes, pick manual-review share as the metric with fraud share not worsening, auto-stop on fraud rising by 0.5 percentage points, and a 14-day deadline. The dry run over last month shows decisions diverging in 4% of cases. You launch.","tips":["Set a cap on affected operations: a deadline in days does not limit volume during a peak week.","Name the observer explicitly â an ownerless experiment runs until someone happens to notice.","After the experiment, roll the candidate out through the go-live wizard rather than switching it to one hundred per cent."]},"cooperativeDissolution":{"title":"Cooperative dissolution","summary":"The wizard terminates a cooperative by resolution of the general meeting: it records the basis, checks open obligations, sets the settlement order and performs the irreversible termination.","whenToUse":"After the general meeting resolves to dissolve. The console records a decision already made â how it is made is governed by the charter and the law.","concepts":["The basis is the meeting minutes with date and quorum. A mismatch with the minutes makes the decision contestable.","The pre-check covers the main risk: terminating with outstanding loans, open deposits or live votes leaves members' funds locked.","Settlement order: third-party obligations first, then return of members' shares, then distribution of the remainder.","The claims deadline is the window in which creditors and members raise claims before final closure.","Termination is irreversible: restoring a cooperative means creating a new one, with a new membership and new shares."],"example":"The meeting resolved to dissolve at a 78% quorum, minutes no. 14. You check: no outstanding loans, two deposits closed early, no open votes, balances reconciled. You set the settlement order and a 60-day claims deadline, notify members and the regulator, produce the closing pack. You type the cooperative name and terminate it.","tips":["A single member leaving is not a dissolution: returning their share under the charter is enough.","Do not terminate before the claims deadline expires: a late claim is then handled outside the platform.","Produce the closing document pack before termination â afterwards the cooperative's data set changes."]},"feeRecalculation":{"title":"Bulk fee recalculation","summary":"The wizard runs a recalculation of fees across a selection of operations. The run rewrites history at once and has no rollback: it applies today's configuration to a past period.","whenToUse"
1:"When a rate or channel mapping has been corrected and historical fees must match the current configuration. Results are checked against operations and the ledger.","concepts":["The run takes the current terminal fees and partner tariffs: if configuration changed after the operations, the historical picture is replaced by the current one.","A filter is mandatory: the backend rejects an empty body â the only thing standing between the operator and recalculating everything.","The response has no body: you cannot learn afterwards how many operations were affected, so the scope is estimated beforehand from the operations list with the same filter.","There is no rollback. A mistake is corrected only by another run with a different configuration â that is, one more pass over the same selection."],"example":"A partner rate was corrected retroactively from 2.2% to 1.9% effective 1 July. You bring terminal fees to the right values, set the selection: partner, 1â31 July, type payment, status success. You open operations with the same filter â 4,812 records â and carry the number into the estimate. You type the confirmation, run it, then reconcile the fees in the ledger.","tips":["Never run with a single filter dimension: the selection will almost certainly be wider than intended.","Bound the period on both sides â otherwise the run touches the organisation's entire history.","Check channel fees before launching: the wizard does not verify them for you, it only reminds you."]},"currencyPair":{"title":"Currency pair setup","summary":"The wizard adds a currency to the reference and opens a rate with a validity window. Mistakes here are not visible immediately: overlapping windows make conversion depend on which rate was picked, and a currency's minor unit is set irreversibly.","whenToUse":"When opening a new conversion direction. Markups and multi-currency settings live on the currencies page.","concepts":["The minor unit (decimal places) determines how every amount in the currency reads. Changing it on a currency with history rewrites the meaning of that history.","A rate validity window is the period it applies to. Overlapping windows on one pair is the costliest error: the divergence surfaces at reconciliation, not at conversion.","Nominals set the scale: a rate 'per 100 units' and 'per 1 unit' are different records, and confusing them gives a result off by two orders of magnitude.","A rate without an end date applies indefinitely: the next rate must be closed manually or it will overlap the previous one.","The markup lives separately from the rate and applies at organisation, partner or terminal level."],"example":"You open the USD/KZT pair. KZT is already in the reference, so you only add the rate: source â platform reference, nominals 1:1, value 512.40, effective from 1 September with no end, environment test. You set a 50 basis point markup at organisation level on the currencies page. After a trial conversion you move the rate to prod.","tips":["Verify the minor unit against ISO 4217 before creating a currency: JPY and KRW have no fractional part, while BHD and KWD have three decimals.","Close the previous rate before opening a new one if the new one starts inside its window.","Set the pair up in test first: a nominal mistake shows on the very first trial conversion."]},"tokenRegistry":{"title":"Token registry entry","summary":"The token registry defines how the platform reads every amount for a contract. A scale error is not rejected by the form and is invisible on screen â it surfaces as an amount that is off by a factor of ten, a thousand or a trillion.","whenToUse":"When adding a new token â fiat, gold, stablecoin or wrapped asset â to the platform registry.","concepts":["Scale (decimals) is how many decimal places the contract counts in. It is not formatting but the way all of the token's amounts are read: 18 against 6 is a millionfold difference.","The currency code must exist in the reference before the token is recorded, otherwise the registry points at nothing and you find out on the first operation.","Before writing, the platform asks the contract for decimals() itself. A mismatch is a 422 and nothing is written. Silence from the chain means the record
1is accepted with a 'scale unverified' mark.","The 'scale unverified' mark is informational: it does not block operations with the token. The background audit clears it as soon as the chain answers.","Settlement eligibility and the active flag are different things: an inactive token is not tracked by the node at all, while a non-eligible one simply does not take part in settlement."],"example":"You add a fiat rouble token on the test network. RUB already exists in the reference, the symbol is RUB_T, type 'fiat', numeric code 643, contract address from the factory issue, scale 18. The wizard shows that the same on-chain record reads as 1,000 at scale 18 and as a billion at scale 9. You verify the value against the contract itself rather than the issue description, and write the record.","tips":["Check the scale against the contract, not the token documentation: on upgradeable contracts it changes with the implementation and leaves no trace in storage.","The chain identifier must match the network: 1 for mainnet, 11155111 for the test network. The wizard flags a mismatch before writing.","Add the token on the test network first: a scale mistake there costs only time."]},"shopDescriptor":{"title":"Payment descriptor by shop","summary":"An aggregator runs payments for hundreds of shops through one terminal, and by default the buyer sees a technical operation identifier on the statement. The wizard replaces it with a meaningful description chosen by shop.","whenToUse":"When onboarding a sub-merchant, when 'I don't recognise this charge' tickets grow, and when the provider a shop's payments run through changes.","concepts":["The order is mandatory: without a category description the shop cannot be created at all â the form returns an error.","The category-mode marker goes into the terminal's default description field. Nothing in the interface mentions it â the field is plain text with no hint.","Ordinary text in place of the marker gives the same descriptor on every payment of the terminal. This is the most common misconfiguration and it shows on the very first transaction.","The shop is matched from specific to general: first the record for that provider, then the record with no qualifiers, and only then any record with that shop identifier.","A shop's own description overrides its category description. If it is empty, the category one is used."],"example":"A partner runs payments for 240 shops through one terminal. You add a 'gaming' category description in Russian and English, then a shop record for shop_1042 qualified by provider, then enable description substitution on the terminal and enter the marker. Instead of a technical identifier the buyer sees 'Game account top-up'. A text change applies from the next transaction â neither the partner nor the terminal is touched.","tips":["Always add a description in the local language: without it the buyer sees text in another one.","A provider qualifier makes sense when the same shop runs through different channels with different descriptor requirements.","The shop's active flag does not affect the description â it rejects payments only when shop-identifier validation is enabled on the terminal."]},"localEkyc":{"title":"Local customer identification","summary":"The wizard assembles the configuration for verifying a customer through a state registry: provider, identification level, requested data, subject consent and mismatch rules. The Russian, UAE and Indonesian profiles differ in reference data; the steps are the same.","whenToUse":"When opening a new market where customer identification relies on a state registry.","concepts":["The account level determines what the customer is allowed to do. A simplified account does not confirm the data and is not enough for identification under anti-money-laundering rules.","The scope of consent is examined by supervisors as closely as the identification itself: do not request data beyond what the chosen level needs.","The rule for a mismatch between the result and the questionnaire matters more than the check itself: mismatches generate most of the review workload.","The agreement with the registry operator is signed outside the console â it is a legal precondition of access, not a technical setting.","The provider configuration is not yet written into the platform: no configuration endpoint exists for any of the three. The wizard records the decision; results are observed in KYC cases."],"example":"You enable identification through the Russian state portal. Level â standard account; data â full name, date of birth, insurance number and tax number;
1 consent valid for 12 months; recheck after a year. A mismatch with the questionnaire goes to manual review, as does a provider refusal. Registering the system with the ministry and obtaining the certificate happen before connection.","tips":["A fallback provider must give the same identification level, or some customers will pass through a weaker check.","Plan the recheck: without it the data ages with nothing to trigger an update.","The existing UAE and Indonesia wizards remain â they are the same profiles opened straight at the right jurisdiction."]},"partnerProgram":{"title":"Agent and reseller onboarding","summary":"The wizard adds the partner layer on top of ordinary onboarding: partnership type, a reward model on top of tariff fees, the referral loop and the programme's boundaries.","whenToUse":"When onboarding a partner who brings in customers or manages them directly.","concepts":["A share of turnover and a share of the platform fee differ by orders of magnitude: the same number means entirely different money. The base must match the wording of the contract.","A reseller needs the partner portal: without it they cannot manage their own customers.","The referral bonus goes to the referred customer, not the partner: the partner's reward is a separate model.","The partner-branded environment is configured by a separate wizard: this one creates the partner and the terms, then hands over.","The partner's data visibility and rights come from their role in the partner portal after onboarding."],"example":"You onboard an agent who brings customers in two countries. Type â agent, partner portal enabled, reward â 20% of the platform fee on the referred customers' operations, payout threshold 10,000, monthly frequency, markets RU and KZ. A referral code is also created with a bonus for the referred customer, valid until the end of the year.","tips":["The partner password must be at least 12 characters: a shorter one is rejected by the platform.","The rate and partnership type can be changed later on the partner card â the programme need not be set up again.","The tariff plan and individual rates live in billing: the wizard records the reward model on top of them, not instead of them."]},"supplyChainAdvance":{"title":"Supply chain advance","summary":"The full path of a supplier financing request: the parties, amount and term, fee and repayment schedule, dual control and disbursement. Before this wizard the mechanism was unreachable from the console.","whenToUse":"When financing a supplier against a future delivery.","concepts":["Disbursement is irreversible: the money is with the counterparty and recovery goes through collection. That is why the cost is computed before the decision, not after.","Dual control means more than one approval is required, and approvals are counted against different accounts.","The last instalment takes the rounding remainder â otherwise the debt never closes to the last unit and the request stays open.","The advance as a share of the invoice estimate shows the coverage: an advance above ninety per cent of the estimate is not secured against short delivery.","Creating the request disburses nothing: it records the terms and opens approval."],"example":"A supplier asks for a 500,000 advance against a delivery six weeks out. The invoice estimate is 700,000, so the advance is 71%. The fee is 2% and there are three instalments: two of 170,000 and a final one that takes the rounding remainder. After the request is created, two staff members approve it, then the operator checks the details and confirms disbursement by typing it out.","tips":["If no supplier is specified, the request is recorded against the current session's partner â when acting on someone else's behalf, always fill the field.","The number of instalments is capped at thirty-six: the platform will not accept more.","Check the payout account balance before confirming: a failure at this step leaves the request approved but undisbursed."]},"musharaka":{"title":"Partnership contract","summary":"The wizard creates a partnership contract, including the diminishing form where the partner's share is bought out on a schedule. Computing shares over time is what makes a step-by-step pass worthwhile at all.","whenToUse"
1:"When concluding a partnership contract, especially a diminishing one where shares change from payment to payment.","concepts":["Profit is shared as the parties agree; loss follows the contribution shares strictly. A contract that splits loss otherwise does not meet the requirements.","In the diminishing form the partner's share is bought out on a schedule: the last payment takes the remainder, or rounding leaves a micro-share and the contract never closes.","Each side's contribution is fixed in minor units: the share is computed from it, not from the appraised value of the subject.","The buyout schedule is computed by month and is not revised retroactively: changed terms mean a new contract."],"example":"The bank contributes 8,000,000 and the client 2,000,000, giving shares of 80 and 20. Profit is split 60/40 in the client's favour; loss strictly 80/20. The form is diminishing over 24 months: the bank's share is bought out in equal payments and the last one takes the rounding remainder. The wizard shows how the shares change month by month before the contract is created.","tips":["The difference between profit and loss sharing is highlighted deliberately: it is not an error but the essence of the contract.","Enter amounts in major units â the wizard converts them to minor units itself.","Choose the diminishing form only when a buyout is genuinely intended: for a standing partnership it complicates accounting for nothing."]},"equityPartnership":{"title":"Equity partnership contract","summary":"The wizard registers a joint venture contract, including the diminishing form where the organisation's share is bought out on a schedule. Working out how the shares change over time is what makes a step-by-step pass worthwhile.","whenToUse":"When entering a contract where the parties pool contributions into a common venture and share the outcome: a simple partnership, a share in a cooperative project, joint ownership of the contract's subject.","concepts":["Profit is split by agreement, loss strictly by contribution shares. This is not a formality: a contract shielding one party from losses at the other's expense stops being equity participation.","In the diminishing form the organisation's share is bought out on a schedule: the last payment takes the remainder, otherwise rounding leaves a micro-share and the contract never closes.","Each contribution is entered in the contract currency; it reaches the ledger in minor units, and the wizard does the conversion.","The buyout schedule is calculated per month and is not revised retroactively: changed terms mean a new contract."],"example":"The cooperative contributes 8,000,000, the participant 2,000,000 â shares of 80 and 20. Profit is split 60/40 in the participant's favour, loss strictly 80/20. Diminishing form over 24 months: the cooperative's share is bought out in equal payments, the last taking the rounding remainder.","tips":["The difference between profit and loss splits is highlighted on purpose: it is the substance of the contract, not a mistake.","Enter amounts in major units â the wizard converts them to minor units itself.","Currency is picked from the platform reference: a code outside it means the amount's scale is unknown.","Choose the diminishing form only when a buyout is actually agreed: for a permanent partnership it complicates accounting for nothing."]},"rosca":{"title":"Rotating savings group","summary":"A circle of contributions and payouts whose parameters are tightly coupled: the number of seats also sets the number of cycles, and the cycle length determines the length of the whole round.","whenToUse":"When setting up a new rotating savings group in a community.","concepts":["The product offers neither editing nor cancelling an existing group â only admitting members, contributions and running cycles.","The number of seats equals the number of cycles: each member receives a payout exactly once per round.","The payout per cycle equals the contribution times the number of members: it cannot be set separately.","How the recipient is determined is chosen at creation: ordinary queue, priority, or a form without a reward component."],"example":"Twelve members, a contribution of 10,000 a month. The wizard immediately shows the consequences: twelve cycles, a round lasting a year, a payout of 120,000 per cycle. With eleven members the round shortens by a month and the payout drops by 10,000 â none of which can be recomputed after creation.","tips":["Check how the parameters interlock on the preview step: after creation there is nothing to edit.","Agree the composition of the circle beforehand â adding a member changes both the round length and the payout.","A mistake is fixed only by creating a new group, so the preview here is not a formality."]},"budgetCycle":{"title":"Community budget cycle","summary":"Opening a cycle requires consistent records in two entities: the community rules, which change between cycles, and the cycle itself, whose fields are immutable once open.","whenToUse"
1:"When opening a new community budget cycle â once per period.","concepts":["Two levels of configuration: the voting model and quorum belong to the community rules, while the budget, currency and voting deadline belong to the cycle.","The cycle's fields are immutable once open: the product offers neither editing nor cancellation.","Community rules change between cycles â changing them mid-vote means changing the terms in flight.","Quorum is set before opening: if it is unreachable with the current membership, the vote never completes."],"example":"A community of 340 members opens an annual cycle with a budget of 3,000,000. The voting model is one vote per member with a 25% quorum, and voting runs for four weeks. The wizard checks that the quorum is reachable and separates the fields by level: quorum and model go to the community rules, budget and deadline to the cycle record.","tips":["Allow headroom in the voting deadline: an open cycle cannot be extended.","A quorum above a third is usually unreachable in a large community â check turnout in past cycles.","Edit the community rules before opening the cycle, not after."]},"dataSubjectRequests":{"title":"Data subject requests","summary":"The queue of requests a person makes about their personal data: access, correction, erasure, restriction of processing, portability, objection. The response deadline runs from the date of the request and is thirty days under most regimes, so the queue is worked by deadline, not by convenience.","whenToUse":"When a request about personal data arrives, and after notifying customers of a data breach â the volume of requests rises sharply afterwards.","concepts":["Request states: pending, verified, in progress, rejected, fulfilled. Identity verification happens outside the platform; the console only records its outcome by moving the request to 'verified'.","The request type is shown on the card and dictates the action: access and portability need an export, correction needs an edit, erasure needs irreversible deleti
1on.","Rejection requires a stated reason â without one the action does not go through. This is not interface ceremony: the justification for a refusal is the first thing a supervisor asks for.","An erasure request is confirmed in a separate step with a warning: deleted data cannot be restored, and the duty to retain certain records under anti-money-laundering law still stands.","The roles of controller and processor differ. The request is addressed to whoever determines the purposes of processing â usually the platform's client, not the platform."],"example":"A Canadian customer asks for a copy of their data. The request appears as 'pending'. Their identity is confirmed outside the console and the state moves to 'verified'. The type is access, so an export is prepared and handed over, after which the request is closed as fulfilled. The whole thing has thirty days from the request date; the pending filter shows what is approaching the deadline.","tips":["Work the queue by deadline: a late response is itself a breach, even where the refusal was substantively correct.","State the reason for refusal by reference to a rule, not in generalities â this text goes to the requester and to the supervisor.","Breach notification and answering requests are different processes with different deadlines. The first is configured by the privacy wizard, the second is worked here."]},"regulatoryReports":{"title":"Regulatory reporting","summary":"The register of supervisory reports: generation for a period, progression through states, and file export. Central bank periodic forms, tax returns and sector reports for every jurisdiction the organisation operates in run from here.","whenToUse":"At every reporting date, and during a supervisory inspection â the evidence pack is assembled from here and from the compliance section.","concepts":["Report states: draft, awaiting approval, approved, submitted, rejected. The summary shows how many forms sit in each state, which is how you see what will miss its deadline.","Submission is recorded in the console while the filing itself goes through the regulator's own channel. The console keeps the record and the file; it is not wired directly into supervisory intake systems.","The list of report types is defined per country. A jurisdiction with no form set of its own answers with an explicit error pointing at the region list â previously it silently fell back to Bank of Russia forms, and the substitution showed up only inside the file.","A report is built from ledger data for the chosen period. Accounting entries made after generation do not appear in the finished file â the form has to be rebuilt.","The filing schedule and delivery channel are set by the separate regulatory reporting wizard, not on this page.","A currency-zone country reports on the zone's forms: a bank in Senegal files BCEAO forms, one in Cameroon files COBAC forms."],"example":"A monthly central bank form is due on the tenth. On the generation page you pick region, report type and period; the form appears in the register as a draft. The person responsible checks the contents on the card, approves it, exports the file and files it through the regulator's channel, then marks it submitted. A report rejected by the regulator returns to the register in that state and is rebuilt.","tips":["Build the form after the period is closed in accounting: built earlier, it diverges from the ledger by the amount of late entries.","Approval and submission are deliberately separate steps: a human accountable for reporting sits between them.","A dry run before the first mandatory date is cheaper than handling a rejection: field sets differ noticeably between countries' forms."]},"bankTransfers":{"title":"Transfers and alternative channels","summary":"This section covers everything that is not a card payment: bank transfers, mobile money, remittances and hawala, national instant payment schemes and QR schemes. Each transfer shows its number, provider, direction and state.","whenToUse":"When you need to make or investigate a transfer over a non-card channel, and when connecting a national payment scheme in a new country.","concepts":["The direction â inbound or outbound â determines both the set of details and how you investigate: for an inbou
1nd payment the sender is not always known.","Each national channel lives as its own adapter with its own detail requirements. The shared screen presents them uniformly, but the mandatory fields differ by channel.","Remittances and hawala are subject to stricter sender and recipient identification than card operations: the threshold for full verification is set by the jurisdiction.","QR schemes differ in who presents the code: with a merchant-presented code the buyer pays from their app, with a customer-presented code the merchant scans it. That determines where an error arises.","The state shown in the console reflects what the channel reported. Finality of credit is determined by the national scheme's rules, not by a label on screen."],"example":"A customer sends money to a neighbouring country over a national instant payment scheme. The transfer appears in the list with its number and provider, direction outbound. The state shows the channel accepted it; final credit is confirmed by the statement. Where amounts diverge, the investigation runs from the transfer number to the ledger entry.","tips":["Connecting the channel itself is done by the national payment rail wizard; this page only uses channels that are already connected.","For inbound transfers, agree in advance which field you match the payment to a customer on: it differs by channel.","Check the channel's limits and operating window before sending: a transfer outside the window is not rejected immediately, it hangs until the system opens."]},"transactionsRegistry":{"title":"Operations","summary":"A single register of every operation type: acquiring, payouts, refunds, captures and voids. This is where you investigate an individual payment, create a refund manually and pull the provider request history when debugging an integration.","whenToUse":"When investigating a query about a specific payment, when refunding, during a cardholder dispute and when debugging a partner integration.","concepts":["A refund is a separate operation linked to the original payment, not a change to it. Both records are visible in the register, and their amounts differ.","Partial refunds are allowed repeatedly until the refunded total reaches the payment amount. Anything beyond that is rejected by the platform.","Disputes and chargebacks come from the cardholder's bank; the operator does not create them. What is handled in the console is the consequence: preparing evidence and accounting for the deduction.","An escrow payment differs in when it is released: funds are taken but not passed to the recipient until a condition is met. In the register it looks like an ordinary operation in a particular state.","The provider request history for an operation is the core debugging material: it shows exactly what went to the channel and what came back."],"example":"A buyer asks for a refund. The original payment is found by operation identifier, its state and remaining refundable amount are checked. A refund is created for the required amount and appears as a separate record. It does not clear through the provider instantly â the state updates as the channel responds, and telling the buyer the money has arrived before the final state is premature.","tips":["Before refunding, check whether a dispute is running on the operation: a simultaneous refund and chargeback debit the merchant twice.","Bulk payouts are not assembled in the interface â they run through the API; what you see here is the outcome of each individual payout.","When debugging, look first at what was sent to the provider and only then for a fault on your side: the divergence is usually in the request field set."]},"subscriptions":{"title":"Subscriptions","summary":"The register of recurring charges: state, interval, amount, current period. Subscriptions are paused, resumed and cancelled here â the same actions the buyer has in their own portal.","whenToUse":"When a buyer queries a charge, when investigating failed attempts, and when checking mutual obligations between organisations for a settlement period.","concepts":["States: active, paused, cancelled, completed, and past due â when the latest charge attempt failed.","Pause and cancel differ in reversibility: a paused subscription can be resumed, a cancelled one cannot â a new one has to be created.","A past-due subscription enter
1s the retry sequence. The retry schedule and the reminder texts sent to the buyer come from settings, they are not chosen per subscription.","Card expiry is the most common cause of a stop: the platform cannot refresh the credentials itself, the update is requested from the payer.","A subscription is created from a completed successful payment: that payment supplies the stored payment method the charges will run against."],"example":"A buyer reports a failed charge. The subscription is found under the past-due filter: the attempt was declined and the card has expired. The operator pauses the subscription and asks the buyer to update their payment method in the portal, then resumes it. The period history shows which month was missed.","tips":["Cancel only on an explicit request: it cannot be resumed, and a new subscription restarts the periods and disrupts billing.","Check the current period before cancelling: cancelling mid-period does not return what was already charged â that is a separate refund.","Operator actions on a buyer's subscription are recorded in the audit log: in a dispute that is the only proof of who stopped it."]},"fiuReport":{"title":"Financial intelligence report","summary":"Building a report to the financial intelligence unit: suspicious transaction, mandatory-control transaction, cross-border transfer. Report types, filing deadlines and mandatory field sets differ by jurisdiction.","whenToUse":"When an operation has been judged suspicious after review, and when a mandatory-control threshold is reached.","concepts":["The report type is chosen first and drives every field that follows: subject details, operation details and the grounds for suspicion differ between types.","The deadline runs not from the date of the operation but from the moment suspicion was established. Being late is a breach in its own right, separate from the substance.","The subject â natural or legal person â is stated explicitly: the required identification details depend on it.","A suspicion report must not be disclosed to the customer. The prohibition on tipping off continues after filing.","Building the report in the console and filing it into the regulator's intake are different steps. The console assembles and stores the report; each jurisdiction has its own filing channel."],"example":"Working the suspicious operations queue produces a conclusion: a series of transfers is being structured below the mandatory-control threshold. A suspicious transaction report is built: region and customer are selected, subject details and a description of the grounds are filled in. The report is saved and filed through the regulator's channel within the jurisdiction's deadline.","tips":["Describe the grounds with facts â amounts, dates, sequence â not with judgements: the report is read by someone who has never seen your customer.","Check the deadline for the specific report type: within one jurisdiction deadlines range from a few days to a month across types.","Record the filing decision in the customer's KYC case: the case-to-report link is what a supervisory inspection asks for."]},"taskList":{"title":"Task queue","summary":"The shared queue of work that needs a person: manual review of suspicious operations, human steps in workflows, acceptance and correction of extracted document data. Each task has a type, a team, a deadline and a state.","whenToUse":"Daily â this is the main working screen for an operator handling reviews.","concepts":["Task states: pending, in progress, completed, escalated. A task is claimed by an explicit action â until it is claimed, nobody owns it.","The deadline comes from the process definition, not from the operator. An overdue task escalates automatically.","A claimed task belongs to whoever claimed it: to hand it over you must return it to the queue, not simply stop w
1orking on it.","Completion requires confirmation and, for some types, a decision â accept or reject. The decision goes back into the process and determines its next step.","The queue summary shows how many tasks are waiting, claimed, completed and overdue, the average wait and deadline performance by team."],"example":"The queue holds a manual review task for a high-risk operation. The operator claims it, opens the linked operation, checks the customer's details and payment history and completes the task with a decision. If the decision is to reject, the process moves the operation to declined; if to accept, the payment continues its normal path. A task not claimed in time escalates.","tips":["Claim a task only when you are ready to work it: a claimed and abandoned task never escalates, because formally it is in progress.","Check the summary at the start of a shift: it shows where the queue is building before the overdue items appear.","For document tasks, correcting the data and deciding on the document are separate steps: fix the extraction first, then accept."]},"kycCases":{"title":"Customer verification cases","summary":"The queue of identity and integrity checks: customer card, uploaded documents, automated screening results and the operator's decision with a risk level.","whenToUse":"During customer onboarding, when an automated check fires, and when a scheduled re-verification falls due.","concepts":["Case states: under review, documents required, in verification, approved, rejected, expired. An expired case means re-verification is due, not that the customer was refused.","Approval carries a risk level â low, medium, high. The level drives both the depth of ongoing monitoring and the next review date.","Rejection requires a comment: it stays in the case and explains the decision when a supervisor asks a year later.","Automated screening results against state registries are inputs, not decisions. A registry mismatch is exactly what lands with the operator here.","The enhanced due diligence flag means the standard document set is not enough: source of funds and ownership structure are required."],"example":"A corporate customer submits documents. Automated screening against the state registry returns a name mismatch. The case moves to 'documents required' and the customer supplies an extract. The operator checks it, approves the case at medium risk, and the platform sets the next review date from that level.","tips":["Set the risk level on the merits, not by default: it governs re-verification frequency, and an understated level turns into missed monitoring.","A registry mismatch does not always mean forgery â more often the registry itself is out of date. Request a document rather than refusing outright.","Connecting a particular verification source is configured by the local identification wizard; only the result is visible here."]},"auditLog":{"title":"Audit log","summary":"The chronology of actions in the console: who did what and when. Filter by operation identifier, request identifier, action name and period, with search inside nested data.","whenToUse":"When investigating an incident, when preparing evidence for an inspection, and whenever you need to establish who performed an action.","concepts":["An audit record is created once and never changes. It has no states â it is a fact, not a task.","The log spans actions across every part of the platform: banking operations, administrator logins, access keys, crypto operations, rules-engine decisions, cross-organisation access.","Search inside nested data is the main instrument: it finds events that have no dedicated field, such as the launch of a maintenance procedure.","The log records actions taken in the console, not data changes as such. An edit made outside the interface will not appear in it.","For a payment card security standard assessment the log is the evidence base: it answers 'who changed what'."],"example":"You need to establish who disabled a live terminal overnight. Filtering by period and action name finds the record: the actor, the time, the request address and the parameters. From there the request identifier pulls the neighbouring actions of the same session â which reconstructs the whole sequence rather than a single event.","tips":["Start with the peri
1od and narrow from there: searching by action name alone is useless at production volume.","The request identifier ties together the actions of one session â it assembles a chronology faster than timestamps do.","Prepare an inspector's export for a specific period: nobody reads the whole log, and surplus data invites questions."]},"appStatus":{"title":"Application status","summary":"Publishing service status to customers, with a change history. States: operational, maintenance, disabled, unavailable. The record's history is the incident chronology.","whenToUse":"During an outage, during planned maintenance, and when preparing an information-security incident report for a regulator.","concepts":["A status record is public: users will read the details, so write them for users rather than for internal correspondence.","Every status change and every edit to the details lands in the history. Detection time, containment time and recovery time are taken from it.","Planned maintenance and unavailability are deliberately distinct: the first is expected and announced in advance, the second is an incident.","Closing an incident means returning the status to operational. The record is not deleted: the history remains the proof of timings.","An incident report to a regulator rests on this chronology rather than on email threads: in several jurisdictions the notification deadline is counted in hours."],"example":"A payment provider stops responding. A record is opened: the affected application, status 'unavailable', details for users. As the investigation proceeds the details are refined â each edit lands in the history. After recovery the status returns to operational and the details record the regulator's case number and the date the final report was filed.","tips":["Publish the record immediately, before you understand the cause: detection time matters more than wording, and it cannot be backdated.","Write for the customer: 'card payments unavailable' is clearer than the name of an internal service.","Do not delete records of closed incidents â the change history is your proof that deadlines were met."]},"instantPayments":{"title":"Instant payments","summary":"Transfers over national instant payment schemes: sending by recipient identifier, watching the state, and cancelling an operation while it has not yet gone to the national system.","whenToUse":"When a transfer must settle in real time over a scheme where the recipient is addressed by an identifier rather than bank details.","concepts":["The recipient is addressed by an identifier â a phone number, a tax number or a scheme alias. Matching the identifier to a name is done by the scheme, not by the platform.","Transfer states: processing, executed, rejected, cancelled, expired. An expired transfer is one the scheme did not accept within its window.","Cancellation is possible only before the operation is handed to the national system. After that, recovery is a request to the recipient, not a cancellation.","An executed instant transfer is final: unlike a card payment, these schemes have no chargeback mechanism.","The set of supported rails is defined by the platform. A missing scheme means the channel is not connected, not that the transfer is impossible in principle."],"example":"A customer sends funds to a phone number. The rail is chosen, then the amount, recipient identifier and name, the debit account and the payment reference. The transfer goes to processing and the scheme confirms execution within seconds. Had the recipient been wrong, recovery would depend entirely on their goodwill â which is why the name is checked before sending.","tips":["Compare the name returned by the scheme with the one the payer gave: that is the last point where the mistake can still be stopped.","Remember the scheme's operating window: not every national system runs around the clock.","Fill the payment reference meaningfully â in instant schemes it is often all the recipient sees."]},"interbank":{"title":"Interbank operations","summary":"The interbank message flow and the correspondent network: inbound and outbound message queues, balances on 'ours with them' and 'theirs with us' accounts, and daily reconciliation against the correspondent's statement.","whenToUse"
1:"Before an outbound international payment, when investigating statement differences, and for daily coverage control.","concepts":["An 'ours with them' account holds your funds at the correspondent bank; 'theirs with us' holds theirs at you. They must not be confused: only the first provides cover for an outbound payment.","A message and a transfer are different things. A sent message is an instruction, not a completed credit.","Reconciliation shows four figures: total items, matched, 'ours not theirs', 'theirs not ours', and the resulting difference. The two middle categories are what you investigate.","'Ours not theirs' usually means a payment in transit; 'theirs not ours' means a fee or a credit you do not know about yet.","Daily reconciliation is mandatory: a difference found a week later takes far longer to resolve â the chain of intermediaries has had time to grow."],"example":"Before a large payment the balance on the 'ours with them' account in the payment currency is checked â cover is sufficient. The message goes out and its state is visible in the outbound queue. Next day reconciliation shows an 'ours not theirs' item: the payment is still with an intermediary bank. A day later the item clears and the difference returns to zero.","tips":["Check cover before sending, not after a rejection: returning an unexecuted payment costs fees and time.","Investigate differences on the day they appear â that is cheaper than any other cadence.","Record a difference explained by an intermediary's fee: without that it returns as new in the next reconciliation."]},"marketplaceModules":{"title":"Module catalogue","summary":"The catalogue of platform capability modules: activation, trial period, paid subscription and deactivation. Each card shows the module's dependencies and the jurisdictions it requires.","whenToUse":"When a section you need is missing from the console, and when planning platform spend.","concepts":["The activate button stays disabled until dependencies are met: a module built on another does not work without it, and there is no way around that.","A trial opens access immediately; the card shows a trial marker and the days remaining. When it ends, access closes unless a subscription has been taken out.","The subscription currency is chosen from those the biller has a tariff in â an arbitrary currency cannot be entered.","Deactivation takes effect immediately: the module's sections close at once, with no grace period.","Required jurisdictions are not advisory: without the country pack activated, the routes for the corresponding procedures stay closed."],"example":"An operator needs the participatory finance section but it is missing from the menu. The module is found in the catalogue; its card shows the dependency satisfied and no jurisdictions required. A trial is started and the section appears immediately. A few days before it ends a subscription is taken out: currency chosen from those available, plus a period.","tips":["Warn the team before deactivating: sections close at that moment and any unfinished work in them is interrupted.","Read the whole dependency chain â deactivating a base module breaks everything standing on it.","A trial makes a convenient rehearsal: activate the module and run your scenario end to end before paying."]},"crowdfundingCampaigns":{"title":"Crowdfunding campaigns","summary":"The campaign register and campaign cards: raise parameters, state, investor composition and a live monitoring view of how the raise is going.","whenToUse":"When launching a campaign, when watching a raise approach its deadline, and when investigating a failed escrow release.","concepts":["Contributions sit in the campaign's escrow wallet until the raise closes. Until then they do not belong to the organiser.","Reaching the goal, refunding a shortfall and closing the campaign are executed by the platform under the rules set when the campaign was created, not by hand.","The monitoring view refreshes automatically: the time of the last refresh is shown beside the heading, which is how you know the data is live.","A failed escrow release is retried by the platform up to three times before it is handed to an operator. The investigation runs from the ledger entries to the campaign state.","Raise parameters do not change after launch: goal, contribution limits and refund rules are set once by the campaign launch wizard."],"example":"A campaign has three days left and 82% of its goal. The monitoring view shows the trend of recent days. The raise closes short â the platform refunds contributions under the campaign's rules. The ledger shows the movement out of the escrow wallet and the campaign state moves to closed-undersubscribed.","tips":["Look for campaigns nearing their deadline early: with a day left there is nothing left to influence.","When investigating an escrow release, compare the ledger against the campaign state â the divergence between them is the thing to explain.","Check investor composition before the raise closes: an incomplete investor verification surfaces precisely at release."]},"crowdfundingInvestors":{"title":"Investors and their positions","summary":"The register of positions filtered by campaign, investor type, verification state and cooling-off period. The card shows the amount invested, distributions received and the result on the position.","whenToUse"
1:"When accrediting an investor, when reconciling a performance statement, and when handling a query about a payout.","concepts":["Investor type sets the permitted investment limits: they are tighter for a non-qualified participant, and that is a jurisdictional requirement rather than a platform setting.","The cooling-off period is the window in which an investor may withdraw without giving reasons. While it runs, the funds are not finally raised.","Investor verification state is separate from position state: an incomplete verification does not cancel the position but does block distributions.","The result on a position splits into realised and unrealised: the first has been paid out, the second is a carrying estimate that can still move.","The investor statement is built from the same data, so a divergence between statement and card means an error in the underlying data, not in the statement."],"example":"An investor disputes a figure in their statement. Their position is found by filter and the card is checked for amount invested and distributions received. The divergence turns out to be a distribution falling after the statement date. The period boundary is explained to the investor and the statement is not reissued.","tips":["Check accreditation before taking funds, not after: refunding an over-limit amount is processed as a withdrawal and skews the campaign's numbers.","Distinguish realised from unrealised result when talking to an investor â most queries come from conflating the two.","Factor the cooling-off period into escrow release planning: closing a raise while it is still running is premature."]},"rbfContracts":{"title":"Revenue-based financing","summary":"Contracts where repayment is tied to a share of revenue rather than a calendar: the list with progress toward the repayment cap, the terms card, recording a revenue report for a period, and termination.","whenToUse":"When deciding on an application, monthly when recording the revenue report, and when working arrears.","concepts":["The repayment cap is the ceiling after which the contract is closed regardless of remaining term. Progress toward it is visible in the list.","The instalment is computed from actual revenue for the period, so the borrower's report is a required input. Without it the calculation stays pending.","If the report is not filed by the due date, a minimum instalment is charged. A late report is still accepted, and the system charges the difference up to the actual instalment itself.","Termination is available only for an active contract or one in arrears â a closed contract cannot be terminated.","Arrears more often arise from unreported revenue than from a lack of funds: check the report first, the debt second."],"example":"By the fifth no revenue report has been filed and the calculation waits. By the fifteenth the platform charges the minimum instalment and progress toward the cap moves by that amount. On the twentieth the borrower files a late report: the actual instalment is higher than the minimum, and the difference is charged automatically. The contract stays active.","tips":["Record a late report even if the minimum instalment has already been charged: without it the period's calculation stays unreconciled.","Read progress toward the cap in the list â it is more honest than the term: a contract can close before its calendar end.","Move to termination only after checking the reports: unreported revenue explains most arrears."]},"programmablePayments":{"title":"Programmable payments","summary":"Payments executed when a condition is met: collective approval by a set number of signers, an external data source firing, a date arriving. The list shows condition type, state and amount.","whenToUse":"When a payment must not leave immediately: it needs several people's approval or a verifiable event.","concepts":["A collective approval condition is defined by two numbers: how many approvals are needed and from which list of signers. The list cannot be changed after creation.","An approval is counted against a specific signer: one person cannot fill the quorum with several actions.","The external source's parameters live inside the condition itself â address, path to the value, threshold, comparison operator and polling interval. There is no separate registry of sources on the platform.","An error in the value-extraction rule c
1auses a false trigger and an irreversible transfer. It can only be caught by a trial poll before the payment is set up.","Until the condition is met the payment is not an instruction: the funds stay in the payer's account."],"example":"A contractor payment is set up requiring approval by two of four directors. It appears in the list as pending with an approval counter beside it. The first director opens the card, checks the details and approves. After the second approval the condition is satisfied and the payment leaves.","tips":["Check the signer list before creating: it cannot be changed afterwards, and a payment with an unreachable quorum hangs forever.","For an external-source condition, run a trial poll: the value-extraction rule is where mistakes concentrate.","Do not use collective approval where ordinary sign-off suffices: a quorum slows the payment by however long people take to react."]},"notifications":{"title":"Notifications","summary":"The log of push notifications sent to devices: title and body, partner, time, delivery flag and the list of recipient devices. Manual sending starts from here too.","whenToUse":"When investigating an 'I never got a notification' query and when sending a message to a partner's users by hand.","concepts":["There are two addressing modes: specific devices or a subscription topic. The second delivers to everyone subscribed â the recipient set is not fixed in advance.","The delivery flag means the notification was accepted by the delivery service, not that the user saw it. Reads are not visible to the platform.","The list of recipient devices is stored in the log record: it shows whether the addressee was among the recipients at all.","Push notifications and operation callbacks are different mechanisms. The first addresses a person, the second a partner's system.","A sent notification cannot be recalled: it is already on the device."],"example":"A partner's user reports missing a payment notification. The notification is found in the log by time and partner: the delivery flag is set, but the user's device is not among the recipients. So this is not a delivery problem â the device is not registered, and the investigation moves to the app side.","tips":["Check the addressing before a manual send: a subscription topic can reach far more people than you assume.","Write as though it will be read on a lock screen â only the first few words are visible there.","A device missing from the recipient list is the answer: the cause is registration, not the platform."]},"openBankingTpp":{"title":"Open banking providers","summary":"The register of third-party providers admitted to data and payments: registration, suspension and revocation of admission, and each provider's state.","whenToUse":"When admitting a new provider, on suspicion of access abuse, and when a provider's authorisation lapses.","concepts":["Suspension and revocation differ in reversibility: a suspended provider can be restored, a revoked one must register again from scratch.","Provider admission and customer consent are different layers. A provider with valid admission gets no data from a customer who has not consented.","A provider's authority rests on its regulatory licence. Expiry of that licence is grounds for revocation, and watching for it is the operator's duty.","Customer consent is limited by term and by data scope: it cannot be widened without the customer.","Connecting to an external bank as a data consumer is the mirror-image task and is configured by a separate wizard."],"example":"A provider aggregating statements applies for admission. Its licence and declared data scope are checked and it is registered. Six months later notice arrives that the regulator has suspended its licence â admission is suspended the same day and access stops, while customer consents remain in force in case it is restored.","tips":["Set yourself a reminder for the provider's licence expiry: the platform does not track regulators.","On suspicion of abuse, suspend rather than revoke: revocation forces full re-registration, and the investigation may clear them.","Check customer consents separately from provider admission â they are different objects with different terms."]},"workflowDefinitions":{"title":"Process definitions","summary":"The register of workflow definitions: creation, versioning and visual editing of the diagram. A definition sets what steps a process consists of and which of them need a person.","whenToUse"
1:"When automating a repeating procedure and when changing a process that is already running.","concepts":["A definition version is bound to running instances: changing the definition does not change processes already under way â they live out their version.","Publishing a new version and applying it are different things: new instances take the new version, existing ones stay on the old.","Steps needing a person land in the shared task queue. That step's deadline is set here, in the definition, not by the operator handling it.","The visual editor and the textual definition are two views of the same thing: an edit in one shows up in the other.","A process without an explicit terminating step never completes: instances accumulate unclosed."],"example":"The new-customer check process gains an approval step for amounts above a threshold. The edit is made in the diagram and published as a new version. Customers already in checking finish on the old diagram, new ones follow the updated one. A week later approval steps appear in the task queue â which shows the new version is in use.","tips":["Test the change on a trial instance: a fault in the diagram surfaces only at the step the process has not reached yet.","Do not delete the old version while instances are running on it: they will have nowhere to go.","Set step deadlines realistically: too short produces a stream of escalations, too long quietly stretches the process."]},"blacklists":{"title":"Blocklists","summary":"Lists that decline an operation automatically: cards, devices, addresses, recipient details. Entries are checked at the point the operation decision is made.","whenToUse":"After confirmed fraud, at the request of an investigation, and when handling a complaint about a mistaken block.","concepts":["A blocklist entry takes effect immediately and on every subsequent operation â there is no deferred application.","The check runs before the operation is approved, so being on a list looks to the customer like a payment declined without explanation.","A list matches on an exact value. A fraudster who changes one digit no longer matches â that is what velocity rules and the risk profile are for.","An entry with no expiry lasts indefinitely: a list that is never reviewed accumulates entries that stopped being relevant long ago.","A mistaken entry hits a legitimate customer silently â the complaint comes to you, not to the platform."],"example":"Fraud on a particular card is confirmed. Its details are added to the list and the next payment attempt is declined. A month later a customer complains after being reissued a card with the same number: the entry is reviewed, found no longer relevant and removed.","tips":["Record a reason and a date when adding: in six months nobody will remember why the entry is there.","Review the lists: indefinite entries are the main source of complaints about unexplained declines.","Against adaptive fraud a list is powerless â velocity rules and the risk profile do that work."]},"billing":{"title":"Organisation billing","summary":"The monthly billing cycle: what is charged automatically through the month, what is invoiced at the end of it, how payment is collected and what happens when an invoice goes unpaid.","whenToUse":"When reconciling charges against expectations, when reviewing an invoice and when a payment against one fails.","concepts":["In-month charging and the end-of-period invoice are two parts of one cycle. The fee on an operation is withheld immediately; the shortfall against the monthly minimum is invoiced at the end.","The monthly minimum is not a subscription on top of fees but a floor: if withheld fees fall short, only the difference is invoiced.","The invoice covers a closed period. Operations made after closing land on the next invoice, not the current one.","Non-payment does not restrict operations instantly: first a notice, then a restriction. The order and the timings come from the contract, not from a console setting.","Charges follow the organisation's tariff plan as it stood at the time of the operation. Changing the plan does not recompute operations already made."],"example":"Fees with
1held over the month come in below the monthly minimum. At period end an invoice is issued for the difference, not for the whole minimum. The summary shows how much was withheld in-month and how much was invoiced, so any divergence from expectations is examined on those two numbers.","tips":["Reconcile charges on a closed period, not the current one: an open month keeps moving.","Schedule a tariff change for the start of a period: mid-month you end up with two stretches on different rates.","A mass divergence in charges is fixed by a dedicated recalculation run, not by editing individual operations."]},"workflowCases":{"title":"Cases","summary":"A folder for one complicated situation: no predefined path, with an arbitrary set of tasks added as you go. Tasks, their outcomes and documents live in one place.","whenToUse":"When a situation does not fit a defined process: a dispute between participants, an unusual request, an incident involving several parties.","concepts":["A case differs from a process in having no diagram: the steps are not laid out in advance, the operator adds tasks as understanding develops.","States: active, resolved, closed. A closed case can be reopened â the history is preserved in full.","Tasks inside a case follow the same rules as those in the shared queue: they are claimed and completed, and assignees see them in the same place.","Documents attach to the case rather than to an individual task: they outlive task closure and remain the evidence base.","The case type is set at creation and only affects filtering in the list â it does not change how the work is done."],"example":"Two participants in a shared-financing project disagree about how income was split. A case is opened with a description, and tasks are added: request the organiser's calculation, check the ledger entries, prepare a reply. Documents are attached as the tasks complete. Once decided, the case is marked resolved and closed.","tips":["Write the description for someone joining in a month's time: cases outlive tasks.","Do not close a case before the parties have been told: reopening is possible but reads as going back on a settled matter.","Attach documents as they arrive rather than at the end: reconstructing the set afterwards costs more."]},"bankAccounts":{"title":"Customer accounts","summary":"The register of bank accounts: opening, details, balance, transaction history and standing orders. Accounts are blocked, unblocked and closed from here.","whenToUse":"When opening an account for a customer, when compliance requires operations suspended, and when investigating a balance query.","concepts":["The account number is generated by the platform from the organisation's data region and bank identifier if the field is left empty. A manually entered number is taken as given and is not checked against the standard.","Account type and currency are set at opening and do not change: changing them means opening a new account and moving the balance.","The overdraft limit and the daily debit limit are different constraints: the first permits going negative, the second caps turnover per day even on a positive balance.","Blocking suspends operations without closing the account: the balance stays where it is and continues to appear in reporting.","Closing requires a zero balance. An account with funds cannot be closed â transfer first, then close."],"example":"Compliance requires operations on a customer account to be suspended. On the account card the state is changed to blocked â debits and credits stop while the balance stays visible. After the review the state is restored. Had the account been closed instead of blocked, it could not have been brought back.","tips":["Use blocking rather than closing for a suspension: closing is irreversible.","Give the customer their details only after the account is open: a manually entered number means nothing until then.","Check the account's standing orders on the card: they keep executing even after the receiving account is blocked."]},"loans":{"title":"Loans","summary":"Lending products and disbursed loans: terms, repayment schedule, servicing state and work on non-performing debt.","whenToUse"
1:"When disbursing a loan, during monthly servicing control and when a payment falls overdue.","concepts":["The product defines the frame â currency, term, rate and accrual rules â and the contract inherits it as at disbursement. Changing the product does not change loans already issued under it.","The repayment schedule is built at disbursement. Early repayment rebuilds it, so the outstanding balance before and after the rebuild differs by design.","Arrears are counted in days from the payment date, not from the date of contact. The threshold at which a loan is deemed non-performing comes from the organisation's policy.","Restructuring means new terms on the same contract, not a new loan: the payment history is preserved, and that is exactly what a supervisor looks at.","The provision against non-performing debt follows the jurisdiction's regulatory rules and is recorded separately from the debt itself."],"example":"A loan payment is forty days overdue. The card shows the schedule, the actual payments and accumulated arrears. Restructuring is agreed: the term is extended and the instalment reduced, on the same contract. The record of past arrears remains â the loan does not become 'new and clean'.","tips":["Work from the date of the first missed payment, not the date the customer got in touch: arrears and provisions are counted from it.","Restructure before the loan is classified as non-performing where you can: after classification the provisioning requirements change.","Check early repayment against the rebuilt schedule â the outstanding balance does not move by the amount paid."]},"treasury":{"title":"Treasury and liquidity","summary":"The treasury summary: mandatory liquidity ratios against their required minimums, liquidity positions with buffers, the currency position and the maturity gap between assets and liabilities.","whenToUse":"Daily for ratio control, when planning a large outflow, and when preparing supervisory reporting.","concepts":["Liquidity ratios are monitored daily, not at the reporting date. A breach is recorded on the date and cannot be topped up retrospectively.","The buffer above the minimum is not a nice-to-have but an operating requirement: a ratio running at the floor breaks through it on the first sizeable outflow.","The currency position is measured per currency: a portfolio balanced in total can still breach the limit in a single currency.","The maturity gap shows what covers the obligations of the nearest periods. A negative gap in a short bucket is more dangerous than a large gap far out.","Ratios are computed from accounting data. Entries not posted to the ledger do not reach the ratio â that is usually where a divergence from expectation comes from."],"example":"A large payout is planned for the end of the week. The summary shows the short-term liquidity ratio running with a slim margin and the nearest maturity bucket in negative gap. The payout is split in two or funded with additional cover â otherwise the ratio is breached on the date, and that goes into reporting.","tips":["Read the summary before committing, not after: the ratio breaks at the moment of outflow, not at the moment of reporting.","Check the currency position per currency â overall balance guarantees nothing.","Look for divergences from expectation in unposted operations: the ratio is computed from the ledger."]},"islamicProducts":{"title":"Islamic banking products","summary":"The register of contracts under Islamic financing forms: cost-plus sale, trust investment, lease, partnership and others. Each card shows execution progress and the actions available.","whenToUse":"When servicing a contract, when obtaining Sharia approval and when distributing profit on a trust investment.","concepts":["A mark-up instead of interest is not a rename: it is fixed when the contract is signed and does not change with how late payment actually is. Arrears do not increase the debt.","Sharia approval is a distinct action recorded with a decision identifier. Until it is given the contract does not move into execution.","In a trust investment, profit is shared in pre-agreed proportions while loss falls on the capital provider. Gross profit is entered and the shares are computed from it.","A lease with purchase and an operating lease differ in what happens to the asset at the end: in the first it passes to the customer, in the second it stays with the bank.","Anything recovered for late payment cannot be the bank's income: the contract either waives such charges or directs them to charitable purposes."],"example":"A customer is a month late on a cost-plus sale contract. The debt has not grown â the mark-up was fixed at signing. The card shows paid, outstanding and days overdue. Any late charge that is provided for goes to a charitable destination rather than
1into the bank's income.","tips":["Enter the Sharia decision identifier at the moment of approval: without it the contract cannot be evidenced to the board.","For a trust investment, enter gross profit rather than the bank's share: the platform computes the shares.","Choose the financing form by the substance of the deal, not by accounting convenience: form not matching substance is the main source of board findings."]},"chartCustomization":{"title":"Own-brand appearance","summary":"Configuring how the environment looks: colours, logo, domain and email templates. The customer sees the operator's brand rather than the platform's.","whenToUse":"When launching an own-brand environment and when the corporate style changes.","concepts":["Appearance and domain are separate layers. Colours and logo apply immediately; your own domain needs DNS records and a certificate.","Email templates inherit the appearance, but the sender address is set separately: mail from someone else's domain lands in spam regardless of how it looks.","Changes are visible to every user of the environment at once. There is no preview mode for appearance, so edits are made outside working hours.","The logo appears in the interface, in email and on the payment page â check all three, they render it differently.","Environment appearance does not affect the payment page if that is configured separately: it has its own configuration."],"example":"An operator launches an own-brand environment. Primary colour, logo and name are set. The domain and the mail sender address are configured separately. After publishing, three places are checked: console login, the invitation email and the payment page â on the last of these the appearance comes from its own configuration.","tips":["Check the logo on dark and light backgrounds: in email the background is chosen by the mail client, not by you.","Configure domain and sender address together: mail from the platform's domain under someone else's brand looks suspicious to the customer and to the spam filter alike.","A full brand setup pass is available as a wizard â it will not let you forget the domain and the mail."]},"pricingPlans":{"title":"Tariff plans","summary":"Plans and their fee configurations by currency: rate in basis points, fixed component per operation, minimum and maximum withheld. Individual terms for an organisation are assigned from here too.","whenToUse":"When setting commercial terms for a new client, when revising rates and when investigating a divergence in charges.","concepts":["The fee combines a percentage rate and a fixed component per operation. The minimum and maximum withheld cap the result â and they are what produces surprises on very small and very large amounts.","The rate is expressed in basis points: hundredths of a percent. An order-of-magnitude error here is not visually obvious and surfaces on the first invoice.","Configuration is per currency: a plan with no configuration in the operation's currency will not apply, and the operation falls to the default plan.","Individual terms override the plan without replacing it: only what is set explicitly is overridden.","Volume tiers apply on turnover actually reached in the period, not on forecast: the rate drops after the threshold is passed, not before."],"example":"A client is offered 1.2% plus a fixed component. The configuration records 120 basis points, the fixed component and a minimum withheld. On a small payment the minimum kicks in â the effective charge exceeds 1.2%, which is entirely explainable if you look at the minimum.","tips":["Say the basis points out loud: 120 is 1.2%, 1200 is 12%.","Configure every currency the client trades in: a missing one sends operations to the default plan.","Explain the minimum withheld before signing: it generates most of the questions about small payments."]},"charity":{"title":"Charitable endowments","summary":"Managing endowments and distributing their income to beneficiaries, plus automatic routing of a share of receipts to charitable purposes.","whenToUse":"When distributing endowment income, when enabling automatic routing and when reporting to trustees.","concepts":["The endowment corpus is inviolable: only the income earned on it is distributed. That is a constraint of the form itself, not a setting.","Beneficiary shares are fixed by the deed. They cannot be changed in the console â a change is executed outside the platform and reflected by setting up a new distribution.","Automatic routing sends a defined share of a receipt to its purpose without operator involvement. A configured rule applies from the next receipt onward.","Distribution is an operation on the endowment, not on an individual beneficiary: the amount is split by shares at once, and distributing to one beneficiary alone is not provided for.","Amounts recovered for late payment under Islamic contracts are directed here: they cannot be the operator's income."],"example":"Over the quarter the endowment earned income on its corpus. The operator runs a distribution: the amount is split by the deed's shares among beneficiaries and the corpus is untouched. The trustee report is assembled from the same operation â no separate calculation outside the platform is needed.","tips":["Before distributing, confirm the amount is income and not corpus: there is no reverse operation.","Check beneficiary shares against the deed rather than the previous distribution: the deed may have changed.","Turn on automatic routing at the start of a period â otherwise some receipts fall outside the rule and it shows in the report."]},"omniAccount":{"title":"á¨áµáá
á± á¨á°á ááá áá³á¥","summary":"á¨áµáá
áµá áá¥á¨á¶á½ á á¦áµáµ áááᦠá¨áááá¥á á¨ááªáᶠá᪠áá³á¥á£ á¥áµááá á¨áá ᣠáá£áªá«áá½á á¨á°á³áµá áááááµ á¢áá¨áµáµááá¶á½á£ á á
ááá á á ááªá« á¶ááᢠá¨RWA á¶á¨áá½á á¨dCLS á¦á³áá½ á áá«á°á±á â á¨á¨á«á³á¸á ááá á áá¸áᢠá¨ááá« áááá¶á½á á¥áá ááá»á¸á«áá¢","whenToUse"
1:"áµáá
á± á á á
áá áá á«á
á á¥áá³áá áá¨áµ á²á«áµáááᣠá¥á áááá á áá áááá ááááµ á²áá¨á¥á¢","concepts":["á á
ááá á á áá á°áá áá° á ááµ áááᬠáááá£áᢠáááᥠá£áááá³ááµá á¨á°áá áá áááá£á â áá
á¨áá³á¥ áµá
á°áµ á áá°ááá¢","á¨á°áá«á© ááááµ á¦á³áá½ á¨áá°áá©áµ áá° á ááªá« á¶áá á¨á°ááá¡ á áá á¥á» ááᦠá¨áááᥠá᪠áá³á¥á£ á á¥áµááá áá ááµá¥ á«á áµáá»á á ááá» ááµá¥ á«á á¢áá¨áµáµáááµ á áá± á ááá á áá°á«áá¢","á¨áááá¶á½ áá½á½á á á á
áá ááªá á áá áá°á¨á°á«áᣠá á ááµ á³áªá á áá°ááᦠáá á²áá á áá«á½ á£áá¦áµáµ áá ááááµ ááµ áá£áá áá¸áááá¢","ááá± á á áá ááá³ áá á¨á°áá á¨á° ááᢠá áá½á½áá á ááá áá«á¨á áááᥠáá½ááᤠáµááá
áá½á½á© ááá á¥áá áá á áá°ááá¢"],"example":"áµáá
á± áµáá
áá á áá° áá ááá ááᢠáá½á½á© á¦áµáµ ááááµ á«á³á«áᦠá¨ááµá¥ áááá áá«á½ áá áá á°áá£á© á áá á£áá ááᤠá¨áá³á¥ áá¨á¥ ááµ áá áá á áá«á áá áá°áá³áᤠá°ááá·á á á£áá®á½ áá«á¨á áááá áá«á½ áá áá á¦áµáµ áá áááµá³áᢠááá«á á áá á¥áá á á³áªá á áá°ááá¢","tips":["á á
ááá á¨á°áá áá áááá£áᦠá¨á á ááµ áá á«áá°áµáá ááááªá« áá
á áááá¨á±á¢","á¨áááá¶á½ áá½á½á á¨áááá á ááµ áá²á«áá á«áµááᦠááá³áá½ á¨áá³á á á áá áá¥ááµ áááá£áá¢"]},"nettingMonitor":{"title":"Netting monitor","summary":"Netting windows: window start, instruction count, breakdown by channel, gross and net volume, netting efficiency and window state.","whenToUse":"When watching the netting cycle and when working out why net volume came out higher than expected.","concepts":["Netting efficiency is the share of obligations extinguished against opposing claims. Low efficiency means a one-directional flow, not a broken mechanism.","Gross volume is the sum of all instructions in the window; net is what actually goes to settlement. The difference between them is the benefit of netting.","A window closes on time, not on instruction count. An instruction arriving after close falls into the next window.","Netting across different channels is reduced to a single settlement unit: without that, opposing obligations in different networks would never meet.","The window state â pending, in progress, completed â refers to settlement rather than to the instructions: an instruction can be accepted while the window is still open."],"example":"Forty instructions accumulate in a window; gross volume markedly exceeds net â efficiency is high and only a small residue goes to settlement. In the next window the flow is one-directional: there are almost no opposing claims, efficiency drops and net approaches gross. That is not a failure but a reflection of what the flow contained.","tips":["Explain low netting efficiency by the composition of the flow, not by settings: the mechanism nets what exists.","Look for instructions sent near the close in the next window: the boundary is time.","Compare gross and net over a period rather than a single window: the benefit of netting shows up over a series."]},"reports":{"title":"Reports and exports","summary":"Summary figures for a period broken down by day, currency and partner, plus one-off exports: turnover and a reconciliation statement in tabular form.","whenToUse":"For daily turnover control, at period close, and when accounting needs an export.","concepts":["Figures are computed for the chosen period and environment. Mixing live and test data is the most common cause of divergence from expectation.","Turnover and operation count move differently: conversion falls at unchanged turnover if the average amount has grown. Read both.","The reconciliation statement is assembled for a closed period. Assembled for the current one, it will change every time the peri
1od is reopened.","An export reflects the state at the moment it was produced: a file received yesterday is not recomputed for later changes.","Scheduled delivery of a register to a recipient is configured elsewhere and does not appear here â this page is about one-off exports."],"example":"Accounting needs the reconciliation statement for last month. The period is closed, the range, currency and partner are chosen and the export is produced. A week later a late correction arrives on one operation â the statement does not recompute itself, so the export is repeated and the difference is explained separately.","tips":["Check the environment toggle before exporting: test data in a reconciliation statement gets noticed at the accountant's desk.","Produce the statement after the period closes â otherwise it diverges from the ledger by the amount of late entries.","Configure scheduled register delivery with the export wizard: repeating it by hand every month will eventually be missed."]},"cryptoAnalytics":{"title":"Crypto asset analytics","summary":"Monitoring of virtual asset operations: volumes, addresses, counterparty risk scoring and the material behind supervisory reporting under a digital asset licence.","whenToUse":"For periodic risk control on crypto operations and when preparing a report for a supervisor.","concepts":["Address risk scoring is built on connections rather than volume: a small amount from a tainted source is more dangerous than a large transfer between known participants.","A digital asset licence carries its own reporting, separate from banking reporting: its content and frequency are set by the jurisdiction.","Exchange, transfer and custody are three distinct licensable activities. Holding a licence for one does not confer the others.","The travel rule requires originator and beneficiary information to accompany a transfer: without it the operation is non-compliant even if it went through technically.","Analytics reflects what is visible on chain. Operations that stay inside the platform and never touch the chain do not appear here."],"example":"Ahead of the quarterly report the operation profile is checked: volumes by activity, the share of transfers from higher-risk addresses and the presence of accompanying information. A series of transfers is found lacking a complete originator set â that is what gets resolved before filing, not after.","tips":["Investigate higher-risk addresses by their connections, not by amount: a small transfer from a tainted source is not a minor matter.","Compare the list of activities you actually perform against your licence: extending services without extending the licence is found at inspection.","Look for internal, off-chain operations in the general operations register â they will not be here."]},"standingOrders":{"title":"Standing orders","summary":"Recurring debits of a fixed amount on the account holder's instruction: debit and credit accounts, amount, frequency, next and last execution dates, state.","whenToUse":"When setting up a recurring payment for a customer, when suspending one on request, and when investigating a missed debit.","concepts":["A standing order differs from direct debit in who initiates: here the account holder instructs, not the payee.","Suspension is available only for an active order and resumption only for a suspended one. The states strictly alternate.","Cancellation is irreversible and separately confirmed: a cancelled order cannot be resumed, a new one has to be set up.","A missed debit is not automatically carried to the next day: on insufficient funds the payment is skipped while the order stays active.","The next execution date is recomputed after each debit. Suspension does not shift it â on resumption the order continues its calendar."],"example":"A customer asks to pause a rent payment for two months. The order moves to suspended â debits stop while the calendar is preserved. Two months later it is resumed and executes on its usual date. Had the order been cancelled, the calendar would have had to be set up again.","tips":["Use suspension rather than cancellation for a temporary stop: cancellation is irreversible.","A debit missed for insufficient funds does not restore itself â if the payment is obligatory, make it separately.","Check the credit account at setup: an error there repeats as many times as the order executes."]},"tierTreasury":{"title":"Crypto treasury","summary":"The organisation's internal wallets by purpose: storage tiers, quarantine and a gas wallet. Each shows network, environment, address and balances.","whenToUse"
1:"When setting up an organisation's crypto environment and when investigating stuck receipts.","concepts":["Storage tiers differ by risk and purpose: working funds and long-term holdings are not mixed, and that is a measure against key compromise rather than a convenience.","Quarantine is the wallet for receipts that need review. Funds land there automatically under risk rules and are not moved out by hand until a decision is made.","The gas wallet holds the network's native coin to pay fees. Without it nothing leaves, however large the token balance.","A non-zero token balance on the gas wallet is the trace of a failed swap, not a normal state: the gas wallet holds native coin, not tokens.","Wallets are not created on the fly: if no wallet exists for a network-and-environment pair, the operation is deferred and the funds stay at the original address."],"example":"A receipt fails to distribute across wallets and the money stays at an intermediate address. Checking the treasury shows that no wallet of the required tier exists for this network in the live environment. Once the missing wallets are provisioned the operation completes â the platform deliberately will not create an address mid-flight.","tips":["Provision the full wallet set for each network-and-environment pair at once: a missing wallet halts receipt distribution.","Watch the native coin balance on the gas wallet: running out looks like operations failing for no clear reason.","Investigate tokens sitting on the gas wallet: they indicate a swap that did not finish."]},"giftCards":{"title":"Gift cards","summary":"Issued card batches: denomination, quantity, card states and the escrow balance for the batch. Batches are issued, exported and frozen from here.","whenToUse":"When issuing a batch, when investigating a redemption and during a code leak incident.","concepts":["The code is the money: a card is a bearer instrument, and whoever knows the code can spend the denomination. Everything about how codes are handled follows from that.","The whole batch's denomination is debited to a dedicated escrow wallet at issue. Cards cannot be issued on credit, and no reverse movement out of escrow is provided for â it is drawn down only by redemption.","The code is shown once when a single card is issued, and cards appear only as masks in the interface. A full code does not exist in the console.","Exporting codes requires second-factor confirmation: this is distributing money, not a report.","Freezing a batch blocks redemption without moving money. It is reversible and intended for an incident, not for recalling cards."],"example":"A leak of a batch's code list is discovered. The batch is frozen with a second factor â every active card stops redeeming while the money stays in escrow. Cards already redeemed are unaffected. After the review the batch is either unfrozen or left frozen until the cards expire.","tips":["Save a single card's code immediately: it is never shown again anywhere.","On suspicion of a leak, freeze first and investigate second: freezing is reversible, redemption is not.","Remember that the escrow balance is the unredeemed cards: it falls only through redemption and is not returned to the issuer on request."]},"balances":{"title":"Balances and settlement","summary":"Wallet balances for the organisation broken down by purpose: working funds, fees, holds and blocked amounts.","whenToUse":"When checking the available amount before a payout, when answering 'why is less available than the balance' and during settlement with a merchant.","concepts":["Balance and available amount are different figures. The difference comes from the retained reserve, funds in in-flight operations and blocks.","A hold is a separate wallet type: funds sit on it and take no part in payouts. The platform shows that wallet's balance but does not compute the share held back and keeps no release schedule â both are set by contract and executed by an operator's decision.","Settlement with a merchant runs against the available part. Trying to withdraw the whole balance runs into the hold â that is expected behaviour, not an error.","Funds in in-flight operations have already left the available amount but have not yet gone out: between those states the balance looks smaller than expected.","A compliance block and a contractual hold are different things on different grounds: the first is lifted by a compliance decision, the second by moving funds back to the working wallet."],"example":"A merchant asks why less is available for payout than the balance shows. The breakdown shows three parts: a retained reserve with its release schedule, funds in in-flight operations, and the rest â available. The reserve returns on its sc
1hedule, not on request.","tips":["Explain the difference between balance and available amount up front: it is the most common question around a merchant's first payouts.","Look up the hold release terms in the merchant contract: the platform does not store them and will not return the funds by itself.","Distinguish a block from a hold in conversation: the first is lifted by a compliance decision, the second by a transfer back."]},"investmentLimits":{"title":"Investor limits","summary":"Rules for the participatory finance area: investment limits by investor type, accreditation thresholds and the withdrawal window.","whenToUse":"When configuring the area to a jurisdiction's requirements and when investigating why an investment was rejected.","concepts":["The limit is measured by investor type, not by campaign: a non-qualified participant is constrained across all campaigns at once.","The check runs at the moment of investing. Changing a limit does not revisit investments already accepted.","The accreditation threshold and the investment limit are different figures: the first decides what an investor counts as, the second how much they may commit.","The constraints come from the jurisdiction. Relaxing them in settings does not make an over-limit investment lawful."],"example":"An investor tries to commit more than the limit for their type. The investment is rejected before funds move. Two routes follow: the investor is accredited and changes type, or reduces the amount. Investments accepted earlier are not revisited.","tips":["Check the limits before launching a campaign: a rejection at the point of investing looks to the investor like a platform fault.","Arrange accreditation in advance â there is no time for it at the moment of investing.","Record any relaxation with a justification: it is the first thing a supervisor looks at in this area."]},"leads":{"title":"Inbound applications","summary":"The queue of enquiries from prospective clients: application state, owner and the step across to creating an organisation.","whenToUse":"When working inbound enquiries and when handing an application to onboarding.","concepts":["An application is not yet an organisation: until one is created the client does not exist on the platform and nothing can be configured.","The application state reflects work with a person, not readiness of an environment: a confirmed application means agreement, not configured processing.","Creating the organisation is a one-way step in that the organisation persists even if the client walks away â it then has to be closed separately.","The application owner and the owner of the created organisation are different roles: the second is assigned during onboarding."],"example":"An enquiry arrives from a payment agent. The application is worked until terms are agreed, then an organisation is created from it â at which point the onboarding wizard takes over: team, tariff, billing currency. Had the client walked away after creation, the organisation would need closing as a separate action.","tips":["Create the organisation after terms are agreed, not to try things out: empty organisations clutter reporting.","Assign an owner immediately: an unowned application goes stale unnoticed.","The onboarding wizard drives what comes next â do not configure the environment by hand alongside it."]},"portfolioAnalytics":{"title":"Portfolio analytics","summary":"Performance across a set of campaigns: return, arrears, distribution of investments and movement across periods.","whenToUse":"For periodic review of the area's results and when preparing an investor report.","concepts":["Portfolio return is not the average of campaign returns: it is weighted by amount, and one large failing campaign outweighs several small successes.","Realised and expected results are computed separately: the second keeps moving until campaigns close and is not a promise.","Portfolio arrears are measured by amount, not by contract count: ten small delinquencies can matter less than one large one.","Figures are built on closed periods. The current period is incomplete and cannot be compared with a past one directly."],"example":"For the quarter, portfolio return sits below the average campaign return. The distribution shows why: one large campaign fell into arrears and outweighed the rest. The investor report is built on that explanation rather than on the average figure.","tips":["Compare closed periods with closed periods: the current one always looks worse because it is incomplete.","An unweighted average return misleads â quote the weighted one.","Call the expected result an estimate when talking to an investor, not a forecast of income."]},"impactTracking":{"title":"Impact tracking","summary":"Social impact measures per project and their mapping to sustainable development goals, for reporting to investors and donors.","whenToUse"
1:"For regular impact reporting and when preparing material for investors who care about it.","concepts":["An impact measure is defined by the project and expressed in its own units: comparability between projects only appears through mapping to a shared goal.","The data is entered by the project organiser rather than computed by the platform: its credibility rests on supporting documents.","Mapping to a development goal is a classification, not a measurement: it does not make measures comparable by itself.","Impact and financial result are independent: a project can succeed on impact and lose money."],"example":"A water project reports the number of households with access to clean water. The measure maps to the relevant development goal. In the investor report it sits alongside the financial result rather than instead of it â the two do not substitute for each other.","tips":["Require supporting documents for impact figures: without them the report will not survive external scrutiny.","Do not add measures across projects: different units do not sum, even under one goal.","Always show the financial result alongside â otherwise the report reads as one replacing the other."]},"governanceProposals":{"title":"Community votes","summary":"Proposals put to a vote: votes for and against, the quorum required and the closing date. Proposals are created, voted on, tallied and executed from here.","whenToUse":"When putting a question to a collective decision and when tallying a vote.","concepts":["Quorum is the share of members without which a decision is invalid. A vote that misses quorum is not rejected: it simply did not take place.","The tally is an explicit action after the closing date. Until then votes are visible but there is no decision.","Execution is a separate step after the tally: an adopted decision does not apply itself.","The list of voters is anonymised: you can see quorum was met, not who voted which way."],"example":"A proposal to change the membership fee wins a majority of those voting, but quorum is not met â only a third of members voted by the deadline. The tally records that the decision failed on quorum rather than on the merits. The question is put again, this time with advance notice to members.","tips":["Notify members before voting opens: a missed quorum is almost always ignorance rather than disagreement.","Allow generous time: an open vote cannot be extended.","Do not forget the execution step: an adopted but unexecuted decision reads as one that was ignored."]},"shariaReview":{"title":"Sharia product review","summary":"The organisation's live Sharia-compliant products with their approval state and review dates.","whenToUse":"When preparing for a board meeting and when introducing a new product.","concepts":["Approval is granted to a product, not to an individual deal: deals under an approved product need no separate board decision.","Approval has an expiry: an expired one needs review even if the product has not changed.","Changing a product's material terms voids the existing approval â it is a new edition, not an amendment.","Form not matching the substance of a deal is the main source of findings: a contract named as one form but operating as another will not be approved."],"example":"Ahead of a board meeting the list is checked: two products have approvals expiring this quarter, and one has changed its mark-up terms. The first two go for review, the third as a new edition. Deals under live products need no separate decision.","tips":["Track review dates in advance: an expired approval stops sales of the product, not just its reporting.","Take term changes to the board before applying them, not after the first deal.","Record the board decision identifier on the contract card: without it the deal cannot be evidenced at review."]},"deposits":{"title":"Deposits","summary":"Deposit products and open deposits: terms, tenor, interest accrual and the treatment of early closure.","whenToUse":"When opening a deposit for a customer, at interest accrual and on early closure.","concepts":["The rate is fixed at opening. Changing the product does not change deposits already open.","Early closure recomputes interest at the reduced rate set by the product: the customer receives less than the schedule showed.","Withholding tax on interest income depends on jurisdiction and recipient type and follows the tax profile, not a deposit setting.","Auto-renewal renews at the rate in force on the renewal date, not the previous one."],"example":"A customer closes a one-year deposit after eight months. Interest is recomputed at the reduced early-closure rate â the payout is less than the schedule showed at month eight. The difference follows from the product terms, not from a calculation error.","tips":["Explain early-closure terms at opening: it is the most common dispute on deposits.","Check the auto-renewal rate in advance â the customer expects the previous one.","Verify tax with
1holding against the jurisdiction's tax profile rather than the product settings."]},"cards":{"title":"Cards","summary":"Issued cards, card transactions and the organisation's card products: scheme, currency, limits and fees.","whenToUse":"When issuing a card, when investigating a card transaction and when configuring a card product.","concepts":["The product defines the frame â scheme, currency, default limits and fees. A card inherits it at issue.","Daily and monthly limits apply at the same time: an operation is declined by whichever is exhausted first.","Transaction currency and settlement currency differ on conversion, and the rate is fixed at processing rather than at purchase.","Blocking a card and reissuing it are different actions: the first is reversible, the second changes the details and requires delivery."],"example":"A customer reports a declined purchase on a positive balance. The card's transactions show the daily limit exhausted while the monthly one still has room. The limit is raised on the card, or the customer waits for the next day.","tips":["When investigating a decline, check both limits: either can be the one exhausted.","Explain the difference between transaction and settlement currency by the processing-date rate â it is a frequent dispute on foreign purchases.","Use blocking for a temporary stop: reissue changes the details and needs the card delivered."]},"creditScore":{"title":"Credit assessment","summary":"A customer's creditworthiness assessment and the issuing of a proof that it is at or above a threshold, without revealing the exact value.","whenToUse":"When assessing a financing application and when a counterparty needs confirmation without disclosure.","concepts":["The proof confirms only 'at or above the threshold'. The exact score is not contained in it and cannot be recovered from it.","The threshold is set when the proof is issued: one proof confirms one threshold, another requires a new one.","The proof is tied to the moment of issue: a later change in the score does not invalidate it, so the recipient needs their own validity window.","The assessment is built on platform data. External credit history is not included unless it was supplied separately."],"example":"A customer applies for financing with an external partner. Instead of a statement showing the score, a proof of 'at or above the threshold' is issued. The partner verifies it and decides, receiving neither the exact score nor the data behind it.","tips":["Agree the threshold with the recipient before issuing: a proof for a different threshold has to be reissued.","Agree how long the proof stays valid: the platform does not revoke it when the score changes.","Do not let a proof stand in for full borrower assessment â it answers exactly one question."]},"crowdfundingDistributions":{"title":"Campaign distributions","summary":"The queue of income distributions: period, campaign, amount, state and payment dates. Distributions are run manually and failures investigated from here.","whenToUse":"For regular income payouts to investors and when a distribution fails.","concepts":["A distribution belongs to a period, not to the date it was run: running it late does not change the period the income belongs to.","The financial breakdown shows gross profit, costs and the investors' share separately. Those three numbers explain the amount paid.","A failed distribution stays in an error state with the reason given â no money moved.","The upcoming payment plan shows what goes out in the coming month: it reveals the liquidity load in advance."],"example":"A monthly distribution fails: the error state says the campaign account has insufficient funds. No money moved. After topping up, the distribution is run manually with the same period label â the period stays the same despite the later run date.","tips":["Check the upcoming payment plan at the start of the month: it shows the load before it arrives.","State the period label explicitly on a manual run â otherwise the distribution attaches to the current period.","Read the error text in full: it usually names a specific cause rather than a generic failure."]},"rwaAssets":{"title":"Tokenised real-world assets","summary":"The register of real assets brought on chain: asset description, valuation, issued share and income distribution to holders.","whenToUse"
1:"When registering a new asset and when distributing income from it.","concepts":["A token is a share in the asset, not the asset. A holder's rights come from the issue documents, not from holding the token.","The valuation is set at registration and updated separately: the token's market price does not follow it directly.","Income is distributed pro rata to holdings on the distribution date, not on the date the income arrived â a holder who bought later takes part in the next distribution.","Withdrawing an asset from tokenisation requires buying out every share: while holders exist the asset carries obligations."],"example":"An income-producing property is registered: description, valuation, number of shares issued. Quarterly rental income is distributed pro rata to holdings on the distribution date. A holder who bought a week before that date participates on equal terms.","tips":["Announce the record date in advance: it determines who receives.","Refresh the valuation regularly: a stale one misleads in secondary trades.","Set out holder rights in the issue documents â they do not follow from holding a token."]},"providerQuality":{"title":"Provider quality","summary":"A ranking of payment providers: an overall score broken down into availability, settlement speed and freedom from disputes, each with its weight.","whenToUse":"When choosing a primary channel, when revising the routing cascade and when discussing quality with a provider.","concepts":["The score combines three measures with different weights: availability carries the most, settlement speed and dispute-freedom split the rest evenly.","The overall score is useless without the breakdown: two providers on the same score can be weak in different places and are not interchangeable.","Measures are computed from actual operations over a period. A provider with few operations has an unstable score.","The score does not drive routing by itself: excluding an unhealthy channel is done by a separate monitoring mechanism."],"example":"Two providers score closely. The breakdown shows the first has high availability but slow settlement, the second the reverse. The first is chosen for acquiring, the second for payouts. That decision could not have been made from the overall score.","tips":["Read the breakdown, not just the total: the same score can mean opposite problems.","Do not compare providers with very different operation counts â at low volume the score is noise.","Bring a specific measure and period to a conversation with a provider: an overall score is not an argument."]},"dclsReserves":{"title":"Settlement network reserves","summary":"The daily check that bank cover matches issued token supply: the held balance may never be less than what has been issued.","whenToUse":"For daily cover control and when preparing a proof of reserves.","concepts":["The rule is simple and has no exceptions: the bank balance is never below issued supply. A breach means unbacked tokens in circulation.","The check runs automatically every day. A manual run is for investigation, not for routine control.","A divergence more often comes from an uncredited top-up than from missing funds: check the statement first, issuance second.","External proof of reserves is a separate procedure: the platform's internal check does not replace it."],"example":"The morning check shows issuance exceeding the balance. The bank statement reveals a top-up credited late in the evening that missed the snapshot. Once the data refreshes the invariant holds â no issuance beyond cover took place.","tips":["On a divergence look at the statement before issuance: a late credit is the most common cause.","Do not let the internal check stand in for external proof of reserves: they address different audiences.","Resolve a divergence the day it appears â unbacked tokens in circulation do not wait."]},"dclsSettlement":{"title":"Payment-versus-payment settlement","summary":"Atomic settlement between two network participants: both sides receive at the same moment, or neither does.","whenToUse":"When watching the settlement cycle and when investigating a failed settlement.","concepts":["Atomicity removes the risk of one side having paid while the other has not: no intermediate state exists.","A failed settlement returns both sides to where they were. Funds do n
1ot sit stranded with one of them.","Pausing the settlement contract moves instructions to failed, and the retry is started by hand â it does not resume on its own.","Settlement executes against the instructions accumulated in a cycle. An instruction arriving after the cycle closes waits for the next one."],"example":"Settlement between two participants does not go through because the contract is paused. Both instructions move to failed and the funds stay with their owners. Once the pause is lifted the retry is started manually â there is deliberately no automatic resumption, so that settlement never proceeds unexamined.","tips":["Always start the retry after lifting a pause: instructions do not revive by themselves.","Resolve the cause of the pause before retrying â otherwise the retry hits the same wall.","Do not go looking for funds stranded on one side: by design they are not there when settlement fails."]},"minterOnboarding":{"title":"Issuer onboarding","summary":"Onboarding a new licensed issuer to the settlement network: stages from initial checks to live operation with a minimum reserve in place.","whenToUse":"When onboarding an issuer and when tracking the state of an application.","concepts":["Stages run strictly in order: issuance cannot start before the checks, even where the licence has been verified outside the platform.","The minimum reserve is set before going live and caps issuance volume â not the other way round.","The applicant can see their own application state: they know which step is required and are not left waiting in silence.","Issuer approval and settlement participant approval are different roles: an issuer mints, a participant settles."],"example":"A bank applies for the issuer role. Its licence and legal details are checked, then a minimum reserve is set, and only once that is confirmed does the application move to live. Until then issuance is unavailable, even though every document has already been verified.","tips":["Agree the minimum reserve before go-live: it caps issuance from day one.","Track the application state with the applicant â silence on their side usually means they do not know the next step.","Do not conflate the issuer and participant roles: the second needs its own application."]},"dclsParticipantsNetwork":{"title":"Network participants","summary":"The roster of approved settlement network participants: legal name, jurisdiction, settlement mode, address and state. Public data only.","whenToUse":"When checking a counterparty before a deal and when watching token positions.","concepts":["The section shows public information about participants. A given participant's limits and positions are visible to them, not to everyone.","Settlement mode determines where the obligation is discharged â in the platform's ledger, on chain, or both. Speed and finality follow from it.","Approaching a position cap raises an alert: an excess is blocked rather than examined afterwards.","A participant's state is changed by the network operator: a suspended participant stays on the roster but takes no part in settlement."],"example":"Before a large deal the counterparty is checked: jurisdiction, settlement mode and state. The mode shows settlement runs on chain rather than in the platform ledger â so finality follows network confirmation, and the deal's timing is planned around that.","tips":["Check the settlement mode before the deal: it decides when the obligation counts as discharged.","Address an approaching position cap in advance â once exceeded, the instruction simply will not go through.","Remember this is public data only: you will not learn a counterparty's own limits here."]},"coreBankingOperations":{"title":"Banking operations","summary":"Handling problem cases in the banking environment: the issues queue, identity checks, applications and account openings, plus the daily reconciliation summary.","whenToUse":"Daily when working the issues queue and when rolling back a composite operation.","concepts":["A composite operation rolls back in reverse order: the last completed step is compensated first. A partial rollback leaves the system inconsistent.","Compensation is a new operation, not a cancellation of the old one: both remain in the history, which is correct for audit.","A problem case does not always mean a platform fault: more often it is waiting on an external party and closes by itself.","The daily reconciliation summary surfaces divergences before a customer reports them."],"example":"Account opening breaks after the record
1is created but before details are assigned. The composite operation rolls back: no details were assigned, and the account record is compensated. Both actions â creation and compensation â remain in the history and show what happened.","tips":["Do not patch the aftermath of a composite operation by hand: rollback belongs to the compensation mechanism, or state drifts apart.","Work the issues queue at the start of the day: some cases will have closed by themselves.","Resolve divergences from the daily reconciliation before the customer calls â it is cheaper."]},"invoicesAdmin":{"title":"Organisation invoices","summary":"The invoice register filtered by state: awaiting payment, paid, rejected. Invoices are issued to organisations and payment confirmed from here.","whenToUse":"When issuing an invoice, when confirming receipt of payment and when chasing an unpaid invoice.","concepts":["An invoice is issued to an organisation rather than to a user: the addressee is the legal entity, and payment confirmation attaches to it.","Confirming payment is an operator action, not an automatic consequence of money arriving: the platform does not match a bank payment to an invoice by itself.","A rejected invoice stays in the register: it is not deleted because it is part of the settlement history with the client.","The invoice environment is set at issue â an invoice in the test environment has nothing to do with live settlement."],"example":"An invoice for the period is issued to an organisation. The client pays by bank transfer, the operator finds the credit on the statement and confirms payment in the register, changing the invoice state. Without that action the invoice stays awaiting payment even though the money has arrived.","tips":["Confirm payment right after reconciling with the statement: an unconfirmed invoice looks like client debt.","Check the environment at issue â a test invoice among live settlements is not spotted quickly.","Do not delete rejected invoices: they explain the gaps in numbering at audit."]},"islamicSetup":{"title":"Islamic banking launch","summary":"The wizard for the Islamic environment: jurisdiction and supervisor, the Sharia board's composition, the product set, mark-up in place of interest and the treatment of late-payment charges.","whenToUse":"When launching the Islamic line and when taking it into a new jurisdiction.","concepts":["A Sharia board is a precondition, not decoration: without one products cannot be approved, and therefore cannot be offered.","The product set is chosen for the jurisdiction: permitted forms and their requirements differ between supervisors.","The mark-up replaces interest in substance rather than in name: it is fixed and does not grow with how late payment actually is.","Anything recovered for late payment cannot be the operator's income: the wizard sets either a waiver or a charitable destination."],"example":"An operator opens the Islamic line in a new jurisdiction. The supervisor is chosen, the board's composition entered and the financing forms permitted in that country selected. The treatment of late-payment charges is set separately â without that decision the environment cannot be launched.","tips":["Settle the board's composition before launch: product approval is impossible without it, and the time it takes is usually underestimated.","Check the product set against the specific jurisdiction rather than carrying it over from another.","Participatory products in neutral terminology are configured separately: this wizard is about the Islamic banking environment."]},"cryptoSweeps":{"title":"Crypto sweeps","summary":"Moving funds from single-use deposit addresses into internal wallets according to the payer's risk score: source, destination, amount, tier, state and transaction hash.","whenToUse":"When watching receipts and when investigating a stuck sweep.","concepts":["Every payment gets its own single-use address: internal wallets are never shown to the payer, and the provenance of funds does not get mixed.","The destination tier follows the payer's risk score. Higher-risk funds go to quarantine rather than to a working wallet.","The destination wallet is not created on the fly: if no wallet of the required t
1ier exists for that network and environment, the operation is deferred and the money stays at the deposit address.","A failed sweep does not lose funds: they remain at the source address until the cause is fixed."],"example":"A sweep is in a failed state. The treasury has no wallet of the required tier for this network in the live environment. The money is safe â it is at the deposit address. Once the missing wallet is provisioned the operation is retried and completes.","tips":["On failure, check the treasury composition for that network-and-environment pair first.","Do not move funds out of quarantine by hand before the risk decision â that is what quarantine is for.","Keep the transaction hash when investigating: it is the only link between the console record and the on-chain event."]},"usernames":{"title":"Wallet names","summary":"Readable names in place of addresses: the organisation's name register with state, expiry date and the wallet each is bound to. Names are registered, renewed and released from here.","whenToUse":"When registering a name on request, when renewing and when handling an expired name.","concepts":["A name is a subscription with an expiry, not property: once it lapses it is released and someone else may take it.","Releasing a name is irreversible: the register entry is deleted, and the previous owner can only get it back by registering again, if nobody else has taken it.","A name is bound to a wallet. Changing the wallet means re-registering, not editing the entry.","A readable name does not replace checking the address on a large transfer: it reduces the risk of a typo, it does not confirm the recipient."],"example":"A customer's wallet name is about to expire. On request it is renewed for a year and the state and expiry update. Had the term lapsed, the name would have been released and anyone could have taken it: there is no restoration in favour of the previous owner.","tips":["Warn owners of expiry in advance: a released name cannot be recovered.","Release a name only on an explicit request â the action is irreversible.","Explain to customers that a name eases entry but is not confirmation of the recipient."]},"multisig":{"title":"Multi-signature treasury","summary":"Wallets with several owners and a signature threshold: the queue of proposed transactions, signature collection and execution once the threshold is met.","whenToUse":"When setting up a partner's corporate crypto treasury and when making an outbound transfer.","concepts":["The threshold is written as 'how many out of how many': a transfer leaves only after the required number of owner signatures.","Proposing a transaction moves no funds: until the threshold is met it is an entry in a queue.","The transaction sequence number matters: it guards against replay and against reordering the queue.","The section is partner-scoped: a platform staff member can open the page but will not see the data â the restriction is deliberate."],"example":"A partner sets up a wallet with four owners and a threshold of two. A transfer is proposed with recipient, amount and call data. The first owner signs â the queue shows one of two. After the second signature the threshold is met and the transfer executes.","tips":["Choose the threshold with an owner's absence in mind: a threshold equal to the number of owners stops the treasury at the first holiday.","Check recipient and amount before the first signature: signatures are collected against a specific transaction.","Remember the section is partner-scoped: an investigation has to run with the partner, not on their behalf."]},"routingSimulator":{"title":"Routing dry run","summary":"Checking channel selection without making a payment: step by step you see how many candidates survive each filter.","whenToUse":"When an operation found no channel and the merchant got a decline with no explanation.","concepts":["A 'no terminal found' decline means no candidates survived the filters. The dry run shows at which step the count reached zero.","The run makes no payment and moves no money: it reads configuration rather than transacting.","Filters apply in order. A candidate cut at an early step never reaches the later ones, so the cause is at the first zero.","The run reflects the configuration as it is now. If settings changed after the decline, the run will show a different picture."],"example":"A merchant reports a declined payment. The run is given partner, amount, currency and operation type. The cards show three channels surviving the currency filter and none surviving the amount filter: all three have an upper bound below the payment amount. The cause is found in a minute.","tips":["Enter the amount in minor units: a two-order error here produces a false
1conclusion.","Find the first step where the count hit zero â looking further is pointless.","If settings were edited after the decline, the run shows the new picture: check against the time of the incident."]},"routingHealth":{"title":"Channel health","summary":"Monitoring the error rate per provider and per channel: automatic exclusion of an unhealthy channel from selection, manual disabling and return to service.","whenToUse":"When declines rise on a channel, during a provider's planned maintenance and when bringing a channel back after recovery.","concepts":["An unhealthy channel is excluded automatically once the error-rate threshold is passed. That protects turnover; it is not a penalty on the provider.","Manual disabling requires a stated reason: it stays on the card and explains the decision a month later.","Return to service is an explicit action. A manually disabled channel does not come back on its own, even once the errors stop.","An out-of-cycle check recomputes the figures immediately and is useful after fixing the cause â there is no need to wait for the next cycle."],"example":"A provider announces two hours of maintenance. The channel is disabled manually with a stated reason â payments fall through the cascade to the backup. After the work an out-of-cycle check is run, the figures are clean and the channel is returned to service by an explicit action.","tips":["Disable a channel yourself ahead of planned maintenance: automatic exclusion only triggers after a run of failures on real customers.","Describe the reason for disabling in detail â a month later a date alone reconstructs nothing.","Do not forget to bring the channel back: a manually disabled one stays disabled indefinitely."]},"orgBaas":{"title":"Regulatory status","summary":"Organisation type, banking tier, licence set and bank details. Organisations are moved between fintech and banking mode from here.","whenToUse":"When a new licence is obtained, when changing tier and when converting an organisation to a bank or back.","concepts":["The organisation type determines the capabilities available: for a fintech organisation the tier controls are disabled, and that is not a permissions fault.","Tier and licences are independent: raising the tier adds no licences, and adding a licence raises no tier.","Bank details are shown only for the banking type â before conversion there is nowhere to enter them.","Collapsing the banking environment returns the organisation to fintech mode. The banking data remains but becomes inaccessible."],"example":"An organisation obtains a banking licence. Conversion to the banking type is performed on the card: data region, starting tier, bank details and the licence list. Afterwards the banking sections appear and tier management becomes available.","tips":["A full move to bank is easier through the banking launch wizard: it will not let you skip supervisory reporting and roles.","Add licences as they are obtained rather than all at once before an inspection: the entry date is visible.","Agree a collapse in advance â the sections close immediately, along with any work in progress in them."]},"dclsAdminParticipants":{"title":"Settlement participants","summary":"The participant register and protection against off-market rates: tolerance per pair and behaviour when no market reference exists.","whenToUse":"When onboarding a participant and when configuring protection against an erroneous or deliberately unfavourable rate.","concepts":["The participant sets the rate on their own order, which is why protection is needed: a misplaced decimal and a deliberately bad rate look identical to the system.","Tolerance is a percentage deviation from a market reference. An empty value means the pair's default applies, not that protection is off.","The policy when no reference exists is chosen explicitly: reject the order or let it through. Both are defensible, but the choice must be deliberate.","Protection is configured per participant: it is unavailable for revoked and rejected ones, since no orders will come from them."],"example":"Protection is enabled for a participant with a sensible tolerance and a 'reject when no reference' policy. A week later their order at a rate an order of magnitude off the market is rejected automatically â it was a misplaced decimal, and it did not become a loss.","tips":["An empty tolerance does not mean protection is off: it is the pair's default.","Choose the no-reference policy deliberately: letting orders through is convenient until the first night without quotes.","Enable protection for existing participants too, not only new ones: a misplaced decimal does not respect seniority."]},"routingMl":{"title":"Channel selection model","summary":"The learned model's state: accuracy, volume of accumulated data, version and last training time, plus feature importance and retraining.","whenToUse"
1:"For periodic quality control of selection and after a noticeable change in the channel mix.","concepts":["The model does not pick a channel by itself: it reweights candidates that filters already selected. Turning it off does not break routing, it returns selection to the rules.","Feature importance shows both strength and direction of influence. A heavily weighted feature pointing an unexpected way is something to investigate, not to be proud of.","Accuracy is computed on accumulated data. After the channel mix changes, previous accuracy is uninformative: the model learned a different world.","Retraining uses accumulated records. Retraining too often on thin data makes the model unstable."],"example":"Selection quality drops after two new providers are connected. The model state shows the last training predates them. Retraining is run and feature importance is rebuilt â the new channels now take part in scoring on equal terms.","tips":["Retrain after noticeable changes in the channel mix rather than on a schedule.","Watch the direction of feature influence: an unexpected sign more often means a data error than a discovery.","If selection results look doubtful, turn the model off: routing continues on the rules."]},"workflowRules":{"title":"Business rules","summary":"Rules of the form 'conditions - actions' with a priority and a stop flag: the register, building conditions and actions, a trial run against a set of facts, and activation.","whenToUse":"When encoding a decision in the system and when investigating unexpected rule behaviour.","concepts":["Conditions within a rule are joined by AND: the rule fires only when all of them hold.","Priority sets the order: the lower the number, the earlier the rule applies. The stop flag ends the pass over the remaining rules.","A trial run against a set of facts shows which rules fired and what came out â with no effect on live operations.","Disabling does not delete a rule: it stays in the register and can be switched back on. Deletion happens without confirmation and is irreversible."],"example":"A rule is created that raises the verification level for operations from a set of countries. Conditions are assembled in the form and the action sets a flag. The trial run shows the rule fires and does not conflict with a higher-priority one. It is then enabled.","tips":["Always do a trial run before enabling: priority conflicts only show up against facts.","Use the stop flag deliberately â it cancels every following rule, not just the conflicting one.","Delete rules with care: the interface asks for no confirmation, while disabling solves the same problem reversibly."]},"lending":{"title":"Lending pools","summary":"Standing pools of working c
1apital: total and free capital, utilisation, loan count and rate. Applications are decided and repayment schedules kept here.","whenToUse":"When deciding a loan application and when watching pool utilisation.","concepts":["A pool differs from a campaign in being permanent: capital returns to it and is lent again rather than being wound up once a goal is met.","Utilisation shows what share of capital is working. Full utilisation means there is nothing to fund a new application with.","The repayment schedule appears on the card after approval â before the decision there is none.","Rejecting an application requires a reason: it stays on the card and explains the decision at review."],"example":"An application arrives. The register shows the pool has enough free capital and sits at about three quarters utilisation. The application is assessed: amount, term, rate, collateral and its valuation. After approval the repayment schedule appears on the card.","tips":["Check free capital before assessing: an approved application against a zero balance stays unfunded.","State the rejection reason on the merits â it is read by the borrower and by a reviewer.","The pool itself is created by the product wizards rather than by the form on this page: the form here does not collect every required parameter."]},"generalLedger":{"title":"General ledger","summary":"Double-entry bookkeeping against the chart of accounts: the trial balance for a period, adjusting entries, reconciliation and period close.","whenToUse":"Monthly at period close and when the trial balance does not agree.","concepts":["Every entry is balanced: its lines sum to zero. A trial balance that does not agree means a data error, not an arithmetic one.","An adjusting entry does not correct the earlier one, it is added to it: both stay in the ledger, which is correct for audit.","Reconciliation runs before close. Closing a period without reconciling means locking in the divergence.","Period close is irreversible: entries in a closed period cannot be edited, and corrections are made in the next period."],"example":"At month end the trial balance is out by a small amount. Reconciliation points to a one-sided posting. An adjusting entry is made, reconciliation is rerun and passes, and the period is closed â with an explicit confirmation of irreversibility.","tips":["Do not close a period until reconciliation is clean: after close, corrections move to next month.","Describe adjusting entries in detail: six months on, an undescribed entry cannot be reconstructed.","Produce reporting after close â otherwise it diverges from the ledger by the amount of late entries."]},"chartOfAccounts":{"title":"Chart of accounts","summary":"The organisation's chart of accounts with hierarchy and filters, the jurisdiction reference, international reporting standard elements and the active mappings between them. The jurisdiction reference is the list of countries for which a chart of accounts has been implemented: a bank can only be set up in one of them.","whenToUse":"When launching a jurisdiction, when adding a custom account and when preparing reporting in international format.","concepts":["á¨áá³á¥ á»áá± á á ááªá± á°áá£á£áª á¨á°á°ááá á²áá á¨á«áµ áá³á¦á½ á¨áá© áá áá³á¨ááᦠá¨á°á°ááááá ááá
á áá°á«áµ á áá»ááá¢","á¨ááá á áá ááµááá¶á½ áá ááááµ áá¦á²á°á© á«áµááááᦠá ááµ ááááµ á¨áá³á¥ ááá á á áá«ááá á ááá á ááá á
áá¸áµ ááá ᥠá áá áµá¢","á¨ááááµ áááá¶á½ ááá«á«áᦠáá¥á°áᣠá ááµ áá³á¥á áá° á áá«á³ áááá½ áá¨áááᣠá áá«á³áá½á áá° á ááµ áá áááá á ááá« á£á
᪠áá á¨á°áá á¨á° ááá³á ááááµá¢","The jurisdiction reference is itself the list of supported countries: an organisation can be switched to bank mode only in a country from that list, and the platform rejects a region outside it. Countries of the CEMAC and WAEMU zones are picked by their own code â Senegal as SN, Cameroon as CM â while the chart of accounts, the legal-entity document requirements and the reporting forms come from the zone, XOF or XAF. The list shows the zone next to the country name."],"example":"An organisation enter
1s a new country. The prescribed chart of accounts and the account number format are checked in the jurisdiction reference, then custom accounts are added for operational specifics. Mapping to international elements is verified before the first report rather than after an audit finding.","tips":["A country's chart of accounts is created automatically when the organisation is switched to bank mode â there is no need to run the load separately. Multi-currency onboarding is only needed to set currencies and markups.","á¨á«áµ áá³á¦á½á á¨ááá¥á©áµ á¨á°á°áááá ááá
á á á¥áááµ á ááá áá áµ á¦á³ á¥á» áááá¢","áááááá¹á á¨ááááªá«á áªáááµ á ááµ á«á¨ááá¡á¦ á¦á²á°á© ááá°á±á á ááá á ááµ áá á«ááááá¢","A bank in a currency-zone country is created under its own country code; the XAF and XOF codes remain in the list for an organisation not tied to a single country of the zone."]},"mutualCredit":{"title":"Community mutual credit","summary":"Member accounts with a trust limit and offsetting transfers between them: balance, limit and state per account.","whenToUse":"When opening an account for a member and when a balance approaches its trust limit.","concepts":["A negative balance here is normal rather than debt in the usual sense: the member has received goods or services and owes an equivalent back to the community, not to a particular person.","The trust limit caps how far a balance may go negative. It expresses the community's trust, not the member's solvency.","The sum of all balances in a network is zero by construction: someone's minus is someone else's plus. A non-zero sum means an error.","A transfer neither creates nor destroys value: it moves balance between accounts inside the network."],"example":"A member asks for a higher trust limit: their balance has reached it. The history shows they take services actively but supply few of their own. The decision belongs to the community rather than the operator: the trust limit reflects members' willingness to wait for an equivalent in return.","tips":["Check that network balances sum to zero regularly: a deviation means an error, not activity.","Do not raise a trust limit on your own â by its nature that is a community decision.","Explain to new members that a negative balance is normal: otherwise they fear it and the network does not work."]},"chervonets":{"title":"Community settlement environment","summary":"The wizard that assembles an environment from existing parts: structure profile, legal form, the nature of the unit of account, membership and limits, mutual aid instruments, netting and reserve.","whenToUse":"When launching a community settlement environment and when revising its configuration.","concepts":["The environment is not a separate product but an assembly of existing parts: the community section, mutual credit, the rotating savings group, settlement participants and netting windows.","The legal wrapper and the nature of the unit of account are chosen deliberately: they determine how the environment looks to a regulator, not only to members.","The netting and reserve steps are conditional: they appear only when settling outward. A closed environment does not need them.","The unit's ratio to the national currency, the default credit limit and the return-to-zero period are set once for the whole environment."],"example":"A community launches a closed environment: settlement stays internal, no reserve is required. The wizard skips the conditional netting and reserve steps, and the summary shows which parts the environment is assembled from. The configuration is saved and members are onboarded through the ordinary sections.","tips":["Settle the legal form before launch: changing it on a running environment means rebuilding it.","A closed environment does not need a reserve â do not enable it 'for later', it complicates the accounting.","Set the return-to-zero period realistically: too short makes mutual credit useless."]},"fxRates":{"title":"Exchange rates","summary":"Effective rates with their validity windows: source, value, nominals and period. This is where you see which rate a conversion will use.","whenToUse"
1:"When checking the applicable rate and when investigating a divergence in a converted amount.","concepts":["A rate applies within its window. Overlapping windows on one pair make the conversion result depend on which rate was picked â the costliest mistake in this section.","Nominals set the scale: a rate 'per hundred units' and 'per one unit' are different records, and confusing them is a two-order divergence.","A rate without an end date applies indefinitely: the next one has to be closed manually, or the windows overlap.","The operator's markup lives separately from the rate and applies on top of it at its own level."],"example":"A merchant reports a divergence in a converted amount. The windows show two effective rates for one pair with overlapping periods: one entered per hundred units, the other per one. The conversion took the first match. The older rate is closed with an end date and the divergence stops.","tips":["Close the previous rate with an end date before entering a new one: cheaper than untangling an overlap afterwards.","Say the nominals out loud: 'per hundred' and 'per one' differ by two orders in the operation amount.","Open a new pair with the wizard: it checks window overlap before writing."]},"aggregates":{"title":"Counters and limits","summary":"Operation counters over a time window: window length, grouping dimension and selection conditions. Velocity limits and quotas are built on them.","whenToUse":"When configuring velocity restrictions and when investigating why a limit fired.","concepts":["A counter measures a rolling window, not a calendar period: a limit of 'five per hour' releases the first operation an hour after it, not at the top of the next hour.","The grouping dimension determines what is being counted: by card, by device, by recipient. The same limit catches different things in different dimensions.","Selection conditions narrow which operations count. Too broad a selection produces false positives on legitimate customers.","Changing a counter does not recompute the past: the new window starts filling from the moment of the edit."],"example":"A customer reports a decline after several payments in a row. The counter shows the limit is set per device rather than per card: the customer paid from one phone with several cards and hit the restriction. The dimension is corrected and the false positives stop.","tips":["Choose the grouping dimension by what you are actually restricting: card, device or recipient.","Explain the rolling window to customers: 'wait until the next hour' does not apply here.","After editing a counter, let the window refill â the past is not recomputed."]},"walletsManagement":{"title":"Virtual accounts","summary":"The organisation's internal wallets: purpose, currency, balance and linked terminals. This is where you see where funds are credited from and where payouts come from.","whenToUse":"When setting up an acquiring or payout environment and when investigating where a credit went.","concepts":["A wallet is bound to a currency: an operation in another currency will not credit to it, and a terminal with a mismatched currency drops out of selection.","The provider's wallet and the organisation's wallet are different things: the first reflects funds on the channel's side, the second your ledger balance.","A terminal references its wallet by name. An empty or wrong reference silently removes the terminal from routing selection.","A wallet balance is a ledger figure: it agrees with reality only after reconciliation against the provider's statement."],"example":"Payments on a new terminal do not go through even though the provider is enabled. On the terminal card the provider wallet name is empty â the terminal silently drops out of selection. Once the reference is filled in, payments run and credits appear on the right wallet.","tips":["Check the provider wallet name on the terminal first: an empty reference produces neither an error nor payments.","Match wallet and terminal currency â a mismatch removes the channel from selection.","Reconcile the ledger balance against the provider statement: divergences are found by reconciliation, not by recounting."]},"exchangeControl":{"title":"Exchange control","summary":"Limits and requirements by country: daily and monthly limits, the documentary evidence threshold and the reporting threshold, plus a pre-check of a specific operation.","whenToUse"
1:"Before a large currency operation and when handling a regulator's demand for supporting documents.","concepts":["The documentary evidence threshold and the reporting threshold are different figures: the first requires documents from the customer, the second a report to the regulator.","Limits are set by country and customer type: the same amount falls under different rules for an individual and a company.","The pre-check runs before the operation and answers whether it will pass and what is needed. That is cheaper than untangling a rejection afterwards.","The purpose of the operation affects the requirements: the same transfer on different grounds needs a different document set."],"example":"A customer is about to send a large sum abroad. The operation is run through the pre-check with country, customer type, amount, currency and purpose. The answer shows the amount is above the documentary evidence threshold â documents are requested before the payment rather than after it is stopped.","tips":["Pre-check large operations in advance: a stopped payment is worse than a deferred one.","Distinguish the two thresholds when talking to a customer: documents are for them, the report is for you.","Establish the purpose precisely: the required document set depends on it."]},"intakeConfig":{"title":"á¨ááªáᶠááá á« ááá³","summary":"áµáá
á± ááªáá¶á á¥áá´áµ á¥áá°ááá áᦠáá¥á«áá³áá± ááá« á á ááµ áá á áµá«á» ááá á áá¥á³ áá° ááá á¦áá³á¢ á áµá«á» á¨áá°á á± á ááµ á¨ááá ááááá á¨áá«á áá¨ááá«á á¥áá
áááááá¢","whenToUse":"á¨ááªáᶠááá á«á á²ááá©á ááá«áá½ á«áá°á á á á áµá«á» á²á°áá±á¢","concepts":["á¨á ááµ áá á áµá«á»áá½ á¨áááᥠáááá ááá«áᦠá¥á«áá³áá± ááá« á á«á± á áµá«á» áá°áá³áᣠáµááá
á á á«á£áª ááá á¨ááááá© á ááµ á¨áá¹á
áááᥠáá á ááááááᢠááá á áá ááá°á¥á°á¥ á¨áá¨áá á¨ááµááá ááá« ááá¢","áá¥á³ ááá á áá
á áá á«áµáá«á â áááá¡ á áµááµá á ááá á¦áá³ áá ááᢠááµááá½ áá áá½ áá
á¥á¸áá áááá«á³á á áá«á ááᦠáá°á¥á°á¥ á¨áá á á«á± áá áá£áá¢","á¨á ááµ áá á áµá«á» áá¥áá¥á á¨áá¨ááá áµ á áááááµ ááᢠááá á«ááá ááá³á á¥áá° áá¥á³ ááá á áá á«áᣠáá©áá±á á á°áá£á á áááá ááá³ ááµá áá³á«áá¢","á¨áµáá
á± á
áá¥á á¨áá¨á¨á» áá á áá°ááᦠá°áááá áá½á¨á áá½ááᢠá«áá°á© á°ááááá á áá áᣠá áááá¬á á á áá áµááááᥠá¨ááá á« áá´á á ááá« ááá«á áá½ááá¢"],"example":"áµáá
á± á á ááµ áá á áµá«á»áá½ ááá ááᣠááá áá áµááá½ ááá«áá½ á¨áá°á¥á°á¢á« ááªá á áá¸áááᢠá¨áá á á¨áááá áá°á¥ á«áá á¨á°áᨠá°áááá áá á©á á á
áá¥á© ááµá¥ á¨ááá áááá áá áá¥á³ ááá áá á á¥á©á¢ á«áá°á© áµááá½ áá áá½á áá°áá« á°áááá ááá«á â á áá¥á³ áá° á¦áá³ áá°áá³áᣠá¨á°áá©áµ á á ááµ áá á áµá«á»áá½ ááá¥ááá¢","tips":["áá¥á³ ááá á á¨á°ááá ááá á¦áá³ áááááᢠá áááá© ááá«áá á«ááá³á á¥áá á
áá¥á©á á áá°áá â á¨á¦áá³áá½á áááááµ ááá áááá¨á±á¢","á áá³á áá á¨á°áá á¨á° á á
á£á« á¨á°ááᨠá¨á áµá«á» áá£áªá« á á
á«á¢ á²áá á¥á» áá á«áᢠá«áá± ááá áá° áá
á°á áµááµ á¦áá³ ááá³áá¢","á¨áá«á áá¨ááá«á ááááªá« á áááá¨áµ ááá³ á á¥á©áµá¦ á¨áµáááµ á®ááµá«áµ á¦áá³áá½ á¨áá á áµá«á» á ááá ááááµ áááááá¢"]},"routingCascade":{"title":"Routing cascade with fallback","summary":"The wizard assembles a chain of terminals sharing one route key: a primary provider plus one or more fallbacks that take the operation after a failure. The terminals are created for real â through the same request the terminal creation page uses â and are switched on immediately by default. Priority here is not a position in a list but an attempt number: the platform selects terminals with priority 0, then priority 1 on failure, and so on, so a gap in the numbering silently breaks the chain.","whenToUse"
1:"When one direction of a partner â currency plus operation type â has to be served by more than one provider: a fallback in case the primary fails, or traffic split across several channels. You come here already knowing the providers and their connection parameters; the environment (test or prod) is chosen on the first step, and the finished chain is inspected in the terminals list and the routing editor.","concepts":["Route key â partner, currency, operation type and environment. Terminals sharing one key form one chain; the wizard stamps the key on all of them at once, and afterwards it can only be changed by editing each terminal separately.","Priority is an attempt number, not a position in a list. The first attempt selects terminals with priority 0, the second priority 1, and so on. The wizard numbers them in sequence â primary 0, fallbacks 1, 2, 3 â but a terminal added later with priority 5 next to a three-link chain will never see traffic. The routing simulator evaluates one attempt level at a time, so it will not show you the whole chain.","Weight (0â100) splits traffic between terminals of the same priority: the pick is random with odds proportional to the weights, and they need not add up to 100. A wizard-built chain has exactly one terminal per level, so weight acts as a switch â a terminal with weight 0 is dropped from the selection entirely.","The provider fee is set per terminal, the merchant fee once for the whole chain, on the limits step. Otherwise what the merchant is charged would depend on which fallback happened to fire. The percentage is typed as a percentage with the basis-point conversion shown under the field (1.8% = 180); the fixed part and the limits are in minor units of the currency.","Provider params is JSON, and the selection also reads the allowed payment systems from it. Without a payment_system_type key the terminal counts as a card terminal (bank_card), so for SBP or a wallet you write it in by hand: {\\"payment_system_type\\": [\\"sbp\\"]}.","Amount limits and route tags are shared by the whole chain. An operation outside the min/max range finds no terminal in the cascade at all, and a tag does not narrow traffic by itself â it only lets an operation that names a route reach its terminal. In the routing editor the tag has to be picked in the filter: without it the editor lists only terminals that carry no tags.","Terminals are created one by one, in order. A failure on the third does not undo the two already created: they stay in the terminals list, and pressing «Create cascade» again builds the chain a second time, as duplicates."],"example":"A partner needs a fallback for card payments in roubles. Route key: partner Romashka (ID 42), RUB, payment, environment test. Primary terminal â an acquirer with the general wallet and a 1.8% provider fee; first fallback â a second acquirer at 2.1%; second fallback â a local gateway at 2.4%. On the cascade step you keep the order 0 -> 1 -> 2 and weight 100 on all three. On the limits step you set the range 10,000â50,000,000 minor units, that is from 100 to 500,000 RUB, a merchant fee of 2.5% inside the amount, and the tag cards. You tick «activate terminals immediately after creation» and press «Create cascade» â the wizard answers with three terminal ids. You open the routing editor, filter by the partner, RUB, payment, test and the cards tag, and see the chain in priority order.","tips":["Skipping the limits step leaves the maximum at 1,000,000 minor units â 10,000 RUB â and anything above that finds no terminal in the chain. For a production contour set the range by hand.","Weight 0 does not demote a terminal in the queue, it removes it from selection. To close a channel temporarily, clear the terminal's active flag instead of zeroing its weight.","If creation broke off midway, check the terminals list first: part of the chain already exists, and pressing the button again produces duplicates under the same key.","For the production environment untick «activate terminals immediately after creation»: it is convenient to assemble the chain in advance and switch it on in an agreed window.","Change the chain order on the terminals themselves. Dragging in the routing editor rewrites priorities as 100, 90, 80, while selection walks attempt numbers from zero â after such a reorder the chain no longer assembles."]},"directMigration":{"title":"Direct integration migration wizard","summary":"The wizard moves no traffic and creates nothing on the platform â it produces a document. An inventory of the live direct contracts, a decision on each, traffic shares by stage of the parallel period, the full cutover date and the rollback condition add up to a plan: it is shown on the last step, kept as a draft in the browser and exported as migration-plan.md. The point of the plan is that the criteria for advancing and for rolling back are agreed before the migration starts, rather than
1invented at the moment something goes wrong.","whenToUse":"When a client arrives with live direct contracts and real volume: nothing can be switched over at once, so both contours have to run side by side for a while. The wizard is walked before any setup: terminals are created by the payment acceptance setup wizard, traffic shares by the routing cascade wizard, and both contours are reconciled by the provider statement ingestion wizard â the last step links to all three.","concepts":["A decision per integration â migrate to the platform, keep the direct contract, or retire it. A platform terminal is picked only for the migrating ones; for the others the column shows a dash.","Monthly volume is a plain number with no unit; it only feeds the migrating-volume share. So every row must use the same unit, or the share will lie.","The contract end date is not a reference field. The integration whose contract expires first is migrated first, otherwise it has to be extended just to cover the parallel period. The date does not reach the exported plan â the table keeps provider, method, volume, decision and terminal.","A migration stage is a traffic share on the platform. What allows the move to the next stage is the success rate and the reconciliation gap, not elapsed calendar time.","The cutover date and the rollback condition are mandatory â the cutover step will not let you past without them. The condition is stated as a number and a duration: «below 98% for two hours straight», not «if things go badly». The owner field is optional.","The plan is Markdown text: a table of integrations, the parallel period parameters, a cutover section. «Save plan» stores a draft in this browser, «Export file» downloads migration-plan.md. Rows without a provider name do not make it into the plan, and the inventory step will not let you past until at least one row is filled in."],"example":"The client has three direct contracts. A bank acquirer, cards, volume 12,000,000, contract until 30 November â migrate, mapped to a terminal that already exists. A wallet, 3,000,000 â migrate, but no terminal yet. A local gateway, 800,000, contract until 2027 â keep direct. The wizard counts: two integrations migrating, 95% of volume moving, one terminal still to be created. Parallel period â 6 weeks, minimum success rate 98%, acceptable reconciliation gap 0.1%, daily reconciliation of both contours. Stages 5%, 25%, 50%, 100%. Full cutover on 1 December, owner â the head of payments, rollback condition: the success rate stays below 98% for two hours straight and traffic returns to the direct integration without further approval. You save the plan and export the file for sign-off.","tips":["The draft lives in this browser on this machine: a colleague cannot see it and it will not open at another workstation. If several people sign the plan off, export the file.","«Back to the start of the plan» jumps to the first step but keeps everything entered â there is no blank form in the wizard, extra rows are deleted by hand.","The terminal is picked from the ones that already exist, and the list loads the first hundred: with more terminals than that, the one you need may be missing from the dropdown. Until a terminal is there the plan marks the row «terminal not created yet»: the parallel period does not start before the terminal exists and has passed a test operation.","Stage shares are entered as whole numbers: an empty stage field blocks the move to the next step.","The parallel period must cover at least one full settlement cycle with the old provider, and the direct contracts are worth keeping alive for one more cycle after cutover â that is the price of being able to come back."]},"checkoutPublish":{"title":"Hosted checkout publishing","summary":"The wizard creates a payment page configuration and publishes it right away: the page gets a version number, a public access token and a ready payment link. Publishing is not just saving â every publish bumps the version and issues a fresh token, and with it a fresh link, so the one handed out earlier stops opening. The token is valid for twenty-four hours from the moment of publication.","whenToUse"
1:"When a merchant needs a ready payment page without building its own form: the link goes on a site, into an email, or straight to a buyer. The page itself does not process the operation â it opens the payment form, while the payment travels the routes already configured, so the partner's payment acceptance must already work by this point.","concepts":["The page address (the «Slug» field) is part of the link and a unique name within the organisation. Only lowercase latin letters, digits and hyphens are allowed, 3 to 50 characters. The wizard only requires a non-empty value; the platform enforces the format, and a bad address surfaces only as a generic publishing failure.","Publishing is two actions in a row: the configuration is created, then published. Publishing bumps the version and replaces the access token, which is why the previous link stops working. That is also how an issued link is revoked.","The access token is the public part of the link, not a secret. It lives twenty-four hours from publication; after that the page answers with an error and the link is refreshed by publishing again from the Payment pages section. The wizard offers no setting for that lifetime.","The notification signing key is sent to the platform and never comes back â there is nowhere to look it up afterwards, and a lost key is replaced with a new one. The notification address is accepted over https only, and the step itself can be skipped: with no address, notifications simply are not configured.","The logo is likewise accepted over https only, and colours only as six-digit HEX such as #004D40. A mistake in any of these fields produces the same generic publishing failure, without naming the guilty field.","The form composition comes down to three switches: email, billing address and the page footer. Card fields are not configurable and are always present â the payment widget renders them itself.","The product and the payment link are standalone objects, not parts of the page. Both steps are optional, are created immediately by «Create and continue», and live in the Products and Payment links sections; amounts in both are entered in minor units of the currency."],"example":"A merchant needs a page for a single service. Address â bakery-checkout, an internal description, logo served over https, primary colour #004D40, accent #FFB300, variant compact, theme light, input style underline, language ru. You keep email and the footer and switch the billing address off. Notification address â https://shop.example.com/webhooks/checkout, and you set your own signing key, saving a copy on your side straight away. You press «Publish page»: it comes out as v1 and you copy the payment link and the token. Then you add the product: name «Annual subscription», a short description (the step will not pass without one), price 149,000 â that is 1,490.00 RUB â quantity 1. The payment link is made for the same 149,000 RUB, type fixed, methods bank card and SBP. The final step shows the ready link, version v1 and both marks: product and link created.","tips":["Write the address in lowercase latin letters, digits and hyphens: bakery-checkout, not Bakery_Checkout. The wizard does not check it, the refusal arrives at publish time, and there is nowhere to change it later â the field is locked when editing in the Payment pages section.","If publishing failed and pressing again returns the same error, the configuration was most likely already created and has taken the address. Open Payment pages and publish it from there instead of inventing a new address.","The signing key is entered once and never shown again. Store it on your side before pressing publish â it cannot be retrieved from the platform.","The link lives twenty-four hours and republishing issues a new one. Before printing it in a leaflet or baking it into a QR code, work out who refreshes the merchant's link and how often.","Product price and link amount are entered in minor units: 1,490.00 RUB is 149,000. The field label says «kopecks» whatever currency you picked."]},"obConsent":{"title":"Consent Issuance and Authorization","summary":"The wizard assembles an Open Banking consent granting a TPP access to a customer's accounts: the provider from the registry, the permission set, the account list and the validity window. The consent is created in an awaiting-authorization state and is then either authorized or rejected on the same screen â both actions are irreversible and each needs its own confirmation tick. The cost of a mistake is access wider than
1intended: the wizard cannot narrow an authorized consent, leaving revocation and a fresh pass as the only route.","whenToUse":"When a provider already present in the registry needs access to one specific customer's accounts. The provider must exist and be active beforehand â inactive ones do not appear in the list. Authorization issues an authorization_code that gives the provider access to the data; the consent state is then looked up in the Consents section.","concepts":["The provider is picked from the registry and only with active status â the list is fetched filtered by status and capped at the first hundred entries. A consent belongs to exactly one provider, and the provider cannot be swapped after creation.","Scope inheritance applies while the set is empty: the first time you pick a provider, its scopes are pre-filled. If you go back and pick a different provider, the set is not overwritten â adjust it by hand on the permissions step.","Rights come in two layers. Scopes (accounts, payments, funds-confirmation) are mandatory, at least one, or the wizard will not move on. Granular permissions (ReadBalances, ReadTransactionsDetail and the rest) are optional and refine what exactly the provider reads inside a scope.","The account list is not sent at creation â it is sent at authorization. The «all accounts» mode sends no list at all, so every account the customer links is covered. The «specific accounts» mode takes identifiers one per line or comma-separated, and the counter under the field shows how many were parsed.","The date fields mean different things. «Expires» is a point in time: the browser reads it in your local time zone and sends it as UTC. «Transactions from/to» are the boundaries of the period the provider will see operations for. «Valid from» is not sent to the backend at all â the consent takes effect as soon as it is authorized.","After creation you can still walk back through the progress bar, but nothing changes server-side: permissions and dates were sent at creation. The single exception is the account list, which is sent at authorization, so editing it still has effect."],"example":"«Fintech App Ltd» needs access to two of a customer's accounts for an expense-tracking service. You pick it from the list â accounts and payments are pre-filled; you drop payments and keep accounts only. You tick three granular permissions: accounts basic data, balances and detailed transactions. On the accounts step you switch to «specific accounts» and paste two identifiers â the counter reads «Accounts: 2». For dates: expires 30 November 2026, 23:59, transactions from 1 June to 30 November 2026. You press Create consent, copy the identifier from the message, tick the confirmation and hit Authorize â both accounts go out with the request, and the final message shows who authorized it.","tips":["Copy the consent identifier right after creation: the Consents section only offers lookup by identifier, there is no consent list there.","If the permission set turns out wrong after creation, do not authorize. Press Reject and run the wizard again â an authorized consent cannot be narrowed here.","Switching to «specific accounts» and pasting nothing behaves exactly like «all accounts»: an empty list is not sent with the request.","«Expires» is entered in your browser's time zone and stored as UTC. If you need end of day in the customer's time zone, work that out before authorizing, not after.","The wizard keeps nothing between visits: leave the page before creation and the permissions, accounts and dates have to be entered from scratch."]},"tppOnboarding":{"title":"TPP regulatory onboarding","summary":"The wizard registers a third-party provider in the Open Banking registry: profile, regulatory roles, regional standard, certificate-based identification and OAuth2 redirect URIs. The platform then issues a client_id / client_secret pair, and the secret is displayed exactly once â neither the wizard nor the registry will show it again. A mistake in roles or redirect URIs does not surface here; it surfaces on the provider's first authorization attempt.","whenToUse"
1:"When a provider has obtained its regulatory authorization and asks for access to your APIs. It runs before consent issuance: until the provider is in the registry there is nobody to issue a consent to. Start in the sandbox and register production as a separate entry â the environment is chosen on the first step and the wizard never changes it afterwards.","concepts":["Roles drive scopes. AISP reads accounts and transactions, PISP initiates payments on the customer's behalf, CBPII confirms funds availability for a card. Each role maps to exactly one scope (accounts, payments, funds-confirmation); scopes cannot be picked independently of roles, and at least one role is required.","The standard trims the roles. PSD2 and UK Open Banking allow all three, Open Finance Brasil allows AISP and PISP only. Roles are chosen before the standard, so an incompatible role is dropped when you press Next on the standard step: the wizard warns you in advance, showing the scope of the role about to go, but it changes the set itself.","Identification has two parts. The certificate DN is mandatory under every standard and must match the certificate the provider presents on mutual TLS. The Software Statement (UK OBIE SSA) is mandatory for UK Open Banking only; for PSD2 and Brazil it is optional.","The client type decides how authorization works: confidential (the default) means a server-side application that stores the secret itself; public means a mobile or single-page application using Authorization Code + PKCE.","Redirect URIs are entered strictly one per line, at least one is required. The wizard only trims surrounding whitespace and sends them as typed: a comma is not a separator and ends up inside the URI, while a trailing slash, a different port or http instead of https will be rejected at authorization time.","The secret is issued once. There is no second display in the wizard or in the registry â the registry offers suspend, revoke and delete for a provider, but not re-issuing the secret. A lost secret means registering again."],"example":"You register «Fintech App Ltd», contact e-mail [email protected], environment sandbox. You tick AISP and PISP, and the resulting scopes block shows accounts and payments. You leave the standard at PSD2, so both roles survive. In Certificate DN you paste CN=Fintech App Ltd,OU=PSDGB-FCA-123456,O=Fintech App Ltd,C=GB and skip the Software Statement â PSD2 does not require it. You leave the client type confidential and enter one redirect URI, https://app.example.com/callback. You tick the one-time-secret acknowledgement (the button stays disabled without it) and press Register TPP: the TPP ID, client_id and client_secret come back, each with a copy button. You copy all three into secure storage and move on to consent issuance â the provider is now in the list.","tips":["Store the secret before you leave the page: there is no recovery, and a lost secret means a new registry entry.","Check the final scope set in the summary on the last step, especially if you changed the standard after picking roles â an incompatible role has already been dropped by then.","Put one redirect URI per line and verify them against what the provider's application actually sends: matching is done on the full string, and the wizard does not validate them.","The environment stays a record field only: consent issuance filters providers by status, so sandbox entries sit next to production ones â tell them apart by name.","After registration, walking back through the steps changes nothing â the entry already exists. To onboard the next provider press Register another TPP and the form resets."]},"verticalGoLive":{"title":"Vertical Go-Live â industry vertical","summary":"The wizard switches on an industry profile: for the chosen vertical it creates one business rule per MCC group in the rules engine. The rules set a risk profile on the operation, add an enhanced identification level when the enhanced profile is chosen, and add an industry report code when reporting is on. They are created enabled and match on the category code rather than on a particular merchant, so the MCC set is worth checking before the run, not after.","whenToUse"
1:"When a merchant enters an industry segment â gambling, travel or digital goods â and its operations need an industry profile. The wizard does not bind terminals to MCCs and does not switch on report delivery: the Terminals and Reporting sections come next, and links to them, along with a link to Business rules, appear on the completion screen.","concepts":["A vertical is a group of MCC codes plus an industry report code. Gambling and betting is the single code 7995 with the TSUPIS report; travel and air is the continuous range 3000â3999 plus codes 4511 and 4722 with the BSP / IATA report; digital goods and SaaS are codes 5734, 5815, 5817, 5818 with the Usage / MRR report.","One rule per code group. Conditions inside a rule are joined with AND, so a range and a list cannot share one rule: the travel vertical produces two rules, the others one. The count is shown in the summary before you commit, in the «rules to be created» row.","The rule matches on MCC, not on the merchant. The condition compares the category code only, and the rule runs in the payment context within the organisation, so any operation in the organisation carrying that code picks up the industry profile.","The rule sets facts rather than blocking operations: the risk profile, plus an enhanced identification level under the enhanced profile, plus the industry report code when reporting is on. Decisions based on those facts are taken by the dedicated sections.","Priority 50 and an unbroken chain. The engine walks priorities from lower to higher and ordinary rules are created at 100, so the industry profile applies first; a match does not stop the chain, and the general rules still run afterwards.","Rules are created enabled and apply to operations from that moment â there is no deferred start. Everything is reversible, though: rules can be edited, disabled or deleted in the Business rules section, where their names begin with «ÐеÑÑикалÑ:»."],"example":"A travel-agency merchant starts selling air tickets. On the selection step you take the travel and air card â the MCCs 3000â3999, 4511, 4722 are shown under the name. You leave the risk profile standard (it is preselected): the enhanced one belongs where operations require enhanced identification, typically gambling. You leave industry reports on, and the caption reads BSP / IATA. The summary shows the vertical, the standard profile, reporting enabled and «rules to be created: 2». You press Create vertical rules â the wizard creates one rule for the 3000â3999 range and one for the pair 4511, 4722, both at priority 50, and reports «rules created: 2». From there the links take you to Terminals, to bind the merchant's terminals to the right MCC, and to Reporting, to switch on the BSP schedule.","tips":["Rules are created one after another. If the second travel rule fails, the first one already exists â the wizard shows the error, but removing what was created is a manual job in the Business rules section.","Within one visit the wizard will not create a second batch: after success the button turns into a link to the wizard list. Re-entering the wizard is not restricted, however â you get a second batch of rules with identical names and the engine runs both.","The risk and reporting steps can be skipped with Next, which leaves the defaults in place: standard profile and reporting enabled. Check both in the summary before you commit.","Enabled reporting only puts a code into the operation's facts. The delivery schedule itself is switched on in the Reporting section: without it the code is set but no report is produced.","Before the run, check whether other merchants in the organisation carry the same MCCs: the rule does not tell merchants apart and will cover their operations too."]},"recipientExport":{"title":"Recurring registry export to recipient wizard","summary":"The wizard sets up a registry recipient configuration: which transactions to export, in what file, in what email and on what schedule. Between the setup and the schedule sits a mandatory check â a preview of the rows for a chosen date, and optionally a real email send. The schedule can only be switched on after a non-empty preview: an empty registry arriving every morning is usually discovered by the recipient, not by you.","whenToUse"
1:"When a partner, a provider or an accounting team should receive the transaction registry on their own, without asking support. Come here once the scope of the export and the addresses are agreed; afterwards the work continues in Registry recipients and Registry exports.","concepts":["Selection filters â provider, partner IDs, terminal IDs, operation types and the «reconciled only» flag. An empty field means «all»: a configuration with no filters exports the entire flow to the recipient.","The preview is not built the way the export is. It looks only at provider, environment and date, requests at most 25 transactions, and filters operation types after loading, on the interface side; partners, terminals and «reconciled only» take no part in it.","«Send now» is not a rehearsal. The button creates the recipient configuration and sends the registry for the chosen date to the listed addresses. It unlocks right after any preview, including an empty one, and a sent email cannot be recalled.","The condition for the schedule is a non-empty preview. While the preview returns zero rows, the recurring-delivery toggle stays unavailable and the wizard sends you back to the trial send.","The cron expression and timezone are entered on the Delivery step and switched on at the Schedule step. If the expression is left empty, no schedule is saved and the configuration stays on manual sending.","The configuration comes into existence the moment you press «Send now» â even if the email then fails to leave. After that, finishing the wizard updates only its schedule and timezone; change format, filters and addresses in Registry recipients."],"example":"Partner Romashka needs a daily registry for the previous day. Name «Romashka â daily registry», recipient type «Partner», environment prod, provider mtsbank, partner IDs 17, operation types payment, payout. Format CSV, semicolon delimiter, Windows-1251 encoding because their accountants open the file straight in Excel; filename template report_{{date_from}}_{{date_to}}.csv, columns id, provider, amount, status, started, summary and header row enabled. The email goes from [email protected] to [email protected] with a copy to [email protected]; on the same step you set cron 0 9 * * * and timezone Europe/Moscow. On the trial step the date is already filled with yesterday, 20 August: the preview returns 25 rows, so the selection is alive. You press «Send now», the email leaves and an export id appears. On the schedule step the toggle is unlocked â you enable recurring delivery and finish, and the schedule is applied to the configuration that already exists.","tips":["The preview row count only tells you the selection is not empty; it is not an estimate of registry size â at most 25 transactions are requested and the first ten are shown.","Reread the address list before pressing «Send now»: the email reaches the real recipient. For a rehearsal put your own address in and set the real one later in Registry recipients.","Choose the encoding for the recipient: Windows-1251 for those who open the CSV in Excel directly, UTF-8 for those who load the file into their own system. For XLSX the delimiter and encoding are not applied at all.","The {{date_from}} and {{date_to}} placeholders work in the filename, the subject and the body. Without them every export arrives under the same name and the recipient mixes up the days.","The configuration is created active, but with no cron expression it sends nothing. A schedule can be added later in Registry recipients â no need to run the wizard again."]},"reconIngestion":{"title":"Connecting a Provider Registry to Auto-Reconciliation","summary":"The wizard ties two things together: the rules for parsing the registry file and the source the files are fetched from. Then it verifies the resulting chain â connection to the source, parsing of a sample file, and a trial reconciliation of the parsed rows against 4pay.online transactions by external id. The source is created disabled and is switched on only on the final step, so nothing is fetched or reconciled until then.","whenToUse"
1:"When a provider has started sending a registry and the daily reconciliation should come off your hands. You will need a real sample file and access credentials for the mailbox or FTP/SFTP if the files are to be fetched automatically. After the wizard the work lives in Registry imports and Registry reconciliation.","concepts":["The provider ID column is the key to the whole reconciliation: its value is matched against the transaction's external id (outertxid). Point it at the wrong column and the entire file lands in «missing in 4pay.online».","Four columns are mandatory: provider ID, amount, date and status. RRN and card number are optional and take no part in matching â rows are looked up by the external id alone.","Column names are typed in by hand â exactly the headers that appear in the provider's file. «Skip lines from the top» cuts off the technical preamble that precedes the useful data.","Two objects, two creations. «Create and continue» creates the parsing rules on the first step and the source on the second, and every press creates a new object: go back, press it again, and you have a duplicate.","The source is created disabled on purpose. Until you switch it on explicitly on the last step, the schedule does not run and files are not fetched. Switching it on is reversible â the toggle lives in Registry sources.","The preview and the control reconciliation save nothing: the file is parsed on the fly, rows are compared with transactions for the chosen period, and no import and no reconciliation marks remain afterwards.","«Missing in registry» counts 4pay.online transactions in the chosen period that are absent from the uploaded file. If the file covers one day and the period covers a week, the number will be large and say nothing."],"example":"Provider Acme emails its registry every morning. Parsing rules: name «Acme registry (CSV)», provider acme, environment test; provider ID column â order_id, amount â amount, date â created_at, status â state, RRN â rrn. Semicolon delimiter, Windows-1251 encoding, skip 1 line from the top, date format DD.MM.YYYY HH:mm:ss. The source is «Acme â registry mailbox», type «Email (IMAP)», host imap.example.com, port 993, folder INBOX, schedule 0 6 * * * in Europe/Moscow. The connection test passes; you upload yesterday's file and 342 rows parse, with dates and amounts landing in the right places. The control reconciliation defaults to the last week and «missing in registry» shows 1,240. You narrow the period to 19 August: 336 matched, 2 missing in 4pay.online, 4 amount mismatches and no status mismatches â all 342 rows are accounted for, so order_id is mapped correctly. On the last step you leave the activation checkbox ticked and finish: from six in the morning the files are fetched on their own.","tips":["Use the file the provider actually sent, not the sample from their documentation: the delimiter, the encoding and an extra preamble line are what usually differ.","Match the control reconciliation period to the file's date. The default is a week, and transactions from the other six days land in «missing in registry» even though the setup is fine.","An «amount mismatch» is more often about notation than about money: amounts are compared character by character, so 1500 against 1500.00 already counts as a mismatch. Statuses, by contrast, are normalized â success, completed and approved are treated as the same thing.","Do not walk the first two steps again to fix something: every «Create and continue» creates another set of parsing rules and another source. Edit what already exists in Registry configs and Registry sources, and delete the leftovers there.","Run the chain on test first. The same wizard is repeated for prod later, and a column-mapping mistake costs nothing on the test contour."]},"bankLaunch":{"title":"Banking Environment Launch Wizard (BaaS)","summary":"The wizard converts an organization from fintech mode into a bank and immediately builds out what a bank cannot work without: details, supervisory reporting and staff roles. The conversion is irreversible in business terms: a route back exists in the system but is treated as an emergency procedure. The data region is chosen here once â it determines the regulator, the license list, the supervisory integrations, and later the region of every account the organization opens.","whenToUse"
1:"The organization has obtained a license and must start operating as a bank: opening accounts, running customer checks, reporting to the regulator. Before the wizard the organization exists and works in fintech mode; after it, the first clients are taken on for banking service and their accounts are opened.","concepts":["The data region is the storage jurisdiction. It drives the regulator (shown under the field), the license list on this step and the supervisory integrations on the next one. Changing the region clears the licenses already ticked. Pick a currency-zone country by its own code: its chart of accounts and reporting come from the zone, shown in brackets in the list.","The conversion is the wizard's only point of no return. Only fintech-type organizations are listed: once converted, the organization drops off the list and cannot be run through the wizard again.","Confirmation by typing the name requires an exact match with the selected organization, otherwise the «Convert to bank» button stays disabled. Until the conversion is done the step has no «Next» button, and the progress circles do not allow jumping forward.","Bank details are saved as a whole, not field by field. The form opens empty and pulls nothing from the organization, so an empty BIC or correspondent account is sent as an empty value and overwrites whatever was stored before.","Supervisory credentials are written into the organization configuration â the same place the organization integrations page writes them. A card in which you filled even one field replaces the stored credentials for that system entirely; untouched cards are left as they were.","Roles are assigned by the client_id of an existing platform client, one request per row. Rows without a client_id are skipped, and the step can be passed empty."],"example":"«Mars Finance» runs in fintech mode and has obtained a banking license. You pick it from the list, set the data region to Russia (RU) â the regulator fills in as CBR â choose the Growth tier and tick the «CBR banking license». On the conversion step you type «Mars Finance» exactly and press «Convert to bank»: the organization type becomes bank. Then you enter the details: BIC 044525999, correspondent account 30101810400000000999, central bank ID 1234, license No. 3999 dated 14 March 2026, and press «Save and continue». For Russia the supervisory step opens the Rosfinmonitoring card (FES messages and operation reports under 115-FZ): you fill in the API URL, the key and the entity ID. In roles you add two staff members by client_id: operator and finance. The summary shows bank, RU, growth, one license and two assigned roles.","tips":["The wizard asks for the data region only once â at conversion time â and there is no way to change it afterwards. The tier and licenses stay editable: the tier can be upgraded and downgraded, licenses added and revoked, in the BaaS management section.","Do not walk through the details step on a «I'll fill it in later» basis if details are already stored: the form opens empty and saving sends empty values over them.","Fill in a supervisory system card completely: a URL without the key overwrites the stored pair as a whole and the key is lost.","Roles are applied one by one, in sequence. If a row with a non-existent client_id fails, the previous ones are already assigned: delete the successful rows and retry only the failing one."]},"baasClient":{"title":"BaaS client onboarding","summary":"The wizard walks the client through the mandatory order: identity check, risk rating, account opening, putting the account to work. The order is not decorative â the account form stays locked until the client's case is approved. Screening runs on the platform side and takes time, so the wizard is built for coming back: the case status is refreshed manually with a button and the work can resume later.","whenToUse":"When a case already exists for the client and has to be carried through to a working account. The wizard does not create the case itself â it arrives through the platform API. After the wizard the account is ready to receive funds and a card can be issued against it.","concepts":["The client case (KYC case) is picked from existing ones: the wizard loads up to fifty cases, the step has no search, and there is nowhere in the operator's cabinet to create a new case. Each case is listed by the customer identifier, the customer type (individual or legal_entity) and the status.","Screening â sanctions, politically exposed persons (PEP) and adverse media â starts with a single button and runs on the platform side. The result does not reach the wizard by itself: the case status has to be refreshed with the «Refresh status» button.","The r
1isk rating and the case decision are sent in one request â you cannot set the rating without recording a decision («Under review», «Approved» or «Rejected»). The «Skip saving» button in the bottom navigation moves past the step with no write at all.","An approved case is the only condition for opening an account: while the status is not approved, every field of the form is locked. The «Prohibited» risk rating shows a warning but does not lock the form.","The «Region» field on the account form only filters the currency list â it is not sent in the request at all. The account region is taken by the system from the organization's data region.","Putting the account to work depends on its status: «Activate account» appears only for a blocked or dormant account; for an account in pending there is no separate action â its state is polled with «Refresh status», while «Mark as activated» records a note inside the wizard and does not change the account status."],"example":"An enquiry from OOO «Veter» has produced a case with the status documents_required â the list shows it by the customer identifier, the type legal_entity and that status. You select it, assign an officer by their UUID, upload the incorporation documents and the proof of address, and start the screening. An hour later you come back and refresh the status â no matches. You set the risk rating to «Medium», the decision to «Approved», write the rationale into the notes and press «Save and continue»: the case status becomes approved. On the account step the fields unlock: type «Checking», region Russia, currency RUB, owner type pre-filled as «Organization», owner ID taken from the case, chart of accounts code 40702, IBAN left empty so it is generated automatically. «Open account» creates the account with the status pending; you refresh the status, see active, and the summary shows an approved case, medium risk and a working account.","tips":["If the client is not in the case list, no case has been created for them yet: the wizard only works with existing cases and shows at most fifty, with no search or filters.","Never pair the «Prohibited» risk rating with an «Approved» decision: the wizard will let it through and unlock the account form â the warning stays nothing more than a warning.","«Skip saving» on the risk step writes nothing: not the rating, not the decision, not the notes. To get them into the case, use «Save and continue».","Leave the IBAN empty unless you have a number reserved in advance: a manually entered number is sent for saving exactly as typed, typo included.","Until the account is open the wizard will not move on â the «Next» button on the account step stays disabled."]},"cardIssuance":{"title":"Card Issuance Wizard","summary":"The wizard issues a card against an already open customer account: the account fixes the currency and the customer, the card product sets the limit frame, and separate steps refine limits and features. Issuance is irreversible: a created card cannot be cancelled, only blocked. Limits are applied by a second request right after creation, so a failure at that point leaves the card already issued.","whenToUse":"When the customer has an active account in the required currency and needs a card â a first one or a replacement. Before the wizard the customer is onboarded and the account works; after issuance the card appears in the card issuing section, where its status and limits can be viewed but not changed.","concepts":["The account is the source of the currency and the customer. Only active accounts with a linked customer are listed, with a search by account number, IBAN or customer. The currency of the chosen account becomes the card currency and does not change afterwards.","Card products are filtered by the account currency and the active flag: products in another currency will not appear. The product supplies the default and maximum limits and pre-selects the card type, which can still be changed by hand.","All limits are integers in minor units: 500000 means 5,000.00. The field accepts digits only and has no decimal separator.","Limit rules are validated when you move on: daily above zero and within the product maximum; monthly, if set, not below daily and within the product maximum; single, ATM and online not above daily; contactless not above single.","The feature switches only build the summary shown before issuance: they are sent neither with the card creation nor with the limits. Creation sends the product, card type, customer, account, cardholder name and delivery address; the six limit values, contactless included, follow.","Issuance is three consecutive requests: create the card, apply the limits and, if ticked, activate it. The «Issue card» button unlocks only after the «I confirm issuing the card with these parameters» checkbox. The first request is irreversible: there is no cancel, only a block."],"example":"Customer Ivan Ivanov, account 40817810099910004123 in RUB, active. You select it and the card currency is fixed as RUB. The product «Classic Debit RUB» comes with a default daily limit of 5000000 and monthly of 50000000, with maximums of 10000000 and 100000000. The type is pre-filled as debit, the cardholder name is entered in Latin as IVAN IVANOV, the delivery address is a Moscow one. On the limits step you keep the daily at 5000000 â that is 50,000.00 RUB â lower the single limit to 2000000, the cash withdrawal limit (labelled «ATM limit») to 1000000, and set contactless to 100000, which otherwise stays at zero. Features: contactless, online and ATM stay on, international is switched off. You tick immediate activation, tick the confirmation and press «Issue card» â the card is created, masked ****1234, limits applied, card active.","tips":["Check the cardholder name and the delivery address before pressing «Issue card»: afterwards the card can only be blocked â the wizard cannot cancel or reissue it.","The contactless limit is not inherited from the product: it is pre-filled with zero, while single, ATM and online are set equal to the daily limit. Set it by hand if the card is meant to pay by tap.","Count the zeros: 5000 is 50.00, not five thousand. After issuance the mistake is only visible in the card issuing list.","If the card is created but the limits or the activation fail, the card is issued all the same. Pressing the button again issues a second one â fix the limits outside the wizard instead, through the card limits API."]},"correspondentRelations":{"title":"Opening correspondent accounts","summary":"The wizard opens a mirrored pair of accounts with one partner bank â NOSTRO, our account with them, and VOSTRO, their account with us â and writes the agreed reconciliation procedure into the details of both. The accounts are created exactly the way the account opening form creates them, so currency and number cannot be changed afterwards: a mistake is fixed by closing the account and opening a new one. The point of the flow is that the mirror never goes missing: a single account without its counterpart is a classic source of interbank breaks.","whenToUse"
1:"Once a correspondent agreement with the bank is signed and the pair has to exist before the first interbank transfer. Keep the bank's confirmed details and the agreed statement exchange procedure at hand; after the flow both accounts show up in the general accounts list.","concepts":["NOSTRO and VOSTRO are two sides of one relationship: NOSTRO holds our funds at the partner bank, VOSTRO holds their funds with us. Only NOSTRO provides cover for an outgoing transfer, which is why the pair is created as a whole.","The organization region on the NOSTRO step filters the currency list and nothing else. It is not sent with the request: the account region comes from the organization settings.","Currency and account number are set once. A later account edit accepts the interest rate, spread, limits and extra details, but neither currency nor number â an account in the wrong currency can only be closed.","An empty IBAN field is an instruction to generate the number on our side, not a skipped field. A number already issued by the correspondent bank is typed in manually.","A cross-currency pair is allowed and the wizard warns about it: reconciling a EUR NOSTRO statement against a USD VOSTRO stops being mechanical and requires conversion.","Reconciliation parameters â frequency, statement format, tolerance and auto-matching â go into the details of both accounts as the recorded agreement with the bank. They start no schedule. Tolerance is counted in minor units: 50 means EUR 0.50.","The interbank section keeps its own register of correspondent accounts, with balances, statements and reconciliation items. The wizard adds nothing there: it opens accounts in the general accounts register, so a freshly created pair will not appear on the interbank tabs."],"example":"You open a pair with a bank in Germany. Details: name Correspondent Bank Ltd, BIC CBLTDEFF â the wizard upper-cases it and checks its length â country DE. The organization region is Russia, so the currency list offers RUB, USD, EUR, GBP and CNY; you take EUR for NOSTRO and leave the number field empty. The wizard proposes the same currency for VOSTRO and you accept â the pair is single-currency. Reconciliation: daily, SWIFT MT940 statements, tolerance 50 minor units (EUR 0.50 for intermediary fees), auto-matching on. The button opens NOSTRO first, then VOSTRO, and the success message shows two account ids. The pair is then visible in the accounts list by type and currency.","tips":["The accounts are created one after another with no rollback: if VOSTRO fails, NOSTRO already exists. Pressing the button again gives you a second NOSTRO â open the missing account from the account opening form instead.","The BIC is validated by shape only: 8 or 11 latin letters and digits. A typo passes validation and surfaces on the first statement, so check the code against the bank's confirmation.","Tolerance is in minor units: 50 means half a euro, not fifty. The field starts at 0, which means only exact matches clear automatically.","The wizard does not edit an existing pair â a second pass opens new accounts. If the reconciliation arrangement changes, change it on the accounts themselves rather than re-running the flow."]},"externalBank":{"title":"External bank connection","summary":"The wizard walks the organization through connecting to someone else's bank as a third party provider (TPP): the Open Banking standard, the bank's connection details, an OAuth2 sign-in that redirects back to our address, the access rights and a test consent. The connection details are not stored on the server â they live in the browser session for the duration of the flow. Only one real record is written here, the test consent: it can be authorized or rejected exactly once, both actions are final and both end the wizard.","whenToUse":"When the bank has already issued your organization a client id and secret and registered the return address, and you need to confirm the integration holds together: the rights are accepted, the consent is created and authorized. Afterwards the consent is looked up on the consents page by its id.","concepts":["The standard defines the catalogue of rights, not the paperwork: PSD2 offers accounts, payments and funds-confirmation; UK Open Banking offers ReadAccountsBasic, ReadBalances, ReadTransactionsDetail and ReadBeneficiaries; Open Finance Brazil offers accounts, credit-cards-accounts, payments and resources. Changing the standard rewrites the entire list on the rights step.","The sign-in step comes before the rights step, so the first trip to the bank carries the default set: openid accounts. The progress bar only allows going back, so you have to complete the sign-in step, pick the rights on the next one and click back onto the sign-in circle â only then does the intended list end up in the address.","The return address (redirect_uri) must match the one registered at the bank character for character; the wizard's own address is filled in by default. A mismatch is rejected by the bank before the consent screen ever appears.","The sign-in address is assembled as /authorize at the host root of base_url â any path inside base_url is dropped. What was actually built is visible in the Authorize URL field before you leave for the bank.","There is no server-side code exchange yet: the exchange button issues values derived from the code itself and simply marks that authorization was completed. The client secret is required by the form but is not used further in the flow and never reaches our server; the whole state lives in the browser session so the flow survives the return from the bank.","The test consent is the wizard's only real record. Creating it has no consequences; authorizing it fixes access (together with the account list when the selected-accounts mode is on), rejecting it revokes the consent. A revoked consent can never be authorized â only replaced by a new one."],"example":"You connect the organization under PSD2. Standard step: PSD2 (EU), provider â the bank's identifier in your configuration, say eubank. Details: base_url https://auth.eubank.example, api_url https://api.eubank.example/psd2/v1, client_id client-4f21, the secret from the bank's developer portal, return address left as filled in. On the sign-in step you open the bank, give consent, the bank returns you with the code in the address â the wizard picks it up and you press exchange. On the rights step you tick accounts and funds-confirmation, switch to selected accounts and paste two account ids, one per line; if the bank has to see exactly that set, go back to the sign-in step and repeat the redirect. On the last step you create the test consent, get its id, tick the confirmation and authorize it: the summary then shows who authorized it.","tips":["Write the consent id down before closing the wizard: the consents page has no list, only lookup by id.","The account list is sent not when the consent is created but when it is authorized, so a mistake in it surfaces on the irreversible step. Check the ids against the accounts list beforehand.","A consent left behind stays awaiting authorization. Rejecting it right away is cleaner than leaving it hanging.","The whole flow state, including the client secret, sits in the browser session and is wiped once you authorize or reject. In a new tab the details have to be entered again."]},"jurisdictionLaunch":{"title":"Jurisdiction launch wizard","summary":"The wizard brings a new country into the banking core: it pulls the regulator, currency, accounting system and account code format from the reference, accepts a chart of accounts as a file or as manual rows, and refuses to go further until local codes are mapped to IFRS elements. On launch the chart is sent as one batch and the organization's own accounts are created one by one. There is no rollback: surplus or wrong codes have to be sorted out on the chart of accounts page.","whenToUse"
1:"When the product enters a country whose chart of accounts is not in the books yet. The chart itself is the prerequisite â a regulator's export in JSON or an agreed list of codes with the hierarchy; afterwards the result is verified on the Chart of Accounts page.","concepts":["The country reference supplies the regulator, currency, accounting system, code format and region; these fields are read-only, because picking the country fixes all of them (Kazakhstan fills in NBK, KZT, Kazakhstan GAAP, the 20-digit format and the CIS region).","The reference also holds the CEMAC (XAF) and WAEMU (XOF) zone entries, but chart records accept a two-letter country code only. With a zone selected every row is rejected while the wizard still reports success â so pick a specific country of the zone.","The import expects JSON: an array of accounts or an object with an entries field; the fields are code, name, name_en, type, category, level and parent_code. The country is not needed in the file â the wizard supplies it â and rows without a code or a name are dropped silently during parsing.","Level and parent code carry the hierarchy: levels 1 to 5, the parent is typed as a code rather than picked from a list, and it is not validated on load â an account with a mistyped parent simply hangs outside its branch.","IFRS mapping (the step is labelled IFRS-маппинг) is a launch gate: without a single link the wizard will not let you through. Nothing is recorded, though â the links are collected as a readiness draft and are never sent to the system.","The mapping type matters when a local account does not fall into a single element: split spreads one account across several elements by ratio, aggregate collects several local codes into one element, conditional depends on maturity or currency. The default ratio of 1.00 only changes for a split.","Custom accounts are the organization's layer on top of the country chart, and the step is optional. A row counts only if code, name and category are filled in; currencies are listed comma-separated and an empty field means any. The launch runs in order â the chart batch first, then custom accounts one by one â so a failure on a custom account does not undo the chart that is already loaded."],"example":"You launch Kazakhstan. On the first step you pick the country and the reference fills in NBK, KZT, Kazakhstan GAAP, the 20-digit code format and the CIS regi
1on. You load the chart from a file: the JSON holds 214 records and the wizard parses 212, two rows having no name. In the table you fix the level on two accounts and the parent on one. On the mapping step you link the due-from-banks code to A.C.IB (Due from banks) and the customer current accounts code to L.C.CD (Customer deposits): direct type, default ratio, IFRS 9 in the IAS field. You skip custom accounts. On the readiness step all four checks are green (the last one, about optional custom accounts, always is) and the counters show 212 accounts and 2 mappings. You launch, then open the Chart of Accounts page to confirm all 212 codes are there.","tips":["Compare the number of parsed rows against the source file before launching: rows without a code or a name are dropped silently and no longer appear in the summary.","The imported count in the success message is the number of rows sent, not the number accepted. The import response also carries a list of per-code errors, but the wizard does not show it, so always verify the outcome on the Chart of Accounts page.","A code is unique per code-and-country pair: re-running the launch returns errors for codes that already exist and adds only the new ones, while the wizard again reports success. If the run failed on custom accounts the chart is already loaded â finish the job on the Chart of Accounts page rather than in a second pass through the wizard.","Keep your IFRS mapping outside the wizard: it is used as a launch condition and is never written anywhere, so the links have to be re-entered by hand on the IFRS mapping tab of the Chart of Accounts page."]},"emiratesIdKyc":{"title":"Emirates ID â verification (UAE Pass)","summary":"The wizard captures how the platform will verify a UAE-resident customer through UAE Pass: the identity level and the attributes requested from the customer. It connects nothing and saves nothing â the exchange with UAE Pass, the retrieval of attributes from the ICA registry and the number checks are performed by the backend when the customer is signed up. The value is that before the integration proceeds you can see how the basic level differs from full KYC and how much customer data you ask for: regulators assess the scope of consent as closely as the verification itself.","whenToUse":"Before opening service to UAE residents: retail accounts, wallet, cards. Access to UAE Pass is arranged under a contract with the operator, outside this interface â an access condition, not a setting here. Afterwards the decision moves into your connection requirements, verification runs at customer sign-up, and its outcome is worked through in KYC cases.","concepts":["Identity level â basic (a UAE Pass account and the Emirates ID number) or full KYC (adding a liveness check and a document check). This is the only mandatory decision: until a level is chosen, «Next» stays disabled.","Requested data â four switches (name, Emirates ID, contacts, address), all on by default. The name comes from the ICA registry in two scripts, Latin and Arabic. The wizard requires none of them: switch all four off and you still reach the end, with a dash in the summary.","The Emirates ID number is 15 digits shaped 784-YYYY-NNNNNNN-C. Both the Luhn check digit and the id_expiry date are validated: an expired card fails verification even when the customer authenticated successfully in UAE Pass.","The «Verification via UAE Pass» screen is read-only, with nothing to do by hand. Three stages: the customer is redirected to UAE Pass and passes biometrics (Face ID / Touch ID), the authorization code is exchanged for a token (POST /idshub/token), and attributes are read from ICA (GET /userinfo).","Consent is recorded under UAE PDPL 2022 and on the UAE Pass side, not in the operator's cabinet. The wizard only defines what is requested from the customer.","The wizard's boundary: the selection is saved neither on the server nor between sessions. «Finish setup» marks the wizard complete in this browser and returns you to the wizard list."],"example":"You are launching a retail wallet in Dubai. At the «Identity level» step you pick full KYC: basic would stop at a UAE Pass account and the ID number, while you need the liveness and document checks. At the «Requested data» step you keep name, Emirates ID and contacts and switch off address â the chosen scenario does not need it. The verification screen you simply read: the customer is redirected to UAE Pass, confirms with biometrics, the platform exchanges the authorization code for a token via POST /idshub/token and reads attributes from ICA via GET /userinfo. Number 784-1990-1234567-1 is validated by its check digit, and validity by the id_expiry field. The summary shows two rows: «Identity level» â full KYC, «Requested data» â name, Emirates ID, contacts. You check them and press «Finis
1h setup»: the wizard is marked complete, while UAE Pass connection credentials are arranged under the operator contract.","tips":["Read the «Requested data» row in the summary before finishing â it is the actual output of your work here. The wizard will not stop you from switching off «Emirates ID», although without the number there is nothing to verify.","You can go back and redo a choice: the circles of completed steps in the progress bar are clickable. Forward movement is only via «Next», and only once a level is selected.","Some rejections in live verification are not failures but expired cards: validity is checked on every request. Separate those cases before escalating to the operator's support.","The wizard stores nothing, and closing the tab discards the whole selection. The decision only matters once carried into your connection requirements and KYC policy."]},"dukcapilEkyc":{"title":"Dukcapil e-KTP â verification (ID)","summary":"The wizard captures how an Indonesian customer will be verified against the Dukcapil population registry: the identity level, the fields submitted for matching, and consent under UU PDP. The registry answers with a per-field confirmation rather than with data, so the accuracy of the NIK decides whether a customer clears or lands in manual review. Nothing is written into the platform: the wizard records the decision ahead of the integration, while the verification itself is performed by the identity layer at customer sign-up.","whenToUse":"When opening the Indonesian market, where identity rests on a state registry: QRIS merchant sign-up, BI-FAST sender, or a customer of an Islamic-finance wallet. Before the wizard, authorised registry access is arranged for the accredited organisation (lembaga pengguna). Afterwards the decision moves into the KYC policy, and each verification outcome shows up in KYC cases.","concepts":["Identity level â basic (NIK and demographic match against the registry, Verifikasi Data Kependudukan) or full (additionally matching a selfie against the e-KTP photo via Face Recognition). «Next» stays disabled until a level is chosen; this is the wizard's only mandatory fork.","The registry answers field by field with «Sesuai» or «Tidak Sesuai». It returns no customer data and does not indicate which character diverges â the discrepancy has to be resolved with the customer.","NIK (Nomor Induk Kependudukan) is the population registry record number, 16 digits. A single mistyped digit is indistinguishable from fabricated data: the verification result is exactly the same.","The wizard does not tie the level to the field selection: you can pick the full level and switch «Photo» off. The check then cannot be assembled, and no warning appears â the contradiction surfaces at the first live verification.","The «Verification via Dukcapil» screen is read-only: the parameters come from the KYC policy. Storage is likewise a platform property, not a wizard setting â the raw selfie is not retained and the NIK is stored encrypted only (UU PDP, PP 71/2019).","What follows the check is not the wizard's call either: assigning the KYC level and recalculating e-money limits is done by the identity layer at customer sign-up.","The wizard's boundary: the selection is written nowhere. «Finish setup» marks the wizard complete in this browser and returns you to the wizard list."],"example":"You are opening a wallet for customers in Jakarta. You pick the full level: a basic match would be enough for an entry-level account, but you need full operational access, which means the photo is needed too. At the «Requested data and consent» step you keep NIK, name and photo and switch off address â the chosen level does not require it, and consent scope is assessed separately. The customer enters NIK 3174012509900001 and the name exactly as on the e-KTP; the platform queries Dukcapil, receives «Sesuai» on every field, and the selfie is then matched against the e-KTP photo. Had the name come back «Tidak Sesuai» â say, a second name element missing from the form â the customer would fail, and the reason would have to be established with them, because the registry response does not carry it. The summary keeps «Identity level» â full and «Requested data» â NIK, name, photo. You press «Finis
1h setup» and the wizard is marked complete.","tips":["If you choose the full level, leave «Photo» switched on: without it the e-KTP match cannot be assembled, and the wizard will not warn you.","Re-running the check does not cure a mismatch. «Tidak Sesuai» arrives against a specific field, and that field has to be reconciled with the customer â most often a second name element missing from the form.","Request the address only if you genuinely need it: the match needs the NIK and the name as printed on the e-KTP, and consent scope under UU PDP is assessed separately from the verification itself.","The wizard saves nothing, on the server or between sessions: closing the tab clears everything. Carry the result into your connection requirements and KYC policy."]},"wpsPayroll":{"title":"WPS â payroll (UAE)","summary":"The wizard walks through UAE employee payroll via WPS: the employer's identifier in the MoHRE registry, the bank agent, the layout of the SIF file and the order of its submission. The wizard neither generates the file nor sends it to the bank â it shows what the file consists of and what the deadline actually depends on. WPS is mandatory for private UAE employers, so a missed submission is not a technical hiccup but an employer breach before the labour ministry.","whenToUse":"When the platform runs payroll for a UAE employer and salaries must go through the Wage Protection System. Before the wizard: the WPS account is opened and an agreement is signed with an authorised bank agent. Afterwards the working connection credentials are entered on the organisation's «Integrations» page, and the SIF file itself is produced and submitted outside the wizard.","concepts":["MOL establishment ID â the employer's identifier in the MoHRE registry, nine digits. The wizard's only mandatory field, yet validated for non-emptiness only: a typo, even letters, will pass, while the bank will reject a file carrying the wrong identifier.","Bank WPS agent â the MoHRE-authorised bank (ENBD, FAB, ADCB) that accepts the file, debits the employer's WPS account and executes the transfers. It is an ordinary text field pre-filled with ENBD and is not required: clear it and the wizard still lets you through, leaving a dash in the summary.","SIF file (Salary Information File) in MoHRE format v2.1 â a fixed-width text file: one employer record (EDR) carrying the identifier, bank agent, record count, total amount and pay date, plus one salary record (SCR) per employee (Emirates ID, name, days worked, basic, allowances, deductions, net). The screen lists the fields for reference only.","Total consistency â the sum of the net amounts across all SCR records must equal the total in the EDR record, and that same total is reconciled against the debit from the WPS account. The only currency in the file is AED.","Employee details â a UAE IBAN (23 characters, AE prefix, MOD97 check) or a WPS salary card. A mistake here is not a platform rejection but one specific person not receiving their salary.","Submission â the file is encrypted with the bank agent's PGP key and sent over a secure channel (mTLS API or SFTP) no later than two business days before the pay date and before the 14th of the month. Acceptance is confirmed by the MoHRE receipt, delivered by webhook within 24 hours.","The wizard's boundary: neither the identifier nor the agent is saved anywhere. The finish button marks the wizard complete in this browser, while the working connection credentials live on the organisation's integrations page."],"example":"The employer is a trading company in Dubai: 48 employees, August salaries paid on 10 September. At the «Employer» step you enter MOL establishment ID 100000001 and leave ENBD as the agent â the WPS account is held there. At the «SIF file format» step you review the layout: one EDR record with the identifier, a record count of 48, the total and the pay date, plus 48 SCR records. For a manager with Emirates ID 784-1990-1234567-1 the record reads: IBAN AE070331234567890123456, 30 days worked, basic 7,000.00, allowances 1,500.00, deductions 0.00, net 8,500.00 AED. The sum of all 48 records â 486,750.
100 AED â must equal the EDR total and the debit from the WPS account. At the «Submission to WPS» step you read the conditions: PGP encryption, mTLS API or SFTP channel, deadline 8 September, two business days before the pay date. The summary keeps «Establishment (MOL ID)» 100000001 and agent ENBD; you carry those into the organisation's integrations and close the payroll period against the MoHRE receipt.","tips":["The wizard does not build or submit the file. The agent connection credentials â API URL, MOL ID, agent code and API key â are entered on the organisation's «Integrations» page; the WPS block appears there only if the organisation's data region is set to the UAE.","The MOL establishment ID is checked for non-emptiness only, so count the nine digits yourself. An error in the identifier will not surface until the file reaches the bank.","Count «two business days before the pay date» against the UAE working calendar: in months with public holidays the window narrows and you need more slack.","A debit from the WPS account does not mean the ministry accepted the file. The confirmation is the receipt, delivered within 24 hours; close the period on the receipt, not on the debit.","Changing the bank agent changes both the encryption key and the submission channel. Schedule it between payroll periods, never inside one."]},"cryptoGoLive":{"title":"Crypto Acceptance Launch","summary":"The wizard assembles crypto acceptance for a single network + environment pair: the hot wallet, the deposit address pool, the risk scoring weights, treasury wallets for three risk tiers, and a test sweep that proves the chain works end to end. Only two steps change platform state: the risk config is saved for the whole organization, and treasury wallets are created on-chain and cannot be deleted. The remaining steps only show what already exists and create nothing.","whenToUse":"When an organization starts accepting crypto on a network for the first time, and when a setup proven on test is moved to production. Requires the use_crypto_tools permission and the blockchain_service module. The final step has a «start another network + environment pair» button that restarts the wizard for a second network or for production.","concepts":["The network + environment pair â Ethereum or TRON, test or production. It is set on the hot wallet step and everything else hangs off it: changing either resets the readiness marks for the wallet, the pool, the treasury and the sweep.","key_ref points at the private key in the KMS or secret store, e.g. kms://hot-wallet/eth-prod. The key itself is never stored or typed into Admin Area, and the field is mandatory â the step will not advance while it is empty. The wizard does not create the hot wallet: it lists the ones already registered for the pair.","Risk scoring weights (KYT, AF, VELOCITY) are entered in basis points and must add up to exactly 10000 â otherwise Save is disabled, and until the config is saved the Next button stays disabled too. The same config carries the behaviour when scoring is unavailable (fail_closed stops the operation, fail_open lets it through unscored) and the address provider from the previous step.","Risk scoring is configured per organization, not per pair: it is the same call the Risk Engine Config screen makes. A «just testing» run rewrites the weights that score production acceptance as well.","A deposit pool is not always needed. Single-use addresses isolate the origin of funds, but the later sweep costs a network fee, and on small amounts the sweep costs more than the amount itself â direct acceptance is cheaper there. The intake mode is configured separately, and the step links straight to those settings.","Provisioning treasury wallets is irreversible: the addresses appear on-chain and cannot be deleted. The step is gated by an explicit confirmation checkbox, and the wizard will not move on until it sees all three tiers â low, medium and high.","A sweep moves incoming funds from the deposit address into the treasury wallet of the matching tier. It cannot be triggered from the wizard: sweeps are initiated by the platform. The operator sends a small test deposit to a free address and checks in the list whether it reached the treasury."],"example":"You are launching acceptance on Ethereum in test. On the hot wallet step you pick Ethereum and test and enter kms://hot-wallet/eth-test â the list below shows a wallet already registered for the pair. On the deposit pool step you keep the hd provider: 50 addresses in total, 48 of them free. On the risk step you set KYT 5000, AF 3000, VELOCITY 2000 â the sum of 10000 turns green, you keep fail_closed and press Save. You tick the confirmation and press the provisioning button â all three tiers appear. You send 25 USDT to a free pool address, refresh the sweep list a few minutes later and see the transfer from the deposit address into the treasury: score 12.5%, tier low, status swept. You press «confirm the chain works», and on the final step you restart the wizard â this time for Ethereum and prod.","tips":["The risk weights are the only setting here that is not bound to the pair. Saving them on test also changes them for production: if the production setup is already live, check the current values before pressing Save.","Treasury provisioning cannot be undone. Before ticking the checkbox, re-read the network and environment badges at the top of the step: a mistake costs you three stray addresses on the wrong network.","The wizard does not create the hot wallet or the pool addresses, it only displays them. If the pair has no wallet or the pool has no free addresses, acceptance will not work no matter how many steps you complete.","The «chain works» mark is set by hand and verifies nothing on your behalf. Tick it once the list really shows a sweep into a treasury wallet, not merely a deposit landing on the address."]},"swapTerminal":{"title":"Swap terminals for gas purchases","summary":"The wizard creates the terminals through which the platform buys gas itself: three terminals per selected network, each drawing on a different source of funds and ordered by priority. It also sets up the wallet that pays for the swap and the provider ledger wallet, without which the operation aborts instead of falling through to the next source. Terminals are created active and shared, the wizard cannot delete them, and a repeat run only fills in what is missing.","whenToUse"
1:"When setting up an organization's crypto contour so the platform buys gas by itself instead of waiting for manual top-ups. Run it after the organization's wallets exist and before the first operation that will need gas. Requires the manage_terminals, manage_wallets and use_crypto_tools permissions plus the blockchain_service module.","concepts":["The three-source cascade â each network gets three terminals with priorities 0, 1 and 2: own stock (self_swap), cold and hot. The router walks them in order until the swap goes through. Ethereum is served by the uniswap provider on the gas_purchase_eth route, TRON by sunswap on gas_purchase_trx.","The gas wallet pays for the approve and the swap on-chain. The wizard shows it per network and provisions it if missing â through the same mechanism as treasury wallets, so the address appears on-chain and cannot be deleted. The address override may stay empty: the provisioned wallet is then used, while a filled-in address must belong to the organization and have a key.","The provider ledger wallet (uniswap for Ethereum, sunswap for TRON) is a ledger record, not an on-chain address. Without it the operation is rejected with \\"no wallet for this provider\\", and this is the case where the cascade does not move to the next source but aborts entirely. Creation is repeatable: an existing wallet is returned as is, and until it exists the wallets step will not advance.","Amount limits are entered in minor units as strings. USDT has six decimals, so 1,000,000 means 1 USDT and 1,000,000,000 means 1000 USDT. Nothing here flags an error of three zeroes.","Allowed price deviation (slippage) is written as a decimal fraction with a dot: 0.02 means 2%. The approve and swap delays are in milliseconds, 60,000 by default, i.e. one minute. These values go into every terminal of the cascade on every selected network.","A repeat run is safe: before creating anything the wizard matches the existing shared terminals of the selected environment by provider, priority and swap mode and marks them as existing. Duplicates are not produced â but the wizard cannot delete what it created either."],"example":"You are setting up gas purchasing for Ethereum in test. You select test and Ethereum â the wizard states that 3 terminals will be created. The network has no gas wallet, so you press provision, an address appears, and you leave the override field empty. Next you create the provider ledger wallet uniswap / ETH / USDT; beside it you see 2 partner USDT wallets on ETH, so the operation will not fail there. You keep the limits at 1,000,000 and 1,000,000,000 (1 to 1000 USDT), deviation 0.02, both delays 60,000 ms. The review step shows three payloads: priority 0 self_swap, 1 cold, 2 hot, route gas_purchase_eth. You run the provisioning: created 3, already existed 0, errors 0. For TRON you run the wizard again â there the provider is sunswap and the route gas_purchase_trx.","tips":["Terminals are created active and shared: the router starts counting them the moment provisioning succeeds. If the contour is not ready yet, start in the test environment.","Before the first operation check the three things the wizard does not: a native balance (ETH or TRX) on the gas wallet, a partner USDT wallet on the right network, and â for the hot source â the partner's ledger balance plus the platform custody wallet. The list is shown on the final step.","Amount limits are entered in minor units: convert them back to USDT before pressing Next. Nobody downstream will check them for you.","The wizard does not create partner USDT wallets â those come from partner onboarding. A zero in the counter on the wallets step means the operation will be rejected with \\"no wallet for this partner\\"."]},"zoltGoLive":{"title":"ZolT Go-Live â gold token","summary":"The wizard walks the one-off launch of the gold token: the deployment network, the contract role model, and the starting mint and redeem limits. It publishes nothing and saves nothing itself â the contract, the roles, the vaults and the price feed are set up on the dedicated ZolT screens. The cost of a mistake is in the decisions, not the buttons: roles are handed out once, and after go-live limits can only be changed through a 48-hour delay.","whenToUse"
1:"Once per network, before the first ZOLT issuance: first on the test network for burn-in, then on mainnet. The wizard is open only to the ZolT operator â a client whose active organization is the operator one (type zolt_admin) and who holds the manage_zolt permission; a platform administrator is not let in. Everything afterwards â minting, redemption, reserve audits, blacklisting â happens in the ZolT section.","concepts":["The wizard is a plan, not a control panel. Five steps: intro, network, roles, limits and summary; neither the deployment nor the role grants happen here. Finish marks the wizard completed and returns you to the wizard list, and the choice itself is stored nowhere â close the page and you come back to an empty form.","Network choice: Sepolia â burn-in of at least two weeks covering the full loop (mint, redeem, pause, oracle); Ethereum mainnet â production deployment via a private mempool with 12 confirmations, which closes the reorg risk. The Next button stays disabled until a network is picked.","Six contract roles: MINTER_ROLE â minting ZOLT, registering vaults and setting limits; AUDITOR_ROLE â publishing proof-of-reserves attestations; PAUSER_ROLE â emergency pause; BLACKLISTER_ROLE â sanctions and AML address blocking; UPGRADER_ROLE â the right to upgrade the implementation (3-of-5 multisig); ORACLE_ROLE â the XAU/USD gold price feed and the volatility guard. The governance multisig grants them, and the key that deployed the contract renounces its root rights afterwards.","Starting limits are set directly, with no timelock: the 48-hour delay applies only to later changes. The wizard shows them as they are and does not let you edit them â 1,000,000 ZOLT per mint transaction and 100,000 ZOLT per redemption request; they are edited on the dedicated ZolT limits screen.","The 24-hour volatility guard: if the gold price moves by more than 5% within 24 hours, the mint limit is automatically halved. It only works with ORACLE_ROLE assigned and an XAU/USD price source connected.","Genesis state: the issued token supply equals the gold accounted for in the vaults, and at launch that is zero to zero. The implementation and a UUPS proxy are deployed, the token has six decimals, and the first issuance becomes possible once a vault is registered."],"example":"You are preparing the launch on the test network. On the network step you pick Sepolia â without a choice the Next button stays disabled. On the roles step you keep all six switches on and write down which key gets what: minting â the treasury safe, reserve attestation â the custodian key, pause and blacklisting â the on-call security safe, implementation upgrade â a 3-of-5 multisig, price feed â the quote provider key. On the limits step you check the rows: mint limit 1,000,000 ZOLT per transaction, redeem limit 100,000 ZOLT per request, and a 5% price move within 24 hours halving the mint limit. On the summary you verify the network, contract roles and limits rows and press Finish. Then you go to the ZolT section: deploy the contract, grant the roles, register the first vault, and only then mint the first tokens. After two clean weeks on Sepolia you run the wizard again, this time choosing Ethereum mainnet.","tips":["Switching a role off cancels nothing in the contract â it only drops the line from the summary. Unassigned roles have different consequences: with no PAUSER_ROLE there is nothing to stop the contract during an incident, with no ORACLE_ROLE the volatility guard does not work.","Spread the roles across separate keys and safes. Combining minting, pause and upgrade on one key strips the scheme of its only protection â separation of duties.","The starting limits are the one moment when they can be set instantly. After go-live every change goes through the 48-hour delay, so agree the numbers before the procedure, not after.","Nothing you choose in the wizard is stored. Copy the summary into the launch task straight away, rather than leaving it until you close the page."]},"riskEngine":{"title":"Risk profile launch wizard","summary":"The wizard assembles the organization's single risk scoring config: it splits the contribution of three dimensions â KYT, anti-fraud and velocity â and refuses to enable any of them without a data source. Weights are entered in basis points and the three must add up to exactly 10000. Activation overwrites the stored config in full, and there is no version history to fall back to. The blackl
1ist and the aggregate created along the way stay in the platform even if you leave before activation.","whenToUse":"Use it when risk scoring for crypto operations is switched on for the first time, or when the balance between dimensions is revisited â say, transaction screening should weigh more and velocity less. If the sources are already in place and only the weights change, the Risk Config page is faster.","concepts":["Basis points are the unit for weights: 100 bps = 1%, 10000 bps = 100%. The three weights must add up to exactly 10000 or the step will not let you continue; each field shows its percentage underneath and the sum carries a green or red badge.","A non-zero weight switches on a source step: anti-fraud above zero adds the blacklist step, velocity above zero adds the aggregate step, KYT above zero makes the address provider mandatory. Zero a weight and the step drops out of the route while that source's confirmation is cleared.","Fail mode decides what happens when the check itself fails: fail_closed blocks the operation, fail_open lets it through unscored. The default is fail_closed.","Confirming a source is a separate action. On the blacklist step the \\"Use this list\\" button appears only when the chosen provider and tags already have entries; until you press it or upload a file, the source counts as unconfirmed and the step blocks the way forward.","The list and the aggregate are created on their own step, not at activation. XML files are read from FULLNAME_CYRILLIC elements, XLSX from the second column starting at row two; the list name is assembled from the tags and the file name.","Activation overwrites the whole organization config â weights, fail mode and address provider. Previous values are kept nowhere, so write them down first if you plan to compare."],"example":"Transaction screening is to carry more weight. The wizard opens on KYT 6000, anti-fraud 2500, velocity 1500. You set KYT 5000 â the field immediately reads 50.00% â then anti-fraud 3000 and velocity 2000, and the sum turns green at 10000. Fail mode stays fail_closed and the address provider stays hd, so both conditional steps remain in the route. On the blacklist step you pick a provider, tags scammer and terrorist, and upload an XLSX with 1240 names; the list is created right there and \\"Anti-fraud source connected\\" appears. On the aggregate step you switch to \\"Create new\\": name cards/velocity/count, op count, argument id, group by card.id, window 1h, then press \\"Create aggregate\\". On the last step all three checks are green, you press \\"Activate risk profile\\" and the config is saved. The wizard then offers to open the Risk Config page so you can confirm the weights match.","tips":["Weights are whole numbers in basis points: 25% is 2500, not 25. An error of two orders of magnitude is invisible at a glance, so check the percentage shown under each field.","Do not zero a dimension just to skip its step: weight 0 means that check no longer contributes to the score at all.","An uploaded list and a created aggregate remain in the platform after you leave the wizard. Check the Blacklists and AF Aggregates sections before a second run, or you will end up with duplicates.","The wizard is open to the platform administrator only: it ends by overwriting the risk engine config, and the backend accepts that write from an administrator alone. A client sees the effective weights on the Risk config page in read-only mode, and creates blacklists and counters on their own pages."]},"velocityLimit":{"title":"Anti-fraud velocity control","summary":"The wizard builds a velocity limit out of a sliding-window aggregate and a limits:v2:evaluate expression that compares the aggregate value against a threshold. There is no separate rule object in the platform: the expression is written into the inspector params of the terminal you select. Activation happens in one click and is irreversible â the aggregate is created first, then the terminal is updated. An existing limits:v2:evaluate on that terminal is replaced with no copy kept, while its other params are preserved.","whenToUse"
1:"When one specific terminal needs a cap on how often â or how much â is processed per card, device or recipient, usually after a burst of enumeration attempts or after a fraud review. The limit applies only to that terminal's traffic; other channels in the cascade need their own.","concepts":["The aggregate counts events over a sliding window, not a calendar hour: a threshold of ten per hour releases the first operation exactly an hour after it happened, not at the top of the next hour.","The group-by key is what velocity is counted against: card, device, recipient. It is given as an event path, for example #event.data.tx.money_storage_meta.card_hash. The same threshold on a different key catches something entirely different.","The event filter decides what enters the aggregate at all: each row is a field, an operator and a value, for example #event.name = tx/started. With no conditions, every event is counted.","The rule is a prefix expression: a verdict, then a comparison of the aggregate value against the threshold. The preview reads [\\"reject\\", [\\">\\", \\"@cards/velocity/count\\", 10]]. Verdict reject declines the operation, warn only flags it; the aggregate is referenced by name with @, not by id.","The threshold is a plain number: counts are units, amounts are minor currency units. One thousand roubles is written as 100000.","The rejection text goes into the limits:v2:rejection_description param, and only when the field is filled in â leave it empty and the terminal keeps its previous text. Updating the terminal itself requires manage_terminals."],"example":"A terminal is seeing card enumeration attempts. The goal: no more than ten operations per card per hour. On the aggregate step you keep the suggested values â name cards/velocity/count, op COUNT, group by #event.data.tx.money_storage_meta.card_hash, window 1 hour, condition #event.name = tx/started. On the rule step you pick that same aggregate, marked \\"(new)\\", with verdict reject and the \\"greater than\\" comparison. On the threshold step you enter 10 and the rejection text \\"Operation rate limit exceeded\\"; the preview becomes [\\"reject\\", [\\">\\", \\"@cards/velocity/count\\", 10]]. On the terminal step you select #42 · alfabank · RUB · prod, and the wizard warns you if limits:v2 is already set there. You press \\"Activate\\": the aggregate is created, the expression lands in the terminal's inspector params, and the eleventh operation on that card within the hour is declined with your text.","tips":["The step-one aggregate is created on activation no matter what â even if the rule step points at a different, already existing one. If you mean to reuse an existing aggregate, expect the one described on step one to show up in the list as well.","Amount thresholds are in minor units: 50,000 roubles is 5000000. An error of two orders of magnitude only surfaces through declined payers.","Put a new limit on warn first and watch what it catches. A reject verdict on the wrong group-by key declines legitimate payers silently â all they see is the rejection text.","Activation is two requests in a row. If the aggregate was created but the terminal update failed, pressing the button again creates the aggregate a second time: check the AF Aggregates section first."]},"complianceReporting":{"title":"Regulatory Reporting Setup Wizard","summary":"The wizard sets up recurring submission of a regulatory report: a template from the built-in catalog, a delivery channel, a schedule and a mandatory test run. The channel and the schedule are created only on the last step and are created enabled, so from the next due date the report goes to the regulator on its own. The test report is a real one: it runs against live data and stays in the generated reports list.","whenToUse":"When the same report has to be filed on a regular basis and doing it by hand is no longer an option â after a license is granted, or when a new jurisdiction is added. A one-off report is faster to produce on the report generation page, without the wizard.","concepts":["The template defines everything substantive: jurisdiction, regulator, data set and export format. Templates are built into the platform and are never created by hand â you only pick one, narrowing the catalog by jurisdiction if needed.","The frequency shown on the template card is a recommendation, not a setting. The schedule step opens on monthly and last_period regardless of what the template says, so a quarterly filing has to be switched over manually.","The period window is the interval each run collects data for, and it is not the same thing as the frequency. A monthly run with last_month covers the whole previous month; with last_30d it covers thirty days back from the run date.","Encrypted delivery requires the recipient's public key: pgp, age and smime will not pass the step without one. Channel parameters are given as JSON â recipients, access credentials, webhook URL; an in_app channel needs none of that and the report stays inside the interface.","The test report is not a simulation. It is produced exactly the way a normal report is, lands in the generated reports list, and must come back with status completed â any other status blocks the step.","The last step, once the confirmation box is ticked, performs two writes in a row: the delivery channel is created first, then the schedule that references it, both enabled straight away. The wizard cannot create a disabled schedule â you can only turn it off later in the schedules section."],"example":"The task: file a monthly settlement report with the National Bank of the Republic of Belarus. You set the jurisdiction filter to BY and pick the NBRB template from the catalog; the card shows its export format and recommended frequency. You name the channel \\"NBRB â primary email\\", type email, replace the sample recipient in the config with the real one, choose pgp encryption and paste the public key. Schedule: name \\"Monthly NBRB report\\", frequency monthly, and the peri
1od window switched from last_period to last_month. On the test step you set the period from 2026-06-01 00:00 to 2026-06-30 23:59 and run it â status completed, with the report id shown next to it. On the last step you check the summary, tick the confirmation and press \\"Enable reporting\\": the channel and the schedule are created and live, and the July report goes out on schedule.","tips":["Run the test over a period that certainly has data: both dates are optional, and an empty period turns the check into a formality. The error would then surface in front of the regulator.","Verify the channel parameters before enabling: sensitive config fields are masked on read, so you will not see them in the clear after saving.","Enabling is two writes in a row. If the channel was created but the schedule was not, pressing the button again creates a second channel: check the Delivery Channels section first.","The cron frequency requires an expression in its own field, for example 0 7 * * * for a daily 07:00 run. For every other frequency that field does not appear."]},"dsrBreach":{"title":"Privacy â DSR and breach","summary":"The wizard ties a jurisdiction's privacy regime to two operator duties: answering a person's request about their personal data, and notifying the regulator about a breach within the allotted window. It sends nothing to the platform â it records the regime you picked, the request types you commit to handling, and the deadline you will live by. The cost of a mistake here is not in configuration but in timing: a missed notification deadline is a violation in itself, even after the breach has been contained.","whenToUse":"Before you start operating in a new jurisdiction, together with the launch of service for that country, and again whenever the applicable regime changes or a data protection officer is appointed. Afterwards requests are worked in the Data subject requests section, and a data incident becomes its own record with its own countdown.","concepts":["Privacy regime â the jurisdiction whose rules govern your answer to the person and your notification to the regulator. Four cards are offered: PDPL UAE (Federal Decree-Law No. 45/2021), PDPA Singapore (PDPA 2012, PDPC), PIPEDA Canada (OPC) and GDPR EU (Regulation 2016/679). Until a regime is picked the Next button stays disabled: the deadline on the following step is derived from it.","A hard deadline and a soft one are different things. GDPR shows 72 hours on screen, PDPA shows 3 working days; PDPL and PIPEDA have no fixed window and the wizard says «as soon as possible». Soft does not mean «whenever»: the delay is yours to justify.","The deadline shown in the wizard is regulatory guidance, not a timer. On the breach record the platform counts the regulator deadline from the detection time and always over 72 hours, whichever regime you picked. If your jurisdiction sets a different window, or counts it in calendar days, keeping track of the difference is manual work.","The wizard lists four request types: access, erasure, rectification, portability. The Data subject requests queue works with six â restriction of processing and objection are there as well. A switch here does not remove a type from the queue; it records which ones you commit to handling.","The response deadline on a request is set by the platform itself â 72 hours from the moment it is registered â and an overdue request is flagged «deadline exceeded» in the list. Only a request in the «pending» state can be approved or rejected, and a rejection requires a written reason.","Erasure is not deletion of everything. Email, name, phone and documents are anonymised, the account is deactivated, sessions and tokens are removed, while transactions, ledger entries and the event log stay â the law requires them kept. Anonymisation cannot be undone."],"example":"A company is opening service in Singapore. On the regime step you pick PDPA Singapore; on the breach step the wizard shows the notification deadline â 3 working days â and the DPO auto-escalation switch (labelled «ÐвÑо-ÑÑкалаÑÐ¸Ñ DPO»), which is on by default and which you leave as is. All four request types stay enabled. The summary on the final step reads: PDPA Singapore · PDPA 2012 (PDPC); access, erasure, rectification, portability; breach window 3 working days, DPO auto-escalation. You press «ÐавеÑÑиÑÑ Ð½Ð°ÑÑÑойкÑ» and carry the choice into your internal rules. The first erasure request lands in the Data subject requests section with its deadline already set â 72 hours from registration. You detect a breach on 14 September at 23:40: the platform counts its own 72 hours from that moment, while the PDPC window is yours to track separately â the wizard records it as 3 working days. Had you picked GDPR instead, the screen would have shown 72 hours.","tips":["Walk the wizard before the first incident, not during one: the middle of a breach is the wrong moment to argue about which deadline applies.","Enter the real detection time, and the same one for the whole team: the platform counts 72 hours from it â moving it back takes time away, moving it forward buys none.","The completion mark lives in the browser; the wizard writes nothing to the platform. If several administrators share the setup, put the chosen regime and window into your internal rules, otherwise each of them will keep seeing the wizard as not started.","Approve an erasure request only after the requester's identity has been verified: anonymisation is irreversible. A rejection requires a written reason, and it stays visible on the request card."]}
1,"workflowAuthoring":{"title":"Workflow â author a process","summary":"The wizard creates a BPMN process definition and, unless you keep it as a draft, publishes it right away. What it creates is a three-node skeleton â start event, human task, end â not a finished diagram: the diagram is drawn afterwards in the editor. Order matters more than content here: once a definition is published the editor opens it read-only, and the diagram can no longer be worked on.","whenToUse":"When a new process is needed â an approval, a client check, a dispute review â and its skeleton is quicker to create here than to assemble in the editor from scratch. The wizard comes before editor work; afterwards the diagram is filled in with tasks and gateways, and instances are started from the published version.","concepts":["Process name â a machine name in lower case with underscores, for example kyc_onboarding. It is mandatory and takes part in the uniqueness check: the pair «name + version number» must be unique within the organisation, otherwise creation fails with «definition with this name and version already exists».","The start type is stored as a marker on the start node, not as a separate node type. Choosing the message or the timer start does not by itself subscribe the process to a message or create a schedule â both are set up in the editor.","Draft and published are different states. The «save as draft» switch on the version step is off by default, so the button on the last step reads «publish process»: it both creates the definition and publishes it at once. With the switch on, the same button becomes «save draft».","The v1.0.0 label on the versioning step is text that goes into the process description. The definition's own version number is an integer: a draft shows as v1, and after publishing the platform increments it, so the list and the editor show the process as v2.","Publishing is irreversible from the cabinet: a published definition opens read-only, the publish button remains only on drafts, and the way back to draft exists only through the API (POST /workflow/definitions/:id/revise).","The review step is a description, not a run: the wizard does not dry-run anything. The graph is parsed on creation, and the full check happens on publish â exactly one start node, an end event present, all nodes reachable, a handler set on a service task. That is why the skeleton carries a human task rather than a service task: it passes those checks."],"example":"You need a process for checking a new client. On the definition step you enter the name kyc_onboarding and choose the message start: the process has to start from the registration form. On the version step you turn on «save as draft» â the diagram still has to be assembled. On the review step you read what exactly the platform will check, move to the publication step and press «save draft»: a «draft saved» message appears together with a card linking to the BPMN editor. In the editor you replace the single «kyc_onboarding: first step» task with the real diagram â document check, a gateway on the result, manual review for edge cases â save it and press Validate. Once the diagram is ready you publish it from the editor: the definition gets the number v2, instances can be started from it, and the diagram opens read-only from then on.","tips":["Turn on «save as draft» whenever the diagram still has to be built: a published definition opens read-only in the editor, and the cabinet offers no way back to draft.","Choose the name the process will live with: it can only be changed while in draft, and running the wizard again with the same name over an unpublished draft hits the error about an existing name and version.","If publishing failed but the definition was already created, do not press the button again: it will try to create the process anew and trip over the same uniqueness check. Open the process definitions list â the draft is already there, and that is where it should be published from, or from the editor.","The editor link appears on the completion screen only after a successful creation. If you navigated away, find the process by name in the process definitions list."]},"copilotOnboarding":{"title":"Copilot Onboarding â AI assistant","summary":"The wizard walks an organisation through the decision about the built-in assistant: where the model runs, what consent is given, which data the assistant may reach, and what stops it. It saves nothing itself â the address, the model and the key are entered afterwards on the Copilot settings page. The point of the walkthrough is not to miss the two limits people remember only after connecting: the data residency requirement, and the fact that the assistant never sees more than the operator does.","whenToUse"
1:"Before operators see the assistant for the first time: the organisation has the Copilot AI module enabled and someone has to decide whose model it runs on. After the wizard the administrator opens the Copilot settings and enters the address, the model and the key; on the platform backend there is nothing to enter.","concepts":["Model source â the platform backend or your own key. On the platform backend the keys and the model are run by the platform and nothing has to be entered. Your own key means your own address and your own model; the settings page offers exactly two types: «Claude API (Anthropic)» and «OpenAI Compatible (Azure, Local LLM)» â the second covers both Azure OpenAI and a model hosted inside your own perimeter.","The organisation's consent is a mandatory step. While the consent switch is off, the access scopes stay disabled and the wizard will not move on. This records a decision rather than writing to the platform: the wizard stores nothing beyond a completion mark in the browser.","Scopes narrow, they never widen. Transactions is on by default, payouts and webhooks are off. The assistant works through tools filtered by the operator's own permissions: enabling the payouts scope will not show them anything they cannot already see in the cabinet. Anything that changes data requires the operator's confirmation.","Data residency outranks your choice. If the organisation's data is localised in Russia or Kazakhstan, the Claude API type is rejected â only an OpenAI-compatible address pointing at a model inside your own perimeter qualifies, as required by 242-FZ. It surfaces as the error region_requires_local_llm, and the settings page warns about RU/KZ in the field hint.","Card data masking cannot be switched off. Card number, verification code, expiry, PIN and magnetic stripe tracks are masked before anything is sent to any model, your own included. Passport, tax and social identifiers, phone, email, address and IBAN are masked for a cloud model and may be passed only to a model in your own perimeter, and only under separate consent.","The emergency shutdown works without you. Besides manual shutdown at platform, region, feature or single-organisation level, it trips on its own: an error rate above half over five minutes shuts everything down, and 500 and 503 responses from the model arriving more than ten times a minute shut down the individual feature."],"example":"An organisation operating in the UAE wants its own model. You pick «own (BYO-key)» â the wizard warns straight away that the key goes into the secret store and will not be read back, and that only its hash stays in the logs. On the consent step you switch on the organisation's consent, which unlocks the scopes: transactions is already on, you add payouts and leave webhooks alone, since a separate team handles them. On the safety step the emergency shutdown and the masking are marked with green ticks and cannot be toggled, while proactive insights stay off for the first weeks. The summary reads: own backend, consent given, scopes transactions and payouts, insights off, emergency shutdown and masking active; you press «ÐодклÑÑиÑÑ Copilot». Then you open the Copilot settings, choose the «Claude API (Anthropic)» type, keep the address https://api.anthropic.com, set the model to claude-sonnet-4-6, paste the key and save â the connection test button becomes available only after saving, and a «connection successful» answer means the assistant window will work for operators. Had the same organisation served Russian clients, the Claude API type would not have qualified: «OpenAI Compatible» with a model address in its own perimeter would have been required.","tips":["Settle the residency question before choosing a model: if the organisation's data has to stay in Russia or Kazakhstan, a cloud key will not help â a model in your own perimeter is required.","The connection test button is disabled until the settings are saved, so save first and test immediately: settings are stored even with a wrong key, and without the test the error surfaces in an operator's chat rather than
1in front of you.","The key is entered once and never read back: on a later save the field can be left empty to keep the current key, and a lost key cannot be retrieved from the platform â only reissued at the model provider.","Proactive suggestions are built on the same scopes as the answers. Narrow the scopes and the suggestions narrow with them â that is the configuration working, not a fault.","The emergency shutdown lives on the platform side, not in the wizard. Agree in advance who applies it and on what signal, so nobody is looking for an owner mid-incident."]},"campaignLaunch":{"title":"Campaign launch wizard","summary":"The wizard assembles a collective funding campaign in one pass: funding model and regulatory regime, funding goal, escrow and refund rules, and the payout order for the organiser. The campaign is created as a draft, and the «Submit the campaign for review» checkbox is ticked by default. The wizard only creates a new campaign â it cannot open an existing one for editing, and a second pass creates a second campaign. So check the target amount and the tranche split against the summary before pressing «Create campaign».","whenToUse":"When the organiser has agreed the project and the platform is ready to open the raise. By then the partner is onboarded and the platform's regulatory regime is chosen; after the wizard an administrator approves the campaign and launches the raise â the escrow wallet is provisioned at launch.","concepts":["The campaign escrow wallet is a segregated wallet that receives every contribution and stays out of the organiser's control until the raise closes. This is platform behaviour, not a setting: the wallet is provisioned when an administrator launches the approved campaign.","The funding model is the one rule on this step the platform enforces itself. All-or-nothing: if the goal is not met by the deadline, contributions are refunded to investors from escrow. Keep-it-all: the organiser receives what was raised even on underfunding, and some regimes restrict this.","The action on underfunding â refund, extend or accept â is a recorded decision stored in the campaign parameters; it does not override the funding model. «Accept» is incompatible with all-or-nothing: the card is greyed out, and switching the model silently resets the choice back to refund. «Extend» reveals an extra «Extension, days» field.","Minor units: the target amount and both contribution limits are entered as whole numbers â EUR 500,000.00 is 50000000. Anything but digits is stripped as you type, and the hint under the field shows the conversion into the campaign currency.","The cooling-off period is the number of days in which an investor may withdraw a contribution without giving a reason. Under ECSP it is 4 days, which is the default; the field is sized for 0 to 90 days.","Payout tranches are milestones with a label and a share. The step does not let you continue until the shares add up to exactly 100%; only milestones with a non-empty label and a share above zero are sent with the campaign, the rest are dropped silently."],"example":"You are raising EUR 500,000 for a solar power plant in Germany. On the product step: model â equity funding, name «Solar power plant, first round», regulatory regime ECSP, region DE. On the goal step: currency EUR, target amount 50000000 â the hint reads EUR 500,000.00, minimum contribution 10000 (EUR 100.00), maximum per investor 5000000 (EUR 50,000.00), the raise runs from 1 September to 30 November. Escrow and refunds: all-or-nothing, cooling-off period 4 days, action on underfunding â refund contributions. Payout in tranches: panel purchase 50%, installation 30%, commissioning 20% â the counter reads 100% and the «Next» button unlocks. Distributions quarterly, expected return 12, project term 36 months. You leave «Submit the campaign for review» ticked: the campaign is created as a draft and moves straight to «pending review».","tips":["The conversion hint under an amount field is your only guard against an extra zero: 50000000 and 5000000 look almost identical in the field and differ by an order of magnitude.","Untick the review checkbox if the description and documents are not ready. After creation, a «Submit for review» button stays on the same step â use it once everything is in place.","A tranche with an empty label never reaches the campaign, even though the counter included it in the 100%. Before pressing «Create campaign», make sure every milestone has a label and a share above zero.","A second pass creates a second campaign rather than editing the first â the wizard cannot open an existing campaign. Everything checkable before creation belongs in the «What will be created» summary."]},"installmentProduct":{"title":"Installment product wizard","summary":"The wizard assembles an installment product: where the money comes from, what the installment costs the buyer, who gets approved and how fast, and which merchant outlet offers it. On your own funds the product is a funding pool: the wizard creates it as a draft, and activation is a separate action. Pool parameters are set once â there is no pool edit in the operator cabinet at all, only capital deposits, withdrawals and activation, so a wrong currency, reward or limit is fixed by creating a new pool.","whenToUse"
1:"When the operator opens installments at a merchant, either with its own funds or through an external provider. The merchant terminal already exists by then; after the wizard the pool is topped up with capital and the payment method is switched on from the terminal page.","concepts":["A funding pool is the form a product on your own funds takes: currency, target and minimum capital, purchase amount bounds, maximum term and the reward. Minimum capital is the threshold at which the pool moves to funding and disbursement.","The external provider is the wizard's second branch, and it creates nothing: the provider grants the installment on its own terms while the wizard only assembles the choice on screen and points you to the terminals page. The terminal and merchant share you pick there are not stored anywhere.","Basis points are the unit for every share in this wizard: 1200 means 12%, 150 means 1.5%, 300 means 3%. The hint under the field shows the conversion; a two-order-of-magnitude slip is the costliest mistake here.","The profit-sharing mode is a reward with no lending interest: the buyer pays a fixed markup known before the deal that does not grow with the term, and the pool's result is shared with depositors by their ratio. Late penalties are not admissible as income in this mode: the «Charge late penalties» checkbox is disabled, and switching back to profit-sharing clears it on its own.","The depositors' share is the part of the pool's result that goes to those who funded it. In profit-sharing mode it is mandatory and strictly below 100% (10000 bp), defaulting to 7000 bp; in interest mode the rate is mandatory instead.","The approval mode is a recorded rule, not an engine running inside the wizard: the manual review threshold, per-buyer debt cap, verification level and grace period are stored in the pool parameters, while decisions on applications are taken in the lending section."],"example":"A retail chain in the UAE, installments in four payments. Source â own pool, profit-sharing mode, currency AED, target capital 100000000 (AED 1,000,000.00), minimum 20000000 (AED 200,000.00). Terms: 4 payments, maximum term 12 months, purchases from 10000 (AED 100.00) to 500000 (AED 5,000.00). Merchant markup 800 bp (8%), depositors' share 7000 bp (70%), platform fee 150 bp (1.5%). Approval â «Automatic up to a threshold» with a threshold of 200000 (AED 2,000.00), per-buyer debt cap 1000000 (AED 10,000.00), basic verification, 5-day grace period; the penalties checkbox is disabled in profit-sharing mode. Merchant: terminal #42, outlet share 300 bp (3%). You leave «Activate the pool now» unticked â it is unticked by default: the pool is created as a draft, you top it up with capital and activate it from the same step.","tips":["12% is 1200, not 12. Read the hint under every basis-point field before moving on: once the pool is created these values cannot be changed, as there is no pool edit in the cabinet.","With an external provider the wizard creates nothing and stores nothing. Carry the terminal and the outlet share over to the terminal page right away, while the summary is still in front of you.","For the first weeks keep approval on «Manual only» or at a low review threshold: an application can be rejected before disbursement, but an issued installment cannot be cancelled â only repaid. The arrears picture does not appear before the second or third payment.","The wizard does not enable the payment method on the terminal, it only records your choice in the pool parameters. Until installments are switched on from the terminal page, the buyer will not see them on the payment page."]},"pfpPartner":{"title":"PFP â issuer onboarding","summary":"The wizard records the issuer partner's product set, the regulatory regime and the fatwa requirement for Islamic products into the platform's PFP settings. It captures what was agreed rather than switching anything on: module activation, compliance review and sandbox work stay with the PFP sections. Settings are stored as a whole in a single request, so the wizard reads the current configuration first and merges its own section into it.","whenToUse"
1:"Right after the issuer partner has completed general onboarding to the platform and both sides have agreed which products it runs and under which rules. After the wizard come the compliance review, sandbox work and product activation on the dedicated PFP pages.","concepts":["The partner onboarding section is what the wizard writes into the settings: the list of ticked products, the regulatory regime, the fatwa requirement flag and the completion timestamp. You can verify what was stored in PFP settings â a card with the link appears on the last step after saving.","Whole-config save: the configuration is replaced in a single request. The wizard reads the current one immediately before writing and merges its section into it, so terminology mode and other platform settings survive; edits made in another window between the read and the write are lost.","The regulatory regime is a mandatory choice with no default: until one is selected, neither «Next» on this step nor the finish button works. ECSP â EUR 5M cap and a 4-day investor withdrawal window; Reg CF â USD 5M over 12 months and Form C; AAOIFI â a Sharia Advisory Board of at least three scholars and the prohibition of riba, gharar and maysir.","The fatwa requirement is a blocking precondition: Islamic products are not activated until the Sharia Advisory Board's fatwa is signed. The toggle is on by default, but it only makes sense together with Islamic products: without them the configuration stores «not required» regardless of its position.","Ticking a product is not enabling it. The toggles record the agreed set: crowdfunding (on by default), Revenue-Based Financing, cooperative and Islamic finance. Each module is enabled separately on its own page.","Running the wizard again starts from scratch: it does not load the previously saved set and rewrites the section as a whole â an unticked product disappears from the set and the onboarding timestamp is refreshed."],"example":"You onboard a cooperative as a platform partner. On the «Products» step you keep crowdfunding on and add the cooperative; Revenue-Based Financing and Islamic finance stay off. On the «Regime» step you choose ECSP â an EUR 5M cap and four days for an investor to withdraw; without that choice «Next» stays disabled. You walk through the Sharia step unchanged: no Islamic products, the fatwa toggle is disabled, and «not required» is what goes into the configuration. The summary shows two products and the ECSP regime, with no fatwa row â it is shown only when Islamic products are on. You press «Finish onboarding»: the wizard reads the current PFP settings, merges its onboarding section into them and saves, while terminology mode and the other parameters stay as they were. Then you open PFP settings from the card on the same step and continue with product activation.","tips":["The regulatory regime has no default: until one is selected the wizard neither moves forward nor lets you finish the onboarding.","Do not edit the platform settings in another window while the wizard is running: the configuration is read immediately before the write, and concurrent changes are overwritten.","A second pass rewrites the section as a whole and starts from the default set â crowdfunding only. To add a single product, tick the whole set again.","The wizard does not cross-check products against the regime: Islamic products will be saved even under ECSP. Keeping the set and the regime consistent is on you."]},"cooperativeProducts":{"title":"Founding a cooperative","summary":"The wizard founds a cooperative in one pass: shares and votes, member loans from a common fund with no lending interest, share deposits and the rules for distributing the year's result. The cooperative is created as a draft â it has no members and no capital yet, and it can only admit members once a platform administrator activates it with a registration number. The accounting currency cannot be changed after creation, and the remaining fields can be edited only while the cooperative is a draft or under review.","whenToUse"
1:"When a cooperative is being founded on the platform â farming, consumer or credit â and has to be set up as a whole rather than assembled section by section. The bylaws should be settled first: they define the share value, the voting model and the quorum. After the wizard the cooperative goes to review, while admitting members, lending and payouts are handled on the cooperative page and in the Funding and Distributions sections.","concepts":["Share value is entered in minor units, exactly as the field hint says: 100,000 means 1,000.00 in the accounting currency, and the summary shows the converted figure. The platform computes cooperative capital as issued shares times share value, so being two digits off changes the whole balance a hundredfold.","Voting model â one member, one vote gives each shareholder exactly one vote regardless of how many shares they hold; proportional makes vote weight equal to the share count. The weight is fixed when a member is admitted and is not recalculated at voting time.","The member loan fund is a separate object in the Funding section, not part of the cooperative: a common fund with no lending interest, where the whole result goes to members. It is created only when member loans are ticked, and it appears as a draft â it starts lending once it reaches its minimum size and is activated.","Accounting currency â a choice of seven: USD, EUR, GBP, AED, SAR, MYR, IDR. The limit comes from the loan fund, which accepts no other currencies, and the fund inherits the cooperative's currency. The currency cannot be edited after creation.","Fund target and minimum are in minor units too, but the fields carry no hint about it: 50,000,000 means 500,000.00, not fifty million.","Draft and review â a created cooperative is a draft, submitting moves it to under review, and a platform administrator activates it with a registration number. A submission is accepted only for a cooperative that already has at least three members."],"example":"You found a farming cooperative. Name «Valley Farmers Cooperative», accounting currency USD, share value 100,000 â the summary shows 1,000.00 USD â cap of 500 members, registration region KE. Shares and votes: minimum 1 share per member, maximum 20, one member one vote, general meeting quorum 50%. On the products step you keep member loans enabled: fund target 50,000,000 (500,000.00 USD), minimum 10,000,000 (100,000.00 USD), maximum loan term 12 months. Share deposits stay on, the result is distributed proportionally to shares, reserve contribution 10%. You untick «submit for review right away» because there are no members yet. The cooperative is saved as a draft and the mutual fund appears under Funding; once the bylaws are signed and members have joined, you submit the cooperative for review from its page.","tips":["«Submit for review right away» is ticked by default, but a submission is accepted only for a cooperative that already has at least three members. A freshly created one has none and the submission fails â untick it and submit later.","If an error arrives after the cooperative itself was created â on the loan fund or on the submission â the cooperative already exists. Pressing «Create cooperative» again creates a second one: open the cooperatives list first and see what you actually have.","The accounting currency cannot be edited after creation, and it also becomes the loan fund's currency. Get it wrong and the cooperative has to be created again.","Fund target and minimum are in minor units and the fields give no warning: 10,000,000 is 100,000.00, not ten million.","Only an activated cooperative can admit members. While it is a draft or under review it holds no shares and no capital, so any calculations on it are meaningless."]},"dclsParticipantOnboarding":{"title":"dCLS participant onboarding wizard","summary":"The wizard walks a bank or fund through the full path to dCLS settlement: the participant is created from an organization's partner, documents are uploaded and verified, compliance moves the participant into review and admits it, then limits, the rate guard and the membership fee are set. Admission opens settlement and, in on-chain modes, registers the participant's address in the allow list. A partner is bound to a participant permanently: a second participant on the same partner cannot be created.","whenToUse"
1:"When a new bank, exchange house or fund joins the dCLS network. Before the wizard the organization must have a partner and the document pack: incorporation certificate, licence, UBO disclosure, AML policy, sanctions screening. Document verification runs on its own schedule, so the wizard can be interrupted and resumed by participant id; once admitted, the participant is part of the next netting cycle.","concepts":["Participant and partner are one to one: a participant is created from a specific partner of an organization, and that partner cannot be reused. The Ethereum address is likewise unique network-wide, and it is mandatory for the on-chain and both modes â without it the participant cannot be created at all.","Admission statuses â pending KYB -> KYB submitted -> under review -> approved. «Start review» becomes active only for a participant in KYB submitted, and «Approve participant» only for one already under review with every mandatory document verified. The wizard does not perform the move out of pending KYB â that comes from the participant's own document submission.","Documents â five mandatory types, up to 10 MB per file. Verification is asynchronous and need not finish in one sitting; the wizard unblocks admission once all five types are marked verified.","Limits â maximum position and daily volume are entered in USD cents as whole numbers with no decimal point: 1,000,000,000 means 10,000,000.00 USD. A fractional value or a decimal point is rejected by the server, and the readiness summary shows the amounts converted to dollars.","The market rate guard compares a deal's rate against the reference rate at matching time, not at settlement. Tolerance is in basis points (500 is 5%); leaving it empty applies the per-pair defaults. The reject-or-allow choice covers the case where no reference rate was found; a rate outside tolerance is always rejected.","Membership fee â the date through which membership is paid. A daily check suspends a participant whose payment has lapsed and removes its address from the allow list, taking it out of the coming settlement windows."],"example":"You onboard a bank in the UAE. On the participant step you enter the organization UUID, pick the partner, legal name Acme Bank Ltd, jurisdiction AE, settlement mode both and address 0x⦠â in an on-chain mode creation fails without it. You upload the five documents and mark each verified; until then admission is blocked. On the review step you press «Start review», the participant moves to under review, then «Approve participant»: the address enters the allow list. Limits: maximum position 1,000,000,000 cents (10,000,000.00 USD), daily volume 500,000,000 (5,000,000.00 USD), currencies USD, EUR, AED; the rate guard is on with a 500 basis point tolerance and rejection when the rate cannot be checked. Membership is marked paid through 31 December 2026. All four checklist items are closed â you finish the wizard and move on to netting windows.","tips":["The currency list on the limits step is sent in the same request as the amounts, and in such a request the platform applies the amounts only. After saving, open the participant record and confirm the currencies were actually stored â otherwise the netting wizard will show no currency coverage for this participant.","Marking the fee paid does not bring a suspended participant back: lifting the suspension is a separate action on the dCLS participants page.","Automatic gas top-up settings currently live in the interface only: there is no server-side write for them, so the values stay in the wizard summary and are lost when you leave the page.","Rejection and revocation are terminal. Recreating the participant on the same partner will not work â the partner-to-participant link is unique, so that route is closed."]},"nettingCycle":{"title":"Netting cycle wizard","summary":"The wizard runs netting off schedule: it shows who is approved for settlement and in which currencies, lets you correct limits and the rate guard, and executes the chosen window. The same engine runs as on the four-hourly schedule, and once started the run is irreversible: ledger positions are closed and on-chain deals go to the network. A reason is mandatory â both the form and the server require it â and it is written to the action log together with the result.","whenToUse"
1:"When the next window cannot be waited for â participants need positions closed today â or when the scheduled run did not go through: the node was unavailable and some instructions were left unsettled. The wizard does not replace the schedule; it walks the same path by hand, with a readiness check on the participants before the run.","concepts":["A settlement window is a four-hour slot in UTC: 00:00, 04:00, 08:00 and so on. An instruction is stamped with its window at the moment it finds a counterparty, and only instructions carrying exactly that stamp take part in the run. The current window is the one in progress: running mid-window settles what has accumulated so far, and the rest is picked up by the scheduled run.","Three run modes: the current window, a past window, and a retry of an unfinished run. The retry list is drawn from the couple of dozen most recent runs, with the same timestamps as the log. A retry is idempotent: the window time is part of the ledger entry key, so what is already settled is not duplicated.","Netting savings â the share of turnover that did not have to be transferred: one minus net flows over gross flows. It is computed per deal, not per instruction: one exchange creates two mirrored instructions, one in each side's book.","The limits step edits the participant's profile, not just this run: «Apply to participant» saves the maximum position, daily volume and rate guard immediately, and they hold for every window that follows. The fields are labelled USD but take minor units â the hint below each field shows what the entered number amounts to.","A participant with no address in an on-chain mode â its deals will not be executed in the blockchain. The wizard lists such participants before the run, because afterwards it is simply a line in the run's error list.","The participants step is a required pass: you cannot move on while no approved participants are listed, or until «participants and currency coverage checked» is ticked. The limits step, by contrast, can be skipped."],"example":"The scheduled 08:00 window did not go through: the node was unavailable. You open the wizard â three participants are approved, covering USD, EUR and AED. Gulf Exchange Ltd settles on-chain but has no address, and the wizard warns that its deals will not reach the network; Nordwind Fund has the rate guard switched off. You tick «participants and currency coverage checked». On the limits step you select Nordwind Fund, enable the rate check, set a tolerance of 500 basis points (that is 5%) and «reject the deal» when the rate cannot be verified, then apply it to the participant. On the window step you choose «retry an unfinished run» and the 2026-08-21 08:00 window from the list. You write the reason: «The 08:00 window was not executed because the node was unavailable; the retry is agreed with the participants», tick the confirmation and run. Result: 42 instructions settled, netting savings 78.3%, no errors.","tips":["The reason is mandatory, and eight characters is only the form's minimum: the server rejects a request without one. Your exact text stays in the log and is what people later use to reconstruct why a run happened off schedule.","The engine has one minute to answer. If the run exceeded that wait and came back with a timeout error, do not fire it again blindly â the settlement may have carried on. Open the Settlement section and see how the window ended.","In «a past window» mode the time is UTC: the field is prefilled from your computer's clock and is sent as is, with no timezone conversion, and on blur it snaps to the start of its four-hour window. For a retry it is safer to take the window from the list, where the run time is already set.","Enabling the rate guard on the limits step does not revisit what is already stamped for the window. Sort out a questionable deal before the run: a completed settlement cannot be undone."]},"orgOnboarding":{"title":"New organization onboarding","summary":"In one pass the wizard creates an organization, invites the team with roles, assigns a pricing plan, switches billing on and applies a referral bonus. Every step writes to the server on its own and immediately, so there is no way to cancel the wizard: the organization survives even if you leave halfway. The step order is not cosmetic â the bonus is credited in the billing currency and therefore strictly follows its selection.","whenToUse"
1:"When a new client or partner joins the platform and needs a workspace. An administrator creates the organization for a client and assigns the plan; a client walking the wizard alone never sees the plan step â the platform assigns it. Processing, payment pages and limits are configured afterwards, once the organization exists and is selected in the top switcher.","concepts":["The owner is the client the organization is registered to. An administrator picks one from the client list; in self-service the signed-in user becomes the owner and the selector is not shown.","The organization address (slug) accepts Latin letters, digits and hyphens only, 3 to 50 characters. A Cyrillic name derives no slug in the form, and the server's own attempt at one fails validation, so a Latin address has to be typed by hand.","A name is unique per owner: resubmitting the same form does not create a twin â it returns 'an organization with this name already exists'.","The environment (test or production) is chosen at creation and defines the contour the data lives in. It can be changed later in the organization edit form on the organizations list, but a new client is better started on test.","An invitation sends no email. The member is written into the organization, and if no client with that address exists yet, a pending invite is stored and linked when they register. Telling the person about their access is on you.","A pricing plan is attached the moment the organization is created (the default starter one), and the plan step replaces it. The billing currency is not stored in the organization settings: this step only enables billing and carries the currency forward â the bonus is credited in it."],"example":"OOO Severny Veter joins the platform. You type the name in Cyrillic, so no slug is derived â you enter severny-veter by hand; environment test, owner â the client [email protected], primary color #004D40, QR providers sbp, alfa. Creation takes up to a minute while storage, wallets and settings are provisioned; leave the page alone meanwhile. On the members step you add three people: the chief accountant as Finance and two support staff as Support, granting the right to invite only to Finance. You assign the Business plan instead of the starter one. RUB becomes the billing currency and billing is switched on. The referral code REF-4PAY26 validates as 50.00 USD; you apply it and the summary shows +450000 RUB â that is 4,500.00 RUB in minor units. From the summary you go to the organization's billing and top up the wallet.","tips":["Do not reload the page while the organization is being created: the request is longer than usual, up to a minute. If you left anyway, the organization is most likely there â look for it in the organizations list. It cannot be deleted, only archived, and that is available to an administrator or the owner.","A Cyrillic name without a manually typed Latin address fails on creation: only a-z, 0-9 and hyphens are allowed, 3 to 50 characters long.","Set roles and the invite right before sending: the wizard does not edit them afterwards â changes happen on the organization members page.","The referral code's face value is denominated in USD, while the credit is made in the billing currency at the internal rate; with no rate for that pair the request is rejected with a rate error. The amount in the summary is shown in minor units â divide by 100."]},"enterpriseSso":{"title":"Enterprise Access and Authentication (SSO)","summary":"The wizard moves an organization's sign-in from internal passwords to a corporate provider â Google Workspace, OIDC or an LDAP directory. The step order is the safety mechanism: the fallback login is prepared first, the configuration is assembled next, and only after a verification login is it written in a single irreversible request. A mistake in the provider parameters locks the whole organization out, and the only way back in is the internal administrator with a password or emergency access.","whenToUse":"When the client's security team requires staff to sign in through the corporate directory instead of individual passwords. The organization must be selected in the top switcher and must have the SSO module enabled â without it the settings write is rejected. After the switch new staff receive their role automatically, while fine-tuning stays on the organization's SSO settings page.","concepts":["Emergency access is a temporary session for the organization: a reason of at least ten characters and a lifetime from the list of 30, 60, 120 or 240 minutes. It is activated by platform staff â the endpoint is an administrative one and a client account does not have it. Its lifetime is finite; it covers the transition only.","The internal administrator is a member with the Administrator role added by email on the first step. They sign in with a password bypassing the external provider and remain the durable fallback once the emergency session expires.","The provider and domain steps write nothing. Everything you enter accumulates in the wizard and goes to the server in a single request on the verification step â until that moment the live sign-in is unchanged.","The configuration is written as a whole and replaces the stored one. For Google and OIDC the secret is mandatory: without it the server rejects the write with 'OIDC requires: client_secret'. An empty LDAP service-account password does not preserve the old one â retype it.","Allowed domains reject sign-ins from foreign email addresses. An empty list means 'any domain is accepted', not 'sign-in is closed'; for an LDAP directory domains are not sent at all.","Auto-created accounts receive the default role â Viewer initially. Role changes for existing members on the sync step are saved immediately, in a separate request, and stay in force even if you never complete the switch."],"example":"A client moves the team to Okta. You open the wizard with the organization Sever
1ny Veter selected. Emergency access: reason 'Moving to corporate sign-in at the security team's request', lifetime 120 minutes â activated. You name [email protected] the internal administrator and tick the fallback-ready confirmation. Provider â OIDC: the Client ID from the Okta console, the secret (the write fails without it), Issuer https://sevveter.okta.com/oauth2/default. You allow the single domain sevveter.ru and enable auto-created accounts with the Viewer role. On the role sync step you raise two members to Operator and leave the internal administrator as Administrator. In a separate incognito window you sign in through Okta, walk the three checklist items, tick 'the sign-in works', then 'I understand the consequences', and press Switch provider. From that minute sign-in goes through Okta.","tips":["Run the verification login in a separate incognito window: your current session is still authenticated the old way, so a misconfiguration simply will not show.","The fallback-ready checkbox only unlocks after emergency access is activated and the internal administrator is assigned â the wizard will not move on without it. This is not a formality: those two are what you will recover access with.","The emergency session expires after the minutes you chose; the internal administrator remains. Enable two-factor authentication for them right away â a password login bypassing the provider is the weakest point of the scheme.","The LDAPS toggle swaps 636 for 389 and back only while the field holds the standard port; a non-standard one is left untouched. Check the field yourself before moving on.","The switch has no rollback. Password sign-in can be restored by choosing the Internal provider â by running the wizard again or on the organization's SSO settings page, that is, only from inside the cabinet."]},"whiteLabelGoLive":{"title":"White-label Go-Live â under your brand","summary":"The wizard assembles and publishes a payment page configuration under the client's brand: name, accent color, default theme and, if a domain is given, the post-payment return address. Publishing is a real action: the configuration is created, published, gets a version number and a public link token. The wizard creates a new configuration every run and never edits an existing one, so changing the color or theme of an already published page happens on the Payment pages screen.","whenToUse":"When a partner or client starts accepting payments and the checkout page has to look like theirs, not the platform's. Run it once the organization exists and is selected in the top switcher â the configuration is created in its context. The logo, the domain binding and moving the contour to production come later, on the dedicated screens.","concepts":["The configuration address (slug) is derived from the brand name: Cyrillic is transliterated, everything else becomes hyphens, and the length is trimmed to 50. It is never shorter than three characters â the wizard prefixes brand- if needed. Within an organization the address is unique.","The accent color is picked from five presets and lands in two places at once â as the branding primary color and as the page's style variables. An arbitrary HEX cannot be entered here.","The 'System' theme is not sent to the server at all: the page accepts only light or dark, so with 'System' it keeps its own default.","The domain is not bound here. It is only used to build the post-payment return address of the form https://domain/payment/result?txid={txid}&status={status}; the wizard strips the scheme and trailing slashes itself. The CNAME record pointing at wl.4pay.online and the certificate stay outside the wizard.","Publishing takes two requests: the configuration is created as a draft first, then published. Publishing bumps the version number and issues a new public link token; by default the token is valid for 24 hours, and the next publish replaces it, so the previous link stops working.","The wizard does not upload a logo. Under the brand it sets the name, the color and the theme; the logo and the rest of the palette live on the branding screens."],"example":"A partner lau
1nches payments under the PayFlow brand. You enter the brand name PayFlow (the field holds up to 40 characters) and pick the Azure #1E88E5 accent. You type the domain as https://pay.example.com â the wizard normalizes it to pay.example.com and builds the return address https://pay.example.com/payment/result?txid={txid}&status={status}. You choose the dark theme. The summary reads: brand PayFlow · Azure, domain pay.example.com, theme Dark, configuration address payflow. You press Launch under the brand â the configuration is created and published, and the message reads 'Contour published: payflow'. Then you open Payment pages, take the link with the token and hand it to the partner, while the CNAME record pointing at wl.4pay.online is created at the domain registrar.","tips":["The brand name is the only mandatory field and the source of the address. A Cyrillic name is transliterated â «ÐÑйФлоÑ» becomes peiflou â so choose a Latin spelling when the address matters.","Running it again with the same brand name will fail: the address is already taken inside the organization by the earlier configuration. Make corrections on the Payment pages screen, and pick a different name for a second page.","The domain typed here does not switch the page on at that address. Without the CNAME record and a certificate the return address leads nowhere â set DNS up before handing the link to the client.","The link with the public token is valid for 24 hours by default, and every new publish issues a different token. Give the partner a freshly taken link rather than one saved in advance."]},"products":{"title":"ááá¶á½","summary":"á¨á áá á¥ááá½ á«á³ááᦠáµáᣠáááá«á£ á á°áá¨á á áááᬠáá á¥á á¥ááµá¢ áááµ á¨ááá« á á¥ááµ ááᦠáá¢á áá áá á«á± á¨áá»á ááá
ááá á¥áá°áá¨áá á¥áá²á«á á¨ááá« áá½ ááá á ááá áá áá«á«ááᢠááá± á«á± áááᥠá á«ááá³á
áµá â ááá«á á á°ááááá½ áá á á°ááá© áááá¶á½ ááá³áá¢","whenToUse":"á±á áá» áá á á«áá á
á½ ááá
á ááµ á¨á°áá°á á¥á â áááµá£ á áááááµá£ áááᣠâ á¨áá«áµá¨áá á ááá á²áááᢠáá áááµá°á«á¨á ááá á¥áá á¨ááµá®á± áááµáááµá á¥áá
ááá£áᢠ«á¨ááá« áá½ áá°á» á áá á ááááµ áá áááµ ááá¥á«áᣠá¨áá á¨áá á áá áááá ááµá¥ áá³á«áá¢","concepts":["áá á áá á¨áááᬠá áá¶á½ ááá£áᣠá áµááá½ á áá¶á½ á áá°ááᢠááµá¨á© á áµááá½ á áá¶á½ á«áµááá£á á¥á á áµáá á© áá á«á± áááá£áá¢","áááᬠá¨ááá± áá á¥á á°á¨á°á á áá á¥áá°ááᣠáááµááᢠá¨áªáµ á¦áá³á áááᬠáá ááá³á°á á¨áá áµáᦠááá£áá á¨ááá á« áááá± á«á¨ááááá¢","á¥ááµ á¨áááá ááá½áµ á áá°ááᣠá¨ááµáá© áµáá á á£á¢ ááᢠááµá¨á© ááá½áµ á áááá á ááááµáá¢","áááµ á¨á áá áá á¨á°á³á°á¨ ááᢠá°áá áá á¨áµáá
á±á á¥ááá½á£ á¨ááµá¨á á áµá°á³á³áªá áááá á«á«á â á°áá³á³á© áááá á áá ááá«á«áá¢","áá°á¨á á¨áááááµ áá á¥á á áµááµá á¨á°áá á© ááá«áá½á á áá°áááᦠáá°á á¥á á¨á°á°á á ááá ááµá«á±á ááá¥ááá¢"],"example":"á ááµ áááá¾á á¥áµáááµ á 3,500 â½ áá áááᢠ«á¨á¥áµáááµ á¥áá» á¨áá áááµ ááá¥á«áᣠá áááá«á ááµá¥ áá á¥áá°áá«á«áµáµ ááá¨áá«áᣠáá 3500ᣠáááᬠRUBᣠá¥ááµ 1ᢠá¨á᫠«á¨ááá« áá½ áá°á» á áá á áá
áááµ ááªá« á ááá áááá£á á¥ááµáá áá°áá áá ááá«áᢠáá¢á áµááᣠáááá«áá á¥á áá áá á áᶠáá¨ááá â ááááá á «áá¥áá¶á½Â» ááµá¥ á¥áá° á°á« ááá á áá³á«áá¢","tips":["áá¢á áµááá áááá«áá á ááá« áá¹ áá á«áá£á â á¨ááµá¥ ááµá³áá» á áá°ááᢠá¨á£áá áááá«á á áá á¥áá²áᣠá áµááá áá»áá¢","á¥á á¨ááá áá á ááµ á¨á áá© á¨ááá« ááá á á¥áá°áá°á« á«á¨ááá¡á¦ ááá± á«á± ááá á á«áµá¬áµáᣠá¨áá°á« á°áááá á¨ááá á ááá á á¥áá¢á³ áá ááááá¢","ááá áµáᣠáááá« á¥á ááá«á áá¸ááá â á áá áááá á áá»ááá¢"]},"paymentLinks":{"title":"á¨ááá« á áááá½","summary":"áá¢áá á áá¥á³ áá° ááá« á
á½ á¨áááµáµ á áááᢠá¥á«áá³áá± á ááá áá áá áááᬠá ááᤠáá á áá (áá¢á áá á«áá áá¨ááá) ááá á°áááá (á áá¨ááµá áµ áá áá°á£á) ááá áá½ááᢠá ááá á«á± ááá« á á«á¨áááá â á
á¹á áá¨áá³áᣠáááá¡ á á°ááááá½ áááá¶á½ ááá³áá¢","whenToUse"
1:"á°á¨á°á á ááµ áá á²áá£á¦ á ááá¥ááµá£ á á¢áááᣠá«á áµá¨ áá½ áá
á°áµá¢ á¥áá
á áá á áááµá°á«á¨á ááá á ááá ááá°á¨á ááá£áá¢","concepts":["áá á á áá á¨áááᬠá áá¶á½ ááá£áᤠááµá¨á© á«á± áá° áµááá½ á áá¶á½ áááá£áá¢","áá áá á áá¢á á¥áá²ááá¨á á ááá
áµáᤠá°áááá ááá
á³áá¢","á á ááá á¨á°áá¨á¡ á¨ááá« áá´áá½ á á°áááá áááá á áá£á¸áᣠá áá ááá« á
á¹ á£á¶ ááááá¢","á ááá á¥áµáªá°á¨á áµá¨áµ ááá«áᤠáá°á¨á á¨áááááµ ááá¢","á¨áá á ááᥠá¨áá« á áá á áááá ááá¨ááµ áá áá²á«áá á°áá£á«á ááááᢠá áµááµáá áá¨áááµ ááá á¥áá°áá á áá°ááá¢"],"example":"áááá¾á ááá¥ááµ 12,000 â½ á°á¨á°á ááá£áµ á áá áµá¢ á ááá ááá¥á«áᦠáá á 12000ᣠáááᬠRUBᣠáááᵠ«áá»ᢠá áµá«á»áá ááá¥á á áá°áá áá ááá«áá¢","tips":["á¨áááá á ááµ á áááá á«áµá áááá±á¤ á£á¶ á
á½ áááµ áá´á á áá°ááá¨á áááµ ááá¢","á ááá ááá á áµá«á» ááᦠá¨áá áá¨á á á«áµááá¡á áµá¢","á ááá á¨ááᥠá áµá«á» ááᢠá¨á°áá áá áá áá áá á«á«á ááááá áá½ááᤠáµááá
á¨áá áá¨á á á«áµáá¡á áµá¢"]},"savedCards":{"title":"á¨á°ááá¡ á«áá¶á½","summary":"áá°á°ááá ááá« á¨á°ááá¡ á¨áá¢áá½ á«áá¶á½ áááá¥á¦ áááá£áá½á£ á«áµ-á°á ááá«áá½á¢ ááµá¨á© á¨á«ááµ áá¥á®á½á á á«áµááá¥á â ááá¥áᣠá¨á«ááµ á áá³áᣠá¨áá¥áá« ááá á¨á á
á«á¢á á¶áá á¥á»á¢ ááá«á á á¶áá ááá³áᣠáµááá
á«áá±á «áá¨áµÂ» á áá»ááá¢","whenToUse":"á°á°ááá ááá« á²áá¨ááᦠáááᣠá áá³á°á°áᣠáá¢á á«áá±á á¥áá²áááµ á á¨áᢠá«áá¶á½ á á«á³á¸á ááá£áᤠá á¥á
ááá á á áá»ááá¢","concepts":["ááá¥á á¥á» áá³á«áᤠáá áá¥á á á¨áµá á¨áá (PCI DSS)á¢","á¨áá¥áá« áá á¨á«áá± áá á¥áá á¨áá¨áá» áá á áá°ááá¢","ááá á áᢠá¢ááá ááá ááá« ááá³áᤠá á«ááµ áá¥á á áá»ááá¢","áá°á¨á á¨áááááµ áá á¥á á°á«á«á¥ áááá£áá½á á«ááá£áá¢","áá°á¨á á¨áááááµ á²áá á áá« á«ááµ áá á¨á°á³á°á© áááá á°á°ááá ááá«áá½ á«ááá£áᢠáááá£á á¨áá« á áá á á¸á¥á³ á áá³á°áµá â áááµááá¢"],"example":"á°áá á áááá£á áááµ áá á¥áá°á°á¨áá áááá«áᢠá á¢ááá áááá áááµ á«áá¶á½ á«áááᦠá áá± ááᣠááá ááá á«ááá áµá¢","tips":["á¨áá°á¨áá á ááµ á á«áá± áá áá áááᣠá áááá©á á«á¨ááá¡á¢","á«áá¶á½ á¨áá³á©áµ á¶ááááá½á á áá°áá á á
á«á¢áá½ á¥á» ááá¢","á«áá¶á½ á¨áá³á©áµ á¶ááááá½áá á áá°áá á á
á«á¢áá½ á¥á» ááᢠá°áá£ááá± á¥á¨á á« á³á á£á¶ áááá áááµ á¨áá áá°á áááá áá
ááá¢"]},"shopCategories":{"title":"á¨áá°á¥á ááµá¦á½","summary":"á¨á áá áá°á¥áá á¨á¥á« ááá á¨áááµá¥ áááá¥á¦ á¨áá³á£ ááááµá£ ááªáá¶á£ áá á«á£ á²áá³á áááá½á£ á ááááá¶á½á£ áááá£áá½á£ ááá³áá½á¢ á¥á«áá³áá± áááᥠáá°á¥á©á (ááá«á£ ááá´á£ á á
á«á¢á£ á»áá) á¨ááµá¥ áá á«ááááá¢","whenToUse"
1:"á á²áµ áá°á¥á á²ááá á¥á á áá¢á á°á¨á°á áá á¨á°á³á³á° áµá á²á³áá¢","concepts":["ááá á¨áá°á¥á© ááá« á¥á» á áá°ááᤠá¨ááá´á£ á á
á«á¢á á»áá áá ááá¢","á¨áá°á¥á© á¨á«á± áááá« á¨ááµá¡á áááá« áá¸áááᤠááá« á½áá á£á¶ áá°ááµá¢","á¨ááµá¥ áááá« á¥áá²á á« á á°áááá \`default_description = '{{shop_category}}'\` áááᥠá áá áµá¢","á¨ááááµ ááááµ áááá¡á á³áá°áá á«á ááá¢","ááµá¡ (gaming, gambling, crypto, marketplace, digital_goods, services, subscriptions, donations, other) ááµáá¢á« á áá°ááᤠá á
á«á¢áá½ á á¥á± áá á°ááµáá°á á¨á á°á áá³á áá°á£áᣠá áá³áá¶á¹á áá á¨áááµ áááá½á áá¨ááááá¢"],"example":"á¨ááá áááᣠáá°á¥á «UNKNOWN MERCHANT» áá áá³á«áᢠsubscriptions ááµá¥ á«áá áááᥠáá¥á¨á áááá«áá á£á¶ áµá°á á á°áááá \`default_description = '{{shop_category}}'\` á«áµááá£áá¢","tips":["ááµá¥ ááá¨á á°á¨á°á á áá°áá¨á¨áᦠá¨á°ááááá á
áá¥á áááá¨á±á¢","gambling á¥á ááªáᶠá á¥á á á
á«á¢áá½ á¨á°á¨áá¨á áá¸áá¢","gambling á¥á crypto á á¥á á á
á«á¢áá½ áááµ á¨á°á¨áá¨á áá¸áᢠá¨áááááµá á ááµ áááá± á«áá ááá áá°ááá á á á
á«á¢ ááá«á±á á«á¨ááá¡á¢"]},"categoryDescriptions":{"title":"á¨ááµá¥ áááá«áá½","summary":"á áá°á¥á© á´ááá«á áµá ááá³ á áá¢á á¨ááá« á°áá¶á½ áá á¨ááá¡ á½ááá½á¢ áááá¡ á¦áµáµ ááá ááᦠááµá¥á£ ááá á¥á á½ááá¢","whenToUse":"á°á¨á°á áµááá á«áá áµá á²ááá á¥á á á²áµ áá á« á²áá¡á¢","concepts":["áááá«á á¨ááµá¡ áá á¥áá á¨áá°á¥á© á áá°ááᦠá ááµ ááᥠá¨áá« ááµá¥ áá°á¥á®á½ áá ááá«áá¢","ááá á¨ááá á á«á ááᤠá½áá á áááá áµá
á°áµ á áá°ááá¢","á¨áá°á¥á© á¨á«á± áááá« áá
á á¨áá« á½áá áá¸áááá¢","á°á°áªá á¨áá á«á á°áááá \`default_description = '{{shop_category}}'\` á²áá¨á á¥á» ááá¢","á°áá±á á¨áá«áá á áá¢á á¥áá á á«á°áá á áá°áá â á¨ááá«á á³ááá³áµ á ááᣠá á áá³ ááµáá áááá ááµá¥á¢ á½áá á«á á ááµ áá³áá
á áá áµá¢"],"example":"áá° áµááá½ áá á« ááá£áᦠsubscriptions ááµá¥á£ es áááᣠ«Suscripción digital» á½áá áá¨áá«áá¢","tips":["á¨ááá á á«á áµáá á¨áá áá¥á á á«áµáá¡á¢","áááá±á áááá¨á±á¦ á£áá®á½ ááµáá©á áááá£áá¢","á á²áµ á½áá á¨áá¨ááá á ááµ á«ááµá ááµá¦á½ áááá¨á±á¤ á á¥áááá áá á¨áááµáá áµááá á¥áá á á²áµ ááµá¥ á áá°ááá¢"]},"ledgerCorrections":{"title":"á¨ááá ááµá°á«á¨á«áá½","summary":"á á°ááá°á ááááµ á¨ááá»á á²áá á¨áªáµ á¦áá³ áá³á¥á á¨áááá á á¥á
á¨áá°á¨á áááá£á¦ á¨ááµá³á¨á
áá©ááµá£ á áµá
á°áµ á¨áᣠááá«á£ á«á³á¢ ááµá°á«á¨á« á«áá áááá¦á½á á á«ááá á áá°ááá â á á²áµ áááᣠáá¨áá«áá¢","whenToUse":"ááµá³á¨á
áá° áá® á³ááᣠáááá«á± á²á³áá
ᣠááá á á
á«á¢á á¨á°ááá°á áá°áµ áá áááᥠá²áááµá¢","concepts":["áá á á áá á áá¶á½ ááá£á á¥á á áá³á ááá áá½ááᦠá²áááµ áááá³áᣠá²á°áá áá¨áá«áá¢","á¨áªáµ á¦áá³áá áááá¬á á ááá½ á
1ááá£áᤠáááá¬á á¨áªáµ á¦áá³á áá ááá³á°á á áá áµá¢","á¨ááµá°á«á¨á« áá á áááá¡ ááµá¥ á«áá á¨áááᣠáá áá á¥áá á¨áá á©á áµ áá á áá°ááá¢","áááá ááá°á á°á¨á áá¨ááá« áá áááᦠ2FA á«ááá áá¹ á á«á³áááá¢","áááá ááá°á áá¨ááá« áá áááᤠ2FA á«ááá áá¹ á á«á³ááááµáᢠáá
á¥á¥á
ááµ á áá°áá â á¥áááµ áááá¥á á¨á°ááá±áµ áá°á»áá½ áá á«ááá³á
á³áá¢"],"example":"á¨ááá°á ááµá³á¨á
á 1,500 â½ á°áá«á¨á¦ á á
á«á¢á ááá«áá áááµ áá á áµáá¥á·áᢠâ1500 ááµá°á«á¨á« á RUB ááá¥á«áá¢","tips":["á¨áá¨ááá¥á á ááµ áááá±á áááá¨á±á¦ ááµá°á«á¨á« á á°áá«á ááµá°á«á¨á« á¥á» áá°á¨ááá¢","áá á áá£áª á¨áᬠááᤠá«áá áá á²á«áá áááá©áµá¢","á ááµ á¦áá³ á°ááá á¥áááµ á¨áá«áµáááá á¨ááᣠáááá«á± á á¥áááá áá áááá± ááá á¨á á
á«á¢á áá
á á¥áá á¦áá³á á áá°ááá¢"]},"ledgerAggregates":{"title":"á¨ááá áµá¥áµá¦á½","summary":"á¨áááá¡ á¨á°á ááá áµáá®á½á¦ á á°ááµá£ á ááᣠá ááᢠááµá¨á© á á°ááµ á ááµ áá á«á
á á¨áá© áááá£áá½á áá°á áµá£áᣠáá³á¡ á ááá®á á³ááá á á°ááá ááµáá®á½ á¥áá²á°áá¢","whenToUse":"áá³á¥ á«á¨á á²ááµá ááá á¨áááá¡ á²áá«á â áµá¥áµá¡ áá°ááááá áá ááµá¨á± á¥áá
áá³á«áá¢","concepts":["áµá¥áµá¥ áµáá áá á¥áá á
á á áá°ááᦠáá á áááá£áá½ á áááá¡ ááá«áá¢","áá°á¥á°á¥ á ááá áá¥á ááá³áᤠá á²áµ áááá£áá½ áá¥ááµ áá á¥á¬ ááá ááá«áá¢","á°á¨ááá½ á°á°á«áá ááᦠá°áá¶á½ áá° áááµá£ áááµ áá° áá«áµá¢","á¨á¥á¬ áááá£áá½ á¥ááµ á ááá«á½ ááᦠá²á¨áá áá³á¦á½ áááá«áá¢","áµáá®á½ á¨á°áá áá¸áᤠá¨áááá¡ á¥áá°áá áá°á áá½ááᣠá áá±á áá£áµá áááᥠá á«á ááᢠáááᥠáá£áµ áá á«á ááá¢"],"example":"á áá á¨áµááá± á½á«á á«áá° áááµáááᢠáµá¥áµá¦á½ á¨áá½áµ áºáá½ áááá£áá½ áá á ááá°á¥á°á£á¸áá á«á³á«áᦠáµá
á°áµ á³ááá áááá¨áµ ááá¢","tips":["á¨á á áááᥠá¨ááááá á ááµ áá°á¥á°á¡ áá°ááááá á°ááµ ááµá¨á±á áááá¨á±á¢","ááá á¥áá°á°áá áá²á«á áªáááµ á áááá¡á¢","áá
á± á¥áá°á°áá áá²á«áá áªáááµ á áááá¡ â á¢á«ááµ á ááµ á¨áá ááá« áá°áµ áááá¢"]},"balance":{"title":"áá³á¥","summary":"á¨á«á¢áá á¨ááááªá« áá« áá½á¦ áµáá
á± á á¥á«áá³áá± áááᬠáá á«á
á á ááᢠáá á á á°ááá á áá á£á á
áá á°á¨ááá â á¨á°ááá á°á¨ááᦠááá£áµ áá»ááᣠá áá á£á á
áá á«áá á°áááá§á áá áá á áá°á ááááᢠáá¹ á«áááá áááááá áá áá³á¥á á áááµ ááá«áµ áá«á¨á á«ááá áá©ááµá á«á³á«áá¢","whenToUse":"á á¨á áá± ááá³áá ááá¨á³áµ á¥á áá¥á á¨áá á áá áá á³ááá³á°á á²ááá¢","concepts":["á¨á°ááá á áá á£á á
áá áááµ áªáµ á¦áá³ á áá°ááᤠá¨á áá± áááµ áááá½ áá¸áá¢","áá³á¥ á¨ááá áµá¥áµá¦á½ áá°ááᣠáá°á¥á°á¥ á á°ááµ á ááµ áá ááᦠá á²áµ ááááá½ áááá°á áá°áá³áá¢","á¨áá á°á
á áá áá½ áááá£á á¥á á á³á
1ªá«á ááá³ áá á°á½áá á ááá¢","áááá¬áá½ á áá°áá©áᦠá¥áá
á á ááá áµáá á¨ááá¢","áá½á½á© á¨ááááá½á áááá á³ááá ááá¡á á«á³á«áᢠáá©ááµ á«á© á áá áááá© á ááá áááᥠááµá¥ ááá¢"],"example":"á áá á°á 40,000 â½ á¨á áá á¥áá°áá á¨á áááá«áᢠá¨á°áâá¨á¡á áá½á½á â40,000 â½ áá°á£áᤠá áááá¡ á¨á°á¨á³ ááá« ááááá¢","tips":["á á á¥áá á¨ááááá á ááµ áµá¥áµá¦á½á áááá¨á±á¢","á «á¨á°áá» á¥á «á á
áá» áá«á¨á á«áá áá©ááµ á ááááµ áá á«á áááᥠááá¢","á¨á³áªá á᪠áá³á¥ ááá á³ááá áá
á½á áµ áá°ááᤠá°áá± á¥áá° áá áá áá³á ááá¢"]},"treasuryBridge":{"title":"ááá á¤áµ","summary":"á¨ááµá¨á© áááᥠá áááá¬á á ááá« áááá¶á½ áá ááá«á¢ á á¥á«áá³áá± ááááµ áá á«á
á á¥áá³áᣠáá á«á
á á¥áá°á°á«áá áá á«á
á á¥áá°ááá á«á³á«áá¢","whenToUse":"á ááµ ááááµ áááá« áááᥠá²á«á¥á¨á ááá áµáá á²áá¨áá¢","concepts":["á¨á°á«á áááµ áá á£á áá« á áá°ááᤠá á°ááá© áµáá¶á½ ááµá¥ á«á áááᥠááá¢","Islamic Pots á¨áµáá áµáá» á«áá¸á á¨á°áá© áááá¦á½ áá¸áá¢","áá ááµ ááµáá á£á¶ ááá áá® á¨áµá á¥áá½áµá á á«ááááµáᤠá áá áááá á¨ááá áááᬠááá áá½ááá¢"],"example":"á¨á©á® ááá«áá½ áááᥠá¥á«á áá¨á½ááᦠá SEPA 900 ⬠ááááᣠ40,000 ⬠á°áááá¢","tips":["«á¨á°á«á» áááá±á á«áá á½áá© á ááá á¤á± á³ááá á á á
á«á¢á á°áá« áá ááá¢"]},"dclsMyWorkspace":{"title":"á¨á¥á dCLS","summary":"á áááᬠáá¥áá¶á½ áµááµ á áá³á¨ áá¨á¥ ááµá¥ á¨á°á³á³á á¨á¥á« á¦á³á¢ áµáááµ áá« áá¾á½ áµá á ááµ ááá á¨á°áá«á© ááá½á¦ á á áá³á© áá á¥áá°ááá áá°á¦á½á áá á¥áá°ááᣠááááᥠá«áá¨á¡áµá£ á áááᥠá¥áá´áµ á¥áá°á°á áááᣠá¨á¶áá ááá£áµá ááááµá£ á¨ááá³á áááᥠááµáá£áµá ááá£áµá£ á¨á áá®á½á áááµ áá¨ááá½á á¨ááµá°á¶á½ áááá¥á¢","whenToUse":"á ááµ á¨á°áá°á áá¥ááµ ááá¨á³á°áᣠááá á áá®á½ áá³ááá á²á á¥áᦠá«áá± á¥á«ááá»á¸á á áááá³áá±áá¢","concepts":["áá°á¦á½áá áá½á°á
á á¨á áá³á© á¦áá¬á°á áááµáá á¥áá á¥ááµá á áá°ááᤠááá£á¥ á¥á» áá¸áá¢","áááªá« á¨áááᥠá¥á«á áá á¥áá áááá¡ á áá°ááᦠá á» áááá áá£á©á á¨áá²áá ááµá®áµ áá á¥ááá¢","á áµááµ áá« áá½ áá á ááá³á áá³á¥ ááá á áááµ ááᣠá áá³á á°áá áá´á³á¢","Mint á¥á Burn á áááµ á°á¨á ááá³áᦠá¨ááµá¨á© áá½á°á
ᣠá¨áá« á á°áá°ááµ áá á á ááªá ááá¸áá¢","á¨á áá®á½ áá¨ááá½ áááááµ áá¸á á¥áá áá³ááá« á áá°ááá¢","Audit trail ááá£á¥ á¥á» ááᦠáááá á¥áá« á¨áá á áá°á¨á°á°á áááµ ááá¢"],"example":"á áá ááá£á± á¥áá³áá°á¨á° á«ááá«áᢠá¨Deposit/Withdraw áá¨á á¥á«áá á¦áµáµ áá á³áá¸áµá
á¥áá°áᨠá«á³á«áᢠá«á¸áµáá³áᣠá¨áá¨ááá« á áá á¥áá°á°áá¸á ááááá£áá¢","tips":["áááá«áá á¨audit trail áááá© á¥áá á¨á°áá¨á¨á áµ áá« áá½ á áá°ááá¢","«á¨á°áá áá á» áááªá« á á¥áááá áá áá£á©á á¨áá²áá ááµá®áµ áá á¥ááá¢","á áá°á¥ áááá«áµ á¨á°áá£áááµ á«á£á á¥á«á á¥áá°áá ááá á¥á
á á¨ááá â á¥áá°áá ááµá
ááááᢠááááªá« á¨á áá³á¨ áá¨á¡ á ááá³áá½ áá°á¡á áááá£áá¢"]},"clients":{"title":"á°áá áá½","summary":"á¨SaaS ááµá¨á á°á áááá½ áááᥠâ áá° á«á¢á á¨ááá¡á á¨áµáá
á³á¸á áá á¨áá á©á¢ á°áá á áá¢á á ááá á áá°ááᦠá¨á¦áµá± ááá°áá á°á¨á ááá¢","whenToUse"
1:"áá³á¨á»á á²áá±á¦ á ááµ á°á ááá£áµ á áá»ááᣠááá°á á°á¨ááá á á£á£ ááá ááá áµáá
áµ á á«ááá¢","concepts":["á°áá á ááá« áá á¥áá áá á áá°ááᦠáá¥á¶á½ á¨áµáá
áµ á á£áááµ ááá£áá¢","áááµ á°á¨á áá¨ááá« á¥áá° ááááµ á¥á» áá³á«áᣠá¨áá
á ááµá°á«á¨ááá¢","á¨áá¨á¨á» ááá¢á« á¥áá
áµáá´á á ááá«áᦠá API ááá á¨áá á« á«á¢ááá á áá¨ááµáá¢","áá¹ áááµá¨á á áµá°á³á³áª á¥á» ááá¢"],"example":"á á²áµ á á«á°á ááá áµáá
áµ á á«ááᢠááá«á á áᣠáµáááµ áá¥á·áᦠá½áá© á á£áááµ áá á¥áá áá³á¨á» á áá°ááá¢","tips":["á°áá á á¨ááá áá á ááµ á á¢ááá ááááá¢","á°á ááá áá¨á á«áᨠá¨áµáá
á±á á á£ááµ áááá¨á±á¢","á áᨠááá« áá á£á¶ á¨áá¨á¨á» ááá¢á« á á¥áááá áá áá¥á£á á áá«á½ á áááá áá á«á³á«áá¢"]},"persons":{"title":"á°áá½","summary":"á¨áá ááá«áá½ â ááµá¨á© á áµáᣠá ááááµá á áááᬠá¨áá«ááá¸á á°áá¥á¯á á°áá½á¢ á¨á«á¢á á°á áááá½á áá¢áá½á á áá°ááᦠá°á á¨áá«áµáááá áááá á¨á°áá°á ááá°á¥ áá á²á°á³á°á ááá¢","whenToUse":"áááá á¨á°á¨ááá á°áá¥á¯á á°á á²á áá
ᣠááá áá¨áá á²á«á¨á
á¢","concepts":["á°áá á°áá á á¨á°áá«á© ááá®á½ áá¸áᦠá°áá áá áá° á«á¢á ááá£áᣠá°á á áá«á½ á ááá£áá¢","ááááµ á¨á°áá¢ááµ áá°á»áá½á áááµáá á¥áá áá¨ááµ á áá°ááá¢","á¨á°áá¨á áááᬠáá£áª á¥á´áµ áá á¥áá áá°á¥ á áá°ááá¢","ááá³á ááááá½ áááá± á¥áá°áá áááá«áᤠá¨á³áá° á°á á áááá¡ ááá«áá¢"],"example":"áá° ááá°á¥ á¨áá°á¨á áááá á á°áá¢ááµ áá¨áá¨ááᦠáááá± á°á³áµá·áᢠá°áµá°á«áá áá°á»á á«áááá¢","tips":["á¨ááááªá«áá á¨ááµá°á«á¨á ááá
ááá°á á°á á ááá á©á¢","á ááá ááá á á¢ááá ááááá¢","á ááá¢á« áµá ááá á á¢ááá ááááᤠá áµá á²ááá á°áá³á³á áµá á«áá á°á áá ááá°á
ááá ááá¢"]},"apiConsole":{"title":"á¨API á®áá¶á","summary":"á¨á«á¢á ááµá¥ áá° ááµá¨á© API áááááá á¥á«á áááᦠáá´á£ á áµá«á»á£ á á«áá á¨áááµ ááááµá¢ á á¥áááµ áá á«á â á¨áá¨á« á¦á³ ááá á
áµá á¥áá³ á áá°ááᢠPOST ááá¥á«áᣠDELETE áá°áááᣠááááµ á¨ááá¢","whenToUse":"á¨áá³á¨á» áá¥á¥ á£á
᪠á²áá°á½á£ á¨áá
á°áµ áµá
á°áµ á²á£áᣠááá á¥á¬ ááá½ á²á³áá¢","concepts":["á¨áááµ ááááµ á¥á«áá á áá áµá á¥áá°áááµ áááá£áᦠááá ááᣠá¨API ááá ááá ááááµ á áá£á¢","á¥á«áá á¥ááµá áá°áá á©á áµ á á«á£á¢ ááá³áᤠá®áá¶á áá®áµá á ááááá¢","ááá¹ á¥áá°áá¨á° áá³á«áᣠá¨áµá
á°áµ á®á¶á½áá á¨á áááááµ ááµá®á½á á¨áá®á¢","á®áá¶á áá¥á¶á½á á á«á°ááᦠáá¥áµ á¨ááá á¥á«á 403 áááá³áá¢"],"example":"á áá API á£á¶ áááá á¥áá°ááááµ áááá«áᢠá ááá GET /transactions á á¥ááᥠá£á¶ áµááµá áááá³áᦠááá á¨áá áµáá
áµ ááá¢","tips":["POST ááá DELETE á¨áááá á ááµ á áµá«á»áá á¥áá°áá á«áá¥á¡á¢","á¨áá á°á á½áá ááá£ááµ á¨á¥á±á ááá áá ááá¢","á£á¶ á¨GET ááá½ á¥á áá á¨áá¨á á ááááá á³ááá á¨áááá á¨á°á³á³á° áá°á á«áááá³áá¢"]},"cacheManagement":{"title":"á¨áá¸áá« á áµá°á³á°á","summary":"á¨ááµá¨á©á á¨áá¸áá« áá¤á¶á½ áá¨áµá áá½á³áµ â á áá ááá á á°áá°á áááᢠáá¸áá«á á áµááµá á¨á°á°á ááá¾á½á ááááᤠáá½á³áµ á ááá¥áá á¥áª á¥áá°áá á¥áá²á°á á«áµááµá³áá¢","whenToUse"
1:"ááá© á°ááá® á³á á áááá¹ á«á¨á áá¨á á²á«á³áá¢","concepts":["áá½á³áµ áá¨áá á á«áµá°á«áááᣠá¥áá°áá á¥áá²áá ᥠá«áµááµá³áᦠááá© áµá
á°áµ á¨áá á«á áááá³áá¢","áááá áá½á³áµ áááµ á¥á«áá³áá± áá£á á¥áª á¥áá°áá áá°áá â á¨áá³á á¨á«á á«áá¢","ááá á¨áá½ áµá á³ááá á¨ááµá¥ ááá« ááᦠáááá©á áááá¨á±á¢","áµááá± á¨áááááµ ááᤠá á°áá á«á áá á¥áá áá£áµ á áá°ááá¢"],"example":"á¨á°áá¨á¨ á¨áááᬠá°áá á áááá¹ áá á«á¨á áá ááá«áᢠá¨á°ááá¹á áá¤áµ á¥á» á«á¸á³áá¢","tips":["á ááá á¨áá½á³áµ áááá©á¢","á¥á´á± á¥áá°áá á«á¨á á½áá© áá¸áá«á á áá°ááᦠááá©á áááá¨á±á¢","á áááµ á á«á£á¢ áááá ááá¨á¡á¤ áá½á³á± áá²á«áá á²á ááá
á¥ááá± á«á ááá ááá«á áá¨áá» áá á«áá¢"]},"depositPool":{"title":"á¨á°ááá ááá³","summary":"ááµá¨á© áá°áá°á ááá«áá½ ááá¢áá½ á¨áá°á£á¸á á¨á¥ááá¼áá á áµá«á»áá½ ááá½áµá¢ á áµá«á»áá¹ á¨á ááµ HD ááá áááá«áᣠáµááá
á áµááµá áááááµ áá»ááᢠá¥á«áá³áá± ááááµ á«áááᦠáá» â áááá« á¨á°á°á â á¨á°á áá â á¨á¥á« á¨áá£á¢","whenToUse":"á¨ááªáᶠááá á á á áµá«á» á¥á¥á¨áµ á²á¨á½áᣠááá á á²áµ á áá³á+á á«á£á¢ á¥áá¨áµ á¨áááá© á ááµá¢","concepts":["ááá³ ááµáá¢á« á áá°ááᦠáá»á£ á¨á°á°á ᣠá¨á°á ááᣠá¨áá£á£ á á°áá¢ááµ á¨ááááá¢","ááá³á áá±á ááᦠáá» á áµá«á» á«ááᨠááá á á áááááᣠááááá¢","á áµá«á»áá½ á áá¢áá½ áá«á¨á á áá°ááá â á¨á ááµ áá á áµá«á»áá½ áµááá áá
ááá¢","ááá³ áááá á á«áµááááᦠá áá¥á³ ááá á áááá¡ áá²á«á áá° áªáµ á¦áá³ ááá³áá¢","á áµá«á» ááá á á áá
áá½ áá á¥áá á á ááá á áá°ááá¢"],"example":"á ááªáᶠáááá á áá¨ááµáᦠáá» á áµá«á» áá®á£ ááá «á¨á°á áá»ᢠá á²áµ áµá¥áµá¥ ááá¥á«áᣠááá á áááá³áá¢","tips":["á¨áá» á áµá«á»áá½á áá¥á á¥áá° á°á áá áá áá¨á³á°áá¢","á¨ááá© áááá®á½ áá°áá± á áá½áá áµ áá á áµá«á»á á¨á¥á« á á«áá¡á¢","á¨áááá á áµá«á» á¥áá
á³ááá á á°áá¢ááµ áá¨á ááµá¥ ááµá°ááá³áᤠááá³á ááá³áá á¥á» á«á³á«áá¢"]},"complianceFrozen":{"title":"á¨áááá ááááá½","summary":"á áµááµ áá°á» á¨áá ááááá½ áá¨áᣠá¨á°á áá³á á¥áµáªáá£á¢ á áá°á¨áá¨áá á áá°á¨ááááᦠáááá¡ áá á¥ááᢠá¥á«áá³áá± áááᥠá¨ááµá¨á» á áµá«á»á£ áá áᣠá¨áµááµ áá¥á¥á á¨áááá« áááá«áµ á«á³á«áá¢","whenToUse":"á á¨áá â áá
á¨á¥á« áá¨á áá á¥áá áááᥠá áá°ááᦠáááá¡ á¥áµá«á áµá¨áµ á¨á ááµ á°á áááᥠá áááá³ááµáá¢","concepts":["ááááá áááµ á áá°ááᦠá¥áµá¨ áá³á á«á ááá ááá¢","á¨áµááµ áá¥á¥ áá° áá³á á¨ááᣠá¥áá áá³áá á áá°ááá¢","áááá«á± á¨á á«áá áá áá°áááᤠá°áá³á³á áááá«áµ á á°ááá á¨áᣠá¥áá± á áá ááá¢","áá³áá á¨áááááµ ááᦠá¨á°á¨áá¨á ááá á áááá¥áá¢","áá¥á¶á½ á¨á°áá«á© áá¸áᦠá¨AML áááá«áá½á á¨ááµá°á³á°á áá¥áµ á«áá á°áá á áá¨ááá á«á«áᣠá¨áá«á¸áµáá ááá á¨áá¨áááá áá á¨ááµá¨á© á áµá°á³á³áª á¥á» ááᢠáá¨ááá áá¨áµ á¨ááá°á áá¥áµ á áá°á¥áá¢"],"example":"á áá¨áá 78 áá¥á¥ á«ááá «á áµá«á» á áááᥠáááá» áááá«áµ á«áá ááá£áµ á áᢠá áµá«á»á á á
áµá á
á¥á« á¥á» á°áá³á°áᦠá¨áá°áµ áááá« ááᣠá«á¸áµáá³áá¢","tips":["áá¨ááá á ááµá áá«á á¥áá á áá á á áá°ááá¢","áá¨áá á¨áá«á¸á±áµ á áá á¨á¨áᨠáá°á¦á¹ á á£á á¥á¥á
áá¸áá¢","á¨ááááá á ááµ á¨á áá©á á³áªá áááá¨á±á¤ á á°ááá° á°áá á áá á ááµ áá¥áá« á¥á áá á¨á°áᥠáµá
á°áµ á¥áá áá áá³á¥ á áá°ááá¢"]},"blockchainTransactions":{"title":"á¨á¥ááá¼áá áá¥áá¶á½","summary":"ááµá¨á© á á áá³á®á¹ ááµá¥ á¨áá«á«á¸á áááá®á½á¦ áá° á áµá«á»áá»á½á á¨ááá¡á á¨á¥áá± á¨ááá¡á¢ áá
á¨á«á¢á ááá«áá½ áááá á³ááá á á°áá°áá± á¨áááá á
á½á á³á ááµá ááá¢","whenToUse"
1:"áááᥠ«áá¥á¶ á³áá°ááµÂ» á²ááᣠááá á¨áá¡ ááá«áá½á á á¥áááµ á¨áá£á áá á²á«áá³áá©á¢","concepts":["á¥áá
á«áá áááᥠá¨á áá³á ááµá°áµ áá á¥áá ááá« á áá°ááá¢","á¨á¥áá áá¥á áµá áá¨ááá« áááá«á á¥áá áµá áá¨á¨á»ááµ á áá°ááá¢","á á«á£á¢ áá¥á³ á áá³á©á á¨áá¨á«á ááá«áá¢","áá½ á¥á¸áá á áµá°ááá á¨ááá ááá ááá¢"],"example":"áá¢á áá¹á ááá«áᦠáááá© á°áá·áᣠáá á á áá³á ááá« á°ááá¶á¢ ááá«á á á«á± á áá°áááá¢","tips":["á¨áá á á³ááá á¨áá½ áááá©á¢","á áá·á á¨áááµ á ááµ á á«á£á¢áá áááá¨á±á¢","áááá© á á°áá°áá± áá áá ááá«á á«áá°ááᣠáááá«á± áá áᣠá áµá«á»á ááá á¨áá¨ááá«áá½ á¥ááµ áá â áªá³á« á áá°ááá¢"]},"blockchainHealth":{"title":"á¨á¥ááá¼áá áá¶á½ á¤á","summary":"ááµá¨á© á¨á áá³á®á½ áá á¨áááááá£á¸á áá¶á½ ááá³á¦ áá á«á ááᣠá°áá³áµáá ááᣠáµááµ áá¨á¤áµ á ááᢠá¨áᢠáááá áá³á¨áµá á¨á᪠ááá á áá
ááá°ááá¢","whenToUse":"á¨ááªáᶠááááá½ á¥ááá³ á²ááᦠáááá®á½ áááá°á á²á³á©á£ ááá«áá½ á³ááá¡ á²áá©á¢","concepts":["«áá á«á» áááµ á°áá³áµáá á¥á áá¨á¤á¶á½ á ááµá¢","«á°á°áááá» á¥á «ááµá» áá
á áá¸á á¥áá á¥áá½áµ á áá°ááá¢","ááá³á°á á¨á°ááááµ áá áá£áᦠáá°áá á¨áᨠááµ á«á á ááµ áµá
á°áµ á á®á áá¨á áá°á£áá¢","á¨áá¨á¤á¶á½ áá¥á áááááµá ááá«áá¢"],"example":"á¨Ethereum á°ááá ááááᥠá«áááᦠáá± áááá³á áá á¨á³áá ááµááá á áá á¥á¨á°áá³á°á ááᢠáá á á
á¥áá áááá á áá°ááá¢","tips":["áµáá á áááá á¥á«á á¨áá
á¨á¥á á ááµ á¥áá
áááá¨á±á¢","á¥á«áá³áá± á áá³á á á«á± ááá«áá¢","á áá³á¨ áá¨á¦á¹ á á°áá á áá á«áᤠá áá± á¢ááµá
ááá¹á á ááá«áá¢"]},"cryptoBalances":{"title":"á¨ááªáᶠáá³á¦á½","summary":"á¨áµáá
á± á¨ááªáᶠá áµá«á»áá½ á᪠áá³á¥ á á áá³áá á á á«á£á¢á¢ áá á á á°ááá á áá á£á á
áá á°á¨áááᦠá¨á°ááá á á áá³á© á°á¨ááá§áᣠá áá á£á á
áá á«áá áá áá¨ááá« á¥á¨á°á á°á ááá¢","whenToUse":"á¨ááá« á ááµ á áµá«á»á á á áááá ááá¨ááá¥á¢ á¥á «áááá¡ á¨áá³á¨á á áá áá» á²á£áá¢","concepts":["á áá á£á á
áá á«áá á¨á áá³á ááá³ áá á¥áá á¨á áááá½ áááá¨áµ á áá°ááá¢","á áá á£á á
áá á«á ááªáá½ á¨á°áááá áá²á«á áááá³áá¢","áá³á¥ á¨á áá³á+á á«á£á¢ á¥áá¨áµ áá á¨á°á³á°á¨ ááá¢","á¨áá¨á¨á» á¥á«á á°ááµ á¨áá¥á©á á á²áµááµ áááá«áá¢"],"example":"á¨2 ETH ááá« á áá³á«á á áµá«á»á 2.3 á¢á«á³ááᦠá¨á°ááá 1.4 á¥á» ááᣠááªá áá¨ááá« áá á¥ááá¢","tips":["á²á«á
á± á á°ááá áááá¨á± á¥áá á á á
ááá á áá°ááá¢","á¨áá¨á¨á» á¥á«á á°ááµ á«á¨á ááááªá« á¨áá¶á½á á¤á áááá¨á±á¢","á ááá³ á áµá«á» áá áá® á᪠áá³á¥ á¨á°ááá° ááᤠááá«áá á¥á¨á á á ááá¢"]},"smartContracts":{"title":"á¥áᥠááá½","summary":"The ZolT token contract on-chain: its address, its state (running or paused), the vaults and the issuance and redemption requests. The cabinet does not hold wallet keys: a holder transfers tokens from their own wallet, here the contract state is only read, and operator actions go to the network on behalf of the operator organization.","whenToUse"
1:"When you need to see whether the contract is deployed and whether it is paused, check an address balance or its blacklist status, or find a vault or a request. The tabs with actions â minting, pause, blacklist, reserve audit, contract roles, timelocked changes â are open to the ZolT operator only.","concepts":["No private key is entered here. The transfer and approve forms have been removed from the page: the backend performs those only with a wallet key in the request body, and the cabinet does not dispose of other people's keys â a holder transfers tokens from their own wallet.","«ááá» á¨áá ááá³ áá á¥áá á¨ááµá¨á© á áá°ááᦠááá áááá á á«áááá¢","The tabs split in two. Contract state, vaults and requests are visible to everyone who has the ZolT section open; minting, pause, blacklist, reserve audit, contract roles and timelocked changes belong to the operator only: a client of the operator organization (type zolt_admin) holding the manage_zolt permission. Others are not shown those tabs â the backend would answer them with not_zolt_operator.","á¨áá á áµá«á» á¨á áá³á© áá á¨á°á³á°á¨ ááá¢"],"example":"ááµá¨á© á¨ZolT ááááá½á á ááᦠáá «ááá» á°á¥á á á¥á
á°ááá§áá¢","tips":["An address balance and its blacklist status are reads from the network: no key is needed for them, and any address can be checked, not only your own.","An operator action goes to the blockchain and has no way back: pause, blacklisting an address and destroying blacklisted funds are undone only by a new operation, and destroyed tokens do not come back.","áá «á áá°á°áá«á» á«á áá¹ á áá°á áá¸á â á áá« á áá³á¨ áá¨á¥ áá á ááá á¨ááá¢"]},"hethWallet":{"title":"á¨Heth áªáµ á¦áá³áá½","summary":"á áµáá
áµ á¨Heth áªáµ á¦áá³áá½ áá ááá«á¦ áªáµ á¦áá³áá½á£ á¨á°á ááá áá³á¦á½á£ á¨áµáááµ áááá¥á á¨á°á áá áµáá½á¢ á áµá°á³á°á«á á¥áá³ á¥áá á¨ááá á¦á³ á áá°ááá¢","whenToUse":"áµáá
á± áá á¥áá³ááá á áá ááá³ á¥áá°áá ááá¨á³áµá¢","concepts":["á¥áá
á«ááµ áá³á¦á½ á¨á°á ááá áá¸áᦠá¨áªáµ á¦áá³áá½ áµáá á¥áá á¨á ááµ á áµá«á» á᪠á áá°ááá¢","áááá¡ ááá£á¥ á¥á» ááᦠáá á¥áá³á°á¨áá áááá«á á¥áá á¥áá´áµ á¥áá°ááááµ á áá°ááá¢","á¨á°á áá áµáá½ á°ááá áµáá½ áá¸áᦠá ááµ á°á áá á¥á áªáµ á¦áá³ ááá¨á áá½ááá¢","á á°áá á áááµ á£á¶ áááá áªáµ á¦áá³ á¨áá áááµ áá á¥áá áá³á¨á» á¨áá áááµ á áá°ááá¢"],"example":"á á°á áá áµá á¨á°á°á¨á áááá áá°á°á³á³á° á¦á³ ááá³áᦠáááá¡ áµá á á¥á«ááá á á áá»á¸á áá«á¨á á¥áá°á°áá¨á¨ á«á³á«áá¢","tips":["á¨á°á áááá á¨á ááµ á áµá«á» áá á á«áá³áµá©á¢","áááá¡ ááá³á á¥áá´áµ á¥áá°á°áá ᨠá«á¥á«á«áá¢","á á°áá³á³á áááᬠááá°á á¦áá³ á¨ááá áá á ááµ á¨ááááªá«á á£á¶ áá á¥áá³á á«á¨ááá¡á¢"]},"routingAnalytics":{"title":"á¨ááá« áá°áááá« áµáá°á","summary":"á á°áá¨á á áá ááµá¥ áá¥á«áá³áá± ááµáá áá ááá«á¦ áµááµ ááá« áá° á¨áµáá ááµáá á¥áá°áá°á£ áá á«á
á á¥áá°á°á³á«á£ á á
á«á¢áá á áá á«á
á áá á¥áá°ááá°á¢ «á¨áµáá ááµáá áá»áá» áááá áááá³á á¥áá «á áá
ááá« áá áá á°á¨á°Â» áááá á áá°ááá¢","whenToUse":"ááá á°á¨á᪠áá á á¥áá°áá°á¥ áµáµááµáᣠá¨á á
á«á¢ áá á¨áá áááá áµá³ááá
ᣠááá á¨á á ááá á¨ááᣠá
áá½ áááá«áµ áµáµáááá¢","concepts":["á¨áµá¬áµ áá á áá¨á«áá½á ááá¥á«á á¥áá áááá¥á á áá°ááᢠáááµ ááµ á¥áá¢á³áá½á áᶠáµááá½ áµá¬á¶á½ á«ááµ ááµáá á¥á© áááµááᣠáªá³á«á áá á¥áááµ ááá¢","áµááá½ áá¥á®á½ á«á³áááᦠá á áµá ááá« ááµá¥ á ááµ á¥áá¢á³ áá áá á á¥á áá¥á¥ á«ááá³á
á°ááᢠááµáá®á½ á¨ááá»á¸á©áµ á á°áá³á³á áá á á¥á» ááá¢","á áá«á á¨ááá½ áá á á
á«á¢áá áááá»á á¥áá áá¢áá á áá°ááᦠá á£áá© á¨3-D Secure áá½ áá á¨á°á£á¨áá áá á¥áá
á áá«á°áµáá¢","á¨á á
á«á¢áá á¨áµá áá«á á¨á°ááµ ááááá áá¨áá³áᢠá¥áá« á¥áá¢á³áá¹ á ááá áá á°á á³áµáá áááµ á á ááµ á°ááµ á°á¨áá½á°á á¥áá°áá áá³á«á â ááá°áá á¥áá½áµ á¥áá á¨ááµáá á¥á«áµ á áá°ááá¢"],"example":"ááᣠá á³áááµ á ááµáµ áá¥á¥ áá¨á°á¢ á á áá á¨á¡ ááµá¥ á«áá áá á á áá°ááá áᣠááá áá á ááµ á á
á«á¢ á¨á°ááá°á 94 ááá
62 á áᶠá«á³á«áᢠá¨áµáá á«áᦠááá á¥áá¢á³áá½ á¨á¡á á¨14 á¥áµá¨ 17 á°ááµ áá¸áᢠáµááá
á¨áá¢áá½ á£á
᪠á³ááá á¨ááµáá á¥áá½áµ ááᣠá¨á á
á«á¢á áá á¨áá°á¨áá ááááá áµááá« ááá°áµ á¥á» ááá¢","tips":["ááá á áááµ áááµ ááá°ááᣠá áá£áªá á ááµ á³áááµ ááᤠá¨á á
á«á¢ áá áµáµáááá á°áá³á³á ááá°á¶á½á á°á ááá¢","á á°ááµ áá á³ áá á«áá ááµááµ á¥ááá áá á¨ááµáá á¥áá½áµ áá ááá£á áá â á¨áá«á áá á¨ááµáá®á½ á¤á á á¨ááá¥á¢","áµáá°á á¨áááᥠáªáááµá á áá°á«áᦠáá áá¹ á áá¥áá¶á½á á ááµá³á¨á
ááµá¥ ááá á£áá¢"]},"webhookMonitor":{"title":"á¨áá¥áá ááµá¨áµ","summary":"ááµá¨á© áá° á áá®á½ á¥áááµ á¨ááá«á¸á áá³ááá«áá½ áááá¥á¦ á¨áµáá ááµá°áµá£ áá° á¨áµáá á áµá«á»á£ áµááµ áá¨á« á°á°á¨áᣠá°áá£á©á áá ááá°á¢ á¥áá°áá áááá á¨áá áá°á¨ááá¢","whenToUse"
1:"ááá´á ááá«á á ááá á²á á¥ááá± áá á«ááá ááᦠáµááá á áá°áááᣠááá á áá°áá¨áá¢","concepts":["á¨ááµá¨áµ ááá³ á¨ááá« ááá³ á áá°ááᢠáááá¡ á ááᣠá áá áá³ááá«á ááá°ááµ áá½ááᤠáá
ááá«áá á«á±á á ááá«ááá¢","áá¨á«áá¹ á áá á¥á¨á«á«á ááá³áᢠ«á áá á£á á
áá» á¨áá£á áá¨á« á°ááµ áá áááµ á¥ááá± á á«á± áá°áááᣠá£áá ááá£áµá á á«áµáááá áááµ ááá¢","«á áá°á¨á°á» áááµ áá¨á«áá¹ á ááááᦠááµá¨á© á¨áá« á áá á áá°áááᣠá á¥á
á¥áá°áá ááá á«áµááááá¢","á¨ááá½ á®áµ á¨áá ááá á¥ááµ á¥áá°áá á«á³á«áᦠ5xx á¥á áá ááá
á¨ááá´á á°áá£á áá¸áᣠ4xx á¥ááá áá á áµá«á» ááá ááá ááᣠ200 á¨á
á¬á³ áá á²áá áá áá³ááá«á á°áᶠá áá°á°á«á áµá áááµ ááá¢"],"example":"á ááµ ááá´ á¨á ááµ ááá® áµáááá½ á¥áá°áááá á«ááá«áᢠá ááµáµá ááµá¥ á᫠«á áá°á¨á°á» á¨áµáá½ á áᣠááá á¨áá¨á¨á» ááá»á¸á 502 áá â áµááá
á¨áá°áá á¨á¥á± á°áá£á á¥áá ááµá¨á© á áá°ááᢠá¥á± á«áµá°á«á¨á á áá á áá° á¥áá°áá áµáá«áá
ᣠááá³áá¹á «á°áá·á» ááááá¢","tips":["á¨áµáá áááµá¦ á¨ááá¹ á á«áá á¨áµá
á°á± á½áá á¥áá« á áᣠáá
á á¥ááá áá á¨ááááµ á«áµááá¢","á¥áá°áá ááá á«áá ááµá°áµ ááá«á á¥áá á á²áµ á ááá¥ááᤠá¨ááá´á á°áá£á áµáááá½á á áµááá á¥áµá¨á«á áµá¨áµ á
á
á ááááá¢","á¨Â«á áá á£á á
áá» áá¨áá¸áµ á ááµá ááá´ á³ááá áááá á°áá áááá°á½ áááá«áµ ááá¢"]},"twoFactorAuth":{"title":"á¨áááµ á°á¨á áá¨ááá«","summary":"áá«áµá
ááá¢á« á¨á ááµ áá á®á¶á½á áá¥á«áµá áá¥ááµá¢ ááµá¥á© á ááµ áá á¥á» áá³á«á â á QR á®áµá á á½áá â á¨áá« á áá á¨áá¨ááá« áá°áá áªá«á á á¨á áá³ á°á¨áá± á¨áµáµáµáµ á áá á®áµ á«ááá«áá¢","whenToUse":"á ááááªá« áµá³á á«áᣠáá° á á²áµ áµáá áµáµá¸áááᣠá¥á áµá³á ááá¢","concepts":["áá
á¨á«áµá
á ááá« áá á¥áá á¥áá áµáá
á±á á áá°ááᦠá¨áá
áááá½ á á£ááµ áá¥á«áµ á áá»ááᣠá¥á«áá³áá± áá«á± á«á°ááááá¢","ááµá¥á© á¨áá³á¨á á ááááªá« á°á¨á á¥á» ááᢠá«ááµááá¥á¨áá áµáá© á¨á á á¨ááááµá áµ ááá á ááááá¢","á®á± á¨áá áá á¨á°á³á°á¨ áá á¥áá á¨á áá³á¨ áá¨á¥ áá á áá°ááᢠáá°áá áªá«á á«á á¢áá°áááµ áá á«áᣠá¨áµáá© á°ááµ á¨á°áᣠáá á®á¶á¹ á ááá ááá¢","áá¥ááµ á¨ááá áááá áá
á³á á®áµáá áá ááá â á«ááá ááá°áá á°á¨á áá á ááá¨ááá¢"],"example":"áµáá á¥á¨áá¨áá ááᢠá á®áá á á¥á
á
á¥á«áᦠá ááá ááá á á á®áá áµáá á®áµ á¥á ááá á á¥áᣠá¥áá°áá á á¥á«á á á²á±á QR á®áµ á á á²á± áµáá áá á áá¥á¥á¢ á á®áá áµáá á áµááµá á¨á á á¨á°ááá°á ááááµ á áá á«á â á¨ááµá¨á á áµá°á³á³áª á¥áá³á³ á«áµááááá¢","tips":["á¨ááµá¥á©á á½áá á ááá áá á áµá°á³á³áª ááµá¥ á áµááᥠâ áµáá© á¢á á á¥á¸áá ááµáµá ááá¢","á¨áµáá©á á°ááµ á á«áµ-á°á áá áá á ááᦠá¨á ááµ á°áá áá©ááµ á¥áá³ á®á¶á¹á á«á áá»áá¢","á¨á®áµ áá¨ááá«á á¥áµáªá³á« áá¹á á áµááá
ᦠá¥áµá¨áá« áµá¨áµ á¥á áá á áá á«áá¢"]},"referrals":{"title":"á¨áá¥á£ á áááá½","summary":"áµáá
áµ á á᪠áá³á¡ áá á¨ááá» ááá» á¨áá«ááá£á¸á á®á¶á½á¢ á¥áá
á®áµ ááá á«áᣠá¨ááá» áá áá á¨áá¥áá« áá áá°á ááᣠáµááµ áá á¥áá°á°á ááá áµá áá³á«áá¢","whenToUse"
1:"á°áá áá½á ááá³á¥ ááá» áµáµááá ááá áá°áá°á áµááááµ á®áµ áµá³ááá
á¢","concepts":["áµá-áá á¥ááµ ááᦠáá áá á¨á°ááá á áµ áááá¬á¢ á°áá áá á áá áááᬠáá¨ááá áá½áá â ááµá¨á© áµá-áááá á á ááá³áá¹ á°áá áááá¨ááᣠáµááá
áá° á᪠áá³á¥ á¨ááá£á áááá á¥áá
á«áµáá¡áµ áá¥á á áá°ááá¢","áá á á¨ááá£á á áµá-ááá áááᬠá ááµá°á á áá¶á½ ááᦠ50000 áááµ 500.00 USD ááᣠáá 50000 JPY (á¨á á ááµá°á á ááµ á¨ááá) á¥á 50.000 KWD (á²áá áºá
á áá¶á½ á ááµ)á¢","á ááµ á®áµ áµááµ ááá áá á« áá½ááᣠááá áá á ááµ áµáá
áµ á¨áµáááá á®áµ á¢á áá á¨áªáá«á ááá» á¨áá«ááá á ááµ áá á¥á» ááᢠá®á±á á¨áááµá¡áµ á¨áá¥áá« ááá á¨Â«áá¢á» áááá± á¥á» áá¸áá¢","áá¥ááµ áá¥ááµ á áá°ááᤠá¨á°áá á®áµ áá¥á«áµ á«ááá áá á¨áµá³á²áµá²á© áá á áááá© ááµá¥ ááá«áᢠááá á«áááá á¨á°ááá á á°áá«á¨ ááá© áá³á«áᣠáá¤á³á¸á áá á ááµ ááᦠááá±á áá áá á áá»ááá¢","á®á± á áá´ á¨á°á áá á áá áµá-ááá â áá áá áááá¬áá â áááá
ááᦠááá¨á© á áµááµá á¨á°á°á¡ ááá»áá½á á¥áá°áá á«áµá°áááᢠáá áá á ááá
á¨á¥ á á²áµ á ááá ááá á©á¢"],"example":"áá£á¤ á¥á«áááá
ááᦠááá»á á¥áµá¨ áá áá¨á¨á» áá¥áá« á«áá á®áµ áá¥á¨á
á áááá á³á°á«á«áá
ᢠá¨á³áááµ á áá á á¥á« áááµ á á ááá áá³á«á â á á¥á« áááµ áµáá
á¶á½ á á᪠áá³á£á¸á áááᥠá ááá°ááᢠá¨ááá»á á áá á áá á°á áá
á¨á¢á« ááµá¥ á«áá á ááá ááááá á¥áá³áá á« á®á±á á³á ááá
á¢","tips":["á¨á°á°á áá á á
áá áá á á¥á á¥áá á¨á á ááá á¥ááµá á¥á» á áá°ááᦠá á᪠áá³á¦á½ áá á¥ááá°á áááᥠá¨áááá á¥á± ááá¢","á¨áá¥áá« áá á ááá áá áµ áá áá´á³ áá â á áá á áµáááᣠá áááá½ á¨ááá»áá½ á áá ááá«áá¢","áááá«áá á áá° á¥á» á³á«áá
ᦠá®á± á¨á¨áµáá ááá» á¥áá°áá á»áᣠá áá ááá« á¨ááá½ áááµ á áá ááá á á«áµá³áá°ááá¢"]},"applyReferral":{"title":"á¨áá¥á£ ááá»","summary":"á ááá
áµ áá ááá á¨á¥á« á áµáªá«á
á¨á°áá á®áµ ááµáá£áµá ááá»áá áá° áµáá
á± á᪠áá³á¥ ááµáá£áµá¢ ááááªá« á®á± áá¨ááá£á â áá áá ááá áá³á«á â á¨áá« á¥á» áá°áá á«áá¢","whenToUse":"á ááµ áá á¥á»á£ á®á± á á¥á
á
á²ááᢠáá¨ááá¡ ááá á áááá¥áᦠá®á± áá á¥áá°áá°á¥ á«á áá´á³ áá¨áµ áá»ááá¢","concepts":["áá¨ááá¥á áá áá áááµ á¨á°áá«á© á°á¨ááá½ áá¸áᦠá¨áá ááá«á ááá á¥áµáªá«á áµá¨áµ ááá á ááá£áá¢","ááá»áá á¨áá³ááá áµáá
á± á¥áá á°á ááá á áá°ááᢠá¥á áµáá
á¶á½ á«áááµ áááá¡ áá° á¨áµáá á᪠áá³á¥ á¥áá°ááᣠááá¨á¡á¢","áµá-áá á¥ááµ ááᦠáá áá áááá¬áᢠá¨ááá¢á« áááᬠáá¥á»á ááá¨á£áᦠá¨áµá-ááá áááᬠá¨á°áᨠá¨áá ááµá¨á© á®á±á á£áá£á á ááá³áá½ á°áá áááá¨ááᣠáµááá
á¨áá£á áá á á¨áµá-ááá áá á ááá³á°ááá¢","ááá áá á¨á°áá á ááá ááá á á°áá¨á á áµáá
áµ ááµá¥ á á£áááµ á«áµááááᦠá®á±á ááá á°á áµáá
áµ áá áá á áá»ááᣠá ááµ áµáá
áµá á¨áµáááá á®áµ á¢á áá á¨áªáá«á ááá» á¨áá«ááá á ááµ áá á¥á» ááá¢","á¨áá°á áá á á ááá áá â á®á± áá° áááá áá°á á á«á± ááá¨á«á â á°á¨á᪠ááá°á¶á½á á°áá³á³á áááá¶á½ áá ááá á«áá¢"],"example":"á áµá¥á°á£ áá á®áµ á°á¡ááµá¢ á«áµáá¡áµá£ áá¨ááᥠáá«á â «áµááááᣠáµá-áá 500 USDᣠá¥áµá¨ áá© áá¨á¨á»Â»á¢ áµáá
á±áá á¨ááá¢á« áááá¬áá ááá¨á¡á¢ USD á«áµáá© á¥ááá«á 500 áá° á᪠áá³á¥ ááá£áᤠEUR á¨áá¨á¡ áµá-ááá á á ááá³áá¹ á°áá ááá¨á«áᣠá¨áá£áá áá á ááá«á«áᢠá¨á°á áá á áá á áµááá á¨áá£á áá á á¨á¨áµáá áµá-áá á¥áá°áᣠá á¥á® áá³á«áá¢","tips":["«á®áµ á áá°ááá» á¨áá áá¥ááµ ááá
á¨áá°á áµá
á°áµ ááᦠá ááá á¨ááá³á± ááááá½á á á¨ááᥠâ áá®á áá°á Oᣠá ááµá Iá¢","á¥á áµáá
á¶á½ á«á á¨áá°áá áá
á ááµ ááá«áá á á¨ááá¥á¦ á¨áᣠá áá áá
1ááµ á¨ááá¢","ááá» á á᪠áá³á¥ áá á«á áááᥠáá á¥áá á
áá½ á áá°ááᦠá á°ááá°á ááááµ ááá£áá¢"]},"wizardsHub":{"title":"á¨ááááªá« á áááá½","summary":"á°á¨á á á°á¨á á¨ááá± ááá³áá½ á«á³ááᦠá¨ááá« ááá áá áááááµá£ ááªáá¶á ááµáááᣠá ááá ááµáá£áµá á á°ááá á¨ááá á© ááá½á¢ á ááá á á°á¨ááá½ ááá«ááᣠá áá¨á¨á»á á¨áá«áµááááµá á á«ááµ á«á± ááá¥á«áá¢","whenToUse":"á¥á«á á¨á ááµ áá á²ááá á¨á°á¨ááá¹ á
á°á á°á¨á°á á á á¥áá® á¨áááá á²áá â á¥áá²áá áááá©á á á²áµ á á«á°á á²á á«áá¢","concepts":["á áááá¹ á¥áá° áááá á°á¨áááááᦠá«áá± áá¤á± á¨áááá¨á°á ááá á¡áµá ááµá¥ ááááá¢","á¨ááá áá£áªá«á á¨áá ááá ááá£á â á á ááµ á¡áµá ááµá¥ á«áá «á¨ááááªá« á áááá½Â» á¨áµá áá
á áá½ á áµááµá á°á£áᶠáá¨áá³áá¢","á¨á°ááá á«ááµ á¨áááµ á¥á¦áµ á³ááá á«áá°ááá ááá ááá á«áá°á ááá á¨áµáá
áµ ááá³ ááᤠáá áá¥á«áµ á¥áá°áá»á á¥áá²á³á áá³á«áᢠáááµá
á¨áááá
á°á áá áá á áá á°á°á¥ááá¢","áááá á á«áá± áááµá á áá áááá« ááµá¥ ááá³á á¥áá á ááµá£á áµáá½ á áá°ááᦠá á¥á«á áááµ áááá áá»ááá¢"],"example":"á á²áµ á á«á°á á á
á«á¢ á¥áá²á«ááá á°áá°á ᢠá°ááááá½áᣠá á
á«á¢áá½áá áá°áááá«á á¨ááá ááá
á áááá¹á áá¨áá³áᣠ«á¨ááá« ááá á» áááá á«á£á«áᣠááá³ááá áá á áá á«ááá â á¨áááá½ á¥áµá¨ á¨áá¨á« ááá«á¢","tips":["á£á¶ áááá á¥ááá áá á¨ááá áá£áªá« áá¥á«á±á á«á³á«á â á ááá á¨áá á¨áááµá
á ááµ á á¥ááá¢","á¨á°á ááá á áá ááá«áᦠáááá©á á¥áá°áá ááááá£áµ á³áá áá¨áá³áá¢","á ááá á¨á°ááá± áá¾á½á á áá°á«á â á¨áá á¨á ááá á áá á á¥á
ááµá°á«á¨ááá¢"]},"binData":{"title":"á¨BIN ááá«","summary":"á á«ááµ á¨ááááªá« á ááá½ ááááᦠá¨áµáá á¨ááá« á áá³áᣠá¨áµáá á á᪠á£ááᣠá ááᣠá°á¨áá á¨á«ááµ ááááµá¢ áá
ááááá« á¨áá«áááá áá£áá» áá á¥áá á
áá¥á á áá°áá â áá¨áá á¥áá
á¨ááá ᥠá¥á» ááá¢","whenToUse":"á ááá«á ááµá¥ á¨áá á«ááµ á¥áá°á°á³á°á ááá
á²á«áµáááᦠá¨á°áá á áá ááááᣠáá¥á«áªá« á¨áá«áµáááá á¥áá¢á³á£ á¨á«áá± á áá á¨áá¢á á«á³ááá á áá áá ááá³á¨áá¢","concepts":["BIN á¨á«ááµ áá¥á á¨ááááªá«áá¹ áµáµáµáµ á¥áµá¨ áµáááµ á ááá½ áá¸áᢠá£áá©áá ááá±á ááá«á á¥áá á°áá¬áá á áá°ááᦠá BIN á¨á«áá±á á£áá¤áµ ááá
á áá»ááá¢","á¨á«ááµ á°á¨á â áá°á áᣠááá
ᣠá¨áµáá
áµ â á¨á¨ááá á¥áá¢á³á á¨ááá« áá©ááµ á«á¥á«á«áᦠá á¨áá°áá á áµáá
áµ ááá¶á½ áá á¨á ááªá áá á á á
á«á ááá¢","á¨á«áá± á áá á¨á ááªá á áá áá á¥áá á¨á£áá¤á± áááªá« á áá°ááᢠá¨áá¢á á áá áá á áááá³á°á á á«á± á¨ááá áá á ááááµ á áá°ááá¢","ááá«á á¨áá¨á á
á½á á³á ááµá áá á¥áá áá° á«ááµ á áá³á á¨ááá áá¥á³ á¥á«á á áá°ááᦠá á²áµ á¨á°á°á ááá á¥áá
áá áááᶠáá³á«áá¢"],"example":"á ááµ á
á¬á³ á¥á¨á°áá¨áᨠááᦠááá«á á°á¨ááááᣠáá¢á áá á«áá± á¥áá°áá á« á«á¨ááá£áᢠBIN á¨áá á£áá á¨áµáá
áµ á«ááµ áááá á«á³á«áᢠá¨áá« á áá á¥á«áá áááµá¨á© á³ááá á áµáá
áµ á«ááµ áµááá°á¨á á¨ááµáá áá ááá« áá ááªá ááá² ááá¢","tips":["áááá áµáµáµáµ á áá á á ááᤠáá á¨á«ááµ áá¥á á á«áµááááᣠááµáá£áµá á ááá£áá¢","á á áá áááá áá á«á ááááá áá á
ááᦠá¨áµáá¹ á áá³á®á½á á ááªáá½ á¥áá°áá á áá³á«áá¢","á£á¶ áá¤áµ ááá á ááá«á ááµá¥ á áááá©á á«á³á«á á¥áá á«áá± á¨á°áá á¨á ᨠáááá á áá°ááá¢"]},"schedules":{"title":"á¨á
áá½ ááááá¥á","summary":"á¨ááá¡ á¨á°áá áááµ áááᣠá
áá¾á½ á°ááᦠáá¼ á¥áá°áááᣠá á¨áµáá áááá£á á áá á«á
á áá áᢠá¨á¥ááá±á ááá á«á³á«á á¥áá áá¤á±á á áá°áá â á¨á°áá¸á á
áá¾á½ á áá¥áá¶á½ ááµá¥ áááááá¢","whenToUse"
1:"á°áá áá áá¼ á¥áá°ááááµá áµ á²á áá
ᤠáááá£á á²áá ááá á
áá½ á¥áá°áááᣠáá¨ááᥠá²á«áµáááᤠá«ááá á ááá« á²áá¨áá©á¢","concepts":["á¨ááááá¥á áááᥠáá
áµ áá á¥áá á¨áááᥠá¥áá
áµáá´ á áá°ááᢠá áá á£á á
áá á¥áµá«á áµá¨áµ ááá á áá°ááá°áá¢","«á°áá½áá» áááµ ááá á°áᶠáá¨á« á°á°ááá áááµ ááᢠááá«á á«á± áá³á«á± á áá¥áá¶á½ ááµá¥ ááá á£áᦠáá¨á«á á á¥áá¢á³ áá ááá
áá½ááá¢","áá
áá½ á¨áá«á³á á¥á» ááᢠá¨á³áá°á á
áá½ á¨áá
ááá³áµ á áá»áá â áá
á¨áá°á¨áá á áááá£á á á«á± ááá¢","ááááá¥á© á¨áááá£á á á«á ááᦠáá á«ááá áááᣠá¨áá á£á á
áááᥠá«áá ááá á¨áá á á
ááá
áá£á«áµ ááá£áá¢"],"example":"á°áá áá áááá£áá á°áá á á²áµ á
áá½ ááá«áᢠááááá¥á©á á «á áá á£á á
áá» áá£áªá« áááµá¦ á¨á¥á± áááᥠá¥áá« á«á áµá¨áá á¥áµá¨áá¨á¨á»á á áá°á¨á°á â áµááá
áµá©á¨áµ á¨áá«áµáááá áááá£á á«á± áá á¥áá ááá áá á á
á áá°ááá¢","tips":["á¨ááá³ áá£áªá« á¨áá¹ áá áá£áªá« ááᦠ«á áá á£á á
áá» áá á¥áá°áááᣠ«á°áá½áá» á°áá áá á¥áá°á°á á« áááá³áá¢","áá á á áá° áááá á á áá° á¨á°ááµ ááá áá³á«á á¥áá á á°áá áá á áá°ááá¢","áá áá á¨áááá£á áá á áá³ááᦠáá©ááµ áááµ á
áá¹ á¨á³áá° á áá á³áªá á°ááá§á áááµ ááá¢"]},"telegramEntities":{"title":"á¨á´ááá«á á¦á¶á½á á»ááá½","summary":"á¨ááµá¨á© á¨á´ááá«á á°áá£á®á½ áááá¥á¦ áá³ááá«áá½ á¨ááá©á£á¸á á¦á¶á½á£ á»ááá½á á¡áµáá½á¢ á¥á«áá³áá± áááᥠááááµá£ á¨ááááµ ááá« á¥á â áá¦áµ â á¶áá á ááá¢","whenToUse":"á á²áµ á¨áá³ááá« á»áá á²á¨ááµá£ áá³ááá«áá½ áá° áá á¡áµá á²ááá©á£ ááá ááá¥áá¶á½ ááá ááá£áµ á¥áá³áá á²áá¨áá©á¢","concepts":["á¦á±á ááµá¨á»á áááµ á¨á°áá«á© ááá®á½ áá¸áᢠá¶áá á¨á¦á± ááᣠá¨ááááµ ááá«á á°áá á¦á± á¨áá½áá áµ á»áá ááá á¡áµá ááá¢","á¨ááááµ ááá« áá¥á áá á¥áá áµá á áá°ááᢠá á¡áµáá½ ááµá¥ á áá³á ááᤠá¨á ááá á¨á°áá³ áµá á ááµá© á áá á«áá¢","á¦á± áá° á»áá ááá á¡áµá áá¨ááá á¨áá»á áá¥áµ ááááµ á áá áµá¢ á¥áá
áµáááá áááᥠá á´ááá«á á á©á á«ááá áá¥áµ á áá°á«áá¢","á¶áá áá° á¦á± áá áá³á¨á» ááᦠá«áá á°á á á¦á± áµá áá½ááᢠá¶áá á á´ááá«á á¨á°áá¨á¨ áááá¡á á áááᣠá áá ááá« ááá© á á¸á¥á³ ááááá¢"],"example":"áµá áµááá
ááá«áá½ á¨ááá© áá³ááá«áá½ áá° á¨á¥á« á¡áµá ááµá¨áµ á ááᢠáááá¡ á á áá ááá¥áá¶á¹ á á«áááᦠá á£ááµá á áá½á³áµ áá
áµ á¦á± á¨á¡áµá á°ááá·áᢠá¦á± á°ááᶠá¨áá»á áá¥áµ áá°á áá â ááá© á áááá¡ áá ááᥠá³áá°á¨á ááá¥ááá¢","tips":["áááá«áá áá°á£áááµ ááá á°á ááᦠá¨ááá½ áááµ á áá «á¦áµ 2» ááá á¥áá°á°áá ᨠá á«á¥á«á«áá¢","áááá±á á á¥áááµ áá¨á¥ â á¡áµáá á
1±áá á¡áµá á ááá« ááá«á«áᣠá¨á°á³á³á° ááááµ á«áá áááá¥á áááááµ áá¨á¥á³áá¢","áááá¡á áá°á¨á á¦á±áá á»áááá á áá°áááᦠá¨áá áá á°áá£á© á¥á» ááᣠááµá¨á©á áá° á¥á± áá»á á«áááá¢"]},"absolutTransactions":{"title":"á¨á£áá áá¥áá¶á½","summary":"á¨á áá á£áá áá° á«á± áá°áµ á¨áááá¨áµá áµ ááµá®áµá¦ á á á
á«á¢á á«áá ááá«áá½á£ á¨á¥áá áááá¦á½ áááá¶á½ ááᢠá¨áá á áµá°á³á³áª áá á¨ááµá¨á© áá ááá á á«ááá¢","whenToUse":"ááááµ á¨á°á°á¨áá£á¸áá áááááá½ ááá³á á ááá¨áá©á áµ ááᣠá¥á á ááµ áááá áááá« á²ááá â á«áá± áá° áá áá¥áá± ááá«áá¢","concepts":["á¨á¥áá áááᥠááááµ ááááµ áá á¥áá áááµ á áá°ááᢠá¨áááᥠáá ááá£á áá á«áááá³á á¥áá á¨á°á¨ááá ááá áá áá á áá°ááá¢","á ááááµ ááááµ á¨áá°á¨á áá£áªá« â á áá áá£áªá£ á á¸á£áªá£ ááá áá á â áá°á±á áá° á ááµ ááµá¥ á«á á£áᤠ«ááá» á°áá ááááµ á¨á°á°á¨áá áµá á¥á» á³ááá áááá áá°áµ á«á³á«áá¢","á¥áá
á¨áááµ á á«á£á¢ á¥á»á á ááµ á á
á«á¢ á¥á» áá¸áᦠá¨áá¨á« ááá«áá½á ááá½ ááµáá®á½ á áá
áááá ááµá¥ á ááá¡áá¢","á á«áá± áá á«áá ááá« áá° áá áá¥áá± á¨áá«á°ááµ á ááá ááᦠáááá¶á¹ á¥áá
áá³á«áᣠá¨á¥áá¢á³ áááá«á¶á½á á¨á á
á«á¢á ááá¾á½ á¥áá« áá¸áá¢"],"example":"á¨á ááµ á
ááµá¦ «á áá áá£áªÂ» áá£áªá« á¨ááá±á á¦áµáµ áááá®á½ á«á³á«áᢠááá± á¨áµá ááá£á á ááá á°ááᣠá¦áµá°áá áááá« áááááᢠá ááá«á áá áá¥áá± á°á¨áᶠá¥á«á á¥áá« ááá¥ááá¢","tips":["áááá¶á¹ á¨ááµá¨á© á¥áá áááá¦á½ ááá£áᦠá¨á£áá© á¨ááµá¥ áááá áá ááá«á¨áµ áááá¦á¹á áááá³á¨á áááá«áµ áá á¥áá ááá«áá ááááá á áá°ááá¢","áá á á ááááá áááᬠáá³á«á â á¨áááá¬áá á®áµ á¥áá áá¥á©á á¥á» á áµáá¢","á¨ááááµ ááááµ áá£áªá«á ááá³áµ ááá áá£á«áµ á á«á ááᦠáááá©á áá¥á á¡á á¥á» á«áááá¢"]},"absolutRegistry":{"title":"á¨áááᥠáá¤áµ","summary":"á¨á°áá¨á áá áá
áµ á¨á£áá áµá¬á³á áááááá½ áá° CSV ááá£áµá¦ ááᣠáá áᣠááªá£ á°áá£áá á¨áááá ááá«á¢ á ááµ á áá«áá á ááµ á
áá¸áµ â áá¹ á¨áá«á°ááá áá
áá ááá¢","whenToUse":"áááá¡ á á£áá© á á©á áááµá³á¨á
ááá ááªáááµ á²á«áµááá â á á¨ááᣠá á¨áá© ááá á á¥á«áá¢","concepts":["áá° áá¤á± á¨ááá¡áµ á áµá¬áµ á¨á°á ááá áááááá½ á¥á» áá¸áᢠá¥áá¢á³áá½á á«áá°á ááá ááá«áá½ áá° áááá¡ á ááá¡áᦠáá¥á«á¸á á¨ááá ááµáá®á½ áá á ááá¥ááá¢","áá
á±á ááá±á áááµ áááµááᦠá áá± á¥á» á¥áµá¨á°ááá áµá¨áµ á¨ááá«á á áá«á á áá á«áᢠáá°áá¹ áá áááµá áá¸áááᣠá¨ááááªá«á ááááªá« á¥áµá¨ áá¨á¨á»á áá¨á¨á»á¢","á¨á°áá£á© áµá áá° ááááªá« áá°á áá á«áᦠáááá¡ á¨ááá£á á áá á³áááá½ áááµá³á¨á
á áááááµ áá°á£áá¢","ááá£á± áá
á±á á áá áá°á áµá£á á¥áá á¨áá³á¨áá áá½ á áá°ááᢠá á°á ááá°áµ áá áá áááµá³áᣠá¥áµáªá¨ááµá áµá©á ááááµ á ááá£áá¢"],"example":"á áá áá¨á¨á» ááµá³á¨á
áááááᦠá¨ááááªá«áá á¨áá¨á¨á»á áá áááá£áᣠááá«á áá«ááᣠáááá ááá£áᢠá¨á£áá© á áá áá á«áá áá©ááµ á áááá ááá« ááááá â á ááá±á á¥ááá¶á½ á«á áµááá á¨ááá¥á á¥á¸áá ááµá ááá¢","tips":["á ááá ááµá¥ á«á áá áá½ á áá áááá½á á áááµ á áá áá¸áᦠá
áá¸á± áá°áá á¨á¥ á°áµáá áá á°ááá
á·áá¢","á¨á£áá© áá á°áá³á³á á¨áá
áµ áá°áá½á áá°áµá¦ á¨á ááµ áá ááá¸á«á°áµ áá áá á á°áá³áµ á¨áááá áá©ááµ ááá¥á«áá¢","ááá á ááá«á á°ááµ áá°á¨áá â á áá
á± áµá ááá¨áᣠá áá ááá« á¨áá á áá ááá á áááááá¢"]},"workflowAnalytics":{"title":"á¨áá°á¶á½ áµáá°á","summary":"á¨á°ááá© áá°á¶á½ á¥áá´áµ á¥áá°áá á©á¦ áµáá± á áá°áµ áá áá áµáá±áµ á°á áááᣠá áá á«á
á ááᣠá¨áµ ááááᣠáá áá°á¡áá áá á¥áá ááᢠááá áá°áá¨á á áá°áµá áá
áµ áá°ááá¢","whenToUse"
1:"áá°á± á áá°á áá á¥á¨á á« áá á°áá½ áá áµá áá á²á«ááá©á£ á¨áµáá á°á¨á áááá á¥áá°áá á ááá
á²á«áµáááá¢","concepts":["á¨áá ááá
áá áá á¨áá áá°á¥ áá á á
á¨á°áá«á© áá¸áᢠáá°áµ áááá á°á áá ááááá áááá áá½ááá¢","ááááá½ á á°á¨á ááá«áᦠá áá«áá 95áá áá¶áᢠááá°ááá á°ááá¨áµ â á áá«á© á áµááá á
á¬á³ á¨ááá³á£á¸áá áá³á®á½ áá¸áááá¢","á¨ááá á á
á á¨á°ááá©áµá á¨á°á ááááµ ááá«áᢠááµáá®á¹ áá«á«á
áááµ á¨ááááµ á áá áá°á¶á½ áááá«áᦠá°áá á¥á«á°á áá áááµ ááá¢","á¨á°áá½ á°áá£á«áµ áá¥á»á¸á áá³á«áᢠááá áá°áá« á¨áááµ á¨áá á½áá© á«áµ-á°ááá± á³ááá á«áá ááá á¨á°áá£á© á áááá½ ááá¢"],"example":"á¨á°áá á ááµáá£áµ «ááá¨Â»á¢ áá ááá«á áá°á á á¨áá ááá
áá á á«á³á«á áá á¨áá áá°á¥ áá á á
62 á áᶠááᢠá¨ááááá¹ ááµá¥ á¨á°ááµ áá¨ááá« á°á¨á á áᦠá á áá«á áá« á°ááᣠá 95áá áá¶á áááµ ááᢠá«áµ-á°á© á¥á© ááᤠá¥á«á á á°áá½ áá á¥á¨á°á¨áᨠááá¢","tips":["á ááá áá°á¶á½ ááá¨á
á¨áá« á á¥á¥á¥á¦ á¨á á«á£á¢ ááµááµ á¨áá³á¨á á¨á á
ááá á³á« áá á²áá»á¸á á¥á» ááá¢","á£á¶ áá
áµ áááµ á«áá á³áªá á áá áááµ áá â á¨á ááµá á¨áá áááá»á¸á ááá¹á á ááá½ á áµááá¥á¢","á¨á ááµ á°áá á á³á½ á áá«á 95ááá áá¶á á¥áµá«áá°ááá¨áµá áµá¨áµ áá°áµá³ áááá«áµ á áá°ááá¢"]},"onboardingTemplates":{"title":"á¨ááµáá£áµ á á¥áá¶á½","summary":"ááá á¨á°áá á ááá á« ááááá½ â áSaaSᣠáááá´áá áá£ááᢠá¥á«áá³áá± á¨á°á¨ááá¹á á¥ááµá á¨KYC áá¨ááá«áá¹á áµá¥áµá¥ á«á³á«áᤠá¨á á¥áá± á¨áµáá
á± á¨á¥á« áá°áµ ááá á«áá¢","whenToUse":"ááµáá£áµ á áá¥ááµ á²á«áµáááá áááá á¨á£á¶ áááá£áµ áµááá á²á«á£ â á¥áá²áá áá«áµá
á¥áá° ááá»á¢","concepts":["á á¥ááµ ááµá áá á¥áá á¨áá á« áá°áµ á áá°ááᢠá¨á¥á± áá°áµ á¥áµá«áá°áá ᨠáµá¨áµ ááá á á«áµááááá¢","á¦áµá± á á¥áá¶á½ á¨ááá«á©áµ á áá¨ááá« á¥áááµ á¥áá á ááá á áá°ááᦠá¨á£áá© á¨ááá´áᣠááá´áá á¨SaaS áá á¥ááᢠá ááµá á«á áµ ááµáááµ áá¨á¥ á¥áá á á©á£áá«á
áµá á áá°ááá¢","á¨á°áá á¨á áá°áµ á¨á á¥áá± ááá ááᦠá¥á±á áá¨á á á¥áá±á á áááá¥áᣠá á¥áá±á ááááá áá°á á²á á¨á°áá á© áá°á¶á½á á áá°ááµáá¢","á
áµá-á¥áá³ á°á¨ááá¹áá á¨áá¨ááá« áµá¥áµá¡á á¨ááá á á ááµ á«á³á«á â ááá¨áµ á¥á» áá°áµ á¨ááá á ááá
á¥á±á á°á ááá¢"],"example":"á¨ááá´á áµáá
áµ á¨áááᥠáá¨ááá« áá ááµáá£áµ á«áµáááááᢠá¨á£áá á á¥áá±á á
áµá-á¥áá³ áá¨áá³áᣠáá¨ááá«á á áµá¥áµá¡ ááµá¥ ááá©á á«á¨ááá£áᣠá¨á¥á± ááá½ áµá á«áá áá°áµ ááá¥á«áᣠá¨áá«á á¨á«á³á¸áá á
á á¥á» á«áááá¢","tips":["ááá°á± á°áá᪠áµá áµá áᦠ«ááµáá£áµ 3» á¨áá á áá á¨ááá¹ á ááááá¢","á¨á£á±á á á¥ááµ ááá¨á¥ áááá áá áá á¨ááááµ ááááᦠáµáá á°á¨ááá½á ááµáááµ á¨áá°á áá¨ááá«áá½á á¨áá¨áá ááá¥ááá¢","áµááááá áµáá
áµ ááá¨á¡á á á¨ááá¥á¦ áá°á± á á¥á± ááµá¥ ááá á«á á¥áá «á á¥á
á» á áá°ááá¢"]},"community":{"title":"á¨á¥áµá áá
á á«áµá ááá¦á½","summary":"á á ááµ áá½ áá áááµ áááá®á½á¦ á¨áµáá
á± á¨á¥áµá áá
á á«áµá ááá¦á½á¢ á ááᥠáá á¨áµáá± áµáá°áá áá á¥á¨áá° á¥áá³áᣠáá£á© áá¼ á¥áá°áá°ááµá áµááµ á á£á á¥áá³á áá³á«áá¢","whenToUse"
1:"á¨áá
á á¨á°á¡á ááá³ á á á ááá ááá
á²á«áµáááᦠá¨áµáá¹ ááá¦á½ á¥á¨áá± áá¸áᣠá¨áµáá á á
áá¡ áá¨áááᣠá¨áµ á á£ááµ á áá ááá¢","concepts":["áá
á áá ááᥠá¨á°áá«á© áá¸áᢠáá
á á á¨áá« á«áá³á á«áá á
á¥á¨áµ ááᤠááᥠá°áá áá¨á¨á»á á¨áá³áá
á¨ááá®á á¨ááá« áá áá ááá¢","«áá 3 á¨12» á¨á áá»á¸á áá¶á á³ááá á á°á«á ááµá¥ á«á á¦á³ ááᦠá«á á«á
á á á£á á áµááµá á°á¨ááá³áá¢","á¨áá£á© áá áá á¨áá© ááááµ áááá«á á¥áá á á¥á
á áááá¥áᦠá¨ááá¡á áááªá«áá½ á³ááá© áááá³ááµ á áá»ááá¢","á¨á°áá ᨠááᥠá áá³á¨ááᦠá¨á¦á³áá½ á¥ááµá£ ááá®áá á¨áá© ááááµ áááá áá á¨á°áá°á áá³ááá½ áá¸áá¢"],"example":"á áá
á á¨á°á¡ ááá« ááᨠá°á¥á ááá¨á«áᢠáááá© ááá¡ á áá 5 á¨12 á¥áá³áá áá£á© áá á¨á³áááµ á áá á¥áá°áá á«á³á«á â áááá¨áµ á¨ááᣠá á£á á°á«áá á¥á¨á á á ááá¢","tips":["á á²áµ ááᥠá¨ááááµá
á ááµ á°áá³á³á á áááá©á á á¨ááá¥á¦ á á£ááµ áááµ áá á á ááµ áá á áá¸á¨ááá¢","áááá¬á á ááá áá áµ áá ááá¨á£á áááá ááá áá á«áᦠá á°áá«á© áááá¬áá½ ááá® ááááá á áá»ááá¢","á«áá± áá° ááá¡ áááá ááá«á â á á£ááµá á¨áá á³áªá á¥áá« áá¸áá¢"]},"pfpDashboard":{"title":"á¨á°á³áµá áááááµ á á ááá ááá³","summary":"á¨áµáá áááá ááá á á«áµ áá¥á®á½á¦ áµááµ ááá» á¥á¨áá° ááᣠáµááµ á°á°á¥áµá§áᣠáµááµ á£ááá¥áµ á áᣠáµááµáµ á°á¨ááá¸ááᢠááá¢á« á¥áá á¨á¥á« á¦á³ á áá°ááá¢","whenToUse":"á áá á ááµ áá ááá á¨á áá«á© áá á¨ááááá á ááµ â áááá© á¨áµ á¥áá°áááá áááá
á¢","concepts":["á¨á°á°á á°á áá á¨á°á¨ááá á°áá«á áá°á¶á½ áá¸á á¥áá á ááµ áá¥á á áá°ááᢠá¨ááááªá«á á¨á£ááá¥á¶á½ áá£á¤ ááá°áá áá° á¥áá± á°ááá°á¢","áá ááá»áá½ á ááá³ ááá á«á á¥áá á á¥áá
áµáá´ á áá°ááᦠá áá
á³áááµ ááá® á¨ááá ááá» á ááá áá ááá¢","áµááá
áá áá½ áá° áºáá½á ááá®áá½ áá á«á â áááá³á¨á áá¥á®á¹á á¨ááá»áá½ áá½ áá°áµ á¥áá á¨áá
á áá°ááá¢","áá¥á®á¹ áááá áµáá
áµ áá¸áááᢠá¥áá
á ááá»á£ á á£ááá¥áµ ááá á áááᬠáááá á¨ááᦠ᫠á á¨áá¹ áá ááá¢"],"example":"á áá«á© á©á¥ ááá± á¥áá´áµ á¥á¨áá° á¥áá°áá áá áááᢠááá³á á¨á£ááá¥á¶á½ áá¥á á¥á¨á¨áᨠáá á¨á°á°á á°á á áá á á¥áá³áá°ááá á«á³á«áᦠáááµ á áá«á ááá® ááá·á â áááá«áá á ááá»áá½ ááá¥áá á¥áá á¥áá
á áá°ááá¢","tips":["á£á¶ á¥á´áµ áááªá«á á áá°á¨á°á áááµ áá á¥áá áá® áá áááµ á áá°ááá¢","ááá³áá á¨áá³á¥ áááᥠáá á áá¥á³ á á³áá³áµáᦠá¥áá
á¨ááá ááá³ áá á¥áá á¨áááᥠá¥áá
áµáá´ á áá°ááá¢","ááááá© áá° ááá»áá½á£ á£ááá¥á¶á½á ááááá½ ááµ â ááá³á á¨áµ á¥áá°ááá± á¥á» á«á³á«áá¢"]},"pfpRegulatory":{"title":"á¨áá¥á¥á áªááá¶á½","summary":"á¨á°á³áµá áááááµ ááá á áá á«á áµ ááµáááµ áá á¨áµ áªáá
1á¶á½á¦ á¨ECSP áá
á³á áªáááµá£ á¨AAOIFI áá ááµá¨áá á¨áµáá á°áá°áá¬áµá¢ áªááá± á á áá«á ááá á«á á¨áá«á áááá³áá¢","whenToUse":"áá° ááµá¨á¨á¢á« áá á²áá¨á¥á£ á á°áá£á£áª á¥á«áᣠá¥á á£ááá¥áµ á¨áµááá áá¨ááá« á²á áá
á¢","concepts":["áªáááµ á á°áá á¨á áµ á
á½á áµ á«á ááµá ááᢠá¨áá« á áá á¨á°ááá¡ áá¨ááá½ á ááá¡á áµáᦠáµá©áµ á«áµááá á¥áá°áá áá áá¢","áµáªáµ á ááµ ááááµ á á°áá ᨠáá¥á áá¨áá«áᢠáªáááµ áµáµáá áµáªá±á áááᥠâ á áá ááá« áµá áá©ááµ áá¨á«á¨á á áá»ááá¢","«á°áá á¨Â» áááµ áááá¨áµ ááá áá áááµ á¥áá á°áá³á áááµ á áá°ááᢠáá° á°áá£á£áª ááá á¨ááµá¨á© áá áá¨ááááá¢","á¦áµá± áááá¶á½ á¨á°áá«á© ááµááá¶á½á á«áááᦠECSP á¨ááµá¨á© áá
á³á áªáááµá£ AAOIFI á á¥áµááá ááµááá¶á½ áá ááµá¨áᣠá¨áµáá á°áá°áá¬áµ á°áá áá ááµ á£ááá¥áµ á¨áá°á¥ á°ááµ ááá¢"],"example":"á°áá£á£áªá á¨á©á¥ ááá±á áá
á³á áªáááµ á á¨áᢠECSP ááá á«áᣠ«á°áá á¨Â» á¨ááá ááá³ áá á ááᣠááá áááá³áᣠá¨áµáªá± áá¥áá ááááá£á â á¨áá á áá á¥ááá« áá¥á®á½ á¨á¨áµ á¥áá°áá¡ ááµá¨á³áµ á«áµáááá¢","tips":["áá
á± á¨á°áá á áá áá á á¥áá á áá¨á¨á»á áá á áá°ááᦠá áá ááá« áááá°á á¨áá¡ á¥áá
áµáá´áá½ ááá«áá¢","á¨áá¨á±áµá áááá½ á«áµá
á áµááá¥á¦ áááá© áªáááµ á¥áá°áá ᨠá«á³á«áᣠáá á
áá
á¨ááá¸á ááá¢","á ááµá áááᵠ«áá¥ááá» á áµáá áᦠá¥á«áá³áá± áµáªáµ áá á¨áµáá áá° á°áá£á£áª á¥áá°áá° áá¥á«áªá« áá áááá¢"]},"pfpDaos":{"title":"á«áá°áá¨á áµáá
á¶á½","summary":"á¨áµáá
á± á¨DAO ááááᦠáµáᣠá¨áµáá
á á°á£á¥ áá´áᣠáááá° áá£á¤á ááá³á¢ á¨áá
DAO ááá á«áᣠá¨áá
á áá° áá³á¦á½á áµáá
á á°á£á¥ áá¸ááá«áá¢","whenToUse":"á¨áá
á á¨á°á¥ áá³ááá½á á ááµ á áµá°á³á³áª á³ááá á á£ááµ á²ááµáᣠá¨áµáá
á á°á£á¥ á¥ááá±á áá½ááµ á²ááá áµá¢","concepts":["á¨áµáá
á á°á£á¥ áá´á á¨áá áµáá
áá á«á
á á¥áá°áááá áááµááᦠá ááµ á á£á á ááµ áµáá
ᣠááá á áµáá» á¨ááááᢠá¥ááá
á¨á°áá«á© á¨ááá²á« á¥ááá¶á½ áá¸á á¥áá á¨áá³á« á
áá¥á á áá°ááá¢","áááá° áá£á¤ á á¥áá« áµáá
á áá°ááᢠá¨á°á³áµá á°á¨á ááᦠáá¤á± á¥áá²áá á áµááµ áµáá
áá°á áµ á¥áá³áá áµá¢","á á£á á¨á á«á áááá° áá£á¤ á¨áá
á°áá áá áᥠá á°áá ááᦠá á¥á± áá³á¦á½ á¨áᶠá á«áááᣠáá³ááá½á á°áá¡á á ááá áá° á áµá°á³á³áªá áááá³áá¢","DAO á á«á¢áá ááµá¥ á«á áá¥á¶á½á á áá½ááᢠáµáá
á á°á£á¡ á¨áá
á á¨á°á¡á áá³á áááµááᤠá¨áá«áµáá½ááµ áá á¨ááµá¨á© á¨á°ááá± áá´áá½ áá¸áá¢"],"example":"á ááµ á
á¥á¨áµ á¥á« áá
á á áµáá áá´áµ á¥áá°áááµ ááá°á á áá áµá¢ á áµáá» á¨á°ááá áµáá
á 30 á áᶠáááá° áá£á¤ á«áá DAO ááá¥á«áᦠáµááá
á£ááµáá»áá½ á áµááá¾á¹ á¥ááµ á ááá¡áᣠá«á á°á³áµá áá ááá á á«áááá¢","tips":["áááá° áá£á¤áá á á¥ááá°á á°á³áµá á áµááᥠá¥áá á ááááá á áá°ááᦠá¨áááá¹ á áá³ á áᶠá¨áááá© áµáµá³ á áᶠáá»ááá¢","áµáá á¨áááµ á áá áá
DAO áá á¥áá°áááµá ááá½ á áá«á°áá ááá© á»áá¢","á¨áµáá
á á°á£á¥ áá´áá á¨ááááªá«á áµáá
á ááµ áá¨á¥á¦ á°áá¡á á ááá ááá¨á á á£ááµá áááá¨áµ á¥ááá á ááááµ ááá¢"]},"infraFinance":{"title":"á¨á á᪠áááµááá®","summary":"á¨á°á°á¡ á¦áá¶á½á á±á©á áá ááá«á¦ áµááµ áá¥á¨áµá£ áµááµ á áááá ááᣠáµááµ á£ááá¥áµá£ áá£á© á©ááá áá¼ á¥áá°áá°ááµá¢ á¨á³á½ á¨á°áá¶á½ ááááá áá£ááá¥á¶á½ á¨áááᥠáªáááµ á áá¢","whenToUse"
1:"á¨á©áá áá á ááµá£ áá£ááá¥á¶á½ áªáááµ á²ááá
ᣠá¥á á á
áá¡ á¨áá°áá°áá á áá¥ááµ áá¨áµ á²á«áµáááá¢","concepts":["á¦ááµá á±á©á á á ááµ áááá ááµá¥ áá¸á áá á áááá«á¸á á¨á°áá«á¨ ááᦠá¨á±á©á áᢠá¨áááµ áá£á á³ááá á¨áá¥á¨áµ áá áá³á°á«á â á¨áá
á á¨á°áá³ á¨áá ááµá¨á ááµááá¶á¹ ááá«á«áá¢","«á¥áµá¨ áááá« á᪠áááµÂ» á¨á¥á« áá áá°á¥ áá á¥áá áá¨á á áá°ááᦠá á¥á± áá¢á áá³áá³áᣠá£ááá¥á¶á½á áááá«á¸ááá¢","«á°ááá§á» á¨á°áá± ááá³ áá á¥áá á¨ááµá¨á© á¥áá½áµ á áá°ááᦠááá³á á¥áµáªáá¨á ááá«áá¹ á ááá±áá¢","áá£á© á©áá áááá á£áá¤á¶á½ á¨áá°ááµ áá á áá á¥áá áá áá± á áá°ááᦠá á£ááá¥áµ áá¨ááá á¨áªááá± á¥á« áá á¥áá á¨ááá
ááµ á áá°ááá¢"],"example":"á¥áµá¨ á©áá áá á ááµ á³áááµ ááá·áᢠáá ááá«á á¨ááá£áá ááá« áá á á«á³á«áᣠáááá© á°áá á¨áµáá á°ááµ á¥áá°áá«ááá¨áᢠáá£ááá¥á¶á½ áªáááµ áááááᣠá áá³á¡ áá á¨áá¨áá ááá©á á áµááµá áá¨ááá£áá¢","tips":["áªááá± á¥áá° ááá áááá³á â á áá
á± á áµááá á á¥áá á áá¨á°á áµ áá á áá°ááá¢","á¨á©áá áá£á á áá¶á áá³á«áᦠá¨á ááªá ááá³áá½ áá á áá³áá¨á á¥áá á¨á£ááá¥á± á°áµá áá á áá°ááá¢","á¨á°á¨áá á°áá¶á½ á áááá© ááµá¥ ááá«áᦠáá
á³áªá áá á¥áá á áá á«á áá´á³ á áá°ááá¢"]},"minterKyb":{"title":"á¨á á᪠áá¨ááá«","summary":"á¨á¶á¨á á ááªáá á°áá¶á½ ááááá« áá
á¨á¥á á¨áá« áááá« ááá³á¢ áá
á¨á¥ á¨áá»áá á ááµ áá áá â áááá«á á¥á¨á á á á¥á«áᤠá¨áá« á áá á áá«á© áá ááá¢","whenToUse":"áá° á áá³á¨ áá¨á¡ á²áá¡á¦ áá¨ááá«á á¥áµáªá«áá áµá¨áµ á¶á¨á ááá£áµá ááá á á áá»ááá¢","concepts":["á¨áááá«á ááá³ áá ááµá¨á á¥áá°áá»á áááµááᢠáá
á¨á¥ á¨áááá°á áááá«á á áá á¥á
á áµ ááá³ á¥á» ááᤠ«á áááá« áá» á¥á «á¸áµáá» á áµá
á°áµ áááµ áá á¥áá³áááᥠá áá«á©á á«á ááá¢","ááµá
áá°á¨á áá¨á¨á» á³ááá áááµá°á«á¨á ááááµ ááᢠá³áá áá
á¨á¥á á¨áá¨áá°á á¨á áá³á¨ áá¨á¡ á¦áá¬á°á á¥áá á áá
áá½ áá á«áá á áá«á á áá°ááá¢","á áµá°á«á¨á±á á¨á áá³á¨ áá¨á¡ á¦áá¬á°á á«áá ááᢠá á°áá¶á¹ ááµá¥ á«ááµá áá©áá¶á½ á¨áá«á¥á«á«áá á»á á¥áá á¨á°áá¶á¹á áµáááá½ á áá°ááá¢","áá¨ááá«á á¨á á᪠áµáá
á±á áááá¨á³á á¥áá á ááµá á°á á áá°ááᦠáááá á¢áá¨á á¨áááá«á ááá³ á áááá¥áá¢"],"example":"á ááµ áµáá
áµ á¥áá° á á᪠ááá£áᢠáááá«á áá
á¨á¥á áá á¥ááᦠá áµá°á«á¨á±á ááá°á á«ááá£áᣠááá³áá «ááá§á» ááááᢠá¨áá« á¨á¦áá¬á°á©á áá³á áá á¥áá â á°áá áá«á ááá á á«áá¥ááᣠá áá«á© á áµááµá á áá·áá¢","tips":["á¨áááá
á ááµ á°áá¶á¹á á á¨ááá¥á¦ á³áá áá
á¨á¥ á á¦áá¬á°á© áá á¥áá á á áá° áá á ááá°ááá¢","á¨áá
á¨á¢á«á áá ááááá£á â áá áá á«á
á á¥áá°á á á á²á£á« á¨áá ááµ ááá¢","«á¸áµáá» á¨ááá ááá³ ááá£áµáá ááá áá áá¨áá³áᤠá¨áá« á ááµ á¨á¶á¨á á¥á«áá½ á ááááá¢"]},"minterMintBurn":{"title":"á¨ááá£áµá á¨ááá á á áá»á¸á","summary":"á ááªá á á°áá°áá± áá ááá½áá¸á á¨ááá¡ á¨á¸á°á á¥á«ááá½ á°ááᢠá á¥á ááá á¦áá³ ááµá¥ á¨á°áá¨á á áá á¨áá¥áá± áá½ á¥áá
ááá£á á¥á«áá ááááá¢","whenToUse"
1:"á¨á áá³á¨ áá¨á¡ á¦áá¬á°á á¥á«á á£á¸á°á áá¥áᦠá á°áá°áá± áá á¨á áá°á á°áá£á á¨áá á¥áá á¥á± áá á¥áá á°áá«áá á áá°ááá¢","concepts":["á áááá© ááµá¥ á¨á¸á°á á¥á«ááá½ á¥á» á áᢠáá³á á¨áá á¥ááµá ááµá
á¨á°á°á¨ááµ á¥áá
á ááá¡á â á á³áªá© ááµá¥ áá¸áá¢","ááµá¨á© á á áá° ááµá á áááááᢠáááá© á á¥á ááá á¦áá³ ááµá¥ áá¨ááááᤠáá¹ áá á¥á«ááá á áµááµá á¨á°áá¸á áá¥ááµ áá á¥á» á«ááááá¢","áá½ áá¨ááá« áá á¥áá áµááá á áá°ááᢠá¥á±á á ááµáá£áµ ááááá á á°áá°áá± áá áá¨áááá áµááá»áá
ᤠáá ááá á áµá«á»áá ááá³á¨á ááµá á¥áá áá á áá°ááá¢","á áá»á¸á á¨áááááµ ááᢠá áµá
á°áµ á¨á°á«á«á áá½ á á áá³á¨ áá¨á¡ á¦áá¬á°á á á©á áá³á¨áá á¥áá á áá¹ ááµá¥ á áá°á¨á á áá°ááá¢"],"example":"á¦áá¬á°á© á¨á ááµ ááá®á ááá£áµ á á¸á°áᢠá ááªá á á¥á ááá á¦áá³ ááµá¥ ááááá½á áá°á áµá£áᣠáá¥áá± áá° á°áá°áá± ááá£áᣠáá¹á á¨á á³á¹ á°ááµá¶ áá° á¥á«áá ááá£áᢠá¥á«áá á°áá½áá áááá â á áááá¡á á á°áá°áá± áá«á¨á á«áá áá©ááµ á°ááá¢","tips":["á á¥á«áá ááµá¥ á«ááá áá áá á áá³á¨ áá¨á¥ á á¥áááµ á¨áá¨áá¨á áá á áá³ááᦠááµá¨á© áá
á á á áá° ááµá ááµá¨á á áá½ááá¢","áá¹á áá¥áá± á¥áá°á°á¨ááá áá²á«á á áµáᣠá¥áá á áá áá¨á¨á» á áá°ááᦠá¥á«áá áááµ á¥áµá¨áá áªááá± á ááá£á ááá¢","á¨á¸á°á á¥á«á ááááµ ááá áá á áá¦áá¬á°á© á³ááá áá áá° ááááµ ááᦠá á°áá°áá± áá ááá á áá°á¨ááááá¢"]},"minterHistory":{"title":"á¨ááá£áµá á¨ááá á á³áªá","summary":"á¨á ááªá ááá á¨ááá£áµá á¨ááá á á¥á«ááá½ â á¨ááááµá£ ááá³á áááµ ááᢠ«áá á°á¨ááá» áááá áááá³á á¥áá «á áá áá ááµáá» áááá á áá°ááá¢","whenToUse":"á¨áá³á¥ áá á²á«áá³áá©á£ á á¨á«á«áª áááá á²áá¨áá©á£ á¥á áá áá³á¨ áá¨á¡ á¦áá¬á°á áá áá¼ á¥áá°á°á¨ááá áá³á¨áµ á²á«áµáááá¢","concepts":["á³áªá© áááá ááá³áá½ ááááᣠááµá
á¨á°á°á¨ááµáá á¨á°á°á¨ááµáá á¨áá®á¦ áááᥠáá á¥áá á¨áµá¬áµ áááá á áá°ááá¢","á¨ááááµ áá£áªá« ááá£áµáá ááá áá ááá«áᢠá áááá áá ááá áá á ááá±á á«áµááááᦠáá©áá± á¥áá áµáá© á áá°ááá¢","áááá¦á½ á áá³á¨ááᢠáµá
á°áµ á á á²áµ á¥á«á áá³á¨áá á¥áá á á®ááá á ááµá°á«á¨á á áá°áá â á áá ááá« á³áªá© ááµá¨á ááá á«á ááá¢","á¨á¥á«áá ááá á¨á áá»á¸á áá á¨á°áá«á© áá¸áᢠááªáááµ áááá áááµ áá»áá ááá°áá áá á¨áá«áµááááá¢"],"example":"áá³á¡ á á ááµ áá á ááá¥ááᢠá á³áªá© ááµá¥ ááá£áµáᣠá¨áá«á ááá áá á á£áá°á áµáá®á¹á á¨áááᥠá¥áá
áµáá´áá½ áá á«áá³áá«áᦠá ááá¥áá áá á á áá°áá áá á¨á°áá¸á á¥á«á áááá â áá©áá±á á¨áá á¨á á¥á± ááá¢","tips":["á¨á áá³á¨ áá¨á¡ á¦áá¬á°á áá á¨áá¨á«á¨áá
á ááµ á³áªá©á áááµá¦ á ááµá¡ á«ááµ áááµ á¨ááµá³ááµ ááá
á°á¨á£á áá¸áá¢","á¨á°á°á¨áá ááµá
á¨á°á°á¨á á ááµ á áá°ááᦠá¨ááááªá«áá á á«áá á áá³áᣠááá°ááá á¦áá¬á°á©á¢","áááá³á¨á á¨á°áá¸ááµá áááá¦á½ áá°áµá¦ á¨á¸á°á áá á«áá°áá¸á á¥á«á áá á¶á¨á á ááá á¨áá¢"]},"installmentSale":{"title":"Instalment sale contract","summary":"The wizard creates a contract in which the seller buys the asset, takes ownership and resells it at a markup fixed at signing. The markup grows neither with time nor with delay â that is what separates it from a loan.","whenToUse"
1:"When the buyer needs the asset now and will pay for it over time."},"lease":{"title":"Lease contract","summary":"The wizard creates a lease and shows both possible endings on the first step. The form is chosen once: an operating lease ends by return, a finance lease by transfer of title after full payment, and it cannot be changed later.","whenToUse":"When the user needs the asset and the owner keeps both title and the ownership costs."},"investmentDeposit":{"title":"Investment deposit","summary":"The wizard creates an application for a term deposit whose return depends on results. The indicative rate sits on its own step with a plain warning: it records the past, takes part in no calculation and is not a promise.","whenToUse":"When the depositor accepts results instead of an announced rate."},"ermOnboarding":{"title":"á¨áµááµ á áµá°á³á°á á¨ááááªá« áá
á á¨á³áµ","summary":"á¨á³á± á¨áµááµ ááá á«á á¥áá± á¨ááá á«á£á¸áá á á«áµ áá³ááá½ á°á¥áµá¦ á á ááµ á¨áá¨á¨á» á°á¨á ááá«á¸ááᦠá¨ááµá¥ áµáááµá£ á¨ááµáªááµ áááᣠá¨áµááµ ááááµá á¨ááááªá« áµáá¶á½á¢ á ááááµ áá ááá á áá»áá â á ááááªá« á
áá¥á®á½á£ á¨áá« ááááµá£ á¨áá« áµáá¶á½á¤ áááá«á±á á¨ááááµ áá»á»á á¨ááá á£áªá« áá áááááᣠáµááµá á¨ááµá¥ áµááá±á ááµá¥ áá á
á³áᢠáá°áá á á¨áá±á á
áá¥á®á½á áá á áá áá°á«áᦠááááᣠáááá¹áá áá£áªáá á¨ááµá¥ áµáááµá¢","whenToUse":"á¨áµááµ áá±á á áá á²á á«á áááá¡ áá á£á¶ á²ááᣠááá áá°á á¨á£á¶ á²ááᣠáá ááá áµ â á á²áµ á¨ááµáªááµ áá áá á á²áµ á¨ááá áµá¥áµá¥á¢ á ááµ ááá á¥á» á¨ááá¨á á¨áá á¨áá±á á
áá¥á®á½ áá½ ááá¥ááᣠááááá á ááá«áá¢","concepts":["ááµáªáá± á°áááá ááᦠá á¥á«áá³áá± ááá á¨3 á¥áµá¨ 6 á°á¨áᤠáµááá
5x5 á¨3x3 á¥á á¨6x4 áá á«á á ááµ á áá«á ááᢠá¨á³á¥á áá¥á¥ ááµá á á°á½áá á²á£á ááᤠáµááá
á¨ááá á£áªá« á¨áááá¹ ááááµ áá¤áµ ááá¢","áááá¹ á¨1 á¥áµá¨ á£áªá«á á«ááµá áá¥á¦á½ á«á ááá°áµá á«á áá°á«á¨á¥ áá¸áá á áá£á¸áᢠááá á¨ááá áá¥á¥ á á«áá³á áá ááá á¨ááá áµááµ ááᣠá ááá áªáááµ ááµá¥ á¨áµá á¨áááᣠá¨ááááµá áá á áááááᤠáµááá
á½áá á°á«á«á¥ á¥áµáªáá áµá¨áµ á¨á³á± áá°ááµ á áááµáá¢","á¨áááá áá á ááá¨á áááá¹á áá° á á²á± á£áªá« á«ááááá¸ááᦠáááá«áá¹á áá£ááá¹ áá á ááᣠáá°á¦á¹á áááá áá¨á°ááá¢","á¨ááááµ áááá«áá á¨áá°á áµá á á¨ááááµ áá¹ á¨áá ááá á°áá³á³á á áá³á ááᢠá¨áá»á»á áá á á áá áááªá«áá½ áá°á¨á£áᣠá áá«á½ á áá²áµ á á°áá°áá½ ááááµá áá° áááµ áááªá«áá½ ááá³á â áá ááµ áááᥠááá°á á
á½ á¨ááá¢","á¨ááááªá«áá¹ áµáá¶á½ á¥áá° á¨áá
ááááá£áᦠá¨á³á± áááµá ááµá¥ áááµá³áᣠáááááᣠá£áá¤á±á á¨áááµá áá
á± áá á áµááµ á«áá± áá áá á«áá¢"],"example":"á á²áµ áµáá
áµ áá±áá á áá á áááᢠá á¨á³á± ááµá¥ FERMA-2002á áááá£áᣠ4x5 ááááá á«áµááá£á (á á«áµ á¨ááµá á°á¨ááá½á£ á ááµáµ á¨á°á½áá á°á¨ááá½á£ á£áªá« 20)ᣠá 1-20 áá á á«áµ áááá½á áááá£áᣠáá»á»á 12 á¨áá á ááµ á¨ááááµ áááá« áá½ááᣠá¦áµáµ á¨á³áá áµáá¶á½áá ááá¨áá«áᢠáá°áá á á
áá¥á®á¹á á«áµááá£áᣠáááá«áá ááá¥á«áᣠá¦áµá±áá áµáá¶á½ á¥áá° á¨áá
áá° áááá¡ á«áµáá£áá¢","tips":["áááá¡ á¨áááá± á ááµ á¨ááµáªáá±á áá á áááµáᦠáááááá½ á¨á°á¨ááá á¦á³ áá á
á³áᣠá áá áááá áá³ááµá á¨áá°ááá¹á á°á¨ááá½ á¦á³ á áᣠá«á°ááá¸ááá¢","á¨ááááµ á°á¨ááá áááá áá»áá â áááá¡ á«á á¥á±á áá á«áᣠáá ááááá áááá á¨áá°á¥ áá á áááááá¢","á¨á³á± manage_erm_settings áááµ áááááᦠá¨á«á±á áá« áá½ á¥á» á³ááá á¨áá±áá á
áá¥á®á½ áá½ááá¢"]},"ermHub":{"title":"á¨áµááµ á áµá°á³á°á á á ááá á¥áá³","summary":"á¨ááá ááá¢á«á¦ á á«á³á¸á áá½á á¨ááá¸á± á á«áµ áá¨ááá½ â á¨á°á£á± á¨á ááá«á½ á°áá½á£ á¨á°á¨á± á¨áµááµ áááááá½á£ á¨á¨á³á± á¨ááá½á á¨ááá¸á á¨áá á« áá¥á¥á á¨ááá¸á á¨áááá ááµááá¶á½á¢ á¨áááá¡ áá áá á¨ááááá½ á½áá á ááá¸á á¥áá° á ááµ á¥áá á¥áá° á°áá£á á áá°ááá¢","whenToUse"
1:"ááá á¥áá
áááá©á¦ áá« áá¹ á¨áááá°á «áᬠáá³á á¨áá«áµáááá áááµá áá» á¨áááá á¥áá «á á á ááá ááá®á½ á¥áá´áµ áá¸á» á¨áááá á áá°ááᢠá¥á«áá³áá± á«ááµ áµááá± áá°ááá¸áá áµ áá« áá½ á¨áááµáµ á ááá á¥áá á¨ááá ᥠáªáááµ á áá°ááá¢","concepts":["á¨á°á£á± á°áá½ â á¨á ááá«á¹ á¨ááááµá á¨áá¥á¥á á¥á´á¶á½ áááµ á¥á°á¶á½á¤ á¨áá¥á¥á á¥á´áµ á¨á áµá°á³á°á á á«áá áá³á áá áááᣠá¨ááááµ á¥á´áµ á°áá á¨á£áá¤á±á áá¥á«áªá«","á¨á°á¨á± áááááá½ â next_review_at á«ááá£á¸á áµáá¶á½á¦ á«áá°áááá áááá á«á¨ááᣠá áááááá á᪠áµááµ áááá¹á á«ááá","á¨á¨á³á± á¨ááá½ â á á¨áá
ááá³ áá origin=ai á«áá¸á áááá¦á½á¤ á¨á áá³ áááµ á áá á«áá°áá« á¨áá
ááá á«ááá áá³á¡ á ááá áá áá","á¨ááááá½ á½áá â á¨ááá¸á á¢á«ááµ á ááµ áá¥á¥á á«áá¸á ááµááá¶á½ áµáá»á¤ á áá á¨áµ áá¥á¦á½ ááá£á (100 % = 10 000) á¥áá á áá¶á áá¥á¥ áºáá á áá°áá","á¥áá
á ááµáªááµ áá áááá áá á°á¥á á¨ááᦠáá á¨áµáá± á ááá áááá áááá«áᣠááá á ááá½ áá áá ááá« á á«ááá¥á â áááá½ áá° ááµáªáá± ááá±"],"example":"á á ááá á¥áá³á áááµ á¨á°á£á± á¨áá¥á¥á á¥á´á¶á½áá á°á£áµ ááá«á¸á á«áá áááááá½á á«á³á«áᢠááááªá« á¥á°á¶á¹á¦ á¨áá¥á¥á á¥á´áµ á¨áá
á áá ááµá áááá« á áá°ááᢠá¨áá«á áááááá¹ â á¨áááµ á ááµ á¨á°áááá áµááµ ááá á¢áá á áªáááµ ááµá¥ á¨á°á«á áááµááá¢","tips":["á¨á¨á³á± á¨ááá½ áá£áª áᥠá áá°ááᦠááá á¨ááá¨áá°á á á áá³ áááµ ááµá¥ á¨áááá¡ áá áá","áááá¡ á á«á± á«áµááᤠáá¨ááá¹ áá á á«áµáá â áá¨ááá¹á áá¨á³á°á","á áááµ á¨ááá°á¡ á«áá¶á½ (á ááá«á¾á½á£ áá¥á¥á®á½á£ á
áá¥á®á½) á¥áá° á£á¶ á¦á³ á¨áá³á¨áµ ááá
á ááá á ááá©á"]},"ermRisks":{"title":"á¨áµááµ áááá¥","summary":"á¨áµáá
á± áá á¨áµáá¶á½ ááááᣠá ááá³á£ á áááᣠá ááµá¥ áµáááµ ááµá¥á£ á áááá á á£áá¤áµ á¨á°á£á«á¢ áá£á«á± á á áááá© á á©á ááᣠá¨áá« áá¹ ááá³ á URL ááµá¥ ááá«áᣠá¨XLSX áá¤á±á á«ááá¨áá áá£áªá« áááá« áá ááá³áá¢","whenToUse":"áá°áá°á ááá« áá°áá
ááá¡á¦ «á¢á«áá á¨áá«áµá°á³áµá«á¸á áá á¨á°áá£á áµáá¶á½Â»á£ «á¨á³á± á«áá¨á£á¸áá ááá á«áá¨ááá£á¸á áá»ᢠá¥áá²á
á«á ááá« á¥áá° á ááá ááá«á â URLá áá á áá áááá¸ááá¢","concepts":["ááá³áá½á¦ á¨áá
ᣠááᣠá¨á°ááá°á£ á¨á°áá áᣠá¨á°ááᣠááá á«ááá áµ","ááá© á°á ááá ai ááᤠááá£á© áá½á á ááá¨áá â ááá£á á«áµááá ááᣠáááá«á±á á áá½á áá³á¥á á á°á áá³á áá«á¨á á«áá áµáá á á á°áá áá áá ááá¥á¨áµ á¨áá áµá","«áááµ á¨áááµ á¥á»Â» á¨á°ááá ááá«á¸á á«áá áááá¦á½á á«áµááá³á â áá°á áá á¨á¥á« ááá³","á¨áááᥠá¨áµá áá¥á¥á ááá á ááááᦠáááá á¨á°áᨠáááᥠááᣠá áá¥á¥ áá á¨á°áá á¨á°á á¨áááµááá® á¥áá³á á¨ááµáªáá±á á¨áµááá
áµáá¶á½ áááá ááá£á","á
á°á á°á¨á°á á á°á«áá áá½ áá á¥áá á ááá áááᥠáá á áá á«áᦠá¨áááá© áá á¨á
á°á á°á¨á°á ááµáááµ á ááá ááᣠáá« áá¹á áá
á á ááá½ á
1ááá«á"],"example":"á«ááá á©á¥ áááµ á¨áá¨áá áá¨áµ áááááᢠ«áááµ á¨áááµ á¥á»Â»á á¨áá ááá³ áá á«áµááá¡á á áááá áá á¨áµáá½ áá° áµáá
áá°ááµá© â á³áá á¥áá³ á²á á¥á á¨áá© áµáá¶á½ áá° áá ááá£áá¢","tips":["áááááá áá£áªá« ááá¨á áá° ááááªá«á áá½ áááá³á â á áá ááá« á á£á¥ á áá áµá¥áµá¥ á£á¶ á ááµá°á áá½ áá á«áá áá á","áá£áªá«áá¹á á¥áá°áá ááµááá á
á°á á°á¨á°áá á ááá«áᦠá áá£á¢á á
á°á á°á¨á°áá áá á¥á ááá®á³áᣠáá£áªá«áá ááá³áµ á¥á» áá á¨á á¨áá","áá¤á± á¨á ááá áá£áªá« áááá áá¾á½ á«ááá á¥áá á¨áá³á¨áá á¥á» á áá°ááᦠá áµáá
áááᥠáá áá áááµá³áᣠá¥áµáá±á áá³á«á"]},"ermRiskCreate":{"title":"áµááµá ááááá¥","summary":"á¨á á²áµ á¨áááᥠáá¤áµ á
á½á¦ áááµá£ á®áµá£ áááá«á£ á¨ááá á¨ááµá¥ áµáááµ ááµá¥á£ á á°á áá á«áá áááᣠá£áá¤áµá£ á¨ááá« ááá á¨áá£á áááá ááᢠááµááᥠá¨áµááµ á«áá±á áá¨áá³áá¢","whenToUse":"áµáá± á¨á°áá¨á á£áá¤áµ á«áá á ááᢠá£áá¤áµ á¨ááá áááᥠááá á áá»ááᣠáá á¥áá²á
á«ááá áµááµ ááá á áááááááᦠáááá á¨á£áá¤á± áá´á³ á¥áá á¨ááá á áá°ááá¢","concepts":["ááµá¡ á¨áµáá
á± áá á¨ááµá¥ áµáááµ ááá£á (FERMAᣠCOSOᣠá£áá II â á¨áá±á á
áá¥á®á½ á¨áá°áááµ ááááá)ᤠá
á¹ á¨á«á± á°áá¨áµ á¨ááá","áááá áµáá±á á¨áá«á°áá ááá áá á«áµá¨ááᦠá«ááá« áááááµ áµááµ ááµáá
á± á£áá áµááá áá°á¨á°á á áá½áá","á¨áá£á áááá áá á¨áá±á á
áá¥á®á½ á¨áááá áµáááá½ á áµááµá ááááᣠáá³á¨áá áá½áá","á¨áááá¡á ááá á
á¹ á ááá¨áá â ááá£á á«áµááá áá"],"example":"á á ááµ á¨ááá« á á
á«á¢ áá á¥ááááµ á°ááá·áᢠáááµá áááá«á£ ááµá¥ «á°áá£á«á â á á á
á«á¢ áá á¥ááááµÂ»á£ ááá «á¨ááá« ááá«á¨áµ áá£áááµÂ»á£ á£áá¤áµ â á¨áááá áááᣠáááá á á ááµ á©á¥ áááµ ááµá¥á¢","tips":["áá®á± á¨á«áµáá áá¥á áá ááᦠá¨áá°áá áªá«á á᪠á£á áá áá£á¤áá½á áªááá¶á½ ááµá¥ áµáá±á ááá¥ááµ á¨áá«áµá½áá á¥á± áá","á¥áá
ááá áááá á ááá£á â á¨á°áᨠáááᥠá²áá á áá ááµá¥ ááá£á¥ á¥á» ááᤠáµáá±á ááááá¡á£ ááááááá á á«áá± áá á«áá¥á¡","á£á¶ á¨áááá áá «áá½á á áµáááá» áááµ ááᦠá¥áá²á
á«á áµááµ ááá«á¸á á£ááá£á¸á áá¨á ááµá¥ áá½á á áá³áá"]},"ermRiskDetail":{"title":"á¨áµááµ á«ááµ","summary":"áµááµ á¨áá á¥áá°á°á á« á¨áá«áá¸á£áá áµáµáµáµ áµá®á½á¦ á á ááá á¥áá³á£ á á½áá á¨á°á¨ááá áááááá½ (á°áá¥á¯áᣠááªá£ áá¥)ᣠá¨áááµá áá
á¶á½á£ áá¥á¥á®á½á£ á ááá«á¾á½á á¨ááᥠá°áá°ááµá¢ á¥á«áá³áá± áµá á¨á«á±á áá¨á á¨áá«áá£á á¨á°á¨áá° á áá á¥á» ááá¢","whenToUse":"á¥á«áá «áá¥á¡ áµááµ áá» á³ááá «ááá á¥áá²á
áá» á²ááᢠá á°áá¥á¯ááá á ááªá á°á¨á áá«á¨á á«áá áá©ááµ áá¥á¥á®á¹ á¨áá«áá¡áµ ááᤠá¨á
1á¥á¥á®á½ áµá©á á¨áá«áá£áá á«á³á«áá¢","concepts":["á°áá¥á¯á áµááµ â á¨áá¥á¥á®á½ á ááµ á«áá ááááᤠá᪠â áá¥á¥á®á¹ á²á á© á¨ááá¨áᤠáᥠâ áµáá
á± áá°ááµá áµ á«á°á á","áááááá½ á áá ááµá¥ ááá£á¥ á¥á» áá¸áᦠááááááá½ POST ááá PUT áµááá «ááááá» á¨áá á áá«á á¨áá","áááá¹ (á á¨ááá´á£ á¢á«á£ áá) á áá±á á
áá¥á®á½ á«ááµ áááµ á°áá½ áááá«á á¥áá á¥áá° áááá áááµ á áááá¡á","á¨áµáá± áá á¨á°á«á«á á ááá«á¾á½ ááµáá á«áµá áá
ááᦠá¨á°á£á° á¨ááááµ á¥á´áµ áªá³á«áá¹ á¨áá¨á°á³á¸á á ááµ á¥áá
áá³á«á","á¨ááᥠá°áá°áᱠ«áá áá¼ ááá³áá áá¨á¨á» áááá áááµ á¨áá°á¥á áµ áá"],"example":"ááªá áá¥á¥ á¨á³ááá á¨áµááµ ááááµ á áá ááᢠá¨áá¥á¥á®á½ áµá© áááµ áá¥á¥á®á½á á«á³á«áᤠá áá± áá á¥á« á á«áµ áá«áµ á áá°áá°áá â áµááá
ááªá á°á¨á á¨á°áµá áá á°á°áá·áᢠá£áá¤áµá á¨áá¨á¨á» áá á«áá á¨áááµá áá
áµ áá¨áá³áá¢","tips":["á¨á¨á³á± á¨áá
ááá³áá áá° áá á áááá áá¨ááá£á â á¨á«á± á
áµá ááá³áá½ á«ááµ á¨á°áᨠáááá á¥áá á¨ááµá áá¨áá« á áá°áá","á¨áµááµ áá á¨á°á«á«á áá áá½á á«áá°áá°á áá¥á¥á ááªáá áááá á áá¨ááµ áá á¥á» á«ááá³á","áµááµá áá°á¨á manage_erm_registerá áááááᤠáááá±áá á áá°á«áᦠá¨á°áá áµááµ á á³áªá ááµá¥ ááá«á"]},"ermRiskEdit":{"title":"áµááµá áá¨á","summary":"áá á¥áá° áááá£á á
á½á£ á á°á«á áááᥠáá á¨áá°áá áᦠáááµá£ á®áµá£ áááá«á£ ááµá¥á£ áááᣠá£áá¤áµá ááá±á áááµá¢ áááááá½á£ áá
á¶á½á£ áá¥á¥á®á½á á ááá«á¾á½ á¥áá
á áá³á¨áá â á¨á«á³á¸á áá« áá¾á½á á¨á«á³á¸á ááááá½ á áá¸áá¢","whenToUse":"á¨áááá¡ á«á± ááá³áá½ á²áá¨á©á¦ á á²áµ á£áá¤áµá£ á¨á°á³á á áááá½á£ áá° áá á¨ááµá¥ áµáááµ ááµá¥ áá¸áááᣠá¨á°áá¨á¨ á¨áááá ááá¢","concepts":["á¨ááá³ ááᥠá¨á«á± á¨áá áááá á¥áá á¨á
á½ ááµá á áá°ááᦠá½ááá© á
áµá ááá³áá½á á¨á«á± á¨áááᥠáá¤áµ á áá","á áµáá¶á½ áá«á¨á á²ááá³áá± á
á¹ á¥áá°áá ááá á«áᤠáµááá
á¨á°á¨á á á½áá á¨ááµáá áááᥠáá¨á áá áá½á á áááááá","á ááᣠá¨áá°á¨á áá°áµ á°á á¥á¨á°á¨á á«ááá áá½á á áá°ááµáµá"],"example":"á¨áµáá± á£áá¤áµ á©á£áá«áá áááᢠá«áá± á á²áµ á£áá¤áµá á á²áµ á¨áááá áá á«ááá â á á²á± á£áá¤áµ á¨á°áá¨á° á³ááá á¨á«á± á¨áá áá á«áµáááááá¢","tips":["á¨ááµá¥ áµáááµ ááµá¥á ááá¨á áµáá±á á á¥á«áá³áá± á¨áªáááµ áááá ááµá¥ á«ááá³á
á°áá â áá¥áááµ á³ááá áá á¥áá á«áµáááµ","áá¨á á á²áµ á¨áááá áµáªáµ á ááá¥ááᦠáááááá½ á¨á«á³á¸áá á³áªá áááá"]},"ermMatrix":{"title":"á¨áµááµ ááµáªááµ","summary":"á¨áááµááá®á á¨áááµ á«áá³á¦ ááµá á ááᣠá°á½áá á ááᣠá¨áµáá¶á½ á¥ááµ á á³á¥á ááµá¥á¢ ááááá á°áááá ááᣠá¨3x3 á¥áµá¨ 6x6ᤠáá á á¨á áááá© ááá£á á¥áá áá½á á ááááµá
1á¢","whenToUse":"áááµááá®áá á á á ááá á²áááᦠá¨áµ á¥áá°áá¨áá½á£ á¨áᶠá«áá°ááááá áá á¥áá°ááᣠá¨á áá ááá á᪠á¨áá°áá áá á¥áá°ááᢠá¨á°áá á³á¥á áá á á
ááµá¨á á¨á¨áµ á¥áá°áá¡ á ááµá³áá» áá° áááá¡ áááµáµáá³áá¢","concepts":["á¨á³á¥á áá¥á¥ á¨ááµáá á¨á°á½áá á¦á³áá½ áá¤áµ ááᤠá¨ááá á£áªá« á¨áááá¹ ááááµ áá¤áµ áá","á¨á³á¥á ááá á á¦áµáµ áááá¶á½ á á ááµ áá áá°áááá â áááᣠá¨ááµáá ááµáá á¨áá°á ááááµá¤ ááá á¥á»áá á á á áá°áá","á¨á«áá³á á½áá (á°áá¥á¯áᣠááªá£ áá¥) á á áááá© ááá¨á£áᣠá áá« áá¹á áá áá°á¨ááᤠáá³á¨á»á ááµáááµ áµááááá á á¥áá
ááá¨áªá« á¨áá","«á«áá°áááá» á áá
á½áá ááµá¥ áááá á¨ááá¸áá áµáá¶á½ ááá¥á«áᤠ«á¨ááá ááªÂ» ááá á²á ᥠáá° áá á¨áá°á áááááá½á ááá¥á«á","5x5 áá£áª á³ááá á¨3x3 á¥á á¨6x4 áá á«á á áá«á áá"],"example":"áµáá
á± 4x5 ááá áá áááᣠá£áªá«á 20ᢠá á«áµ áµáá¶á½ á áá© ááá ááµá¥ áá¸á â á áá³ á ááµ áá «á«áá°áááá» áá¸áᢠá¥ááá« á áá³ á áá± áááá á¥áµáªá«áá áµá¨áµ á«áá³á á¨áááµáá á á£á á«áá°áá áááµááá® áááá»áá¢","tips":["á¨áááá¹ á áᵠ«á«áá°áááá»áá «á¨ááá ááªÂ»á á«áá¥á¡á¦ á£á¶ á«áá³á á¥á© áááµá áá½áá","áááá¡ á¨ááá áá£áªá« á¨ááá â áá¥á¡ á ááááá ááµá¥ á¥áá á áááá¡ ááµá¥ á ááááᤠá á
ááµá¨áá ááá áá«áá¹á á¥áá° ááµá³áá» áááµá³á","á á
áá¥á®á½ ááµá¥ á¨áááá áá á ááá¨á áááá¹á á¥áá°áá áááá£áᦠá¨á á²á± á£áªá« á áá á«á á¨ááµá áááááὠ«á¨ááá ááªÂ» ááµá¥ á«ááá"]},"ermObjectives":{"title":"ááááá½","summary":"áµáá¶á½ á¨á°á«á«áá£á¸á á¨áµáá
á± ááááá½á á á¥á«áá³áá³á¸á áá áµááµ áµááµ á¥áá°áá«ááᢠá¨ááá áá á«áá áááááµ á¨áµáá¶á½ ááááá áá° á
áµáá« á¨áááá¨á ááᦠáµááµ á¨áá«á°áá ááá á«á
á áááááá¢","whenToUse":"áááµááá®á á ááµá¥ áµáááµ ááµá¥ á³ááá áµáá¶á¹ á áá«á°ááµ ááá ááá ᥠá²ááá áµá¦ á¨ááá« ááá«á¨áµ áá£áááµá£ á¨áááµ ááá³áá½á£ á¨ááµáááªá« áááµá¢","concepts":["ááá á¨á«á± ááá³ á«áá á¨áááá áááµ áá¤áµ ááᤠáµáá¶á½ á objective_id áá á
á±á³á","á¨ááá á¥áá³á á¨á áá«á©á «á á¥áá á áá£áá áá áá«á¨á áá á á» á¨áá á¥á«á áááá³áᤠá¨ááµá¥ á¥áá³á á°áá á¨áµááµ á áµá°á³á³áªáá «á¨áµ áá¨áá»á» á¨áá á¥á«á","áµááµ á¨ááá ááá áá ááá á«ááá¨áá¨á ááá áá ááá ááá á¨áá«á°áá áá â á¨áµáá á¥áá°áá á£áá¤á± á¥á» áááá áá½áá"],"example":"«á á á²áµ á¨áá ááá á°áá£áááµá ááµááá» á¨ááá ááá áá á áµáá¶á½á áá¸á¨ááᤠá°á£á± á°áá£á«á ááá± á°áá á¨áá¥á¥áᢠáá
á¨áá®áááµ á®áá´á á ááá³ á¥áá á¨ááá áááᥠáá¤áµ á áá°ááá¢","tips":["ááááá½á áá¨á á manage_erm_register ááá°á£á â áááá¡á á¨áá¨á áá á°áá³á³á áá¥áµ","áµááµ á¨ááá áá á¨áá«á«áá á áµááµ á«áá± áá á¥áá á¨áá
á áá°áá","á áá
áµáªáµ áá« áá¹ áá á á½á ááᦠáááá±á£ ááá¶á¹á á¥ááá á°á«ááááᣠááá± á ááá¥áá á°á¨á ááá£á"]}
1,"ermAppetite":{"title":"á¨áµááµ ááááµ","summary":"á¨áµááµ ááááµ áááá«áá½á¦ áµáá
á± áá á«á
á áµááµ ááá¸á¨á ááá°á á¥áá°ááᣠá á¨áµáá áá»á»á ááµá¥á á áá á¥áá£áᢠá¨ááá¸á á áááá á á ááá á á â áá á¨ááá°á ááá á¥á«á á¨ááᣠááááµ á¥áá á¨áá á áá á¨áááᥠáªáááµ á áá°ááá¢","whenToUse":"á¨á áµá°á³á°á á á«á áá°á¥ á²á«á¸áµá
ᣠáá°á¥ á¨á¥á« ááá³ á²áá£á£ á¥á áááµááá®á áá° á³ááá áá°á áá á«á
á á¥áá°áá¨á ááá
á²áááá¢","concepts":["á¨áµááµ ááááµ (ISO 31000) â áµáá
á± ááááá¹á ááá³á«áµ áááá°áµ ááá°á á¨ááá á¨áµááµ áá áᤠáá»á»á á°áá á¨á¥á± á¨á°ááá°á áá©ááµ áá","á á ááá á áá¶á áá¥á¥ áºáá ááá£á (100 % = 100 000) á¥áá á áá á¨áµ áá¥á¦á½ á áá°ááᦠá¥áá±á ááááá á áµááá á¨á á¥á á¥á¥á áµáá°áµ áá","áá½á°á
á¨á«á± áááá ááᦠáá«áááá á¨áá áá
á°áá á¨áá«áµááá á á áááá© á¥áá á
á¹ á áá°áá","áááá« áá½á á áá°á¨áá â á¨á¥á« ááá³á á¥ááᤠá¨á¸á°áá áá°á¥ áá°á¨á á¨á áµá°á³á°á á á«áá áá³á á¨á³áªá© áá á«á áá","áá¨áá áá½á°á
á manage_erm_appetite ááá°á£áᤠá view_erm á¥á» áá¹ ááá á£á áá á¨áµáááµ á áá«á®á½ á¨ááµá"],"example":"á ááµ áááá« á¨á©á¥ ááá±á á á
áá á°áá£á«á áªá³á«áá½ áááµá£áᢠá á ááá 82 % á²áá á©á¥ ááá± á¥á©áá³ á°áá·áᢠáá
á¥á°áµ á áá°áá â áá ááá á á
á áááá«áµ á áá°ááᦠá áá áá¥ááµ áá°á¡ ááá á¨áá¥áá± á ááµ áá£á³áá¢","tips":["á¨áá»á»á áá á á áá áááªá«áá½ áá°á¨á£áᣠá á áá²áµ á á°áá°áá½ ááááµá áá° áááµ áááªá«áá½ ááá³á â áá ááµ áááᥠááá°á á
á½ á¨áá","á¨á°á£á° áá°á¥ áá áµá°á³á°á á á«á áá³á á¥áá á¨á áá á¨á¥ á¨áµá á áá°ááᦠá áá³á áá ááá
á áá áµ","á«áá¸á°á áááá« ááá á áááµá¥á â á¨ááá á¨áá
á¥á» áá"]},"ermKri":{"title":"ááá á¨áµááµ á ááá«á¾á½","summary":"á¨ááá á¨áµááµ á ááá«á¾á½ ááááᦠá®áµá£ áááµá£ á¨ááá ááá (á´áááµáªá£ SQLᣠáá«á ááá¥)ᣠá á ááá«á¹ á¨á«á± áááªá« á«áá á¨áá¨á¨á» á¥á´áµá£ áááµ á¥á°á¶á½ á¨áá«áááá±áµ ááá á¨áááµ á³áááµ á áááá«á¢","whenToUse":"áµáá¶á½ á¨áá¨á°á³á¸á á ááµ á¨áá«áµá áá
ááá áá¨áµ á²áááᣠá¥á á áá á¨áµáá á ááá«á½ á¢á« ááá áá á¥áá°ááᢠá¨ááá ááá á¨ááá± á á áᥠáá áááá«á±á «ááá áá¨á á¨áá» á¨áá« áááá«áá¢","concepts":["á¨ááááµ á¥á´áµ â á¨áá°ááµ ááµá áááá« á°áᦠá¨á£áá¤á±á áá¥á«áªá« áá ááá","á¨áá¥á¥á á¥á´áµ â á¨áá« á áá áá¥á«áªá« á³ááá á¨á áµá°á³á°á á á«á áá³á á¨áá«áµáááá áµ á°á","á á
á£á«á á°á á á¨áµáá áá á¥áá°áá áááµááᦠhigher_is_worse áá° áá áá£á£á³áᣠlower_is_worse áá° á³á½á¤ á«á á á
á£á« á°á á ááá á¥á","á¥á«áá³áá± á ááá«á½ á¨á«á± áááªá« á ááᦠáá¶á á áá¶á áá¥á¥ áºááᣠáááᥠá áááá¡ ááá á áááµ áááªá«áá½á£ á¥áá²áá á¥ááµá£ ááá°á¨ááµá áááµ","áááªá« ááá á°á á¨ááá á ááá«á½ áᰠ«á áá³áá
á» áááµáá á¥áá áᰠ«á á¨ááá´Â» á áá°ááᦠá á¨ááá´ áá¥á¥ ááá á«ááá¨áá¨áá ááá ááá°áá«á"],"example":"«á¨á«áá°á³á© ááá«áá½ áµáá»Â» á¨ááá á ááá«á½á£ á¨ááááµ á¥á´á± 2 % á¥á á¨áá¥á¥á á¥á´á± 5 % ááᣠáááá°á áá á 2.4 % áá áááᢠáá á¢á« ááᣠá¥á°á± áááµ ááᣠá£áá¤á±á áá¥á«áªá« á áá áµ â á¨áá¥á¥á á¥á´á± áá á¨ááµá¨á± á ááµá¢","tips":["áááá áá½ áá¨ááá á á°áá áá á á©á áá°ááᦠá ááá«á¾á½ á á á¥á áºáá½ á³ááá á á á¥á®á½ áµáááá á© áá áááá áµááááá½ á á ááµ áá áááá³á","áá¹ áá á°á¥á á áá ááᦠá¨á¥á«áá³áá± á¨áµá á¥á´áµá á áááá« á¨ááá³á áá ááá«áá½ á¨á°áᨠá¥á«á áá¸á","á°á á¨ááá á ááá«á½ ááá á áá¥áµáᣠá°á« á¨áá¥á®á½ á°á¨á³á³á ááá ááá«á"]},"ermKriCreate":{"title":"á ááá«á½ ááá á","summary":"áµááá áá¥áá á³ááá á¨áááá±á ááááµ áááá»áᦠá¨ááá áááá á®áµá£ áááªá«á£ áµáááá½á£ á á
á£á«á á¨áá ááá« á°áá¥á¢ ááµááᥠá°áá¹ á¨áááá¡á áµá á«ááµ áá¨áá³áá¢","whenToUse"
1:"áµáá± á¨áá¨á°á± á ááµ á¨áá£á£áµ ááá« á¨áá½á áá á á²ááᢠáá á á áá°á áááµá á á°áá³á³á ááááµ ááá á¨ááá½á á¨áá á ááá«á½ á ááááá¢","concepts":["á¨ááá ááá â á¨ááµá¨á© á´áááµáªá£ á¨SQL á¥á«á ááá áá«á ááᥠâ á ááµ ááá á²á áá½ á ááá«á¹ á¥áá´áµ á¥áá°ááá áááµáá","áááªá«á á ááµ áá áá³áááᣠá¨á¥á«áá³áá±áá á¥á´áµ ááá áááµááᦠpercent_milli á¨áá¶á áá¥á¥ áºáá ááᣠminor_units áááᥠá²áá áááᥠááááá","á á
á£á« áá´á³ ááᦠá ááµ áá¥á áá ááµ á ááá«á½ á¨áááá áá°á¥ á²áá áááá á¨á³á½áá áá","áµáááá¹ á¨áá á ááá á¨áááªá« ááµ á«áµááá£á â á ááá«á¹ áá ááá±á á¨áá«áµá°áááµá á áá« áá"],"example":"«á¨ááá« áá¨ááá« ááᣠááá°á¨ááµÂ» á á´áááµáª áá ááá á«áᣠá á¨á°áá±á£ higher_is_worseᢠá°áá¹ á á«áá± áá áááá£áᦠááááµ 3000ᣠáá¥á¥á 10000á¢","tips":["áááá£á á ááá«á½ áááᥠáááááᦠá«á á¥á± ááá á áá³áá
áᣠá á°áá ᨠááá áá á«á áá¥áá á á¥á á¥á¥á áá³á³á³á","ááá á¨áá«á¥á«á«áá á ááá«á½ á ááá á©á¦ á°á á£áá¤áµ ááááá","á°áá¹ á¥áá
áá á°á¥á á áááá¡á â á¥áµáªáá© áµá¨áµ á ááá«á¹ ááá á áá¥áµá"]},"ermKriDetail":{"title":"á¨á ááá«á½ á«ááµ","summary":"á¨áááªá« á³áªá© á áá«á áá á¨ááááµá á¨áá¥á¥á á¥á´á¶á½ áá á°áµáᣠá¨á°á á áá³áá á¨á¥á°áµ áááá¥á¢ á¨á°á á á°áá áá á á ááá«á¹ á á
á£á« áá áááᦠálower_is_worse á¨ááµáá© á á³á½á£ áhigher_is_worse á¨áá©á¢","whenToUse":"á ááá«á½ á°á á²á¥áµá á«á«á³á á¨á áááá« ááá¨áµ á²á«áµáááᤠá°áá¹ ááááá á²á°áá±á¤ á¥á°áµ á áá¥á«áªá« ááááµ á²ááá áµá¢","concepts":["á¨ááááµ á¥á´á± áá°ááµ ááµá áááá« ááᣠá¨áá¥á¥á á¥á´á± á°áá á¨áá« á áá á¨á áµá°á³á°á á á«á á¨áááµáá áµ áá°á","á¨á¥á°áµ á°á¨ááá½ á áá¤á³á¸á ááá«á«áᦠá¨áá¥á¥á á¥á´áµá á¨á á
á á¥á°áµ áá³á áá áááᣠá¨ááááµ á¥á´áµá á¨áá»á»á á¥á°áµ á°áá áá¥á«áªá«","á¥á´á¶á¹ á¥áá° áá áá¥á ááá£áᣠáááªá«áá á áµáááá ááµá¥ áá³áááᦠááááá áá¥á á«á ááá á áá³á°áá","á°áá¹ á áá
áá½ áá á£á áááá ááµá¥ áá³á¨áá â áá á°á¥á á¨á°áᨠááááµ á¨ááᦠá áá£á¢á á¥á¨á°á¨áá á«áá á³áªá á á áᥠááá«á"],"example":"áá«á á ááá«á¹ á á ááµ áá ááµá¥ á¨ááááµ á¥á´á±á á¦áµáµ áá á²á«áá á«á³á«áᣠááááá á áááá« ááᢠáá
á«á á¥áá á«á«á³ á áá°áá â á°áá á¥áá°á á áá°ááᦠááá¨á á«áá áµ áá°á± á¥áá á áá«á áá á«áá ááµáá á áá°ááá¢","tips":["áá³ á¨áᣠá°á á áá¬á á¨á á«á£á¢ áá á°áá£á«á áááá â áá á á á«á£á¢ áá ááá áªá« á¥áá á UTC á áá°áá","á¥á°áµ á¥áá²á á á°áá áááá³ááµ áµáá±á áá¨áµ ááá á¥áá ááµáááµ á áá°áá","ááá á°áá
á® á£á¶ áá«á ááá© ááá¡ áá á¥áá áááµ ááᦠá¨ááá ááá áááá©"]},"ermLossEvents":{"title":"á¨á°áá£á áµááµ ááµá°á¶á½","summary":"á¨á°á¨á°á± ááµá°á¶á½ áá¨áá»á¦ á¨áááµ ááµááᣠá¨á£áá II á¨ááµá°áµ ááááµá£ áááᣠá á
áá áªá³á«áá½á ááááá½á£ á¨áá¨á á°á
áááµ ááááµá áááµá¢ áá£á«á± áá á áá á á áááá© á á©á á²áá ááá³áá á URL ááµá¥ ááá«áá¢","whenToUse"
1:"á áá°á£á£ á áá ááá á á°ááá
ááµá°á¶á½ á¡áµá ááá« á²áááᦠááªáááµá£ ááµáááá½ áµáá°áᣠá¨áá³á¥ á á«á«á áá áááµá°á«á¨áµá¢","concepts":["á á
áá áªá³á«áá½ á¨áááá á ááµ á«áá áá á ááᤠááááá½ áá° ááááá±á áá°áááááá± áá¨áááᤠá¨á°á£á«á áªá³á« áá©áá³á¸á áá","á¨á£áá II áá°á£ â á¨áááµ ááµáá á ááµá°áµ ááááµ â ááµá°á± á áá áªáááµ á¨áá°á¨áá áµ áá","á¨á¡áµá áá£áá» á¨á ááµ á¥á áááµá ááµá°á¶á½á á ááµ áá á«áµá«áᦠá¨á°á ááá á á
áá áªá³á«áá½ á á¨áµá á³ááá á á¡áµá ááá á«á","á¨áá¨á á°á
áááµ áááá± áá° á°áᨠá¨áªáááµ áá°á á¨áááµá ááµá°á¶á½á á«áááá³á","áááá© á¨áá» á½áá áááá á¨áá á áá£áªá«á á¨áááᦠáá ááá±áá á ááá ááᣠá á°á«áá áá½ áá á á°áá á á á©á á¨áá°á¨á áá£á«áµá áºá
ááµá°á¶á½ á£áá ᵠ«3 á°ááá·á» ááá"],"example":"áá£áªá«á¦ á¨áááµ ááµáá «ááá«áá½á ááá«á¨áµÂ»á£ á©á¥ ááá±á£ á¨áá¨á á°á
áááµ á áᢠá á¥á« áµáááµ ááµá°á¶á½á£ á¨á¥áá± á¦áµá± á¨á¡áµá áá£áá» ááá«á â áá
áá° á¦áµáµ áááᥠá¨á°á¨áá á ááµ áá áá ááᣠáá° áªááá±á á¥áá° á ááµ ááµá¨áµ á áá áµá¢","tips":["áá á áá á¢áááµá á¥áá³ ááµá°áµá ááááá¡á¦ áµáááá¹ á¥áá° áá á á«á
á á áµááá áá","á¨áá¨á°á» ááá á¨áááµ áá á¨á°áá«á© áááµ áá¸áᣠá áá«á¨áá¸á á«áá áá©ááµá á á«á± á ááá«á½ áá","áá£áªá«á á¥áá° á ááá ááá«áᦠá¥á«áá³áá± ááµáááµ á URL ááµá¥ ááá«á"]},"ermLossEventCreate":{"title":"ááµá°áµá ááááá¥","summary":"á ááµ á¥á«á á¨ááµá°á±á áá¨ááá½ á¥á» á«áµááá£áᦠáááá«á£ áá°á£á£ áááµá£ áááᣠá¨á¡áµá áá£áá»á á¨áá¨á á°á
áááµ ááááµá¢ á¨áªá³á«á á¨áááá áá áá½ á áµááµá á ááá ááµá°áµ áá á á«á³á¸á ááááá½ ááááá£áá¢","whenToUse":"á¥ááá³á á¥áá°á°á¨ááá ᢠáá á áá á£áá³áá
á ááµá°á±á ááááá¡á¦ á¨áááµ áá á¨ááááªá«á á¨áá³áµ áááµ áµááááááµ áá áá£áá¢","concepts":["á¨á£áá II áá°á£ áá´á³ ááᦠá«á á¨áááµ ááµááá á¨ááµá°áµ ááááµ áááá¡ áá° ááááá á¨áªáááµ áááá á áá°ááµá","ááµá°á± á áµááµá á¨áá«áááµ áá áá á á«á á¨áá á¨á¡áµá áá£áá»áá áá²á«áá á«áµááá¡","áá áá¹ ááá¾áµ á³ááá á¨á°áá© ááááá½ áá¸áᦠááááá½ á²áá¡ ááá¨á«áᣠá³áªá«á¸áá á¨áá¨ááá¹ á°ááᶠááá¨áµ á áá áµ"],"example":"á¨á°á°áá ááá á áᣠá¨áá®á½á áááµ áá á áµá¨áááᢠá ááµ ááµá°áµ á¨áá¨á°á»á á¨áááµ áá áá ááááá£áᣠá¨áááµ ááµáá «ááá«áá½á ááá«á¨áµÂ»á£ á¨ááµá°áµ áááᵠ«á áá»á¸áᣠá á
áá¦áµá á¨áá°áµ á áµá°á³á°á»ᢠá á
áá áªá³á«áá¹ á ááá á ááááá£áᤠááááá¹á á°ááá½ ááá«áá¹á áá¨á°ááá¢","tips":["áááá¡á áááá á á¨áá¨á¨á»áá áá á á áá á¥áᦠáá á á¨ááá ááµá°áµ áá á¨ááá ááá
á¨á áá á¥ááá°á áá","á¨áá¨á á°á
áááµ áááá±á á ááµá°á± á
1ááµ á¥áá á á«áá á¡áµá á á«áµááá¡"]},"ermLossEventDetail":{"title":"á¨ááµá°áµ á«ááµ","summary":"á¨ááµá°á± áá¨ááá½á£ á á
áá áªá³á«áá½á ááááá½á£ á¨áµáá¶á½á á¨áá¥á¥á®á½ áá ááááá¶á½á£ á°áá°áá±á á¨ááá³ áááá¡á¢ áá¨ááá¹ á¥áá
á á°ááá° áááá á áá³á¨ááᦠááá
áá¨ááá½ áááá«áµá á¨á á«á°ááá áµá á á«á ááá³ ááá¨á«áá¢","whenToUse":"á á²áµ á¥ááá³áá½ á²áá¡á¦ ááááᣠá¨á°á£á« áá áᣠá¨áµááµ áá áááááµá£ á¨áááá« ááá³ ááá¥á¢ á¥áá²áá áá¦á²á°á áá áá¨ááá á¥áá°áá¨á¨áá á áá áá á¨áµ á¥áá°áá áá³á¨áµ á²á«áµáááá¢","concepts":["ááá³ (á ááá½ 6.20) áááá«áµá á áµá á¨á°á áá° á á«á°á á«áá áááá ááᦠá¨á°ááá° áááá á¨á áááááµ ááµá®á½á á¥á» ááá ááᣠáá
á ááµáááµ á ááá³ á¨áá«áá «áá¨á» á¨áá á áá«áá á¨áá","á á
áá áªá³á«áá½á£ á¨ááááá±á á¨áááááá± ááááá½á£ á¥á á¨á°á£á«á áªá³á« á á«áµ á¨á°áá«á© áá¥á®á½ áá¸áᤠáªááá±á á¥á«áá³áá±á áá ááá","á¨ááá³ ááᥠá¨á«á± á
áµá ááá³áá½á á¨á«á± á¨áááᥠáá¤áµ á«áá á¨á°áᨠáááá áá","á¨áµááµ áá á«á áááááµ á ááµá á¥ááá³ áá° áá¨á«á¨áªá« áááá¨ááᦠá¨á°á¨á°á° ááµá°áµ á¨áµáá±á á ááá áááá á«á¨ááá£á ááá á«áµá°á£á¥áá"],"example":"á¨áááá£á á ááµ áá á áá á¢áá¹á«áá± á¨áá³á±á á¨áá á¸áááᢠáááá ááááá£áᣠá¨á°á£á«á áªá³á« á¥áá°áá áá°ááᣠááµá°á±á á¨Â«á¨á
áá áá°áµ ááµááµÂ» áµááµ áá áá«á«áá â á¨áá«á á᪠áááá ááµá áá³á£á ááá á«áááá¢","tips":["ááá½ áááá«áµ á¨ááá ááá³ á¥á
á á¨áááᦠáááá«á±á á¨áá«áá á á¦á²á°á á¥áá á¥ááá± á áá°áá","áá áá¹ á¨á áááá© á¨áááá¡á á¨ááá áá á áááµ áááªá«áá½ ááá£áᤠááá á ááá³áá
á áµ áá «áááá áá» áá¥á á³ááá á°á¨á áá³á«á"]},"ermTreatmentPlans":{"title":"á¨áµááµ áááµá áá
á¶á½","summary":"áµááµá áá° áá¡ á°á¨á áááµá¨áµ á¨á³á°á¡ áá
á¶á½á¦ ááá³á£ á£áá¤áµá£ á¨áá¨á¨á» ááá á ááµá£á¸á á«á áµááá¶á½á¢ á¨á áá á¨á¡ á áá áá á«ááá£á¸á áá£áª á áᦠáá
áµ á³áá ááá
á¥áµá¨á°áá áá á áµá¨áµ á¨áµáá± á᪠á°á¨á áááµáá á áµááµá á¥áá°á á« á°áá¥á® ááá¥ááá¢","whenToUse":"áµááµá áááááµ á¨á°áᣠá¥á«áá³áá± áá á á ááµ á¦á³ áá³á¨áµ á²ááá áµá¦ á¨á¸á°ááᣠá áá°áµ áá á«ááᣠááá á«ááá áµá á áá á¥á
á¥áá³áá¢","concepts":["á¨áµááµ áááµá (ISO 31000) â á¥ááááá½á ááá¨á¥á ááá¸áᦠááááµá£ ááµá°áááᣠáá«á
ááá ááá á","áá «ááá á«ááá áµÂ» á¨áá ááá³ á¨áááᦠááá á«ááá áµ áááµ á¨áá¨á¨á» áá á«áá áááµ áá
áµ ááᣠáá« áá¹á á«á°ááá","ááá³áá½á¦ á¨áá
ᣠáá½á°á
á áá á£á á
ááᣠá¨á¸á°áᣠá áá°áµ ááᣠá¨á°á áááᣠá¨á°áá£áááµ á«á£á£ á¨á°á°á¨á","á áá
áµ ááµá¥ á«ááµ áµááá¶á½ á á¥áááµ á¨áá¨áááá áá¸áᤠáµáááµ á¨ááá áá
áµ ááá á¥á» áá","á¨áᥠá¨áµááµ á°á¨áá áá
á± á¨áá«á°áá°á ááᤠá«á á¥á± á áᶠá¥áá°áá áááá«áµ ááááµ á¨áá"],"example":"áá« á¦áµáµ áá
á¶á½á£ áµáµáµá± ááá«á¸á á«ááᣠá¨á¥ááá« áµáµáµáµ á á«á± á á ááµ á£áá¤áµ á¥á
ᢠáá
á¨áá
áµ á½áá á³ááá á¨á£áá¤á± á á
á á½áá ááᣠá¨ááá³áá áááµá á áááá³ááµ á³ááá á áá¨ááá ááá¢","tips":["á¨áá¨á¨á» ááá áááá³ááµ áá³á á¥áá á¨ááµá áá¨áá« á áá°ááᦠá¨á°á«áá áá
áµ áááá«áµ ááááá","ááá á«ááá áµ áá
áµ á áªáá
1á¶á½ ááµá¥ áááµááá®áá á«á³áá¨áá â á ááá ááµá¥ á á£á ááµ á¨ááá á¸á¥á°á áµáá°áµ","áá£áªá«áá¹á áá¹ á URL ááµá¥ ááá«áᦠ«á¨á¢á«áá ááá«á¸á á«áá ááá áá
á¶á½Â» á ááá áá"]},"ermControls":{"title":"á¨áá¥á¥á á¤á° áá»áááµ","summary":"á¨áá¥á¥á®á½ áááá á¨áá¤á³ááá³á¸áá ááá¨á¨á» áá á¨á°áá°áá áµ áá ááᢠá áµáááá áááá© á³ááá ááá°á á¨á°á¨á± áá¥á¥á®á½ áá£áª ááᦠá«áá°áá°á áá¥á¥á á áªááá¶á½ ááµá¥ ááªáá á¨áµááµ á°á¨á ááá¨á±á ááá¥ááá¢","whenToUse":"á¥á«áá «áá
á áµááµ á á¥áááµ á¨ááá³á áááµá áá» á²ááᣠá¥á á¨áá°á ááá áá¥á á²á³ááµá¢ áá£áªá«á á áá¤á³áááµ áá á«áᦠá«áá°áá°áᣠáá¤á³áᣠá á¨áá áá¤á³áᣠáá¤á³á á«áááá¢","concepts":["áá¤á³áááµ á¨áá¨á¨á»á áá°á áá¤áµ á¥áá áá¥á¥á©á á¨á»áá á°á ááá á áá°áá","«á«áá°áá°á» ááᵠ«áá á«á» áááµ á áá°ááᦠá¥áµá¨ ááááªá«á áá°á áá¥á¥á áá
áµ áá","áá¥á¥áá ááá°á áááµ á¨áá ááááá½ áá¸áᦠáá°á áá¨áá³áᣠá¨áá«á á áá¤áµ ááááᤠ«ááµáá» á¨áá á ááµ á¥á«á á¨áá","ááá¶á¹ á°áá«áá°ááᦠmanage_erm_controls ááá¥á«á á«ááááᣠtest_erm_controls áááµáá á¥á» â áá³á áá½á «ááá á» á¨áá á áá«á á á«áá","áá¥á¥á á¨áááá ááµááá¶á½á áá«áá áá½ááᤠááááá± á¨ááá á á á¨áá¥á¥á© á á©á áá"],"example":"á áᣠáá¥á¥á®á½á£ á¨á¥áá± á á¥á« á áá± ááá¨á¨á» áá á¨áááµ á áá á ááµ á°ááµáááᢠá¥ááá« á á¥á« á áá± á᪠á°á¨áá¸á á¨á°áµá áá á¨á°á°á áµáá¶á½ ááᣠáááá â á¨á©á¥ ááá± á¨áá°á ááá áá¥áá á¨áááá¨á á áµááá á¨áá« ááá¢","tips":["á¨áá¨á¨á»á áá°á áá á¨áá¥á¥á© ááᣠááá á¥áá°áá á¨áá«á³á á¥á¸áá á¦á³ áá","áá¤á³á á«ááá áá¥á¥á ááµááµ á«áµá¨áµááᦠááµááµ ááááá³áµ á¥á áá°áá «á á¨áá áá¤á³á» á¥á ááááµ á«áµá áá³áá áá","á¨áá¤á³áááµ áá£áªá«á á URL ááµá¥ áááá£á"]},"ermControlDetail":{"title":"á¨áá¥á¥á á«ááµ","summary":"áá¥á¥á© á¨ááá³á áááµá ááᣠá¨áµáá¹á á¨áááá ááµááá¶á½ á«áááᣠáá¼á á áá áá¤áµ á°áá°áᢠááááá¶á¹ áá á°á¥á á¨áá°á á³áªá© á á áᥠáá¸áᦠá á ááµáµ áµáá¶á½ áá á«áᣠááááµ áááµ á«áá°áá°á áá¥á¥á áááµ á¨á°áµá áá á¨á°áááá á ááµáµ áµáá¶á½ áááµ ááá¢","whenToUse":"á¨áá°á á ááµ áá°áá ááá¨á³áµá¤ á¨áá°á á áá áá¤á± á¨ááá«áá ááá¨áµá¤ ááµááµ á ááá¨ááá áµ áá á áµááá áá á¥áá°áá°á áááááµá¢","concepts":["á¨áá°á á³áªá© á¨áá¤á¶á»á¸áá á¨ááá¶á»á¸á áá á¨á°á¨áá±á á¨á°áá áá°ááá½ á
á°á á°á¨á°á áá","á¨áááá ááµááá¶á½ á¨áá¥á¥á© á á©á ááá á£áᤠá¨áµááµ áá á«áá áááááµ áá á¨áµáá± á á©á ááá á«á áá³á«áá â á¨áá¥á¥á© á«ááµ á¨áµáá¶á½ áááá á¨ááá","áá¤á³á á«ááá áá°á ááµááµ áááá³áµ áá á¨áµ á¥áá áá¥á¥á©á á¥áá°áá ááá»á áááá«áµ á áá°áá","á¨áá¥á¥á© á£áá¤áµ áµá á áá»á¸áᣠá¨áµáá± á£áá¤áµ áµá áµáá± á°á¨á áááá³áᦠá¥ááá
á¨á°áá«á© áááá½ áá¸á"],"example":"«á¨á᪠áááᥠááµá°á«á¨áµÂ» á¨ááá áá¥á¥á áááµ á¨áááá ááµááá¶á½á á«áááᣠá¨á¦áµáµ áµáá¶á½á áá á°á«áááᢠá¨áá¨á¨á»á áá°áá á¨á á¥á« á á«áµ áá«áµ á áᵠ«á á¨áá áá¤á³á» á áá áá¤áµ áá áᢠáµááá
á¦áµáµ á᪠áááááá½ á¨áá á áá á°ááá°ááᣠá¨ááµáá± á¦á³á á¨áªááá± á áá á³ááá á ááµ ááá¢","tips":["á¨áá¥á¥á© á áááá½ á ááµ á¨áá¨á¨á»áá á¨áá°á áá á«áá¥á¡","áá¥á¥á á¨áááá ááµáááµ á¨áá«áá á¨áá áá¤á³á á áááá áá²á«áá á¨á½áá ááá°áµ áááá"]},"ermFrameworks":{"title":"á¨ááááá½ á½áá","summary":"á¨á°áá¨á á áááá áµááµ ááµááá¶á½ á áá á© áá¥á¥á®á½ á¥áá°á°á¸ááᢠá á ááµ áá á ááµ ááááᦠPCI DSS á¥á SOX áááá»á¸áá á á°áá«á¨ ááááµ ááá¥á«áᣠá á¥áá±á á¨á°áá«á¨ ááá á«áááá³áᤠáµááá
á ááµ á áá á¨á¥ ááá© á áá½ááá¢","whenToUse"
1:"á¨áá«á áááá á ááµá á¥á« á²á³ááµá¦ áá« áá¹ ááµááá¶á½ á¨áᶠáá¥á¥á á¨ááá¸á á¨áµ á¥áá°ááᣠáá¥á¥á áá® áá áá¤á³á á«ááá á¨áµ á¥áá°áá á«á³á«áá¢","concepts":["á½áá á áá á¨áµ áá¥á¦á½ ááá£á (100 % = 10 000) â á¥ááá
á¨áµááµ á ááá«á¾á½ á¨áá ááá áµ á¨áá¶á áá¥á¥ áºáá á áá°áá","ááá± áµáá»áá½ ááá«á«áᦠááááá á¨á°á«á«á áá¥á¥á á«áá¸á ááµááá¶á½á£ á¥á áá¤á³á áá¥á¥á á«áá¸á ááµááá¶á½á¤ ááá°áá áááá á¥ááá°áá áá","áááá á á®áµ á¥áá á id á áá á«á â áµááá
ááá«á á URL ááµá¥ ááá«áᣠá¨á°áá« á áááá áá á áá£á áµ á¦á³ á«ááá","áá¥á¥á á¨ááá ááµáááµá áá¤á³á á«ááá áá¥á¥á á«áá ááµáááµ á¨á°áá«á© ááá°á¶á½ áá¸áᣠá á°áá«á¨ ááááµá áááá"],"example":"áááá 8 400 á¨áá á¨áµ áá¥á¦á½ á¨á°á¸áá ááµááá¶á½á á«á³á«á â 84 % â áá¤á³á áá¥á¥á á«áá¸á áá 6 100 á¥á»á£ áááµá 61 %ᢠá¥ááá« 23 á¨áá¶á áá¥á¦á½ á¨á¦á²á°á© áá á¨áá°á¨áá ááááµ áá¸áá¢","tips":["á áá±á á¥á» á¨ááá ᥠááá
ááá±á á¨á½áá áá¥á®á½ á«áá³áµá©á¦ á¨á°á«á«á áá¥á¥á áá á¨áá á« áá¥á¥á á áá°áá","ááááá ááá¨á á áááá áááá¨áá â ááá«á á°á°ááá áµ áá£áá°á¨á£á ááá©áµ","á¨á½áá áá á¨áµ áá¥á¦á½á á¨á ááá«á¾á½ á¨áá¶á áá¥á¥ áºáá áá á á«áá³á±á¦ áá©áá± á áµááá á¨á á¥á á¥á¥á áá"]},"ermDeficiencies":{"title":"á¨áá¥á¥á ááµáá¶á½","summary":"áá¥á¥á á¨ááá á«á£á¸á á¦á³áá½ áááá¥á¦ áá¥á°áµá£ á¥áá´áµ á¥áá°á°ááᣠá£áá¤áµá£ á¨ááµá°á«á¨á« ááᢠá¨á áá á¨á¡ á áá á áá¥á°áµ á¨á°á¨ááá áá£áªáá½áᣠáá¥á»áᣠááá«á¸á á«áááµ á¥ááµ á áᦠáá á«ááá áµ ááµááµ áá
áµ ááá ááᶠá¥ááá³ áááá¢","whenToUse":"á«áá°á³á« á¨áá¥á¥á áá°á á ááᣠá¨ááµá¥ ááá á¨áá á¦á²áµ á ááᣠá¥á ááááá á²ááá â á¦á²á°á© ááááªá« áá á¥áá°áááá¨áµ ááá¨áµá¢","concepts":["áá¥á°áµá¦ áá
á°áᣠáá«á¨ááᣠá¨áá°áᣠáá³á â á°á¨á á á°á£á¡ á¨áááá© ááááµ áá áá£á","ááá© (á¨áá¥á¥á áá°áᣠá¨ááµá¥ á¦á²áµá£ á¨áá á¦á²áµ) á«á³á½á á ááá°áá á¥áá°áá áááá«á","ááµááµ á¨áá¥á¥á áá áá«á«ááᣠá áá¥á¥á©á á á©á á᪠ááááá¸á á á¥á± áá á¨ááá á¨á± áµáá¶á½ áá","ááá ááá á¨ááµá°á«á¨á«á áá áá°ááᣠá¨á°áᨠááá³á á áá°áá"],"example":"áááµ áá³á ááµáá¶á½á£ ááá±á á¨ááá¸á á ááµ áá á ááááᢠáá
áá«á áááá ááááªá« á¨áá¨áá°á ááᣠáááá±á á¨áááá¨á á ááá³á¸á á³ááá áá ááá á¥áá³áá ááá¢","tips":["á¨ááµá¥ á¦á²áµ á«áááá á ááá á¨á°áµá°á«á¨á ááµááµ áá¥ááá± ááá°áá«áᤠá°áá³á³á© ááµááµ ááá á«ááá áµ áá á á¥á± áá ááá°áá«á","áá³á áá¥á°áµ á¨áá
á°áá á á ááµ á°á¨á á¨á á«á á£áá¤áµ áááááᦠá¥áá£á á¨ááá áá á áá¨á áá"]},"ermAcceptances":{"title":"á¨áµááµ á°áá£áááµ","summary":"áµááµá á¥áá³á áááá á á¨áááá¡ á¥á«ááá½á á á¥áá± áá á¨ááá°á áá³ááá½á¢ á°áá£áááµ á ISO 31000 ááá á¨áááµá ááááµ áá â áá á¥áá° áá³á á¨á°áááá á áá á¥á»á¦ á ááá³ á«á áááµá á¨á°á°á áµááµ á°áá£áááµ á«áá áµááµ á áá°ááá¢","whenToUse"
1:"áµááµá ááááµ á¨áá¸á¨á ááá
ááµ á²ááá á¥áá£á á«áá á°á áá
á ááááᥠá²ááá áµá¢ á¨ááµáªáá± áá ááá áááá áá½á°á
áá áááá¢","concepts":["á°áá£áááµ á°á«á²á£ ááá á¨áá¥áá« áá á«áá áá³á áá â á¨áááµá áá
áµ á áááá á áá°áá","á¨approve_risk_acceptance áá¥áµ áááá¡á á¨áá¨á áá¥áµ á°ááá·áᦠáµáá±á á¨ááá áá á¨áááá á á°á á áá°áá","á°áá£áááµ ááá á«áááᦠááá á²á«á á áµáá± ááááá á°áá£áááµ á«áá áá á¨ááá¨áµ ááá
áá° áá°á áá áá°áµ áááá³á","á°áá£áááµá áá»á á¨á«á± áááá ááᦠáá³áá á¨áááá«á± áá á ááá½ áá°á¨áá"],"example":"á¨á ááµ áµááµ á᪠áááá á áá© ááá ááµá¥ á²áá á¨áááµá áá
á±á á¨á¥á± á¨ááá£á á¨á ááµ áááµ áªá³á« áá áá£áᢠáá ááµ áááµ á¨áá¨ááá« áá á¨á°áá£áááµ á¥á«á áááá£áᤠáá³áá á¨á áµá°á³á°á á á«á á¥áá á¨áµáá± á£áá¤áµ á áá°ááá¢","tips":["á¨áá¥áá« áá á¨ááá á°áá£áááµ áá³á á³ááá áµáá±á áá¨áµ áááá« ááááµ áá","á°áá£áááµ á«áá áµááµ á ááá ááá«áµ á áá áµá¦ á°áá£áááµ á«ááá á°á¨á á¥áá áááááµ á áá°áá","á áá
áµáªáµ áá« áá¹ áá á á½á ááᦠáááá±á£ ááá¶á¹á á¥ááá á°á«ááááᣠááá± á ááá¥áá á°á¨á ááá£á"]},"ermReports":{"title":"á¨áµááµ áªáááµ á áá«á¨á¥","summary":"á¨áá³á°á ááá³á á¨á áá«á áªáááµá¦ á¨áááµááá® áµá¥á¥áᣠááµáªáá±á£ á¨áµááµ ááááµá£ áµááá
áµáá¶á½á áá°áá¨á á áááµ á¨ááááá½ á½ááᣠáá
áµááµ á á ááµ áá½ á°á°á¥áµá áᢠáá±á á á áááá á á©á áªáááµ á á«áá£áá¢","whenToUse":"áá áµá°á³á°á á á«á ááá áá¦ááµ á°ááµ á²á«áµáááᦠá¨ááá± ááµá á á ááµ á¦á³á£ áá
áµááµá áááá áááá¢","concepts":["áªááá± á¨á áá«á áªáááµ ááᣠáá
áá áááá«áᦠá¨áá¥á¥á á
á¾á½ (0409106ᣠá¨DORA RoI) á á á³á½ ááµá¥ á áá°á á°á¡á","áá°áá áªá«á á¨ááá£á á
á½ á áááá© á¨ááááá áµ áá á ááá³á°ááᣠáá©áá±á á á°áá£á£áªá ááµ ááᣠáá á â áµááá
á¥áá
á¥áá²á
á«á ááá³ á¨áá","áá¨áá á¨ááá áá« áá¾á½ á¨áá ááá£á¸á á°áá³á³á ááá®á½ ááá£áᦠá¨áááµááá® áá ááá«á£ á¨áááµ á«áá³á£ ááááµá£ áµááá
áµáá¶á½á£ á½áá","á¨áá¹ á«áµá áá° áá¨ááµ á áááµáᦠá¨áá³á°áá áªáááµ á¥áá á¨áá« áá½ á
á á áá°áá"],"example":"áá¦ááµ áµá¥á°á£ á«ááá áááµ ááá¨á£áᣠáá¹ áá° PDF áá³á°ááᣠá¨áµááµ á°áá£áááµ áá³ááá½ áá áá£á¤áá½ ááá á¨á°áá¶á¹ áá áá«á«ááá¢","tips":["á°áá± á¨áµáá
á± á²áᣠá¨áªááá±á á¨áá¨ááá« áµáá á«á¨ááá¡á¦ á¨á³á°ááµ á¥ááá
áá¥á®á½ áááá¸áá á«á¨ááá£á","áªááá± á¨áá¥á¥á á
á½á á áá°á«áᣠá áá± ááá á ááá"]},"ermSupervisory":{"title":"á¨áá¥á¥á áªáááµ","summary":"á¨á á°á ááá á¨áá¥á¥á á
á¾á½ á áá áááá á á°áá£á£áª á á«á á°á°á£áµá áᦠá¨á¥á«áá³áá± á¨áá
á¨á¥ áµáááá½á á¨ááá á
áá¸áµá£ á¨á áááá© á¨áá«á á áá«áá á¥áµá«áá á¨áá£á áá á³áªá â á¨áá¨ááá« áµááá á¨ááá¨áµ ááá¢","whenToUse"
1:"á
á½ áá° á°áá£á£áª á á«á áááµ á²ááá áµá¦ ááªáááµ ááá á«ááµá£ á áááá© á¥áµáªá«áá£á áá á¥á á¥á áááá á¥áá°á°ááá á«ááá±áµá¢","concepts":["á¨á
á¾á¹ áááá á¨á áááá© áááµ áá á¥áá á á®áá¶á ááµá¥ á¨á°á»á áááá á áá°ááᦠá á«á³áá á¨áá á
á½ á áá
áá« áá½á á¨áá","ááá á¥áá°áᣠá áµááá áááá³á â á¨á
áµááµ á¥áá³ á¨ááᣠáááá«á±á á á á³á½ ááµá¥ á¨á°áá£á á á
á á¨áá¨á á ááá áá¨ááá« áµáá áá á ááá³á°áá","áá®áá¶á á¨áá¨ááá« áá³á á áá°á ááᦠá¨áᣠá
á½ á¨áá¨ááá« áµááá áá á áááᣠá«áá°á³á«á á°áá á áááá© á¨ááá áµá áááá«áµ","«ááá áááá á
á½ á¨áá» á¥á «á¥áµá«áá áá
á¨á¥ á áá°á°á¨áá» á¨á°áá«á© ááá³áá½ áá¸á á¥á áá¨á¥á» áá³á«á","á¨áá¥á¥á áªáááµ á á á°á ááá áá á¨áá¨áá á¨áá¨ááá áµ á áá«á ááᤠá«á á¥á± á«á³áá á á áááá© á«á± áá³á á£á¶ áá áááá³á"],"example":"DORA Register of Information á áááµ á ááµ áá áááá£áᦠááá áá° áªáááµ ááá± áááá£áᣠá
á¹ áá³áááᣠá¨áá£áá á¥á
á ááᶠááá«áᣠá¨áá¨ááá« áµáá©á á áá
á¨á¢á« áááᥠááµá¥ ááááá£áá¢","tips":["á¨áá¨ááá« áµáá©á á¨áá
á¨á¡ áá á á¥á¨á ááááá¡á¦ á¨áá©áµá ááá á áááá© á«áá£á áá á¨áá«áááá á¥á± á¥á» áá","á «á áá°á³á«á» ááá³ á«á á
á½ á¨á®áá¶á áµá
á°áµ á áá°áá â áááá«á±á á«áá¥á¡á¦ á áááá© áá ááá£á á á¥áá³áá»á áááá«á"]},"ermSettings":{"title":"á¨áµááµ áá±á á
áá¥á®á½","summary":"ááá ááá á¨ááá á¨áµá£á¸á áá á¨á³á á°áá¦á½á¦ ááá á¨ááµá¥ áµáááµá£ á¨ááµáªáá± áá¬á¶á½ (á¨3x3 á¥áµá¨ 6x6) á¨á°á¨á áááá«áá½á á¨ááá á°áá½ ááᣠáá£áªá ááááµá£ á¨áááá áµáááá½á á¥á á¨áµááµ ááµá®á½á¢","whenToUse":"á ááááªá« áá
á ááá áá´á á²á¨ááµá¢ á áááµ á°áááµ á¥á« ááá á¥áá
á ááá£áᦠáááá ááá¨á á áµááµá á¨á°á°á¨ááá á¥á«áá³áá±á áááá ááá«áá¢","concepts":["áá¬á¶á¹ á°áááá áá¸áᦠ5x5 á¨3x3 á¥á á¨6x4 áá á«á á áá«á á²áá á¨ááá£áá á¨á
áá¥á®á½ á¥á» áá","áá á¨á°á¨ááá½á á¥ááµá£ á¨áááá« á«áá³áá½áá áááµ á°áá½á (á á¨ááá´á á¢á«) ááá áá â á¨á°á¨ááá½á áá á¨áááá½ áááá á áááá","áá á ááá¨á áááá¹á á¨á á²á± á¨áá¥á¥ á£áªá« á áá»á á¥áá°áá áááá£áᤠá áá ááá« á¨áá°ááá¹ áá¥á¦á½ ááá á áᣠááá áá áᣠááá á¨ááá áµááµá áá° áªáááµá áá° ááááµ ááá»á¸áá á áá°ááµá","á¨á«áá± á¥á ááµá®á½ á¨á«á³á¸á áá¥áµ á²áá á á«á³á¸á á¥á«ááá½ áááá£á","áá¥á¥á®á½á£ á¨áááá á½ááá á¨áá¥á¥á áªáááµ á¨áá á¨á³áá ááá á áá á¨ááá á áá«á®á½ áá¸áᦠá«á á¥áá± áá« áá¾á¹ á£á¶ á¦á³ á³ááá á¨áááá á«ááµ á«á³á«á"],"example":"á ááµ áµáá
áµ á¨5x5 áá° 4x5 áá¸ááá«áᢠá¨áá¥á¥ á£áªá«á á¨25 áá° 20 áááá³áᣠá¨áááá¹ á°áá½á á¨áá« á áá»á á¥áá°áá áááá£áᣠá¨20 á áá áá¥á¥ á«áá¸á áááááá½á á¥áá°áá á¥áµáªáááá áµá¨áµ á áááµ á«áá³á áá «á¨ááá ááªÂ» ááá áá³á«áá¢","tips":["áááá¡ á¨áááá± á ááµ áá¬á¶á¹á áááµáᦠáááááá½ á¨á°á¨á á¦á³á áá á
á³áᣠáááá áá³ááµá á¨áá°ááá¹á á°á¨ááá½ á¨ááá±á áµ á¦á³ á«á³á£á¸áá","áá¨á á manage_erm_settings ááá°á£áᤠá«á á¥á± áá¹ ááá á£áᣠááµá®á¹ áá°áá¨ááᣠá¨ááµááá« á áá«áá á¨áá","áááá á¨ááµá¥ áµáááµ ááá¨á áááá áááᥠá¥áá°áá áááµá£á â á¨áá´ áá³á á¥áá á¨áá½á³ á
áá¥á á áá°áá"]},"ermIntegrations":{"title":"á¨áá GRC","summary":"á¨áá á¨á°áá¢ááµ ááµá¨á®á½ (DrataᣠVanta) áá á«á ááááá¶á½á¦ áá á¥áá°á°áááᣠáááá¡ á áá á°áá³ á¥áá°áá«ááµá£ áá¼ áá¨á¨á» á¥áá°á°á«áá°á£ á¥áá´áµ á¥áá³á áá á¨áµáá¹ áá¥á¥á®á»á¸á á¨á¥á áá á¥áá°á°ááá±á¢","whenToUse"
1:"áµáá
á± áá¥á¥á®á¹á á áá á¨GRC ááµá¨á á²ááá ááá³á¸áá á¨áá°á» áá¤á¶á»á¸á á á¥á
á¨áááá ᥠááá
áá°áá
á¥áá²á°áá± á²áááá¢","concepts":["á¨áá³á¨á» ááá ááá»á á¥á» ááᦠá°ááµá¥á® áááá£áᣠá áááá©á á áááá°áá â áá« áá¹ ááá áááá¡á ááááá á¥áá²á°á« ááµá¨á á¥á» áá½áá","ááááá± á¥áá° á¨áá
ááá á«áᤠááá á¨á á
á«á¢á á°á¨ááᦠá áá áá° á¥á« ááá£á","ááá³á á¨á°á áá³á ááᣠá¨áááá¡ áá¤áµ á°áá áá¨á¨á» á¨á°á¨á°á°á ááᦠá¨á¨á¸á áááᥠááááá±á á á«á ááᣠáá¨á«á áá°ááá","á áá á¨ááá á¨áá áá¥á¥á á á°ááá
ááµ áááá© ááá«á â áá
á¥á« á¥áá á£á¶ á¦á³ á áá°áá"],"example":"Drata á áá£á¥ ááá á°áááᣠááá á°á¨ááá ᣠááááá± áá° á¥á« áá£á£ áááá¡á á áá á ááµ áá áá«áá³áᦠáá¥á¥á®á»á¸á á á®áµ á¨á¥á áá áááá³áᣠá¥á«áá³áá± áá°á»á¸áá á¥áá
á áá°á» á³áªá ááµá¥ ááá£áá¢","tips":["á áá á°áá³ á¨áá°á¨á áááᥠáá¥áá± ááááá±á á á«ááá¥áᦠá ááá á á¥á
ááµááá áá»áá","á áá á¨ááá¸á á¨áá áá¥á¥á®á½ á¨á¥áá ááá á á áá£áª á áá·á â á¨ááá á¥áááµ ááµáªááµáá á¥áá²áá á¨ááá á¥á» á«á¥á©áµ"]},"envPromotion":{"title":"Promote settings to production","summary":"The wizard moves a bundle of settings from the test environment to production: terminals and FX rates are exported as one JSON document, the operator chooses what to take, sees a plan against prod and applies it. The same file can be saved, attached to a ticket and applied later. Before the wizard, settings verified on test were re-entered in production by hand â and the drift between environments became the very bug that made a channel behave differently in production than during certification.","whenToUse":"After the test environment is configured and verified, and production must receive the same configuration. The wizard does not replace configuration and does not run rollouts: it transfers what is already configured, while enabling production terminals belongs to the Go-live wizard.","concepts":["A bundle is a JSON document in the surelle.config-bundle/1 format without identifiers or environment. Objects carry a natural key: for a terminal â partner, provider, currency, type and wallet; for a rate â provider and currency pair.","Matching by key: a match in production means an update, no match means a create. Re-applying therefore never duplicates.","The plan is the platform's answer before anything is written: create, update, unchanged, blocked. A blocked entry always has a reason.","Blockers: the partner is missing in the organization, or the provider wallet does not exist in production. Routing would silently drop such a terminal â the wizard says so before creating it.","Created terminals are disabled unless requested otherwise: enabling in production is a separate decision with a rollout, not a side effect of import.","The file contains provider parameters â the client's credentials with providers. It is the client's secret and is kept like keys."],"example":"Three Bank131 terminals (RUB, USD, EUR) and a RUB/USDT rate are configured on test. The operator exports the bundle from test, deselects EUR (not needed in production yet), builds the plan: two terminals to create, the rate to update (production has an old one). Applies â the terminals appear disabled, the rate is updated. Then the Go-live wizard enables the RUB terminal with a 10 â 30 â 60 â 100 % rollout.","tips":["Build the plan against production first and read the blockers: they name what production is missing.","Store the bundle file with the release ticket â it is the record of what was transferred.","Do not enable terminals via import. Enable them through a rollout, where there is observation and rollback.","A bundle from another organization is rejected by the platform; only support can move settings between organizations."]},"ecosystem":{"title":"Organisation catalogue","summary":"A section that brings together payment channel terms, law firms and assessors, alongside the company's own paid services. It answers the two questions that come up once the product is assembled
1in the test environment: who will arrange the licence, and which channel to route payments through. We do not answer them ourselves â licences and channel contracts remain your responsibility â but we bring the answers together in one place.","whenToUse":"Open it when the environment is configured but the payment channel or the legal side of the launch is not settled yet. It is also the place to start if you are comparing whether moving card data handling to us is cheaper than attesting compliance on your own.","concepts":["Two zones rather than one list. On top, «Company services»: paid services of 2PiR LLC, the same legal entity that supplies the platform. Below, a catalogue of independent firms. The split is deliberate: in one list our own entry would have to be ranked against third parties, and any sorting rule would read as self-preference.","Three entry types in the catalogue: channel offer (fee, lead time, connection link), law firm (jurisdictions, specialisation) and compliance assessment (scope, lead time). Filters are by entry type and region; the region list is built from the entries themselves, so it never offers an empty option. Next to them is a search box by company name: the catalogue holds four hundred entries, and a specific firm is quicker to find by name.","The ready-adapter line appears only on channel offers. It is checked against the platform's live provider list rather than taken from the card on trust, and it shows which channel will start fastest. Having an adapter does not mean the channel will approve your category â that is the channel's decision.","Every entry carries the date its terms were confirmed. Terms are set by the firm and published by us, so you can see as of when they hold. If the date is old, confirm the terms at the source.","Every card ends with contact details: an address where the firm publishes one, phone, email and website. The section collects no requests and forwards nothing â you write to the party you choose directly. Where a card says the firm publishes no direct contacts, it takes enquiries only through the form on its own website. A request form appears only on cards of firms that have confirmed the exchange format with us: there the enquiry is logged on our side and passed to the firm directly."],"example":"An operator has assembled the environment in test and is stuck on which bank to route payments through in their region. They open the section, filter by region, see two channel offers, and one of them shows a ready adapter. The other has none â integration will be needed, and that is a conversation about timing. They follow the link on the chosen one and sign the contract with the bank directly: we are not a party to it.","tips":["Do not confuse this with the «Module Catalog», which enables platform capabilities for your organisation, or with «Partners», which lists your merchants.","The menu item appears once at least two entries from independent firms are published. A single entry is not a choice but an exclusive recommendation. Company services do not count towards this.","We do not connect you to the party you choose and do not vouch for the outcome: a licence is decided by the regulator, an account by the bank, compliance by the assessor.","Working inside our environment reduces your own assessment scope for card data requirements but does not remove the obligation to comply. How much remains is determined by your scenarios and your assessor."]},"agenticCommerce":{"title":"Agentic commerce","summary":"The wizard turns on payments made by a person's software agent rather than by the person, and sets the bounds those payments run inside. An organization configures this for itself and offers it to its partners: the platform performs the mandate checks, so a partner needs neither to parse signatures nor to keep a key registry of their own.","whenToUse":"When an organization's partners need to sell through agents â assistants that search and buy on a person's behalf. Configuration is a one-off per environment: afterwards the partner uses the ordinary payment API while the platform handles mandates and delegated rights. Available to a client with settings permission when the Agentic Commerce module is active.","concepts":["A mandate (AP2) is a person's signed authorisation: buy this, from this merchant, up to this amount, until this moment. The agent presents it instead of clicking Pay","An intent mandate is standing permission, signed while the person was present and spent later when they are not; a cart mandate describes one specific purchase","A delegated right is the string an agent presents instead of a payment credential: it permits a charge against the organization's card, account or wallet within stated bounds. The credential is never shown to the agent and cannot be recovered from the right","The trusted key registry answers whose signatures the organization accepts. Without it a signature proves nothing: anyone can generate a key pair and sign themselves an authorisation","Signing mode: the platform with the organization's Vault key, or the user in their own wallet. The second means the platform physically cannot sign on a person's behalf","Organization ceilings apply on top of a mandate: the mandate bounds one purchase, the ceiling bounds what the organization is willing to hand agents at all. The lower of the two wins","The ACP agentic checkout is a purchase inside someone else's chat: the agent drives the flow while the platform serves the session and the charge"],"example":"A bank wants its merchants to accept purchases from assistants. In the wizard it enables AP2, picks server-side signing (the Vault path secret/agentic/mandate-signing), sets a 500 EUR per-payment and 2000 EUR daily ceiling, adds its wallet's public key to the registry, and on the dry-run step pastes a mandate that wallet issued. A verdict of \\"verified\\" means the configuration works. The merchant then receives the API key, the organization id and a link to the partner documentation.","tips":["Start in the test environment: settings are per environment, and a mistake in the key registry surfaces on the dry-run step rather than on a live payment","An empty ceiling means \\"no ceiling beyond the mandate\\", not zero. If the organization is not prepared to spend whatever a person authorised, set one","One charge per right is the whole point of a delegated right. Anything above one means the agent can repeat a payment without fresh authorisation","Revoking a key works backwards in time and invalidates mandates already issued â that is for compromise. For planned rotation, set a validity window when adding the replacement","An issuer's private key never goes into the registry: the platform needs only the public half"]},"workflowDeadLetter":{"title":"Failure review","summary":"Process tasks that could not be completed: the step handler failed as many times as the retry policy allows, and the process cannot move on by itself. The page shows which node the process stopped at, what the other side answered and how many attempts were made.","whenToUse"
1:"Daily while the list is not empty: every entry is a customer process standing still. Also when investigating a stuck payment complaint and after a provider outage.","concepts":["Not every failure ends up here â only one that exhausted its attempts. Retries apply to failures backed by state on the other side: connection loss, timeout, service refusal. An answer like 'no such account' is not retried, because it will not change.","If the step has an error boundary event drawn in the process itself, the failure follows that path and never reaches this page: the process handles such a case on its own.","Retrying from here re-executes the step for real, rather than marking it done. The process continues from the same place once the step finally succeeds.","Closing an entry does not execute the step: the process stays where it is. It is a decision not to pursue it, not a confirmation that all is well.","The entry context keeps the process variables as of the failure and the task it happened on â they show what data the step could not handle."],"example":"A payout provider stopped responding. The 'send payout' step retried three times with a growing delay and reached the review page with a timeout answer. The operator sees the entry, confirms from the provider log that the connection is back, and presses Retry â the step runs again, the payout goes out, the process continues. If the provider declined the payout on the merits, retrying is pointless: the operator closes the entry and raises a case.","tips":["Before retrying, make sure the cause is gone: a retry against an unresolved cause spends an attempt and returns the entry.","Retrying a payment step without provider-side idempotency can create a second charge â check with the provider before retrying by hand.","The same node appearing here repeatedly is not an operator's task but a reason to change the process or the node's retry policy.","A burst of entries in a short period usually means a provider outage rather than a problem with each individual process."]}}}`),t={help:e};export{t as default,e as help};
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.