feat(partner): data model for Partner Integration Framework#500
Open
wealth4ever123 wants to merge 1 commit into
Open
feat(partner): data model for Partner Integration Framework#500wealth4ever123 wants to merge 1 commit into
wealth4ever123 wants to merge 1 commit into
Conversation
- Add partners table: business classification, onboarding states (sandbox/testing/verified/production), compliance tiers, tenant isolation - Add partner_profiles table: contact matrix, regulatory details - Add partner_api_credentials table: salted API key hashes (Argon2id), asymmetric public signing keys (Ed25519/RSA-2048/ES256), INET[] IP whitelists, webhook URL + HMAC secret hash - Add Rust models: PartnerEntity, PartnerProfile, PartnerApiCredential and DTOs (CreatePartnerRequest, IssueApiCredentialRequest, etc.) - Add repository methods for all three tables in PartnerRepository Closes kellymusk#466
|
@wealth4ever123 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes Fintech Partner API & Data Sharing Framework #469
Closes Remittance Partner Integration & White-label Support #468
Closes Performance SLA Management & Breach Response #465
Closes Partner Integration Framework & Onboarding Pipeline #466
PR Description — SLA Monitoring & Remittance Partner Infrastructure (#468 & #477)
Implemented foundational infrastructure for SLA monitoring and white-label remittance partner integrations in the aframp Rust backend.
SLA Monitoring Infrastructure
Added PostgreSQL schemas and migrations for:
sla_policiesto define latency, availability, throughput, and settlement thresholdssla_breach_eventsto track SLA violations, breach classifications, mitigation status, and penalty/refund metricsThis lays the groundwork for:
Remittance Partner & White-label Infrastructure
Added schemas and migrations for:
remittance_partnersto manage compliance metadata, settlement configs, and transaction limitswhitelabel_profilesfor custom domains, themes, logos, and notification settingspartner_fee_schedulesfor tiered pricing and corridor-specific fee rulesTechnical Details
Impact
Improves: