Divert Batch Result File Data Elements

Tag Name

Length

Data Type

Format

Description

Amount

<=12

Numeric

The sum of the Amount sub-element values of all the <DivertItem> sub-elements

Count

<=6

Number

The number of <DivertItem> sub-elements

Tag Name

Length

Data Type

Format

Description

Date

8

Numeric

The date when the batch was created (in which case the batch will be processed on the upload date) or a future date on which the batch should be processed (a past or future date cannot be more than 1 calendar month from the upload date)

File Name

<=64

Text

The Filename by which the Divert batch can be identified (must be unique for all Divert batches uploaded for an ApplicationID)

CreateTransactionUrl

Boolean

True|False

Generated URL to which a payment can be made by the cardholder.

DivertItem

XML element

An element for each transaction in the Divert Batch, this can occur multiple times within a <Divert> 

Tag Name

Length

Data Type

Format

Description

Application ID

38

GUID

{00000000-0000-0000-0000-  000000000000}

The ApplicationID allocated generated by the gateway during merchant capture (the same ApplicationID must be used for all DivertItem elements under a Divert element)

Mode

4

Text

Test|Live

The mode of an ApplicationID

Command

<=64

Text

Debit|Authorisation|Credit| etc.

The Transaction type used

RequestID

38

GUID

{00000000-0000-0000-0000-  000000000000}

A unique identifier for the transaction allocated by iVeri

Tag Name

Length

Data Type

Format

Description

TransactionURL

<=255

Text

This will be returned to the merchant in the result file if the ‘CreateTransactionUrl’ parameter set to ‘True’

MerchantReference

<=64

Text

Unique merchant reference for this transaction. Must be unique for each DivertItem with Divert uploaded for an Application ID(normally  this an Invoice Number)