|
[Ginger Payments] The «customer/birth_date» property is absent in the JSON Schema of a «POST /v1/orders/» request, but is passed by the official extension for Magento 1.x
|
|
1
|
928
|
February 28, 2017
|
|
The official Ginger Payments and Kassa Compleet extensions for Magento 1.x pass the same customer data to «POST /v1/orders/» besides the «customer/locale» format
|
|
0
|
608
|
February 28, 2017
|
|
[Ginger Payments] The «customer/locale» property is absent in the JSON Schema of a «POST /v1/orders/» request, but is passed by the official extension for Magento 1.x
|
|
1
|
932
|
February 28, 2017
|
|
The official Ginger Payments extension for Magento 1.x duplicates a customer-related code in 5 places
|
|
0
|
649
|
February 28, 2017
|
|
[Ginger Payments] What customer information is passed by the Magento 1.x extension to «POST /v1/orders/» for a SOFORT payment?
|
|
1
|
902
|
February 28, 2017
|
|
[Ginger Payments] What customer information is passed by the Magento 1.x extension to «POST /v1/orders/» for an iDEAL payment?
|
|
1
|
905
|
February 28, 2017
|
|
[Ginger Payments] What customer information is passed by the Magento 1.x extension to «POST /v1/orders/» for a bank card payment?
|
|
1
|
873
|
February 28, 2017
|
|
[Ginger Payments] What customer information is passed by the Magento 1.x extension to «POST /v1/orders/» for a bank transfer payment?
|
|
1
|
761
|
February 28, 2017
|
|
[Ginger Payments] What customer information is passed by the Magento 1.x extension to «POST /v1/orders/» for a Bancontact payment?
|
|
1
|
799
|
February 27, 2017
|
|
[Ginger Payments] The official extension for Magento 1.x
|
|
0
|
459
|
February 24, 2017
|