feat(wallet/backend): add script for managed user and customer creation #1675
Conversation
github-actions
bot
added
package: wallet/backend
There was a problem hiding this comment.
Based on a discussion with Bogdan:
- when we create the managed user we want to add the payment pointer in the
metaobject.- if the user signs up and verifies the email, we can automatically create the payment pointer on our side with the correct value (i.e: 059)
waiting for response ^we can pass themetaobject when creating the managed user
- whitelisting: whenever someone tries to sign up, we fetch all managed users and we check if the email exists
- if the user exists, we can retrieve the payment pointer from the
metaobject and create the payment pointer - if the user doesn't exist: TBD
- if the user exists, we can retrieve the payment pointer from the
- Update ENV variables (DEV & PROD) - Fix API endpoints - Update types
packages/wallet/backend/migrations/20241008143459_add_customer_id_to_users.js
Show resolved
Hide resolved
| meta: Record<string, string> | ||
| ): Promise<void> { | ||
| const url = `${this.apiUrl}/auth/v1/users/managed` | ||
| const body = { meta } |
There was a problem hiding this comment.
This was the reason for the faulty meta object.
There was a problem hiding this comment.
Added a comment and updated the types for the meta object here: 930e750.
raducristianpopa
force-pushed
the
1667-cards-wallet-backend-customer-creation
branch
from
0599b2a
to
930e750
Compare
| ppNumber: string | ||
| } | ||
|
|
||
| const entries = `John;Doe;john@doe.com:8888 |
There was a problem hiding this comment.
is this for example porposes? can the list be read from an external file?
There was a problem hiding this comment.
This is how the entries should be added. It can be updated to read from an external file as well, but for simplicity reason we decided to just put the CSV contents directly in the variable.
| ) | ||
|
|
||
| const user = await gateHubClient.getWalletForUser(managedUser.id) | ||
| const walletAddress = user.wallets[0].address |
There was a problem hiding this comment.
should we use the default wallet created instead of creating on for each account?
There was a problem hiding this comment.
getWalletForUser retrieves the already created wallet - when the managed user is created. We are not creating another wallet here.
|
Latest changes look good @raducristianpopa, thank you! However, I think we can already rename |
Oh, yes! A lot better than keeping the card prefix there. |
Context
Changes
This PR adds the script for managed user and customer creation as well as the updated types and card ordering logic.