Bank Sync Connector Architecture

[rohitdash08]

Feature

Pluggable architecture for bank integrations.

Bounty

$500

Why This Matters

Foundation for future integrations.

Acceptance Criteria

• Connector interface
• Import & refresh support
• Mock connector included

[CattSabreJame]

And what is payment on this?

[rohitdash08]

@CattSabreJame $500 but the current focus is only for Indian banks

[CattSabreJame]

@rohitdash08 Are sandbox APIs or test credentials provided for Indian bank integrations, or is only a mock connector required for the bounty?

[CattSabreJame]

Hi maintainers,

I’d like to work on this bounty as well. I will implement the connector interface, import/refresh support, and provide a mock connector with clean architecture and documentation.

I’ll share progress updates and open a PR once ready.

Thanks!

[rohitdash08]

@CattSabreJame Most Indian banks don’t offer open sandbox access directly to individual developers, This bounty is not limited to a mock connector it should support real integrations via AA/API providers via partner portals.

[CattSabreJame]

@rohitdash08 Got it — so the “real integration” target is AA / API providers (via partner portals), not direct bank sandboxes.

To ensure I build the right pluggable architecture:

1. Which provider(s) should the first real connector target (e.g., an AA gateway/provider you’re already using), or should I implement a “generic AA provider connector” interface with one concrete provider adapter?
2. What auth/consent flow do you want supported in-app (redirect/OAuth, consent handle, webhook callback, polling)?
3. For acceptance: do you require a live end-to-end demo using provided partner credentials, or is a production-ready connector with documented setup + mocked tests sufficient?

I can implement the connector framework + Mock connector + one real provider connector skeleton immediately, and wire it so adding future providers is straightforward.

[rohitdash08]

I don't think you're still aligned @CattSabreJame ,

[CattSabreJame]

@rohitdash08 Understood — I am aligned.

I will deliver a pluggable connector architecture that supports REAL Indian bank data access via AA / API providers (partner-portal based), not just a mock.

Concrete deliverables for this bounty:

• BankConnector interface + connector registry (pluggable)
• Import + refresh sync with cursor/lastSync tracking
• One real AA/API-provider connector implementation wired through the framework (credentials via env/config; works end-to-end when partner creds are provided)
• Mock connector for local dev + CI tests
• Minimal docs: how to add a new provider connector + required env vars + how refresh/import works

To lock the “real” connector target: which AA/API provider should I implement first (the one you’re using / prefer)? If you don’t have a preference, I’ll pick a widely-used AA/API provider pattern and implement it so swapping providers is just a new adapter.

[lmee]

I reviewed "Bank Sync Connector Architecture" and read all comments before proposing a patch path.

Problem I see: Pluggable architecture for bank integrations.
Root-cause hypothesis: a stale-state race between optimistic updates and confirmed data.
Useful clue from comments: @rohitdash08 Are sandbox APIs or test credentials provided for Indian bank integrations, or is only a mock connector required for the bounty?.
First patch plan: reproduce the issue against acceptance criteria, isolate the root cause in the relevant module, and submit a focused fix with regression tests.
If this aligns with maintainer expectations, I will post repro evidence first and then open the scoped patch.

[CattSabreJame]

@rohitdash08 PR opened implementing pluggable connector architecture with import/refresh support, DB cursor tracking, mock connector, and AA provider connector skeleton compatible with partner portal integrations. All backend tests passing.

[taotao211]

Hi team,
I read through the task and I can take this on.
My understanding is: Feature Pluggable architecture for bank integrations. Why This Matters Foundation for future integrations. Acceptance Criteria - Connector interface - Import & refresh support - Mock connector included
I will reproduce the current behavior first, implement the change with a focused scope, and then share verification notes with a clean handoff.
If this direction works for you, I can start immediately.
Differentiation:

• I will provide short milestone updates and explicit verification notes.
• I will keep implementation scope focused to minimize regression risk.