Skip to end of metadata
Go to start of metadata

Plattform / API

Feature

Spanisch kann nun als Endkundensprache (Check-Out) ausgewählt werden.

Spanish can be selected as a consumer language for check-out.

Please see below for english version

Feature

Folgende Änderungen sind umgesetzt worden:

  • Es ist nun möglich im Einstellungsbereich Standardwerte für den Steuersatz festzulegen.

          

  • Vor- und Nachname aus den Endkundenkontaktdaten wurden entfernt
  • Payone Link ist nun in Französisch verfügbar


Bugfixes

  • Hashalgorithmus ausgetauscht
  • Payone Link API lässt Punkt bei Artikelnummern zu



Feature

The following changes have been implemented:

  • It is now possible to set default values for the tax rate in the settings panel.
  • First and last name from the end customer contact data have been removed
  • Payone Link is now available in French


Bugfixes

  • Hashalgorithm replaced
  • Payone Link API allows point at item numbers


Please see below for english version

Feature

Folgende Änderungen sind umgesetzt worden:

Die Navigationsleiste wurde optisch angepasst, um besser zu sehen, wo man sich befindet.


Es ist nun möglich im Einstellungsbereich Standardwerte für folgende Parameter festzulegen

  • Account
  • Portal
  • Notify URL (nur für Status des Links nicht der TRX)



Es ist dem Händler möglich Endkundenkontaktdaten anzugeben. Diese Daten werden Ihrem Kunden auf der Check-Out Seite angezeigt und ermöglichen ihm Sie leichter zu erreichen. Diese Daten können auf Wunsch über unseren Customer Support angepasst werden.


                                    

Testmöglichkeit ohne extra Testaccount für Bestandshändler der PAYONE. Sie können mit ihrem regulären Account das Produkt PAYONE Link testen (max. 100 Links am Tag). Will der Händler live Links erstellen, muss folgendes Feld auf ja (=live) stehen.






           

                                          



                       


WeChat Pay und JCB stehen als Zahlungsart im PAYONE Link zur Verfügung

   

Mit dem Zusammenschluss von Paydirekt und Giropay ist es möglich Giropay als Gastkäufer über Paydirekt zu nutzen. In diesem Zusammenhang wurde das Paydirekt Logo angepasst. Auf die Zahlungsart Giropay hat dies vorerst keine Auswirkung


Bugfixes

  • In den Postleitzahlen ist es nun wieder möglich Leerzeichen mitzugeben, somit können Links auch für Länder wie GB versendet werden




Feature

The navigation bar was adjusted to get a better overview of where you are


It is now possible to set default settings for certain parameters:

  • Account
  • Portal
  • Notify URL (this URL is relevant for the Link status not the transaction status itself)



Within the header of the checkout we implemented merchant contact data, so your user can easily see who he is in relation with and how to contact you. If you wish to change this data, please contact our Customer Support.




                                

                                       

                


                       

Testing is now possible without an extra testaccount for existing merchants. The default setting for PAYONE Link is now on test mode (100 links per day), so if you want to switch to live links simply inform the Customer Support and they can change the setting for you.

WeChat Pay and JCB are now available payment methods within the link.

   

With the cooperation of paydirekt and giropay it is now possible to use giropay via paydirekt as guest user. With this both companies united their logo. Giropay is still available as a single payment method. 


Bugfixes

  • We fixed the zip code, so now you can insert spaces again, which makes the link available again to countries like the UK

Hey everyone, with this release we fixed some minor Bugs and rolled out some relevant merchant features like the compatibility of our invoice module with the PAYONE Link.


  • userid from PAYONE Platform saved within Link
    • We will save the userid created on the PAYONE Platform within the link, so a merchant knows which userid was created

  • Invoicing for PAYONE Link
    • The PAYONE Invoicing module is now also available for PAYONE Link transactions

  • Transaction ID transmitted to merchant
    • For usability reasons we now transmit the respective transaction ID for one link to the merchant via notifies. This way it is easier to find the transaction in question within our account management module.
    • However, this is not a transmission of a paid/not paid status

  • Default background image
    • If for any reason the merchant does not provide the API with a background image, PAYONE provides a default image.

  • General Improvements and Bugfixes


 

Hi all,

in January 2020 we went live with release 4.33.0 and 4.33.1 with the following content:

New Features

  • API - Key - change without downtime
    • When changing the portal key, the old key is valid for another 60 minutes. During this time, the API continues to accept both the new and the old key(s). This allows changes to be made without downtime.

  • Client API  / Hosted iFrame solution
    • The Hosted iFrame  now allows you to enter the credit card expiry date as a 2 or 4 digit date value.

Bugfixes

  • Klarna
    • Special characters in the end customer's address data are now correctly processed and passed on by our platform.

  • PMI - Navigation
    • When using the Hamburg Service Portal, there is now no longer a logout when clicking on "online" (PMI) in the header bar. In addition, a corresponding note is now displayed on how to get access to the PMI.

  • PMI - Transaction Status
    • Corrected the display of dates. Only the URL without parameters is now displayed as the target address.

  • Auto allocation
    • Improvement of payment allocation for SEPA payments


Hi all,

in 2019, we have provided Releases 4.32.0, 4.32.1 and 4.32.2 with the following contents:

Bugfixes

  • common
    • Improvement in the processing of credit card payments

  • auto allocation
    • Improvement in the allocation of payments (especially for subtype POV)

  • PMI -> Transaction Status
    • special characters are now displayed correctly in the transaction status overview
    • the page navigation in the transaction status overview now always shows the correct number of pages


Changes

  • Security issues fixed
  • Masterpass is no longer supported by our platform. Requests with the subtype masterpass are rejected.


Bugfixes

  • PAYONE platform - Client API (Hosted Iframes) are more IOS friendly.

Hi all,

we deployed our newest release for our platform and core API.

New Features

  • PMI -> Channels -> Telesales:
    • It's now possible to search by "PAYONE customer account no.", "Merchant reference number" and "Merchant customer number" for existing customer data
    • These data will be loaded and prefilled into the customer data form
  • PMI -> Customer Accounts -> Administration:
    • Input for "credit card details" has been changed to PAYONE hosted iFrames.
    • By this the credit card type will be detected automatically depending on the credit card number.
  • Request "3dscheck" now supports 3DS2 as well.

Bugfixes


Hi all,

we deployed our newest release for our platform and core API.

New Features

  • PMI -> Accounting -> Payment-Service:
    • Export fields for "Sub type", "State", "Address addition" have been added and can be selected for export
  • PMI -> Channels -> Telesales:
    • Input for "credit card details" has been changed to PAYONE hosted iFrames.
    • By this the credit card type will be detected automatically depending on the credit card number.

Bugfixes

  • 3DS1-test mode now works very similar to 3DS1-live mode.
    • i.e.: "termurl", "MD", "PaReq"need to be present in test-mode as well.
  • PMI -> Export -> Payments: 
    • Field "customerid" was empty in case of "vauthorizations" (Billing / Micropayment)


Integrations

Hi all,

it's finally here: Our new Plugin for Oxid 6.4

==1.5.1==

Bugfixes

  • fixed direct debit issues
  • fixed minor bugs with Amazon Pay
  • remove hard block overwriting in email template
  • adapt templates to avoid duplicate CSS loading
  • Renaming the Paysafe payment types to Unzer

Maintenance

  • compatibilty checked to 6.4.0
  • tested with Oxid 6.4.0


As usual, you can get the new release on Github:

Hi all,

it's finally here: You can now use Apple Pay in your Magento 1 Shop!

New Features

  • Add Apple Pay

Maintenance

  • Rename Payolution to Unzer

As usual, you can get the new release on Github:

Hi all,

it's finally here: You can now use Apple Pay in your Magento 2 Shop!

New Features

  • Add Apple Pay
  •  Add mechanism to prevent double invoice creation
  • Add creditcard cardholder field
  •  Add country restrictions for Boniversum addresscheck

Bugfixes

  • Fixed faulty JSON
  • Fixed class name of Unit Test
  • Fixed problem with hardcoded dummy birthday
  • Fixed gift card amount increase discount diff

Maintenance

  • Add Unit Tests
As usual, you can get the new release on Github:

Hi all,

it's finally here: You can now use Apple Pay in your Shopware 6 Shop!

New Features

  • deactivate payone payment methods on zero amount carts
  • add apple-pay
  • add payment method description

Bugfixes

  • fix config loading error
  • fix storefront requests
  • fix missing service
  • fix missing customer parameter on prepayment

Maintenance

  • fix backwards compatibility
  • Removed cardtype type discover
  • Add dependency to GitHub pipeline
  • Add fix for Version 6.4.5.0
As usual, you can get the new release on Github:

Hi all,

it's finally here: You can now use Apple Pay in your Shopware 5 Shop!

This is new in our latest release:

New Features

Bugfixes

  • fixed a bug that would lead to faulty txstatus behavior in Shopware <5.7
  • fixed a bug in rounding of VAT for countries with non-integer VAT rates (e.g. Switzerland)
  • fixed smaller issues and typos

Maintenance

  • Renamed Paysafe Pay Later to Unzer
  • "use shopware order number" is now active by default, since most merchants would want to use it anyway
  • Tested in Shopware 5.7.6
As usual, you can get the new release on Github:

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
As usual, you can get it on Github:


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

As usual, you can get it on Github:

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
As usual, get it on Github!

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

  • No labels