Lite works by submitting a form post from your checkout to the iVeri Gateway endpoint, including the required parameters listed in the Lite Developer Guide. If you're on a shopping cart platform, you can skip custom integration entirely and use the ready-made WooCommerce, OpenCart or VirtueMart plugin instead. 

You'll need a merchant agreement with an acquirer that specifies DiVert as your solution — this is what creates your merchant profile on the Gateway. From there, payment requests are generated using the DebitRequest command, and you can choose whether the Gateway auto-creates a transaction URL for each request. .

Every Enterprise call needs a certificate ID in the body of the request. Authentication tokens and keys in the headers are optional on top of that. The secret key itself is generated in BackOffice and is only shown in plain text for a couple of minutes before it's hashed, so copy it down straight away — if it's lost, you'll need to generate a new one.

Batch transactions are submitted as an XML file with a defined set of tags, uploaded either through iVeriClient FileTransfer using the "Batch" command or directly from BackOffice. This lets you push a whole set of transactions through in one file instead of submitting them individually. 

For technical issues — integration problems, API errors and the like — reach out to assist@iveri.com.