Product Highlights

We’re excited to share that we’ve added the Prove Face-ID Manual Review feature. This lets you now manually validate users who encounter issues with the Prove Face-ID verification step (e.g., due to poor lighting or low-quality images). After three failures, the system automatically escalates the session for your review via the Mono dashboard.

Check our detailed integration guide to learn more about how this feature works.

API Improvements

1. TIN Lookup: CAC channel

   The cac channel for TIN Lookup is now back up and running, making it the most reliable method to verify TIN via NRS. We've also introduced two new fields to the TIN Lookup response when using the cac channel:

   • nrs_tin: The NRS Tax Identification Number.

   • address: The registered address of the taxpayer.

   For more details, please refer to the TIN Lookup integration guide and our API reference.

2. CAC Lookup: New Status Report endpoint

   We've added a new CAC Status Report endpoint that allows you to retrieve a company's CAC status report as a PDF document. Unlike other CAC endpoints, this returns the actual PDF file directly.

   CAC Lookup: Exact Search Parameter

   We've added a new optional exact parameter to the CAC Business Lookup endpoint. When set to true, only businesses whose names start with the exact search term are returned. This enables more precise business searches. The parameter defaults to false to maintain backward compatibility.

3. Billing Notice: BVN Lookup

   All BVN Lookup API requests are billable, including failed lookups (e.g. BVN not found or invalid).

   To help manage cost, we recommend that you:

   • Validate BVNs before calling the API (BVNs must be 11-digit numeric values).

   • Avoid bulk or blind verification of unverified BVNs.

   • Implement throttling and monitor failed request rates.

4. We've introduced new fields across several core webhook events and the Account Details endpoint to improve how you track applications, manage custom metadata, and audit events.

   A) Improved Context for Account Events: To provide better visibility into which business or application triggered an event, the app and business fields have been added to the following webhooks:

   • mono.events.account_connected

   • mono.events.account_updated

   • mono.events.account_reauthorized

   B) Custom Metadata in Account Connections: We have added support for the meta.ref field (which captures any dynamic parameters passed via the metadata object) to the following areas:

   • Webhook: mono.events.account_connected

   • API: Account Details endpoint response.

   C) Event Tracking with event_id: To assist with event auditing, a unique event_id field is now included in the payload for:

   • mono.events.account_connected

   • mono.events.account_reauthorized

   • mono.events.account_updated

5. We’ve added a new required parameter, disco_code, to the Address Verification endpoint. Please refer to the API reference for more details.

6. We've made updates to the NIN Lookup API, to supports PDF generation. This can be achieved by including the output=pdf query parameter when calling the NIN Lookup API.

   When you include output=pdf, the response will contain a pdf object with a jobid and status. If the status is "completed", a url field will be included with the PDF download link. If the status is "processing", you can use the new Poll NIN Job API to check the status and retrieve the PDF URL when it's ready.

   For more details, please refer to the NIN Lookup integration guide and the Poll NIN Job API reference

We're always available to help

Mono Slack Community

Join the discussion, ask questions, and suggest new features in our Slack community

Get support

Email us at support@mono.co