Direct Post

Integration Guide

Table of Contents
1 Introduction ............................................................................................................................................ 4
1.1

What is Direct Post? ................................................................................................................................. 4

1.2
1.3

About this Guide ....................................................................................................................................... 4

Features and Benefits ............................................................................................................................. 4

1.4

Card Types Accepted................................................................................................................................ 4

2 How is Direct Post Implemented? ............................................................................................................ 5

2.1

Important Information Before You Begin ................................................................................................ 5

2.2

Technical Overview................................................................................................................................... 5

3 Implementation....................................................................................................................................... 6
3.1

General Information ................................................................................................................................. 6

3.1.1
Case Sensitivity
6
3.1.2
HTML Forms
6
3.1.3
Acceptable Form Input Tags
6
3.2
Transaction URLs .................................................................................................................................... 6
3.2.1
Test URL
6
3.2.2
Live URL
7
3.3
Mandatory Fields...................................................................................................................................... 7
3.3.1
Merchant ID
7
3.3.2
Transaction Type
7
3.3.3
Payment Reference
8
3.3.4
Transaction Amount
9
3.3.5
GMT Timestamp
9
3.3.6
Fingerprint
10
3.3.7
Transaction Result URL
10
3.3.8
Card Information
11
3.4
Optional Features ................................................................................................................................... 12
3.4.1
Currency
12
3.4.2
FraudGuard
12
3.4.3
Card Storage
13
3.4.4
3D Secure
15
3.5
Transaction Result ................................................................................................................................. 15
3.5.1
Reading the result
15
3.5.2
Result Page Redirects
15
3.6
Testing .................................................................................................................................................... 16
3.6.1
3.6.2

Test Card Number, Type and Expiry

Simulating Approved and Declined Transactions

16
16

4 Glossary ................................................................................................................................................ 17
5 Appendices ........................................................................................................................................... 19
5.1
Appendix 1: Accepted Input Fields ........................................................................................................ 19
5.1.1
Mandatory Fields
19
5.1.2
Card Storage Fields
23
5.1.3
FraudGuard Fields
24
5.1.4
3D Secure Fields
25
5.2
Appendix 2: Result Fields ...................................................................................................................... 26

SecurePay Pty Ltd

Page 2 of 28

5.2.1
5.2.2
5.2.3
5.2.4

Standard Result Fields

callback_status_code
FraudGuard Result Fields
Card Storage Result Fields

SecurePay Pty Ltd

26
27
27
28

Page 3 of 28

Introduction

1.1 What is Direct Post?

Direct Post is a payment service that accepts Customer data posted directly from a form on your web site.
Unlike an API, the data is transmitted directly from the Customers computer to SecurePay. Once the bank
has processed the transaction, Direct Post redirects the Customer back to a result page on your web site
for order completion and fulfilment.

1.2 About this Guide

This guide provides technical information about installing and configuring Direct Post within your web site.
It is recommended that someone with HTML and web programming experience reads this guide and
implements Direct Post. Talk to your web developer if you require technical assistance with programming.

This guide covers the technical requirements of integrating Direct Post in to your web
site. An understanding of web programming, such as PHP or .NET, is required.

1.3 Features and Benefits

Direct Post benefits Merchants and developers due to the following features:
Direct Post integrates seamlessly with an existing web site both functionally and aesthetically.
Direct Post can be integrated with any web-based programming language.
Direct Post is designed to return data to your system following a transaction to enable seamless
tracking of payments and orders.

1.4 Card Types Accepted

Direct Post accepts the following card types by default via your SecurePay account:
Visa
MasterCard
You may also accept the following cards. However, these must be applied for independently via the
contacts shown:
American Express

1300 363 614

Diners Club

1300 360 500

JCB

1300 363 614

SecurePay Pty Ltd

Page 4 of 28

How is Direct Post Implemented?

2.1 Important Information Before You Begin

The Direct Post Interface is not an API model, it is a browser redirect model.
Credit card numbers must be submitted by the card holder directly to the payment URLs in this document,
and not to your own or a third party server, from an HTML form on your web site. This is a bank
requirement and must be met before live transaction processing can commence.

2.2 Technical Overview

Direct Post is an online, secure credit and charge card transaction system that integrates into a web
programming environment, such as PHP or .NET, via a three-step process that ensures transaction amount
and response integrity.
Step 1: Generate a Fingerprint
A Fingerprint is generated in you web site code by a SHA1 hash comprising your SecurePay Merchant ID
and transaction password, your payment amount, transaction reference and a timestamp. This value is
then presented on your payment form as a hidden field.
Step 2: Customer Submits Card Details to Direct Post
Your customer enters their credit card details on a secure HTML form on your web site and submits them
directly to Direct Post which in turn securely processes the transaction.
Note: When accepting card details on your web site you will require an SSL certificate. It is your
responsibility to obtain and configure the SSL certificate.
Step 3: Redirect to Result Page
Upon completion of the transaction, Direct Post redirects to your result URL and passes result parameters,
including a result Fingerprint to protect the transaction result. Your system checks the Fingerprint, updates
your database and displays the receipt to the Customer.

SecurePay Pty Ltd

Page 5 of 28

Implementation

3.1 General Information

3.1.1

Case Sensitivity

All field name and value attributes should be treated as case sensitive.

3.1.2

HTML Forms

When using an HTML form, the following form tags are used to encapsulate Direct Post inputs:
<form method="post" action="https://">

</form>

All INPUT fields must occur between the form tags for correct submission of information to the Direct
Post Live and Test servers.
Direct Post only accepts POST data from an HTML form submitted by your Customer on your web site to
initiate a transaction. Ensure that the method attribute is set to post".
You may also add the name attribute or any other form functionality that you require.

3.1.3

Acceptable Form Input Tags

Any HTML form tags may be used to submit information to Direct Post.
This document deals predominantly with the input tag, however, you may use any form tag to create the
necessary name/value data pairs that form the information interpreted by Direct Post
Most data is normally passed as hidden type input fields. Some fields, such as the card number, are
entered by your Customer and are typically passed as text type input fields.
Form inputs follow the structure:
<input type=field_type name=field_name value=field_value>

3.2 Transaction URLs

Listed below are the live and test URLs for performing several functions.

3.2.1

Test URL

Transactions are created by an HTML form submitted by your Customer on your

web site to:
SecurePay Pty Ltd

Page 6 of 28

<form method="post"
action="https://api.securepay.com.au/test/directpost/authorise">

3.2.2

Live URL

Transactions are created by an HTML form submitted by your customer on your

web site:
<form method="post"
action="https://api.securepay.com.au/live/directpost/authorise">

3.3 Mandatory Fields

3.3.1

Merchant ID

The Merchant ID field, EPS_MERCHANT, is mandatory. It is the SecurePay account to process payments.
SecurePay Customer Support will supply your Merchant ID when your account is activated. The Merchant
ID will be of the format ABC0010, where ABC is your unique three-letter account code, also used for
logging in to the SecurePay Merchant Log In.
Example: Form tags with EPS_MERCHANT input field
<form method="post" action="https://">
<input type="hidden" name="EPS_MERCHANT" value="ABC0010">

</form>

3.3.2

Transaction Type

The EPS_TXNTYPE defines the payment process. It allows switch of the payment type, as well as addition
of optional services such as FraudGuard and 3D Secure. It also forms part of the Fingerprint.
3.3.2.1

Payment

Payments are real-time, immediately authorised card transactions. Transaction information is passed from
a payment form, to your SecurePay account for immediate processing.
Example: Form fields required to make a card payment
Hidden fields:
<input type="hidden" name="EPS_MERCHANT" value="ABC0010">
<input type="hidden" name="EPS_TXNTYPE" value="0">
<input type="hidden" name="EPS_REFERENCEID" value="Test Reference">
<input type="hidden" name="EPS_AMOUNT" value="1.00">
<input type="hidden" name="EPS_TIMESTAMP" value="201106141010">
<input
type="hidden"
value="01a1edbb159aa01b99740508d79620251c2f871d">

name="EPS_FINGERPRINT"

<input type="hidden" name="EPS_RESULTURL" value=https://www.resulturl.com>

Customer-entered fields:

SecurePay Pty Ltd

Page 7 of 28

<input type="text" name="EPS_CARDNUMBER">

<input type="text" name="EPS_EXPIRYMONTH">
<input type="text" name="EPS_EXPIRYYEAR">
<input type="text" name="EPS_CCV">
A typical approved result from this transaction would be:
https://www.resulturl.com.au?
refid=Test Reference
&rescode=08
&restext=Honour with ID
&txnid=100036
&authid=151678
&settdate=20110617
&sig=MC0CFQCQnNRvziCb1o3q2XPWPljH8qbqpQIUQm9TpDX1NHutXYuxkbUk9AfV+/M=
Refer to "5.2.1 Standard Result Fields" for more information on transaction results.
3.3.2.2

Pre-Authorisation

A pre-authorisation is a transaction that reserves funds on a card account. The Merchant can then
complete the transaction at a later date and receive the funds. If the pre-authorisation is never completed,
it expires, usually after five days. After this, the reserved funds are again available to the card holder.
Pre-authorisations are often used by hotels to reserve funds at booking time and then completed when the
guest checks out.
To pre-authorise an amount, submit all the fields exactly as they were for the PAYMENT (0) transaction type
above, including the card details, and set:
<input type="hidden" name="EPS_TXNTYPE" value="1">
Once submitted, the result will be returned to your "EPS_RESULTURL" including the following field:
Example: Extra result field from a PREAUTH transaction
preauthid=516376

3.3.3

Payment Reference

The "EPS_REFERENCEID" mandatory field is used to tag orders with an identifier meaningful to you. This
may be your invoice number, or could be a unique tracking number produced as part of your own web site.

SecurePay Pty Ltd

Page 8 of 28

The Reference ID is available to the Result URL and emails, and appears as the Transaction Reference in
the SecurePay Merchant Log In.
It is recommended that the Reference ID is unique to aid in reconciliation.
Example: Defining a reference id
Scenario: Your Company wants to include its invoice numbers with every
payment.
<input type="hidden" name="EPS_REFERENCEID" value="Invoice#642193">

3.3.4

Transaction Amount

The "EPS_AMOUNT" mandatory field is the amount that will be transacted through your SecurePay account.
By default the currency is AUD (Australian Dollars).
It is passed in a dollars and cents format. For example, $1.00 would be passed as "1.00".
Example: Setting the transaction amount
Scenario:

A customer
AUD$53.20.

chooses

items

from

your

shopping

cart

totalling

<input type="hidden" name="EPS_AMOUNT" value="53.20">

3.3.5

GMT Timestamp

When sending a request to Direct Post to generate a fingerprint or to process a transaction, you must pass
a Greenwich Mean Time (GMT) timestamp in the field "EPS_TIMESTAMP" (also known as UTC).
The timestamp used to generate the fingerprint must exactly match the one
sent with the associated transaction.
It must be of the format "YYYYMMDDHHMMSS" where:
YYYY is the current year
MM is the current two digit month 01 12
DD is the current two digit day 01 - 31
HH is the current two digit hour in 24-hour format 01 - 24
MM is the current two digit minute 00 59
SS is the current two digit second 00 59
Example: Setting the GMT timestamp

SecurePay Pty Ltd

Page 9 of 28

Scenario: Your system has generated a Fingerprint. It is currently 22:35:05

on 20/06/2011 in Sydney (+10 hours from GMT). The time in GMT is
12:35:05 on the same day.
<input type="hidden" name="EPS_TIMESTAMP" value="20110620123505">

3.3.6

Fingerprint

The Fingerprint is a protected record of the amount to be paid. It must be generated and then included on
your customer payment HTML page as a hidden field. It prevents a customer modifying the transaction
details when submitting their card information.
The Fingerprint is a SHA1 hash of the above fields plus the SecurePay Transaction Password in this order
with a pipe separator |:
EPS_MERCHANTID
Transaction Password (supplied by SecurePay Support)
EPS_TXNTYPE
EPS_REFERENCEID
EPS_AMOUNT
EPS_TIMESTAMP
Example: Setting the fingerprint
Fields joined with a | separator:
ABC0010|txnpassword|0|Test Reference|1.00|20110616221931
SHA1 the above string:
01a1edbb159aa01b99740508d79620251c2f871d
<input type="hidden" name="EPS_FINGERPRINT"
value="01a1edbb159aa01b99740508d79620251c2f871d">

For methods of generating a SHA1 hash in your language please visit:

http://code.wikia.com/wiki/SHA_checksum

3.3.7

Transaction Result URL

Use the field "EPS_RESULTURL" to set the secure page on your web site that must receive and interpret the
transaction result and display the result to the Customer.
When a transaction is complete (approved or declined), Direct Post redirects the browser to your result
page with the transaction result in a series of POST fields. If you redirect Direct Post to another URL, fields
may be sent via the GET method. Please handle both GET and POST methods.
The result includes a Fingerprint that you can verify to check the integrity of the transaction result.

SecurePay Pty Ltd

Page 10 of 28

The values of EPS_RESULTURL must:

o
o

Be written as fully-qualified URLs. I.e. "https://...".

Be secure URLs (unless you are testing) from a trusted provider (not self-signed)

Example: Set the Result URL

Scenario: The special result URL "result.php" has been configured to update
a database and to display the receipt page.
<input type="hidden" name="EPS_RESULTURL"
value="https://www.myserver.com.au/result.php">

3.3.8

Card Information

Each transaction must include the card information submitted by a Customer. This is private information
and should not be visible to you or your system.
The fields, "EPS_CARDNUMBER", "EPS_EXPIRYMONTH", "EPS_EXPIRYYEAR" and "EPS_CCV" are all required
for the transaction.
Visa and MasterCard have the card number and expiry date on the front, and a security number referred to
as a CCV2 printed on the signature strip on the back of the card appearing as a three digit number.
Example: Allow a customer to enter their card information
Scenario: Your system displays a payment page to the customer, complete
with amount to pay, requesting input of card information. The following
input fields collect that information:
<input type="text" name="EPS_CARDNUMBER">
<select name="EPS_EXPIRYMONTH">
<option value="01">01
<option value="02">02
<option value="03">03
<option value="04">04
<option value="05">05
<option value="06">06
<option value="07">07
<option value="08">08
<option value="09">09
<option value="10">10
<option value="11">11
<option value="12">12

SecurePay Pty Ltd

Page 11 of 28

</select>
<select name="EPS_EXPIRYYEAR">
<option value="2010">2010
<option value="2012">2011
<option value="2013">2012
<option value="2014">2013
<option value="2015">2014
</select>
<input type="text" name="EPS_CCV">

3.4 Optional Features

3.4.1

Currency

If your bank supports multicurrency, you may optionally set the currency of the transaction to one other
than AUD
Set EPS_CURRENCY to any ISO three letter currency value.
Example: Set the currency to USD
EPS_CURRENCY=USD

3.4.2

Parameter Callback

All result fields are sent to your EPS_RESULTURL. In addition, a callback URL may also be specified to
enable separation of the browser process from the update process.
Set EPS_CALLBACKURL similarly to the EPS_RESULTURL.
Fields are sent via the POST method. Following a redirect, fields may be sent via the GET method.
The result fields will then also include a callback_status_code the HTTP response code from your URL.
Note that your callback URL must not contain multiple redirects or flash content or other content that may
prevent Direct Post from successfully making a connection.

3.4.3

FraudGuard

If your account has been enabled for FraudGuard, you can set the optional field "EPS_TXNTYPE to include
the FraudGuard option and pass a series of additional payment parameters to the system to help validate
your customer.
Note: FraudGuard cannot eliminate fraud. It observes transaction patterns and conservatively judges
whether a transaction is likely to be fraudulent. You should always use your own judgement before sending
goods or supplying services based on the result of any transaction.
All FraudGuard parameters are described in "5.1.3 FraudGuard Fields".

SecurePay Pty Ltd

Page 12 of 28

Example: Sending Fraud Guard parameters with a transaction.

Required (in addition to other required payment fields):
<input type="hidden" name="EPS_TXNTYPE" value="2">
<input type="hidden" name="EPS_IP" value="203.123.456.789">
Optional (any combination is acceptable):
<input type="hidden" name="EPS_FIRSTNAME" value="John">
<input type="hidden" name="EPS_LASTNAME" value="Smith">
<input type="hidden" name="EPS_ZIPCODE" value="2345">
<input type="hidden" name="EPS_TOWN" value="">
<input type="hidden" name="EPS_BILLINGCOUNTRY" value="US">
<input type="hidden" name="EPS_DELIVERYCOUNTRY" value="US">
<input type="hidden" name="EPS_EMAILADDRESS" value="[email protected]">

The field "EPS_IP" is your customer's browser IP address. This can be obtain from your web server as the
Remote IP address environment variable.
If the transaction passes Fraud Guard, you will receive the following result codes:
rescode = Bank response code
restext = Bank response text

afrescode = 000

If the transaction does not pass FraudGuard you will receive:

rescode = Error code
restext = Associated error text
afrescode = Value other than 000
afrestext = Associated Fraud Guard result text

3.4.4

Card Storage

The card number used in the transaction may be optionally stored for subsequent batch or XML
transaction triggering.
By setting "EPS_STORE=true, the card will be stored in SecurePays Payor system using the
EPS_REFERENCEID as the Payor ID.
3.4.4.1

Payor

This is the default card storage method.

SecurePay Pty Ltd

Page 13 of 28

With Payor storage, you define the Payor ID to store with the card. Cards and Payor IDs can be edited via
the Merchant Login.
You may also set EPS_STORETYPE=payor to use this storage type.
You may optionally pass in an alternative value for the stored Payor ID to override the use of
EPS_REFERENCEID.
Set EPS_PAYOR to your required value.
Example: Set card storage with type Payor and my own Payor ID
EPS_REFERENCEID=123456
EPS_STORE=true
EPS_STORERTYPE=payor
EPS_PAYOR=MyCustomer
3.4.4.2

Token

A Token is a string that represents a stored card number. If the card number changes, so does the token,
therefore card numbers and tokens cannot be edited, they may only be added or deleted.
Tokens can be used in 3rd party systems to represent card numbers.
If a card is passed to the system for storage several times, the same token is always returned.
To have SecurePay generate a token for a card, or return an existing token for a pre-stored card set
EPS_STORETYPE=token.
Direct Post will return the token in the result parameters.
Example: Set card storage with type Token
EPS_REFERENCEID=123456
EPS_STORE=TRUE
EPS_STORERTYPE=TOKEN
3.4.4.3

Stored Transaction Reference

When triggering a payment from a stored card of either type Payor or Token via batch or API, the
Transaction Reference defaults to the Payor ID (or Token). This can be overridden by setting a specific
Transaction Reference at the time of storage.
Set the EPS_PAYORREF to store your desired Transaction Reference against the stored card.

SecurePay Pty Ltd

Page 14 of 28

This is particularly useful; for tokens, as the token does not necessarily represent your Customer.
Example: Set
Reference

card

storage

with

type

Token

and

your

own

Transaction

stored

Transaction

EPS_REFERENCEID=123456
EPS_STORE=true
EPS_STORERTYPE=TOKEN
EPS_PAYORREF=123456
In this example, the Payment Reference ID
Reference for future triggering are the same.

3.4.5

and

the

3D Secure

Visaa Verified by Visa and MasterCards SecureCode together become 3D Secure

This is an additional service that can be added to your SecurePay account.
Once active, you can instruct the system to use 3D Secure by setting the EPS_TXNTYPE to include 3D
Secure.

3.5 Transaction Result

After the transaction has been processed, a set of result parameters will be returned to the URL you
defined in EPS_RESULTURL. You may then use these parameters within your defined result URL program
to update your application and display the desired outcome to the Merchant.

3.5.1

Reading the result

Result parameters are returned using the POST method with parameter names as described in Appendix
2: Result Fields.
Some parameters will only be returned if a particular feature is used.

3.5.2

Result Page Redirects

If your web site redirects the Direct Post result to another page on your site, Direct will automatically follow
the redirect. This will occur until Direct Post is no longer redirected.
Direct Post will POST result parameters the first time it calls your server, but Direct Post will send result
parameters using the GET method based on RFC 2616 standards after being redirected.

SecurePay Pty Ltd

Page 15 of 28

3.6 Testing
As you build your system, you can test functionality when necessary by submitting parameters to the test
URL found in "3.2 Transaction URLs". You can generate a fingerprint and then complete the transaction by
using the card details listed below.

3.6.1

Test Card Number, Type and Expiry

Use the following information when testing transactions:

Card Number: 4444333322221111
Card Type:

VISA

Card CCV:

123

Card Expiry: 08 / 13 (or any date greater then today)

3.6.2

Simulating Approved and Declined Transactions

You can simulate approved and declined transactions by submitting alternative payment amounts.
If the payment amount ends in 00, 08, 11 or 16, the transaction will be approved once card details are
submitted. All other options will cause a declined transaction.
Payment amounts to simulate approved transactions:
$1.00
$1.08
$105.00
$105.08
(or any total ending in 00, 08)

Payment amounts to simulate declined transactions:

$1.51
$1.05
$105.51
$105.05
(or any totals not ending in 00, 08)
Note that when using the live URL for payments, the bank determines the transaction result, independent
of the payment amount.

SecurePay Pty Ltd

Page 16 of 28

Glossary
3D Secure

A method used by Visa, MasterCard and JCB to authenticate the cardholder

during an online transaction. Cardholders who have enrolled in either the Verified
by Visa, MasterCard SecureCode or JCB J Secure programs can be asked to
supply a password during the shopping experience to validate their identity. The
password request is made by the cardholders Issuing Bank and the response is
available only to that bank. Under certain circumstances, the cardholders right to
deny involvement in the transaction is removed by the application of 3D Secure.
Refer also to J Secure, MasterCard SecureCode and Verified by Visa.

CSC

Cardholder Security Code. This is an extra code printed on the back of a Visa or
MasterCard, typically shown as the last three digits on the signature strip. It is
used during a payment as part of the cardholder authentication process. You may
also know it as the Cardholder Verification Value (CVV), Card Verification Code
(CVC), or the Personal Security Code.
American Express and Diner Club Cards use a 4 digit Security Code in much the
same manner.

FORM

The HTML tag used to mark the start and end of the area of your payment page that
passes name/value data pairs to Direct Post.

HTML

Hypertext Markup Language. The language interpreted by web browsers. This is the
language used to create your Direct Post payment form.

Hyperlink

A shortcut to another function within the system, accessed by clicking on an

underlined label.

Input Field

HTML tags that define Form input fields. Used to submit information to Direct Post
from your order form.

J Secure

JCBs brand name for its version of 3D Secure. Refer also to 3D Secure.

Log Date/Time The date and time that the transaction was processed via Direct Post. Log Date
and Time helps to tie a transaction back to your business system and assists in
searching (via SecurePays Transaction Search) for transactions which occurred
during a specific period. Refer also to Settlement Date.
Merchant ID

Your SecurePay Merchant ID used to direct which account payments are made.

Merchant
Number

Your banks merchant number.

MOTO

An acronym for Mail Order/Telephone Order. MOTO is now a general term used to
describe any process of processing a credit or charge card transaction by manual
entry of the card details.

MasterCard

MasterCards brand name for its version of 3D Secure. Refer also to 3D Secure.

SecurePay Pty Ltd

Page 17 of 28

SecureCode
Payment

A transaction which both reserves card holder funds and transfers those funds to
the merchants account in a single step. Refer also to Pre-authorisation and
Complete.

PreA transaction which reserves card holder funds but does transfer not those funds
authorisation to the merchants account until a follow up Complete transaction is performed.
Refer also to Complete and Payment.
Response
Code

A numeric code associated with a transaction to indicate a specific transactions

processing result. Transactions which are successfully passed through the
banking system are returned with a two digit response code allocated by the
banking system. Transactions which were rejected during FraudGuard processing
or which encountered technical problems and therefore were not successfully
returned by the banking system will be allocated a 3 digit response code by
SecurePay. A full list of Response Codes is included in this document as Appendix
2.

Settlement
Date

The date on which funds associated with successful transactions are transferred
to the merchants account. Settlement is usually same day for transactions which
have been processed by your bank before 6-10:00 pm AEST and next day for
transactions processed after that time. Settlement for American Express, Diners
and JCB cards will vary depending on your relationship with these organisations.
Searching by Settlement Date helps to tie a transaction back to your bank
statement. Refer also to Log Date/Time.

SSL

Secure Sockets Layer. The mechanism used to encrypt form data submitted from a
browser.

Transaction
Password

This password is sent in transaction requests along with your Merchant ID to

authenticate your account. It is not your online login password, however, it can be
changed via your online login. Be aware that changing this password may prevent
transactions from being processed unless you also update it in your programs.

Transaction
Reference

A meaningful business reference such as customer name, customer number,

order number, reservation number etc which you allocate to your transaction at
the time of processing. Transactions processed by SecurePay are immediately
recorded in the secure database which is accessed by the Merchant Log In.
Transaction Reference (or any part of it) is an important search criterion within
the Merchant Log In.

Transaction
Source

The point of origination of this transaction. Valid Transaction Sources are: Online,
Direct Post, IVR, Batch, Periodic, and Administration. Each of these is individually
explained in more detail in this Glossary.

Transaction
Type

The type of processing requested by this transaction. Valid Transaction Types are
Payment and Pre-authorisation. Each of these is individually explained in more
detail in this Glossary.

Verified
Visa

SecurePay Pty Ltd

by Visas brand name for its version of 3D Secure. Refer also to 3D Secure.

Page 18 of 28

Appendices

5.1 Appendix 1: Accepted Input Fields

Mandatory

Optional

Fraud Guard

3DSecure

EPS_MERCHANT

EPS_CURRENCY

EPS_IP

3D_XID

EPS_TXNTYPE

EPS_REDIRECT

EPS_AMOUNT

EPS_CALLBACKURL

EPS_REFERENCEID

EPS_MERCHANTNUM

Fraud Guard (Optional)

EPS_FIRSTNAME

EPS_TIMESTAMP

Card Storage

EPS_LASTNAME

EPS_FINGERPRINT

EPS_STORE

EPS_ZIPCODE

EPS_CARDNUMBER

EPS_TOWN

EPS_EXPIRYMONTH

Card Storage (Optional)

EPS_BILLINGCOUNTRY

EPS_EXPIRYYEAR

EPS_STORETYPE

EPS_DELIVERYCOUNTRY

EPS_CCV

EPS_PAYOR

EPS_EMAILADDRESS

EPS_RESULTURL

EPS_PAYORREF

5.1.1

Mandatory Fields

5.1.1.1

EPS_MERCHANT

CLASS:

Mandatory

FORMAT:

Alpha-numeric, length 7

DESCRIPTION:

A unique identifier for the Merchant within the Payment Gateway. This Merchant identifier value is an
alphanumeric string allocated to you by SecurePay. This merchant identifier value is not the same as the
merchant number provided by your bank.

TYPICAL USE:

<input type="hidden" name="EPS_MERCHANT" value="ABC0010">

5.1.1.2

EPS_TXNTYPE

CLASS:

Mandatory

FORMAT:

Numeric

DESCRIPTION:

Used to determine the processing type for an individual transaction. May be one of the following:
0 - PAYMENT: A card payment/purchase transaction.
1 - PREAUTH: Used to pre-authorise an amount on a card. The result parameters include the
preauthid which must be stored and used when completing the pre-authorisation
2 PAYMENT with FRAUDGUARD: A card payment/purchase transaction with the optional
FraudGuard service
3 PREAUTH with FRAUDGUARD: A card preauthorisation transaction with the optional FraudGuard

SecurePay Pty Ltd

Page 19 of 28

service
4 PAYMENT with 3D Secure: A card payment/purchase transaction with the optional 3D Secure
service
5 PREAUTH with 3D Secure: A card preauthorisation transaction with the optional 3D Secure
service
6 PAYMENT with FRAUDGUARD and 3D Secure: A card payment/purchase transaction with the
optional FraudGuard and 3D Secure services
7 PREAUTH with FRAUDGUARD and 3D Secure: A card preauthorisation transaction with the
optional FraudGuard and 3D Secure services
TYPICAL USE:

5.1.1.3

<input type="hidden" name="EPS_TXNTYPE" value="0">

EPS_AMOUNT

CLASS:

Mandatory

FORMAT:

Numeric, two decimal places, from 0.01 to 99999999.99

DESCRIPTION:

The total amount of the purchase transaction. This value must be a positive decimal value of dollars and
cents. Please be careful to correctly specify the amount as Direct Post has no method of determining
whether an amount has been correctly specified.

TYPICAL USE:

<input type="hidden" name="EPS_AMOUNT" value="107.95">

5.1.1.4

EPS_REFERENCEID

CLASS:

Mandatory

FORMAT:

String, min length 1, max length 60

DESCRIPTION:

A string that identifies the transaction. This string is stored by SecurePay as the Transaction Reference.
This field is typically a shopping cart id or invoice number and is used to match the SecurePay transaction
to your application.

TYPICAL USE:

<input type="hidden" name="EPS_REFERENCEID" value="My Reference">

5.1.1.5

EPS_TIMESTAMP

CLASS:

Mandatory

FORMAT:

String, format "YYYYMMDDHHMMSS" in GMT (UTC).

DESCRIPTION:

The GMT time used for Fingerprint generation. This value must be the same submitted to generate a
fingerprint as submitted with the transaction. SecurePay validates the time to within one hour of current
time. The time component must be in 24 hour time format.

TYPICAL USE:

<input type="hidden" name="EPS_TIMESTAMP" value="20110620122453">

5.1.1.6

EPS_FINGERPRINT

CLASS:

Mandatory

FORMAT:

String, length up to 60

DESCRIPTION:

A SHA1 hash of
EPS_MERCHANT|TransactionPassword|EPS_REFERENCEID|EPS_AMOUNT|EPS_TIMESTAMP
Where the EPS_ prefixed fields are sent in the request and TransactionPassword is obtained from
SecurePay Support and maybe changed via the SecurePay Merchant Log In.

SecurePay Pty Ltd

Page 20 of 28

TYPICAL USE:

5.1.1.7

<input type="hidden" name="EPS_FINGERPRINT"

value="01a1edbb159aa01b99740508d79620251c2f871d">

EPS_CARDNUMBER

CLASS:

Mandatory

FORMAT:

Numeric, min length 12, max length19

DESCRIPTION:

The card number used in the transaction..

TYPICAL USE:

<input type="text" name="EPS_CARDNUMBER" value="4444333322221111">

5.1.1.8

EPS_EXPIRYMONTH

CLASS:

Mandatory

FORMAT:

String, min length 1, max length 2

DESCRIPTION:

The month in which the card expires. This may only contain an integer value between 1 and 12, inclusive,
corresponding to the month of the year.
The expiry month and expiry year together must form a date that is at least the current month. Transactions
that contain an expiry date in the past will be rejected.
A leading zero is allowed.

TYPICAL USE:

5.1.1.9

<input type="text" name="EPS_EXPIRYMONTH" value="06">

EPS_EXPIRYYEAR

CLASS:

Mandatory

FORMAT:

String, length 2 or 4

DESCRIPTION:

The year in which the card expires. This should ideally be a 2 digit year value. The expiry month and expiry
year together must form a date that is later than the current date. Transactions that contain an expiry date
in the past will be rejected. Four digit years are accepted, with the first two digits ignored. E.g. 1911 will be
treated as 2011

TYPICAL USE:

<input type="text" name="EPS_EXPIRYYEAR" value="15">

5.1.1.10 EPS_CCV
CLASS:

Mandatory

FORMAT:

Numeric, length 3 or 4

DESCRIPTION:

The Card Check Value (CCV) field should contain the three digit value that is printed on the back of the card
itself, or the four digit value printed on the front of American Express cards.
When sending transactions to the Payment Gateway test facility, any 3 or 4 digit value will be accepted.
This field may be referred to elsewhere as a Card Verification Value (CVV2) or a Card Verification Code (CVC),
most notably in information provided by banks or card providers.

TYPICAL USE:

<input type="text" name="EPS_CCV" value="999">

SecurePay Pty Ltd

Page 21 of 28

5.1.1.11 EPS_RESULTURL
CLASS:

Mandatory

FORMAT:

String, fully-qualified URL

DESCRIPTION:

The URL on the Merchant web site that accepts transaction result data as POST elements.
The result page may be almost any form of web page, including static HTML pages, CGI scripts, ASP pages,
JSP pages, PHP scripts, etc, however cookies or other forms of additional information will not be passed
through the Payment Gateway.
The EPS_RESULTURL must be a URL for a publicly visible page on a web server within a domain that is
delegated to a public IP number. Internal machine names, such as "localhost", Windows-style machine
names, and privately translated IP numbers will fail.

TYPICAL USE:

<input
type="hidden"
value="http://www.myserver.com.au/result.asp">

name="EPS_RESULTURL"

5.1.1.12 EPS_CURRENCY
CLASS:

Optional

FORMAT:

String, length, ISO 4217 three letter currency code

DEFAULT:

AUD

DESCRIPTION:

Used to set the transaction currency sent to the bank for processing. You must have a bank merchant
facility that accepts currencies other than AUD before using this feature.
Set the currency to any ISO 4217 three letter currency code. E.g. USD, NZD, GBP, etc.

TYPICAL USE:

5.1.1.1

<input type="hidden" name="EPS_CURRENCY" value="NZD">

EPS_REDIRECT

CLASS:

Optional

FORMAT:

String, values FALSE or TRUE

DEFAULT:

FALSE

DESCRIPTION:

Directs the system to redirect to the EPS_RESULTURL. Result parameters are appended to the URL as a
GET string. Validate the result fingerprint to ensure integrity of the bank response. Use the EPS_CALLBACK
if separate database update and page redirect URLs are required.

TYPICAL USE:

<input type="hidden" name="EPS_REDIRECT" value="TRUE">

5.1.1.1

EPS_CALLBACKURL

CLASS:

Optional

FORMAT:

String, fully-qualified URL

DESCRIPTION:

The URL on the Merchant web site that accepts transaction result data as POST elements for the purpose
of updating a client database or system with the transaction reeponse.
The page is not displayed in the browser.
The result page may be almost any form of web page, including static HTML pages, CGI scripts, ASP pages,
JSP pages, PHP scripts.
The EPS_CALLBACKURL must be a URL for a publicly visible page on a web server within a domain that is

SecurePay Pty Ltd

Page 22 of 28

delegated to a public IP number. Internal machine names, such as "localhost", Windows-style machine
names, and privately translated IP numbers will fail.
TYPICAL USE:

<input type="hidden" name="EPS_CALLBACKURL"

value="http://www.myserver.com.au/read_callback_result.asp">

5.1.2

Card Storage Fields

5.1.2.1

EPS_STORE

CLASS:

Mandatory for Card Storage

FORMAT:

String, values FALSE or TRUE

DEFAULT:

FALSE

DESCRIPTION

TRUE to enable card storage

TYPICAL USE

<input type="hidden" name="EPS_STORE" value="true">

5.1.2.2

EPS_STORETYPE

CLASS:

Optional

FORMAT:

String, values PAYOR or TOKEN

DEFAULT:

PAYOR

DESCRIPTION

Type PAYOR will store the card in the SecurePay Payor database. The EPS_REFERENCE field will be used as
the Payor ID unless overridden with EPS_PAYOR.
Type TOKEN will either create and store a new token that represents the card number ro return a preexisting token if the card has been stored previously. Tokens are stored as non-editable Payors.

TYPICAL USE:

5.1.2.3

<input type="hidden" name="EPS_STORETYPE" value="payor">

EPS_PAYOR

CLASS:

Optional if EPS_STORETYPE=PAYOR

FORMAT:

String, length up to 20

DEFAULT:

If not specified, EPS_REFERENCEID is used

DESCRIPTION

The Payor ID to store with the Payor. This will become the Transaction Reference for future triggered
payments against that Payor unless overridden with EPS_PAYORREF

TYPICAL USE:

<input type="hidden" name="EPS_PAYOR" value="MyPayorID">

5.1.2.4

EPS_PAYORREF

CLASS:

Optional

FORMAT:

String, length up to 30

DESCRIPTION

Sets the Transaction Reference for future triggered payments. If not set, the system will log the Payor as
the Transaction Reference when a payment is triggered

SecurePay Pty Ltd

Page 23 of 28

TYPICAL USE:

5.1.3

<input type="hidden" name="EPS_PAYORREF" value="MyTransactionReference">

FraudGuard Fields

FraudGuard is SecurePays system for fraud minimisation. FraudGuard is an additional feature that must be
enabled by SecurePay before utilisation.
Merchants using this feature are required to include the following fields with all transactions sent to the NAB
Transact system.
5.1.3.1

EPS_IP

CLASS:

Mandatory when EPS_TXNTYPE includes FraudGuard

FORMAT:

String, length up to 15

DESCRIPTION

Payees IPV4 IP Address should be obtained from the card holders browser. Typically a programmatic
environment variable such as remote IP.

TYPICAL USE:

<input type="hidden" name="EPS_IP" value="203.123.456.789">

5.1.3.2

EPS_FIRSTNAME

CLASS:

Optional

FORMAT:

String, length less than 30

DESCRIPTION

Payees first name

TYPICAL USE:

<input type="text" name="EPS_FIRSTNAME">

5.1.3.3

EPS_LASTNAME

CLASS:

Optional

FORMAT:

String, length less than 30

DESCRIPTION

Payees last name

TYPICAL USE:

<input type="text" name="EPS_LASTNAME">

5.1.3.4

EPS_ZIPCODE

CLASS:

Optional

FORMAT:

String, length less than 30

DESCRIPTION

Payees zip/post code

TYPICAL USE:

<input type="text" name="EPS_ZIPCODE">

5.1.3.5
CLASS:

EPS_TOWN
Optional

SecurePay Pty Ltd

Page 24 of 28

FORMAT:

String, length less than 30

DESCRIPTION

Payees town

TYPICAL USE:

<input type="text" name="EPS_TOWN">

5.1.3.6

EPS_BILLINGCOUNTRY

CLASS:

Optional

FORMAT:

String, length 2, ISO 4217 currency code

DESCRIPTION

Payees Country two letter code

TYPICAL USE:

<input type="text" name="EPS_BILLINGCOUNTRY">

5.1.3.7

EPS_DELIVERYCOUNTRY

CLASS:

Optional

FORMAT:

String, length 2, ISO 4217 currency code

DESCRIPTION

Order delivery country two letter code

TYPICAL USE:

<input type="text" name="EPS_DELIVERYCOUNTRY">

5.1.3.8

EPS_EMAILADDRESS

CLASS:

Optional

FORMAT:

String, length less than 30

DESCRIPTION

Payees email address

TYPICAL USE:

<input type="text" name="EPS_EMAILADDRESS">

5.1.4

3D Secure Fields

5.1.4.1

3D_XID

CLASS:

Mandatory when EPS_TXNTYPE includes 3D Secure

FORMAT:

String, length 20

DESCRIPTION

3D Secure Transaction ID string. MUST uniquely reference this transaction to the Merchant, and MUST be
20 characters in length. Any ASCII characters may be used to build this string.
E.g. May comprise of a timestamp padded with 0s for uniqueness: "20110714112034872000".

TYPICAL USE:

5.1.4.2
CLASS:

<input type="hidden" name="3D_XID" value="20110714112034872000">

EPS_MERCHANTNUM
Mandatory when EPS_TXNTYPE includes 3D Secure

SecurePay Pty Ltd

Page 25 of 28

FORMAT:

String, length less than 20

DESCRIPTION

Your online merchant number specified by your bank which has been registered for Verified by Visa or
SecureCode, or both. This will be your bank merchant number, e.g. "22123456".

TYPICAL USE:

<input type="HIDDEN" name="3D_XID" value="20110714114257796000">

<input type="HIDDEN" name="EPS_MERCHANTNUM" value="22123456">

5.2 Appendix 2: Result Fields

5.2.1

Standard Result Fields

5.2.1.1

summarycode

The one digit summary of the transaction result

1 = Approved
2 = Declined by the bank
3 = Declined for any other reason
Use rescode and restext for more detail of the transaction result.
5.2.1.2

rescode

The primary indicator of the transaction result.

Bank response or internal error code numbers used to determine the transaction result. Rescode's of 00,
08 and 11 indicate approved transactions, while all other codes represent declines. A full list of response
codes is available for download from the SecurePay web site.
5.2.1.3

restext

The associated text for each "rescode". For bank response codes 00 99, this field is generated by the
bank's payment systems. All other codes have the "restext" generated by SecurePay.
5.2.1.4

refid

The value of the EPS_REFERENCEID parameter from the transactions request. This value is returned to the
Merchant's processing system to allow matching of the original transaction request.
5.2.1.5

txnid

The bank transaction ID. This string is unique at least per terminal, per bank and per settlement date. This
value is required to be re-entered along with other details of the original payment when processing
refunds.
5.2.1.6

settdate

The bank settlement date. This is the date the funds will be settled into the merchant's account. The date
will correspond to today's date until the bank's cut-off time (typically 6-11pm), then roll to the following
business day. The settlement date is returned in the format "YYYYMMDD".

SecurePay Pty Ltd

Page 26 of 28

5.2.1.7

preauthid

The bank pre-authorisation ID returned by the payment gateway. This value is used when sending a preauthorisation complete transaction via XML or Batch.
5.2.1.8

pan

The masked card number of format first sixlast three. E.g. 444433111
5.2.1.9

expirydate

The four digit expiry date entered by the customer. E.g. 0813
5.2.1.10 merchant

The EPS_MERCHANT value used for the transaction

5.2.1.11 timestamp

The GMT (UTC) time used for the response fingerprint of the format "YYYYMMDDHHMMSS". This value
must be used when generating a string to compare to the response fingerprint value to validate the
response. The time component must be in 24 hour time format.
5.2.1.12 fingerprint

A string used to validate the transaction output.

A SHA1 hash of the following fields in order, separated by |:
merchant, transaction password, reference, amount, timestamp, summarycode
For Example:
ABC0010|mytxnpasswd|MyReference|1000|201105231545|1
is SHA1 hashed to give:
3f97240c9607e86f87c405af340608828d331e10

5.2.2

callback_status_code

The HTTP status code of the callback to the EPS_CALLBACKURL.

This can be used to determine if Direct Post was able to successfully contact your web server.

5.2.3

FraudGuard Result Fields

FraudGuard fields are returned in addition to the Standard Result Fields if the input field EPS_TXNTYPE
includes FraudGuard.
5.2.3.1

afrescode

FraudGuard code if EPS_TXNTYPE includes FraudGuard. Returns 400 if the transaction passes
FraudGuard tests. Returns a different string depending on the type of fraud detected.
5.2.3.2

afrestext

FraudGuard response text. Used if the afrescode is not 000. Contains a description of the FraudGuard
result.
SecurePay Pty Ltd

Page 27 of 28

5.2.4

Card Storage Result Fields

Card storage fields are returned in addition to the Standard Result Fields if the input field
EPS_STORE=TRUE.
5.2.4.1

strescode

Storage code Returns 800 if the Payor or Token was successfully stored. Returns a different string if the
storage failed. The strestext describes the failure reason.
5.2.4.2

strestext

Storage response text. Contains a description of the storage result.

5.2.4.3

payor

If EPS_STORETYPE is set to PAYOR (default), the EPS_PAYOR field will be returned in this result field.

5.2.4.4

token

If EPS_STORETYPE is set to TOKEN, the system-generated token will be returned in this field. If the card
has never been stored before, this will be a new value. If the card has been stored previously, the stored
value will be returned.

SecurePay Pty Ltd

Page 28 of 28