Skip to content
This repository has been archived by the owner on Mar 27, 2021. It is now read-only.

Error with Card Split-field Form #146

Closed
MathieuAllegorithmic opened this issue Jan 10, 2018 · 8 comments
Closed

Error with Card Split-field Form #146

MathieuAllegorithmic opened this issue Jan 10, 2018 · 8 comments

Comments

@MathieuAllegorithmic
Copy link

MathieuAllegorithmic commented Jan 10, 2018

I've got an error when I'm using the card split-field form on the JSFiddle demo.

error: {type: "invalid_request_error", message: "Missing required param: card[exp_month].",…} message: "Missing required param: card[exp_month]." param: "card[exp_month]" type:"invalid_request_error"

@sauldhernandez
Copy link

Getting the same error here.

@yegortokmakov
Copy link

yegortokmakov commented Jan 10, 2018

rolling back to 1.2.x might solve the issue.

in release 1.3 there is a change allowing to provide a custom instance of Stripe to Stripe provider:
https://github.com/stripe/react-stripe-elements/tree/v1.3.0#using-an-existing-stripe-instance

which, in case of not providing it, leads to Unrecognized Stripe() parameter: stripe is not a recognized parameter. This may cause issues with your integration in the future.

@yegortokmakov
Copy link

we are using injectStripe to get initialized an instance of Stripe if it helps.

can it be related to a new prop stripe = null which ends up in options here? v1.2.1...v1.3.0#diff-ac604848eeadb1baa24313a33b809514R93

@michelle
Copy link
Collaborator

Hi! Sorry for the confusion. We’re rolling back 1.3.0 right now, and will investigate these issues.

@michelle
Copy link
Collaborator

@yegortokmakov your issue sounds different from the expiry issue. What properties are you passing to StripeProvider? Does your integration work in 1.2.X?

@sauldhernandez
Copy link

Rolling back to 1.2.0 fixed this issue for me.

@michelle
Copy link
Collaborator

1.3.0 is now unpublished, and a fresh install should get you 1.2.1. We’re working on rolling 1.3.1 with the bug fixes ASAP. Sorry for the inconvenience.

@jez
Copy link
Collaborator

jez commented Jan 10, 2018

This should be fixed now in v1.3.1. Again, sorry for the inconvenience.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants