[Admin]

Just send all variables by every click to buy button to php script that would be saved all variables to seesion? Maybe exist some js function where I can put needed function after errors? So info will be send after js validation passed? Thanks you.

[Admin]

It is clear. Thanks a lot. Have a nice day.

[Admin]

The plugin needs a thank you page where the payment processing happens. You can specify a custom Thank You page URL for each of your product. This will make it so the customer gets sent to the page you specify after they pay for that product.

In your case you can use the URL of the page where you have the form that the user should submit after the payment. So the user pays for the product and gets sent to the page where the form is.

If you read the following documentation, it will explain the feature:

Customize the Thank You Page URL and Message of the Stripe Payments Plugin

[Admin]

That comes from your theme. Your theme controls what meta details (author, date etc) are shown in a WordPress post or page.

You theme should have an option to turn those off. You should also be able to hide those using some CSS.

[Admin]

Did you also delete the cached files. Sometimes the cached files (if its there) will continue to show cached page even if the plugin is deactivated.

Try emptying the cache and do a new test transaction. Let me know how it goes after that.

[Admin]

No, I had disabled the caching plugin (w3 total cache) previously. This occurred since that.

[Admin]

We don’t have an option for that at the moment. You can create 4 subscription plans then put 4 subscription buttons on your landing page. The customers can pick the one they want.

[Admin]

Do you have any caching on this site?

[Admin]

At the moment, this plugin only deals with products created inside this plugin. If we get many requests for it, we will look at maybe adding an option to connect with products created in stripe.

[Admin]

Thanks a lot, this makes sense. I have implemented this as follows:

[accept_stripe_payment_checkout]
[accept_stripe_payment_checkout_error]
There was an error with the payment transaction:
{error_msg}
Please try again.
[/accept_stripe_payment_checkout_error]

But when I try this with one of Stripe’s test numbers (4000000000000341), the [accept_stripe_payment_checkout] shortcode itself also returns a message, namely

“System was not able to complete the payment. Your card was declined.”

This now duplicates the error message that follows just after:

“There was an error with the payment transaction:
Your card was declined.
Please try again.”

Is there a way to silence the output from [accept_stripe_payment_checkout]?

Note that I cannot use the enclosing form “[accept_stripe_payment_checkout] … [/accept_stripe_payment_checkout]” because I am using the asp_stripe_payments_checkout_page_result filter hook to generate a custom message (which is only displayed when using the self-closing shortcode).

Thanks,
Jorg

[Admin]

Yes, if you enable the multi-currency addon it will allow the customer to pick the currency for the donation. The customers will select the currency and apply it. Then they will be able to enter any amount that they want to pay you.

[Admin]

The {customer_name} email merge tag has been added in the latest release of the plugin. We have updated the documentation for it:

Email Merge Tags (Email Shortcodes) for Email Customization

[Admin]

You rock, thank you for being so responsive 🙂

I’ll mark this as resolved, and please reach out to me if you need anything in the future!

[Admin]

Hi Remi, Thanks for reaching out. This kind of issues can happen on rare occasions so its totally fine. We will update the plugin.

[Admin]

Hey,

Thanks a lot for the quick answer! And I totally hear your feedback. I like rants too 🙂

We made the change internally to a parameter that is supposed to be for internal use only. I don’t think this parameter has been documented in years either. So we did not expected anyone to be relying on its usage.

We take backwards-compatibility really seriously as you can see on our documentation page here and we’re really careful to ensure that we push changes that don’t affect existing integrations.

Unfortunately, it’s not always easy to know when some integrations rely on undocumented behavior as we have no way to track this easily, especially when it all happens client-side like in this case.

We’re really sorry that this broke some of your customers’ integration. It’s not the experience that we want to offer to our users.

In the future, you should feel free to contact us whenever something like this happens. We would have been able to find the issue immediately and pushed a fix that did not require you to make an urgent change on your end. I’d recommend trying #stripe on Freenode or our contact form here: https://support.stripe.com/email if you ever discover another regression like this one. Or you can always email me directly (remi at stripe dot com).

Cheers!
Remi

[Author]

Posts