A hardware wallet, built into Magento checkout.

A hardware-backed, biometric digital wallet brings encrypted, tokenized payment to online checkout. IWD engineered the Magento extension that places its Tap to Pay and 1-click checkout on any store, decrypting the wallet's device token and routing it across multiple payment processors.

The client

A global technology brand

Our client, a global technology company we're keeping confidential, built a hardware-backed, biometric digital wallet that brings encrypted secure storage to online checkout. Putting it in front of shoppers meant building it into Magento, the kind of payment work our Magento extension team is built for.

The solution

A hardware wallet needs to live where people check out.
So we built it into Magento.

Wallet Magento extension

A Marketplace extension placing the wallet button on any Magento 2 checkout, across major operating systems.

Device-token security

The wallet's encrypted EMV device token decrypted and routed to the processor, keeping card data off the store.

Multi-processor support

One wallet button routing through Braintree, Stripe, CyberSource, and Global Payments.

Tap to Pay

A contactless Tap to Pay flow rendered in the cart, with shipping details passed in from checkout.

1-click Quick Pay

Pre-enrolled wallet information, including shipping address, completes a purchase in a single confirmation.

Marketplace distribution

Documented, demo-store-ready, and license-scanned for publication on the Magento Marketplace.

By the numbers

Engineered,
not assembled.

Routing a hardware wallet across multiple processors and checkout experiences, with card data tokenized end to end, is payment engineering. So we built it as a product.

Start a project
4 payment processors
3 checkout experiences
3 operating systems
1 Marketplace extension
The stack

Many processors. One wallet button.

The platform, the marketplace, the processors, and the checkout, wired around one tokenized wallet credential, so the same button works wherever a merchant already takes payment.

  • PlatformMagentoThe Adobe Commerce checkout the button lives in
  • DistributionMagento MarketplaceWhere the extension is published for merchants
  • PaymentsBraintreeProcessor routing for the wallet token
  • PaymentsStripeProcessor routing for the wallet token
  • PaymentsCyberSourceAuthorize, capture, and refunds
  • PaymentsGlobal PaymentsAuthorize and authorize-and-capture
  • SecurityEMV TokenizationDevice tokens decrypted, not card data
  • CheckoutDominateWallet enabled in the Dominate checkout
  • CheckoutTap to PayContactless tap-to-pay flow in the cart
The build

Built in phases.

The wallet wasn't a single drop. It moves from the core extension, to additional payment processors, to Tap to Pay and 1-click in the checkout, to Marketplace distribution, each phase widening where the wallet can be paid with.

  1. Phase 01Build the wallet extension

    Engineering the core Magento 2 extension that places the wallet button on any store checkout, decrypting the wallet's EMV device token and rendering the payment sheet, with the first processor support in place.

  2. Phase 02Add the processors merchants use

    Extending the extension across additional payment processors so the wallet token can authorize, capture, and refund through the gateway a merchant already runs, rather than forcing a switch.

  3. Phase 03Bring it to the checkout page

    Enabling the wallet through the Dominate checkout, with a contactless Tap to Pay flow and a pre-enrolled 1-click Quick Pay that draws shipping and payment details straight from the wallet.

  4. Phase 04Ship it on the Marketplace

    Packaging the extension with documentation and demo stores and passing open-source and static license scanning, so it ships clean on the Magento Marketplace for any merchant to install.

A shopper tapping a phone on a contactless payment terminal at checkout
Payment engineering

One button, many rails.

The hard part isn't any single feature. It is making one hardware-wallet button work across several payment processors and checkout experiences, with the credential tokenized end to end, on any Magento store a merchant happens to run.

4payment processors behind one wallet button
  • Tokenized end to end. The wallet's EMV device token is decrypted and routed, so card data never lands on the store.
  • Processor-agnostic. The same button rides Braintree, Stripe, CyberSource, or Global Payments.
  • Built to distribute. Packaged, documented, and license-scanned for the Magento Marketplace.
The payoff

A wallet that
meets shoppers at checkout.

The build is never the point. This is what the extension changes for how a hardware wallet reaches shoppers and how easily a merchant can offer it.

Get this for your store
Reach

One extension, any Magento store

Published on the Magento Marketplace, the extension lets any merchant on Magento 2 drop the wallet's payment button into checkout, turning a hardware wallet into a button a store can simply install.

The build. Wallet, processors, checkout.

Bringing a hardware wallet to Magento is token-handling, processor integration, checkout UX, and Marketplace packaging, each piece built so the same button works on any store. This is the extension, payment, and distribution work the engagement covers. The product is owned by the client.

Platform

Wallet Magento Extension

What it doesThe core Magento 2 extension that places the wallet payment button on a store's checkout, built to be operating-system agnostic across major desktop platforms and to work on any current Magento 2 storefront.

Why it matteredA hardware wallet only reaches shoppers if it lives where they check out. A native Magento extension is how the wallet becomes a button on real stores.

Security

EMV Device-Token Decryption

What it doesLogic to decrypt the wallet's EMV device token, a tokenized payment credential rather than a raw card number, and pass it to the payment processor for authorization.

Why it matteredTokenization is the whole point of the wallet. Handling the device token, not card data, keeps sensitive details off the merchant and inside the secure path.

Experience

Wallet Payment Sheet

What it doesIntegration of the wallet payment sheet into checkout, including messaging injected back into the sheet on payment failure and account creation for non-guest shoppers.

Why it matteredThe payment sheet is where the shopper actually confirms. Handling its success and failure states cleanly is what makes the experience feel native, not bolted on.

Payments

Braintree & Stripe Support

What it doesExtension of the core Braintree and Stripe Magento payment integrations to accept the wallet's decrypted token, establishing the first processors the button could route through.

Why it matteredMerchants already run these gateways. Extending them, rather than replacing them, lets the wallet ride existing payment relationships.

Payments

CyberSource Integration

What it doesExtension of the official CyberSource Magento integration to process the wallet token, supporting authorize-and-capture along with full and partial refunds.

Why it matteredRefunds and capture are table stakes for a real payment method. Building them in makes the wallet a complete processor option, not a demo.

Payments

Global Payments Integration

What it doesExtension of the Global Payments Magento integration for the wallet token, supporting authorize and authorize-and-capture, with transactions handled in the store's base currency.

Why it matteredEach processor models payments differently. A dedicated integration maps the wallet token onto Global Payments' own authorize and capture flow.

Checkout

Dominate Checkout Integration

What it doesEnablement of the wallet as a payment method through the Dominate checkout application, including button placement and rendering the wallet as the default option when a wallet account is present.

Why it matteredMeeting shoppers in the checkout they already use widens where the wallet can appear, beyond a single store's native checkout.

Checkout

Tap to Pay Experience

What it doesA contactless Tap to Pay flow rendered in an iframe in the cart, guiding the shopper to present a contactless card or mobile wallet and complete the payment, with shipping details passed in from the checkout page.

Why it matteredTap to Pay turns checkout into a physical gesture. Embedding it in the cart keeps that experience inside the normal shopping flow.

Checkout

1-Click Quick Pay

What it doesA quick-checkout button that uses pre-enrolled wallet information, including the shipping address held in the wallet, to complete a purchase without the shopper re-entering details.

Why it matteredEvery field a shopper skips is friction removed. Drawing details from the wallet collapses checkout into a single confirmation.

Distribution

Marketplace Packaging & Compliance

What it doesPackaging the extension for the Magento Marketplace with full documentation and demo stores, and passing open-source and static license scanning so it ships clean for any merchant to install.

Why it matteredMarketplace distribution is what makes the wallet broadly available. Passing the platform's scanning and documentation bar is the gate to getting there.

Let's work together

Got a payment or platform idea to ship?

Build, integrate, and distribute. We engineer Magento and Adobe Commerce extensions and payment integrations, from device tokens to checkout UX to Marketplace publication, and see them through to shipping. Tell us what you're building.