-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
[$1000] Create new library and native module react-native-wallet #36957
Comments
Job added to Upwork: https://www.upwork.com/jobs/~01e91e840e65f1cbba |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @akinwale ( |
Triggered auto assignment to @lschurr ( |
|
Hi @thienlnam how can I access issue? |
Hey @suneox, I copied what was relevant from the issue into this description |
Hey @thienlnam - are we just waiting for proposals on this one? |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Upwork job price has been updated to $1000 |
Updated the bounty since this is a more intensive - let's give it another week and then we can hand it to our expert contributors? cc @lschurr |
ProposalPlease re-state the problem that we are trying to solve in this issue.The problem identified is that users may find it unintuitive to manually input their virtual card details into the Apple Pay or Google Pay wallet apps. What is the root cause of that problem?New Feature What changes do you think we should make in order to solve the problem?The proposed solution is to create a new package that will handle the process of adding a Expensify NewDot Virtual Card to the Google Pay/Apple Pay Wallet by creating a new package that will return the necessary parameters and call native methods for adding the card to the wallet First we need to call native modules to fetch specific native variables:
Fetch return values:
What alternative solutions did you explore? (Optional)N/A Note: While I've outlined the proposed solution based on the current understanding of the problem and available resources, I'm open to exploring alternative approaches suggested by the team. |
Could you review the proposal @akinwale? |
Sorry, I can't answer your question. Unfortunately when it comes to permissions I cannot do much. |
This comment was marked as outdated.
This comment was marked as outdated.
Same as above :D |
I can generate an adhoc build on your PR which should allow this to get tested on an iOS device. Can you turn your branch into a draft PR?
I can get the answers to these - will DM you |
sweet. TY! |
This comment was marked as outdated.
This comment was marked as outdated.
I'll be OOO until May 6th |
Update: Continuing to gather iOS native calls this week |
Same as above :D |
Update: Keep working on iOS modules |
Update: Started structuring files for native Android modules |
Update: Keep working on native Android modules |
Update: Continue working on the local branch |
Update: Same as above. |
Update: Continue working on the local branch: https://github.com/brunovjk/Expensify-App/tree/feat/36957/modules/react-native-wallet |
Same as above |
📣 @Darren120! 📣
|
Update: Making progress on error handling, documentation, and unit tests. |
To support tokenization in NewDot which is adding a virtual card to Apple / Google Pay, we will need access to some native methods.
Problem:
Apple Pay and Google Pay are table stakes in the card market today. We support both of them for physical and virtual cards. Going forward, members will be able to access their virtual card details in NewDot. However, it isn't intuitive to know that you can copy your virtual card details, and manually key them into the Apple/Google wallet apps to tokenize your virtual card.
We're going to create a new package that will return the necessary parameters and call native methods for adding a card to the wallet
The endpoint we want to call is CreateDigitalWallet.
We will need to call native modules to fetch specific native variables to call CreateDigitalWallet
Then once we have the return values, we will call the native modules to add these to apple / google wallets
CreateDigitalWallet Summary
The parameters required for the new CreateDigitalWallet API/auth command are:
appVersion
walletAccountID
2.deviceID
certificates
2.nonce
3.nonceSignature
The return values for the new CreateDigitalWallet API/auth command are:
cardToken
opaquePaymentCard
2.userAddress
3.network
4.tokenServiceProvider
5.displayName
6.lastDigits
encryptedPassData
2.activationData
3.ephemeralPublicKey
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: