Implementation
Virtual terminal setup checklist
From an approved merchant account to a reconciled first batch, in six practical stages.
1. Get the merchant account approved
A terminal login has nothing to attach to until the merchant account exists. The application normally needs the legal business name, EIN, registered address, ownership details, a business bank account and a description of what is sold, how it is delivered and what a typical order looks like.
Card-not-present volume triggers more questions because the card is not inspected. Expect underwriting to ask about average ticket, monthly volume, refund policy, delivery time and previous processing history. A new business with a large projected ticket may receive a reserve or a lower initial volume cap.
2. Collect the terminal credentials
After approval, the provider issues a merchant ID and creates the terminal user. A welcome email usually contains the login address, a temporary password and instructions for MFA. Save the merchant ID somewhere the finance team can find it; support calls usually start with that number.
- Confirm the legal business on the merchant record.
- Confirm the login email belongs to the business.
- Record the MID and the provider support path.
- Confirm the settlement bank account before the first sale.
3. Configure security and users
Create named users instead of sharing one password. Give payment-entry access only to people who need it and reserve refund or credit permissions for supervisors. Turn on MFA for every administrator. Set a session timeout that fits the office environment.
- Require a unique password and MFA for each user.
- Use least-privilege roles.
- Limit card-on-file access.
- Set the session timeout.
- Review the audit-log location.
For the full access-control model, read merchant portal login security.
4. Set terminal and risk preferences
| Setting | Recommended starting point | Why it matters |
|---|---|---|
| AVS | Require ZIP; review full-address rules | Adds a risk signal to keyed sales |
| CVV | Require where the processor supports it | Reduces simple card-data abuse |
| Billing descriptor | Use the customer-facing business name | Prevents “unknown charge” disputes |
| Batch close | Once daily before the cutoff | Simplifies reconciliation |
| Receipts | Send an email receipt with the reference | Creates a clear customer record |
5. Run a test transaction
- Process a small sale through the live terminal.
- Find the sale in the open batch and confirm the amount, card type and authorization code.
- Void the transaction before closing the batch.
- Confirm the void status and that the batch total returns to zero.
- Check that the customer receipt and billing descriptor look correct.
A test proves the MID, credentials, risk settings and batch flow. For an OmniFlex account, the OmniFlex virtual terminal guide explains the login and verification-code step.
6. Close and reconcile the first live batch
Close the first live batch before the processor cutoff and save the batch report. Compare three records: the terminal batch total, the processor settlement record and the actual bank deposit. Fees and reserve deductions explain the difference between gross sales and the amount received.
Common setup problems
- No merchant record. The login is attached to the wrong MID or provisioning is incomplete.
- Credit missing. The account is not enabled for standalone credits.
- MFA code not received. The mailbox or phone number on the merchant record is wrong.
- Batch not settling. Check cutoff, status, reserve and whether the batch contains captured transactions.
- Unexpected effective rate. Review fixed and per-item fees, not only the percentage.
Frequently asked questions
What do I need before setting up a virtual terminal?
An approved merchant account, a business bank account, a merchant ID, user credentials and a clear description of the card-not-present volume you expect.
How long does virtual terminal setup take?
Terminal configuration can take under an hour after approval. Merchant account underwriting is the long part and can range from one day to several weeks depending on risk and documentation.
Should I run a test transaction?
Yes. Process a small sale, confirm it appears in the open batch, void it and verify the status. This proves the MID, terminal and settlement path work before live volume.
Which security settings should be enabled first?
MFA, named users, role-based permissions, AVS and CVV requirements, a session timeout and a recognizable billing descriptor.
When should the first batch be closed?
Close it at the end of the first business day, before the processor cutoff, and reconcile the batch record to the expected deposit.
What if the terminal shows no merchant record?
The user may be attached to the wrong MID, the account may still be provisioning, or the role may not include payment entry. Confirm the credential and merchant record with the provider.