Internal Considerations

Topics to reflect on internally when considering a new product or solution.

Top Prerequisites – Technical

If your organization decides to transition from an on-premises IAM deployment to a cloud-based approach, you will need to carefully assess the gap between the technical capabilities desired by your organization and those offered by the FRIP vendor. Thus, there are some technical prerequisites that should be considered before selecting an IGA solution.

Do you have a modern, API-driven Customer IAM system in place?

Many CIAM services have integrations with FRIP services. Check to see if the default integrations meet your organization's requirements. If not, inquire as to how to connect your CIAM to the FRIP service in question (generally via REST APIs, SDKs, and/or with JavaScript for customers).

Can your payments processing or other transaction processing applications interoperate with the FRIP service?

Almost all FRIP solutions are SaaS, and the primary means for interacting with them are via APIs, similar to CIAM.

Will the FRIP services under consideration meet your expectations and/or the Service Level Agreements you have with your customers?

Inquire about how much latency adding callouts to the FRIP services will add. Understand each component of your own transaction or payments processing systems and how that will affect the customer experience.

Understand how fraud is currently affecting your organization.

Quantization is key. What types of fraud is your organization experiencing? How have various fraud tactics changed? Can the FRIP solutions you are considering demonstrably reduce these specific types of fraud and the costs associated with them?

Executive buy-in and the business case for FRIP.

Reducing fraud essentially increases revenue. Engaging a FRIP solution should not be a difficult case to make to executives. Many FRIP vendors can provide case studies showing 10x or more savings compared to the outlay for their services.