* parameter called PaRes (see API manual). These will be needed to complete the payment.
*
* To complete the payment, a PaymentRequest3d should be submitted to the authorise3d action
* of the web service. The request should contain the following variables:
*
* - merchantAccount: This should be the same as the Merchant Account used in the original authorise request.
* - browserInfo: It is safe to use the values from the original authorise request, as they
* are unlikely to change during the course of a payment.
* - md: The value of the MD parameter received from the issuer.
* - paReponse: The value of the PaRes parameter received from the issuer.
* - shopperIP: The IP address of the shopper. We recommend that you provide this data, as
* it is used in a number of risk checks, for example, the number of payment
* attempts and location based checks.
*/
try {
$result = $client->authorise3d(array("paymentRequest3d" => array("merchantAccount" => "YourMerchantAccount", "browserInfo" => array("userAgent" => $_SERVER['HTTP_USER_AGENT'], "acceptHeader" => $_SERVER['HTTP_ACCEPT']), "md" => $_POST['MD'], "paResponse" => $_POST['PaRes'], "shopperIP" => "123.123.123.123")));
/**
* If the payment passes validation a risk analysis will be done and, depending on the
* outcome, an authorisation will be attempted. You receive a
* payment response with the following fields:
* - pspReference: The reference we assigned to the payment;
* - resultCode: The result of the payment. One of Authorised, Refused or Error;
* - authCode: An authorisation code if the payment was successful, or blank otherwise;
* - refusalReason: If the payment was refused, the refusal reason.
*/
print_r($result);
} catch (SoapFault $ex) {
print "<pre>";
print $ex;
print "<pre>";
}
