The official Ginger Payments extension for Magento 1.x duplicates a customer-related code in 5 places

Extensions Ginger Payments

dmitrii_fediuk (Dmitrii Fediuk) February 28, 2017, 8:37am 1

[Ginger Payments] What customer information is passed by the Magento 1.x extension to «POST /v1/orders/» for a Bancontact payment?
[Ginger Payments] What customer information is passed by the Magento 1.x extension to «POST /v1/orders/» for a bank card payment?
[Ginger Payments] What customer information is passed by the Magento 1.x extension to «POST /v1/orders/» for a bank transfer payment?
[Ginger Payments] What customer information is passed by the Magento 1.x extension to «POST /v1/orders/» for an iDEAL payment?
[Ginger Payments] What customer information is passed by the Magento 1.x extension to «POST /v1/orders/» for a SOFORT payment?

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

[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

[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