Skip to content
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

Fix compliance action param #350

Merged
merged 5 commits into from
May 14, 2024
Merged

Fix compliance action param #350

merged 5 commits into from
May 14, 2024

Conversation

rosepuppy
Copy link
Contributor

@rosepuppy rosepuppy commented May 13, 2024

Compliance action param is based on wether or not user has a subaccount.

The original way of determining that was incorrect. It should be checked via the response of /v4/addresses. Use CONNECT if /v4/address returns a valid responsem, use ONBOARD otherwise.

Also support updated at as a compliance/geoblock response.

Updated the logic for both v1 and v2.

Tested E2E via a local build on staging and dev

@rosepuppy rosepuppy merged commit 9bddbe0 into main May 14, 2024
3 checks passed
@rosepuppy rosepuppy deleted the compliance-action-fix branch May 14, 2024 04:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants