Hi all,

we've just released a new Shopware 6 plugin. Here's what's new:

Bugfix

• transaction status transmission of txstatus "paid"

Maintenance

• Shopware 6.4.4.0 compatibility

Notice

• We're dropping compatibility with Shopware 6.2.* in a future release of this plugin

As usual, you can get it on Github:

Hi all,

we've just released a new Shopware 6 plugin. Here's what's new:

New Features

• new PAYONE permissions management
• status mapping per payment method possible

Bugfixes

• fix for unlock the buy now button
• PayPal Express: telephone number not a mandatory field

Maintenance

• Shopware 6.4.3 compatibility
• massive refactoring effort
• Elasticsearch compatibility

Hi all,

we've just released a new Shopware 5 plugin. Here's what's new:

New Features

• added WeChatPay
• added Trustly payments
• compatibility to shopware 5.7.x

Bugfixes

• added cardholder field and validation. Ideally, you should see more transactions using the "frictionless" flow without any redirects to the cardholder bank.
• added cardholder param, translations, and validation fixes
• fixed some backend syntax errors
• several fixes for Amazon payments, Ratepay, credit card, PayPal and Klarna

Maintenance

• tested with Shop version 5.7.2

Known Issues

• You might notice error messages while saving the credit card config. This seems to occur due to a bug in Shopware >5.7.0 and should get fixed in a future shopware release. The config gets saved correctly. References: https://issues.shopware.com/issues/SW-26140https://issues.shopware.com/issues/SW-26126

Hi all,

we've just released a new version of our Shopware 6 plugin!

Here's what's new:

New Features

• compatibility with Shopware 6.4.x

Bugfixes

• fixed API Test for paydirekt
• always provide shipping address for paypal payments
• fixed labels for PAYONE status mapping (finally!)

Maintenance

• tested with Shop version 6.4.1.0
• better error message translations

Hi all,

there's a new release for our Magento 1 plugin:

New Features

• re-introduced credit card holder field for better acceptance when in scope for 3D Secure 2.0.

We had previously disabled it to streamline the amount of fields a customer had to fill by default. With PSD2 and 3D Secure 2.0 in effect, we saw that using the cardholder field can benefit the ratio of frictionless payments vs. leaving it out.

Bugfix(es)

• call Ratepay DFP endpoint only when selected
• better checkout performance for checkouts with many addresses
• fixed item qtys doubled when using multi tabs and redirect payments

Maintenance

• rebranded "RatePay" to "Ratepay"
• tested with Magento 1.9.4.4

Hi all,

there's a new version of our Oxid 6 plugin!

New Features

• Support for Ratepay Device Fingerprinting
• Updated Ratepay Legal Texts
• New payment methods: Alipay, WeChatPay, Trustly

Bugfixes

• fixed clearing data wasn't shown on thank you page in some instances
• fixed SQL syntax errors on activation
• better discount handling
• increased default timeout for transactionstatus forwarding

Maintenance

• cardholder name is now required for better exemption handling with 3D Secure 2.0
• tested with Oxid 6.2.3

Hi all,

there's a new release for our Oxid 5 plugin and this is the changelog:

New Features

• new payment method: WeChatPay
• new payment method: Trustly
• new payment method: Alipay
• re-introduced credit card holder field for better acceptance when in scope for 3D Secure 2.0.
• We had previously disabled it to streamline the amount of fields a customer had to fill by default. With PSD2 and 3D Secure 2.0 in effect, we saw that using the cardholder field can benefit the ratio of frictionless payments vs. leaving it out.

Bugfix(es)

• fixed error in config export xml
• fixed timeout issues when forwarding txstatus messages
• fixed overrides of order email template when not using PAYONE payment methods (boo!)
• smaller fixes

Maintenance

• tested with
• updated legal texts for Ratepay
• Rebranded "RatePay" to "Ratepay"

Hi all,

we've just released a new plugin version for shopware 6. Here's what's new:

New Features

• new payment method: PAYONE safe invoice
• new payment method: Trustly
• added optional submission of order number in the "narrative_text" parameter. This will show the shopware order number on the customer's bank statement or payment info (depending on payment method). If left out, our internal txid is shown.

Bugfix(es)

• fixed payone_allow_refund and payone_allow_capture custom fields to better reflect the current status of an order. This can help when issuing captures and debits via third party systems

Maintenance

• tested with Shopware 6.3.4.1

Hi all,

We pushed out a new release of our Magento 1 plugin. This is what changed:

New Feature

• Removed uses of jQuery where not strictly neccessary

Bugfixes

• Corrected voucher VAT for Klarna start_session call
• Corrected Paydirekt shipping vat

Maintenance

• Updated Ratepay legal texts
• Recognize OpenMage version and incorporate into request diagnostic data
• Tested with Magento 1.9.4.4

Hi all,

as you might have noticed by our recent communication, we're in full swing preparing our systems for the upcoming EMV 3-D Secure 2.0 system. This implementation of multi-factor authentications during credit card payments will make credit card payments more secure for your customers. We have received questions from our customers regarding the readiness of our and their systems for this new and improved implementation of 3-D Secure. So in this post, we'll give you some clarifications and advice on how to proceed.

The Good News

Most of the heavy lifting in implementing 3-D Secure 2.0 lies on us as your payments provider! In most cases, merchants who have processed 3-D Secure 1.0 payments in the past will need little to zero effort to take advantage of the new system.

3-D Secure 2.0 Readiness of Plugins and Integrations

First Party Shop Plugins

Here's a list of systems where we have confirmed 3-D Secure 2.0 works as expected:

Plugin	3-D S 2.0 works
Magento 1
Magento 2
Oxid 4/5
Oxid 6
Shopware 5
Shopware 6
Woocommerce
Prestashop
One-Stop-Shop

Partner Ecosystem

If you're a user of one of our partner integrations (Available Integrations), please check back with your integration vendor and make sure the system is at least able to process redirects during credit card checkouts. This has been a requirement in our integrations for a long time, so most integrations should also work with 3-D Secure 2.0

Recurring Payment Integrations

We've tried hard to introduce as little changes to existing integrations as possible, but the 3-D Secure 2.0 Implementation will likely break the way recurring credit card payments are currently made through our platform. Please direct your integration vendor to this page: Special remarks - Recurring transactions credit card or let them contact us at integrations@payone.com

Need Help? Contact us!

We hope this guide helps you in transitioning to 3-D Secure 2.0 smoothly. If you have any further questions, feel free to contact our service teams: https://www.payone.com/kontakt/