VikStripe not Saving Stripe Parameters

Hi,

Thanks for your message. It looks like the system is unable to save the settings of your payment method, and the issue could be related to the database table responsible of storing such settings, or maybe to an invalid AJAX response.

Stripe is a global payment solution, and so the instructions for Australia are exactly the same as for any other country. The only required settings are the ones you are unable to save, and that’s why the Stripe SDK for PHP is returning that Exception (error) about the missing API Key for Stripe.

The most important settings, beside of course the ones to store your Stripe account credentials, are the followings:

• Payment Type: choose whether payments should be captured or just authorized.
• Enable automatic payment methods: if enabled, any additional payment method beside “credit card” available on your Stripe account will be displayed to customers to complete the payment.
• Set up Future Usage: there are some payment methods available in Stripe that cannot be re-used by the same user for future transactions. For example, third party payment solutions that work with wire transfers or similar transactions do not support the “future usage”, and so if this setting was enabled, such payment options would not be displayed to guests during the payment phase.

The problem is that you cannot save the settings at all. You could also be running the plugin on a multi-site environment, but we would need to check this better from your website.

This topic relates to the commercial version of Vik Booking and to the Add-On for Stripe, so we kindly ask you to get in touch with our technical team so that we can assist you. You can either use the contact form on our website or you can open a support ticket. We would probably need to debug the issue directly from your website with a temporary login account, and so we invite you to reach out to our team directly from our website so that we can investigate the issue.

Thank you!

The VikWP Team

It looks like the system is unable to save the settings of your payment method, and the issue could be related to the database table responsible of storing such settings, or maybe to an invalid AJAX response.

The problem is that you cannot save the settings at all. You could also be running the plugin on a multi-site environment, but we would need to check this better from your website.

– Actually, they ARE being saved to the database.
– Just the API settings are not getting retrieved.
Yes please check the tickets and I’ll provide login details.

• This reply was modified 2 years, 2 months ago by clickingclients.

Hi,

You said:

Stripe API Parameters aren’t being saved

The point is that the front-end Exception (error) thrown by the official Stripe SDK for PHP is saying that you need to provide an API Key, which indicates that this is actually empty.

Are you maybe working on a multi-site environment with your WordPress installation? It may be possible that the settings are being saved on a different database table, but as I said, we would need to debug the issue directly on your website in order to understand if anything is wrong. This is definitely a technical issue, because the behavior you described for saving the settings of the payment method is not normal. Everything should simply be saved and reloaded correctly.

It’s a single site environment.
Nothing special about the DB setup.

I’m looking in the database and can see all the data IS in there.

SELECT * FROMwp_vikbooking_gpaymentsORDER BYshownotealwLIMIT 50

The DETAILS and SETTINGS are retrieved from the DB, but the PARAMETERS are not.

I look forward to you checking the ticket – 2468 or 2070

Thank you

Thanks for opening a ticket with us. I see my colleagues are already trying to help you. It looks like the issue may be caused by the browser, as everything is fine with the database structure.

Anyway, I’m sure our colleagues will be able to provide the necessary assistance.

Thank you.

@e4jvikwp Thanks for your replies.

I’ve have tried in: Brave, Chrome, Firefox, and Safari … with the same results. ?A cleared form on the Right hand side.

I even tethered my computer to my mobile phone – off the wifi – just in case that was a problem.

THEN, I turned off some browser extensions (in Brave: but it shouldn’t make a difference as not all browsers doesn’t have extensions) and tried again.

This time I left the Image field blank.

It WORKED!

So I tried each of the following, only the last one works (3):?

1) https://MY-DOMAIN/wp-content/uploads/2019/07/logo-transparent-150px.png

2) MY-DOMAIN/wp-content/uploads/2019/07/logo-transparent-150px.png

3) wp-content/uploads/2019/07/logo-transparent-150px.png

So the error is including anything before this: ? wp-content/uploads/2019/07/logo-transparent-150px.png

Try it. ?If I’m correct…. please update the plugin to process both, or to give a hint on what is acceptable.

Thank you! ???

Hi,

Thanks for your updates. This is what we suggested in our ticketing system:

I believe our Stripe integration should take care of the URL to the PNG file on your server. In case the base domain URL is missing, this should be added, but feel free to make some tests with the settings and to try what option is working for Stripe to display your company logo properly.

A full URL should always work better than a relative URL, especially because with a relative URL the base domain name is taken from the WordPress settings.

Also, please keep in mind that you are still on a staging domain, and so this setting will have to be updated once you will move the website to the final domain for production.

Thank you.
(for the benefit of others) ….
I wrote:

It is “Image URL (An image to be displayed during the purchase.)” which I am referring to.
My testing showed only WITHOUT “https://my-domain” worked.

wp-content/uploads/2019/07/logo-transparent-150px.png = good.

This is less than 94 characters long in the “imageurl” part of the parameters. The full image path is longer than 94.

After that length, is it simply cut off. Then the JSON becomes malformed when encoding/decoding.

Hi,

Thanks for describing your solution. We believe the exceptional length of your staging domain did exceed the current limit of 512 chars for storing the settings in JSON format. We already had in mind to increase the size of this database field with the upcoming updates, and this is probably the time to do it.

In the meantime, please try to keep the company logo path for Stripe as small as possible so that the JSON string will be properly saved.

Thank you,
The VikWP Team