PX POST is designed to handle transactions using a HTTPS Post Request. The XML is generated at the client site and sent to https://sec.paymentexpress.com/pxpost.aspx.
There is no DPS software needed on the client side, which makes it platform and language independent. This allows for greater flexibility & interoperability.
- No DPS Software needed
- Multiple Account Selection
Transactions can be redirected to different merchant accounts depending on the credentials (Username/Password) that is specified with each transaction.
- Risk Management Rules can be enabled
- Optional reference fields for reconciliation and holding of information that will appear on transaction reports.
- Multi-Currency Support
- SSL V3.0 supported only
Transaction variables are posted to pxpost.aspx in xml form.
||Amount of Transaction (dddddd.cc)
||Card holder's name
||Needs to be generated to add a card for recurring billing and sent again when rebilling transactions.
||Card Verification number. This number is found on the back of a credit card in the signature panel - it is different from the embossed card number and provides an additional safety check.
||This field is used as a CVC presence indicator. It is provided by the card acceptor to indicate availability of the CVC value on the card. Values are 0, 1, 2 & 9.
||Expiry Date on Card
||The BillingId generated by DPS when adding a card for recurring billing. Needed for rebilling transactions when you don't use your own BillingId.
||Output from an original transaction request. Is a required field to do second stage transactions like Refund and Complete.
||Needed for recurring billing transactions when adding a card to the DPS system. Set element to 1 for true and 0 for false
||You will need to specify a three-character currency code here.
||Optional Reference to Appear on Transaction Reports Max 64 Characters
||Username of Account (Supplied by Dps)
||Password of Account (Supplied by Dps)
||'Purchase', 'Auth', 'Complete', 'Refund', 'Validate'
||Optional Free Text
||Optional Free Text
||Optional Free Text
||Used for checking the status of a transaction
||Address Verification System property. Values are 1 (Enable Verification), 0 (Disable Verification).
||Address Verification System property. Values are 0,1 & 2.
|0 - Don't check AVS details with acquirer, but pass them through to Payment Express only.
|1 - Attempt AVS check. If the acquirer doesn't support AVS or is unavailable, then transaction will proceed as normal. If AVS is supported it will check the transaction and give the result.
|2 - The transactions needs to be checked by AVS, even if isn't available, otherwise the transaction will be blocked.
||Address Verification System property. Post Code that is listed on the customer's bank statement
||Address Verification System property. Address that is listed on the customer's bank statement.
||The Issue date of the customer's credit card, if Issuer requires this field to be present.
||The Issue Number of your credit card if Issuer requires this field to be present.
||Extracted from Track2 of credit card.
The Response to the POST is in XML form. The status of a transaction is indicated by the Authorized element (0 = Declined, 1 = Accepted).
Sample XML Response
In the following example, a transaction for $1.23 is requested for cardholder A Anderson, card number is 4111111111111111, Expiry date is Oct 2010, Merchant Reference for the transaction is "Test Transaction".
<Transaction success="1" reco="00" responseText="APPROVED" pxTxn="true">
<CardHolderHelpText>The Transaction was approved</CardHolderHelpText>
<CardHolderResponseDescription>The Transaction was approved</CardHolderResponseDescription>
<MerchantHelpText>The Transaction was approved</MerchantHelpText>
<MerchantResponseDescription>The Transaction was approved</MerchantResponseDescription>
||Authorisation code given back from the bank for that transaction
||1 if transaction successful - 0 if declined or unsuccessful
||CVC / CVV2 Result Code associated with the result of the CVC validation
||Date transaction will be settled to Merchant Bank Account in YYYYMMDD format
||Required for refund and complete transactions.
||Contains the BillingId generated by DPS when adding a card for recurring billing.
||A more detailed explanation of the response from the bank
||2 character response code
||Response Text associated with ResponseCode
||1 if the result of the transaction could not be determined. See the Exception Handling section.
||1 if transaction successful - 0 if declined or unsuccessful. Will be the same value as Authorized
Checking the Status
of a Txn
If you didn't receive a response to your Post, or if StatusRequired was set to 1 in the response, then you must send another Post to request the status of the transaction. For this function to work you will need to send up a TxnId with your origninal transaction. TxnId must be a unique value for each transaction. It can be up to 16 characters long.
XML Format of a transaction status Post:
Character data sent via PX Post must be well formatted XML. For example, the following is invalid XML:
<CardHolderName>Bill & Son</CardHolderName>
<MerchantReference>Abc >> 123</MerchantReference>
Payment Express will be unable to read this XML and will return an error. If there is a possibility that a value will contain invalid characters (such as '&' in the cardholder name), please format the value using "HtmlEncoding".
The above example should be formatted as follows:
<CardHolderName>Bill & Son</CardHolderName>
<MerchantReference>Abc >> 123</MerchantReference>
Amount (input)Datatype: String Max 13 characters
Total Purchase, Refund, Auth or Completion amount. Format is d.cc where d is dollar amount (no currency indicator) and cc is cents amount. for example, $1.80 (one dollar and eighty cents) is represented as "1.80", not "1.8". A string value is used rather than the conventional Currency Datatype to allow for easy integration with Web applications. The current maximum value allowable is $99,999.99. Note that acquirer or card limits may be lower than this amount. When submitting transactions for currencies with no decimal division of units such as JPY the AmountInput must be in an appropriate format e.g. "10".
AuthCode (input) Datatype: String Max 22 characters
Authorization code returned for approved transactions.
Authorized (output) Datatype: Boolean
Indicates if the transaction was authorized or not. Either False (0) or True (1)
BillingId (input) Datatype: String Max 32 characters
If a token based billing transaction is to be created, a BillingId has to be supplied. This is an identifier generated by the merchant application that is used to identify a customer or billing entry and can be used as input instead of card number and date expiry for subsequent billing transactions. To add a BillingId in the transaction request the EnableAddBillCard element needs to be present and set to 1 (true). Upon rebilling this will need to be set to 0 (false).
CardHolderName (input)Datatype: String Max 64 characters
The cardholder name as it appears on customer card. Optional and may be left blank.
CardNumber (input) Datatype:String Max 20 characters
The card number. No leading or embedded blanks are permitted. Must contain a numeric value.
Cvc2 (input) Datatype: String Max 4 characters
Card Verification Code 2 number. Some payment cards are issued with additional identifying information. These cards will have the account number printed on the signature panel of the card followed by a three or four digit value. This value is generated by the issuing bank and can be verified by the bank. Payment card brands have varying names for the value:
American Express: Four-digit batch code (4DBC)
MasterCard: Card Verification Code 2 (CVC2)
Visa: Card Verification Value 2 (CVV2)
Supplying this value provides an indication of that the person participating in a transaction had physical possession of the card at some point in time.
Cvc2Presence (input) Datatype: INT
CVC Presence Verification. Values are 0, 1, 2 & 9.
Merchant to send DPS a presence indicator within "Cvc2Presence" field in the transaction request to one of the below:
0 - You (MERCHANT) have chosen not to submit CVC
1 - You (MERCHANT) have included CVC in the Auth / Purchase
2 - Card holder has stated CVC is illegible.
9 - Card holder has stated CVC is not on the card.
The CVC result code indicate the following:
||You will want to proceed with transactions for which you have received an authorisation approval. A CVC match indicates the values provided matches the Issuing Banks details
||CVC did not match.
||You may want to follow up with the cardholder to verify the CVC value before completing the transaction, even if you have received an authorisation approval. The CVC details provided by the Cardholder do not match their Issuing Banks details
||CVC request not processed.
||Issuing Bank is unable to process CVC at this time
||CVC should be on the card, but merchant has sent code indicating there was no CVC.
||You may want to follow up with the cardholder to verify that the customer checked the correct location for the CVC. If the transaction is Approved you may also wish to consider not fulfilling the transaction
||Issuer does not support CVC.
||The card Issuing bank does not support CVC process
DateExpiry (input) 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.
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.
DpsBillingId(input)Datatype: String Max 16 characters
When output, contains the Payment Express generated BillingId. Only returned for transactions that are requested by the application with the EnableAddBillCard value set to 1 (true) indicating a token billing entry should be created.
DpsTxnRef (input/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 specifiy a transaction for refund without supplying the original card number and expiry date. The DpsTxnRef value returned by the original approved Auth transaction must be supplied also when doing a complete transaction.
EnableAddBillCard (input) Datatype: Boolean
To automatically add a card for subsequent billing purposes, set this to 1 (true). When generating a Billing Transaction for a previously loaded BillingId or DpsBillingId, EnableAddBillCard must be 0 (false).
DateStart (input) Datatype: String Max 4 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.
IssueNumber (input) Datatype: INT
The Issue Number of your credit card if Issuer requires this field to be present.
EnableAvsData (input) Datatype: INT
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.
AvsPostCode (input) Datatype: String Max 20 characters
Address Verification System property. Post Code that is listed on the customer's bank statement.
AvsStreetAddress (input) Datatype: String Max 60 characters
Address Verification System property. Address that is listed on the customer's bank statement.
AvsAction (input) Datatype: INT
Address Verification System property. Values are 0, 1 & 2.
0 - Don't check AVS details with acquirer, but pass them through to Payment Express only.
1 - Attempt AVS check. If the acquirer doesn't support AVS or is unavailable, then transaction will proceed as normal. If AVS is supported it will check the transaction and give the result.
2 - The transactions needs to be checked by AVS, even if isn't available, otherwise the transaction will be blocked.
3 - AVS check will be attempted and any outcome will be recorded, but ignored i.e. transaction will not be declined if AVS fails or unavailable.
The value will most likely be 1 for most circumstances.
InputCurrency (input) 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. Please check here to see an updated list. All other banks can only transact in their home currency. Valid values for Currency are:
||United Kingdom Pound
||Hong Kong Dollar
||New Zealand Dollar
||United States Dollar
||Solomon Islands Dollar
||Papua New Guinea Kina
MerchantReference (input) Datatype: String Max 64 characters
Free text to appear on transaction reports.
PostPassword (input) Datatype: String Max 32 characters
Used with PostUsername 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.
PostUsername (input) Data type: String Max 32 characters
Used with PostPassword 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.
ReCo (Response Code) (output) Datatype: String Max 2 characters
The client application should not interpret the Response Code property contents - it is provided as informational only. TheAuthorized property determines if the the transaction was successful or not.
RmReason (output) Datatype: String Max 255 characters
Risk management rule response Text
RmReasonId (output) Datatype: String Max 16
Risk Management Rule ID
RiskScore (output) Datatype: Int
The risk score associated with the transactions.
RiskScoreText (output) Datatype: String Max 2048 characters
The risk score text provides some meaningful text about the rick management rules that were hit and whether they caused the transaction to be blocked. Each rule is separated by a ','.These are followed by the credit card country of the cardhoder and the IP Country of the cardholder.
RM Rule1 Hit Not Blocked, RM Rule2 Hit Blocked, CCC=NZ IPC=AU
StatusRequired (output) Datatype: Boolean
1 - If transaction result is unknown
0 - If transaction result is in the response. See the Exception Handling section.
Success (output) Datatype: Boolean
1 - If transaction successful
0 - If declined or unsuccessful. Will be the same value as Authorized
TxnData1, TxnData2, TxnData3 (input) Datatype: String Max 255 characters
Optional free text fields. Usually assigned at origin website.
TxnId(input/output) Datatype: String Max 16 characters
Input: contains a unique, merchant application generated value that uniquely identifies the transaction. If TxnId is used, you can check the status of a transaction. Where possible it is recommended that the merchant application sets this value.
TxnType (input) Datatype: String
||Authorizes a transactions. Must be completed within 7 days using the "Complete" TxnType.
||Completes (settles) a pre-approved Auth Transaction. The DpsTxnRef value returned by the original approved Auth transaction must be supplied.
||Purchase - Funds are transferred immediately.
||Refund - Funds transferred immediately. Must be enabled as a special option.
||Validation Transaction. Effects a $1.00 Auth to validate card details including expiry date. Often utilised with the EnableAddBillCard property set to 1 to automatically add to Billing Database if the transaction is approved.
Track 2 DataType: String Max 37 characters
Extracted from Track2 of credit card. Numeric with an equal sign.
When submitting encrypted track2 data the encrypted data sits between the ";" and "?" sentinels. Example:
Payment Express supports Auth/Completion. An "Auth" transaction verifies that funds are available for the requested card and amount and reserves the specified amount. A "Completion" transaction is sent at a later date to cause funds transfer for the previously authorised amount, or a smaller amount if the total original value is no longer required. This transaction set is useful when the merchant needs to ensure that funds up to a certain limit are available but the actual total amount is not yet known or goods or services have not yet been delivered.
Set TxnType to "Auth" for for the amount to be authorised. The Auth response contains a DpsTxnRef. The funds are not transferred from the cardholder account.
After a successful Authorization transaction, but within 7 days maximum, a "completion" (TxnType="Complete") transaction must be sent containing the DpsTxnRef returned by the "Auth" transaction.
Token Billing allows for regular billing of a cardholder card, under the control of the merchant, without requiring the merchant to either store sensitive card data securely or to obtain credit card details every time a new payment is requested. This functionality is implemented by proving the ability for a merchant to request payment express to capture and store credit card number and expiry date and to link these stored details to a merchant supplied "BillingId". The BillingId is a 32 character field that contains a reference that is unique to the merchant's customer, that will be associated with the credit card information stored securely at Payment Express. This is undertaken during the Setup Phase. For subsequent charges to the card (Rebill Phase), the merchant does not need to supply the card number or expiry date, only the BillingId originally associated during the Setup Phase
A setup phase involves loading a card into Payment Express. Optionally the setup phase can include an online $1.00 authorisation (Validate) transaction which will determine that the card is valid and not on hot or stolen card lists and that it has the correct expiry date.
Customers will typically integrate directly into their call centre or web application for the setup phase.
To add a card for future rebilling, send a new transaction request with the following properties:
CardHolderName (optional - strongly recommended)
EnableAddBillCard(Set to true when adding a card)
BillingId (optional - included when generating own billing id. Else, can use returned DpsBillingId determined by Payment Express)
The merchant application or Batch processor requests a new transaction and supplies the appropriate BillingId, or DpsBillingId a MerchantReference which appears on reports and the amount to be charged. 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.
CardNumber2 is a token generated by DPS and associated with card details supplied. It is 16 numeric characters and conforms to a Luhn "mod 10" algorithm. This makes it ideal for storage within the database in place of a card number where the value is validated against checks which might normally be made against credit card numbers. A CardNumber2 value is always unique for a given card number. Should a card number be presented for tokenization multiple times the same CardNumber2 value will be returned.
CardNumber2 tokens are generated for all transactions once enabled by DPS (please contact your DPS account manager to discuss). The token number will be returnd in the "CardNumber2" property of the transaction result.
Charging a CardNumber2 token involves a request from the merchant application or Batch processor including an appropriate cardNumber2, a TxnType (Purchase) and the amount to be charged (an optional MerchantReference can be added for reporting purposes). EnableAddBillCard value will need to 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.
CardNumber2 transactions use the card expiry date stored with the token regardless of whether one is passed through in the transaction data. Once a successful transaction is processed using the real card number accociated with a CardNumber2 token the expiry date stored with this token will be updated to that which was used to process the transaction. If your client application displays details of stored tokens to cardholders eg: masked number and expiry date, then it is advisible upon a successful transaction for the merchant application to update the expiry date that is stored with the generated token.
PX Post is capable of handling refunds (credit) transactions, however you will need to match the original Purchase or Complete transaction for this to happen. The matching is done with the DpsTxnRef given from the response of a purchase or complete transaction. You are able to do multiple refund transactions to the maximum amount of the original matched transaction.
The TxnType will be Refund.
The Payment Manager is provided to merchants with all integrated solutions by DPS, so there is a ready built interface to handle refund transactions already. However, if you wish to integrate refunds into your own interfaces the following input properties need to be provided for a refund transaction:
TxnType = Refund
The client application should not interpret the ReCo (Response Code) property contents - it is provided as information only. The Success property determines if the the transaction was successful or not.
The following table provides assistance in troubleshooting errors.
||No such user for PXPost. Please contact DPS to confirm your account information.
||Blank password for PX Post. Please contact DPS to confirm your account information.
||Invalid Password for PxPost. Please contact DPS to confirm your account information.