Field Notes

Wallets passed cards online.

Your merchants' buyers already made the change. Most checkouts haven't caught up.

Two numbers worth knowing if your software takes payments on behalf of the businesses that use it, and what it takes to act on them.

01The shift

Four in ten online checkouts start with a wallet.

Share of US ecommerce transactions. Worldpay Global Payments Report, 2026. Wallets are projected to reach 44% by 2030.

Card acceptance is now the minority of how people pay online. Apple Pay, Google Pay, PayPal, Venmo and buy now pay later are where buyers go first, and they expect to see them at checkout.

For a software platform, that changes what a good checkout is. Your merchants feel it as abandoned carts and buyers asking for options they don't have. You feel it in payments volume that never shows up on your platform.

The buyers moved. The question is whether the checkout inside your product moved with them.

02The proof

Modern acceptance shows up in the numbers.

A student travel platform with more than $20M in annual payment volume. We put a modern checkout in front of their buyers, and authorization moved more than five points, from the high 80s into the low 90s.

High ticket, travel months away, usually a parent's card hitting a descriptor they don't recognize. That's close to the hardest case card not present has, which is exactly why there were five points sitting there to take.

What five points is worth

Five points of authorization on $1 million of attempted volume is $50,000 more settled volume.

That's on merchants already on the platform, from buyers who were already trying to pay. No new customers signed.

A Lattice checkout showing wallet and alternative payment options above the card form
This is what the 40% looks like. Every one of those buttons is a buyer who never has to go find their card.

It also saves payments that would have been lost. In the first days of live volume, their team flagged this one to us. A customer's card was declined twice. On the third try they paid with Apple Pay, and the payment went through.

From live volume: attempt 1 card declined, attempt 2 card declined, attempt 3 Apple Pay captured

That's the point in a single example: more ways to pay means fewer lost payments.

And the number almost nobody can see: cost per transaction. Lattice reads what each transaction actually cost against what was charged for it, by method, by card type, line by line. Most platforms have never had that view.

03The lift

Live the week you sign.

Adding payments usually loses to doing nothing because it sounds like a project. With Lattice, it isn't one.

Day 0Agreement signed
Day 1Integration built
Same weekMerchants taking payments
  • Lattice isn't a processor. Whatever your platform runs today keeps running exactly as it does. We sit a layer above it and add what's missing.
  • One integration covers cards, wallets, buy now pay later and pay by bank. Average integration time is under two hours.
  • Our team manages the integrations behind it, so your engineers aren't maintaining a list of providers.
  • Payments becomes a growth lever. More of your merchants' volume runs through your platform, more merchants say yes to payments, and the ones you have stay.