Elavon Payment

Your checkout page looks native. Card fields are rendered by Elavon directly in your buyer's browser. Card data goes to Elavon. Your server gets a token. PCI scope drops to SAQ-A — the short questionnaire, not the annual project.

Flip one switch and buyers go to Elavon's payment page instead. No embedded card form on your site at all. Same SAQ-A protection, different presentation. Subscription orders switch automatically to on-site mode when they need card saving.

Returning customers pick their saved card and click once. Card lives in Elavon's encrypted vault — never in your database. Add, delete, or set a default card from the Joomla account area. Return-customer friction: gone.

First checkout establishes the card as a recurring credential. Every renewal fires automatically — no customer re-entry, no missed cycles. Free trials save the card at zero charge so the first real payment goes through clean.

Full or partial refund from the J2Commerce order screen. Void an unsettled authorization before it hits the customer's statement. No gateway portal login. If a void lands after settlement, the plugin automatically falls back to a full refund — clean result either way.

Taking a phone order? Pull up the customer's saved card from the order screen and charge it. Merchant-initiated, compliant, logged in order history. No portal. No copy-pasting. Stays inside J2Commerce.

Charge immediately at checkout, or hold the funds and capture when the item ships. For high-value orders, hold and confirm stock before any money moves. Your fulfillment workflow, your call.

Show Elavon only in the regions where it applies. Set a floor or ceiling cart value — Elavon appears when the order qualifies and hides when it doesn't. Right payment option, right customer, every time.

Add a named surcharge as a percentage, a fixed amount, or both — with optional tax-class assignment. It appears as a clear line item when Elavon is selected. Recover processing fees without burying them in your product prices.

Elavon fires async webhooks for transaction updates. The plugin receives the signal and immediately re-fetches the transaction to verify its real status — a crafted webhook cannot confirm a payment that didn't happen. Double-submit idempotency catches the other edge case.

The J2Commerce admin dashboard shows a visible warning when sandbox mode is active or credentials are missing. No silent misconfigurations. No "why aren't real payments going through?" moments three days after launch.

Ships with American English, British English, German, French, Spanish, Italian, Dutch, Portuguese, Polish, Russian, Japanese, Arabic, Danish, Finnish, Norwegian, Swedish, Turkish, and Traditional Chinese. Full Joomla language override support for custom wording in any locale.