Output Properties

DoProcessResponse (Response)

DoProcessResponse is used to decode the result of the transaction after it has been submitted.

Input Properties

Output Properties

Properties

TxnType  (input) Datatype: BSTR 

Registry Settings

Several registry settings are read by PXACCESS. All Subkeys are registered in the path:

HKEY_LOCAL_MACHINE\SOFTWARE\DirectPaymentSolutions\PXACCESS\KEYS

The following path is the URL of the Hosted Payments Page for the response redirect call. This should only be changed when talking in conjunction with DPS support.

HKEY_LOCAL_MACHINE\SOFTWARE\DirectPaymentSolutions\PXACCESS\SERVER

Fail Proof Result Notification

It is highly recommended that Fail Proof result notification is configured by Payment Express. This setting (EnablePost Response) set at Payment Express host, ensures that the following process occurs for every transaction:

Transaction is performed via hosted payment page. As soon as the transaction is complete, but prior to the results being displayed for the user, a background process issues a HTTP GET to the merchant specified payment page response (UrlSuccess or UrlFail). If the merchant web site is unreachable or returns a response other than "200 OK", the GET is retried every minute for 30 minutes, thereafter every 15 minutes until a preset limit is exhausted. Merchant sites should therefore allow for the possibility that their application could receive more than one notification for the same transaction. The merchant application can distinguish which transaction the response is for by checking the TxnId value.

Auth-Completion

Overview

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.

Operation

1) Authorisation

Set TxnType to "Auth" for the amount to be authorised. The Auth response contains a DpsTxnRef. The funds are not transferred from the cardholder account.

2) Completion

After a successful Authorisation transaction, but within 7 days maximum, a "completion"  (TxnType="Complete") transaction must be sent containing the DpsTxnRef returned by the "Auth" transaction.

Token Billing

Overview

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 a 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

1) Setup Phase

The setup phase consists of loading a card into Payment Express with a transaction. The transaction can be an online $1.00 Auth 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 transaction request (Auth or Purchase) including the following properties:

EnableAddBillCard (Set to 1 when adding a card)
BillingId (optional)

You can supply your own billing ID in BillingId or leave it blank and use the ID returned in DpsBillingId determined by Payment Express)

2) Rebill Phase

The merchant application or Batch processor requests a new transaction and supplies the appropriate BillingId or DpsBillingId, a MerchantReference, 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.