Exact date and time of transaction authorization - csob/paymentgateway GitHub Wiki

This extension returns to merchant new information of date and time of transaction creation and authorization and settlement date in addition to payment/status response.

This extension is not available in the basic setup. Please contact [email protected] for activation of the extension for your merchant account.

Transaction creation date

Date and time of transaction creation on the payment gateway during payment/init call. Format is timestamp, YYYY-MM-DD'T'HH:MM:SS.SSS'Z'.

Authorization date and time

Date and time of authorization, more precisely it's time of start of authorization process on the payment gateway (after parameters are validated, before authorization request is sent to authorization processor system). Format is YYMMDDHHMMSS.

Settlement date

The settlement date determines at which statement the transaction ends. Format is YYYYMMDD.

Extension parameters in payment/status response

Newly added parameter is extensions, which contains a list of all activated extensions for a given operation. Extension trxDates will be returned only in payment/status response.

Description of trxDates extension parameters

Parameters in bold will always be returned.

Item	Type	Description
extension	String	Extension ID (assigned by the gateway). It is always trxDates for this particular extension.
dttm	String	Date and time of response YYYYMMDDHHMMSS.
createdDate	String	Date and time of transaction creation, YYYY-MM-DD'T'HH:MM:SS.SSS'Z' format.
authDate	String	Date and time of authorization, YYMMDDHHMMSS format, present only if transaction is authorised.
settlementDate	String	Date of transaction settlement, YYYYMMDD format, present only if transaction is waiting for settlement or is settled.
signature	String	Extension signature, BASE64 encoded.

Example of a response to payment/status call with the trxDates extension:

{
  "dttm": "20151119113916",
  "signature": "base64-encoded-response-signature",
  "payId": "e80cfaedc3a85BD",
  "resultCode": 0,
  "resultMessage": "OK",
  "paymentStatus": 7,
  "authCode": "453708",
  "extensions": [
    {
      "extension": "trxDates",
      "dttm": "20151119113916",
      "createdDate": "2016-04-12T12:06:20.848Z",
      "authDate": "160412100635",
      "settlementDate": "20160412",
      "signature": "base64-encoded-extension-signature"
    }
  ]
}

The cryptographic signature calculation is based on the string of parameters in exactly the same order as listed in the specification (see above).

trxDates|20151119113916|2016-04-12T12:06:20.848Z|160412100635|20160412

Note: The signature of the core parameters remains unchanged. The extensions item does not affect the calculation of the payment/status response. Each extension has its own signature.

Extension signature and its validation uses the same algorithm SHA1withRSA (for API 1.7 and older) or SHA256withRSA (for API 1.8 and newer).