craftcms/commerce-stripe

Live environment fails when test customer is used

Closed this issue · 7 comments

ryssbowh commented

Description

We have a website just gone live (migrated from Craft 3) where payments are failing for admin users. Those users have been making payments on the dev version of the website and in Stripe they are linked to a test environment. Stripe complains :

Could not fetch Stripe customer: No such customer: 'cus_Ge1tS7lpPzAWCK'; a similar object exists in test mode, but a live mode key was used to make this request

The only thing I can do is deleting the record in the stripe_customers table and it fixes the issue.

Shouldn't stripe customers be environment aware ? or should we have a way to delete those references in Craft itself ?

Thank you

Steps to reproduce

  1. Make a payment on a dev site in a Stripe test environment
  2. Make a payment on the live version of the dev site in a Stripe production environment

Additional info

  • Craft CMS version: 4.12.1
  • Stripe for Craft Commerce version: 4.1.5
  • PHP version: 8.2
  • Database driver & version:
  • Plugins & versions:
ryssbowh commented

This is also an issue when trying to save payment methods using craft\commerce\controllers\PaymentSourcesController::actionAdd

sm9 commented

Hi, we have also just run into this issue. We're using Craft 4.10.2, Commerce 4.6.4, Stripe for Craft Commerce 4.1.5, and PHP 8.1.29.

User accounts that have placed orders on the staging site and Stripe test mode previously are showing the error that @ryssbowh has reported above on the live site in Stripe live mode.

Is carrying out the suggested fix above safe, and also what @lukeholder recommends doing as a workaround for now? Or is a proper fix imminent?

The only thing I can do is deleting the record in the stripe_customers table and it fixes the issue.

Thanks,

Stephen

teachmeter commented

This is also an issue when you remove the customers from the test environment on Stripe and using Live Keys.
The error then becomes No such customer: 'cus_AABBCCDDEE'

I think a simple solution would be to store in the stripe_customers table some kind of md5 with the keys used which could be quickly calculated before getting the information from the db.
THis would allow to have multiple identity per keypair for a user aka env switch.

Switching then back and forth would also not require any adjustments in the stripe environment.

nfourtythree commented

Hi all

This is a common issue with carrying over test data into the live environment as the data that is stored in Stripe is completely separate.

If you are importing data into your production site when you are about to go live it is wise to use the craft commerce-stripe/reset-data data command to remove all Stripe references to the test environment.

This is also a useful command when pulling a production DB to work on locally, you can run the command on your local dev to remove the references to the live Stripe environment.

Hope this helps, thanks!

  • 👍1
sm9 commented

Hi Nathaniel, thanks for posting back about this.

What is the best way to remove test Stripe data from a live database, without wiping live data? As an example, we have a client that had a front-end rebuild and was using a private 'beta' version of the website for testing, prior to launch. We weren't aware of the craft commerce-stripe/reset-data command at that time. So we've ended up in a situation where we're running into this error when the client uses their own account on the live site (as they used their own account when testing the private beta).

The original poster said in the first message:

The only thing I can do is deleting the record in the stripe_customers table and it fixes the issue.

Is this the best workaround to use in our situation? I just wanted to double-check before deleting anything from the database, in case there were any knock-on effects to this that we weren't aware of.

Thanks.

nfourtythree commented

Hi @sm9

Thank you for your reply!

Unfortunately, with the project being in this state it will be a case of identifying the customers with the invalid Stripe customer numbers and removing them from the stripe_customers table (as mentioned previously). I assume this will only be for those users that were using it in test mode and therefore there won't be too many of them.

I would try it with one you know for sure and then test the system before doing any further records. If you have access to live Stripe dashboard you can also take the customer identifier from the reference column in that table and use the search bar to see if that record exists.

Do you have an idea of how many users are affected by this?

Thanks!

  • 👍1