Create Verification Status & Compliance API

[Kalchaqui]

Create Verification Status & Compliance API

Task Description

Develop a centralized Verification API responsible for exposing KYC and KYB verification status across the platform.

The API should become the single source of truth for compliance-related information.

---

Deliverable

Verification Status API.

---

Requirements

Expose verification information for:

• Individual users
• Organizations

Support queries such as:

• Is Verified?
• Verification Level
• Verification Expiration
• Verification Provider
• Last Updated

Return standardized compliance responses.

---

Technical Requirements

Suggested endpoints:

• GET /verification/user/:id
• GET /verification/business/:id

The API should aggregate information regardless of the underlying provider.

---

Additional Notes

This service will later be consumed by Agreements, Reputation, Enterprise APIs, and future marketplace integrations.

[Truphile]

Hi team, I’d love to take this on!

As a returning contributor, I’m already familiar with the repository workflow and setup. This is right up my field I’ve implemented very similar architectural patterns and requirements before.

I’ve reviewed the acceptance criteria and can deliver a clean, well-tested solution immediately. Ready for assignment!

[OpensrcLord]

Hello @maintainer, I understand the expected outcome and would love to work on this. I'll provide a solution that satisfies the acceptance criteria.

[josueazc]

Hi! I'd like to work on this issue.

I have experience designing and implementing REST APIs with a focus on clean architecture, standardized responses, and provider abstraction. My approach for this task would be to build the Verification Status API as a centralized source of truth that aggregates KYC/KYB verification data independently of the underlying provider.

The implementation would include:

GET /verification/user/:id
GET /verification/business/:id
Standardized compliance response models.
Support for verification status, level, expiration, provider, and last updated fields.
A provider-agnostic service layer to simplify future integrations and additional verification providers.

I'll ensure the API is well-structured, documented, and designed to support future consumers such as Agreements, Reputation, Enterprise APIs, and marketplace integrations.

I'd be happy to take this on.

[grantfox-oss]

🦊 GrantFox — @josueazc has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #74)
2. Your PR will be reviewed by the Thalos-Infrastructure maintainers

Good luck! Track your progress on GrantFox.

[ManuelJG1999]

🎉 Congratulations @josueazc ! This issue has been assigned to you.

Before you start, make sure you understand the requirements. If you have any questions, ask us in our community chat:
https://t.me/ThalosOSSCommunity

Please keep us updated on your progress. If there's no activity or communication within 48 hours, the issue may be reassigned to another contributor.

Happy coding, and thanks for contributing to Thalos! 🐉

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign | FWC26 campaign!

@josueazc's PR #85 was approved and merged by @Kalchaqui.

🏆 @josueazc: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (277 total points). Track your full progress on GrantFox.

👏 Great work, @josueazc! Keep contributing to Thalos-Infrastructure.