Capture Card Deposit
Every card deposit reaches the
AuthorisedByProvider state after successful authorization (funds reserved but not debited yet). To capture the transaction either the automatic capturing in PXP Financial PaymentService can be used, or the merchant can invoke the executePaymentAction web method with
actionID = 205 (Capture).
Merchant responsibility for Authorisation Reversals (Cancellations)
In case the merchant is not intending to capture the authorised card deposit and therefore no longer requires the amount to be held, the payment must be cancelled to return the amount to the customer’s card. This should be performed as soon as possible after the merchant is aware that it is not required to hold the amount any longer. The cancellation/reversal request will be sent immediately to the issuer and the funds will be available to the cardholder as soon as it is processed.
With this, merchants can ensure that cardholders are not negatively impacted by extended authorization holds against their accounts and that the money can be used for other purchases.
executePaymentActionRequest for capturing a card deposit:
<?xml version="1.0" encoding="utf-8"?> <executePaymentActionRequest xmlns="http://www.cqrpayments.com/PaymentProcessing" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <merchantID>KalixaAcceptDEMO</merchantID> <shopID>KalixaAcceptDEMO</shopID> <paymentID>72dbae7f-5240-402b-aa64-5035a9a3f483</paymentID> <actionID>205</actionID> <remark>Capture Payment TEST</remark> </executePaymentActionRequest>
executePaymentActionResponse for capturing a card deposit:
<?xml version="1.0" encoding="utf-8"?> <executePaymentActionResponse xmlns="http://www.cqrpayments.com/PaymentProcessing" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <statusCode>0</statusCode> <actionResults> <result xsi:type="keyStringValuePair"> <key>lastStateDefinition</key> <value>306</value> </result> </actionResults> </executePaymentActionResponse>
Updated over 4 years ago