Support Dashlane Payment method autofill
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- android, react-native, typescript
Research direction
Start by reproducing the issue with the CardField component on Android 10 using Dashlane autofill, then inspect the onCardChange result after autofill. Confirm that brand, last4, and complete are populated and that a setup intent no longer reports "Card details not complete."
Written by the indexing model from the issue text.
Description
Describe the bug
I'm using the CardField component to let the users enter their credit card information. With a payment manager installed on Android, like Dashlane for example, you can autofill the credit card information.
All the fields seem well filled. But in fact, in the object, the last4 and the brand attributes are missing, and the completed attribute is false. If I try to do a setup intent, I'm getting the error "Card details not complete".
To Reproduce
Steps to reproduce the behavior:
- Install a payment method manager (ex: Dashlane) on an Android phone and configure a payment method.
- Set Dashlane as the autofill service you want to use on your phone
- Open your app with a CardField component, and autofill your payment information thanks to Dashlane
- All the fields are fulfilled, but if you try to do a setup intent then you will get the error "Card details not complete"
Expected behavior
When auto-filling the credit card method, all the information should be saved and the onCardChange function should return an object with all the attributes fulfilled.
Screenshots



LOG {"brand": null, "complete": false, "expiryMonth": 11, "expiryYear": 34, "last4": null}
Desktop (please complete the following information):
- OS: macOS Big Sur v11.5.2
Smartphone (please complete the following information):
- Device: OnePlus 6T
- OS: Android 10 - OxygenOS 10.3.9
Additional context
@stripe/stripe-react-native: v0.2.3
- Dominant language
- TypeScript
- Stars
- 1.4k
- Forks
- 328
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 23
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from stripe/stripe-react-native
-
[Bug] @stripe/stripe-react-native@0.52.0-crypto-onramp-2-private-beta.4 Swift-generated header bug Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
stripe/stripe-react-native#2547 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
stripe/stripe-react-native#2546 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
stripe/stripe-react-native#2661 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
stripe/stripe-react-native#2660 · 1 comment · 2 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
stripe/stripe-react-native#2637 ·
All issues in stripe/stripe-react-native
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·