July 24, 2017 | Author: Elwin Alexander | Category: N/A
Download Elavon Payment Gateway- Reporting User Guide...
Elavon Payment GatewayReporting User Guide
Version: v1.1
Contents 1
2
3
4
5
6
About This Guide ............................................................................................................................ 4 1.1
Purpose ................................................................................................................................... 4
1.2
Audience ................................................................................................................................. 4
1.3
Prerequisites ........................................................................................................................... 4
1.4
Related Documents ................................................................................................................. 4
1.5
Terminology............................................................................................................................. 4
1.6
Conventions ............................................................................................................................ 7
The Transaction Process, Login, and Homepage........................................................................... 8 2.1
Login ........................................................................................................................................ 8
2.2
Password Reset ...................................................................................................................... 9
2.3
Navigation Menu ................................................................................................................... 10
2.4
The Transaction Process ...................................................................................................... 12
2.4.1
Authorisation ................................................................................................................. 12
2.4.2
Settlement ..................................................................................................................... 12
The Reporting Homepage ............................................................................................................. 13 3.1
Contact Us............................................................................................................................. 13
3.2
Feedback............................................................................................................................... 14
Terminal - Processing a Transaction ............................................................................................ 15 4.1
Terminal - Sale ...................................................................................................................... 15
4.2
Terminal – Refund ................................................................................................................. 19
4.3
Terminal – Manual ................................................................................................................ 22
4.4
Terminal – Card Verification.................................................................................................. 25
4.5
Find Transactions to Void, Settle or Rebate ......................................................................... 28
Transactions - Managing and Viewing .......................................................................................... 29 5.1
Viewing Transactions in Pending .......................................................................................... 30
5.2
Voiding a transaction ............................................................................................................. 31
5.3
Transactions - Viewing Voided transactions ......................................................................... 33
5.4
Transactions - Viewing Failed transactions .......................................................................... 34
5.5
Transactions - Offline ............................................................................................................ 35
5.6
Transactions - Delayed transactions ..................................................................................... 36
Settled Transactions ..................................................................................................................... 40 6.1
Batch List Level ..................................................................................................................... 41
6.2
Batch Overview Level ........................................................................................................... 43
6.3
To download reports to excel: ............................................................................................... 45
6.4
Transaction List Level ........................................................................................................... 46
6.5
Transaction Details Level ...................................................................................................... 48
6.5.1
Details ........................................................................................................................... 48
Copyright © 2013 Elavon, Inc.
Page 2
Sep-13
7
8
9
6.5.2
Fraud ............................................................................................................................. 51
6.5.3
DCC ............................................................................................................................... 52
6.5.4
History ........................................................................................................................... 53
6.6
Viewing Related Transactions............................................................................................... 54
6.7
View and Print Receipt .......................................................................................................... 55
6.8
Rebating a Transaction ......................................................................................................... 56
Fraud Management ....................................................................................................................... 59 7.1
Fraud Scoring ........................................................................................................................ 59
7.2
Fraud Rules ........................................................................................................................... 59
7.2.1
Enabling/Disabling a Check .......................................................................................... 60
7.2.2
Adding Data to a Check ................................................................................................ 61
7.3.1
Suitability score screen .................................................................................................. 63
Searching for Transactions ........................................................................................................... 64 8.1
Search ................................................................................................................................... 64
8.2
Search for a range of transactions ........................................................................................ 65
Settings ......................................................................................................................................... 66 9.1
Change Password ................................................................................................................. 66
9.2
Compulsory Password Change............................................................................................. 67
9.3
User Management ................................................................................................................. 68
9.4
Adding new Users ................................................................................................................. 69
9.5
User roles and permissions ................................................................................................... 71
9.6
User registration process ...................................................................................................... 73
9.7
Viewing & Editing existing Users........................................................................................... 74
Appendix ............................................................................................................................................... 76 Security Code Results ....................................................................................................................... 79 AVS Results ...................................................................................................................................... 79
Copyright © 2013 Elavon, Inc.
Page 3
Sep-13
1 This section outlines the purpose and aim of the Guide, target audience, any source materials or terminology used, and a general document description. Please note that this document is regarded as confidential and is for customer use only. It has been supplied under the conditions of your payment-processing contract.
1.1
Purpose
The purpose of this Guide is to give assistance to Users using Elavon Payment Gateway Reporting.
1.2
Audience
The target audience for this Guide is Reporting Users.
1.3
Prerequisites
In order to use this Guide, you should have experience with and knowledge of the following concepts: ▪
Correct use of the Elavon Auth service, as outlined in the Elavon Auth Developer's Guide
1.4
Related Documents
In addition to this Guide, you can also refer to the following documents in the Elavon Payment Gateway documentation set for information about the Elavon Auth service: ▪
Elavon Auth Response Codes
1.5
Terminology
The terminology specific to the Elavon Auth application is as follows: Expression
Definition
Acquiring bank
Your bank, with which you have a merchant services contract.
Transaction
A transaction is a request sent to Elavon Payment Gateway. Transactions can be used to authorise or refund an amount on a credit or debit card. It can also be used to void or settle
Copyright © 2013 Elavon, Inc.
Page 4
Sep-13
Expression
Definition an amount on a card.
Authorisation
The process of submitting the request to your bank in real time to authorise the payment i.e. mark the funds on the card holders account.
Batches
The process of collecting all valid authorisations for your account and submitting these to the bank for settlement, to be funded to your bank.
Settlement
When the acquiring bank (your bank) pay/move the funds to your bank account.
Settled
Once the transactions have been sent to the bank for settlement they are known as "settled" transactions.
Pending
All transactions that have not yet been settled. These may be transactions that are: waiting to be settled by Elavon Payment Gateway automatically (occurs at 12 every night) need to be manually settled by you (delayed settlement)
Delayed
A delayed transaction is a transaction that will not be settled automatically by Elavon Payment Gateway. This transaction must be manually settled within 28 days on the Elavon Payment Gateway systems. Please note that you may incur exception charges from your bank depending on how long you take to settle the transaction. Check with your acquiring bank for these terms and conditions when using delayed settlement.
Void
If a transaction is still pending i.e. not yet settled then it is possible to void it. A void means that the transaction will be cancelled and therefore not settled. A transaction can
Copyright © 2013 Elavon, Inc.
Page 5
Sep-13
Expression
Definition only be voided when it is pending. Note: that the funds are still marked on the card-holders account but will not be debited.
Rebate
A rebate depends on the original authorisation that was processed, and so you do not need the card number to refund the money onto the card. You can rebate up to 115% of the original amount. Note: This limitation does not apply to Irish Laser debit cards. You can rebate a transaction for up to 180 days from when the original transaction took place.
Refund
Similar to a rebate, the refund is a transaction that refunds monies to the cardholder and will debit your account. A refund is not dependent on an original transaction and so you will need the card number to process the refund. There is no time limit to when a refund can be processed.
Terminal
A facility for processing a transaction online. A section of Reporting in which you can process a credit card payment.
Account
You can have multiple sub accounts set up on your main account. By default you will be set up with a sub-account called "moto". You can set up further sub-accounts, for example "call centre".
Declined
This is a response that you can receive when a transaction is sent for authorisation. When an authorisation is declined, this means that the issuing bank of the card holder have decided not to allow the transaction to go ahead. Payment will not be taken from the card.
Referral A
This is a response that you can receive when a transaction is sent for authorisation. When an authorisation receives a Referral A the card has
Copyright © 2013 Elavon, Inc.
Page 6
Sep-13
Expression
Definition been marked as lost, stolen or cancelled. Payment will not be taken. This is a response that you can receive when a transaction is sent for authorisation. When an authorisation receives a Referral B, the issuing bank of the card holder will not allow the transaction to go through automatically and is requesting that you call their authorisation centre to process the payment.
Referral B
1.6
Conventions
Elavon Payment Gateway documentation uses the following conventions: Note: Tips or advice for the User. Caution: Important note. Potential financial impact.
Convention
Description
Example
Orange Italic or Plain Type
Hyperlinks and crossreferences
For more information see Table 1.
Italics
Names of other Guides
Elavon Auth Developer’s Guide
Courier New
Program code, screen messages,
directory files, and file names Courier New
Placeholder for element names,
card_holder_name
field values, or User input BOLD CAPS
Copyright © 2013 Elavon, Inc.
Error and warning messages
Page 7
101 / REFERRAL B
Sep-13
2 This chapter describes the following: ▪
Login
▪
Navigation Menu
▪
The Transaction Process
2.1
Login
Navigate to the URL https://reporting.elavonpaymentgateway.com The Login screen is displayed.
To Login: 1. In the Client id field, enter your client id as supplied by Elavon Payment Gateway. 2. In the Username field, enter your Username. 3. In the Password field, enter your password. 4. Click login.
Copyright © 2013 Elavon, Inc.
Page 8
Sep-13
2.2
Password Reset
Click here to start password reset process.
In order to reset your password select “Forgot Your Password” as above. The below screen will then display:
To reset the password: 1. In the Client id field, enter your client id name as supplied by Elavon Payment Gateway. 2. In the Username field, enter your Username. 3. In the Email Address field, enter your registered email address. 4. Click submit. 5. You will then receive an email with a link to reset your password.
Copyright © 2013 Elavon, Inc.
Page 9
Sep-13
2.3
Navigation Menu
The main menu of the Reporting homepage is located in the top panel of the screen as below.
Navigation menus.
Explanation of main menu options: Field Name
Explanation
Home
This brings you to the Reporting homepage.
Transactions
In this section you can view the transactions that have been authorised but not yet sent for settlement. You can also view and download the transactions that have been sent to your acquiring bank for settlement. The transactions are bundled into batches which are typically created Monday through Friday. For more information on your specific bank batch times contact Elavon Payment Gateway.
Customer
This section allows you to store Customer details for recurring use. More information on this section can be found in the Secure Data Vault and Scheduler Users Guides on the Resource Centre.
Terminal
You can use the Terminal to process Sales, Refunds and
Copyright © 2013 Elavon, Inc.
Page 10
Sep-13
Field Name
Explanation
Manual transaction types. Note: The Manual transaction type will not be setup as default on your account. Manual Transactions needs an authorisation code from the acquiring bank. Reports
In the reports section you can view reports that have been generated throughout the Reporting application. A history of the previous twenty five reports ran will be viewable in this section. It also gives you the option of downloading your reports to Excel.
Settings
In this section you can change your login password and view your general information.
Search on
This section allows you to search for individual transactions based on specific search criteria.
Log out
Allows you to end your session and securely log out of Reporting.
Copyright © 2013 Elavon, Inc.
Page 11
Sep-13
2.4
The Transaction Process
The transaction is processed in two stages - authorisation and settlement.
2.4.1
Authorisation
▪
Elavon Payment Gateway receive the transaction, either from your system e.g. your website or from a Elavon Payment Gateway system e.g. the online Terminal.
▪
Elavon Payment Gateway sends the transaction for authorisation in real time through the bank network and then send the response back to you.
▪
If the transaction is successful, the transaction is displayed in the Transactions - Pending section. If you wish, at this stage, you can void the transaction and the money will not be taken from the customer's card (although it will remain held on the card until such time as it is released by the customer’s issuing bank).
▪
If you are using 3DSecure, there is an authentication procedure which preceeds the authorisation of the transaction. Please see the 3DSecure Outline Guide for details of this process.
2.4.2
Settlement
▪
If the transaction is processed for automatic settlement, then Elavon Payment Gateway will settle this transaction and send it to your acquiring bank in the next batch. This is an overnight process. The delivery time of the batch will depend on the acquiring bank that you are using. Please note that for some acquirers, batches will only be sent on weekdays or may be sent on Sundays but not Fridays. For information on batch delivery times, please contact Elavon Payment Gateway.
▪
The length of time that it takes for the transaction to be funded to your bank account will be determined by your acquiring bank. If you have any queries about when you will receive funds for transactions processed, please contact your acquiring bank.
▪
If the transaction is processed through delayed settlement, we then send it for settlement once the transaction has been settled by you.
▪
Once the transaction has been sent for settlement it can then be viewed in the ‘Settled’ section. When a transaction is settled the option to void no longer exists, however, you can process a rebate to credit the customer their money.
Copyright © 2013 Elavon, Inc.
Page 12
Sep-13
3 The homepage displays news and announcements from Elavon Payment Gateway as shown below.
Click ‘Contact Us’ to view the support contact details.
3.1
Contact Us
The home page also displays the Elavon Payment Gateway contact details. The “Contact Us” option on the bottom left of the screen is accessible from every screen.
Copyright © 2013 Elavon, Inc.
Page 13
Sep-13
3.2
Feedback
To provide Elavon Payment Gateway with any comments or feedback you may have, click on the feedback button to the right of the screen.
Select the feedback button to open the feedback tab.
This will open up the feedback tab where you can enter your comments. Using the drop down menus available, choose the type and area which best relate to your comments.
Select the appropriate description for your comment.
Send your comment to Elavon Payment Gateway.
Finish by clicking the “Submit Feedback” button. All feedback will be reviewed by Elavon Payment Gateway.
Copyright © 2013 Elavon, Inc.
Page 14
Sep-13
4 4.1
Terminal - Sale
The Terminal can be used to take card payments if you are contacted by a customer over the phone or by Mail-Order. 1.
Select the "Terminal" option from the navigation menu.
2.
To process a sale, “Sale” must be selected from the “Type” dropdown.
3.
To select a particular sub-account, choose the account from the Account dropdown. If you have a single sub-account this will be populated by default. 1. Select Terminal from the Navigation menu.
2. Select transaction type from drop down.
3. Select account.
4. Transaction result .
5. Click on the “Printer” symbol to display the receipt.
4.
If the transaction result is successful or declined the appropriate result and message will appear in the “Result” section.
5.
To print a receipt for this transaction click the “Printer” symbol.
Copyright © 2013 Elavon, Inc.
Page 15
Sep-13
6.
The transaction message gives more detailed information of the transaction. The example below shows that the security code entered did not meet the expected length and as a result the transaction did not proceed to authorisation.
6. Transaction message.
When entering a transaction via the Terminal interface please note the following; 1. The Order ID must always be unique. For example, you could use an invoice number or a unique reference for the transaction. 2. The amount must Never contain decimal places; it is in cent value i.e. to process 10.00, type 1000 for All currencies. 3. The currency and card type options are restricted to what your acquiring bank have advised Elavon Payment Gateway to set up on your account. 4. You can enter the security code, the 3 digit number on the reverse of the card for VISA and MasterCard. For an AMEX card, it is a 4 digit number.If you don’t have this you can select “No Code”. Note: We advise that you always enter this information where possible for added security. 5. The non-mandatory fields Product ID, Variable Ref, Customer Number and Comment1 can be used for your own reconciliation purposes, e.g. they can be used for reference numbers that identify the product, customer etc. 6. When you have completed all the transactional information, you then click on “Process” to complete the transaction. 7. The result will appear on the bottom of the screen. If the transaction has processed successfully the result will be highlighted in green, however if the transaction is declined the result will be highlighted in red. Further information will be available for each transaction in the Message field.
Copyright © 2013 Elavon, Inc.
Page 16
Sep-13
Format and Length of fields: Note: Please be aware that "" means a space. The mandatory fields are marked with a star; these are required in order for the transaction to process. Field
Explanation
Order ID *
The order number must always be unique. For example, you could use an invoice number or a unique reference for the transaction.
a-z A-Z 0-9 _ -
1-40
Amount *
The amount must never contain decimal places; it is in cent value i.e. to process 10.00, type 1000 for ALL currencies. The card number. The card holder name.
0-9
1-8
0-9 a-z A-Z 0-9 “” ‘ _
12-19 1-100
0-9 “”
3-4
a-z A-Z 0-9 ' ", + “ ” . _ - & \ / @!?%()*:£$&€#[]|=
0-255
Card Number * Customer Name * Security Code
Comment 1
Format
You can enter the security code, the 3 digit number on the back of the card, also. If you don’t have this you can select “No Code”. Free text field; can be used to store information that will be relevant for your own reconciliation purposes.
Length
Customer Number
Free text field; can be used to store information that will be relevant for your own reconciliation/reporting purposes.
a-z A-Z 0-9 – “” _ . , + @
0-50
Product ID
Free text field; can be used to store information that will be relevant for your own reconciliation/reporting purposes.
a-z A-Z 0-9 – “” _ . , + @
0-50
Copyright © 2013 Elavon, Inc.
Page 17
Sep-13
Field
Explanation
Format
Length
Variable Ref
Free text field; can be used to store information that will be relevant for your own reconciliation/reporting purposes.
a-z A-Z 0-9 – “” _ . , + @
0-50
Shipping Code
Enter the Address Verification Service (AVS) shipping code alphanumeric.
a-z A-Z 0-9 “” , . - / |
0-30
Predefined
Predefined
a-z A-Z 0-9 “” , . - / |
0-30
Predefined
Predefined
Note: Please note that AVS can only be used for UK merchants and you need to have this functionality set up in your system. Shipping Country
Select the shipping country from the drop down.
Billing Code
Enter the Address Verification Service (AVS) billing code alphanumeric. Note: Please note that AVS can only be used for UK merchants and you need to have this functionality set up in your system.
Billing Country
Select the billing country from the drop down.
Copyright © 2013 Elavon, Inc.
Page 18
Sep-13
4.2
Terminal – Refund
The refund transaction type can only be accessed if you have sufficient permissions. You will need to have been assigned the role of Administrator or Power User to gain access to this section of the Terminal. In order to gain access you will need to contact your Administrator User. 1.
Select the "Terminal" option from the navigation menu:
2.
To process a refund, “Refund” must be selected from the “Type” dropdown. 1. Select Terminal from the Navigation menu.
2. Select Refund transaction type from drop down.
3. Select account.
4. Enter User password.
3.
To select a particular sub-account, choose the sub-account from the Account dropdown. If you have a single sub-account this will be populated by default.
4.
Your password is a mandatory field; you will be required to enter your personal login password.
Note: You need to have the full card number and expiry date to process a refund; if you don't have these details and the transaction is less then 180 days old, you should process a rebate (see Rebating a Transaction).
Copyright © 2013 Elavon, Inc.
Page 19
Sep-13
Format and Length of fields: Note: Please be aware that "" means a space. The mandatory fields are marked with a star; these are required in order for the transaction to process. Field
Explanation
Order ID *
The order number must always be unique. For example, you could use an invoice number or a unique reference for the transaction.
a-z A-Z 0-9 _ -
1-50
Amount *
The amount must never contain decimal places; it is in cent value i.e. to process 10.00, type 1000 for ALL currencies. The card number. The card holder name.
0-9
1-8
0-9 a-z A-Z 0-9 “” ‘ _
12-19 1-100
0-9 “”
3-4
a-z A-Z 0-9 ' ", + “ ” . _ - & \ / @!?%()*:£$&€#[]|=
0-255
Card Number * Customer Name * Security Code
Comment 1
Format
You can enter the security code, the 3 digit number on the reverse of the card for VISA and MasterCard. For an AMEX card, it is a 4 digit number.If you don’t have this you can select “No Code”. Free text field; can be used to store information that will be relevant for your own reconciliation purposes.
Length
Customer Number
Free text field; can be used to store information that will be relevant for your own reconciliation/reporting purposes.
a-z A-Z 0-9 – “” _ . , + @
0-50
Product ID
Free text field; can be used to store information that will be relevant for your own reconciliation/reporting purposes.
a-z A-Z 0-9 – “” _ . , + @
0-50
Copyright © 2013 Elavon, Inc.
Page 20
Sep-13
Field
Explanation
Format
Length
Variable Ref
Free text field; can be used to store information that will be relevant for your own reconciliation/reporting purposes.
a-z A-Z 0-9 – “” _ . , + @
0-50
Shipping Code
Enter the Address Verification Service (AVS) shipping code alphanumerics.
a-z A-Z 0-9 “” , . - / |
0-30
Predefined
Predefined
a-z A-Z 0-9 “” , . - / |
0-30
Predefined
Predefined
Note: Please note that AVS can only be used for UK merchants and you need to have this functionality set up in your system. Shipping Country
Select the shipping country from the drop down.
Billing Code
Enter the Address Verification Service (AVS) billing code alphanumerics. Note: Please note that AVS can only be used for UK merchants and you need to have this functionality set up in your system.
Billing Country
Select the billing country from the drop down.
Copyright © 2013 Elavon, Inc.
Page 21
Sep-13
4.3
Terminal – Manual
The Manual transaction type can only be accessed if you have sufficient permissions. You will need to have been assigned the role of Administrator or Power User to gain access to this section of the Terminal. In order to gain access you will need to contact your Administrator User. Note: Manual transactions are not sent to the bank for authorisation, instead they are added directly to the day's settlement file. Merchants must manually obtain an authorisation code for transactions of this type. Typically, this involves contacting the acquiring bank's authorisation centre by phone. Elavon Payment Gateway will require confirmation from the acquiring bank before this facility can be used. 1.
Select the "Terminal" option from the navigation menu:
2.
To process a manual, “Manual” must be selected from the “Type” dropdown.
1. Select Terminal from the Navigation menu.
2. Select Manual transaction type.
3. Select account.
4. Input Authcode .
3.
To select a particular sub-account, choose the sub-account from the Account dropdown. If you have a single sub-account this will be populated by default.
4.
A manual transaction does not go on-line for authorisation with your acquiring bank, so you are required to input a two to six alphanumeric authcode. You should check with your Acquiring bank for format and lengths when signing up to this service.
Copyright © 2013 Elavon, Inc.
Page 22
Sep-13
Format and Length of fields: Note: Please be aware that "" means a space. The mandatory fields are marked with a star; these are required in order for the transaction to process. Field
Explanation
Order ID *
The order number must always be unique. For example, you could use an invoice number or a unique reference for the transaction.
Amount *
The amount must never contain decimal places; it is in cent value i.e. to process 10.00, type 1000 for ALL currencies. The card number. The card holder name.
Card Number * Customer Name * Security Code
Comment 1
Format
You can enter the security code, the 3 digit number on the reverse of the card for VISA and MasterCard. For an AMEX card, it is a 4 digit number.If you don’t have this you can select “No Code”. Free text field for your own reconciliation.
Length
a-z A-Z 0-9 _ -
1-50
0-9
1-8
0-9 a-z A-Z 0-9 “” ‘ _
12-19 1-100
0-9 “”
3-4
a-z A-Z 0-9 ' ", + “ ”._-&\/@!? %()*:£$&€#[ ]|=
0-255
Customer Number
Free text field for your own reconciliation.
a-z A-Z 0-9 – “” _ . ,+@
0-50
Product ID
Free text field for your own reconciliation.
a-z A-Z 0-9 – “” _ . ,+@
0-50
Variable Ref
Free text field for your own reconciliation.
a-z A-Z 0-9 – “” _ . ,+@
0-50
Shipping Code
Enter the Address Verification Service (AVS) shipping code alphanumeric.
a-z A-Z 0-9 “” , . /|
0-30
Predefined
Predefin ed
Note: Please note that AVS can only be used for UK merchants and you need to have this functionality set up in your system. Shipping Country
Select the shipping country from the drop down.
Copyright © 2013 Elavon, Inc.
Page 23
Sep-13
Field
Explanation
Format
Length
Billing Code
Enter the Address Verification Service (AVS) billing code alphanumeric.
a-z A-Z 0-9 “” , . /|
0-30
Predefined
Predefin ed
Note: Please note that AVS can only be used for UK merchants and you need to have this functionality set up in your system. Billing Country
Select the billing country from the drop down.
Copyright © 2013 Elavon, Inc.
Page 24
Sep-13
4.4
Terminal – Card Verification
The Card Verification transaction type can only be accessed if you have sufficient permissions. You will need to have been assigned the role of Administrator or Power User to gain access to this section of the Terminal. In order to gain access you will need to contact your Administrator User.
The Card Verification transaction type is used to check a card is valid and active without authorising or holding funds. In the past a merchant might authorise a small amount (like 10c) to check the card and then void that transaction. The Card Verification transaction should be used if supported by the acquiring bank and Elavon Payment Gateway. 1.
Select the "Terminal" option from the navigation menu:
2.
To process a card verification transaction, “Card Verification” must be selected from the “Type” dropdown.
1. Select Terminal from the Navigation menu.
2. Select Card Verification transaction type. 3. Select account.
The amount is zero as no money is held.
3.
To select a particular sub-account, choose the sub-account from the Account dropdown. If you have a single sub-account this will be populated by default.
Copyright © 2013 Elavon, Inc.
Page 25
Sep-13
Format and Length of fields: Note: Please be aware that "" means a space. The mandatory fields are marked with a star; these are required in order for the transaction to process. Field
Explanation
Order ID *
The order number must always be unique. For example, you could use an invoice number or a unique reference for the transaction.
Card Number * Customer Name * Security Code
The card number. The card holder name.
Comment 1
Format
You can enter the security code, the 3 digit number on the reverse of the card for VISA and MasterCard. For an AMEX card, it is a 4 digit number.If you don’t have this you can select “No Code”. Free text field for your own reconciliation.
Length
a-z A-Z 0-9 _ -
1-50
0-9 a-z A-Z 0-9 “” ‘ _
12-19 1-100
0-9 “”
3-4
a-z A-Z 0-9 ' ", + “ ” . _ - & \ / @ ! ?%()*:£$&€#[]|=
0-255
Customer Number
Free text field for your own reconciliation.
a-z A-Z 0-9 – “” _ . , + @
0-50
Product ID
Free text field for your own reconciliation.
a-z A-Z 0-9 – “” _ . , + @
0-50
Variable Ref
Free text field for your own reconciliation.
a-z A-Z 0-9 – “” _ . , + @
0-50
Shipping Code
Enter the shipping code.
a-z A-Z 0-9 “” , . - / |
0-30
Shipping Country
Enter the Address Verification Service (AVS) shipping code alphanumeric.
Predefined
Predefined
Note: Please note that AVS can only be used for UK merchants and you need to have this functionality set up in your system.
Copyright © 2013 Elavon, Inc.
Page 26
Sep-13
Field
Explanation
Billing Code
Enter the Address Verification Service (AVS) billing code alphanumeric.
Format
Length
a-z A-Z 0-9 “” , . - / |
0-30
Predefined
Predefined
Note: Please note that AVS can only be used for UK merchants and you need to have this functionality set up in your system. Billing Country
Select the billing country from the drop down.
Copyright © 2013 Elavon, Inc.
Page 27
Sep-13
4.5
Find Transactions to Void, Settle or Rebate
The “Search on” option is used to find transactions that you may need to void, settle or rebate. You can do this by entering the text to search for in the text box provided, then choose the search option in the "Search on" dropdown list then search by clicking "Go". This returns a list of transactions that match your search.
2.Enter transaction text.
1.Select transaction criteria.
Format and Length of fields: Note: Please be aware that "" means a space. The mandatory fields are marked with a star; these are required in order for the transaction to process. Field
Format
Order ID
Length
a-z A-Z 0-9 _ -
1-50
0-9
12-19
a-z A-Z 0-9 “” ‘ _
1-100
Var Ref
a-z A-Z 0-9 – “” _ . , + @
0-50
Customer Number
a-z A-Z 0-9 – “” _ . , + @
0-50
Product ID
a-z A-Z 0-9 – “” _ . , + @
0-50
Card Number Cardholder Name
Copyright © 2013 Elavon, Inc.
Page 28
Sep-13
5
-
Transactions that are not settled are listed in the “Transactions” section by date. Transactions fall into four categories: ▪
Pending - transactions that will be settled in the next batch.
▪
Delayed settlement - transactions that need to be manually settled.
▪
Failed transactions - transactions that have declined.
▪
Voided transactions - transactions that have been voided.
You can select each option in the Transactions Type dropdown menu screen on the left of the screen. Select Transactions from the navigation menu.
Transaction status.
Transaction categories.
Copyright © 2013 Elavon, Inc.
Page 29
Sep-13
5.1
Viewing Transactions in Pending
1. To view your Pending transactions select Transactions – Pending; the twenty most recent pending transactions will display on screen. The screen is displayed as follows:
Transaction Status.
1. Pending. 2. Transaction line.
3. To navigate through a range of transactions click ‘Next’.
2. To view more details on the transaction, click anywhere on the transaction line.
3. To view the next twenty transactions, click on the ‘Next’ located at the bottom right of the screen to proceed to the next page.
Copyright © 2013 Elavon, Inc.
Page 30
Sep-13
5.2
Voiding a transaction
Transactions in the Pending and Delayed categories can be voided to prevent the transaction from proceeding to settlement. Note: If a transaction is voided, the amount of the authorisation will still show as having been debited on the card holder’s account until the funds are released by the card holder’s bank. This process can take up to twenty eight days. For this reason, it is recommended that if it is necessary to credit a customer, the Rebate or Refund transaction types are used where possible. 1. Navigate to the transaction you wish to void. Click on the transaction line to view the transaction details. The Void option will be available for transactions with a transaction status of Pending or Delayed. Click here to display the Void screen.
Transaction status.
Copyright © 2013 Elavon, Inc.
Page 31
Sep-13
2. You are then presented with the modal screen below, where you can enter an optional comment for reconciliation purposes before voiding.
Additional comments can be entered here.
To complete the void, click "void".
Format and Length of fields: Note: Please be aware that "" means a space. The mandatory fields are marked with a star; these are required in order for the transaction to process. Field
Format
Length
Comment Line
a-z A-Z 0-9 ' ", + "" . _ - \ / @ ! ? % ( ) * : £ $ € # [ ] | =
0-255
Copyright © 2013 Elavon, Inc.
Page 32
Sep-13
5.3
Transactions - Viewing Voided transactions
To view your Voided transactions select Transactions – Voided, the twenty most recent voided transactions will display on screen. To view the voided transactions details, click on the transaction line to display the following screen:
Transaction Status.
To view the histories of a transaction select “History”.
Copyright © 2013 Elavon, Inc.
Page 33
Sep-13
5.4
Transactions - Viewing Failed transactions
To view your Failed transactions select Transactions – Failed, the twenty most recent failed transactions will display on screen. To view the Failed transactions details, click on the transaction line to display the following screen:
Transaction Status.
Copyright © 2013 Elavon, Inc.
Page 34
Sep-13
5.5
Transactions - Offline
Some authorisations will be declined with a code 102 Response, the message will be Bank Referral (102) or similar. These transactions may still be authorised in Reporting by using the offline request type. Merchants must manually obtain an authorisation code for transactions of this type. Typically, this involves contacting the acquiring bank's authorisation centre by phone. Offine transaction type is not enabled by default. To have the transaction type enabled, please contact the Elavon Payment Gateway Support team. If a transaction has failed with a 102 Response, it will be located in the failed transaction section of Reporting. If you have obtained the authorisation code for this transaction, you can then proceed by clicking on the “Offline” tab as seen below.
Offline.
To complete this transaction, you must enter the authorisation code into the “Offline Authcode” field.
Orignal Order ID.
Enter authorisation code obtained by acquiring bank.
Copyright © 2013 Elavon, Inc.
Page 35
Sep-13
5.6
Transactions - Delayed transactions
When transactions are submitted for authorisation to Elavon Payment Gateway it is possible to flag the transaction for delayed settlement. Note: All transactions are sent for automatic settlement by default. To process a delayed transaction through the Terminal unselect “Automatically settle to the bank” as below:
To process a delayed transaction deselect “Automatically settle to the Bank”.
Transactions that are set to delayed settlement will authorise in real time but will not be funded to your account until you manually settle the transaction, either through Reporting or by sending in an XML settle request. Note: You must manually settle a delayed transaction within 28 days of the initial authorisation. Caution: Failure to settle a delayed transaction within this timeframe will result in the loss of the authorised amount. You will then need to contact the cardholder to process the transaction again in order to receive payment.
Copyright © 2013 Elavon, Inc.
Page 36
Sep-13
To view delayed transactions: To view your Delayed transactions select Transactions – Delayed, the twenty most recent delayed transactions will display on screen.
Select Delayed from the drop down menu.
Transaction Status.
1.Click on the transaction line to view more details from the transaction.
Copyright © 2013 Elavon, Inc.
Page 37
Sep-13
To settle a delayed transaction: To view the delayed transactions details, click on the transaction line to display the following screen: 2. On this screen you are given the option to "Settle". 1.
Transaction Status.
2.Click ‘Settle’.
Copyright © 2013 Elavon, Inc.
Page 38
Sep-13
When you choose to Settle a transaction the following modal appears:
4. For reconciliation purposes, a Customer Number. Variable Reference, Product ID and Comment can be included. 3. Amount in cents/pence.
5. Click here to settle the transaction.
3.
The transaction amount can be adjusted up to 115% of the original authorised amount. The amount must be entered in cents e.g. 1000 is equal to €10.
Note: The adjustment amount is dependent on your acquiring bank. 4.
For reconciliation purposes, a Customer Number, Variable Reference, Product ID and Comment can be included.
5.
To complete the transaction click "Settle".
Note: If the transaction was authenticated by 3dsecure, you must settle exactly 100% of the authenticated value i.e. if the authenticated and authorised value was €100 then the transaction must be settled for €100. Format and Length of fields: Note: Please be aware that "" means a space. The mandatory fields are marked with a star; these are required in order for the transaction to process. Field
Comment Amount Customer Number Product ID Variable Reference
Format
Length
a-z A-Z 0-9 ' ", + "" . _ - \ / @ ! ? % ( ) * : £ $ € # [ ] | = 0-9 a-z A-Z 0-9 - "" _ . , + @
0-255
a-z A-Z 0-9 - "" _ . , + @ a-z A-Z 0-9 - "" _ . , + @
0-50 0-50
Copyright © 2013 Elavon, Inc.
Page 39
0-8 0-50
Sep-13
6 Once the transactions have been sent to the acquiring bank for settlement they are known as "Settled" transactions. The transactions are settled in batches which are typically created Monday through Friday. For more information on your specific bank batch times contact Elavon Payment Gateway. There are four levels in the settled section; each level holds more information about the batch you want to view: ▪
Batch list level - shows a list of all your batches.
▪
Batch overview level - shows the details of a selected batch.
▪
Transaction list level - shows a list of the transactions in the batch.
▪
Transaction details level - shows the details of a selected transaction in the batch.
To access select “Settled” from the Transactions section.
Copyright © 2013 Elavon, Inc.
Page 40
Sep-13
6.1
Batch List Level
To view your Settled transactions select Transactions – Settled, the most recent twenty batches will display on screen. Note: In the settled section batches are listed by date.
Bank Name.
No. of Sales.
Net Total.
Timestamp.
Batch id.
No. of Refunds.
Explanation of Column Titles on Batch List screen: Title
Description
Date of Batch
This is the date that the batch was opened, this defaults to the date of the first authorisation request in the batch. It is not the date of batch submission.
Batch ID
This is a batch number assigned by Elavon Payment Gateway; these numbers are not in sequence.
Merchant Number
This is the merchant services number that the transactions have been processed through.
Copyright © 2013 Elavon, Inc.
Page 41
Sep-13
Title
Description
No. of Sales
This displays the total amount and currency for the authorisations in this batch.
No. of Refunds
This displays the total amount and currency for the refunds and rebates in this batch. Refunds/Credits are displayed in blue.
Net Total
This displays the Net total and currency of the batch i.e. Sales/Debits amount minus the Refunds/Credits amount.
Copyright © 2013 Elavon, Inc.
Page 42
Sep-13
6.2
Batch Overview Level
You can click on each batch line to see further details about the batch as shown below.
Sub Account Breakdown.
Generated reports can be found in the “Reports” section.
To view a list of all transactions in this batch please click here.
In the above example the Batch ID is 2612739 and the batch is broken down by Account and Card Issuing Country. By clicking “Generate Report” in the top right corner you can schedule the batch report in the “Reports” section. You can view the individual transactions in the Batch by selecting the “View Transactions” button on the bottom right of the screen.
Copyright © 2013 Elavon, Inc.
Page 43
Sep-13
Explanation of each Column in Batch overview level: Title
Description
Date of Batch
This is the date that the batch was opened, this defaults to the date of the first authorisation request in the batch. It is not the date of batch submission.
Batch ID
This is a batch number assigned by Elavon Payment Gateway; these numbers are not in sequence.
Merchant Number
This is the merchant services number that the transactions have been processed through.
No. of Sales
This displays the total amount and currency for the authorisations in this batch.
No. of Refunds
This displays the total amount and currency for the refundsand rebates in this batch. Refunds/Credits are displayed in blue.
Net Total
This displays the Net total and currency of the batch i.e. Sales/Debits amount minus the Refunds/Credits amount.
Generate Report
This action queues the batch in your “REPORTS” section for download to excel.
View Transactions
This action lists all transactions in the Batch.
.
Copyright © 2013 Elavon, Inc.
Page 44
Sep-13
6.3
To download reports to excel:
In the batch overview level, The “Generate Report” button on the top right of the screen enables you to queue a report in the “Reports” section of the main menu. In the reports section you can then download to an excel spread sheet. 1.
Click on the download icon to the right of the report line to open or save the file.
2.
If you choose to save the file, you can save it as an excel file on your local machine.
3.
The file starts downloading to excel based on your browser settings.
Select the Reports tab.
The report status. Click on the download icon to open or download report.
Copyright © 2013 Elavon, Inc.
Page 45
Sep-13
6.4
Transaction List Level
By choosing View Transactions on the batch overview screen you are taken to the below screen. This screen lists the most recent transactions in the batch.
1.Select arrow to view complete Order ID.
2. Click on ‘Next’ to view next twenty transactions.
1.
You can click on each transaction line to view the individual transactions details for that transaction.
2.
By selecting the arrow on the left of the transaction you can display the complete Order ID.
To view the next twenty transactions, click on the navigation arrow located at the bottom right of the screen to proceed to the next page. Note: Rebates/Refunds are displayed in blue within the Pending screen.
Copyright © 2013 Elavon, Inc.
Page 46
Sep-13
Explanation of columns on Transaction List screen Title
Description
Time Stamp
The time the transaction was authorised.
Order ID
Your unique Order ID that was sent in the authorisation request.
Cardholder Name
The cardholder name.
Status
The status of the transaction in the Pending section will be ‘Pending’
Amount
The Settled amount of the transaction.
Currency
The Currency of the transaction.
Card Type
Displays the scheme of the card used.
Fraud Score (TSS)
This is the score that the transaction received from Risk Manager the fraud scoring tool.
Customer Number
This displays information sent in the Customer Number field of the authorisation. This information can be specific to your company, for example, a reference number that you use to identify your customers. If you are taking transactions through the Terminal, this will be the value that you entered in the Customer Number field. To find out how to send information in this field from your website, please consult the Elavon Auth Developer's Guide.
Prod id
This displays information sent in the Product ID field of the authorisation. This information can be specific to your company, for example, a reference number that you use to identify your products. If you are taking transactions through the Terminal, this will be the value that you entered in the Product ID field. To find out how to send information in this field from your website, please consult the Elavon Auth Developer's Guide.
Var Ref
This displays information from the Var Ref field. This information is specific to your company. If you are taking transactions through the Terminal, this will be the value that you entered in the Variable Ref field. To find out how to send information in this field from your website, please consult the Elavon Auth Developer's Guide.
Copyright © 2013 Elavon, Inc.
Page 47
Sep-13
6.5
Transaction Details Level
You can view more information on a transaction by clicking on the transaction line.
6.5.1
Details
In the Details section you can view general information about the transaction as below.
Currency.
Explanation of Field Titles on Transaction Details screen. Title
Description
Order ID
This is the unique identifier for the transaction.
History
This tab displays the history of the transaction such as authorisation details. If the transaction had been voided or rebated this information can be viewed in this section.
Account
The sub-account that the transaction was processed under. In the example above this is “Internet".
Transaction Amount
The value of the transaction.
Currency
The currency the transaction was processed in.
Copyright © 2013 Elavon, Inc.
Page 48
Sep-13
Title
Description
Timestamp
The date and time the transaction was processed.
Result
The result of the transaction which is passed back by the card holders issuing bank.
Message
This is the result message which is passed back by the card holders issuing bank.
Pas Ref
This is an internal Elavon Payment Gateway reference, unique to each transaction.
Fraud Score (TSS)
This is the score that the transaction received byRisk Manager, the fraud scoring tool.
Batch id
This shows the Batch ID of the batch that the transaction is associated with. If this transaction was still declined and therefore not batched, then this would say "-1". however, in the “Settled” area, there should always be a Batch ID here.
Security Code
This shows the result of the Security Code check. Please see the Appendix for the possible security code results.
AVS Postcode
This shows the result of the Address Verification Service (AVS) on the postcode. Please note that this can only be used for UK mercahnts and you need to have this functionality set up in your system. Please see the appendix for the possible AVS results.
AVS Address
This shows the result of the Address Verification Service (AVS) check on the numbers in the billing address supplied by the customer. Please note that this can only be used for UK merchants and you need to have this functionality set up in your system. Please see the appendix for the possible AVS results.
Cardholder Name
The Cardholder name.
Card Number
This shows the card type and the card number masked with X's for security reasons.
Card Issuer
This displays the name of the bank that issued the card, if that information is available.
Card Issuer Country
The country the card was issued in.
Originating I.P.
This shows the IP address that the transaction was processed through.
Copyright © 2013 Elavon, Inc.
Page 49
Sep-13
Title
Description
Customer I.P.
This shows the IP address of the customer.
Status
This shows the current stage of the transaction process.
Customer Number
This displays information sent in the Customer Number field of the authorisation. This information can be specific to your company, for example, a reference number that you use to identify your customers. If you are taking transactions through the Terminal, this will be the value that you entered in the Customer Number field. To find out how to send information in this field from your website, please consult the Elavon Auth Developer's Guide.
Product Code
This displays information sent in the Product ID field of the authorisation. This information can be specific to your company, for example, a reference number that you use to identify your products. If you are taking transactions through the Terminal, this will be the value that you entered in the Product ID field. To find out how to send information in this field from your website, please consult the Elavon Auth Developer's Guide.
Var Ref
This displays information from the Var Ref field. This information is specific to your company. If you are taking transactions through the Terminal, this will be the value that you entered in the Variable Ref field. To find out how to send information in this field from your website, please consult the Elavon Auth Developer's Guide.
Transaction id
This is an internal Elavon Payment Gateway reference, unique to each transaction.
Comment 1 & 2
This is an available field for your reconciliation. Note: For transactions processed through Reporting and the Virtual Terminal, the ‘Comment 2’ field displays the User who processed the transaction.
Copyright © 2013 Elavon, Inc.
Page 50
Sep-13
6.5.2
Fraud
In the Fraud section you can view the 3d secure information for the transaction.
3D secure result summary is displayed here.
Click here to view 3dsecure transaction details.
Please see table below for detailed description of each.
Explanation of Details on Fraud Transaction Details screen Title UCAF (AAV/CAVV) XID ACS URL ECI
Visa
Description This is the Cardholder Authentication Verification Value created during cardholder authentication. This is a Elavon Payment Gateway generated transaction reference that the merchant sends to the ACS in advance of the cardholder authentication. This is the address of the Access Control Server, the issuing banks website. This is the E-Commerce Indicator, it can be the following values:
MasterCard/Switc h (UKDM)
Ecommerce Indicator (ECI)
Full 3D Secure – cardholder Enrolled Merchant 3D Secure – cardholder not enrolled or attempt ACS server was used 6 1 Non 3D Secure transaction. E.g. a refund or a 3D Secure transaction which failed midway. It is up to the merchant to decide whether or not to 7 0 proceed with a non-3D Secure transaction. The liability shift no longer applies. For more information on 3d Secure implementation and management please see the 3DSecure Developers Guide.
5
2
Copyright © 2013 Elavon, Inc.
Page 51
Sep-13
6.5.3
DCC
In the DCC section you can view the Dynamic currency conversion (DCC) result of the transaction. For more information on DCC implementation please see the DCC Developer’s Guide.
Click here to view DCC transaction details.
Copyright © 2013 Elavon, Inc.
Page 52
Sep-13
6.5.4
History
In the history section, you can view the details of the authorisation and all subsequent actions that have been carried out against the order. These may include settle, rebate and void details.
Subsequent Void.
Original Authorisation.
Copyright © 2013 Elavon, Inc.
Page 53
Sep-13
6.6
Viewing Related Transactions
While in the transaction details screen you can link to related transactions by clicking on the “Cross reference search” icon’s. For example if you click on the Cross reference search tag to the right of the card number this will display all transactions processed on this card. Please see the below screen shot to see the common fields on which a Cross Reference Search can be processed.
You can carry out a cross reference search on all fields with a cross reference search icon as highlighted for the card number above.
Copyright © 2013 Elavon, Inc.
Page 54
Sep-13
6.7
View and Print Receipt
To print a receipt following a transaction, click on the “Printer” symbol. This will open up a new tab in your browser, containing the receipt. Then use the onscreen options to save or print the receipt as necessary.
Click on the printer symbol to open the receipt in a new tab.
You can also view and print the receipt from the transaction details window. Again click on the “Printer” symbol to open up the receipt in a new tab in your browser.
Click on the “Printer” symbol to open the receipt in a new tab.
Copyright © 2013 Elavon, Inc.
Page 55
Sep-13
6.8
Rebating a Transaction
A rebate is a transaction that refunds monies to the cardholder and debits the merchant’s bank account. It uses the card details from the original authorisation transaction; therefore, you do not need the card details to process a rebate. Note: The Rebate transaction type can only be accessed if you have sufficient permissions. You will need to have been assigned the role of Administrator or Power User to gain access to this section. In order to gain access you will need to contact your Administrator User. There are two restrictions for rebates that do not apply to refunds (for more information on processing a refund, please see Section 3.2, Terminal - Refund) ▪
There is an upper limit on the amount that you can rebate: you can partially rebate the transaction, rebate the full amount or rebate any amount up to 115% of the original authorisation. Note: This limitation of 115% does not apply to Irish Laser debit cards.
▪
You can only rebate the transaction up to 180 days after it has originally been processed. After 6 months, you will need to process a refund (see Section 3.2, Terminal - Refund).
Rebate.
Copyright © 2013 Elavon, Inc.
Page 56
Sep-13
To process a rebate: 1. Find the original transaction, you can do this by using the Search on option (see Search on – Search for a single transaction) or navigate through the Settled section. 2. Click on the transaction line to bring you into the transaction details. At the top of the transaction details you can see the button “Rebate” as shown above. 3. You can change the amount that you want to rebate and you can also enter a Comment, Customer Number, Variable Reference and Product ID for reconciliation purposes. 4. You are required to enter your personal login password. 5. Click on “Rebate” to process this transaction. You can then view the rebated transaction in the Pending section.
Change the amount (in cents / pence) to the amount you want to rebate.
Add comments here.
Action Rebate. Enter your login password.
Copyright © 2013 Elavon, Inc.
Page 57
Sep-13
Format and Length of fields: Note: Please be aware that "" means a space. The mandatory fields are marked with a star; these are required in order for the transaction to process. Field
Format
Length
Comment
a-z A-Z 0-9 ' ", + "" . _ - \ / @ ! ? % ( ) * : £ $ € # [ ] | =
0-255
Amount
0-9
0-8
Customer Number
a-z A-Z 0-9 - "" _ . , + @
0-50
Product ID
a-z A-Z 0-9 - "" _ . , + @
0-50
Var Ref
a-z A-Z 0-9 - "" _ . , + @
0-50
Copyright © 2013 Elavon, Inc.
Page 58
Sep-13
7
Fraud Management
This chapter describes the fraud scoring system that Reporting employs to identify potentially fraudulent transactions.
7.1
Fraud Scoring
Reporting Fraud Management is designed to assist merchants with managing fraud at the point of sale by identifying negative data and pattern checking for each transaction in real time. This is a merchant configuration tool and the rules and weights are set by the merchant. The result of this checking is returned with the transaction response. The Fraud Management section of Reporting is used to configure various parameters and settings for Fraud Scoring.Fraud Scoring uses data entered in Reporting and also data sent in the transaction to carry out the checks. This is carried out on a per sub-account basis and needs to be set up individually on each sub-account. You should also reference the Fraud Management User Guide which details how to set up the checks.
7.2
Fraud Rules
When you click on the ‘Fraud Management’ tab in Reporting you are presented with a list of currently enabled/disabled checks on a subaccount basis. You choose the sub-account you wish to apply the rules to from the Account drop-down menu.
Select sub-account from dropdown menu.
Copyright © 2013 Elavon, Inc.
Page 59
Sep-13
The Fraud Rules can be classified into four separate zones. These are: Transaction Screening (Zone 1000): These rules compare the data in the transaction against data supplied through Reporting. These are unique to each merchant. E.g. high risk card number. Data Sanity Checking (Zone 2000): These rules compare certain fields in the transaction against other fields in the transaction. E. g. comparing shipping country to billing country if supplied in the transaction. Pattern Matching (Zone 3000): These rules compare data in a transaction against data from previous transactions. E.g. the same card used with a different name. Post Auth (Zone 5000): These rules can reduce the score based on checks that occur after the authorisation of the transaction. E.g. the address check or security code check if supplied in the transaction.
7.2.1
Enabling/Disabling a Check
Within the Fraud Checks screen, you can enable or disable a rule, choose to send the result of the rule in your response or enable or disable Auto Check. Auto Check allows you to reject transactions automatically based on the Fraud Score. It is not enabled by default; you will need to speak to Elavon Payment Gateway to enable it. To enable a check, you will need to go to the Disabled Checks section within Fraud Checks. This is located at the lower part of the screen.
Click to ‘Enable’
Copyright © 2013 Elavon, Inc.
Page 60
Sep-13
After the check has been enabled, it will then be located in the Enabled checks section on the top part of the screen. By clicking view, you can amend the weight that is given to each rule or disable the rule. You can amend the weight that is given to each rule, which calculates its importance. For example: If you set all weights to 100, then the rules are all of equal importance. If you set rule 1000 to 75 and rule 1010 to 25, then rule 1000 is 3 times more important than rule 1010 and this will be reflected in the score received. See the weights section in the Fraud Management User Guide.
By clicking Edit you can amend the weight of the rule. Click to ‘Disable’
7.2.2
Adding Data to a Check
For rules in Zone 1000 (except 1012,1100) they are configurable via the Edit button contained within the row of the selected rule. This is where you enter the specific data that you wish to have your transactions checked against. To the right of the selected rule, the Default Return Score is displayed. This is the score that is returned if the given rule is not triggered by the data entered for the transaction. This can be amended via the Change button beside the Default Score. To enter a new value for a particular rule, simply enter that value into the relevant field and click Find or Add. You will be then prompted to select which score you wish to have returned for that rule if that value appears in a particular transaction. For example, if you wish to reduce the Fraud Score whenever you receive a transaction from a customer “Joe Bloggs”: Go to rule 1001 – Cardholder Name Click Edit, then enter in “Joe Bloggs” in the text field and click Find or Add. Choose the score you wish to have returned if this value appears in the transaction. Click Save.
Copyright © 2013 Elavon, Inc.
Page 61
Sep-13
Below is an example of how to add data to a check:
Enter Cardholder Name that you wish to reduce the Fraud Score when a transaction contains this name.
Then click ‘Find or Add’.
You can then choose the score you wish to return if the value appears in the transactions Select number from the scale to be returned if information returned is a value submitted in a transaction matches.
To save this Fraud Score, click ‘Save’.
Copyright © 2013 Elavon, Inc.
Page 62
Sep-13
7.3.1 Suitability score screen The transaction score will be displayed in the transaction details, in the suitability score field. You can click on this score to view a breakdown of the checks that have passed and failed. The screen looks as follows:
Within the transaction details, click on the magnifying glass beside Fraud Score to display the Score breakdown for that transaction.
This will display a breakdown of the Fraud Score results for that transaction:
Copyright © 2013 Elavon, Inc.
Page 63
Sep-13
8 8.1
Search
The “Search” option in the Transactions section, allows you can search for a single transaction or alternatively search for a range of transactions based on the search criteria entered. The “Search” menu will display on the left of the screen as below:
Search results can be displayed or queued in the Reports section.
Search Menu.
Copyright © 2013 Elavon, Inc.
Page 64
Sep-13
8.2
Search for a range of transactions
Select sub-accounts to search under.
Select your date range within one calendar month.
You can narrow your search by including known transaction details.
To search for a range of transactions: To search a specific sub-account you can click on the “Account” field and select the subaccount(s) from the drop down menu which will list all your available sub-accounts. To remove accounts from your search simply click the “x” to right of the account name. Please refer to the above screenshot. You will need to enter from and to dates; you can type the desired date or use the calendar by clicking on the provided text boxes for each. The maximum search range is one calendar month. To narrow your search include known transaction details. e.g. Order ID You can then click “Search” to display the screen or “Report” to queue the report for download to an excel spread sheet in the “Reports” section of the main menu. Please refer to the above screenshot.
Copyright © 2013 Elavon, Inc.
Page 65
Sep-13
9 This section covers:
Change Password
Compulsory password change
9.1
Change Password
In Settings, you have the option to change your password.
To change your password click “Edit”.
The change password section will expand as below:
Copyright © 2013 Elavon, Inc.
Page 66
Sep-13
9.2
Compulsory Password Change
Due to our security requirements here at Elavon Payment Gateway we enforce that all Users of Reporting change their password every 90 days. If your password has expired the below screen will display on login.
To change your password successfully, you must use the following criteria: Password must: Be at least 7 characters in length; Contain a mix of at least 3 of the following four groups •
upper-case letter(s)
•
lower-case letter(s)
•
number(s)
•
symbol(s)
You cannot use a previously used password.
Copyright © 2013 Elavon, Inc.
Page 67
Sep-13
9.3
User Management
Note: To access the User Management section of Reporting you will need to have the Administrator role assigned to your User login. The User Management section is located under Settings – User Management. This section covers the following: 1. Adding new Users. 2. User roles and permissions. 3. User registration process. 4. Viewing & Editing existing Users.
Select settings from the navigation menu.
Select User Management.
Copyright © 2013 Elavon, Inc.
Page 68
Sep-13
9.4
Adding new Users
To create a new User click on “+ Add New” as below.
Select to add a new User.
You will then see the following screen:
Copyright © 2013 Elavon, Inc.
Page 69
Sep-13
Format and Length of fields: Note: Please be aware that "" means a space. The mandatory fields are marked with a star; these are required in order for the transaction to process. Field
Description
Format
Length
Email *
This is the Users email address
[A-Z a-z 0-9 . _ % -] + @ [A-Z a-z 0-9 . -]+\\.[a-z A-Z]
5-50
User Name
This is the Users Username
a-z A-Z 0-9 ! _
3-20
First Name
This is the Users First Name
a-z A-Z 0-9 + . ' ; “”,-_ &
0-50
Surname
This is the Users Surname
a-z A-Z 0-9 + . ' ; “”,-_ &
0-50
Enable for automated password reset
This flag determines whether a User can use the automated password reset functionality
Predefined
Predefined
Roles*
A role must be selected for the User in order to specify their User permissions. The role will be one of those described below.
At least one role needs to be selected.
Predefined
Administrator Role *
Users can access all functionality of Reporting and User Management.
At least one role needs to be selected.
Predefined
Power User Role *
Users can access all functionality of Reporting except User Management.
At least one role needs to be selected.
Predefined
Sales Agent *
Users can access the Terminal only
At least one role needs to be selected.
Predefined
Read Only *
Users can view Reporting only.
At least one role needs to be selected.
Predefined
Copyright © 2013 Elavon, Inc.
Page 70
Sep-13
9.5
User roles and permissions
Users of Reporting can be assigned a role which defines the areas and functionality to which they have access. The following roles can be assigned: Administator Power User Sales Agent Read Only Fraud Manager Below are the actions each roles can carry out: Action
Administrator
Power User
Sales Agent
Read Only
Fraud Manager
Ability to view transaction details
Ability to generate, view and download reports Ability to process sales
Ability to perform rebate / void / settle transactions
View the settings general section Change your existing password
Add new Reporting users
Change the Roles of other Users
Ability to perform refunds
Request an Automated Password Reset for other User View Fraud Management Section- View/Edit Fraud Rules
Note: All Users must be assigned at least one role.
Copyright © 2013 Elavon, Inc.
Page 71
Sep-13
Within the User Management section, Administrators can assign roles to existing and new Reporting Users.
User Roles.
Copyright © 2013 Elavon, Inc.
Page 72
Sep-13
9.6
User registration process
Once you have been sent a registration request you will receive and email from
[email protected]. Simply click on the registration link in this email to be brought to the registration page below:
The fields that have been completed in the User Management section by your Administrator User will be populated on the registration page. Note: If the username was set by the Administrator it cannot be changed when you are registering. All fields on the registration page are mandatory unless the Administrator User has deselected “Enable for automated password reset” on the add User screen in User Management. By deselecting this option, the mobile number field is no longer mandatory when setting up a new User. Click “Register” to complete the registration process and you will be directed to login to Reporting. (see section 2.1 Login)
Copyright © 2013 Elavon, Inc.
Page 73
Sep-13
9.7
Viewing & Editing existing Users
1. To view and edit an existing Users details, select the Username from the User Management drop down as below.
2. Select the “View” button to display the Users details.
1. Select the Username from the drop down.
2. Click View to display selected User details.
Copyright © 2013 Elavon, Inc.
Page 74
Sep-13
The Users details are displayed on screen as below:
1. Send Password Reset Email.
2. Click to “Edit” User details.
3. Click to return to previous page.
1. If the User has been set up for Automated password resets you will have the option to “Send Reset Password Email”. This option allows you to send an email to the Users registered email address containing a link to prompt them to change their password. Example email below: “Hi (Your Name), You have requested to reset your password. Please use this link to reset your password within the next 24 hours. Once you open the link you will also receive a text message with your password reset code. https://Reporting.ElavonPaymentGateway.com/reset/80a5ec88-76d7-4b0f-adc5-864cd3764c8 If you did not request for your password to be reset please email support@ElavonPayment Gateway.com to let us know. Regards, Elavon Payment Gateway Support Team”
2. To change the Users details or role click “Edit”. 3. To return to the previous screen click “Back”.
Copyright © 2013 Elavon, Inc.
Page 75
Sep-13
This appendix lists the following: ▪
The current set of result codes returned by the Elavon Payment Gateway system.
Transaction Response Codes Note: All Response Codes are subject to change without notice. Code
00 101 102 103 2xx 3xx 5xx 666
Result 00 101 101 101 101 101 101 101 101 101 101 101 101 102 102 102 102 103 103 103 106 107 108 109 200
Description
Successful Declined by Bank Referral by Bank (treat as decline in automated system such as internet) Card reported lost or stolen Error with bank systems Error with Elavon Payment Gateway systems Incorrect XML message formation or content Client deactivated.
Message AUTH CODE: nnnnnn CANCELLED CARD CARD EXPIRED DECLINED INVALID AMOUNT INVALID CARD NO. INVALID CURRENCY INVALID EXP DATE INVALID MERCHANT INVALID TRANS NOT AUTHORISED RETAILER UNKNOWN UNABLE TO AUTH CALL AMEX CALL AUTH CENTRE REFERRAL REFERRAL B REFERRAL A PICK UP CARD RETAIN CARD Auth Failed - Contact Auth Centre (Generally Switch Card issue number is incorrect) Fails Risk Manager Fraud Checks Using test system. Please use pre-approved test cards ONLY Comms Error – scheduled bank maintenance Unspecified bank error
Copyright © 2013 Elavon, Inc.
Page 76
Sep-13
202 205 301 302 303 303 303 304 305 501 502 502 503 503 504 505 505 505 505 506 506 506 506 507 508 508 508 508 508 508 508 508 508 508 508 508 508 508 508 508 508 508
Network error: cannot connect to EPoS Comms Error – bank connection error. Cannot connect to Database Configuration error with your bank details (acquiring bank) - please contact Elavon Payment Gateway There is no default merchant account set. Please contact Elavon Payment Gateway if you continue to experience this problem. Error in configuration - merchant has more than one config for this currency/card combination Somehow more than one transaction matches these parameters. Can't find transaction details in database Elavon Payment Gateway are currently updating the system. We apologise for the inconvenience. This transaction has already been processed. Compulsory field not present - cannot continue. Please check the Developer Documentation for compulsory fields Type [type] not implemented. Please check the Developer Documentation for allowed types Request type not recognised Request type [type] not allowed for this merchant There is no such merchant id. Please contact Elavon Payment Gateway if you continue to experience this problem. md5hash incorrect - check your code and the Developers Documentation sha1hash incorrect - check your code and the Developers Documentation You are not allowed to access this service from there! The refund password you entered was incorrect. There is no such merchant account. Please contact Elavon Payment Gateway if you continue to experience this problem. No xml in request Too much data Bad xml formation currency/card combination not allowed Invalid data in merchantid field Invalid data in account field Invalid characters in Order ID - please use only A-Z a-z 0-9 _ Please only numbers in amount - see Developers Guide Leading zeros or other error in amount field Zero, negative or insufficient amount specified Invalid data in currency field Invalid data in timestamp field Invalid timestamp Transaction out of date Invalid hash supplied Invalid Auto Settle flag Invalid Auto Settle flag Invalid Data in Billing code field Invalid Data in Billing country field Invalid Data in Shipping code field Invalid Data in Shipping country field Invalid characters in cust num - please use only A-Z a-z 0-9 _ - . , + @
Copyright © 2013 Elavon, Inc.
Page 77
Sep-13
508 508 508 508 508 508 508 508 508 508 508 509 509 509 509 509 509 509 509 509 509 509 509 510 511 512 512 512 512 512 512 512 512 513 514 514 514 514 666
Invalid characters in variable reference - please use only A-Z a-z 0-9 _ - . , + @ Invalid characters in product id - please use only A-Z a-z 0-9 _ - . , + @ Invalid data in card type field Can't find original transaction in database. The original transaction failed! You can't rebate a failed transaction. You may only rebate up to 115% of the original amount. Can't find original transaction in database. This transaction was successful the first time! Can't find original transaction in database. Can't settle a settled transaction. Can't settle for more than 115% of that which you authorised. NonNumeric in Credit card number. Invalid credit card length NonNumeric in issue number. Invalid issue number length Only Switch cards have issue numbers Card number fails Luhn Check Invalid expiry date Card Expiry date in past Expiry month invalid That Card Number does not correspond to the card type you selected An ECI value must be included for MPI enabled accounts. Length of CVV data is incorrect That amount is greater than the max allowed Unable to connect to the merchant response url This transaction has already been rebated and cannot be rebated again. Original transaction not found You may only refund the original card number. You can't refund a delayed transaction that has not been sent for settlement. (You are refunding money to a customer that has not and never will be charged!) Original account was not [account] Original transaction currency was not [currency] You may only refund 115% of the value of the original transaction. This transaction has already been refunded through the epage remote interface and cannot be refunded again. Can't void a settled transaction. Original Transaction Failed! If you just want to give money to the customer use the refund Terminal in emerchant. Original Transaction was Successful! Can't settle a settled transaction. Can't settle a transaction already settling. This account has been deactivated. Please contact Elavon Payment Gateway for further details.
Copyright © 2013 Elavon, Inc.
Page 78
Sep-13
Security Code Results Result M N I U P
Message Security Code Matched Security Code Not Matched Security Code Not checked due to problem Security Code Not checked as Issuer not certified Security Code Not Processed
AVS Results Result M N I U P
Copyright © 2013 Elavon, Inc.
Message Data Matched Data Not Matched Data Not Checked Unavailable Partial Match
Page 79
Sep-13
