-
Notifications
You must be signed in to change notification settings - Fork 42
SDP-1619: Add /embedded-wallets/profile to pass verification info
#973
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: feature/c-accounts
Are you sure you want to change the base?
Conversation
|
stellar-disbursement-platform-backend-preview is available here: |
|
stellar-disbursement-platform-backend-preview is available here: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Discussed offline -- we're going to move the logic into a separate profile handler which will serve things like SEP-24 status as well as org logo, receiver info, supported assets, etc.
| AND p.type = $2 | ||
| AND p.status = ANY($3) | ||
| ORDER BY p.updated_at DESC | ||
| LIMIT 1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can there be multiple pending assets?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, there can be, but we only need one, and we don’t care which one the user verified with.
is_verification_pending and pending_asset to embedded wallet refresh token/embedded-wallets/profile to pass verification info
|
stellar-disbursement-platform-backend-preview is available here: |
|
stellar-disbursement-platform-backend-preview is available here: |
|
stellar-disbursement-platform-backend-preview is available here: |
| embeddedWalletModel := EmbeddedWalletModel{dbConnectionPool: dbConnectionPool} | ||
|
|
||
| DeleteAllEmbeddedWalletsFixtures(t, ctx, dbConnectionPool) | ||
| defer DeleteAllEmbeddedWalletsFixtures(t, ctx, dbConnectionPool) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we also DeleteAllReceiversFixtures?
| }) | ||
| } | ||
|
|
||
| func (e *EmbeddedWalletService) GetReceiverWalletByContractAddress(ctx context.Context, contractAddress string) (*data.ReceiverWallet, error) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: We can make this function private since it's only used by isVerificationPending.
| }) | ||
| } | ||
|
|
||
| func (e *EmbeddedWalletService) IsVerificationPending(ctx context.Context, contractAddress string) (bool, error) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This function needs a test.
What
/embedded-wallets/profileto passis_verification_pendingandpending_assetto FEclientAttributionRequiredcheck during SEP-45 challenge creationWhy
is_verification_pendingandpending_assetare needed for FE to initiate the SEP-24 deposit flowclientAttributionRequiredis temporarily removed due to blocking the FE’s SEP‑45 flow:Sep10ClientAttributionRequired, defaulting to true.client_domainbecause it’s self hosted inside SDP, there’s no separate client domain TOML or signing key to reference.Known limitations
N/A
Checklist
SDP-1234: Add new featureorChore: Refactor package xyzformat. The Jira ticket code was included if available.CHANGELOG.mdis updated (if applicable)