PAYONE Payment Extension for Magento 2

PAYONE GmbH

Last update: Nov 10, 2022

Related tags

Miscellaneous magento magento2 payment-methods magento2-extension payment-processing payone payment-solution payment-service

Overview

PAYMENT FOR YOUR MAGENTO 2-SHOP

The PAYONE payment extension for Magento 2 is massively reworked since the first version. The Github-Community was important for this development. Take a look at our last released version and send us commits or other feedback to take care for the best possible solution. Your feedback is very important to us to ensure a flawless code and rapid development.

Important functions for Magento 2

Seamless integration of Magento's OnePage Checkout
Very wide range of functions, simple and comprehensible supported by detailed online help
Central configuration and management options on the Magento Admin Panel
Export function of the configuration in XML format to facilitate the technical support
Optional multi-partial capture for partial deliveries
Supports simplified PCI DSS conformity in accordance with SAQ A
Payment methods can be automatically hidden depending on the amount of the order and the credit rating of the customer
Find all currently supported payment methods on https://docs.payone.com/x/WoAS

Installation

Go to your installation directory of Magento 2 and perform the following commands
composer require payone-gmbh/magento-2
php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento cache:clean

Magento Version Support

We follow Magento's version lifetime according to their Enterprise Agreement. In theory, Magento 2.0 is still supported, but not actively tested.

Support for Magento 2.1 was phased out in June 2019. From that date, we discontinued actively testing Magento 2.1.

Support for Magento 2.2 was phased out in December 2019. From that date, we discontinued actively testing Magento 2.2. Subsequently, it will be removed from our build matrix in the future.

More information

For documentation see: https://docs.payone.com/display/public/INT/Magento+2+Plugin

Contact

PAYONE GmbH
Office Kiel
Fraunhoferstraße 2-4
24118 Kiel, Germany
Phone +49 431 25968-400 Fax +49 431 25968-1400
[email protected]

License

See our License Agreement at: https://www.payone.de/fileadmin/downloads/sonstiges/PAYONE_Haftungs_und_Lizenzvereinbarung_Extensions.pdf

About BS PAYONE

Since the end of August 2017, the two payment specialist companies PAYONE and B+S Card Service merged to become BS PAYONE GmbH. All current partnerships will be maintained the way they are. APIs, interfaces, and other technical parameters will stay the same. Your current contact persons will continue to gladly be at your service.
BS PAYONE GmbH is headquartered in Frankfurt am Main and is one of the leading omnichannel payment providers in Europe. In addition to providing customer support to numerous Sparkasse banks, the full-service payment service provider also provides cashless payment transactions services to more than 255,000 customers from various branches – whether that be in stationary retail or when completing e-commerce and mobile payment transactions.

Comments

Appointed status double and Double invoice
@niclashoyer @fjbender @hreinberger @FatchipRobert When order placed by Payone Paypal always two invoices created one is with original amount and other for 0.00 amount also we having two Appointed Status.

This is start happening sudden from last week. where as in last two weeks we didn't change any thing in db or files. Server is very normal no load on server. very less users and not a heavy catalog

Please guide how to fixed it and also if it from magento side how to catch this issue for further debugging

2***:f**:08:::4:1 - - [09/Mar/2020:23:09:15 +0100] "POST /payone/transactionstatus/decouple/ HTTP/1.1" 302 4268 "-" "-"

1*5.*0.0. - - [09/Mar/2020:23:09:14 +0100] "POST /payone/transactionstatus HTTP/1.1" 200 4093 "-" "PAYONE FinanceGate"
opened by omargits 17
Advance Payment not automatically captured

When paying with advance payment, an invoice is created when the customer pays. Order is marked as fully paid and goes into processing however the payment is not really captured.

Is there a reason why it does not capture automatically? Maybe I am missing some configuration. Having to manually confirm hundreds of payments each day is not a very good solution.
stale

opened by domeglic 14
MAG2-96 doesn't fix existing config

hi there,

if you have core_config_data entry with "store" instead of "stores" it's not fixed by MAG2-96. Instead the broken config stays in the DB and causes trouble later.

You should create a migration patch for it!

Rico
stale

opened by riconeitzel 12
Multi store admin orders

Hello,

we are currently investigating some issues which are related to orders in general, including admin orders. All the payment types of our client are PayOne only. Two stores are affected, whereas the first store was there from the beginning and second store is a new one which was taken into the same system this year.

assumption / question

Momentarilly we asume, that the PayOne Magento2 module is not handling admin orders in a multistore correctly. Please verify or decline this, please.

Details from our investigation

Especially the IP-Check makes problems while creating admin orders. It seems that at this point is not taken the second store PayOne configuration of the IP-check, in which we included Germany besides Austria, because the admins are located in Germany and must be able to create orders for austrian customers as well. It throws errors and makes order creation impossible, until we deactivate the first stores IP-Check. So then we concluded to the above question: Is the module really using the correct configuration and payment portal or is maybe a generic problem with admin orders in multistores?

opened by LB-Team-igniti 11
release 1.3.1 breaks magento2 API

In the latest release, the Payone\Core\Model\WebApi\Addresscheck was added as a webservice class.

It does not follow the magento2 best practices for creating a new service in the service layer and fails an internal check which leads to an exception (in our case, when calling the getOrderList SOAP Call)

main.CRITICAL: InvalidArgumentException: The service interface name "Payone\Core\Model\WebApi\Addresscheck" is invalid. in /var/www/share/stage.ballon24.de/project/releases/20170206141358/vendor/magento/module-webapi/Model/ServiceMetadata.php:227

I assume, this breaks all SOAP API calls (maybe also REST) since the exception is thrown during the WSDL generation.
bug

opened by davidverholen 11
release for compatibility with Magento 2.3.2

The latest available release (2.6.0) is not compatible with Magento 2.3.2 as it lacks the changes from https://github.com/PAYONE-GmbH/magento-2/issues/248 that were added to the master branch after the release. Are there already plans to provide a new release that includes these changes?

Thank you and Best regards

opened by berwa 10
Order Items send to Payone during capture

Hi,

during an online capture the order items are collected here in order to be sent to Payone: https://github.com/PAYONE-GmbH/magento-2/blob/master/Model/Api/Request/Capture.php getInvoiceList()

As you can see it expects request parameter, this means an online capture can only be done from the backend. There should be another solution so that you can create an online capture maybe on command line or in some other scope.

The only way now is to fake the request parameters, if possible.

Thanks :-)
enhancement

opened by sydekumf 10
Order confirmation sent when payment failed

yesterday, we had the case, that a payment could not be completed because the mastercard was not registered for mastercard securecode (regarding to the error message of the cc provider).

after the payment failed, order confirmations have still been sent to the customer.

opened by davidverholen 10
New behavior in Observer/TransactionStatus/Paid.php for advanced payment
There is a new behavior in the mentioned file.

// if advance payment is paid should create an invoice if ($oOrder->getPayment()->getMethodInstance()->getCode() === PayoneConfig::METHOD_ADVANCE_PAYMENT) { $oInvoice = $this->invoiceService->prepareInvoice($oOrder); $oInvoice->setRequestedCaptureCase(Invoice::NOT_CAPTURE); $oInvoice->setTransactionId($oOrder->getPayment()->getLastTransId()); $oInvoice->register(); $oInvoice->save(); $oOrder->save(); if ($this->baseHelper->getConfigParam('send_invoice_email', 'emails')) { $this->invoiceSender->send($oInvoice); } }

Is there a traceable discussion why it is necessary to create an invoice instant after the TransactionStatus paid is received? In our case the former behaviour is preferred, that there is no invoice created. As I can see, the invoice is not captured, too. So in fact we ran into the problem, that we tried to refund an order, but it was not possible because the invoice was not captured. In Magento 2.4 the possibility to capture afterwards is missing, so we had a lot of trouble to clean up this case.

If there is no reason to keep this code, I would suggest to remove it or to make this behavior at least configurable.
stale
opened by andreasberenz 9
Multi-website Magento instance Base Currency / Display Currency issue

We have a Magento instance that has multiple websites (multiple stores and store views).

When PayOne is configured, you can choose 2 options. Base Currency and Display Currency. The base currency for Magento instance is EUR.

The problem is that for each website we have different Base Currencies. E.g. for the polish website - Base Currency is PLN, but for PayOne the base currency is always EUR.

This is a very critical issue that does not allow charging money in certain store views.
stale

opened by ostukalovprovectus 9

Refund orders with several variants for one configurable

When an order with a payone payment method was placed and captured, the refund during creditmemo creation fails in specific cases.

Given:

$order->getAllItems() = [
  0 => ['productId' => 1, 'sku' = 'abc_1', 'type' => 'configurable'],
  1 => ['productId' => 1, 'sku' = 'abc_1', 'type' => 'simple'],
  2 => ['productId' => 1, 'sku' = 'abc_2', 'type' => 'configurable'],
  3 => ['productId' => 1, 'sku' = 'abc_2', 'type' => 'simple'],
  4 => ['productId' => 2, 'sku' = 'def_1', 'type' => 'configurable'],
  5 => ['productId' => 2, 'sku' = 'def_1', 'type' => 'simple'],
];

$aPositions = $creditmemo->getItems() = [
  0 => ['orderItemId' => 11, 'productId' => 1,  'sku' = 'abc_1'],
];

Then the following code is executed for every order item (no dummy positions) and will create an invalid API call (\Payone\Core\Model\Api\Invoice::addProductItem):

[...]
if ($aPositions !== false && array_key_exists($oItem->getProductId(), $aPositions) !== false) {
  $dItemAmount = $aPositions[$oItem->getProductId()];
}
[...]

Order item 0 is included in parameters, because productId of creditmemo item matches order items product id. That is correct, because sku matches also. Order item 2 is included in parameters, because productId of creditmemo item matches order items product id. That is not correct, because sku does not match.

opened by david-fuehr 9

Missing handling of region-codes (Magento/ISO vs. Payone api)

Hello Payone-Team, we recently ran into the following problem within one of our projects: The customer can not continue or complete the checkout, as his address from Argentina is rejected by the Payone server/api with the message Parameter {state} faulty or missing. The data transferred as state was AR-X, which is the same code that is used in Magento, and that is created during the Magento-installation: https://github.com/magento/magento2/blob/2.4-develop/app/code/Magento/Directory/Setup/Patch/Data/AddDataForArgentina.php#L72 From the information publicly available AR-X (and the other state/region-codes used by Magento for Argentina) are the proper ISO 3166-2 codes (https://www.iso.org/obp/ui/#iso:code:3166:AR), but the Payone api expects different ones (https://docs.payone.com/pages/releaseview.action?pageId=1213957#ISOSubdivisions(ISO31662)-AR-Subdivisions).

According to a quick check the same issue is also present for state/region-codes for China, Magento (https://github.com/magento/magento2/blob/2.4-develop/app/code/Magento/Directory/Setup/Patch/Data/AddDataForChina.php#L63) and ISO 3166-2 (https://www.iso.org/obp/ui/#iso:code:3166:CN) use a CN-letter combination, whereas the Payone api expects a numeric code (https://docs.payone.com/pages/releaseview.action?pageId=1213957#ISOSubdivisions(ISO31662)-CN-Subdivisions).

In my opinion the Payone extension should make sure that the state/region-codes are transmitted to the Payone api/server as specified in the Payone documentation and thus convert the codes from Magento accordingly.

Best regards

opened by berwa 1
Additional cancelled order after successful payment using Paypal
Steps to reproduce:

Go to checkout and select Paypal as a payment method

Click on place order button and get redirected to Paypal payment portal

Click 'cancel' button in a browser.

Success message display

Order Placed on Admin

https://user-images.githubusercontent.com/11783161/199046455-0becf1b3-dae3-4295-be9d-b3da246802a8.mp4
stale
opened by sanjuantala 2
Product quantity is reduced on payment error
Hi,

I couldn't find the place where in the module this happens. But here's how to reproduce:

Magento-Version: Open Source 2.4.5-p1

default catalog inventory, no MSI

configuration cataloginventory/options/can_back_in_stock = 1

no backorders allowed

Payone Module Version: 3.6.0

Reproduce

have a product with qty=1

add to cart, go to checkout

enter invalid address data, for example firstname=1, lastname=2, street=3

select "Paypal" as payment method

click "Place order"

after the error message, go back and fix your address

proceed to payment page again

select "Paypal"

click "Place order"

Expected result

product was not ordered, so it should still have qty=1

Get redirected to Paypal & being able to finish the payment

Actual ### result

product has qty 0 (can be seen in backend & database)

Error message: "This product is not in stock", ordering not possible

Any idea how this happens?

Thanks Simon
opened by simonrl 3
storage is undefined after failed 3D-Secure Password

Magento 2.4.3-p1 Module: 3.5.0

Customers tend to be confused by the necessity to enter another password after entering their credit card data in the shop. This results in a redirect back to the shop which fails with an error in the JS console (Uncaught TypeError: storage is undefined) pointing to line 178 in the file vendor\magento\module-customer\view\frontend\web\js\customer-data.js.

All JS stops and the page is stuck with a spinner.

All works fine if the correct password is entered.

Not sure if this is related to this issue: https://github.com/PAYONE-GmbH/magento-2/issues/464
stale

opened by OvalMedia 2

Releases(v3.6.0)

v3.6.0(Sep 29, 2022)
New Features

Removed IBAN and BIC inputs from Sofortüberweisung

Payment list will now always be updated when billing address is changed

Bugfixes

Changed IP proxy mode to be used everywhere when reading users IP

Changed placeholders to single curly brackets

Fixed issue with Amazon Pay Widget javascript

Allow academic title in credit card holder name (big thanks to @netzkollektiv)

Fixed a PHP 8.1 problem with a null value

Fixed problem with compatibility to Amasty Checkout

Removed Amasty coupon code from invoice list

Fixed subshop config usage for backend orders

Maintenance

Added test account link to config menu

Tested with 2.4.5

Source code(tar.gz)
Source code(zip)
v3.5.0(May 23, 2022)
New Features

Add validation if birthday is a valid date

Compatibility for Magento 2.4.4 and PHP 8.1

New payment method: Ratepay Direct Debit

New payment method: Ratepay Installment

Saved creditcard data will be filtered by available credit card providers

Bugfixes

Fixed unserialize problems with encoding

Changed iDeal clearing information template

Fixed creditcard cardholder is not saved on first entry

Fixed cardtypes in hosted iframe config for cvc validation

Ratepay javascripts now only loaded if method is activated

Fixed display of creditcard data in order overview

Fixed cardtypes in hosted iframe config for cvc validation

Fix potential cross-site scripting flaw on checkout page. Big thx @riconeitzel for finding this!

Maintenance

Updated iDeal bankgrouptypes

Add missing translation for Place Order button

tested with Magento 2.4.4 with PHP 8.1
Source code(tar.gz)
Source code(zip)
v3.4.1(Feb 3, 2022)
New Features

Bancontact integrated

Bugfix(es)

Fixed problem with Klarna for registered users

Do not cancel successful paid redirect payments even after interruption

Amazon Pay fix: Load quote only when checkoutConfig is available

Maintenance

Readded version number to composer.json

Changed internal payment names

Added CSP whitelist to module

Removed accountnumber and bank code from invoice

tested with 2.4.3

Change composer.json

Source code(tar.gz)
Source code(zip)
v3.4.0(Jan 31, 2022)
New Features

Bancontact integrated

Bugfix(es)

Fixed problem with Klarna for registered users

Do not cancel successful paid redirect payments even after interruption

Amazon Pay fix: Load quote only when checkoutConfig is available

Maintenance

Readded version number to composer.json

Changed internal payment names

Added CSP whitelist to module

Removed accountnumber and bank code from invoice

tested with 2.4.3

Source code(tar.gz)
Source code(zip)
v3.3.0(Nov 2, 2021)
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

Source code(tar.gz)
Source code(zip)
v3.2.0(Oct 27, 2020)
New Feature

Added Ratepay Invoice

Bugfixes

Fixed getting Base Currency from right scope (#298)

Shipping address phone number is now sent to Klarna

Override mandatory fields when using Amazon Pay

Maintenance

Tested with Magento 2 2.4.1

Source code(tar.gz)
Source code(zip)
v3.1.0(Aug 18, 2020)
New Feature

narrative text (when filled) now gets forwarded to PayPal for easier transaction assignment at PayPal

Bugfixes

fixed back button on SEPA page

fixed amasty integration

better txstatus forwarding

Maintenance

Magento 2.4 compatibility

Source code(tar.gz)
Source code(zip)
v3.0.0(Jul 1, 2020)
Known Bugs

Klarna can not be completely deactivated, see #324 - will be fixed in v3.0.1

New Feature(s)

new klarna implementation

auto-cc-detection

EE Gift Card Support

Amasty Gift Card support

multicurrency functionality for Amazon Pay

Breaking Change

klarna legacy will be shut down in the end of Sep 2020 and has been removed (!) Only upgrade if you are either not using Klarna or have been set up with the new Klarna Connector on the PAYONE platform

Billsafe has been removed, as it has been discontinued for quite some time now

Bugfix(es)

fix KnockoutJS scope problem with getCode()

fix score of creditrating getting lost

fixes path to privacyDeclaration for Debit/Installment methods > thx @mborkowski

cash on delivery Template without clearingdata

deprecated function name > thx @sippsolutions

Maintenance

removed BillSafe

updated Amazon Pay decline handling

Source code(tar.gz)
Source code(zip)
v2.8.0(Feb 4, 2020)
New Features

Paydirekt Oneclick (early stage. If you want to use this method for your instance, please get in touch with us!)

Bugfixes

fixed txstatus behavior with virtual orders

fixed an encoding issue

Maintenance

PHP 7.3 Support

Source code(tar.gz)
Source code(zip)
v2.7.0(Sep 16, 2019)
New Features

Amazon Pay is now PSD2 compatible

Decoupled txstatus forwarding from internal processing so a failed forward doesn't break the whole process

added webrestrictions.xml to avoid transaction-updates being blocked by website-restrictions (thx @berwa)

Bugfixes

better performance for address checks

more robust Amazon Pay button when official Amazon Plugin is also installed (but not active)

Maintenance

Compatibility with Magento 2.3.2

A Word on PSD2

At the time of Release, only Amazon Pay requires code changes to be compatible with the upcoming PSD2 regulation. However, you can configure the plugin for optimized conversion when using Credit Cards and 3-D Secure 2.0. For more info see our Remark on docs.payone.com https://docs.payone.com/display/public/INT/Magento+2+Plugin#Magento2Plugin-EnsuringMaximumConversionWith3DSecure2.0
Source code(tar.gz)
Source code(zip)
v2.6.0(Jun 13, 2019)
New Features

New status in response in case of curl timeouts (thx @gerritpechmann)

Added mechanism to create substitute orders in case of a delayed appointed status

Bugfixes

fixed a bug with billing address checks

Fixed issues with multiple addresschecks

fixed rounding error in transaction log

fixed problem with $aPaymentMethods index not set

Maintenance

added new bankgroup "Handelsbanken" to iDeal

fixes to unit tests

Note on Protect

We decided to introduce a new way of using our Protect Module. This implementation allows more flexible and complete use of our risk assessment requests and can be customized to your needs. Check it out at https://github.com/PAYONE-GmbH/magento-2-simple-protect

This new approach was designed to give you more flexibility when using complex risk assessment methods, so take a look if you need more flexibility than is currently offered in our plugin.

Feel free to contribute and ask questions in the linked repository. Please get in touch if you want to test drive the new changes.

Change in behavior on initial setup

Due to changes in Magento 2.3.1, all payment methods are active after an initial installation. Please make sure to deactivate all non-wanted payment methods before launch.

This doesn't affect updates, so you'll keep your active payment methods after an update.
Source code(tar.gz)
Source code(zip)
v2.5.0(Jan 14, 2019)
New Features:

Amazon Pay

Bugfixes

fixed setup:upgrade when table prefix is used (thx @andreasberenz)

Maintenance:

Magento 2.3.x compatibility

Source code(tar.gz)
Source code(zip)
v2.4.2(Nov 29, 2018)
Bugfixes:

fixed missing workorderid in certain PayPal ECS Requests

fixed issue where discounts weren't sent to BS PAYONE API during refunds

fixed issue where the transaction status changed a canceled order before a substitue could be created

fixed various issues which occured when using the "back" button of the browser during checkout

fixed a small spelling error (thx @niclashoyer)

Maintenance

the hard coded Paysafe auth setting was removed

Source code(tar.gz)
Source code(zip)
v2.4.0(Sep 3, 2018)
Bugfixes:

sped up API calls by using indices in payone_protocol_transactionstatus (thx @david-fuehr!)

Fixed store code usage in backend

not cancelling Appointed processing anymore when email was already sent

Maintenance:

Renamed Payolution to Paysafe Pay Later

Removed deprecated infopage in backend

updated bank groups

Source code(tar.gz)
Source code(zip)
v2.3.0(Jun 28, 2018)
Features

Address check is now also executed for addresses in the address book

IP Addresses in logs are now masked

Credit card minimum validity timeframe can now be specified

Safe Invoice is now removed from list of payment methods if customer is denied (thanks @juules) - this can have impact if you modified the error processor, see #179

Bugfixes

Invoice is only saved if it existed (#164, thanks @josefbehr)

Added missing backend template

Clearing data in capture responses is now processed correctly

personstatus parameter in consumerscore requests is now mapped correctly

Source code(tar.gz)
Source code(zip)
v2.2.0(Apr 4, 2018)
Features

Registered customers are now banned for 24h from using Payone Safe Invoice if they're rejected

CVC length for credit cards is now enforced

Transactions can now be processed in either Base Currency or Display Currency, depending on configuration (#157, thanks @josefbehr)

Bugfixes

The date of birth for registered customers is now correctly evaluated

Updated the composer.json to use https Magento repository

Source code(tar.gz)
Source code(zip)
v2.1.0(Feb 22, 2018)
Features:

Direct Debit orders can now be created in the backend

Invoices for authorization order are now created on Appointed TX-Status

The TX-Status controller can now recognize Forwarded-For headers

Business relation ("b2b" or "b2c") is now transmitted for safe invoice orders

Bugfixes:

Serialized to JSON conversion now works correctly on upgrade

Multiple items with same ID but different SKUs are now handled correctly

Fixed a problem where credit memos for non-Payone orders would throw an exception

Converted the last raw SQL queries to PDO

Fixed a problem where the shop could not be built when phpunit was not present

Fixed a bug where payment methods would not be displayed when using Magento B2B

Source code(tar.gz)
Source code(zip)
v2.0.2(Nov 23, 2017)
Cancel and Return URLs now return to payment selection

New payment method AliPay

A Cash on Delivery refund can now contain SEPA data to automatically rewire the amount to the buyer (see #120 for details)

We now successfully build on PHP 7.1

When upgrading from Mage 2.1 to 2.2, serialized payone data is converted to json

Source code(tar.gz)
Source code(zip)
v2.0.0(Oct 26, 2017)
Added compatibility for Magento 2.2

Unit Tests only work with PHPUnit 6 now

Added some missing translations

Added compatibility for 3rd party module

Source code(tar.gz)
Source code(zip)
v1.3.6(Oct 18, 2017)
Added new payment method Payone Safe Invoice

Fixed a bug where the request type could be void when it really shouldn't

Fixed test order in module.xml

Post-order calls now honor all special parameters

Enabled CC functions in bundled JS mode

Fixed the preauth/capture process for Advance Payment

Fixed layout in checkout_index_index

Source code(tar.gz)
Source code(zip)
v1.3.5(Aug 9, 2017)
Added Payolution payment methods

Capture and debit calls now provide invoice data

Bank data now added to order confirmation email per default

Various bug fixes

Source code(tar.gz)
Source code(zip)
v1.3.4(Jun 30, 2017)
Added Boniversum features

Remove PayPal ECS Button from product pages

Send invoice data for preauth requests

Fixed basket update bug when address check was activated

Locale is now taken from shop environment and not system wide locale

More little bug fixes

Source code(tar.gz)
Source code(zip)
v1.3.3(May 18, 2017)
Order confirmation mail now only sent when Payone confirms transaction

More Unit Tests

Various bugfixes

Source code(tar.gz)
Source code(zip)
v1.3.2(May 2, 2017)
Added first bunch of Unit Tests

Added some small features for individual payment methods

Fixed a ton of bugs (Thanks @FatchipRobert, @skymeissner, @bragento, @espressobytes)

Source code(tar.gz)
Source code(zip)
v1.3.1(Jan 20, 2017)

Added "protect" components address check and consumer score
Source code(tar.gz)
Source code(zip)
v1.2.7(Dec 12, 2016)

Fixed a bug where a wrong cart would be submitted with variant articles (MAGE-281).
Source code(tar.gz)
Source code(zip)
v1.2.5(Dec 5, 2016)
Fixed #8 where table prefix would not be used

Fixed #9 where conditions would not apply for cc orders

Added default status mapping

Source code(tar.gz)
Source code(zip)
v1.2.3(Nov 8, 2016)

Source code(tar.gz)
Source code(zip)
v.1.2.2(Oct 26, 2016)

initial commit of the newly produced and testet module
Source code(tar.gz)
Source code(zip)