SPIKE - Investigate Postal Code Availability via SBC Connect from BC Services Card Account

[mbertucci]

Spike

Objective:
The objective of this spike is to determine whether the BC Services Card Account, accessible via SBC Connect, currently provides us with the user's postal code. We need to understand what specific data is available through the API, particularly focusing on whether the postal code is included, even if the full address is not. This information will help us assess the feasibility of using this data to run automatic approval logic.

We use the Host address and compare it to the rental address if they are the same then there is a higher likelyhood that the str is in their principal residence. This is the first step in Provisional approval process https://miro.com/app/board/uXjVKQlO-ME=/?moveToWidget=3458764591407730831&cot=14

Context:
To run automatic approvals we are exploring the possibility of automatically retrieving the user's postal code from the BC Services Card Account via SBC Connect. However, before proceeding, we need to confirm whether this data is accessible through the API and what specific information we can currently access.

Research Questions

1. Data Availability:

   • Does the BC Services Card Account currently provide us with the user's postal code via SBC Connect?
   • What specific data fields are accessible through the SBC Connect API, and is the postal code among them?
   • If the postal code is not currently available, what are the reasons for its exclusion, and is there potential for future access? We are not to pursue further conversations with BC Services Card at this time. Until we hear back from Kaine on the matter. We may have the answer to this soon.

2. Existing Data Usage:

   • What specific data are we currently retrieving from the BC Services Card Account via SBC Connect?

3. Integration with other systems:

   • What API or data exchange methods does SBC Connect provide for accessing postal code information, if available?
   • Are there any technical constraints or requirements that we need to consider for retrieving postal codes through the API?

4. Regulatory Compliance:

   • What are the legal or regulatory implications of accessing postal code information from the BC Services Card Account?
   • How does this align with FOIPPA and other relevant privacy regulations, particularly regarding the use of postal codes as non-identifiable data?

Expected Outcomes

• A clear understanding of whether the BC Services Card Account provides postal code information via SBC Connect.
• A detailed list of the data fields currently accessible through the SBC Connect API, with a focus on postal codes.
• Are there any other APIs that we can tap in to for Address and Postal Code
• An assessment of the technical feasibility of integrating postal code retrieval into our application if available.
• Recommendations on whether to pursue further development based on the availability and accessibility of postal code data.

Timebox

This spike will be timeboxed to [insert duration here, e.g., "one week"]. During this time, the team will gather the necessary information, conduct any necessary discussions with stakeholders, and document the findings.

Deliverables

• A report summarizing the findings of the spike, including answers to the research questions.
• Documentation of the data fields currently accessible through the SBC Connect API, particularly focusing on postal codes.
• Recommendations on next steps, including potential blockers or challenges identified during the spike.

Additional Considerations

• User Experience: If postal codes are available, consider how they could enhance the user experience by reducing manual entry and improving data accuracy.
• Collaboration: Engage with Service BC and SBC Connect technical teams to ensure alignment and obtain necessary support or documentation.
• Future Development: If postal codes are not currently accessible, consider documenting potential future enhancements that could enable this capability.

[mbertucci]

I am going to close this spike and then copy it to create a new story for the PO Backlog.

I believe we determined that we can do what we need but need to revisit the form on whether or not we want to make any changes.