HeartChain Labs Is Now the Merchant of Record for HeartBadge

As of today, HeartChain Labs LLC is the direct merchant of record for HeartBadge memberships purchased through our platform. Card and digital-wallet payments are now processed through our own payment processor account, settling into HeartChain Labs's primary banking infrastructure. The transition completes a planned move out of the interim authorized-reseller arrangements that supported the soft launch period.

This post explains what changed, why we sequenced it this way, and what it means in practice — both for our members and for the operational record we're committed to maintaining as HeartBadge scales.

What Changed

Three things happened together as part of today's transition:

HeartChain Labs is now the named merchant on member statements. When a member purchases a HeartBadge membership using a card or digital wallet, the descriptor on their card statement reads HeartChain Labs (or a HeartBadge-prefixed variant of it, depending on the card network). Members are now buying directly from the company that operates HeartBadge, with no intermediary in the chain of custody.

Funds settle directly to HeartChain Labs. Card processing routes through our payment processor — our own account, opened under HeartChain Labs LLC, with our own regulatory profile and our own dispute and refund authority. Net proceeds settle to our operating account on the standard daily payout schedule.

The interim reseller arrangements are being phased out. During the soft launch, HeartBadge memberships were purchasable through several authorized resellers who fronted the merchant relationship while HeartChain Labs LLC completed entity formation, banking, and processor underwriting setup. Those arrangements served their purpose. They are now being wound down on a planned timeline that respects existing in-flight transactions.

Why This Matters

For members, the change should be invisible at checkout — the purchase flow looks the same, the badge mints the same way, the rewards work the same way. What's different is what happens behind the scenes. Every dollar paid for a HeartBadge membership now flows through a single, clean chain of custody: member → payment processor → HeartChain Labs. No margin shared with intermediaries. No reseller in the middle. No question about who fulfilled the membership and who is responsible for it.

For the project itself, the change matters more. Direct merchant-of-record status is a precondition for several things we've been working toward:

• Single, audit-clean accounting for membership revenue, with one source of truth and one set of books
• Direct relationships with payment networks for chargeback handling, refund authority, and dispute resolution
• Proper separation between operational revenue (memberships) and the member-rewards endowment, with no third-party in the path between them
• A defensible posture for the regulatory and tax conversations that come with operating at scale — a story we can tell honestly because it's structurally simple

Why We Used Resellers in the Interim

Forming a U.S. operating entity, securing business banking, completing payment-processor underwriting, and integrating it all into a working checkout flow is the kind of work that takes weeks under good conditions and longer when any single piece slips. We didn't want HeartBadge to wait. The interim reseller arrangements let us launch with real members, real badges, and a real product — while the entity-and-banking layer was being built underneath.

Resellers were a bridge. The bridge served its purpose. Today the bridge comes down because the structure underneath it is ready.

We're grateful to the partners who supported the bridge. Each of them did exactly what they agreed to do, on the timeline we asked for, with the operational care this kind of work deserves. The transition out is not a comment on their service. It's a comment on HeartBadge growing into the operational shape it should always have been in for the long term.

What's Operationally Different Today

Concretely, here's the new state:

• Card and digital wallet (Visa, Mastercard, Amex, Apple Pay, Google Pay): processed by payment processor, merchant of record HeartChain Labs LLC, settling to our operating account
• Bank transfer (ACH): processed via direct invoice, direct to HeartChain Labs
• Wire (large purchases and partner agreements): direct to HeartChain Labs at our operating account
• Protocol-native rails (Bitcoin, USDC, on-chain): unchanged — these continue to serve members who prefer them, with no intermediary

The badge minting flow, the rewards distribution pipeline, and every protocol attestation surface are unchanged. The change is upstream of all of those — at the moment money moves into the company. Everything downstream of that moment continues to work the way it did yesterday.

For the Audit Record

Part of why we're publishing this post on the engineering site, with a date and time and signature on it, is that we believe operational milestones for an infrastructure project should be visible and time-stamped. Future operational changes of comparable significance — payment processor changes, banking changes, custody-model changes, treasury allocation changes — will be logged the same way, here on this site, in this format.

We think the right way to operate a membership protocol that asks members to trust it is to make the operational decisions visible, in writing, in their own voice, on the day they happen.

For Members, Plainly

If you're a HeartBadge member or a member-to-be, here's what you actually need to know:

• Your existing badge is unchanged. Your existing rewards are unchanged. Your existing wallet is unchanged.
• Future purchases will show HeartChain Labs on your card statement instead of a reseller name.
• If you have an in-flight purchase that started through a reseller, it will complete through the original path. Nothing breaks.
• If you ever need a refund or have a dispute, you now reach HeartChain Labs directly. Faster, cleaner, more accountable.

This is a quiet change. It's also a foundational one. We wanted to mark it.

As HeartBadge scales, we expect more of these moments — operational decisions that are invisible at the surface but matter for the integrity of the whole system. We'll keep logging them here.