crackajax

To be clear, it is not just a generic appendage of “wp_” to the old _stripe_customer_id key, but it is actually an appendage of the database prefix to the old key.

@dougaitken thanks for getting back to me. The cron job will run again overnight and I hope to resolve this for my client.

But, I want to be clear, that the issue regarding the token is strictly the plugin code and not affected by any other customization outside of the filter: add_filter( ‘wc_stripe_force_save_source’, ‘__return_true’ ); The custom code creates and charges orders in a script that only runs on the 1st day of the month via a cron job.

That being said, I deactivated ALL plugins except Woocommerce and Woocommerce Stripe and activated the Twenty Twenty theme just to be sure. I added the filter: add_filter( ‘wc_stripe_force_save_source’, ‘__return_true’ ); to the top line of the Twenty twenty functions.php file as the only customization in the system. With this minimal setup, I created an order with my Stripe sandbox settings to test. The transaction does go through and I can see the user in my Stripe Test Data, but it did not save the card it appears, nor did it add the _stripe_customer_id to the wp_usermeta table. From My Stripe Dashboard:

EMAIL DESCRIPTION DEFAULT SOURCE CREATED

donnie+testytesty@crack-ajax.com
Name: Testy Testy, Username: Testy
—
Jul 31, 1:04 PM

So, with the minimal setup two important pieces of data do not seem to be occurring as expected. I know this was working correctly at one time as the customers who bought into the system prior to March 2020 do have the tokens and the cards are saved. Since March 2020, the clients that have bought in are in Stripe and it appears their cards are as well (even though I don’t see the cards in my test today) AND the stripe id is in the wp_usermeta table. So, it is clear that something has changed in the WC Stripe plugin given this result – totally independent of any custom code other than the force save card filter.

As a hunch, I just searched the meta key filed in the wp_usemeta table for anything %stripe% and lo and behold, I see my three test customers I have created during the troubleshooting we have done over the last 3 months, and sure enough there is a meta key with the token, but the meta key is no longer:

_stripe_customer_id

it is now:

wp__stripe_customer_id

This is the source of the entire issue and one that I would have hoped you could have provided in support of your plugin 3 months ago. This token is necessary to do an auto charge because how else do you identify the Stripe user in order to charge their crd for a given order?

Anyway, this turns out to be the answer to this question on two tickets, and hopefully any developer in the future will find this useful if they encounter the same issue. I would also suggest that the documentation for the plugin is also updated with this information as well.

Thanks for all your help,
Donnie

So, is there a bug with the plugin not saving the token when using the force save filter?

Is there a way to add the token after the fact given that the customer account is created in the Stripe account as is the credit card stored, but the token is not entered into the WordPress database?

Or, do I not need the token in order to auto charge the customer now?

I currently have:

//Charge user via Stripe API
$charge = \Stripe\Charge::create([
‘amount’ => $totalNoDec,
‘currency’ => ‘usd’,
‘customer’ => $tokenString,
‘description’ => ‘Tiffany Andersen Brands – Order ‘ . $order->get_id()]
[‘idempotency_key’ => $order->get_id(),
]);

But, before I hit the API, I am checking for the token in the WordPress database:

//Get Stripe customer token that was created when the card was saved in woo
$tokenString = get_user_meta($user_id, ‘_stripe_customer_id’, true);

//If no token string, then user does not have a credit card on file
if ( empty( $tokenString ) ) {
$this->record_error_to_log( ‘User has no credit card on file for VIP Order #’
. $order->get_id() . ‘ for User ID #’ . $user_id );
return;
}

Is this even necessary now? Will the order go through without the token?

@dougaitken thanks so much! I have been testing to there expecting the checkbox. It is the client’s Stripe account, and I don’t have access there to verify the customer creation. I will setup my own Stripe account on the dev site and verify that way. Thanks again!

@dougaitken I am using a cron job the 1st of each month to create a preselected assortment of products to build an order and using Stripe API to charge payment. It has been running for a year without problems other than the forced save card issue. Does that answer your question?

Hi Gabriel,

I created a test page at https://submityourloanapplication.com/password-reset/ with the password reset shortcode only, but it does not work. But, if you add the query string ?submitted=yes it does.

The registration page is at https://submityourloanapplication.com/user-registration/ for testing.

(I apologize for the late response – I replied in the email notification and apparently you do not get those).

@wpmudev-support9 I think I may have figured out the issue. I have been spot checking several pages on my site regarding this issue. My clients have been reporting the contact page that they cannot access specifically. In my spot check all the pages did come up except the contact page, which reported the Content Encoding Error (net::ERR_CONTENT_DECODING_FAILED) error. It will clear when I clear the cache and load fine. But, the thing that makes that page different is that it has a Google Map iframe embedded. I am thinking this is the reason it throws the error. The specific page is https://crack-ajax.com/contact-crack-ajax-web-technologies/. Is there a way to turn caching/Gzip off for this page only?

Hi Adam,

I only got cache control headers set in my .htaccess, but no other caching going on.There are definitely no other caching plugins installed.

Thanks,
Donnie