Elavon — Merchant Configuration
⚠️ STUB PAGE — Awaiting gateway onboarding information (OI-001: capabilities/elavon.yaml missing; OI-002: schema is SEED only).
This page will be expanded once the following are available: - Confirmed capabilities list from Elavon/ViaConnex - Complete field schema with verified values - Portal navigation screenshots
Overview
Elavon uses the ViaConnex payment gateway for card-present and ecommerce processing. Credential placement follows a similar pattern to MPGS — host URLs sit on the MPG entries, not on a top-level merchant object.
| Configuration Object | Purpose |
|---|---|
| TerminalConfig | Terminal identity — TID issued by acquirer |
| MPG PM4 | Ecommerce processing host URL |
| MPG PM99 | 3DS / MPI host URL |
Collecting Credentials from the Elavon Portal
When your Elavon portal setup is complete, the following credentials will be issued. Use this table to map the portal label to the correct field in the Astral MGMT configuration.
These are secrets. Never store in source control or share in plain text. Supply via the secrets manager.
| Portal Label | Where to find it in the portal | Our Field Key | MGMT Object | MGMT Field |
|---|---|---|---|---|
| Ecom Processing Host URL 🔒 | ViaConnex portal → Merchant settings → Ecom Processing URL ⚠️ confirm exact location | ECOM_HOST_URL |
MPG PM4 (ecom_processing) | extData1 |
| MPI Host URL 🔒 | ViaConnex portal → 3DS / MPI settings → MPI Host URL ⚠️ confirm exact location | MPI_HOST_URL |
MPG PM99 (mpi) | extData1 |
| Terminal ID (TID) 🔒 | Elavon acquiring setup → Terminal provisioning → Terminal ID ⚠️ confirm exact location | ACQUIRER_TID |
TerminalConfig | channelTerminalId |
🔒 = secret field — supply via secrets manager, never hardcode.