Release Notes 2.5.2 – Live

Sprint Duration: April 20 – May 8, 2026
Release Date to Production: Wednesday, July 22nd, 2026

---

Quick Peek – What We Worked On

Sprint 2.5.2 focused on improving annual re-verification workflows, expanding BPO support across the BCID ecosystem, refining webhook payload behavior, and improving communication during vetting reviews.

During this sprint, we completed work on:

• A fix for the View option after 365-day re-verification
• A hotfix for Display Identity webhook payloads
• Improvements to the 365-day annual re-verification document flow
• Two-way comments for flagged steps
• New BPO registration and onboarding workflows
• New BPO role permissions and portal behavior
• New Submitted By tracking in Status List and Display Identity views
• BPO support across webhook payloads and reporting logic

---

Detailed Changes

1. View Option Fix After 365-Day Re-Verification

We identified an issue where, after completing the 365-day annual re-verification, the View option in the Status List could open a blank page instead of showing the BCID application details.

This issue has now been fixed so the View option always displays the application correctly, even after annual re-verification.

In the meantime, users can still download the PDF version of the BCID application if they need to review it.

Why this matters

This ensures continued access to BCID application details after annual re-verification is completed.

2. Hotfix – Include NumHub Entity ID in Display Identity Webhook Payloads

We prepared a hotfix to include the NumHub Entity ID in all Display Identity webhook payloads.

This request came from OSP partners currently using this identifier to help map data internally. While our long-term direction continues to focus on ecosystem-facing identifiers such as:

• EID
• Display Identity ID
• Parent ID
• Deal ID

we understand some integrations still rely on NumHub-specific identifiers today.

Important Note

This hotfix is tentatively planned to be pushed to production on May 22nd, 2026.

Why this matters

This supports current partner integrations while we continue guiding OSPs toward a more standardized long-term ID strategy.

3. 365-Day Annual Re-Verification – Require New Documents

We updated the 365-day annual re-verification flow so that Step 7 now requires new supporting documentation.

Previously, users could still see and rely on files originally submitted during the initial BCID onboarding. Going forward:

• Previous files will remain stored for audit history
• Users must upload newly dated versions during annual re-verification

This includes:

• Updated LOA
• Updated proof of telephone number ownership

Why this matters

Annual re-verification should rely on current documentation, not files submitted a year or more ago. This helps maintain stronger compliance standards within the BCID ecosystem.

Important Note

If you are currently completing annual re-verification, we strongly recommend uploading newly dated documentation to avoid additional follow-up requests from the vetting team.

4. Two-Way Step Comments for Flagged Steps

We introduced a more interactive communication workflow for flagged BCID application steps.

Previously, OSPs could only review flagged-step comments through:

• The Status List comments column
• Email notifications

With this enhancement, users can now:

• View vetting comments directly inside the affected BCID application step
• Reply back to those comments directly within the step itself

This creates a more centralized communication flow between OSPs and the vetting team.

Important Note

These comments are best used to explain updates made inside the BCID application itself. If immediate assistance is required, users should continue opening Zendesk tickets, since comments are only reviewed when the vetting agent returns to the application.

Why this matters

This improves visibility around flagged items and reduces confusion during the BCID correction and resubmission process.

New Feature – BPO Registration & Submission Workflow

Sprint 2.5.2 introduced foundational support for BPOs (Business Process Outsourcing) within the BCID ecosystem and the NumHub platform.

OSP partners can now register BPO organizations directly through Deal Registration and allow those BPOs to submit BCID applications on behalf of enterprise customers.

5. BPO Registration & Automatic BPO ID Generation

When registering a new deal, OSPs can now identify the deal type as a BPO.

Once selected:

• The BPO receives an invitation to the OSP’s white-label portal
• The system automatically generates a unique BPO ID
• The BPO is automatically registered within the BCID ecosystem

Important Clarification

The BPO ID represents the BPO’s ecosystem-level identifier and is internally tied to a BPO EID.

After successful registration:

• OSPs can view the BPO ID directly inside the Deal Registration form
• API users will also receive the BPO ID in the API response payload for reference

Why this matters

This creates a scalable onboarding structure for partners managing multiple enterprise submissions through outsourced operational teams.

6. Parent ID, Deal ID, BPO ID & EID Relationship Logic

To avoid confusion across APIs, webhooks, and reporting, Sprint 2.5.2 introduces a standardized hierarchy for BPO-related submissions.

Relationship Structure

• Parent ID = Always the OSP
• Deal ID = The BPO Deal Registration record
• BPO ID = The BPO ecosystem identifier
• EID = The actual enterprise company submitted by the BPO

Important Clarification

Enterprise customers submitted by a BPO do not receive separate Deal IDs.

Instead:

• The BPO itself owns the Deal ID
• Each enterprise submitted by the BPO is identified through its own EID

This means webhook payloads and platform records will clearly identify:

• Which OSP owns the relationship
• Which BPO submitted the application
• Which enterprise company the BCID application belongs to

Why this matters

This standardization creates cleaner reporting, easier integration mapping, and more transparent ownership structures throughout the BCID ecosystem.

7. New “Submitted By” Tracking in Status List & Display Identity Views

To help OSPs better understand where BCID applications originate from, we added a new column called:

Submitted By

This logic now applies to both:

• Status List
• Display Identity views

Submission Logic

The platform will display:

• OSP Name → if the OSP submitted the BCID application
• Enterprise Name → if the enterprise submitted its own application
• BPO Name → if a BPO submitted the application

New Filters

Users can now filter records by:

• OSP Submitted
• Enterprise Submitted
• BPO Submitted

Why this matters

This gives OSPs significantly better visibility into who is actively submitting BCID applications and Display Identities within their ecosystem.

8. New BPO Portal Role & Access Permissions

A new user role type called:

BPO

has been added to the platform.

This role is automatically assigned when a Deal Registration is created using the BPO deal type.

BPO Portal Access

BPO users can now log into the white-label portal and access:

Branded Calling

• Dashboard
• Status List
• Display Identity

Reports

• Settlement Data

Users

• Users section

BPO users will only be able to view data associated with applications they submitted themselves.

Additional Visibility

Inside the portal, BPO users will now see:

• OSP ID
• BPO ID

displayed for easier ecosystem tracking.

Why this matters

This allows BPO organizations to independently manage BCID submissions while maintaining proper data separation and ecosystem ownership rules.

9. BPO-Specific BCID Application Workflow & LOA Support

BPO users can now submit BCID applications directly through the standard Step 1–7 workflow.

However, because BPOs submit applications on behalf of enterprise customers, the BCID ecosystem requires a different Letter of Authorization (LOA).

New BPO LOA Logic

The BPO-specific LOA confirms that the BPO:

• Has authorization to use the enterprise’s brand assets
• Can submit BCID applications on behalf of the enterprise
• Has permission to use associated logos and branding information

Vetting Process

Once submitted:

• The vetting workflow continues normally
• CX teams can flag steps as needed
• BPO users can resubmit corrected information
• Approved applications proceed through standard Display Identity generation

Why this matters

This enhancement aligns NumHub with BCID ecosystem requirements while supporting more advanced enterprise submission models.

10. BPO Support Across Display Identity & Reporting Workflows

Sprint 2.5.2 also expanded BPO support into downstream platform workflows.

Display Identity Enhancements

When Display Identities are generated from BPO-submitted BCID applications:

• The associated BPO ID is now tied to the Display Identity

This helps downstream systems and signing agents understand the Display Identity originated from a BPO-managed workflow.

Settlement Reporting

Settlement reports now include:

• BPO ID columns where applicable

allowing OSPs to better track activity and reporting associated with BPO-managed enterprises.

Webhook Payload Standardization

Webhook payloads were updated to standardize:

• Parent ID
• Deal ID
• BPO ID
• EID
• Company Name

Important Note

During this sprint, webhook payloads were updated first. API payload standardization will continue in future sprints.

Why this matters

This creates more consistent reporting, cleaner integrations, and improved ecosystem transparency for OSPs managing BPO relationships.

---

Why It Matters to You

• Better visibility into BCID applications after annual re-verification
• Cleaner webhook payload structures and ecosystem identifiers
• Stronger annual compliance workflows with updated documentation requirements
• Easier communication during flagged-step reviews
• New scalable BPO onboarding and submission capabilities
• Better tracking of who submitted BCID applications and Display Identities
• Improved reporting and ecosystem transparency for BPO-managed enterprises

---

Questions or Feedback

For questions about these updates or anything else related to the platform, please contact:

Daniela Villamar
[e-mail]