394114 Report Types v1.6 Dev

8/13/2019 394114 Report Types v1.6 Dev

1/12The information contained in this document is proprietary and confidential Docdata Payments.

All product names referenced herein are trademarks of their respective companies.


2/12

CONTENTS

1. Introduction

2. Report Type: txt simple

!. Report Type: txt simple2

". Report Type: xml std

#. Report Type: xml ext

$. Report Type: xml all

The information contained in this document is proprietary and confidential Docdata Payments. All product names referenced herein are trademarks of their respective companies.


3/12

1. Introduction An important step in the inte%ration &ith Docdata Payments is retrievin% the status report of a payment

cluster. This document descri'es the different report types &hich are availa'le &ithin the Docdata

Payments system. Please note that Docdata Payments does not allo& pollin% of status information(

therefore the )tatus *han%e +otification )ervice must 'e used for retrieval of status information only.

This procedure is descri'ed in the Inte%ration ,anual.

It is also important to inte%rate the parameters 'y name and not 'y position. Inte%ration 'ased on

position may lead to pro'lems if a parameter is added to a specific report type. The parameters that are

send- differ per payment method- especially for the more detailed report types. or example- parameters

concernin% cardholder information are included &ith credit card transactions- 'ut are not sent in the case

of a 'ank transfer.

/hen you su'mit the command status payment cluster you should specify &hich report type you &ant

to use. The five different report types that &e send are the follo&in%:

0 txt simple(

0 txt simple2(

0 xml std(

0 xml ext(0 xml all.

An example of a status payment cluster- &here the report type xml std is selected- can 'e found

'elo&:

This %uide makes reference to Payment )tatuses- more information can 'e found on our support site or

'y clickin% on the a'ove link.


https: test.tripledeal.com ps com.tripledeal.paymentservice.servlets.Payment)ervice

command3status payment cluster4merchant name3&e'shop nl4merchant pass&ord3pass&

ord4payment cluster key3567175"*"DA85*2698$9*" "!2D*!66"12$A9 #!8 " A689 #

A 229D29"554report type3xml std


4/12

2. Report Type: txt simpleThe first and most simple report type is called txt_simple . This report only contains an A)*II text &ith

the letters ;+< or ;=completely? paid and/or not all the statuses of the payments are set to

paid and/or the considered safe period has not yet expired for one of the payments.

= The payment cluster has 'een paid completely and for all the payments in the payment

cluster the considered safe period has expired.

N


5/12

!. Report Type: txt simple2The other simple report type is txt_simple2 . This report contains t&o letters &hich are either a ;+< or a

;=


6/12

". Report Type: xml std A more detailed report type is the standard xml report type xml_std . The parameters that are included in

this report are sho&n 'elo&:

Parameter Description

payment cluster process The status of the payment cluster process.

last partial payment process The status of the last started payment process

last partial payment method The payment method of the last started payment process.

payout process The status of the payout process.

meta considered safe @aria'le that sho&s if the payment is considered safe.

meta char%ed 'ack This field is no lon%er used and &ill al&ays sho& a value of +.

meta amount received The amount received 'y the Docdata payment service from the

client.

An example of an xml_std report is sho&n 'elo&:


xml version3B1.6B encodin%3BCT 0 B

0 status payment cluster

0 status

payment cluster process started payment cluster process

last partial payment process ne& last partial payment process

last partial payment method accept%irone&0nl0

nl% last partial payment method

payout process ne& payout process

meta considered safe false meta considered safe

meta char%ed 'ack + meta char%ed 'ack

meta amount received none meta amount received

status

status payment cluster


7/12

#. Report Type: xml ext Another more detailed report type is the xml extended report type xml_ext . Please note that the actual

parameters that are send- differ per payment method dependin% on the information provided 'y the

particular financial institution. The most common parameters that are included in this report are sho&n

'elo&:



last partial payment process The status of the last started payment process.





meta amount received The amount received 'y the docdata payment service from the

client.

payments The payment information of every partial payment- includin%

payment id- method- method0reada'le and state.

risk The accumulative risk score of all payment risk checks.E

E This parameter is only presented &hen the risk checks functionality is ena'led for the specific account.



8/12

An example of an xml_ext report is sho&n 'elo&:


xml version3B1.6B encodin%3BCT 0 B 0 status payment cluster0 status

payment cluster process paid payment cluster processlast partial payment process paid last partial payment processlast partial payment method direct0'anktransfer0nl last partial payment methodpayout process started payout processmeta considered safe true meta considered safemeta char%ed 'ack + meta char%ed 'ackmeta amount received paid meta amount received

status0 payments0 payment id3B155 !5!6"!B method3Bdirect0'anktransfer0nlB method0reada'le3BFver'oekin% +ederland >direct?B state3BpaidB0 reason0 GH*DATAH12!"#$9 A+8 DF8 DI8,8+ A++CAJ )C7)*RIPTIF+KK

reasonpayment amount 1".55 payment amountpayment currency 8CR payment currency

paymentpayments



9/12

An example of an xml_ext report- risk check included- is sho&n 'elo&:



0 status payment cluster

0 status

payment cluster process paid payment cluster process

last partial payment process paid last partial payment proces

last partial payment method ems0mc0ssl0testshop nl last partial payment method

payout process started payout process

meta considered safe true meta considered safe


meta amount received paid meta amount received

status

0 payments

0 payment 'incountry3B+JB capture 'atch id3B!661#!!1B id3B155 6 #19$B mcsc3ByB

method3Bems0mc0ssl0testshop nlB method0reada'le3B,astercardB

refund 'atch id3BBrisk3B96Bstate3BpaidB transaction reference nr3B"#"9#"!5B

ucaf3BfalseB visa !ds3BfalseB0 reason 0 GH*DATAHauthoriLed 'y issuer KK

reason

payment amount 1".55 payment amount

payment currency 8CR payment currency

payment

payments



10/12

$. Report Type: xml allThe most detailed report type is the report type xml_all . This report type also includes- in case of a credit

card payment- the last " di%its of the credit card. The most common parameters that are included in this

report are sho&n 'elo&:



last partial payment process The status of the last started payment process.


cluster amount Amount of the payment cluster.

cluster currency *urrency of the payment cluster.




meta amount received The amount received 'y the docdata payment service from the

client.

Payments The payment information of every partial payment- includin%

payment 'incountry- id- method- method0reada'le- reason-

payment amountpayment currency- pid and id value- 'ank

account information- holder information- last " di%its of credit

card and state. Fnly applica'le information is sho&n.

Risk The accumulative risk score of all payment risk checks.E

E This parameter is only presented &hen the risk checks functionality is ena'led for the specific account.



11/12

An example of an xml_all report is sho&n 'elo&:



status payment cluster status

payment cluster process paid payment cluster process

last partial payment process paid last partial payment process

last partial payment method ems0mc0ssl0testshop nl last partial payment method

cluster amount 1".55 cluster amount

cluster currency 8CR cluster currency

payout process started payout process

meta considered safe true meta considered safe


meta amount received paid meta amount received

status

0 payments

0 payment 'incountry3B+JB capture 'atch id3B!661#!!1B id3B155 6 #19$B mcsc3ByB

method3Bems0mc0ssl0testshop nlB method0reada'le3B,astercardB refund 'atch id3BB

state3BpaidB transaction reference nr3B"#"9#"!5B

0 reason0 GH*DATAHauthoriLed 'y issuerKK

reason

payment amount 1".55 payment amount

payment currency 8CR payment currency


12/12

0 payment0info

pid value3Bpid155 6 #19$tB

id value3B155 6 #19$B

holder name value3BdoeB

holder Lipcode value3B1611 AAB

holder city value3BDiemenB

holder country value3B+JB

card country value3B+JB

mcsc value3ByB

PA+ last" value3B#666B

payment0info

payment

payments


Documents

394114 Report Types v1.6 Dev