In some instances a merchant may receive an order from a customer that will not be available for shipment within an authorization hold period of 7 (i.e. final authorization) respectively 30 days (i.e. pre-autghorization).

This is typically the case for:

  • highly configured products that are Build to Order (BTO) such as bicycles, computer servers, furniture or other manufactured items that exceed standard specifications

  • pre-orders of upcoming products such as new phone models

  • out of stock items


Please note that if the authorization is to take place a considerable time after the initial order it is best practise to send a reminder to the cardholder a couple of days before authorization to maximize the likelyhood for funds to be available.


To maintain a potential liability shift of 3DS authentication it is recommended follow a two step process:

  1. Initial Card Add as part of a none payment transaction (NPA)

  2. Subsequent unscheduled COF MIT with authentication data from step 1 (UCOF MIT)

Initial Card Add as part of a none payment transaction (NPA)

To establish the card on file mandate and to authenticate the cardholder please submit an authorization request to VR-ePayment Gateway.


Amount

The specified Amount will be used within the 3DS authentication process and displayed during the cardholder challenge to the customer. It should be the final amount that is to be charged to the customer once the order is fulfilled as it will be also the maximum amount for the liability shift.


COF

The cardholder challenge will be enforced through the credentialOnFile indicator labelling the transaction as a mandate establishment for subsequent MITs.


Account Verification

To surpess an immidiate authorization hold of the full order amount on the cardholder's account and to comply with the card scheme rules for card add transactions it is required to perform an account verification (aka zero-value authorization) transaction by submitteing the key AccVerify with the value ‘Yes’.



The response JSON object threeDSData in combination with the conditional (i.e. challenge flow) JSON object resultsResponse contains the authentication data needed for the subsequent MIT authorization request once the order is ready to be shipped.

UCOF MIT

Once the product or service becomes available and is ready to be shipped or at any other date that permits to put an authorization hold on the cardholder’s account please submit an authorization request flagged as UCOF MIT in combination with the authentication data obtained in initial COF establishment transaction.


COF

The credentialOnFile flagging of MIT prevents the issuer from requesting a cardholder challenge and links the transaction via the schemeReferenceID to the initial COF.


threeDSData

Liability protection can be established by submitting the threeDSData object containing the authentication data of the initial COF CIT transaction.