jairo094215_api

[frank olive]

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1218095975881642004

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[placid quartz]

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

• jairo_subscription-duplicate, 2 days ago, 25 messages

[random helm]

hello! you shouldn't be creating a PaymentMethod with raw card numbers. If you need a ready-made PaymentMethod, you can always pass in the pm_ objects listed https://stripe.com/docs/testing

[gray fern]

Ok, I know that there are some ready-made payment methods, but in this test I would like to create a new one to ensure our correct integration with Stripe's API

and the PaymentMethod API documentation don't says anything about this limitation

https://docs.stripe.com/api/payment_methods/create

In the example, you're showing the same plain card number that I'm using in my test

It means that this endpoint cannot be used in test mode? Or are there a way to send the card number correctly to avoid this error?

[random helm]

do you have a different account id which you're using in production where you're passing in raw card numbers?