Diagnose Interface 2 tables


1. REQUEST PARAMETERS WITH TRANSACTION-ID

The POST request should contain the following mandatory components:

  • Test Credentials

EXAMPLE :

Diagnose Request & Response with transaction-id

Diagnose Request

Field NameTypeLengthMandatory?Description
merchantidalphanumeric40 charactersmerchant identification
typealphanumerictx
transactionidnumericempty or transactionidpayment gateway transaction identificationnumeric
signaturehex40 charactersSHA1–HashSignature Calculation

Diagnose Response

Field NameTypeContentDescription
amountnumericempty or amount valueamount
creation_datealphanumericcreation dateDate and time for transaction insert into payment gateway
currencycharempty or currency valuecurrency
custom1alphanumericCustom1Custom 1
error_codealphanumericError Code0-successful, 2000-pending, otherwise-failed
order_idalphanumericempty or orderid valueorderid in the merchant shop system
typecharTypeType

2. REQUEST PARAMETERS WITH ORDER-ID

The POST request should contain the following mandatory components:

  • Test Credentials

EXAMPLE :

  • Diagnose Request & Response with orderid

Diagnose Request

Field NameTypeLengthFormatMandatory?Description
merchantidalphanumeric40 charactersmerchant identification
typecharacterorderid
orderidalphanumericmax 30 charactersorderid in merchant shop system
start_datealphanumeric10 charactersdd.mm.yyyystart time frame
end_datealphanumeric10 charactersdd.mm.yyyyend time frame
signaturehex40 charactersSHA1–HashSignature Calculation

Diagnose Response

Field NameTypeContentDescription
amountnumericempty or amount valueamount
creation_datealphanumericcreation dateDate and time for transaction insert into payment gateway
currencycharempty or currency valuecurrency
custom1alphanumericCustom1Custom 1
error_codealphanumericError Code0-successful, 2000-pending, otherwise-failed
order_idalphanumericempty or orderid valueorderid in the merchant shop system
typecharTypeType

3. REQUEST PARAMETERS WITH TYPE = CAPTURE

The POST request should contain the following mandatory components:

  • Test Credentials

EXAMPLE :

  • Diagnose Request & Response for Capture

Diagnose Request

Field NameTypeLengthFormatMandatory?Description
merchantidalphanumeric40 charactersmerchant identification
typecharactercapture
start_datealphanumeric10 charactersdd.mm.yyyystart time frame
end_datealphanumeric10 charactersdd.mm.yyyyend time frame
signaturehex40 charactersSHA1–HashSignature Calculation

Diagnose Response

Field NameTypeFormatDescription
orderidalphanumericempty or orderid valueorderid in the merchant shop system
transactionidnumericempty or transactionidpayment gateway transaction identification
amountnumericamount or empty valuenumber
currencycharempty or currency valuecurrency
booking_datealphanumericdd.mm.yyyybooking time frame
issue_datealphanumericdd.mm.yyyyissued time frame

4. REQUEST PARAMETERS WITH TYPE = CHB ( CHARGEBACKS)

The POST request should contain the following mandatory components:

  • Test Credentials

EXAMPLE :

  • Diagnose Request & Response for Chargeback

Diagnose Request

Field NameTypeLengthFormatMandatory?Description
merchantidalphanumeric40 charactersmerchant identification
typealphanumericchb
transactionidnumericempty or transactionidpayment gateway transaction identificationnumeric
start_datealphanumeric10 charactersdd.mm.yyyystart time frame
end_datealphanumeric10 charactersdd.mm.yyyyend time frame
signaturehex40 charactersSHA1–HashSignature Calculation

Diagnose Response

Field NameTypeFormatDescription
orderidalphanumericempty or orderid valueorderid in the merchant shop system
transactionidnumericempty or transactionidpayment gateway transaction identification
amountnumericamount or empty valuenumber
currencycharempty or currency valuecurrency
booking_datealphanumericdd.mm.yyyybooking time frame
issue_datealphanumericdd.mm.yyyyissued time frame

5. REQUEST PARAMETERS WITH TYPE = PENDING

The POST request should contain the following mandatory components:

  • Test Credentials

EXAMPLE :

  • Diagnose Request & Response for Pending

Diagnose Request

Field NameTypeLengthFormatMandatory?Description
merchantidalphanumeric40 charactersmerchant identification
typecharacterpending
start_datealphanumeric10 charactersdd.mm.yyyystart time frame
end_datealphanumeric10 charactersdd.mm.yyyyend time frame
signaturehex40 charactersSHA1–HashSignature Calculation

Diagnose Response

Field NameTypeFormatDescription
orderidalphanumericempty or orderid valueorderid in the merchant shop system
transactionidnumericempty or transactionidpayment gateway transaction identification
amountnumericamount or empty valuenumber
currencycharempty or currency valuecurrency
booking_datealphanumericdd.mm.yyyybooking time frame
issue_datealphanumericdd.mm.yyyyissued time frame

6. REQUEST PARAMETERS WITH TYPE = FAILED

The POST request should contain the following mandatory components:

  • Test Credentials

EXAMPLE :

  • Diagnose Request & Response for Failed

Diagnose Request

Field NameTypeLengthFormatMandatory?Description
merchantidalphanumeric40 charactersmerchant identification
typecharacterfailed
start_datealphanumeric10 charactersdd.mm.yyyystart time frame
end_datealphanumeric10 charactersdd.mm.yyyyend time frame
signaturehex40 charactersSHA1–HashSignature Calculation

Diagnose Response

Field NameTypeFormatDescription
orderidalphanumericempty or orderid valueorderid in the merchant shop system
transactionidnumericempty or transactionidpayment gateway transaction identification
amountnumericamount or empty valuenumber
currencycharempty or currency valuecurrency
booking_datealphanumericdd.mm.yyyybooking time frame
issue_datealphanumericdd.mm.yyyyissued time frame

7. REQUEST PARAMETERS WITH TYPE = RETRIEVAL-REQUEST

The POST request should contain the following mandatory components:

  • Test Credentials

EXAMPLE :

  • Diagnose Request & Response for Retrieval-request

Diagnose Request

Field NameTypeLengthFormatMandatory?Description
merchantidalphanumeric40 charactersmerchant identification
typecharacterretrieval_request
start_datealphanumeric10 charactersdd.mm.yyyystart time frame
end_datealphanumeric10 charactersdd.mm.yyyyend time frame
signaturehex40 charactersSHA1–HashSignature Calculation

Diagnose Response

Field NameTypeFormatDescription
orderidalphanumericempty or orderid valueorderid in the merchant shop system
transactionidnumericempty or transactionidpayment gateway transaction identification
amountnumericamount or empty valuenumber
currencycharempty or currency valuecurrency
booking_datealphanumericdd.mm.yyyybooking time frame
issue_datealphanumericdd.mm.yyyyissued time frame

8. REQUEST PARAMETERS WITH TYPE = REFUND

The POST request should contain the following mandatory components:

Test Credentials

EXAMPLE :

  • Diagnose Request & Response for Refund

Diagnose Request

Field NameTypeLengthFormatMandatory?Description
merchantidalphanumeric40 charactersmerchant identification
typecharacterrefund
start_datealphanumeric10 charactersdd.mm.yyyystart time frame
end_datealphanumeric10 charactersdd.mm.yyyyend time frame
signaturehex40 charactersSHA1–HashSignature Calculation

Diagnose Response

Field NameTypeFormatDescription
orderidalphanumericempty or orderid valueorderid in the merchant shop system
transactionidnumericempty or transactionidpayment gateway transaction identification
amountnumericamount or empty valuenumber
currencycharempty or currency value
error_codealphanumericError code
issue_datealphanumericdd.mm.yyyy
refund_datealphanumericdd.mm.yyyy

Here is a list of the possible types one can get in the response

type=invoce -> authorized
type=booked -> captured
type=refund
type=chargeback
type=retrieval_request
type=partial booking -> partial capture
type=reversal

Note: The end_date is inclusive, e.g. if you want to get a list of all transactions imported into the payment gateway on the 1st of May 2015 for example, your start_date and end_date would both be <01.05.2015>.