rhuzaifa_api | Stripe Developers | Page 1

tawny domeBOT Mar 17, 2025, 1:05 PM

#

👋 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/1351179702001205289

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

#

spare frost Mar 17, 2025, 1:08 PM

#

Hi, we discourage automation testting and document here that you should instead simulate our API: https://docs.stripe.com/automated-testing

shy nexus Mar 17, 2025, 1:11 PM

#

Hi, thanks for taking a look.

Actually, I am using stripe fixtures via CLI for testing (which is recommended i believe?), and some apis for testing like the doc you linked mentions.

spare frost Mar 17, 2025, 1:17 PM

#

I see, the behavior you see is expected: https://docs.stripe.com/testing?testing-method=card-numbers

0341 should fail as documented above. Upgrading/ downgrading causes prorations: https://docs.stripe.com/billing/subscriptions/upgrade-downgrade to charge for the difference between the plan and to account for unused time.

#

Can you tell me more about why you expect this to not fail before step 10 for card 0341?

shy nexus Mar 17, 2025, 1:19 PM

#

ok, Now I understand, it's not failing because of the prorated amount for the customer, which hasn't refunded yet.

#

this is honesty so silly on my end. Thanks @spare frost for the help.

#rhuzaifa_api