GET /user/onboarding as usual. There is no migrated flag to check.
What changes for a user ?
When a user comes to V2 endpoint, Gnosis Pay infra recognises the user as an existing v1 customer, their identity verification is carried over to v2 and they are moved forward in the flow, skipping the steps they have already completed.What the user goes through
1
Sign in with the right wallet
The user authenticates with SIWE. Recognition is based on the wallet address, so it must be a wallet that currently owns their existing Safe. This wallet becomes the only wallet the user can sign in with and the sole owner of the new account. It cannot be changed later.
2
Verify email and register
The user completes email OTP verification and registers through
POST /user. This is the only point where recognition happens. If the user registers with a wallet that is not recognised, they are treated as a new customer and cannot be migrated afterwards.3
Accept the Terms of Service (action_accept_tos)
This step is always required. The terms have been updated, so earlier acceptance does not carry over.
4
Wait for verification to transfer (waiting_kyc_setup)
Continue polling as normal. Gnosis Pay transfers the existing verification data asynchronously. It is usually quick, but you should not rely on a fixed duration.
5
KYC and Source of Funds, usually skipped
The user skips
action_complete_kyc entirely and never needs to open the KYC provider again. They also skip action_complete_sof if their previous answers still match the current questionnaire. If they do not, the user fills in the questionnaire as usual. Support both outcomes and let the polled status guide the flow instead of hardcoding the skip.6
Create the account, verify phone, and create a card
From here, the flow is identical to onboarding a new user. The user creates their account, a new Safe is deployed, and phone verification applies if you require it.