1 - Introduction

This document describes how retailers can take advantage of Corporate Payments Web Service at Valitor. If changes occur in the web service, a new version will be issued and merchants will be informed of any changes. The older version will remain active for a certain time, except in the case of an error that requires immediate change.

Before a vendor can use Valitor's Corporate Payments Web Service he/she first needs to get a user name, password, and contract number for the Corporate Payments Web Service along with one or more POS terminal IDs.

1.1 - Recent changes

Recently the following changes have been made in Corporate Payments Web Service

1.1.1 - New service designed to work exclusively with 3DSecure transactions

Information on the new 3DSecure process can be found in this chapter and the service documentation is located here.
Information on changes to virtual card numbers after the update is located here

Short overview:

  • New endpoint to obtain 3DSecure authentication
  • New parameters required when creating a virtual card in 3DSecure service.
    • cvv (card verification code) is required to perform a 0 amount payment for verification of the card and provide the initial transaction where cardholder participation is verified.
    • txid and cavd parameters are also required, those are additional 3DSecure authentication parameters required also for the 0 amount payment for verification of the card and provide the initial transaction where cardholder participation is verified.
  • When updating expiration date in 3DSecure service, additional 3DSecure authentication parameters will be required.
    • cvv or card verification code is required to perform a 0 amount payment for verification of the card and provide the initial transaction where cardholder participation is verified.
    • txid and cavd parameters are also required, those are additional 3DSecure authentication parameters required also for the 0 amount payment for verification of the card and provide the initial transaction where cardholder participation is verified.
  • FaHeimild function in 3DSecure is unchanged
  • FaOgildingu function in 3DSecure now requires amount
  • FaSidustuFjoraIKortnumeriUtFraSyndarkortnumeri function is not present yet in 3DSecure service, but can be added in future versions.
  • FaAdeinsheimild and NotaAdeinsheimild endpoints are removed since the concept of pre-authentication does not match with the new 3DSecure model.
  • FaEndurgreitt is removed because FaOgildingu will now cover both instances. In case cancellation comes late, the system will automatically convert the cancellation into a refund.

1.2 - Web Payments Page URL

1.2.1 - 3DSecure Test environment

https://api.processing.uat.valitor.com/Fyrirtaekjagreidslur/Fyrirtaekjagreidslur3d.asmx

WSDL: https://api.processing.uat.valitor.com/Fyrirtaekjagreidslur/Fyrirtaekjagreidslur3d.asmx?WSDL

1.2.2 - Non-3DSecure Test environment

Warning

Usage of non-3DSecure web services is not in full compliance with the new SCA Regulatory Update.

https://api.processing.uat.valitor.com/Fyrirtaekjagreidslur/Fyrirtaekjagreidslur.asmx

WSDL: https://api.processing.uat.valitor.com/Fyrirtaekjagreidslur/Fyrirtaekjagreidslur.asmx?WSDL

1.2.3 - Production environment

A merchant agreement needs to be completed prior to gaining access to production environment. Contact Valitor for further information.