With CRS's Consumer Credit B2C offering, you have multiple integration methods to offer Consumer Credit Scores and Credit Monitoring directly as part of your web or mobile experience.
Overview
Once you have chosen your integration option from among:
- Usage of credit reporting on a web page with user authentication managed by CRS: Web Widget with Integrated Authentication
- Usage of credit reporting on a web page with user authentication managed by you: Web Integration with Custom Authentication
- Usage of credit reporting on a custom UI such as a website or mobile app with authentication managed on the website/in the app: API Integration for Custom Web or Mobile App
Webhooks pertain to all 3 integration options, but they are optional. Web Messaging only applies to the Widget (integration option 1: Web Widget with Integrated Authentication and option 2: Web Integration with Custom Authentication), and is a feature of the widget that customers can use for greater extensibility and insight into the stages that the widget is rendering.
- Webhooks - Customers should implement Webhooks if they want their users to receive notifications. The customer's webhook endpoint receives the notifications for all their users in nightly batches, and then the customer can send these notifications to their users in whatever fashion they wish.
- Web Messaging - the widget has window events that can be listened for using an event listener (mozilla doc)
- window.addEventListener('message', receiveMessage, false); : this creates the 'listener' callback function, receiveMessage, which receives notifications for events
- these events have types that can be checked by the customer for triggering whatever javascript code they want when a desired event.data.type value is received.
- there is a function on the event.source object called postMessage(). This function can be used for pre-populating certain fields -- additionally, for integration option 2: Web Integration with Custom Authentication, postMessage({}) can be used for redeeming the preauth token (authenticating a user) as an alternative to passing the preauth token as an iframe URL parameter.