Verifications

The Verify operation lets you post verification payments, which are used to confirm validity of card information without reserving or charging any amount.

Introduction

This option is commonly used when initiating a subsequent One-click card payment or a recurring card payment flow - where you do not want to charge the consumer right away.

Verification through PayEx Payment Pages

  • When properly set up in your merchant/webshop site and the payer initiates a verification operation, you make a POST request towards PayEx with your Verify information. This will generate a payment object with a unique paymentID. You either receive a Redirect URL to a hosted page or a JavaScript source in response.
  • You need to redirect the payer's browser to that specified URL, or embed the script source on your site to create a Hosted View in an iFrame; so that she can enter the credit card details in a secure PayEx hosted environment.
  • PayEx will handle 3D-secure authentication when this is required.
  • PayEx will redirect the payer's browser to - or display directly in the iFrame - one of two specified URLs, depending on whether the payment session is followed through completely or cancelled beforehand. Please note that both a successful and rejected payment reach completion, in contrast to a cancelled payment.
  • When you detect that the payer reach your completeUrl , you need to do a GET request to receive the state of the transaction.
  • Finally you will make a GET request towards PayEx with the paymentID received in the first step, which will return the payment result and a paymentToken that can be used for subsequent One-Click Payments and recurring server-to-server based payments .

Screenshots

You will redirect the consumer/end-user to PayEx hosted pages to collect the credit card information.

1551694389702-244.png

API Requests

The API requests are displayed in the Verification flow. The options you can choose from when creating a payment with key operation set to Value Verify are listed below. The general REST based API model is described in the technical reference.

Options before posting a payment

All valid options when posting in a payment with operation equal to Verify, are described in the technical reference.

General

  • No 3D Secure and card acceptance: There are optional paramers that can be used in relation to 3d-secure and card acceptance. By default, most credit card agreements with an acquirer will require that you use 3D-Secure for card holder authentication. However, if your agreement allows you to make a card payment without this authentication, or that specific cards can be declined, you may adjust these optional parameters when posting in the payment. This is specified in the technical reference section for creating credit card payments  - you will find the link in the sequence diagram below.
  • Defining CallbackURL: When implementing a scenario, it is optional to set a CallbackURL in the POST request. If callbackURL is set PayEx will send a postback request to this URL when the consumer has fulfilled the payment. See the Callback API description here.

Verification flow

The sequence diagram below shows the two requests you have to send to PayEx to make a purchase. The links will take you directly to the API description for the specific request. The diagram also shows in high level, the sequence of the process of a complete purchase.
When dealing with credit card payments, 3D-Secure authentication of the cardholder is an essential topic. There are three alternative outcome of a credit card payment:

  • 3D-Secure enabled - by default, 3D-secure should be enabled, and PayEx will check if the card is enrolled with 3D-secure. This depends on the issuer of the card. If the card is not enrolled with 3D-Secure, no authentication of the cardholder is done.
  • Card supports 3D-Secure - if the card is enrolled with 3D-Secure, PayEx will redirect the cardholder to the autentication mechanism that is decided by the issuing bank. Normally this will be done using BankID or Mobile BankID.
  • No 3D-Secure - if this is specified in the request (see options above), no authentication is requested.

Options after posting a payment

Technical reference

You find the full technical reference here.

Created by Fredrik Köhler on 2018/10/04 14:41