search.noResults

search.searching

saml.title
dataCollection.invalidEmail
note.createNoteMessage

search.noResults

search.searching

orderForm.title

orderForm.productCode
orderForm.description
orderForm.quantity
orderForm.itemPrice
orderForm.price
orderForm.totalPrice
orderForm.deliveryDetails.billingAddress
orderForm.deliveryDetails.deliveryAddress
orderForm.noItems
and tools for fraud prevention, responsible gaming, geo- location, and identity verification, such as for example multi-factor authentication and biometric verification. Many of those are coming out of the box with iCore’s KYC and Fraud&Risk modules and some are built on top by integrating third party solutions such as Iovation, Fingerprint, Callsign, CAF, and Legitimuz.


iCore's Fraud&Risk module leverages user defined rules powered by real-time algorithms that allows us to detect suspicious activities instantly. For instance, our system analyses transaction patterns and flags anomalies that may indicate fraud or even automatically conducts preventive actions. We regularly update our anti-fraud systems to adapt to new threats ensuring that customer’s operation remains secure and reliable.


Comtrade manages enterprise clients across multiple markets on individual deployments. How are iCore upgrade deployments phased to mitigate risk?


For each client we have a dedicated project team that works on client’s specific roadmap and manages to customise and deploy Core product roadmap updates into their releases. We plan all upgrades at predefined times to ensure consistency and prevent disruption. Tis allows us to coordinate with clients and ensure they are prepared for the updates.


Te QA lead of the project team organises customer 88


consolidation meetings to review the status of deployments and address any issues promptly. Deployments are scheduled with each client individually. Tis ensures that all stakeholders are aligned, and any potential risks are mitigated swiftly. With each client we have multiple dedicated development environments, integration environment(s) under continuous integration and staging.


We run smoke and sanity tests on integration environment(s) to ensure that all affected test cases are re-executed and validated. Tis helps us identify and resolve any issues before they impact the production environment. Bug triage sessions allow us to prioritise reported issues and decide on the necessary actions. By planning, phasing and individualising iCore upgrade deployments in this manner, Comtrade ensures that risks are minimised, and clients receive reliable, high- quality updates across multiple markets.


Who is responsible for communicating with operators about new feature rollouts and iCore's upgrade strategy? Are the tech team involved in these discussions?


As mentioned earlier for each client we have a dedicated project team. And the primary responsibility for communicating with operators about new feature rollouts and iCore's upgrade strategy lies with the Project Managers (PMs) and Business Analysts (BAs) when it comes to details. Tey ensure that operators are informed about upcoming changes, benefits, and any potential impacts. And it is important to


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56  |  Page 57  |  Page 58  |  Page 59  |  Page 60  |  Page 61  |  Page 62  |  Page 63  |  Page 64  |  Page 65  |  Page 66  |  Page 67  |  Page 68  |  Page 69  |  Page 70  |  Page 71  |  Page 72  |  Page 73  |  Page 74  |  Page 75  |  Page 76  |  Page 77  |  Page 78  |  Page 79  |  Page 80  |  Page 81  |  Page 82  |  Page 83  |  Page 84  |  Page 85  |  Page 86  |  Page 87  |  Page 88  |  Page 89  |  Page 90  |  Page 91  |  Page 92  |  Page 93  |  Page 94  |  Page 95  |  Page 96  |  Page 97  |  Page 98  |  Page 99  |  Page 100  |  Page 101  |  Page 102  |  Page 103  |  Page 104  |  Page 105  |  Page 106  |  Page 107  |  Page 108  |  Page 109  |  Page 110  |  Page 111  |  Page 112  |  Page 113  |  Page 114  |  Page 115  |  Page 116  |  Page 117  |  Page 118  |  Page 119  |  Page 120  |  Page 121  |  Page 122  |  Page 123  |  Page 124  |  Page 125  |  Page 126  |  Page 127  |  Page 128  |  Page 129  |  Page 130  |  Page 131  |  Page 132  |  Page 133  |  Page 134  |  Page 135  |  Page 136  |  Page 137  |  Page 138  |  Page 139  |  Page 140