Anchor KYC Status Verification Service

[Haroldwonder]

Create a service that:

Polls anchor KYC status endpoint

Stores verification status (pending / approved / rejected)

Updates user profile in DB

Prevents transfers if KYC not approved

Must support:

Multiple anchors

Token-based authentication

Goal: Sync frontend KYC UI with real backend verification.

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[daveades]

@daveades has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Good Day,

I’ve reviewed Issue #168 – Anchor KYC Status Verification Service in the SwiftRemit repository.

The goal is clear: implement a backend service that polls anchor KYC status endpoints, persists verification state (pending/approved/rejected), updates the user profile in the database, and blocks transfers unless KYC is approved—while supporting multiple anchors and token-based authentication.

I’m confident I can implement this in a clean and scalable way by:

• Designing a multi-anchor integration layer that:

  • Registers multiple anchors and their KYC status endpoint configurations
  • Supports per-anchor token-based authentication and secure token storage/rotation practices where applicable

• Implementing a polling job (or webhook-first with polling fallback if the architecture supports it) that:

  • Fetches KYC status for relevant users
  • Normalizes anchor-specific responses into a consistent internal status model (pending/approved/rejected)
  • Persists status and last-checked metadata for auditing/debugging

• Updating user profiles in the DB based on the normalized status

• Enforcing transfer gating so transfers are rejected when KYC is not approved, with clear error messaging for the frontend

• Adding tests that cover:

  • Multi-anchor routing and auth handling
  • Status transitions and DB updates
  • Transfer blocking behavior for pending/rejected users

I will keep the implementation modular so new anchors can be added without refactoring core logic, and ensure the frontend can reliably reflect backend verification status.

I’d appreciate being assigned this issue and can begin immediately.

Thank you for your consideration.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @daveades to this issue.

[Jayydy]

@Jayydy has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hello, i would like to handle this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Jayydy to this issue.

[drips-wave]

Congratulations, @Jayydy! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on February 26, 2026.

🧑‍💻 @Jayydy: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are issued when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊