Skip to main content

Online Payments

Rate this article:

Overview

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-authorizations which can be manually captured after. Currently supported service providers are: ABS, EFTPOS NZ, NETS

Requirements

Before you start using the Virtual Terminal you need to create a public key for Secure Card Capture to start accepting eCommerce transactions. You do not need to use this key for the plugin configuration, it simply needs to be created to ensure any card details are encrypted in the browser, so that information can be safely passed from you (merchant) to Verifone. 

To generate a public key from your Verifone Central account follow these steps:

  • Navigate to Administration  Organisations, and select the required organization.
  • Scroll down to the bottom of the page to see the Secure Card Capture area.
  • Click on the Create new public key button. 

Integrate Magento 2 Plugin for Verifone_11

Access

Your level of access determines if you can process payments in 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

In order to initiate the payment, the user must set the following configurations: 

  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.
  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 support 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.

payment settings

 

Payment form

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

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

payment form

Payment completed

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

You can now do the following: 

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

Successful transaction

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

Transactions

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

Virtual terminal failed transaction

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 6 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's 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.  

 

 

Recurring transactions

As part of the Recurring features, the Virtual Terminal supports recurring transactions using ABS WEB provider. There are two types of recurring transactions: SIGN-UP and CHARGE.

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

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

Rate this article:
Logo of Verifone