Fiserv FirstData Payeezy Payment

 The MageDelight Fiserv FirstData Payeezy Payment extension connects the store's native checkout directly to Fiserv's Payeezy payment platform, letting customers pay by card, save that card securely, and check out in one click on every return visit. Once API credentials are added in the admin, the payment method appears inside checkout automatically, with no separate payment page or custom checkout rebuild required. A subscription retailer, for example, can let a first-time buyer enter card details once and complete every later order without re-entering them, while a wholesale seller taking phone orders can charge a saved card using a re-entered CVV, without asking a customer to read out a card number again.

On the storefront, checkout looks like the existing card payment step, with an added option to save the card and a saved-card selector for returning customers. In My Account, a saved-cards panel lets shoppers add, edit, or delete stored cards. In the admin, a configuration panel controls API credentials, order value limits, eligible countries, and the default payment action, so behavior can be tuned without code, including Authorize Only, Authorize and Capture, or Capture Later, partial refunds, and multi-invoice capture.

Features

• One-click checkout using a securely saved credit card
• Unique customer profile ID stored on Fiserv's servers for each saved card holder
• Authorize Only, Authorize and Capture, and Capture Later payment actions
• Online partial refunds issued directly from a credit memo
• Multiple invoices per order with independent capture
• Admin-side order placement using a saved card, with CVV re-verification
• 3D Secure authentication at checkout
• Self-service saved card management from the My Account section
• Support for 50-plus countries and 140-plus currencies through the Fiserv network
• Native checkout integration with no custom development required

Compatibility spans Open Source, Adobe Commerce, and Commerce Cloud. The integration hooks into the store's native payment method architecture rather than overriding core checkout logic, so it stays stable across routine upgrades.

Security

This extension uses an API-based integration, not a redirect: customers enter card details directly on the store's own checkout page and are never sent to a separate hosted payment page. Those card fields are Fiserv's secure, tokenizing fields embedded in the checkout form, so the data transmits straight from the customer's browser to Fiserv's PCI DSS Level 1 certified infrastructure and is not entered into, processed by, or passed through the store's own server at any point. The store never stores raw card numbers; it retains only the token and profile ID Fiserv issues in return.

The one exception is an admin-initiated order placed on a customer's behalf using a saved card, such as a phone order. There, an admin manually enters the CVV for one-time verification; it transmits immediately to Fiserv over an encrypted API call and is never written to the store's database, logs, or session storage.

Given this architecture, the integration is designed to support SAQ A-EP eligibility; store owners should confirm final scope with their acquirer or QSA. Customer card data is not entered into the store's own server-side processing during checkout and is never stored on the store's server; all card storage lives within Fiserv's PCI-compliant infrastructure, referenced afterward only by a non-sensitive token.

Business-Level Overview

For a founder or eCommerce manager, checkout friction is one of the more fixable causes of lost revenue, and repeat card entry is a common source of it. A saved-card, one-click flow removes a step that otherwise gives shoppers time to reconsider or abandon the order.

The operational impact extends past the storefront. Finance teams handling partial shipments benefit from per-invoice capture and partial refunds instead of a full reversal, and phone order teams can complete a sale without asking a customer to read out card numbers again.

Trust compounds the revenue effect: customers save cards, and return to buy again, more readily when checkout includes 3D secure authentication and the store visibly is not storing raw card data. For compliance stakeholders, keeping cardholder data off the store's server reduces audit burden considerably.

3rd Party Integrations

API Provider: Fiserv (Payeezy)

What it enables: Card tokenization, storage, authorization, capture, and partial refunds, including 3D secure authentication at checkout.

Authentication method: API Key and API Secret combined with a merchant token issued per Fiserv merchant account.

Storefront User Benefits

• One-click checkout using a previously saved credit card
• Self-service card management from the My Account section
• Added fraud protection through 3D secure authentication

Admin Benefits

• Place orders using a customer's saved card, with CVV re-verification
• Choice of Authorize Only, Authorize and Capture, or Capture Later
• Generate multiple invoices for an order and capture each independently
• Issue partial refunds from a credit memo without reversing the full order

Full Feature List

• Save credit cards on Fiserv's servers for future transactions
• Unique customer profile ID per saved card holder
• Online partial refunds via credit memo
• Authorize Only, Authorize and Capture, and Capture Later payment actions
• Tokenized card field security with no self-managed SSL card vault
• One-click native checkout integration, no custom development
• Admin-side order placement using saved cards, with CVV re-verification
• 3D secure checkout authentication
• Multiple invoices per order with independent capture
• Country and order-value eligibility controls for the gateway
• SAQ A-EP eligible tokenized processing architecture

Business Problem vs Solution

Checkout friction from repeat card entry Problem: Returning customers who must re-enter full card details every order are more likely to abandon checkout. Solution: Saved cards on Fiserv's servers let returning customers check out in one click.

Manual work correcting split or partial orders Problem: Partial shipments or backorders often force a full refund and re-charge just to fix one line item. Solution: Partial refunds and multiple invoices per order let staff adjust just the affected portion.

PCI compliance overhead from storing card data Problem: Self-managed card vaults carry significant compliance scope and audit burden for the merchant. Solution: Card data routes through Fiserv's SAQ A-EP eligible infrastructure, not the store's servers.

Fraud risk on phone and admin-placed orders Problem: Orders placed by staff on a customer's behalf are a common target for card-testing fraud. Solution: CVV re-verification and 3D secure add a fraud check on admin-side saved-card orders.

Limited payment flexibility at checkout Problem: A single rigid capture flow forces merchants into one payment timing model regardless of order type. Solution: Authorize Only, Authorize and Capture, and Capture Later match the workflow to the order.

Business Benefits (Measurable Outcomes)

• Reduce checkout abandonment by removing repeat card entry for returning customers
• Cut refund processing time by issuing partial refunds instead of full reversals
• Reduce PCI compliance scope by keeping card data off the store's server
• Increase repeat purchase rate as saved-card checkout lowers buyer friction
• Reduce fraud losses on admin-placed orders with CVV and 3D secure checks
• Expand addressable market across 50-plus countries and 140-plus currencies

Sample Use Case

A multi-store home goods retailer regularly shipped large orders in partial shipments as items came back in stock, so staff were manually reversing and re-charging orders every time a shipment split, prompting repeated complaints about duplicate charges.

After installing the extension, the finance team switched to a separate invoice per shipment, capturing payment independently, with no custom development. Saved cards also meant repeat buyers no longer re-entered card details on follow-up orders.

Within two months, checkout abandonment on the payment step dropped 17 percent, refund-related tickets fell sharply, and the finance team cut time spent reconciling split-order payments by more than half.

FAQs

Q1: Does installation require custom development work? No. Configuration happens inside the admin. Most stores finish setup in under an hour.

Q2: Is this PCI compliant, and does card data touch my server? Yes. Card fields transmit directly to Fiserv's PCI DSS Level 1 infrastructure, keeping raw card data off the store's server and supporting SAQ A-EP eligibility.

Q3: Can customers manage saved cards after checkout? Yes. Customers can add, edit, or delete saved cards from the My Account section at any time.

Q4: Does this support partial refunds and multiple invoices? Yes. Admins can issue partial refunds from a credit memo and create separate invoices per item.

Q5: Does it support 3D secure authentication? Yes. 3D secure checkout adds an extra authentication step to reduce fraudulent transactions.

Q6: What countries and currencies are supported? Payeezy, through Fiserv, supports 50-plus countries and 140-plus currencies.

Q7: Will this keep working after a version upgrade? Yes. It uses the store's native payment method architecture, keeping it stable across upgrades.