Hi there, when I try to make a payment on my own page I get this: “No such customer: cus_GCc5lTdNnQH9AR”. That happens as well in test mode but only with name/credit cards I used before. When I use a name/credit card that I never used it works ok (in test mode).
I use Stripe gateway.
I tried deleting all customer ids in Stripe Dashboard but still happens that error.
A friend of mine tried to buy something and it worked, but it was the first buy at my webpage. So, I dont know if old customers can place an order…
What can it be happening?
The page I need help with: [log in to see the link]
This is the exact message I get: No such customer: cus_GKXYCHDNmRtJnZ; a similar object exists in test mode, but a live mode key was used to make this request.
I’ve found your related ticket at WooCommerce.com, where it was recommended that you ask on the forums. I see that you’re asking in the WooCommerce Stripe forum – I’d like to know a bit more about your site.
Could you please share a copy of your site’s System Status? You can find it via WooCommerce > Status.
Select “Get system report” and then “Copy for support”. Once you’ve done that, paste it here in your response.
I’d recommend including that whenever asking for help. It’ll give context and may help you get help faster as people will understand which plugins you’re using.
Our internal reference for the ticket: 2548158-zen
- This reply was modified 2 years, 8 months ago by Hannah S.L. a11n. Reason: Added Zendesk ticket number for cross-referencing
Thanks Hannah. Here’s the report:
### WordPress Environment ### WordPress address (URL): https://mamafermenta.com Site address (URL): https://mamafermenta.com WC Version: 3.8.1 REST API Version: ✔ 1.0.2 Log Directory Writable: ✔ WP Version: 5.3.1 WP Multisite: – WP Memory Limit: 1 GB WP Debug Mode: – WP Cron: ✔ Language: es_ES External object cache: – ### Server Environment ### Server Info: Apache PHP Version: 7.3.12 PHP Post Max Size: 128 MB PHP Time Limit: 14400 PHP Max Input Vars: 20000 cURL Version: 7.62.0 OpenSSL/1.0.2k SUHOSIN Installed: – MySQL Version: 5.5.5-10.1.41-MariaDB-cll-lve Max Upload Size: 64 MB Default Timezone is UTC: ✔ fsockopen/cURL: ✔ SoapClient: ✔ DOMDocument: ✔ GZip: ✔ Multibyte String: ✔ Remote Post: ✔ Remote Get: ✔ ### Database ### WC Database Version: 3.8.1 WC Database Prefix: wp_ Tamaño total de la base de datos: 15.39MB Tamaño de los datos de la base de datos: 13.39MB Tamaño del índice de la base de datos: 2.00MB wp_woocommerce_sessions: Datos: 0.18MB + Índice: 0.01MB + Motor MyISAM wp_woocommerce_api_keys: Datos: 0.00MB + Índice: 0.00MB + Motor MyISAM wp_woocommerce_attribute_taxonomies: Datos: 0.00MB + Índice: 0.00MB + Motor MyISAM wp_woocommerce_downloadable_product_permissions: Datos: 0.00MB + Índice: 0.00MB + Motor MyISAM wp_woocommerce_order_items: Datos: 0.03MB + Índice: 0.01MB + Motor MyISAM wp_woocommerce_order_itemmeta: Datos: 0.10MB + Índice: 0.08MB + Motor MyISAM wp_woocommerce_tax_rates: Datos: 0.00MB + Índice: 0.01MB + Motor MyISAM wp_woocommerce_tax_rate_locations: Datos: 0.00MB + Índice: 0.00MB + Motor MyISAM wp_woocommerce_shipping_zones: Datos: 0.00MB + Índice: 0.00MB + Motor MyISAM wp_woocommerce_shipping_zone_locations: Datos: 0.00MB + Índice: 0.00MB + Motor MyISAM wp_woocommerce_shipping_zone_methods: Datos: 0.00MB + Índice: 0.00MB + Motor MyISAM wp_woocommerce_payment_tokens: Datos: 0.00MB + Índice: 0.00MB + Motor MyISAM wp_woocommerce_payment_tokenmeta: Datos: 0.00MB + Índice: 0.00MB + Motor MyISAM wp_woocommerce_log: Datos: 0.00MB + Índice: 0.00MB + Motor MyISAM wp_commentmeta: Datos: 0.31MB + Índice: 0.25MB + Motor InnoDB wp_comments: Datos: 0.30MB + Índice: 0.13MB + Motor InnoDB wp_et_bloom_stats: Datos: 0.22MB + Índice: 0.00MB + Motor InnoDB wp_et_social_stats: Datos: 0.00MB + Índice: 0.00MB + Motor MyISAM wp_ewwwio_images: Datos: 0.00MB + Índice: 0.00MB + Motor MyISAM wp_failed_jobs: Datos: 0.00MB + Índice: 0.00MB + Motor MyISAM wp_hugeit_slider_slide: Datos: 0.00MB + Índice: 0.00MB + Motor MyISAM wp_hugeit_slider_slider: Datos: 0.00MB + Índice: 0.00MB + Motor MyISAM wp_huge_itslider_images_backup: Datos: 0.00MB + Índice: 0.00MB + Motor MyISAM wp_huge_itslider_params_backup: Datos: 0.00MB + Índice: 0.00MB + Motor MyISAM wp_huge_itslider_sliders_backup: Datos: 0.00MB + Índice: 0.00MB + Motor MyISAM wp_imgoptimizations: Datos: 0.30MB + Índice: 0.03MB + Motor MyISAM wp_imgoptimizeractions: Datos: 0.04MB + Índice: 0.02MB + Motor MyISAM wp_iwp_backup_status: Datos: 0.02MB + Índice: 0.00MB + Motor InnoDB wp_links: Datos: 0.02MB + Índice: 0.02MB + Motor InnoDB wp_mailchimp_carts: Datos: 0.00MB + Índice: 0.00MB + Motor MyISAM wp_odb_logs: Datos: 0.00MB + Índice: 0.00MB + Motor MyISAM wp_options: Datos: 2.50MB + Índice: 0.14MB + Motor InnoDB wp_postmeta: Datos: 2.52MB + Índice: 0.69MB + Motor InnoDB wp_posts: Datos: 6.47MB + Índice: 0.27MB + Motor InnoDB wp_queue: Datos: 0.00MB + Índice: 0.00MB + Motor MyISAM wp_rp4wp_cache: Datos: 0.06MB + Índice: 0.00MB + Motor InnoDB wp_termmeta: Datos: 0.02MB + Índice: 0.03MB + Motor InnoDB wp_terms: Datos: 0.02MB + Índice: 0.03MB + Motor InnoDB wp_term_relationships: Datos: 0.06MB + Índice: 0.05MB + Motor InnoDB wp_term_taxonomy: Datos: 0.02MB + Índice: 0.03MB + Motor InnoDB wp_tm_taskmeta: Datos: 0.00MB + Índice: 0.01MB + Motor MyISAM wp_tm_tasks: Datos: 0.00MB + Índice: 0.00MB + Motor MyISAM wp_usermeta: Datos: 0.08MB + Índice: 0.06MB + Motor InnoDB wp_users: Datos: 0.02MB + Índice: 0.05MB + Motor InnoDB wp_wc_download_log: Datos: 0.00MB + Índice: 0.00MB + Motor MyISAM wp_wc_product_meta_lookup: Datos: 0.00MB + Índice: 0.01MB + Motor MyISAM wp_wc_tax_rate_classes: Datos: 0.02MB + Índice: 0.02MB + Motor InnoDB wp_wc_webhooks: Datos: 0.00MB + Índice: 0.00MB + Motor MyISAM wp_xcloner_scheduler: Datos: 0.00MB + Índice: 0.00MB + Motor MyISAM wp_yoast_seo_links: Datos: 0.06MB + Índice: 0.02MB + Motor MyISAM wp_yoast_seo_meta: Datos: 0.02MB + Índice: 0.03MB + Motor MyISAM ### Security ### Secure connection (HTTPS): ✔ Hide errors from visitors: ✔ ### Active Plugins (19) ### Akismet Anti-Spam: por Automattic – 4.1.3 Autoptimize: por Frank Goossens (futtta) – 2.5.1 Bloom: por Elegant Themes – 1.3.10 Comet Cache: por WP Sharks – 170220 Cookie Notice: por dFactory – 1.2.48 Heartbeat Control by WP Rocket: por WP Rocket – 2.0 Kadence WooCommerce Email Designer: por Kadence WP – 1.3.6 – No probado con la versión activa de WooCommerce Monarch Plugin: por Elegant Themes – 1.4.12 Quick Featured Images: por Martin Stehle – 13.3.6 Optimize Database after Deleting Revisions: por CAGE Web Design | Rolf van Gelder Eindhoven The Netherlands – 4.8.8 optimizador.io: por David Noguera (webempresa.com) – 1.0.22 Checkout Field Editor for WooCommerce: por ThemeHigh – 1.3.9 – No probado con la versión activa de WooCommerce WooCommerce Stripe Gateway: por WooCommerce – 4.3.1 – No probado con la versión activa de WooCommerce WooCommerce Services: por Automattic – 1.22.2 – No probado con la versión activa de WooCommerce WooCommerce: por Automattic – 3.8.1 Yoast SEO: por Equipo Yoast – 12.7.1 CiberProtector — Protección 2FA + VPN: por webempresa.com – 0.0.1 WP Comment Policy Checkbox: por Fco. J. Godoy – 0.3.2 WP-Optimize - Clean, Compress, Cache: por David Anderson Ruhani Rabin Team Updraft – 3.0.14 ### Inactive Plugins (0) ### ### Dropin Plugins (1) ### advanced-cache.php: advanced-cache.php ### Settings ### API Enabled: – Force SSL: – Currency: EUR (€) Currency Position: right Thousand Separator: . Decimal Separator: , Number of Decimals: 2 Taxonomies: Product Types: external (external) grouped (grouped) simple (simple) variable (variable) Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog) exclude-from-search (exclude-from-search) featured (featured) outofstock (outofstock) rated-1 (rated-1) rated-2 (rated-2) rated-3 (rated-3) rated-4 (rated-4) rated-5 (rated-5) Connected to WooCommerce.com: ✔ ### WC Pages ### Base de la tienda: #3534 - /tienda/ Carrito: #3535 - /carrito/ Finalizar compra: #3536 - /finalizar-compra/ Mi cuenta: #3537 - /mi-cuenta/ Términos y condiciones: #3622 - /condiciones-generales-de-contratacion/ ### Theme ### Name: Divi Child Version: 0.1.1 Author URL: http://elegantthemes.com Child Theme: ✔ Parent Theme Name: Divi Parent Theme Version: 4.0.9 Parent Theme Author URL: http://www.elegantthemes.com WooCommerce Support: ✔ ### Templates ### Overrides: – ### Action Scheduler ### Complete: 0 Oldest: – Newest: – Pending: 0 Oldest: – Newest: – Canceled: 0 Oldest: – Newest: – In-progress: 0 Oldest: – Newest: – Failed: 0 Oldest: – Newest: –
Thanks for sharing that!
You can respond to the ticket from WooCommerce.com with this status log – it shows that you’re using our Stripe plugin, which means that we’ll be happy to help you out. In general, responses will be faster as well having the option to ask you for login credentials if that’s needed. Please also include the URL to this thread, so my fellow colleagues will be able to see what’s been said.
If you prefer, though, we can continue through the forums — in that case, here’s the next step.
This message indicates that WooCommerce and the Stripe plugin have correctly stored the customer ID in the database, but the Stripe API is returning that error. Have you made any changes to your Stripe account? Did you switch Stripe accounts at all lately?
Silly question, but are you positive that the Stripe account you’re logging into is tied to the Stripe account within WooCommerce? It’s worth double-checking that the API keys match, particularly if you recently switched Stripe accounts or migrated data between Stripe accounts.
Hi Hannah, I opened a ticket in woocommerce.com but they told me they can’t help because I’m not a Premium customer. You tell me to answer the ticket I opened in Woocommerce.com? I think they will not help. Maybe I don’t understand you Hannah sorry for my english.
I don’t think I made any changes to Stripe.
The API keys I see at Stripe Dashboard must match with the ones I’ve got at Stripe plugin at WordPress? They don’t match. Can you tell me more about that? Sorry for my little experience… There are two API keys isn’t it? Secret and public, both must match?
By the way, is it better to move this thread to another forum?
Hey there Jordi!
The API keys will not be the same (between the two different key types), but they 2 keys in Stripe should match the 2 keys in your WooCommerce site.
Typically we see your error show up when a customer has ordered when the site was using stripe in test mode, and then switched to be in live mode.
You will need to remove the customer profiles in your WooCommerce site. If it’s only your account that used the testing cards and saved to your profile, then you can do this from the frontend of your site in your “My Account” page. Just remove the saved card there, and you should no longer see the issues.
Hopefully that helps! Have a great one!
I’ve changed the API keys at Woocommerce plugin, they weren’t matching.
I’ve checked the users at Woocommerce/reports and I didn’t see the customers wich cant place an order. So I’m not on that list, kind of weird because sometimes I place orders to check, so… I dont know what to say. Just for your info: customers dont have to register. A friend of mine who never placed an order did it and it worked so new customers can do it…
Thanks a lot
Hey there @mamafermenta,
Let’s move this to a ticket for more hands-on support. I’ve responded to you via the ticket that you created.
I am struggling with the same issue but can’t seem to find a solution online or the root cause. I get this error from the check out page. “No such customer: cus_FfknSQLX2rH4Fe; a similar object exists in test mode, but a live mode key was used to make this request.” In test mode I do not get the error. I worked with tech support on the server and removing the check out pages from the server cache seemed to work for several weeks. Many order went through, then the problem came back. Got back on with tech support and they have ruled that it is a browser cache issue as private browsing windows allow the transaction to go through. I have built several websites with woo commerce and a stripe and this is the first problem I’ve had. Please help!
Hi i have the same issue. No such customer: cus_GKUBlKEfd2cCdg
I found by signing out of my site and using a new email address did the the trick under test mode.
I am having the same issue. I deleted the test user at Stripe. I created a new wordpress admin user and deleted the suspected wordpress admin user and it fixed the issue…. but it caused another issue with another handshake I have in wordpress. I have been comparing the working database and the non working. I found one instance of the customer in the working database and 2 instances of the customer in the non working database. I think 1 of the instances needs to be deleted but I am not sure what is tied to the one I am suspect of. If I could get some help discovering which to delete from my database, that would be great.
Any solutions to this? I can’t seem to figure out the solution on my end. Decreased the chances of customers winning is the only current solution…
- This reply was modified 2 years, 5 months ago by Team Conectar.
We recently ran into a similar issue. Instead of switching between test/live, we had switch to a different stripe account.
Our new stripe account did not have any customers in it, but some of our woocommerce customers had placed orders on our old stipe account and had stripe customer id’s already registered.
The solution that we found was to clear the wordpress database of those _stripe_customer_id from the wp_usermeta table:
DELETE * FROM
You also want to make sure that those customers are not in your stripe account.
After we cleared these fields from the wordpress database, customers were immediately able to place orders with stripe.
I hope this information helps.
- The topic ‘No such customer: cus_GCc5lTdNnQH9AR’ is closed to new replies.