Skip to main content

Online payments

Virtual Terminal

Last updated: 07-Sep-2022
Rate this article:

Overview

The Virtual Terminal is a tool that can be used to initiate payments for card-not-present (CNP) transactions. Virtual Terminal allows merchants to accept payments (when the physical store is closed) over the telephone or email. The cardholder shares their card details over the phone or via email. The merchant must comply with PCI DSS obligations. Card details must be secured stored.

Payment actions like capture, refund, cancel/void are actions that can be performed on payments triggered by the Virtual Terminal. These actions cannot be performed through the Virtual Terminal, but only via the transaction details which can be accessed through the transaction reports. 

Virtual Terminal capabilities support pre-authorization which can be manually captured after. Currently, supported service providers are ABS, EFTPOS NZ, and NETS.

Combining 3-D Secure and mail or telephone orders is not possible.

Requirements

   Before you start using the Virtual Terminal and in order to start accepting eCommerce transactions, you will need to generate a Secure Card Capture Key.

Access

Your level of access determines if you can process payments via the Virtual Terminal.

✅ Access:

  • Merchant Cashier — Initiate payment and cancel/void payment
  • Merchant Supervisor — Initiate payment, capture/refund/cancel/void payment

🚫 No access:

  • Merchant Admin
  • Merchant Reviewer
  • Merchant User

How to use Virtual Terminal  

Payment settings

The user must set the following configurations to initiate the payment: 

  1. Select an Organization to which the transaction belongs. If there is only one organization, this field will pre-populate.
  2. Select a Payment Provider Contract (PPC). The payment provider contract is configured to accept a set of payment methods. If there is only one PPC, this field will pre-populate.
   Please note that for Virtual Terminal, the Payment Provider Contract needs to have mail/MOTO selected as sales channel.

 3.  The Merchant Reference is a field that can be used to link the transaction to an order ID generated by your system. The purpose of the merchant reference is for your administration. If no information is entered, the field will remain blank. An example of a Merchant Reference could be an Order ID from the ordering system.

 4.  The Transaction Amount is the value of the payment. The currency code will be determined based on the Payment Provider Contract. If a contract is configured to process multiple currencies, the currency code field will be a select box.

 5.  Use the checkbox Automatically send transaction for capture if you want to immediately capture the transaction, or only authorize the funds.

 6.  For the Israel market, the virtual terminal also supports new transaction types: installments, sale preferred Isracard and Sale Direct Debit. Additional information on instalments can be found here.

 7.  Once the configuration has been completed, click on Continue to Payment to proceed to the next step.

vt1

 

Payment form

On the next page, you will see the Payment form. Here, you input the customer's Card Number, Expiration date, and CVV.

vt2

  1. Make sure you store the Merchant Reference for your records.
  2. Enter the Card Number, Expiration date, and CVV.
  3. Click on Process Transaction to complete the transaction, or only authorize the funds.

Payment completed

Once a transaction is completed, the confirmation screen will appear.

vt3

You can now do the following: 

  • Click on New Transaction to start a new transaction
  • Click on More Details to review transaction details

Once a transaction is successful, it can be viewed in the transaction log by searching for the Merchant Reference in the Transactions report.

transactions details

If you are using Woodforest acquirer, the payment completed page will also include Authorization code

vt4

If the transaction failed, the page would look like this:

virtual terminal transaction failed

Merchant action scenarios

Once all the payment settings are configured, you enter the card number. The card number is the customer's card number. After typing in the first six digits, the form displays which brand the card is.

Here is an overview of the various scenarios:

Card type Card validated Portal display Merchant actions Additional actions
Single brand Y Card brand provided Fill in the expiration date of the customer's card If the transaction is authorized, a confirmation screen is shown
Single brand N

An error message is displayed. 

If the expiration date is in the past, an error message explains what is wrong with the input.

Choose to ask for the CVV or not.

  • Store how the card details were received (Telephone/Mail)
  • Initiate the payment

If the CVV check is negative, highlight the result.

Example: The CVV does not match the required length.

Ask the user which payment action should be taken -cancel or refund.

Dual-branded Y
  • If the PPC is configured for one of the brands and the brand that is not configured cannot be selected.
  • If the PPC is configured for both brands, the cashier can ask the cardholder which scheme to process the transaction.

Choose to ask for the CVV or not.

  • Store how the card details were received (Telephone/Mail)
  • Initiate the payment
If the transaction is authorized, a confirmation screen is shown
Dual-branded N If the bin lookup fails, an error message is shown to the user Choose to ask for the CVV or not

The user initiates the payment.

If the CVV check is negative, highlight the result.

Ask the user which payment action should be taken - cancel or refund.

Transactions with Stored Credentials

Stored Credential Payments through the Virtual Terminal follow the same flow as any other Payments through the Virtual Terminal.

There are two types of recurring transactions: SIGN-UP and CHARGE.

The Sign-up transaction is the initial transaction used to actually enroll the shopper for a recurring sequence.

The Charge transaction is (one of) the transactions done with a re-use token, which was created with the Sign-up transaction.

Verifone's Virtual Terminal allows Merchants in Israel to do Stored Credential Transactions via UI. The Virtual Terminal UI enables filling out Stored Credential Framework-specific fields as part of MOTO Transactions.

ABS transactions - functional aspects

Virtual Terminal supports recurring transactions using ABS WEB provider. 

The following Stored Credentials Framework-specific functionality is present on the Payment settings page. The user needs to perform the following steps:

  1. Select Transaction Type 'Recurring'.
  2. Use the checkbox to indicate if the Transaction intended to be done is a Sign-up Transaction. If it is ticked, the following Stored Credential-specific fields are shown:
  • Token scope: As a drop-down menu, the possibility to select the Token Scope to be used for this Transaction
  • Total number of payments: An optional field asking for the count of total number of payments, where the field accepts any number value without validation
  • Total value: An optional field asking for the total value of all the Transactions following this Sign-up Transaction. The amount field accepts any number value without validation.
  • Processing model: A radio button offering a selection between the available Stored Credential processing models, which can be:
    • a. Recurring
      • If the Recurring processing model is selected, then the following additional field is shown:
        • Frequency: A field asking for the frequency of the following Charge Transactions. The amount field accepts any number value without validation up to a maximum of 52.
    • b. None
      • If the None processing model is selected, then the following additional field is shown:
        • Merchant sign-up code: An optional field asking for the Merchant sign-up code.
  • Amount: A field asking for the Transaction amount. If it is a Sign-up Transaction for ABS, the Transaction amount is fixed 0.01.
   For ABS, a Sign-up Transaction is a Pre-Authorization Transaction that should not be Captured.

3.  Leave the box unchecked if the Transaction intended is a Charge Transaction. If it is unticked, the following Stored Credential-specific fields are shown:

  • Sign-up reference: A field asking for the reference received for a Sign-up Transaction, which can be:
    • ABS UID
    • Verifone Stored Credential Reference
  • Standing order number: An optional field asking for the sequence number of this Charge Transaction. The field accepts any number value without validation.
  • Processing model: A radio button offering a selection between the available Stored Credential processing models, which can be:
    • Recurring
    • Unscheduled Credential on File

Woodforest transactions - functional aspects

Virtual Terminal supports recurring transactions using Woodforest provider. The sign up transaction must be created using ecom API

The following Stored Credentials Framework-specific functionality is present on the Payment settings page. The user needs to perform the following steps:

  • Select Transaction Type 'Recurring'.
  • Sign-up reference: A field asking for the reference received for a Sign-up Transaction, which can be:
    • Verifone Stored Credential Reference
  • Processing model: A radio button offering a selection between the available Stored Credential processing models, which can be:
    • Credential on File
    • Recurring
    • Unscheduled Credential on File

Details on use cases for stored credentials can be found in the article located here

  • Amount: A field asking for the Transaction amount.
  • Merchant Reference: Optional field that can be used to pass an internal reference ID
  • Transaction Description: Optional field that can be used to pass information directly on the customer's bank statement

woodforest

 

Rate this article:

Need help?

Do you have a question? On our Support page you will find a list with answers to frequently asked questions.
Did not find the answer you are looking for? Please contact us. We are happy to help.

Logo of Verifone