Evaluate sanctions and geoblocking compliance requirements for remittance-flagged jurisdictions

[phertyameen]

Location

frontend/ (any access-control middleware), docs/compliance.md (new)

Problem

Cross-border remittance and aid-disbursement use cases can trigger sanctions-compliance obligations (e.g. OFAC-equivalent restrictions) depending on the jurisdictions involved; no confirmed review or middleware exists addressing whether any geoblocking, IP-based restriction, or explicit compliance disclaimer is needed before this product is used for real cross-border transfers at scale.

Acceptance Criteria

• Legal/compliance requirements for the jurisdictions this product is realistically expected to serve are researched and documented, even if the conclusion is 'no blocking needed at current scale, revisit before wider launch'
• Any required restriction is implemented at the appropriate layer (frontend, bridgelet-sdk, or both) rather than left unaddressed
• Explicitly flagged as a legal question requiring non-engineering input, not something to resolve unilaterally in code without that review

[Sensei-Victor]

@Sensei-Victor has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Please assign so I can work on this

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