Clear answers before you use, integrate, or recommend MyHedge.

MyHedge is a digital financial ecosystem designed to connect individuals, businesses, rewards, and digital value through separate customer and business accounts.

No. MyHedge and AIFI operate independently. AIFI is an ecosystem participant and systems-integration provider. AIFI does not own or control MyHedge.

The public education model is organized around Protect, Use, Grow, and Learn. Protect covers digital value, Use covers practical ecosystem utility, Grow focuses on business outcomes, and Learn focuses on education.

No. MyHedge is not presented as a replacement for banks, POS platforms, ERP systems, CRM systems, websites, or merchant applications. It is designed to connect with existing systems where appropriate.

Yes. Every participating business should maintain its own MyHedge business account for funding and releasing DU30 rewards.

The merchant controls its own reward budget, campaign rules, eligible products, reward amounts, and release decisions.

The participating merchant releases DU30 from the merchant’s own MyHedge business account to the customer’s separate MyHedge account.

Yes. The coffee shop app or POS may calculate and display the reward. The actual DU30 transfer should move from the coffee shop’s MyHedge account to the customer’s MyHedge account.

No. The merchant retains ownership of its brand, customer experience, campaigns, business systems, and commercial relationship.

Yes. A merchant may define fixed rewards, percentage-based rewards, product-specific campaigns, seasonal campaigns, branch campaigns, and other business rules, subject to MyHedge platform capabilities and policies.

DU30 is MyHedge’s internal, non-tradable reward and utility token. It is used for customer rewards and supported ecosystem activity.

No. DU30 is described as a non-tradable internal token and is not intended for public market speculation.

No. DU30 and USDT are different assets. DU30 is an internal reward and utility token. USDT is an external digital-dollar token.

The current MyHedge model values 1 DU30 at 1 USDT inside the platform. This is an internal platform valuation, not a statement that the two assets are identical.

No. Merchants distribute DU30 from their available MyHedge account balances and must maintain sufficient funding for their reward programs.

When DU30 is redeemed to USDT inside MyHedge, the redeemed DU30 is burned and removed from circulation.

USDT is a blockchain-based token designed to track the value of the United States dollar. It is separate from DU30.

No. USDT is issued by a private company. It is not physical United States currency, a government-issued central-bank digital currency, or a guaranteed bank deposit.

No. Users should consider issuer risk, reserve risk, wallet risk, platform risk, blockchain risk, regulatory risk, network fees, and possible price deviations.

USDT may generally be transferred to compatible external wallets and services, subject to the correct blockchain network, wallet compatibility, provider rules, fees, limits, and account restrictions.

The intended resilience model is that external value should ultimately exist as USDT rather than depend permanently on DU30. Actual access still depends on wallet control, network availability, transaction completion, and platform operating conditions.

No. The preferred approach is integration before replacement. Existing merchant systems should remain in place where they already work.

AIFI assesses existing business systems and builds integrations between merchant software and MyHedge. This may include POS, website, mobile-app, ERP, CRM, middleware, API, and automation work.

No. AIFI uses standard platform relationships and maintains its own MyHedge account like other participating businesses.

Yes, subject to the merchant’s software architecture and MyHedge’s available integration interfaces. AIFI can assess the application and design an appropriate connector.

Potential systems include POS platforms, mobile applications, websites, online stores, ERP systems, CRM platforms, booking systems, subscriber systems, loyalty applications, and custom software.

No. Integration capability depends on the actual production APIs, authentication methods, webhooks, platform permissions, and documentation made available by MyHedge.

MyHedge is responsible for platform security controls, while customers remain responsible for passwords, credentials, devices, recovery information, wallet addresses, and avoiding scams or phishing.

No. Many blockchain transfers are irreversible. Users must confirm the wallet address, network, amount, and recipient before sending.

The merchant should verify the transaction, customer identity or account mapping, campaign eligibility, reward amount, sufficient balance, duplicate-request protection, and final transfer status.

No. Production systems should wait for confirmed transaction or settlement status. Requests may fail, remain pending, duplicate, expire, or be reversed depending on the platform flow.

Production integrations should use authenticated APIs, signed webhooks, idempotency keys, immutable transaction references, audit logs, retry controls, reconciliation, access restrictions, and monitoring.