Versions Compared

Old Version 2

changes.mady.by.user Raphael Ferreira Gomes

Saved on

compared with

New Version 3

changes.mady.by.user Ruani, Andrea

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

/wiki/spaces/EGMT/pages/4255419305

  • Fraud rule - rediscuss the problem, rather than jumping into the solution. there seems to be plenty of requests around fraud and we are not even using the fraud prevention provider

  • Should we build fraud rules on our platform or integrate with external fraud provider like https://www.forter.com/ ?

  • Talk with  https://www.forter.com/

  • Talk with US (Felix Zhornitsky, US Payment Lead) how they implement fraud controls.

  • Ticket opened by Iberia regarding one of the problems

    Jira Legacy
    serverSystem JIRA
    serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
    keyIREQ-47

Assessment

  1. App current solutions in place, Forter

  2. App's current vulnerabilities and potential points of attack (Diego?)

  3. Analyze historical data for fraud patterns and vulnerabilities (Radu / Iberia)

  4. Benchmark per industry and geography (?)

  1. App current solutions in place, Forter

 

View file
nameForter & RBI Germany -- Introduction .pdf

Priority (#)

Topic

Notes

1

/wiki/spaces/IN/pages/4254270051

Implement specific rules for cash orders to avoid frauds (46% delivery orders are cash)

Forter Abuse Prevention Process - Flagging Potential Abuse

https://docs.google.com/document/d/1OMaLws85o2C1dGjT_p_nKkZiojMoELeZBiOG59COOXE/heading=h.x5bf9gfs5xoj#heading=h.s6d3dxy2kqfd

...

  1. Analyze historical data for fraud patterns and vulnerabilities (Radu / Iberia)

/wiki/spaces/EGMT/pages/4255419305