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.
FAQ
Got Questions About Getting started?
Merchant Onboarding & Applications.
Provide at minimum:
- Legal / trading name
- Country and region
- Contact name, email, and phone
- Acquiring bank / existing merchant number (if any)
- Product interest (Enterprise, Lite, Divert, Batch, device/POS)
New online merchants often need an acquiring merchant account first. Once that exists, iVeri can connect Application IDs, certificates, and product configuration.
Useful public guides:
Each merchant profile typically has:
|
|
Test Application ID |
Live Application ID |
|
Mode |
Mode=Test |
Mode=Live |
|
Purpose |
Integration / UAT |
Production traffic |
|
Settlement |
No real funds |
Real acquiring settlement |
Always complete required testing before asking for Live migration. Profiles still in Created status usually mean testing is incomplete and Live is not ready.
In V_XML / Enterprise API every transaction must include your ApplicationID:
<V_XML Version="2.0" CertificateID="{YOUR-CERT-ID}" ProductType="Enterprise" Direction="Request">
<Transaction ApplicationID="{YOUR-APP-ID}" Command="Debit" Mode="Test">
<!-- ... -->
</Transaction>
</V_XML>
Common causes from resolved tickets:
- Long period of inactivity on Live
- Merchant / usergroup suspended at gateway
- Profile waiting for Acquiring Bank reactivation
Resolution path that works:
- Confirm which Application ID is inactive (Live vs Test).
- Ask support / Acquiring Bank to reactivate.
- Where available, set the profile to seasonal so quiet periods do not auto-inactivate.
Re-test a small transaction and confirm status shows Active .
A seasonal setting is used for merchants who trade intermittently. Support and Acquiring Bank teams commonly request “reactivate and set to seasonal” so the Application ID does not fall into inactive/suspended solely because of low volume.
Ask your Acquiring Bank relationship / iVeri support contact if seasonal status is appropriate for the MID.
Integrator FICA merchant list tickets are typically Acquiring Bank / compliance workflows feeding merchant enablement into iVeri.
When raising or chasing these:
- Keep the original list / reference in the ticket
- Confirm merchant legal name and MID
- Wait for Acquiring Bank confirmation before expecting Live trading
Merchants waiting on FICA should ask their bank / integrator for status rather than expecting gateway-only activation.
After acquiring approval:
- Confirm merchant number (MID) and usergroup / profile ID.
- Confirm Test and Live Application IDs are created and Active.
- Issue or renew the merchant Certificate ID (Administrator).
- Complete Test transactions.
- Enable required products (3-D Secure, Lite, Divert, devices, out-of-band notifications as needed).
- Run a controlled Live smoke test.
If 3DS and non-3DS profiles both exist, confirm both are active on iVeri and acquiring platforms.
Ownership changes usually require Acquiring Bank re-papering plus iVeri profile updates (administrator, contacts, sometimes new Application IDs).
Provide:
- Old and new legal entity details
- MID(s) affected
- New administrator name, email, phone
- Effective date
Do not assume the old Certificate ID / administrator login remains valid after ownership transfer.
Resolved guidance: duplicate, closed, suspended, or mistakenly created merchant profiles cannot be deleted from the system in normal operations. They can be suspended / deactivated only.
Request deactivation of the wrong MID rather than deletion.