PxFusion

3D Secure Support

Payment Express have implemented a MPI (Merchant Plug-In) that securely allows an automatic 3D Secure redirection with no development cost or hassle to the merchant whatsoever.

The MPI is compliant with the latest 3D Secure technology. Card schemes estimate that with these new security mechanisms in place, merchants will experience an increase in sales generated, lower operational costs and fewer charge backs due to fraudulent transactions.

Note to support 3DS on the account, please ensure merchants contact our Sales and Support team to enable live 3D Secure with the 3DS settings and credentials which are usually supplied by the merchant's bank or acquirer. Usually 3D Secure validation is tested on the live gateway account with the live credit card details.

WSDL

A web services descriptor language (WSDL) file is an XML document that describes the arguments accepted by a specific web service as well as the methods and properties supported by that service. The WSDL specification provides the grammar and syntax rules for WSDL files. For the WSDL schema please see https://sec.paymentexpress.com/pxf/pxf.svc?wsdl or https://uat.paymentexpress.com/pxf/pxf.svc?wsdl.

POST https://sec.paymentexpress.com/PxF/pxf.svc HTTP/1.1 Content-Type: text/xml; charset=utf-8 SOAPAction: "http://paymentexpress.com/IPxFusion/GetTransactionId" Host: sec.paymentexpress.com Content-Length: 2288 Expect: 100-continue Connection: Keep-Alive <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"> <s:Body> <GetTransactionId xmlns="http://paymentexpress.com"> <username>Username here</username> <password>Password here</password> <tranDetail xmlns:i="http://www.w3.org/2001/XMLSchema-instance"> <amount>1.00</amount> <currency>AUD</currency> <enableAddBillCard>false</enableAddBillCard> <merchantReference>Unique ID here</merchantReference> <returnUrl>https://www.mysite.com/returnpage.php</returnUrl> <txnRef>Unique ID here</txnRef> <txnType>Purchase</txnType> </tranDetail> </GetTransactionId> </s:Body> </s:Envelope>

HTTP/1.1 200 OK Cache-Control: private Content-Length: 530 Content-Type: text/xml; charset=utf-8 Server: Microsoft-IIS/7.5 X-AspNet-Version: 2.0.50727 Date: Wed, 09 Feb 2011 04:16:48 GMT <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"> <s:Body> <GetTransactionIdResponse xmlns="http://paymentexpress.com"> <GetTransactionIdResult xmlns:a="http://schemas.datacontract.org/2004/07/" xmlns:i="http://www.w3.org/2001/XMLSchema-instance"> <a:sessionId>0000060001207174fc003a0a60b12345</a:sessionId> <a:success>true</a:success> <a:transactionId>0000060001207174fc003a0a60b12345</a:transactionId> </GetTransactionIdResult> </GetTransactionIdResponse> </s:Body> </s:Envelope>

Output Elements

A single property named Success is returned in response to the CancelTransaction call.

The card detail input values are set by the user as they complete the fields. The SessionId returned by the GetTransactionId call should be included as the value of a hidden input named 'SessionId' within the form. Payment Express will ignore any extraneous variables included within the data posted by the form. UserTxnData1 - 3 fields will be stored by Payment Express only where no values were passed to Payment Express within the TxnData1 - 3 fields within the GetTransactionId request.

POST https://sec.paymentexpress.com/pxmi3/pxfusionauth HTTP/1.1 Accept: image/gif, image/jpeg, image/pjpeg, application/x-ms-application, application/vnd.ms-xpsdocument, application/xaml+xml, application/x-ms-xbap, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, application/x-shockwave-flash, */* Accept-Language: en-us Content-Type: multipart/form-data; boundary=---------------------------7db1acd0c3c User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; Trident/4.0; SLCC1; .NET CLR 2.0.50727; Media Center PC 5.0; .NET CLR 3.5.30729; MS-RTC LM 8; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E) Accept-Encoding: gzip, deflate Host: sec.paymentexpress.com Content-Length: 794 Connection: Keep-Alive Cache-Control: no-cache Cookie: PXID=; PXID= -----------------------------7db1acd0c3c Content-Disposition: form-data; name="CardNumber" 4111111111111111111 -----------------------------7db1acd0c3c Content-Disposition: form-data; name="ExpiryMonth" 12 -----------------------------7db1acd0c3c Content-Disposition: form-data; name="ExpiryYear" 12 -----------------------------7db1acd0c3c Content-Disposition: form-data; name="CardHolderName" C. Holder -----------------------------7db1acd0c3c Content-Disposition: form-data; name="Cvc2" 999 -----------------------------7db1acd0c3c Content-Disposition: form-data; name="SessionId" 0000060001207174fc003a0a60b12345 -----------------------------7db1acd0c3c Content-Disposition: form-data; name="Action" Add -----------------------------7db1acd0c3c Content-Disposition: form-data; name="Object" DpsPxPay -----------------------------7db1acd0c3c--

<form method="post" enctype="multipart/form-data" action="https://sec.paymentexpress.com/pxmi3/pxfusionauth"> <input type="text" name="CardNum" /> <input type="text" name="ExMnth" /> <input type="text" name="ExYr" /> <input type="text" name="NmeCard" /> <input type="text" name="Cvc2" /> <input type="text" name="IssNum" /> <input type="text" name="UserTxnData1" /> <input type="text" name="UserTxnData2" /> <input type="text" name="UserTxnData3" /> <input type="hidden" name="SessionId" value="0000060001207174fc003a0a60b12345" /> <input type="submit" value="Submit" /> <input type="hidden" name="Action" value="Add" /> <input type="hidden" name="Object" value="DpsPxPay" /> <img src="http://www.paymentexpress.com/images/logos_transparent/paymentexpress.png" alt="Payment Processor" width="236" height="42" /> </form>

Please discuss with our Implementation and Sales team about your tokenisation use cases if you are unsure. The RecurringMode string value should be set based on the merchant’s business case for tokenising.

You can supply your own billing ID in the BillingId field or leave it blank and use the DpsBillingId returned in the response. We also recommend sending the unique txnRef and a merchantReference. This will make searching and identifying tokens/cards much easier.

Setup Token sample GetTransactionId web service call with RecurringMode in extra transaction details fields

POST https://sec.paymentexpress.com/PxF/pxf.svc HTTP/1.1 Content-Type: text/xml; charset=utf-8 SOAPAction: "http://paymentexpress.com/IPxFusion/GetTransactionId" Host: sec.paymentexpress.com Content-Length: 2288 Expect: 100-continue Connection: Keep-Alive <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"> <s:Body> <GetTransactionId xmlns="http://paymentexpress.com"> <username>Username here</username> <password>Password here</password> <tranDetail xmlns:i="http://www.w3.org/2001/XMLSchema-instance"> <amount>1.00</amount> <currency>AUD</currency> <enableAddBillCard>true</enableAddBillCard> <merchantReference>Unique ID here</merchantReference> <returnUrl>https://www.mysite.com/returnpage.php</returnUrl> <transactionDetailsFields xmlns:ns="http://schemas.datacontract.org/2004/07/"> <ns:transactionDetailsField> <ns:fieldName>RecurringMode</ns:fieldName> <ns:fieldValue>credentialonfileinitial</ns:fieldValue> </ns:transactionDetailsField> </transactionDetailsFields> <txnRef>Unique ID here</txnRef> <txnType>Purchase</txnType> </tranDetail> </GetTransactionId> </s:Body> </s:Envelope>

2) Rebill Phase

The merchant application or Batch processor requests a new transaction and supplies the appropriate DpsBillingId or CardNumber2 or BillingId, RecurringMode (to specify the reason for rebilling with the token), MerchantReference (which appears on reports), and the amount to be charged using either PxPost or the Web Service API. EnableAddBillCard value will be set to "False" (or 0) for the rebill phase.

Payment Express retrieves the credit card number and expiry date stored in the Setup Phase and a purchase transaction is formatted and processed to the card acquirer.

Recurring Transactions

If transactions are being processed to an acquirer that supports and is configured for recurring transactions, the Payment Express account can also be setup to process recurring transactions only.

The main advantage of recurring transactions is that the ExpiryDate is not required. This further reduces the amount of data that needs to be stored for a merchant, and bypasses the issue of expired cards.

To setup your Payment Express account for recurring transaction processing only, please contact [email protected] (note: please ensure that your merchant bank account has been setup for recurring transactions).

PaxCarrier,PaxCarrier2,PaxCarrier3,PaxCarrier4,PaxDateDepart, PaxDate,PaxDate3,PaxDate3,PaxDat4,paxTime1,paxTime2,paxTime3,paxTime4, PaxLeg1, PaxLeg2, PaxLeg3, PaxLeg4, paxStopOverCode1, paxStopOverCode2,paxStopOverCode3, paxStopOverCode4, paxClass1, paxClass2, paxClass3, paxClass4, paxFareBasis1, paxFareBasis2,paxFareBasis3, paxFareBasis4, paxFlightNumber1, paxFlightNumber2, paxFlightNumber3, paxFlightNumber4, PaxOrigin,PaxName, PaxTicketNumber and PaxTravelAgentInfo. Sample data: PaxDateDepart = "14122008" PaxName = "Brian Smith" PaxOrigin = "AKL" PaxLeg1 = "SYD" PaxLeg2 = "LAX" PaxLeg3 = "LHR" PaxLeg4 = "AKL" PaxTicketNumber = "0030458343" PaxCarrier = "QB" PaxTravelAgentInfo = "BA1234567890"

CardNumber2 (output) Datatype: String Max 19 characters

A token generated by Payment Express when adding a card for recurring billing. CardNumber2 is a 16 digit number which conforms to a Luhn 'mod 10' algorithm and has a 1-to-1 relationship with the actual card number used. To use CardNumber2 tokens your account must be configured to generate them. Please contact our support team if you intend to use this feature.

Currency (input/output) Datatype: String Max 4 characters

Indicates currency used for this transaction. If blank, currency will be determined by the bank account used which is selected using the Username/Password details. Not all acquirers can support multiple currencies. Valid values for Currency are:

CurrencyId (input) Datatype: String Max 4 characters

Indicates the input currency's numeric ISO currency code.

CurrencyRate (Output) Datatype: String Max 3 characters

Charge rate, if applicable.

Cvc2ResultCode (Output) Datatype: String 1 character

Depending on the response code, the merchant can make a more informed decision on the payment that has taken place. Please see below table for interpretation of response codes:

DateExpiry (output) Datatype: String Max 4 characters

Indicates card expiry date. Format is MMYY where MM is month 01-12 and Year 00-99. do not insert "/" or other delimiter. Not required for Complete or Refund transactions.

DateSettlement (output) Datatype: String Max 8 characters

Indicates Date of settlement (when money will be deposited in Merchant bank account) if this is supported by the Acquirer, otherwise contains the date the transaction was processed in YYYYMMDD format.

DateStart (input) Datatype: String Max characters

The Issue date of the customer's credit card, if Issuer requires this field to be present.

Format is MMYY where MM is month 01-12 and Year 00-99. do not insert "/" or other delimiter.

Used for Maestro/Solo cards.

EnableAddBillCard (input) Datatype: Boolean True/False

If set to "True" (or 1) on input to GetTransactionId, the details necessary to charge the same customer in the future are securely stored. A BillingId may optionally be attached on input. A DpsBillingId is returned. See Token Billing section for details on using this feature.

EnableAvsData (input) Datatype: Boolean True/False

Address Verification System property. Values are 1 (Enable Verification), 0 (Disable Verification). Your bank may require that you use AVS, in which case you will need to set to 1.

EnableMandatoryCVC2 (input) Datatype: Boolean True/False

When enabled, mandates a CVC2 value in the form post, will return a decline if a CVC2 value is not submitted. Note: The PX Fusion account setting may need to be set to enable this. Please contact the Support team to enable this.

EnablePaxInfo (input) Data type: Boolean True/False

Used for Airline Reservation Systems. Enable collection of extended booking data to go through to the acquirer. Value will need to be true (1) if ticket information is included with the transaction.

DpsBillingId (input/output) Datatype: String Max 16 characters

Returned for a successful billing transaction if EnableAddBillCard is set. Supplied as input to rebill a transaction if BillingId is not used. It is not allowed to specify both a BillingId and a DpsBillingId when rebilling a transaction.

DpsTxnRef (output) Datatype: String Max 16 characters

Returned for every transaction. If the transaction was approved, DpsTxnRef can be used as input to a Refund transaction. Used to specify a transaction for refund without supplying the original card number and expiry date.

MerchantReference (input/output) Datatype: String Max 64 characters

Free Text Field for use by merchant (could be order number, customer number etc.).

Password (input) Data type: String Max 64 characters

Used with Username to determine account for settlement. Payment Express clients can be set up with more than one bank account. Each transaction may be designated for a specific account if required.

PaxCarrier (input) Data type: String Max 2 characters

Used for Airline Reservation Systems. Carrier flight information. Alphanumeric.

PaxCarrier2 - 4 (input) Data type: String Max 2 characters

Used for Airline Reservation Systems. Carrier flight information. Alphanumeric.

PaxClass1 - 4 (input) Data type: String Max 1 characters

Used for Airline Reservation Systems. Class flight information. Alphanumeric.

PaxDate2 - 4 (input) Data type: String Max 20 characters

Used for Airline Reservation Systems. Leg depart date flight information. Alphanumeric.

PaxDateDepart (input) Data type: String Max 8 characters

Used for Airline Reservation Systems. Date departing in YYYYMMDD format. Numeric.

paxFareBasis1 - 4 (input) Data type: String Max 6 characters

Used for Airline Reservation Systems. Fare basis flight information. Alphanumeric.

paxFlightNumber1 - 4 (input) Data type: String Max 6 characters

Used for Airline Reservation Systems. Flight number information. Alphanumeric.

PaxLeg1 - 4 (input) Data type: String Max 3 characters

Used for Airline Reservation Systems. Flight number information. Alphanumeric.

PaxName (input) Data type: String Max 20 characters

Used for Airline Reservation Systems. Passenger Name. Alphanumeric.

PaxOrigin (input) Data type: String Max 3 characters

Used for Airline Reservation Systems. Passenger Origin of departure. Alphanumeric.

PaxStopoverCode1 - 4 (input) Data type: String Max 1 characters

Used for Airline Reservation Systems. Stop over code flight information. Alphanumeric.

PaxTicketNumber (input) Data type: String Max 10 characters

Used for Airline Reservation Systems. Passenger Ticket Number. Format: AAATTTTTTTTTTC. AAA is airline code, TTTTTTTTTT (10 chars) is actual ticket number and C is check digit. Numeric.

PaxTime1 - 4 (input) Data type: String Max 4 characters

Used for Airline Reservation Systems. Leg depart time flight information. Alphanumeric.

PaxTravelAgentInfo (input) Data type: String Max 25 characters

Used for Airline Reservation Systems. Travel Agent description field. Also known as the Booking Reference on some of Payment Express screens. Alphanumeric free text field.

ResponseCode (output) Datatype: String Max 2 characters

Response Code generated by Payment Express Server (for locally declined transactions) or by the Card Acquirer (for host originated responses). The ReCo should not be checked by the client application, as these values differ according to acquirer. Use the Success property to check for successful finishing of a transaction. Refer to the Response Codes section for a list of valid response code errors generated by Payment Express.

ResponseText (output) Datatype: String Max 32 characters

Response Text associated with the response code of the transaction

ReturnUrl (input) Datatype: String Max 255 characters

URL (with protocol prefix) that the user will be forwarded to once the card details are submitted (with the session ID appended).

SessionId (output) Datatype: String Max 32 characters

Unique transaction identifier that is returned after a successful GetTransactionId call and used to obtain Transaction results using GetTransaction.

Status (output) Datatype: Integer Max 1 character

The status property contains an integer indicating the status of the GetTransactionId call and transaction associated with it. Possible values for the status property are as follows.

TransactionId (output) Datatype: String Max 32 characters

Unique transaction identifier that is returned after a successful GetTransactionId call and used to obtain Transaction results using GetTransaction.

TransactionDetailsFields (input) Datatype: String

The XML element to define the array of transaction details fields to enhance the usage of sessions and transactions depending on use cases.

TransactionDetailsField (input) Datatype: String

The XML element to define the array item that specifies the fieldName and fieldValue XML elements.

FieldName (input) Datatype: String

Within the element transactionDetailsField, the XML element to specify field's name.

FieldValue (input) Datatype: String

Within the element transactionDetailsField, the XML element to specify field's value after the fieldName XML element.

TxnData1, TxnData2, TxnData3 (input/output): String Max 255 characters

Optional free text fields. Usually assigned at origin website.

TxnRef (input/output) Datatype: String Max 16 characters

A unique identifier provided by your application to uniquely identify the transaction. This is the TxnRef supplied by the client to initiate the transaction, or, if not supplied, a TxnRef value internally generated by Payment Express on return.

TxnType (input/output) Datatype: String Max 8 character

Username (input) Data type: String Max 32 characters

Used with Password to determine account for settlement. Payment Express clients can be set up with more than one bank account. Each transaction may be designated for a specific account if required.