Let's Get Started

Back Office User Guides to learn the essentials, then explore our Plug-ins for seamless integrations, and finally dive into our Developer Guides for advanced implementation and customisation.

Getting started with Enterprise

Everything you need to log in to BackOffice and set up authentication before your first transaction — whether your integration uses a client certificate or a shared secret.

User Group: Enter your Billing Details ID.
User Name: Type in Administrator.
Password: Copy and paste the Administrator password sent with your Billing Details ID.

During integration, generate credentials for whichever method your integration requires. Toggle below to see the process for each.

Legacy Authentication
Digest Authentication

Client certificate

Identifies your application to the gateway using a managed client certificate, installed in your integration environment.

Open certificate managementIn BackOffice, navigate to the certificate section for your Application ID.
Generate the certificateRequest a client certificate for the environment you're integrating against — Test or Live.
Download & store it securelySave the certificate and install it in your application server or API client.
Confirm it's activeCheck the certificate is correctly associated with the Application ID before sending test transactions.
Repeat per environmentTest and Live each need their own certificate.

Client certificates are sensitive credentials — store them securely and limit access.

Shared secret

Digest Authentication

Uses a shared secret to sign or hash requests exchanged between your integration and the gateway.

Open the digest configurationIn BackOffice, navigate to the shared secret section for your Application ID.
Generate a shared secretCreate a new secret for the environment you're integrating against — Test or Live.
Store it securelyCopy the secret and keep it in a safe location accessible to your integration.
Configure your integrationAdd the shared secret to your code so outgoing requests are correctly signed.
Repeat per environmentTest and Live each need their own shared secret.

If a shared secret is ever compromised, regenerate it immediately from BackOffice.

Method	You generate	Typical use
Legacy Authentication	Client certificate	Integrations authenticating via mutual TLS / client certificate
Digest Authentication	Shared secret	Integrations authenticating via request signing / hashing

Back Next

1. Test

Run test transactions

Confirm authentication works end-to-end using your Test Application ID.

2. Review

Check Application Parameters

Confirm which transaction types are enabled for your Application ID.

3.Go live

Repeat for Live

Once testing passes, set up the same credentials in your Live environment.

Back You're Set Up

FAQ

Common questions

Can't find what you're looking for? Reach out to our support team.

How do I integrate iVeri Lite into my website?

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.

What do I need in place before I can use DiVert?

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. .

How does authentication work with the Enterprise API?

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.

How do I submit a batch of transactions at once?

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.

Who do I contact for help with iVeri?

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