Credit Card Payments WordPress

Credit Card Payments WordPress Overview & Payment Terminal Architecture

Credit Card Payments WordPress is a self-hosted payment terminal plugin engineered for agencies and developers to accept direct card transactions across ten processing gateways from a single WordPress installation. The plugin removes the bottleneck of writing per-gateway integration code by shipping maintained terminal modules for Stripe, Authorize.net, PayPal Pro, Elavon, InternetSecure, eWay, FirstData (LinkPoint), Moneris Canada and Moneris US, PaymentExpress, and Optimal Payments. In production workflows it functions as a shortcode-driven checkout layer, embedding configurable card capture forms into posts, pages, and client deliverables without requiring theme template modifications.

Technical Specifications & Deployment Matrix

Multi-Gateway Payment Processing & Execution Pipeline

The core mechanism is gateway abstraction: a shared front-end card form dispatches validated payloads to swappable per-gateway processing modules. When a visitor submits the embedded form, the plugin reads the configured amount, normalizes numeric formatting, transmits the card data to the selected processor’s API endpoint, and reports the authorization result back to the page. Because Elavon and InternetSecure were separated into distinct processing code paths, each terminal module owns its own request construction, credential handling, and response interpretation rather than sharing a forked codebase.

Amount handling deserves specific attention from a compliance standpoint. Historical changelog entries record incorrect thousands separators being transmitted for Moneris and Authorize.net, along with wrong amounts appearing in email notifications — issues resolved through dedicated decimal normalization logic. This illustrates the plugin’s validation approach: numeric sanitation occurs before API dispatch so that the processor receives a clean, unambiguous transaction value. For the PayPal Pro terminal, gateway error code 10571 is deliberately treated as a success condition, mapping an otherwise ambiguous processor response to a completed transaction state.

Core Technical Capabilities of Credit Card Payments WordPress

• Multi-terminal gateway registry: Ten processor modules — Stripe, Authorize.net, PayPal Pro, Elavon, InternetSecure, eWay, FirstData, Moneris CA/US, PaymentExpress, Optimal Payments — operate as independent terminals selectable from the admin configuration layer.
• Shortcode service targeting: Each terminal can be embedded individually via shortcode for a particular service, allowing multiple gateways to coexist on different landing pages within one site.
• Front-end card type guesser: JavaScript inspects the entered card number pattern and infers the card brand (Visa, Mastercard, and related schemes) before submission, reducing invalid-gateway mismatches.
• Sandbox credential switching: Documented test credentials for Elavon, Moneris Canada, Moneris US, and Optimal Payments enable staging verification against processor test environments prior to live key deployment.
• Stripe SCA compliance: The November 2019 release added Strong Customer Authentication handling for Stripe transactions, aligning the terminal with European payment regulation requirements.

For fintech-oriented studios exploring separate standalone alternatives outside the WordPress runtime — such as issuing virtual prepaid cards through a Stripe-powered SaaS platform — E-Card represents an independent custom-code path rather than an extension of this plugin’s architecture.

Production Implementation & Operational Resilience

Deployment begins with activating the plugin, selecting a gateway module from the tabbed admin interface, and entering processor credentials — live keys for production or the documented test credentials for staging. The admin panel itself received a layout refresh in version 3.4.1 that resolved cases where configuration tabs rendered empty, and earlier releases fixed colorbox load conflicts caused by other plugins injecting competing modal libraries. When JavaScript library collisions occur in stacked plugin environments, isolating the modal dependency remains a practical diagnostic step.

Because the plugin transmits raw card data through front-end forms, transport security depends on a properly configured TLS certificate on the host, and hardening the surrounding attack surface is a deployment prerequisite. Layering BBQ Firewall at the WordPress perimeter blocks malicious traffic before it reaches payment endpoints, keeping request paths to the terminal modules clean.

Secondary development operates within the terminal-module pattern: extending payment support means writing a new processor module that conforms to the existing request/response contract, following the precedent of the Elavon/InternetSecure separation. Version 3.4.1 also updated Elavon and Moneris processing code, confirming that gateway modules receive independent maintenance as processor APIs evolve. The plugin is not Gutenberg-optimized, so embedding relies on shortcode placement within the classic editor, custom HTML blocks, or template code rather than native block registration.