FAQ

Stripe payment plugin frequently asked questions.

1. Does your plugin support 3D Secure, and will users see it when making a payment?

Yes, 3D Secure is implemented automatically if it is provided by the bank which has issued the debit/credit card. There is no option to enable or disable it in the plugin. 3D Secure appearance depends on the card and bank.

If 3D Secure does not appear during payment, it means that its display depends on the card-issuing bank. If the bank supports 3D Secure, the user will be prompted to confirm the payment.

2. The payment is successful in VirtueMart, but it has pending status in Stripe dashboard

You missed Webhooks settings. Please, get Webhook URL and add it to Stripe settings.

3. How can I test payments?

Enable Sandbox mode, add test API keys and use Test card numbers and tokens or Testing 3D Secure payments.

4. Stripe accept extra payments methods as iDEAL, Klarna, Sofortüberweisung, Apple Pay and other. How I can add them?

We provide two versions of Stripe integration with VirtueMart. Both Stripe plugin and Stripe Checkout plugin accepting cards as well as allowing to include additional payment methods.

The list of supported methods: (to be updated)

The actual list of available integrations can be checked at the official documentation.

You can activate required payment methods from Stripe Dashboard. Go to Dashboard > Settings > Payment methods.

Enable additional payment methods in Stripe
Enable additional payment methods in Stripe.

Then enable and configure the required method(s). They will appear at the front-end of your site. You do not need to activate anything in payment method in VirtueMart.

5. I get error: 0 - Invalid API Key provided

This error means that one of the keys used in your plugin settings is invalid. Make sure that Publishable Key and Secret Key are valid.

6. Is your plugin PCI compliant, and is compliance handled by Stripe?

Stripe (inside the shop): The plugin uses Stripe Elements, which provides hosted payment fields for handling all sensitive card data. This means the cardholder enters their payment information directly in fields served from Stripe’s PCI DSS–compliant servers, not on your site. As a result, the burden of PCI compliance for handling card data is mostly on Stripe, not on you as the website owner.

Stripe Checkout (external page): The plugin redirects users to Stripe’s hosted payment page, where they enter their payment information. Since all sensitive data is handled directly by Stripe’s PCI DSS–compliant servers, the burden of PCI compliance is fully on Stripe.

Last updated