Marketing

Info

DARCA’s marketing strategy in the EU is built around quickly guiding the user to their first result in the Core and scaling without reliance on large budgets.

---

The role of marketing in the DARCA model

DARCA marketing is about moving everyday financial actions into a single framework and reinforcing habit, not reach for the sake of reach.

Note

The main goal is not to “collect installs”, but to drive the user to the first result and repeatability: transfers, exchange, payments, documents.

• Regional priority: EU, then the UAE and the US.
• Marketing is grounded in scenarios (what the user does) and in a measurable outcome (what they receive).
• The Core is the main engine for acquiring a mass audience. Modules and the Academy are conversion and retention amplifiers, as well as separate entry points for specific segments.
• The core growth logic: transparency (the outcome before confirmation), error reduction (contact-based transfers), trust (documents, security, support).

Tip

The conceptual foundation of this approach is Product-led growth: growth is achieved through product scenarios and UX, not only through advertising budgets.

Goals and success criteria

The goal is growth of the active audience and turnover, and the success metric is activation and retention, not registration.

Warning

If marketing is managed only through installs and clicks, “empty traffic” grows and the share of users who actually move into daily usage declines.

• The main objective: growth of the active audience that uses DARCA as an “everyday bank” (fiat and crypto together).
• The key quality criterion: the first useful action within the first 24-72 hours and repeatability over the course of weeks.
• Steering metrics:
  • Activation - the share of users who reach their first result.
  • Retention - repeat usage and retention.
  • time to first result (time-to-first-value).
• For the business audience, the “lead - meeting - pilot - first operation” cycle is added, because value is built around the process and documents, not around an impulsive action.

Example

The goal is not “downloaded the app”, but “made a contact-based transfer and understood how much the recipient will receive before confirmation”, and then repeated the scenario.

A strategy to reach maximum audience without large budgets

Growth is built on durable sources: demand capture, education, referral loops, content, and partnerships.

Info

With limited budgets, the winning model is one where growth is driven by product mechanics, and advertising is used as an accelerator, not as the only source.

• Three core mechanisms that enable scale without large budgets:
  • demand capture (people already want to complete the action)
  • education (reducing fear of mistakes through the Academy)
  • network effect (shared usage, invitations)
• The source of sustainability: repeatable Core scenarios and minimizing errors and uncertainty.
• Accelerators: partnerships and targeted segment campaigns, but always centered around one scenario, not around “the entire product”.

Note

The foundation of organic scaling is the Network effect, which becomes stronger when it is more convenient for people to use DARCA together (contact-based transfers, payment requests, shared scenarios).

Priority acquisition methods and launch sequence

Channels with high intent and low cost are launched first, followed by accelerators and scaling.

Tip

Launch order matters: first what drives activation, then what enables scale.

• 1. Academy as an acquisition channel (and as an error-reduction tool)
  • the external Academy guides the user to one action in the app
  • the internal Academy reinforces the scenario and leads to the next steps
• 2. ASO and organic store traffic
  • positioning through 3-4 Core scenarios, localized for the EU
  • reviews are requested after a successful result, not “blindly”
• 3. Search as the paid minimum
  • focus on high-intent Core scenarios, with a separate stream for business
  • ads drive to a scenario, not to a “universal landing page”
• 4. Referral program to strengthen shared usage
  • rewards for activation, not for registration
  • rewards “in utility” (limits, reduced overage, access to features)
• 5. Content and community
  • checklists, guides, error breakdowns, short scenario demos
  • social media is used to “show the action” and bring users into the Academy
• 6. Partnerships as low-cost scale
  • expat/relocation, accountants/ERP integrators, merchants/PSPs (as Payments readiness increases)

Example

The default funnel: the Academy or Search brings the user to one scenario - the user completes the first action - the internal Academy and messaging gradually reveal the Core and modules in sequence.

Modularity and targeted entry points

Modules can serve as standalone entry points for specific segments, as long as each entry addresses one clear pain point and delivers a fast result.

Question

Each module entry must answer the question: what pain does it solve, and what next step moves the user into the Core?

• Rule: one module - one pain - one outcome. This prevents marketing fragmentation.
• Modules that work well as entry points:
  • Enhanced security - an entry for risk-sensitive audiences, users concerned about mistakes, and users with higher balances.
  • Documents and the Business perimeter - an entry for companies and professional users, where value is measured through documentation, exports and control.
  • Payments - an entry through merchants and the payment scenario, if the merchant flow is ready.
  • P2P - an entry is possible with strict communication around the process, statuses, and risk control.
• Moving from a module into the Core: immediately after the first result, the user completes the next logical Core action (contact-based transfer, exchange with transparent outcome, document creation).

Warning

If too many modules are advertised at once, cognitive load increases and conversion drops. At the start, 2-3 module entry points are enough.

Funnel: from acquisition to regular usage

The funnel is built around the first result and a gradual disclosure of capabilities without overload.

Danger

If you show “all capabilities at once”, the user gets lost. DARCA must guide step by step: one scenario - one result - the next step.

• Stage 1: entry (Core, Academy, or a module).
• Stage 2: first result (one action that delivers immediate value).
• Stage 3: reinforcement (repeatability of the Core’s basic scenario).
• Stage 4: usage expansion (additional Core scenarios).
• Stage 5: revealing modules as trust and retention amplifiers (without overload and without a “feature showcase”).

Note

Disclosure management is managed through Segmentation: the next step is determined by user behavior, not by a generic list of capabilities.

Principles of communications and creative

Communications are built around transparency, error reduction, and trust - without loud promises and without feature overload.

Info

A strong DARCA message is a clear scenario where it is visible in advance what will happen and what the outcome will be.

• Scenarios instead of slogans: one message = one scenario.
• Transparency: the operation outcome and cost are visible before confirmation.
• Error reduction: contact-based transfers and recipient identification.
• Trust: documents as the standard output, security as a regime, support as guidance through completion.
• The Academy is used as a public “entry through value”: education leads to action, not to reading.

Tip

Modules strengthen positioning, but the Core must remain the primary promise: everyday actions within one perimeter, a clear outcome, and minimized errors.

Minimum set of metrics to manage growth

Metrics capture audience quality and growth sustainability: activation, repeatability, retention, and the contribution of invitations.

Example

Growth management: source - activation - repeatability - retention - invitation share - cost of acquiring an activated user.

• Activation: share of users who reach the Core’s first result.
• Time-to-first-value: time to the first result.
• Retention D7/D30 by segments and entry points (Core, Academy, module).
• Invitation share and the referral channel’s contribution to growth.
• Customer acquisition cost per activated user for paid channels.
• For business: lead - meeting - pilot - first operation, with conversion assessment at each stage.

Warning

In reporting, priority goes to metrics that reflect real usage, not superficial interest.

Positioning and provable pillars

Info

This block defines not a slogan, but a durable product logic: the category, the value Core, and verifiable pillars that can be demonstrated in the interface and processes.

---

Framework: a stable Core and adaptive execution

DARCA defines immutable principles of an everyday bank while remaining flexible to market, regulation, and infrastructure.

Note

Markets, regulation, and payment rails change quickly. DARCA adapts at the execution layer while keeping UX principles and the Core promise unchanged.

We define positioning as a set of durable principles that do not depend on specific networks, providers, or the current set of integrations. This allows implementation details to evolve without breaking the product promise.

DARCA’s flexibility is enabled by its architecture: the Core is responsible for everyday scenarios and a unified experience, while market changes are handled through updates to rails, integrations, and modules, without disrupting user behavior or the “daily” logic.

The source of truth for adjustments is scenario data: what leads to the first result, what repeats, where errors occur, and where distrust grows. Decisions are made based on behavior and compliance requirements in specific jurisdictions, primarily in the EU.

DARCA’s category and the meaning of an “everyday bank”

DARCA is a unified perimeter of everyday finance, where fiat and crypto operate under the same rules and are experienced as one seamless flow.

Tip

An “everyday bank” is measured not by the number of features, but by whether regular actions become simple, predictable, and repeatable.

DARCA belongs to the category of a daily bank: a product where the user solves everyday tasks without switching between fragmented services. The key meaning of this category is a single process-driven experience for fiat and crypto, where actions are equally clear and operationally complete.

An “everyday bank” in terms of real-life scenarios means that core actions are performed by default in a simple way, regardless of whether fiat or crypto is used:

• buy something in a store (for example, “buy bread”) - pay with fiat or crypto without feeling like it is a “different world”
• pay for an online purchase or delivery - with fiat or crypto, including virtual and disposable card scenarios
• transfer money to a person - via phone or email, not via a long address, with clear recipient confirmation
• top up, withdraw, exchange - as standard banking operations, not as separate exchange activity
• receive confirmation of the result - status, history, and a document as the standard completion of an action

A distinct value of DARCA is that the product does not only compete as a convenient bank. It brings the simplest and most familiar banking experience into the complex and often unclear cryptocurrency market. In other words, crypto stops requiring a separate “specialization” and becomes a natural extension of everyday banking.

The systemic market problem DARCA solves

The market problem is not a lack of tools, but fragmentation, errors, and uncertainty that prevent crypto from becoming everyday behavior.

Warning

Most solutions add features but do not create a unified process. As a result, complexity grows, errors increase, and trust in regular usage declines.

DARCA assumes that the market is overloaded with tools, but does not systematically close the everyday perimeter. Key problems appear repeatedly across different audiences and scenarios:

• Service fragmentation of financial actions
  • storage, exchange, payments, transfers, accounting, and security are spread across different services
  • constant switching breaks habit and increases the likelihood of errors
• Uncertainty of the operation outcome
  • users do not know in advance how much will be deducted, how much the recipient will receive, or how the cost is formed
  • the outcome becomes clear only after execution, which reduces trust and increases cancellations and disputes
• Details errors and a high fear of “making a mistake”
  • addresses, networks, tags, and irreversible operations create a barrier to mass adoption
  • the absence of human-centered recipient identification increases the risk of errors and fraud
• Weak operational execution and process opacity
  • statuses, verifiability, confirmations, and documents are often not the standard
  • it is difficult for users to explain “what happened” and prove the result to external counterparties or for accounting purposes
• Complex UX and a high entry barrier into crypto
  • crypto is often perceived as a separate complex market requiring knowledge and constant monitoring
  • solutions are either trading-oriented or storage-oriented, but not built for daily household activities
• A gap between crypto tools and real daily needs
  • crypto remains an “investment” perimeter that rarely becomes regular financial behavior

For businesses, these problems are amplified, because a repeatable process is required: documents, control, roles, exports, reconciliation, and integrations. Without operational execution, crypto does not become a working tool, even if transactions are technically possible.

DARCA’s core promise

DARCA turns crypto and fiat into a single everyday experience: predictable operations, fewer errors, transparent outcomes, and standard operational execution.

Info

DARCA’s promise is built on product mechanics that can be verified: contacts, outcome preview, recipient identification, statuses and documents.

DARCA promises the market a unified daily perimeter in which fiat and crypto operate under the same rules. The user makes decisions based on a clear outcome before confirmation and completes an action knowing the result, the cost and the recipient.

This is not an attempt to “make crypto more convenient in theory”. It is the construction of a process that reduces sources of errors and distrust, delivers operational completeness, and makes the crypto side as common as fiat operations.

DARCA’s verifiable pillars

Each pillar is a product mechanic that can be verified, removing a specific market pain point and leading to measurable behavior.

Example

The pillar principle is not “we are better”, but “here is the mechanic that removes an error or uncertainty, and therefore increases conversion into action and repeatability”.

Below are the key pillars, each described through: what it is, what problem it removes, how it is implemented, and what effect it delivers.

Pillar 1: A unified fiat + crypto perimeter for everyday use

• What it is: a single perimeter of daily operations without separating “banking” and “crypto”.
• What problem it removes: fragmentation and the need to switch between worlds.
• How it is implemented: the same action principles for fiat and crypto (transfer, pay, exchange, receive confirmation and a document).
• Effect: regular actions are consolidated within one product, usage frequency grows and turnover stays inside the ecosystem.

Pillar 2: Predictable outcome before confirmation

• What it is: an outcome preview of result and cost before confirming an operation.
• What problem it removes: uncertainty of outcomes, fee surprises, and distrust.
• How it is implemented: “you send/you receive” logic as the confirmation standard, not as a hidden detail.
• Effect: higher transaction conversion, fewer cancellations, and higher repeatability through trust in the process.

Pillar 3: Sending to a person, not to details

• What it is: transfers via contacts (phone, email) with recipient identity confirmation.
• What problem it removes: address errors, fear of sending, fraud risk, and irreversible mistakes.
• How it is implemented: contact-based addressing and recipient display (full name and photo) before confirmation.
• Effect: fewer errors and fraud, higher p2p frequency, and stronger shared usage (a natural network effect).

Pillar 4: Operational execution and documents as the standard

• What it is: operations have statuses, history, confirmations, and documents by default.
• What problem it removes: lack of verifiability, accounting difficulty, and process opacity.
• How it is implemented: an “operation dossier”, clear statuses, statements and data export, readiness for accounting and reporting.
• Effect: trust for retail and usability for business, reduced support load, and fewer disputed cases.

Pillar 5: Support as part of the product

• What it is: support-as-action - support drives resolution through actions in the product, not through long instructions.
• What problem it removes: user loss, prolonged investigations, and growing distrust when issues occur.
• How it is implemented: deep-links, buttons, and contextual actions in chat, step-by-step guidance inside the interface.
• Effect: faster scenario recovery, higher retention, fewer negative reviews, and lower servicing cost.

Pillar 6: The Academy as a conversion and error-reduction mechanic

• What it is: education in the “understood → did” format, as an external and internal layer of conversion.
• What problem it removes: high entry barrier and mistakes during first actions.
• How it is implemented: external tracks for acquisition and internal routes for activation, short scenario-based lessons instead of theory.
• Effect: low-cost acquisition in the EU, higher activation, fewer errors, and reduced support load.

The role of modules and positioning discipline

Modules strengthen the pillars and provide segment-specific entry points, without diluting the Core promise or turning the product into a feature showcase.

Danger

Positioning discipline: DARCA does not sell “250 features”. DARCA sells a process where everyday actions become simple, predictable, and verifiable.

Modules expand the product but do not change the base category of an everyday bank. Their role is to reinforce the key pillars and provide separate entry points for segments that require a deeper perimeter of control and processes.

• Enhanced security strengthens trust and risk control, increasing readiness to hold funds and perform regular operations.
• Business strengthens operational execution: roles, processes, approvals, exports, and integrations, turning crypto rails into a working business tool.
• Payments creates distribution through merchants and repeatable payment scenarios, forming sustainable growth loops.
• P2P strengthens exchange scenarios within the ecosystem through a controlled process and clear statuses.

The priority remains unchanged: the Core shapes mass everyday behavior, while modules increase depth, trust, and applicability for specific scenarios and segments.

Segment entry points and first-result scenarios

One product and one core, but different audiences enter through different entry points: the first scenario, a fast result, and a clear weekly loop.

Info

For each segment, the entry point, the first action (24-72 hours), the weekly loop, and the natural monetization trigger are defined. All entry points lead into the core, and modules are connected selectively to avoid fragmentation.

Segment	Main pain	Entry point	First action (24-72 hours)	Weekly loop	Next-step reveal	Monetization trigger
Individuals	Crypto feels complex and risky: mistakes, surprises, unclear outcomes	Core (primary), Academy (for beginners)	Contact-based transfer with recipient identification and a final outcome shown before confirmation (or the first payment/purchase)	Regular transfers/payments + exchange as a banking operation	1-2 adjacent core scenarios, then security/savings based on behavioral signals	Subscription for limits and predictability, overage only when exceeded, security as a trust amplifier
Freelancers	Fragmentation of “received - exchanged - withdrawn - accounted” wastes time and creates errors	Core + Academy, strengthened through documents	Receipt/exchange with final outcome before confirmation + confirmation or an operation document	Cycle “inflow - conversion - allocation - obligations”	Accounting/export, security, automation of recurring actions	Subscription for limits/frequency, overage on excess, modular benefits for accounting and control
Small business	Manual routine and the gap “payment - document - accounting”; needs a legal, repeatable process	Module (Business/documents), sometimes Core for the smallest	First operation with a predictable outcome + document/statement + simple export	Repeatable payments/payouts + export/reconciliation	Roles/permissions and limits, then integrations, later Payments	Subscription/seats + overage on exceeding limits, paid integrations
Mid-size business	Processes and control: approvals, risk, audit, reconciliation, predictable settlements	Module (Business: roles/approvals/audit) + integrations	Role/policy setup + first operation + provable status/log/document	Regular flows + limit control + reconciliation/reporting	Advanced risk policies, API/webhooks, Payments	Subscription/seat model, integrations/API, advanced control policies

Tip

The first scenario must deliver a result in minutes. After it, only the next logical step is shown - no feature showcase.

• For each segment, a single main first value is defined, not a list of scenarios.
• After the first value, only the next step is revealed, to avoid overwhelming the user and creating fragmentation.
• Academy is used where the entry barrier is fear of mistakes and lack of process understanding, and it leads to action, not theory.
• Modules are used as entry points only where they provide a fast and clear result, after which the user is transitioned into the core.
• Monetization is described as a logical upgrade: subscription provides limits and predictability, overage applies only when exceeded, and modules strengthen control and operational capability.

Academy as an acquisition and conversion engine

Academy builds trust through practical education in crypto and finance, then turns knowledge into action: first through applicable tools, then through built-in in-app instructions at the moment of an operation.

Info

Academy is public education on “how to do it correctly”. DARCA can be mentioned as one of the ways to apply knowledge in practice, but the materials do not turn into product tutorials and do not sell directly.

Academy and in-app Guides are different layers, one logic

Academy remains the educational layer about crypto and finance: mistakes, security, fees, accounting, discipline. Inside the app, a separate layer operates: in-app Guides , interactive instructions that help complete a specific action in the interface.

Note

The boundary is simple: in Academy, recommendations and application examples are allowed, but without screen-level “click here”. Any step-by-step interface instructions, animations, video training, and prompts at the moment of an operation belong to the in-app Guides zone.

The “knowledge - application” mechanic without direct selling

Each Academy piece ends with a practical result that can be applied immediately: a checklist, an action algorithm, a template, a calculator or an error map. The transition to the product is framed as an opportunity to apply knowledge within one layer and reduce the risk of mistakes, not as a direct call to install or buy.

Tip

In Academy, the key KPI is not “views”, but the share of readers who finished the material and took the next practical step: saved the checklist, used a template, completed a mini-test, or applied the algorithm in a real scenario.

Core Academy tracks (top level)

To keep Academy manageable and prevent it from turning into an “encyclopedia of everything”, the top level is built around a limited set of tracks that cover mass scenarios and key risks.

• Everyday: how to use crypto and fiat in everyday payments and transfers
• Error-free transfers: networks, addresses, tags, what to check before sending
• Fees and final outcome: how to understand “how much will leave/arrive”, spreads, confirmations
• Security: common fraud schemes and protection practices
• Documents and accounting: operation confirmations, statements, taxes/accounting for individuals and freelancers
• Financial discipline: reserves, stress scenarios, allocation rules, anti-impulse
• Business basics: the crypto operations process: documents, control, reconciliation, integrations
• Payments (later): payment acceptance, process, risks, compliance for merchants

Example

The track principle: one topic = one practical result. The material ends not with an “opinion”, but with a ready action: what to check, what to save, how not to make a mistake.

Academy formats that scale

• Short scenario-based lessons (5-7 minutes) with an outcome and checklist
• Error maps “what to check before confirmation”
• Templates: operation registers, checklists, document examples
• Mini-tools: calculators, tests, risk assessment
• Cases: situation breakdowns and typical mistakes without product instructions

In-app Guides principles (embedded instructions)

In-app Guides cover the “last mile”: they help complete an action directly in the interface, reducing errors and accelerating the first result.

• Contextuality: the prompt appears at the moment of action, not as a general reference
• Interactivity: video, animations, step-by-step scenarios, “try now”
• Pre-confirmation warnings: outcome, fees, risks, checks before sending
• Recovery: when an error occurs, the correct path and next step are shown

Warning

Guides must not turn into a “course”. Their job is to quickly bring the user to the correct action and reinforce a safe habit.

Bridges from Academy to the product that do not look like advertising

• apply a checklist in one place through a single unified action layer
• reduce the risk of mistakes through a predictable outcome and pre-confirmation checks
• automatically save confirmations and operation documents
• enable protection practices through security modes as an application of rules
• for business: embed the process and exports (operations, reconciliation, control)

Segment alignment

• Individuals: from fear and complexity to confidence and regular everyday actions
• Freelance: reinforcing the process “received - exchanged - allocated” and tracking confirmations
• Small business: repeatable operations through documents and reconciliation
• Mid-size business: process discipline, control policies, audit and integrations

Academy discipline

• no “we are better” comparisons and no aggressive calls to action
• no profitability promises and no dominance of “earn” narratives
• neutral “how to do it correctly” language and a practical outcome for every piece
• the product is mentioned as an application tool, but it does not become the subject of education

Lifecycle communications and product disclosure

After the first result, DARCA unfolds step by step: first, a habit is consolidated in the core, then control, documents, and relevant modules are added through the next step based on behavioral signals.

Info

Communications in DARCA are not “mailings”, but management of the next action: one message - one step - a measurable result. No feature showcase and no overload.

Step-by-step product disclosure

DARCA does not show the entire product at once. The user moves through sequential stages, where each next one expands behavior without breaking the simplicity of the core.

• Stage 1: first result in the core (transfer, payment, or exchange with a clear outcome)
• Stage 2: reinforcing the weekly loop (repeatability of core actions)
• Stage 3: trust and control (security modes, confirmations, documents)
• Stage 4: scenario expansion (modules based on signals, without overload)
• Stage 5: business level (processes, roles, integrations) when business intent is present

Tip

The disclosure logic is always the same: behavior first, then control, then expansion. This preserves simplicity and reduces mistakes.

Lifecycle triggers: what signals activate the next steps

Lifecycle is not built as “campaigns”. It activates based on behavioral and risk signals, when the user truly needs the next step.

• did not reach first value within 24 hours
• performed an action once, but did not repeat within 7 days
• performed an action 3 times (time to reinforce and expand)
• transfer/payment frequency is increasing (time to suggest accelerators and convenient scenarios)
• exchange frequency is increasing (time to reinforce predictability, time savings, limits)
• a request for documents/statements/taxes appeared (time to surface the document layer)
• signs of business intent appeared (suppliers, payouts, roles, registers, integrations)
• a risk signal emerged (new device, large amount, suspicious activity) - time to activate protection modes

Where we show the “next step”

The main work happens inside the product, where context and action are directly connected. External channels are used selectively.

• In-app: contextual prompts, “next step” widgets, in-app Guides, deep-links
• Support-chat: buttons and actions in chat as a fast route to resolution
• Push/email: short reminders and confirmations when in-app is not enough
• Academy: when confidence is needed and fear of mistakes must be reduced (without product instructions)

Note

Surface priority: in-app and chat as action layers, and push/email as a short “trigger to return”, not as a carrier of complex explanations.

Communication rule: one message - one next step

• each message suggests only one action
• there is always context “why now” and a clear outcome “what you get”
• “feature showcases” and long lists are excluded
• frequency is regulated: no pressure, no duplication, respect pauses and opt-outs

Lifecycle map: trigger - next step

Trigger	Goal	Next step (one action)	Surface	Success
No first value within 24 hours	Activation	Launch a short route to the first action (transfer/payment/exchange)	in-app Guides	First action completed
1 action, no repeat within 7 days	Repeat	Suggest an adjacent everyday core scenario	in-app	Repeat action within 48 hours
3 actions completed	Reinforcement	Enable simplification of regular scenarios (favorites/template/quick access)	in-app	2 more actions within a week
Rising transfers/payments	Acceleration	Show a scenario accelerator (contacts, recipient confirmation, quick actions)	in-app	Fewer errors/cancellations, higher speed
Rising exchanges	Predictability	Suggest the “clear outcome before confirmation” mode and cost control	in-app	More completed exchanges without cancellations
Request for documents/statements	Trust	Show how to obtain confirmations and a document package for operations	chat + deep-link	Document generated/exported
Business intent	Transition to business	Connect the basic business layer (documents/registers/control)	chat + in-app	First business scenario completed
Risk signal	Protection	Enable or strengthen security and confirmation modes	in-app	Mode enabled, risk reduced

Warning

The table captures the principle: a trigger leads to one action and a measurable result. This prevents spam and preserves experience quality.

Segment ladders (brief)

• Individuals: contact-based transfer - payment/card - recurring payments/exchange - security/savings based on signals - modules when ready
• Freelance: receiving - exchange - confirmations/accounting - allocation/reserves - security/automation
• Small business: first operation - documents/export - roles/limits - integrations - payments when appropriate
• Mid-size business: roles/policies - first operation - audit/register/reconciliation - API/webhooks/integrations - payments

Monetization in lifecycle: subscriptions, overage, modules

A subscription in DARCA is offered from day one as a transparent upgrade: higher limits, less friction, more predictable usage cost, and additional conveniences. Lifecycle communications help demonstrate subscription value in the context of the user’s real scenario, so the upgrade is perceived as a rational decision rather than intrusive advertising.

• Subscription: the focus is on benefits that directly match current behavior (transfers, exchange, documents, business processes)
• Overage: explained upfront as a fair “you only pay for excess” logic and always visible before confirming operations
• Modules: positioned as signal-based amplifiers - security when amounts/risk grow, Business when business scenarios emerge, Payments when merchant intent appears

Partnerships and distribution

Partnerships in DARCA are distribution channels that bring users into the core through repeatable scenarios and sustainable volume, not one-off PR collaborations.

Info

The EU priority is partnerships that deliver recurring scenarios, a fast first result, and clear unit economics, strengthening trust in the product.

Partnership selection principle

• a clear entry point: why the user comes right now
• a fast first result: an action within 24-72 hours
• repeatability: recurring transactions and a weekly loop
• economics: who pays and for what (revshare, fees, subscriptions, seats)

Tip

A partnership is considered “working” only if it leads not to registration, but to sustained repeatability: the user returns to the core as to their everyday bank.

Main partnership buckets (EU focus)

• Payments and merchants (online-first)
• Payout platforms: freelance, creator, service marketplaces
• Business ecosystems: accounting, ERP, invoicing (via connectors)
• Travel/relocation/expat and recurring expense services (insurance, rent, subscriptions)
• Communities/education through Academy and neutral learning
• Infrastructure partners (on-ramp/off-ramp, liquidity) as “rails”, without exchange positioning

Partnership formats

• embedded scenarios and deep-links inside the partner product
• referral / revenue share (without MLM logic)
• B2B distribution: packages and seats for companies through Business
• co-education: joint neutral materials through Academy

Partnership map: entry, first result, repeatability, economics

Partner type	Entry (scenario)	First result (24-72 hours)	Weekly loop (repeatability)	Economics
Payments/merchants	Paying for a purchase/subscription in fiat or crypto with a clear outcome	First payment and operation confirmation	Repeat purchases and recurring payments	payment fees, revshare, subscription growth for limits/convenience
Freelance/creator platforms	Receiving payouts and fast exchange/transfer	First payout + conversion with outcome shown before confirmation	Regular inflows, exchange, and allocation	revshare on flows, subscriptions for frequent operations, overage when exceeded
SMB/Mid: accounting/ERP/invoicing	Accounting layer and an “accounting-grade” process	First operation + document/statement + export	Payments, reconciliation, documents, control	seats/subscriptions, paid integrations, API/overage
Travel/relocation/expat	Cross-border scenarios: expenses, rent, insurance	First payment/transfer with a predictable outcome	Recurring payments and transfers	partner fees, subscriptions for limits and convenience, volume growth
Communities/education (Academy)	Neutral education “how to do it correctly”	Applying a checklist/template and moving to a practical action	Returning to Academy and expanding core scenarios	lower CAC, higher subscription conversion through trust and practice
On/off-ramp infrastructure	Simplified entry/exit and reliable rails	First deposit/withdrawal and conversion	Repeatable operations without friction	infrastructure terms, cost optimization, trust growth

Note

All partnerships lead into the core through everyday actions (payment, transfer, exchange with a clear outcome). Modules strengthen conversion and LTV: Business for processes and integrations, Payments for volume, Enhanced security for trust, Academy to reduce the entry barrier and the cost of attraction.

The link between marketing and monetization

Marketing in DARCA does not buy registrations, but behavior in the core: first result and repeatability. Monetization is designed to remain predictable and not conflict with the user’s interests.

Info

One unified chain: entry - first value - weekly loop - monetization. This chain makes growth manageable and the economics predictable.

What marketing actually “buys”: a measurable result, not interest

Marketing channels, partnerships, and module-driven entry points are evaluated not by installs, but by reaching a result in the core and sustained repeatability.

• Individuals: contact-based transfers, payments, exchange with a clear outcome
• Freelance: receiving funds and conversion, confirmations and operation accounting
• Business: operations with documents/exports and controlled governance (roles, registers)

Tip

Inside the product, results are captured through events: “performed an action”, “repeated”, “enabled control”, “connected the required layer” - this is more reliable than any “interest” metrics.

Subscriptions: a commercial goal without losing trust

A subscription is offered from day one as a transparent upgrade: limits, convenience, predictable usage cost, and additional capabilities. Lifecycle and communications do not “hide” the subscription, but translate its value into the context of real user behavior.

• the subscription is brought into focus when it delivers practical value in the current scenario (transfers, exchange, documents, business processes)
• the user understands not a “plan”, but what exactly improves right now: limits, speed, control, predictability

Overage: fair logic on top of limits

Overage is used as a predictable rule: “you only pay for exceeding limits”, without the feeling of a fee on every operation.

• the cost is always visible before confirmation
• overage lowers the barrier to start: the user understands the economic model is transparent and controllable

Note

This structure reduces conflicts of interest: DARCA is not incentivized to earn on every action, but earns from increasing usefulness and usage scale.

Modules: segment monetization and LTV growth without overloading the core

Modules are connected selectively based on behavioral and risk signals: they strengthen control, trust, and operational capability, increasing retention and LTV without turning the app into a feature showcase.

• Security - when amounts/risk grow and for users with high asset value
• Business - when business scenarios emerge and there is a need for documents/processes/integrations
• Payments - when merchant intent appears and payment acceptance is required

Lifecycle as the mechanism that turns acquisition into revenue

Channels bring users into a specific scenario, and lifecycle drives them toward repeatability and upgrade.

• in-app and in-app Guides accelerate result achievement and reduce mistakes
• support chat with buttons and deep-links reduces “time to resolution”
• communications follow the rule: one message - one next step

Map “entry - behavior - monetization”

Entry point	First value	Weekly loop	Primary monetization	Comment
Core-first (transfers/payments)	Contact-based transfer or payment with a clear outcome	Regular payments and transfers	Subscription + overage	Predictability and limits as a logical upgrade
Exchange-first (exchange)	First exchange with outcome shown before confirmation	Repeatable conversion for expenses/income	Subscription + overage	Convenience and time savings for frequent operations
Academy-first	Applying a checklist/algorithm and moving into action	Return to practices and expanding core scenarios	Subscription (through practical value)	Trust and lower barrier, without aggressive selling
Business-first	Operation + document/export	Payments, reconciliation, control	Seats/subscription + integrations + overage	Monetization as part of processes and control
Payments/merchant partners	First payment/payment acceptance	Regular payments/purchases	Fees/revshare + subscription growth	Drives volume and frequency, strengthens daily use
Security-led	Enabling protection and confirmation modes	Trust as volume/risk grows	Module/subscription	Strengthens retention and reduces incidents

Warning

For any channel, the full path to economics is defined: entry - result - repeatability - monetization. If the chain does not hold, the channel does not scale.

Short summary

Marketing in DARCA brings users into the core through specific scenarios and measurable results, not through abstract “interest”. Subscriptions and overage create predictable economics and support trust, while modules increase LTV selectively and based on signals, without breaking the simplicity of the daily experience. Lifecycle ties everything into a manageable growth mechanism: result - habit - upgrade.

Tip

DARCA scales not through “loud marketing”, but through repeatable core scenarios. Channels bring the user to first value, lifecycle reinforces the habit, and the product unfolds gradually - in a way that preserves simplicity and reduces mistakes.

• At the foundation of growth is an everyday bank, where crypto and fiat operate by the same principles: a clear outcome before confirmation, contact-based transfers, predictable costs, and transparent actions.
• Acquisition is built around channels that can scale without massive budgets: Academy as a trust-based entry, organic and search, partnerships as distribution at “points of regular use”, and targeted entry points through scenarios and modules.
• For each audience, its own entry and a fast result within the first 24-72 hours are defined, after which the user is moved into the core weekly loop and then shown only the next logical step - without a feature showcase.
• Academy remains neutral education on crypto and finance, while inside the app interactive instructions and prompts help users act correctly at the moment of an operation and reduce mistakes.
• Lifecycle communications connect everything into a controllable mechanism: one behavioral signal - one next step - a measurable result; support and action-driven chat accelerate the path to resolution and reduce friction.
• Partnerships are selected based on their ability to generate recurring volume and trust: payments/merchants, payout platforms, accounting/ERP, travel/relocation, and communities; formats include embedded flows, deep-links, revshare, B2B seats and joint educational projects.
• Monetization follows the same logic: the subscription is offered as a transparent upgrade, overage works as a fair charge only for exceeding limits, and modules strengthen LTV selectively based on signals, without breaking the simplicity of the core.

Note

In the end, marketing, product, and monetization work as one unified system: an entry leads to a result, the result becomes a habit, and the habit scales through predictable economics and scenario expansion without overload.