How To Use The Rabo Ompo Kassa Dashboard On A Bank Account On A Credit Card Or Debit Card On A Sim Sims.Com (European)

(1)

User Guide

Dashboard of the Rabo OmniKassa

(2)

1 The Rabo OmniKassa dashboard ... 4

2 Logging in ... 5

2.1 The login page of the Rabo OmniKassa dashboard ... 5

2.1.1 Navigation ... 5

2.1.2 Logging in ... 5

2.2 The 'Forgot password' page ... 6

2.2.2 Dialogue window ... 6

2.3 The 'Change password' page ... 7

2.3.2 Dialogue window ... 7

2.4 The ‘Change User Account’ page ... 8

2.4.1 Dialog window ... 8

2.5 Logging out ... 9

3 Transaction management ... 10

3.1 List view ... 10

3.1.2 Search for transactions... 11

3.1.3 Search results ... 14

3.1.4 Exporting transactions list ... 15

3.2 Details view ... 15

3.2.2 Transaction details subwindows ... 18

3.2.3 Validating a transaction ... 21

3.2.4 Cancelling a transaction ... 22

3.2.5 Refunding a transaction ... 23

3.2.6 Export transaction details ... 24

4 Payments ... 25

4.1 List view ... 25

(3)

4.1.3 Search results ... 26

4.1.4 Exporting payment list ... 27

4.2 Details view ... 27

4.2.2 Subwindows ... 28

4.2.3 Exporting payment specifications ... 32

5 Payment pages ... 33

5.1 Default display ... 33

5.2 Uploading your own logo ... 33

6 Additions & modifications ... 35

6.1 Adding a payment method or register service ... 35

6.2 Add a webshop ... 35

6.3 Change name of webshop... 35

6.4 Adding and changing user/contact person ... 36

6.4.1 Changing user role ... 36

7 Questions, system failures ... 37

8 Footer ... 38

9 Appendices ... 39

9.1 Appendix 1: About acquiring and server response codes ... 39

9.1.1 List of acquirer and server response codes for MasterCard and Maestro ... 39

9.1.2 List of acquirer and server response codes for VISA and V PAY ... 42

9.1.3 List of acquirer and server response codes for Bancontact/Mister Cash ... 46

9.1.4 List of acquirer and server response codes for iDEAL ... 48

9.1.5 List of acquirer and server response codes for MiniTix ... 49

9.1.6 Response codes for Incasso, Acceptgiro, rembours ... 49

9.2 Appendix 2: List of currencies ... 50

9.3 Appendix 3: Complementary code ... 51

9.4 Appendix 4: Definitions ... 52

9.5 Appendix 5: Explanation of fields in Excel attachment (specification) with e-mail message “Rabo OmniKassa specificatie uitbetaling” (e-Statement) ... 54

(4)

1 The Rabo OmniKassa dashboard

The Rabo OmniKassa dashboard contains all information on your transactions and payments for all your webshops. Here, you can perform functions such as exporting transactions to your accounting system or refunding online transactions to customers (if the payment method allows). Credit card transactions (MasterCard/Visa) can also be cancelled and validated through the dashboard if you have activated this feature. The dashboard is also where you can change a number of different settings.

To access the Rabo OmniKassa dashboard, you need a username and password. After Rabo OmniKassa has been activated by Rabobank you will receive an e-mail with your username and with a link enabling you to set your own password.

This guide uses a number of different screenshots to help explain how the Rabo OmniKassa dashboard works. It also explains how to navigate to the windows you need and what subsequent options you have.

Chapter 2 explains how to obtain access to the Rabo OmniKassa dashboard and how to set your personal information.

Chapter 3, 'Transaction management', describes the information the Rabo OmniKassa dashboard contains about online payment methods and the various search options available. Here you will also learn how to fully or partially refund online transactions.

Chapter, 'Payments', explains how to view payments to your Rabobank account in the dashboard and see what specific transactions are linked to a given payment.

Your Rabo OmniKassa will grow with your webshop. In chapters 5 and 6, you will read how you can adapt your Rabo OmniKassa to the circumstances your market demands.

Information about how to handle questions, problems or service outages involving the Rabo OmniKassa can be found in chapters 7 and 88.

The schedules, in chapter 9, provide more detailed information about the various values and codes that are or can be used in the Rabo OmniKassa and the dashboard.

Good to know

The transactions (details) of the Rabo OmniKassa payment can not only be found in the Rabo OmniKassa Dashboard, but are also reported in the Excel attachment of the e-mail message ‘Rabo OmniKassa payment details’. This e-mail message (e-Statement) is sent by Rabobank to the contact person of the webshop on the day a payment is made to the webshop for one or more successful transactions. You will find an explanation of the most important fields of the Excel attachment referred to above in bijlage 1.

(5)

2 Logging in

2.1 The login page of the Rabo OmniKassa dashboard

2.1.1 Navigation

 How do you open this page?

 This page is accessed from the following URL: https://dashboard.omnikassa.rabobank.nl. This page is the starting point of the Rabo OmniKassa dashboard.

 Where can you go from this page?

 Once you have successfully logged in, you are automatically sent to the list view of the Transactions service (see section 3).

 If you have forgotten your password, or if your password has expired, navigate to the 'Forgot password' page through the link at the bottom of the login page.

2.1.2 Logging in

Image 1: The ‘login’ page

 When you need to log in to the Rabo OmniKassa dashboard, type your username and password in the appropriate fields and click .

 Your password must consist of a minimum of 10 and a maximum of 20 characters, and must include at least one uppercase letter, one lowercase letter and one number.

(6)

 After Rabo OmniKassa has been activated by Rabobank you will receive an e-mail with your username and with a link enabling you to set your own password.

2.2 The 'Forgot password' page

2.2.1 Navigation

 Click on the link 'Click here if you forgot your password' at the bottom of the login page (see section 2.1.2).

 Because you can open this page even if you are not logged in, there are no navigation URLs available on this page. This means that you cannot access any other dashboard pages from here.

2.2.2 Dialogue window

Image 2: Request new password

 If you need to request a new password: enter your username and e-mail address in the appropriate fields and click .

 To clear the form, click .

 After sending the form, a confirmation message appears. The new, temporary password is sent to the registered e-mail address.

 You can request your username if you have forgotten it, or you can have your username unblocked if it has been blocked. To request this, contact the Support Team Rabo OmniKassa. You can reach the team by phone on 0900-0400180 (Mondays through Fridays from 08.00 am to 07.30 pm) or by e-mail at: contact@omnikassa.rabobank.nl. From abroad the team is available by phone on +31 30 7122117.

(7)

2.3 The 'Change password' page

2.3.1 Navigation

 After you are logged in, click on the 'Change password' link found on the heading of any page.

Image 3: Going to the 'Change password' page

 After you log in, the heading with links is available on all dashboard pages. This heading provides links for the following functions:

 access to user-configurable settings: change password, change e-mail address  access to the individual services for which you are authorised

 log out of the dashboard

 access to the Rabobank website (by clicking on the logo)  change the language of the dashboard

 After changing your password, you can go to the dashboard start page by clicking the appropriate link at the top of the confirmation message.

2.3.2 Dialogue window

Image 4: The ‘Change password’ dialog window

 To change your password, type your current password once and your new password twice in the appropriate fields, and then click .

 After sending the form, your password is changed and a confirmation message appears in the page. You can then go back to the dashboard start page.

(8)

2.4 The ‘Change User Account’ page

 After you are logged in, click on the 'Change User Account' link found on the heading of any page.

Image 5: Going to the 'Change User Account' page

 After you log in, the heading with links is available on all dashboard pages. This heading provides links for the following functions:

 access to user-configurable settings: change password, change e-mail address  access to the individual services for which you are authorised

 log out of the dashboard

 access to the Rabobank website (by clicking on the logo)  change the language of the dashboard

 After changing your e-mail address, you can go to the dashboard start page by clicking the appropriate link at the top of the confirmation message.

2.4.1 Dialog window

Image 6: The ‘Change e-mail address’ dialog window

 To change your e-mail address, type your surname and first name and then enter your new e-mail address twice in the appropriate fields. Then click .

 After sending the form, your e-mail address is changed and a confirmation message appears in the page.

(9)

2.5 Logging out

Image 7: Logging out To log out of the dashboard, click on the link .

(10)

3 Transaction management

3.1 List view

3.1.1 Navigation

 Once you have successfully logged in, you are automatically sent to the list view of the Transactions service.

 In the menu bar, click 'Transactions’. The page with the list of transactions opens immediately.

Image 8: To go to the transactions list, click on the 'Transactions' option in the menu bar.  Or, if you find yourself on the 'Payments' page, click the 'Transactions' link in the menu

bar to go back to the transactions list.

Image 9: To go to the transactions list, click on 'Transactions' in the menu bar.

 Or, if you find yourself on the ‘Transaction details’ page, click the 'Transactions list' link or the 'Return' link in the navigation path in the submenu.

Image 10: Going to ‘Transactions list’ from the ‘Transaction details’ page using the navigation path

 You can view the details of a transaction by clicking on any line in the list. The selected line is shaded in dark grey.

(11)

Image 11: The ‘Transactions’ page Possible “Payment”

(see image 11) status Description

--- This is the status during the day the transaction is initiated.

Waiting for creation The day after initiation this status will appear while transaction information is being verified.

Created Settlement date has been determined To be settled Settlement in progress

Settled / Credited Transaction has been settled

Settled / Debited Refund or chargeback has been settled

3.1.2 Search for transactions

3.1.2.1 The subwindow for simple searches

(12)

 Fields

A number of different fields are available for the search instruction:

 Transaction Reference: Enter the transaction reference here. This is the required reference per unique transaction.

 Order Number: Here, enter the optional order number1_{that you may use to assign the}

transaction your own reference in the payment request. Consult the integration guide for the structure of the payment request.

Tip: You can use a wildcard (*) in either field (transaction reference or order number). For example, if you enter '12*' in the order number field, the search results will show all transactions with an order number beginning with 12.

 Date From/to: Here, enter the date range within which the transaction or transactions you are searching for fall.

 Time From/to: Here, enter the time range within which the transaction or transactions you are searching for fall.

Tip: You can enter values in the date fields either by typing them or using the calendar icon . A few examples are provided to show the date notation to use.

 Status: You can search for transactions of a specific status. A status entered into this field must be one of the following simple statuses:

o Successful

o To be authorised (only if validation is used) o To be settled (only for refunds)

o Not successful

See Appendix 1 for more information about the underlying technical statuses.

 Performing a search

Enter all desired search criteria and click . A list of all transactions meeting the criteria is displayed.

 Clearing fields

To restore all fields to their default values, click .

 Show/hide search criteria

You can show or hide the dialog window with search criteria at any time. To do this, click >Hide or >Show at the top right of the window.

1_{To be able to find (for instance) the name of your customer in a transaction in your own (order) records, it is advisable to}

use the optional field ‘orderId’ in the payment request. This field allows you to assign a reference code to the transaction. This reference code will then be included in the response message. Manual or automated reconciliation with the details in your own (order) records will be possible on the basis of the details in that response message, enabling you (for instance) to find the name of your customer. For this to be possible, your customers must (at some time in the past) have registered with their name in your webshop and every order/purchase must be linked to that registration.

The reference code ‘orderId’ can also be found in the Rabo OmniKassa dashboard (Order Number) and is stated in the Excel attachment in the e-mail message ‘Rabo OmniKassa payment details’. The Integration Guide Rabo OmniKassa provides information on using the optional field ‘orderId’ in the payment request (sections 2.2, 5.1 and chapter 6).

(13)

3.1.2.2 The subwindow for advanced searches

 How do you open this window?

 In the Search window, click >Advanced search. The page with the transactions list opens immediately. Close this window by clicking >Close advanced search, to the left of the centre of the subwindow.

Image 13: The subwindow for advanced searches

 Fields

An advanced search includes all the fields from the simple search, plus the following:  Payment method: Choose from a set list, which may include iDEAL, MiniTix, Visa,

MasterCard, Maestro, V PAY, Bancontact/Mister Cash.  Webshop: Select one of your webshops from the list.

 Amount min/max: Here, enter the range within which the amount of the transaction or transactions you are searching for fall.

 Technical status: A status allowed by the payment method in question. See Appendix 1 for a list of the possible technical statuses.

Tip: To find all credit card transactions that still need to be validated, search for the technical status 'To be validated'.

 Currency: The currency in which the transaction was paid. See Appendix ‎1 for a list of possible currencies.

 Cre/Deb: You can search for transactions with the following values:

Image 14: Search values for Cre/Deb

When your customer purchases a product or service in your webshop and pays for it using the Rabo OmniKassa, or if a chargeback of a credit card transaction proves to be in error,

(14)

this results in a credit to your Rabobank account. Credits can be searched for using the following terms:

 Credit: This value shows all successful transactions by your customers.

 Credit for chargeback: This value shows all chargebacks that were wrongly settled and which have been correctly rerouted to you.

 All credits: This value shows all transactions marked either ‘Credit’ or ‘Credit for chargeback’.

If you yourself make a repayment on a previous transaction by one of your customers, or if your customer submits a chargeback, the result is a debit against your Rabobank account.

 Debit for chargeback: This value shows all chargebacks settled at the instruction of your customer. Prior to this settlement, you will have received an e-mail notifying you of the chargeback.

 Debit for refund: This value shows all refunds that you yourself have created.  All debits: This value shows all transactions marked either ‘Debit for chargeback’

or ‘Debit for refund’.

 Clearing fields

You can call up or hide the dialog window with search criteria at any time. To do this, click >Hide or >Show at the top right of the window.

3.1.3 Search results

Image 15: Transactions search result

(15)

You can use to define how many transactions per page are displayed. Clicking on a column heading sorts the values by that field.

The column Cre/Deb displays the same text with a different background colour: indicates a transaction performed by a customer.

indicates a refund transaction performed by you.

indicates a chargeback settled at the instruction of your customer. Prior to this settlement, you will have received an e-mail notifying you of the chargeback.

indicates a chargeback that was wrongly applied and has been correctly rerouted to you.

The icon is shown for transactions that have at least one refund in their transaction history.

You can jump to the desired page by entering the page number in the field and clicking OK, or by clicking the left/right arrows. This page selector is located above the transactions list to the right.

3.1.4 Exporting transactions list

You can export the search results together with the search criteria to a PDF, DOC or XLS file. Select the desired file format in the drop-down menu and then click OK.

Tip:

If a payment has been made to you from Rabo OmniKassa, an mail will always be sent to the e-mail address that was stated when applying for Rabo OmniKassa. This e-e-mail contains important details on the payment made and will include a CSV file as an attachment. This file contains the details of the payment and the underlying Rabo OmniKassa transactions. You can also use this CSV file for reconciliation purposes.

3.2 Details view

3.2.1 Navigation

 On the Transactions page, click a transaction line in the search results list (see previous descriptions).

(16)

Image 16: The ‘Transactions’ page

 Or, on the payment details page, click a transaction line in the search results list (see description below).

Image 17: Going to the transaction details from the ‘Payment details’ page

 Your search results

(17)

Image 18: Transaction details

 To the details of another transaction: in a window with transaction details, click (top or bottom of the window). The details of the previous or next transaction in the search results is displayed.

 To the last page opened: click (top or bottom of page).

 To the page with the details of a payment: click the underlined link (in this example, 635856) in the Payment details window, or on the underlined Details link next to Pay out in the Transaction history subwindow.

 To jump to the page with details of a refund and then back to the original transaction to which the refund is linked. Click on the underlined Details link next to Refund remittance in the Transaction history subwindow.

 From the details of a refund, you can return to the original transaction by clicking on the underlined Initial transaction link under Refund in the Transaction details subwindow.

(18)

Tip: If you want to know more about a field on a page, hover your mouse pointer over it.

Tip: You can hide a subwindow at any time by clicking . To show it again, click .

3.2.2 Transaction details subwindows

3.2.2.1 Transaction details & Order subwindows

Image 20: The subwindows Transaction Details & Order

The subwindow transaction details shows the following information about a transaction:

 Transaction type: This can be one of the following values: 'Payment by customer', 'Refund', 'Negative repayment' or 'Positive repayment'.

 Creation date: The date on which the transaction was created.

 Initial amount: The original amount and the currency of the transaction.

 Current balance: The current balance of the transaction. If the icon is displayed next to the amount, the transaction includes a repayment that has not yet been accounted for in the balance.

 If the transaction is a refund, only the Amount field will be displayed. This shows the amount and the currency of the transaction.

 Status: The status of the transaction, with the technical status in round brackets. See appendix ‎1 for more information about transaction statuses.

 Payment method: The payment method used for the transaction.

 Customer account: The account number of the customer in question (this function is not yet available).

The Order subwindow shows the following information about the order associated with the transaction:

 Order number: This field may be used in the payment request (see integration guide) to give the transaction a unique reference code. This is an alphanumeric code with a

maximum of 32 characters.

(19)

3.2.2.2 The Payout details subwindow

Image 21: The ‘Payout details’ subwindow

This subwindow shows the information on the payment (credit) to your Rabobank account to which the transaction is linked.

 Transaction included in payment: The link from your bank statement to the transaction involved in this payment. The value shown is the reference number of this payment.

 Payout date: The date on which the payment is or will be made.

 Payout status: The status of the payment. Possible values are 'Settled' or ‘Date set'.  Payout amount: The amount and the currency of the payment.

3.2.2.3 The Transaction history subwindow

Image 22: The ‘Transaction history’ subwindow

This subwindow shows the various steps in the history of the transaction. The possible steps are:  Initial transaction: Your customer's first transaction.

 Refund remittance: This may be a full or partial refund. The underlined Details link next to Refund remittance is a link to the transaction details of the refund.

 Pay out: The payout of the transaction. The underlined Details link next to this reference is a link to the transaction details.

 Cancellation: The cancellation of the transaction. This may relate to the entire transaction or a portion of the transaction, and may appear one or more times.

 Validate (if used): The validation of the transaction. This may be full or partial and may only appear once.

(20)

3.2.2.4 The Technical details subwindow

Image 23: The ‘Technical details’ subwindow

 Server response: This field contains a code that indicates the status of the transaction. The code is also notified to you in the response to your payment request. If the code is 00, the transaction was successful. Any other value indicates that there was a problem with the transaction. The value and the significance of the code differs for the different payment methods: see appendixe 9.1 of this user guide. The integration guide provides the information you need to write the payment request and process a response message.  Netsurfer IP address: The IP address of the customer who made the transaction.  Visual cryptogram: Indicates whether the CVV (Card Verification Value) was or was not

entered during the transaction.

 Liability shift: This field contains a technical code that indicates the status of the processing of a credit card transaction with the 3-D Secure process. Code ‘0’ means that the transaction is processed under the 3-D Secure protocol for both the webshop and the card holder. Code ‘2’ means that the card holder does not join the 3-D Secure protocol. Code ‘3’ means that a 3-D Secure transaction has started.

 Acquirer response code: Contains the response code from the acquirer's authorisation server: see appendix 1 of this user guide.

 Complementary code: This field contains a technical code that provides supplemental information about the result of the fraud check on a credit card transaction. See Appendix 3: Complementary code for more information about the fraud check.

 Complementary information: Explanation of the complementary codes for the additional fraud checks.

 Client identifier: The identification number of the customer in your system (this function is not yet available).

 Transaction condition: This field contains a technical code that indicates the status of the 3-D Secure process.

The codes ‘0’, ‘1’, ‘9’ successively mean: 3-D Secure ‘guarantee’ is applicable, 3-D Secure ‘guarantee’ is not applicable, 3-D Secure ‘guarantee’ could not be determined. An empty field (no code) means that the 3-D Secure 'guarantee' could not be checked upon.  Transaction score: Colour of the transaction evaluated.

 Authorization code: The ID of the acquirer in Rabo OmniKassa.

(21)

 Return context: The return context in your system (this function is not yet available).

3.2.3 Validating a transaction

Image 24: Validating a transaction

If in a payment request you have included the instruction that after initiation, a credit card transaction (1) must be validated automatically after a given number of days, or (2) must be validated manually by the dashboard user, you will see the button as long as the status of the transaction allows validation. See appendix 1 for more information about transaction statuses.

How you arrange (1) deferred automatic validation or (2) manual validation of credit card transactions can be found in section 5.1 of the integration guide (optional fields in payment request). Important:

If you use either one of these two options, be sure you are not validating a credit card transaction more than 6 days after authorisation. After that time, the authorisation is no longer valid and you run the risk that the card issuer may reject the transaction.

Click the button to select the amount you wish to validate. Please be aware that you can validate a transaction only once!

Image 25: Select the amount to be validated

Enter the amount you wish to validate, and confirm this by clicking . If the confirmation window is open and you want to change the amount, click and then click the OK button to validate.

(22)

Image 26: Confirm the validation

3.2.4 Cancelling a transaction

Image 27: Cancelling a transaction

If a credit card transaction has the status 'Successful (Submitted for processing)', you can cancel this transaction with the button. See appendix ‎1 for more information about transaction statuses.

When you click this button, you can select the amount you wish to cancel. You can run a cancellation on a single transaction multiple times, as long as the transaction status allows and the upper limit of cancellation has not yet been reached.

Image 28: Select the amount to be cancelled

Enter the amount you wish to cancel, and confirm this by clicking . If the confirmation window is open and you want to change the amount, click in this window and then click in the cancellation screen again.

(23)

Image 29: Confirm the cancellation

3.2.5 Refunding a transaction

Image 30: Refunding a transaction

If you have registered a payment method that allows refunds (e.g. iDEAL, credit card), you will see the button on transactions that allow refund status. See appendix 1 for more information about transaction statuses.

When you click this button, you can select the amount you wish to refund. You can run a refund on a single transaction multiple times, as long as the transaction status allows and the upper limit for refunding has not yet been reached.

Image 31: Select the amount to be refunded

Enter the amount you wish to refund, and confirm this by clicking . If the confirmation window is open and you want to change the amount, click and then click

again. Important:

1. Refunds cannot be paid to a customer by making your own transfer by internet banking or mobile banking to the account number from which you receive the payments for Rabo OmniKassa transactions. This is because that account number is not actually your customer's

(24)

account, but an account held by Rabobank. If you accidentally make a payment to this account, our only option is to return it to you.

2. The ‘Refund’ function is not available between 10.00 p.m. and 11.00 p.m..

3. Refunds to a customer will be paid on the 2nd working day after you have entered and confirmed a refund order in the Rabo OmniKassa dashboard..

Image 32: Confirm refund

3.2.6 Export transaction details

You can export the transaction details to a PDF, DOC, XLS or CSV file. Select the desired file format in the drop-down menu and then click OK.

Tip:

(25)

4 Payments

4.1 List view

4.1.1 Navigation

 Click on the 'Payments' link in the menu bar. This takes you directly to the page with the list of payments.

Image 33: Going to payments through 'Payments' in the menu bar

4.1.2 Payment search

Image 34: The dialog window for payment searches

 Fields

 Payment number: Enter the 6-digit payment reference number here.

 Payment date from/to: Here, enter the date range within which the payment or payments you are searching for fall.

Tip: You can enter values in the date fields either by typing them or using the calendar icon . A few examples are provided to show the date notation to use.

 Amount min/max: Here, enter the range within which the amount of the payment or payments you are searching for fall.

 Cre/Deb: Here, select the values you want to use to filter the results: credit (payment), debit (collection) or both (all). Collections may happen if you have sold less on a day than

(26)

you have refunded or paid back to a customer/credit card holder based on a chargeback claim.

Enter all desired search criteria and click . A list of all payments meeting the criteria is displayed.

 Clearing fields

You can show or hide the dialog window with the search criteria at any time. To do this, click >Hide or >Show at the top right of the window.

4.1.3 Search results

At the top of the list, you see the number of payments that meet the search criteria.

Payments that meet the criteria are displayed in a table. Click on a line to display the details of that payment.

Image 35: Search results list Clicking on a column heading sorts the values by that field.

is displayed for transactions under which a payment was credited to your bank account. is displayed for transactions under which a payment was debited from your bank account. You can use the drop-down menu to set how many transactions will be displayed per

page .

You can jump to the desired page by entering the page number in the field and clicking OK, or by clicking the left/right arrows.

(27)

4.1.4 Exporting payment list

You can export the search results together with the search criteria to a PDF, DOC, XLS or CSV file. Select the desired file format in the drop-down menu and then click OK.

Tip:

4.2 Details view

4.2.1 Navigation

 On the Payments page, click a payment line in the search results list (see previous descriptions).

Image 36: View payment details by clicking on a payment line in the list.

 Or: on the page with transaction details, click the reference number of the payment in the Payout subwindow.

 Or: on the page with the transaction details, click the Details link next to Payout.

Tip: You can hide the subwindow by clicking . To show it again, click .

(28)

 To the details of a payment: click on a payment line in the list with the search results for payments.

Image 37: Payment details

 To the details of another payment: in a window with transaction details, click (top or bottom of the window). The details of the previous or next payment in the search results is displayed.

 To the last page you opened: click (top or bottom of the page).

4.2.2 Subwindows

4.2.2.1 The Payment details subwindow

(29)

This subwindow shows the following details on a payment:

 Payment number: The link from your bank statement to the transactions (one or more) that make up this payment. The value shown is the reference number of this payment.  Payment date: The value shown is the date on which the payment was carried out.  Amount: This field displays the type (Cre/Deb), the amount and the currency of the

payment.

 Contract account: This shows the number of your bank account linked to the contract.

4.2.2.2 Transaction search subwindow

Multiple transactions may be linked to the same payment. You can use different criteria to search for specific transactions.

4.2.2.3 The subwindow for simple searches

Image 39: The subwindow for simple searches

 Fields

 Date from/to: Here, enter the date range within which the transactions you are searching for fall.

 Amount min/max: Here enter the range of transaction amounts you are looking for. Transactions that fall within that range will appear in the results list.

 Transaction reference: Enter the transaction reference here. This is the required reference per unique transaction.

 Order number: This field may be used in the payment request (see integration guide) to give the transaction a unique reference code. This is an alphanumeric code with a

maximum of 32 characters.

Tip: You can use a wildcard (*) in either field (transaction reference or order number). For example, if you enter '12*' in the order number field, the search results will show all transactions with an order number beginning with 12.

(30)

 Clearing fields

You can show or hide the subwindow with search criteria. To do this, click >Hide or >Show at the top right of the window.

4.2.2.4 The Advanced search subwindow

Image 40: The ‘Advanced search’ subwindow

 Opening the Advanced search dialog window

Open the Advanced search subwindow by clicking >Advanced search. You can close this window by clicking >Close advanced search.

 Fields

An advanced search includes all the fields from the simple search, plus the following:  Payment method: Choose from a set list, which may include iDEAL, MiniTix, Visa,

MasterCard, V PAY, Bancontact/Mister Cash.

 Webshop: Select one of your webshops from the list.

 Currency: The currency in which the transaction was paid. See Appendix ‎1 for the list of possible currencies.

(31)

 Cre/Deb:

Image 41: Search values for Cre/Deb

When your customer purchases a product or service in your webshop and pays for it using the Rabo OmniKassa, or if a chargeback of a credit card transaction proves to be in error, this results in a credit to your Rabobank account. Credits can be searched for using the following terms:

 Credit: This value shows all successful transactions by your customers.

 Credit for chargeback: This value shows all chargebacks that were wrongly settled and which have been correctly rerouted to you.

 All credits: This value shows all transactions marked either ‘Credit’ or ‘Credit for chargeback’.

If you yourself make a repayment on a previous transaction by one of your customers, or if your customer submits a chargeback, the result is a debit against your Rabobank account.

 Debit for chargeback: This value shows all chargebacks settled at the instruction of your customer. Prior to this settlement, you will have received an e-mail notifying you of the chargeback.

 Debit for refund: This value shows all refunds that you yourself have created.  All debits: This value shows all transactions marked either ‘Debit for chargeback’

or ‘Debit for refund’.

4.2.2.5 Transactions list

At the top of the list, you see the number of transactions that meet the search criteria. Transactions linked to the payments which meet the criteria are displayed in a table. Click on a transaction line to display the details of that transaction.

Image 42: Transactions search result Clicking on a column heading sorts the values by that field.

The column Cre/Deb displays the same text with a different background colour: indicates a transaction performed by a customer.

indicates a refund transaction performed by you.

indicates a chargeback settled at the instruction of your customer. Prior to this settlement, you will have received an e-mail notifying you of the chargeback.

(32)

4.2.3 Exporting payment specifications

You can export the specification details to a PDF, DOC, XLS or CSV file. Select the desired file format in the drop-down menu and then click OK.

Tip:

(33)

5 Payment pages

5.1 Default display

In order to allow customers to pay in the Rabo OmniKassa, the webshop must be able to send payment requests to the Rabo OmniKassa server. The Rabo OmniKassa server sends the result of the payment request as a response message back to the webshop. The payment status received in the response message is displayed in the dashboard as described above. The integration guide explains how to program a payment request and response message. This guide can be found on the Rabobank website: www.rabobank.nl/omnikassa-support under ‘+ Hoe integreer ik de Rabo OmniKassa in mijn webwinkel?’.

The payment page your customer sees is composed based on the payment request. If you do not allow your customer to select a payment method on your website, then the customer will see a screen that looks like this one (depending on the activated payment methods):

Image 43: The ‘Default payment’ page

The payment page in Rabo OmniKassa is available for your customers in eight languages. This page will be adjusted to the browsersettings and device your customer is using at that time.

5.2 Uploading your own logo

After integrating the Rabo OmniKassa in your webshop, you can supply a logo to be uploaded for display on the payment page, to better integrate the Rabo OmniKassa with your own visual

(34)

identity. We will then replace the Rabobank logo (top left) with your company logo on the payment page.

Image 44: Company logo on payment page Your logo must conform to the following requirements:

 File format: PNG (may include transparency)  Dimensions: 120 x 100 pixels

 File name: webshopname_logo.png (replace 'webshopname' with your webshop's name) E-mail your desired logo to:

contact@omnikassa.rabobank.nl

.

(35)

6 Additions & modifications

6.1 Adding a payment method or register service

Go to www.rabobank.nl/omnikassa, select and then select:

6.2 Add a webshop

6.3 Change name of webshop

Choose a familiar name to make sure your webshop is recognised by your customers. The default reference we use on your customer's statement is the URL (www.test.nl) of your webshop. You can change this description or the name of your webshop in the dashboard by going to the following change option:

(36)

6.4 Adding and changing user/contact person

If you need to change the data of the general contact person for the Rabo OmniKassa (main user) or technical contact person, use the first link. Choose the second link to change the following user information:

Each new user will receive an e-mail at the e-mail address that was stated when the user concerned was added. The e-mail will state the username and includes a link that enables users to set their own password within a period of 5 days. Users can log in on the Rabo OmniKassa dashboard by using the combination of their username and the corresponding password.

6.4.1 Changing user role

Roles define what rights a user has in the dashboard and what data sets he/she can access through the access point. The available roles and their rights are described below.

 Manager

o Read-only access to all transaction and payments pages o Functions in transaction management (all functions) o Exporting transactions and payments

 Authoriser

o Read-only access to all transaction and payments pages o Functions in transaction management (cancel, validate) o Exporting transactions and payments

 Refunder

o Read-only access to all transaction and payments pages o Functions in transaction management (refund)

o Exporting transactions and payments  Consulter

o Read-only access to all transaction and payments pages o Exporting transactions and payments

(37)

7 Questions, system failures

Contact the Support Team Rabo OmniKassa with any questions or issues by phone on 0900-0400180 (Mondays through Fridays from 08.00 am to 07.30 pm) or by e-mail at:

contact@omnikassa.rabobank.nl.

From abroad the team is available by phone on +31 30 7122117.

Known service disruptions affecting the Rabo OmniKassa or any of the underlying payment methods and/or register services are reported onwww.rabobank.nl/omnikassa-actueel. On this page you can also track the status of any service outages.

(38)

8 Footer

At the bottom of every page in the application, there is a footer that provides a link to the Rabobank site. Just click the Rabobank name in this line.

Image 45: Footer

You can call up a form that can be used to ask questions to the Support Team Rabo OmniKassa. Do this by clicking on the word Contact in the footer.

Image 46: The contact form

Enter your message to the Support Team Rabo OmniKassa in the appropriate box. Also enter the e-mail address at which you would like to receive a reply.

To close the form without sending a message, click or .

(39)

9 Appendices

9.1 Appendix 1: About acquiring and server response codes

The acquirer and server response codes are shown in the subwindow ‘Technical details’ of the Rabo OmniKassa dashboard. See for more information paragraph 3.2.2 until 3.2.4 of this user guide.

The Rabo OmniKassa server sends response messages (HTTP POST) to the URLs defined in the payment request. It will send them to the URL specified in the normalReturnUrl field (return-URL) by default. As an option, a second response message can be sent automatically to the URL in the field automaticResponseUrl (report-URL). The response message contains information on the status of the payment (one of the server response codes listed below) on the basis of which the webshop can further process the transaction. More information about response messages is provided in chapter 6 of the Integration Guide Rabo OmniKassa.

You will find all acquirer and server response codes for all payment means below (9.1.1 – 9.1.5).

9.1.1 List of acquirer and server response codes for

MasterCard and Maestro

MasterCard/Maestro

Rabo OmniKassa Dashboard

Acquirer

response code

Description

Server

response code

Description

Status

00 Successful

approval/completion

00 Captured

Successful

00 Successful

approval/completion

00 To validate

To authorize

1

00 Successful

To be settled

2

01 Contact card issuer

05

Refused Niet succesvol

02 Refer to card issuer

02 Referral

Not successful

03 Invalid merchant

03 Refused

Not successful

04 Capture card

05

Refused Not successful

04 Lost card

05

1

This status appears if one of the optional fields ‘captureDay’ and ‘captureMode’ is used in the Data field of the payment request in case of a MasterCard transaction and capturing/authorization is not yet done.

2

(40)

MasterCard/Maestro

Rabo OmniKassa Dashboard

Acquirer

response code

Description

Server

response code

Description

Status

04 Stolen card

05

05 Do not honour

05

05 Invalid/nonexistent "To

Account" specified

05

05 Invalid/nonexistent

"From Account"

specified

05

05 Invalid/nonexistent

specified (general)

05

12 Invalid transaction

12

12 Invalid Authorization

Lifecycle

12

13 Invalid amount

30

14 Invalid card number (no

such number)

14 => 75

3 Refused Not successful

15 Invalid Issuer

05

25 Unable to route

transaction

25 Refused

Not successful

31 Authorization System or

issuer system

inoperative

90 Cancelled

Not successful

51 Insufficient funds/over

credit limit

05

3

(41)

MasterCard/Maestro

Rabo OmniKassa Dashboard

Acquirer

response code

Description

Server

response code

Description

Status

54 Expired card

05

57 Transaction not

permit-ted to issuer/cardholder

05

58 Transaction not

permit-ted to acquirer/terminal

05

61 Exceeds withdrawal

amount limit

05

61 Exceeds withdrawal

count limit

05

62 Restricted card

05

89 Invalid PIN

89 => 75

89 Allowable number of PIN

tries exceeded

89 => 75

89 Unacceptable PIN

-Transaction Declined-

Retry

89 => 75

3

Refused

Not successful

94 Duplicate transmission

detected

90

Cancelled Not successful

96 Format error

30

96 PIN validation not

possible

90 Cancelled

Not successful

96 Cryptographic failure

90 Cancelled

Not successful

96 System error

90

Cancelled Not successful

3

(42)

9.1.2 List of acquirer and server response codes for VISA

and V PAY

VISA/V PAY

Rabo OmniKassa Dashboard

Acquirer

response code

Description

Server

response code

Description

Status

00 Successful

approval/completion

00 Captured

Successful

00 Successful

approval/completion

00 To validate

To authorize

1

00 Successful

To be settled

2

03 Invalid merchant or

service provider

03 Refused

Not successful

04 Retain card

05 Refused

Not successful

04 Retain card special

condition (other than

lost/stolen card)

05

04 Retain card (lost card)

05

04 Retain card (stolen card)

05

05 Do not honour

05 Refused

Not successful

05 Invalid biller information

05

05 PIN Change/Unblock

request declined

05

05 Unsafe PIN

05

05 Stop Payment Order

05

1

This status appears if one of the optional fields ‘captureDay’ and ‘captureMode’ is used in the Data field of the payment request in case of a VISA transaction and capturing/authorization is not yet done.

2

(43)

VISA/V PAY

Rabo OmniKassa Dashboard

Acquirer

response code

Description

Server

response code

Description

Status

05 Revocation of

Authorization Order

05

05 Revocation of All

Authorization Order

05 Refused

Not successful

12 Invalid transaction

12

12 Security violation

12

12 Unable to locate

previous message (no

match on retrieval

reference number)

12

12 Previous message

located for a repeat or

reversal

12

12 Transaction cannot be

completed; violation of

law

12 Refused

Not successful

12 Surcharge amount not

permitted on Visa cards

12 Refused

Not successful

12 Cash service not

available

12

12 Cash request exceeds

issuer limit

12

13 Invalid amount

30

14 Invalid account number

(no such number)

14

(44)

VISA/V PAY

Rabo OmniKassa Dashboard

Acquirer

response code

Description

Server

response code

Description

Status

14 No savings account

14

15 No such issuer

05 Refused

Not successful

25 Unable to locate record

in file or account

number is missing from

the inquiry

25

25 Invalid date (For use in

private label card

transactions and check

acceptance transactions)

25

25 Issuer or switch

inoperative (STIP not

applicable or available

for this transaction)

25 Refused

Not successful

25 Destination cannot be

found for routing

25 Refused

Not successful

33 Expired card

05

51 Insufficient funds

05

57 Transaction not

permitted to cardholder

05

58 Transaction not allowed

at terminal

05

61 Exceeds withdrawal

amount limit (activity

amount limit exceeded)

05

61 Activity count limit

exceeded

(45)

VISA/V PAY

Rabo OmniKassa Dashboard

Acquirer

response code

Description

Server

response code

Description

Status

62 Restricted card

05

77 Re-enter transaction

05

89 Incorrect PIN

89 => 75

89 Allowable number of

PIN-entry tries exceeded

89 => 75

89 Incorrect CVV

89 => 75

3

Refused

Not successful

89 Decline for CVV2 failure

89 => 75

89 Card authentication

failed

89 => 75

96 Error

90 Cancelled

Not successful

96 File is temporarily

unavailable

90 Cancelled

Not successful

96 PIN cryptographic error

found (error found by

VIC security module

during PIN decryption)

90 Cancelled

Not successful

96 Unable to verify PIN

90 Cancelled

Not successful

96 System malfunction

90 Cancelled

Not successful

96 Force STIP

90 Cancelled

Not successful

3

(46)

9.1.3 List of acquirer and server response codes for

Bancontact/Mister Cash

Rabo OmniKassa Dashboard

Acquirer

response code

Description

Server

response code

Description

Status

00 Successful

approval/completion

00 Captured

Successful

00 Successful

To be settled

1

02 Refer to card issuer

02 Referral

Not successful

03 Invalid merchant

03

04 Retain the Card

05

05 Do not honour

05

13 Invalid amount

30

14 Invalid card number (no

such number)

14 => 75

15 Card Issuer unknown

05

25 Unable to locate record

in file

25

30 Format error

30

31 Identifier of acquirer

entity unknown

90

33 Expiry date of the card

has passed

05

41 Card lost

05

51 Insuffient funds or credit

limit exceeded

05

1

This status indicates that a refund of a Bancontact/Mister Cash transaction has been initiated succesfully. 2_{After three attempts the first mentioned code changes into the last mentioned code.}

(47)

Bancontact/Mister Cash

Rabo OmniKassa Dashboard

Acquirer

response code

Description

Server

response code

Description

Status

54 Expiry date of the card

has passed

05

57 Transaction not

permitted to

issuer/cardholder

05

58 Transaction not

permitted to

acquirer/terminal

05

61 Exceeds withdrawal

amount limit

05

62 Restricted card

05

77 Re-enter transaction

05

89 Allowable number of PIN

tries exceeded

89 => 75

90 Unexpected responce

code

90

94 Duplicate transmission

detected

90

95 Reconcile error

90

96 System functioning

incorrectly

90

97 Expiry of the global

monitoring delay

90

98 Unreachable server

90

2

(48)

9.1.4 List of acquirer and server response codes for iDEAL

iDEAL

Rabo OmniKassa Dashboard

Acquirer

response code

1

Description

Server

response code

Description

Status

01 Open

60

2

Awaiting status report

Pending

03 Success

00 Captured

Successful

00 Successful

To be settled

3

04 Cancelled

17 Aborted

Not successful

05 Expired

97 Expired

Not successful

06 Failure

05

4

Refused

Not successful

1 _{The acquirer responsecode is not displayed in the Rabo OmniKassa Dashboard (empty field).} 2

Transaction is not yet completed; Rabo OmniKassa is waiting for final status from iDEAL. 3

This status indicates that a refund of an iDEAL transaction has been initiated succesfully. 4

(49)

9.1.5 List of acquirer and server response codes for

MiniTix

Rabo OmniKassa Dashboard

Acquirer

response code

Description

Server

response code

Description

Status

040 Payment cancelled

17 Cancelled

Not successful

080 Transaction outside time

window

97 Expired

Not successful

100 Unauthorised user

05 Refused

Not successful

120 Insufficient balance

05 Refused

Not successful

240 Year limit on wallet is

reached

05 Refused

Not successful

250 Spending limit on wallet

is reached

05 Refused

Not successful

260 ARE limit on account

number is reached

05 Refused

Not successful

NA

Transaction successful

00 Captured

Successful

9.1.6 Response codes for Incasso, Acceptgiro, rembours

Due to the way the Rabo OmniKassa supports the register services Incasso (direct debit), Acceptgiro

(giro collection form) and rembours (cash on delivery), there are no specific response codes for the

register services.

(50)

9.2 Appendix 2: List of currencies

The Rabo OmniKassa supports payment in different currencies.

Note that the payment methods iDEAL and MiniTix only allow payments in euros.

Currency Description € Euro $ American dollar

Sfr

Swiss Franc £ Pound sterling C$ Canadian Dollar ¥ Japanese Yen

AU$ Australian Dollar

Kr Norwegian Crown

SEK Swedish Crown

(51)

9.3 Appendix 3: Complementary code

This field contains a technical code that provides supplemental information about the fraud check on a credit card transaction. If the code is 00 or empty, there were no problems with the

transaction. Any other value indicates that there was a problem with the transaction. The most commonly encountered codes are explained in the table below.

Code Checks Description

Empty _{No check performed}

00 All All configured checks were performed; no problems _found

02 _{Card limit} _{Card limit exceeded}

03 _{Grey list} _{Card appears on the grey list} 04 Grey list postal code Postal code appears on the grey list

05 _{Unknown BIN} _{Non-linked card}

06 _{Foreign BIN} _{Card has nationality different from webshop} 07 Blue e-Card Blue e-Card detected

08 BIN range Invalid BIN range

09 IP address country Unknown country of origin of IP address 10 IP address country Blocked country of origin of IP address 11 Black list Card appears on the black list

12 Prohibited combination of _{country/IP address of card} Prohibited combination of country/IP address of card

13 Country of origin IP address or card

Unknown country of origin of IP address or card

16 Current IP address Invalid current IP address

99 _All _{Problem encountered during a check}

Other codes may also be encountered. For an explanation of any code not listed here, please contact the Support Team Rabo OmniKassa.

How To Use The Rabo Ompo Kassa Dashboard On A Bank Account On A Credit Card Or Debit Card On A Sim Sims.Com (European)

User Guide

Dashboard of the Rabo OmniKassa

Table of Contents

1

The Rabo OmniKassa dashboard ... 4

2

Logging in ... 5

3

Transaction management ... 10

4

Payments ... 25

5

Payment pages ... 33

6

Additions & modifications ... 35

7

Questions, system failures ... 37

8

Footer ... 38

9

Appendices ... 39

1 The Rabo OmniKassa dashboard

2 Logging in

2.1

The login page of the Rabo OmniKassa dashboard

2.1.1 Navigation

2.1.2 Logging in

2.2

The 'Forgot password' page

2.2.1 Navigation

2.2.2 Dialogue window

2.3

The 'Change password' page

2.3.1 Navigation

2.3.2 Dialogue window

2.4

The ‘Change User Account’ page

2.4.1 Dialog window

2.5

Logging out

3 Transaction management

3.1

List view

3.1.1 Navigation

3.1.2 Search for transactions

3.1.2.1 The subwindow for simple searches

3.1.2.2 The subwindow for advanced searches

3.1.3 Search results

3.1.4 Exporting transactions list

3.2

Details view

3.2.1 Navigation

3.2.2 Transaction details subwindows

3.2.2.1 Transaction details & Order subwindows

3.2.2.2 The Payout details subwindow

3.2.2.3 The Transaction history subwindow

3.2.2.4 The Technical details subwindow

3.2.3 Validating a transaction

3.2.4 Cancelling a transaction

3.2.5 Refunding a transaction

3.2.6 Export transaction details

4 Payments

4.1

List view

4.1.1 Navigation

4.1.2 Payment search

4.1.3 Search results

4.1.4 Exporting payment list

4.2

Details view

4.2.1 Navigation

4.2.2 Subwindows

4.2.2.1 The Payment details subwindow

4.2.2.2 Transaction search subwindow

4.2.2.3 The subwindow for simple searches

4.2.2.4 The Advanced search subwindow

4.2.2.5 Transactions list

4.2.3 Exporting payment specifications

5 Payment pages