Issue with DateTime type for AbstractOrder::$terms and AbstractOrder::$privacy

[ocean90]

The code documentation says that both properties accept a DateTime object but the API only accepts a timestamp (integer) in requests.

Request:

Response:

Example of a request payload that produces a "Malformed request!" error.

{
   "payment":{
      "paymentInstrumentId":"paymentinstrument_xxxxxxxx"
   },
   "product":"creditcard",
   "async":{
      "successUrl":"http:\/\/google.de?q=success",
      "failureUrl":"http:\/\/google.de?q=failure",
      "cancelUrl":"http:\/\/google.de?q=cancel"
   },
   "terms":{
      "date":"2017-10-26 14:48:15.000000",
      "timezone_type":3,
      "timezone":"UTC"
   },
   "privacy":{
      "date":"2017-10-26 14:48:15.000000",
      "timezone_type":3,
      "timezone":"UTC"
   },
   "description":"Tickets",
   "initialAmount":6000,
   "currency":"CHF",
   "basket":[
      {
         "name":"Stehplatz",
         "totalPrice":6000,
         "unitPrice":6000,
         "quantity":1
      }
   ],
   "customer":"customer_xxxxxxxx",
   "channel":"ECOM",
   "source":"Website"
}

[ocean90]

Turns out the middleware requires the use of milliseconds. To get the current time in milliseconds you have to use round( microtime( true ) * 1000 ); which will return a float by default.

[Sharenkamp]

Hi @ocean90,

the upcoming release will support timestamp and Datetime. The conversion to milliseconds will be handled by the SDK.

For the current version your solution works fine.

best regards, Stefan

[Sharenkamp]

Fixed with 1.1.0