eCommerce is card-not-present (CNP) processing: the card is never physically presented, so the fraud burden shifts to the merchant. Interchange is higher, chargebacks are easier for cardholders to file, and a fraud spike can get a merchant account terminated. The processor’s job is to give the merchant real controls, not just a checkout button.
How does checkout integration work?
Pick the level of control you want, all vault-backed. Hosted checkout is the fastest path: the customer pays on a page QorCommerce serves, and your PCI scope stays minimal. Secure embedded forms put individual card fields inside your own checkout design: the fields talk directly to the vault, so the card number bypasses your servers entirely. Stores on a major cart install the native plugin. In all cases the card is tokenized at capture, which also makes saved-card repeat purchases straightforward.
Which cart platforms have a native plugin?
Seven, on the QorCommerce Gateway (WooCommerce at v2.3.0, the rest at v2.2.0): WooCommerce, Magento 2, PrestaShop, OpenCart, CS-Cart, Shopware 6, and BigCommerce, with a Shopify payment app in development. Each installs through the cart’s own admin and offers the same configuration shape: sale or authorize-then-capture, redirect or embedded iframe presentation, optional 3-D Secure, and hash-verified responses. The WooCommerce plugin goes deepest: compatible with WooCommerce 7.0+ (tested to 9.4), HPOS stores, and, as of v2.3.0, both the classic and block-based checkout, it adds inline card fields as a third mode, void and full or partial refunds with inventory control, a test mode for staging, and WooCommerce Subscriptions support, with scheduled renewals, suspension, reactivation, and cancellation flowing through the gateway. Cards accepted: Visa, Mastercard, American Express, Discover, Diners, and JCB. Updates are delivered into the WordPress dashboard directly from QorCommerce, and the integrations page has the full compatibility table.
What stands between you and CNP fraud?
Layers, each documented. AVS and CVV verification return specific response codes so your order logic can decline mismatches. 3-D Secure authenticates the cardholder and, when it succeeds, shifts fraud liability to the issuer. Behind those, Circuit Breaker watches transaction flow at the platform level and catches anomalies in-line: a card-testing run at 3 a.m. surfaces as it happens, not in a morning report.
What happens when a chargeback arrives?
A chargeback is a forced reversal initiated by the cardholder’s bank. On QorCommerce, disputes appear in the portal with the reason code, the deadline, and the evidence requirements; the docs walk through responding by case type. QorCommerce reporting keeps the dispute rate visible against your volume, because card networks judge merchants on that ratio, and staying ahead of it is much cheaper than fighting your way back under it.