Bank declines
Traditional fiat processors often refuse adult platforms or impose conditions that are incompatible with the business model.
EclipseX Wallet
Top up your wallet once, convert your balance into internal credits and use them for Meet, Creators, Event, Store, Experiences, boosts and private access.
The EclipseX Wallet is used for internal payments. It is not an investment product, not a token and not a promise of return.
Deposit methods
Recent activity
EclipseX Wallet centralizes credits, top-ups, subscriptions, tickets, private content and purchases without exposing users more than necessary.
Card payment refused, hostile processors, lack of discretion, high fees and unstable user experience.
Traditional fiat processors often refuse adult platforms or impose conditions that are incompatible with the business model.
Users want to avoid overly explicit bank labels, visible receipts, or a discomforting experience.
Without a central wallet, each module has to handle its own payments, refunds, subscriptions and histories.
Direct crypto payment per use creates friction, confusion and weak accounting traceability.
EclipseX Wallet solves this with a simple model: one top-up, internal credits, shared balance, private history and controlled payments.
Wallet is not a decorative crypto app. It is the infrastructure that allows EclipseX to monetize Meet, Creators, Event, Store and Experiences.
The user tops up once and uses credits across compatible EclipseX platforms.
Wallet displays a clear credit balance. Core rule: 1 credit = 1 €.
Payments are structured in a private ledger with clean receipts and readable history.
Meet, Creator PPV, Event tickets, Store bundles, boosts and founder access can all use the same layer.
EclipseX credits are used for internal platform transactions. They are not a financial product, yield, staking, stock, token or promised $EXP allocation.
Wallet should stay simple. Users must not have to think in blockchain, gas, token or confusing conversion.
1 EclipseX credit equals 1 €. The balance is readable, understandable and usable across the ecosystem.
Credits are used only inside EclipseX to access services, content, tickets, purchases or compatible options.
Each movement is visible in wallet history: top-up, purchase, subscription, ticket, refund or adjustment.
Credits must not enable member-to-member payments, sexual escrow, or any model bypassing EclipseX rules.
Credit balance
Available for
Credits simplify the experience. Crypto remains a top-up method, not the main user-facing interface.
EclipseX Wallet is designed to work without relying on a classic bank card at launch.
Direct crypto top-up through a single deposit address. Deposit is detected on-chain and then credited into the internal wallet after confirmation.
Top-up via compatible crypto with a simpler flow for users who do not want to manage USDC Base directly.
Top-up by SEPA transfer with a unique reference. At launch, confirmation can be manual on the admin side.
Classic bank card payments are not prioritized at launch. The wallet must first stabilize USDC Base, NOWPayments crypto and SEPA flows.
The wallet gains value because it connects platforms together.
Use credits for Premium, Elite, Couple, Club, boosts and Founder Pass.
Subscribe to verified creators with clear consumption from the wallet.
Unlock private content or a collection with a fixed amount of credits.
Buy a ticket for a private event with verified access and discreet receipt.
Buy a product or Store bundle with the same EclipseX balance.
Pay for a validated and supervised booking without direct user-to-user payment.
Buy temporary boosts for a profile, creator, event or partner.
Pay for founder access or product pass without token promise or yield.
The user tops up their wallet. EclipseX debits credits at each renewal. If the balance is insufficient, access degrades cleanly.
The user chooses Premium, Elite, Couple, Club or Creator subscription.
At renewal, the system verifies whether the wallet has enough credits.
If the balance is sufficient, credits are debited and access is extended.
If credits are insufficient, the status moves to grace period before past due.
If balance is insufficient, status moves to past_due with a grace period.
If the wallet is not topped up, access is automatically downgraded.
Subscription status
Status chips
No complex crypto deductions at MVP. The correct model is: wallet top-up → internal credits → subscription debit.
The wallet must show what matters: amount, type, status, date, reference and related module.
| Date | Type | Module | Amount | Status | Reference |
|---|---|---|---|---|---|
| May 22, 2026 | Deposit | USDC Base | +100 credits | Confirmed | 0x8f...42a9 |
| May 22, 2026 | Subscription | Meet Premium | -14.90 credits | Paid | SUB-1028 |
| May 21, 2026 | Ticket | Event | -35 credits | Paid | TCK-4812 |
| May 20, 2026 | PPV Unlock | Creators | -12 credits | Paid | PPV-2091 |
| May 19, 2026 | SEPA Deposit | Wallet | +150 credits | Pending | ECX-8F42KQ |
USDC Base
Meet Premium
Event
Creators
Wallet
See USDC Base deposits, NOWPayments crypto or SEPA top-ups with status.
See subscriptions, tickets, PPV, Store purchases, boosts and access.
See credits returned after cancellation, dispute or admin adjustment.
Every sensitive operation must have a reference: txHash, ECX reference, invoice, ticket or order ID.
The history should stay clear for users and usable for support, disputes and admin review.
Payment flows should be designed to avoid double credits, fake webhooks, balance errors and untraceable operations.
Each Alchemy webhook must be verified before crediting a wallet.
Balance credit and transaction creation should be done in a single atomic transaction.
Each crypto top-up must have a unique txHash to avoid duplicate credits.
SEPA top-ups can be confirmed or rejected manually at launch.
Sensitive actions must be traceable: confirmation, rejection, refund, adjustment, dispute.
No key, mnemonic, or webhook secret should appear client-side or in logs.
Users do not need to see technical complexity. They must see a clear status: pending, confirmed, rejected, failed or refunded.
This section should be visible to prevent misunderstandings.
EclipseX credits are not a financial product, a share, a return or speculative asset.
Credits are not $EXP and guarantee no future allocation.
Crypto is traceable. EclipseX emphasizes discretion and privacy-first, not invisibility.
Wallet must not allow direct payments between users at launch.
No payments for sexual acts, sexual encounters or prohibited services.
Wallet reduces card dependency but remains subject to compliance, security and moderation rules.
EclipseX Wallet is used for authorized internal transactions in the ecosystem. It must never be used to bypass rules, buy prohibited services or promise returns.
Without a common wallet, EclipseX would be a set of separate sites. With a shared wallet, the ecosystem stays consistent.
Premium, Elite, Couple, Club, boosts and Founder Pass use EclipseX balance.
Creator subscriptions, PPV, private collections and premium messages pass through credits.
Tickets, private access and future event options are paid with discreet wallet payments.
Premium products, bundles, gift cards and event kits can use the same balance.
Verified, structured bookings use credits without direct user-provider payments.
$EXP may eventually become a utility layer later, but it does not replace credits at launch.
The wallet must be built in phases. The MVP should be stable before adding advanced features.
Phase 1
Credit balance, USDC Base top-ups, SEPA top-ups, NOWPayments crypto, history and statuses.
Phase 2
Meet renewals, Creators renewals, past_due, grace period, downgrade and notifications.
Phase 3
Event tickets, Creators PPV, Store bundles, boosts, structured bookings and refunds.
Phase 4
Withdrawal requests from providers, creators, organizers and partners, with admin review.
Phase 5
Automated SEPA confirmation, more advanced webhooks, fraud alerts, exports and reporting.
Phase 6
Internal XP, perks, possible $EXP after traction, audit, legal review and real usage.
Do not add $EXP, staking, yield, APR or token promises to the wallet Core. Wallet Core must first handle credits and internal payments.
EclipseX Wallet
Join EclipseX private access and build an ecosystem where adult payments become clearer, more discreet and better structured.