It is possible that in certain situations additional, changed or other information is supplied in the XML Transfer Report. An important example of these special situations are outlined below.
Note: It is quite common for funds to go into a DISPUTE_FUNDS_HELD and DISPUTE_FUNDS_RELEASED status. This is because anything that does not go direct to a chargeback status is held in a DISPUTE_FUNDS_HELD state.
Where a PayPal transaction is disputed it's either immediately CHARGED_BACK or we move the funds associated with the transaction into a dispute reverse. This is represented by the journalType DISPUTE_FUNDS_HELD.
Here is an example:
<orderStatusEvent orderCode="ORDER_CODE"> <!--Will contain the order code used in the request-->
<payment>
<paymentMethod>PAYPAL-EXPRESS</paymentMethod>
<amount value="14100" currencyCode="EUR" exponent="2" debitCreditIndicator="credit"/>
<lastEvent>SETTLED</lastEvent>
<balance accountType="SETTLED_BIBIT_NET">
<amount value="13802" currencyCode="EUR" exponent="2" debitCreditIndicator="credit"/>
</balance>
<balance accountType="SETTLED_BIBIT_COMMISSION">
<amount value="298" currencyCode="EUR" exponent="2" debitCreditIndicator="credit"/>
</balance>
</payment>
<journal journalType="DISPUTED_FUNDS_HELD" description=" ">
<bookingDate>
<date dayOfMonth="18" month="9" year="2012" hour="8" minute="24" second="14"/>
</bookingDate>
<accountTx accountType="SETTLED_BIBIT_NET" batchId="57">
<amount value="13802" currencyCode="EUR" exponent="2" debitCreditIndicator="debit"/>
</accountTx>
</journal>
</orderStatusEvent>
The funds will then either be moved out of the dispute reserve to be released back to you, the merchant, or to be CHARGED_BACK. This movement out of the disputes reserve is represented by the journalType DISPUTED_FUNDS_RELEASED. Here is an example:
<orderStatusEvent orderCode="ORDER_CODE"> <!--Will contain the order code used in the request-->
<payment>
<paymentMethod>PAYPAL-EXPRESS</paymentMethod>
<amount value="14100" currencyCode="EUR" exponent="2" debitCreditIndicator="credit"/>
<lastEvent>SETTLED</lastEvent>
<balance accountType="SETTLED_BIBIT_NET">
<amount value="13802" currencyCode="EUR" exponent="2" debitCreditIndicator="credit"/>
</balance>
<balance accountType="SETTLED_BIBIT_COMMISSION">
<amount value="298" currencyCode="EUR" exponent="2" debitCreditIndicator="credit"/>
</balance>
</payment>
<journal journalType="DISPUTED_FUNDS_RELEASED" description=" ">
<bookingDate>
<date dayOfMonth="18" month="9" year="2012" hour="8" minute="24" second="14"/>
</bookingDate>
<accountTx accountType="SETTLED_BIBIT_NET" batchId="57">
<amount value="13802" currencyCode="EUR" exponent="2" debitCreditIndicator="credit"/>
</accountTx>
</journal>
</orderStatusEvent>
The structure of the CHARGED_BACK journalType is different for PayPal transactions. Here is an example:
<orderStatusEvent orderCode="ORDER_CODE"> <!--Will contain the order code used in the request-->
<payment>
<paymentMethod>PAYPAL-EXPRESS</paymentMethod>
<amount value="14100" currencyCode="EUR" exponent="2" debitCreditIndicator="credit" />
<lastEvent>CHARGED_BACK</lastEvent>
</payment>
<journal journalType="CHARGED_BACK" description="">
<bookingDate>
<date dayOfMonth="18" month="9" year="2012" hour="8" minute="24" second="14"/>
</bookingDate>
<accountTx accountType="SETTLED_BIBIT_COMMISSION">
<amount value="298" currencyCode="EUR" exponent="2" debitCreditIndicator="debit" />
</accountTx>
<accountTx accountType="SETTLED_BIBIT_NET" batchId="1288">
<amount value="13802" currencyCode="EUR" exponent="2" debitCreditIndicator="debit" />
</accountTx>
</journal>
</orderStatusEvent>
WorldPay operates PayPal through two R level service models, which means that there are a number of differences in comparison to other payment methods. Key differences are:
WorldPay is reliant upon PayPal reporting the status of a particular transaction. This means that it is possible to see three separate events relating to a single transaction that is ultimately CHARGED_BACK in a Transfer Report:
| Guide feedback?
Email us at: guides@worldpay.com |
    
|
| © Worldpay 2018. All rights reserved. |
