Webinar #2 – Blockchain-Native Embedded Finance Pilot

TRACTIAL held a new webinar dedicated to its blockchain-native embedded finance pilot. The purpose of the format was to provide an educational reading of the model, its concrete use cases and the deployment steps associated with it.

Hosted with Jim Dorra, Chief Executive Officer of TRACTIAL, and Marc-Antoine Caen Poletti, a journalist specialising in crypto, blockchain and Web3 ecosystems, the webinar addressed recurring questions about embedded finance, integration into business software, the role of APIs, the place of stablecoins, the regulatory framework and the company's development trajectory.

This summary sets out the main takeaways from the session in a model-understanding and use-case-oriented format. It does not replace the press releases, financial reports and regulated information published by TRACTIAL.

1. What embedded finance means within TRACTIAL's scope

Embedded finance refers to the integration of financial services directly into the business environments already used by companies. Within the scope presented by TRACTIAL, this approach mainly relates to payment tools, accounts, IBANs, reconciliation, payment notifications, wallets and certain technological bridges between traditional finance and digital assets.

The objective is to avoid forcing companies to multiply interfaces in order to manage their financial flows. A user already working in business software, such as a SaaS platform, CRM, ERP or management tool, may access payment features integrated into that environment, while relying on a regulated infrastructure.

Key takeaway: TRACTIAL positions embedded finance as a natural extension of business software, with a focus on usage, automation and compliance.

2. Why SaaS platforms are a strategic entry point

SaaS platforms are playing an increasingly central role in how companies operate on a daily basis. They bring together key functions such as customer management, invoicing, orders, services, activity data and, in some cases, interactions between users within the same professional community.

In that context, payments can no longer be treated only as a final step, disconnected from operational activity. When a platform manages a transaction, invoice, assignment, order or subscription, it naturally needs to know whether funds have been received, whether the operation can be automatically reconciled and whether the information can be fed back into the user journey.

TRACTIAL acts as a provider of financial building blocks that can be integrated through APIs. The partner platform retains its user experience and interface. TRACTIAL provides the payment rails, accounts, compliance tools and financial features required, within the framework applicable to its regulated activity.

Key takeaway: the value of the model lies in integration into existing software ecosystems, where users are already present and where payment needs are directly linked to business use cases.

3. What the pilot is designed to demonstrate

The webinar clarified the notion of a pilot. In the approach presented by TRACTIAL, a pilot is not a theoretical demonstration. It is a first phase of real-life use with a limited number of representative users, designed to assess adoption, the quality of the user journey, the relevance of the service and the conditions for a potential broader rollout.

The name of the partner was not disclosed at this stage. TRACTIAL recalled that such disclosure depends on the authorisation of the partner concerned and may be subject to commercial confidentiality considerations. For a platform, the integration of financial services may be a differentiating factor, which justifies a progressive communication approach.

The company also indicated that integrating platforms of a certain size takes place in stages and may require several months. This timing reflects the technical, operational and regulated nature of the services provided.

Key takeaway: the pilot should be understood as an operational execution step aimed at validating uses before any potential broader deployment.

4. The role of blockchain and stablecoins

TRACTIAL distinguishes between immediately actionable use cases and the possibilities opened up by blockchain technology. The company does not present blockchain as an end in itself, but as an infrastructure layer that may broaden the options available to platforms and their users when there is a relevant client need.

In the short term, the needs highlighted are concrete: collecting payments, identifying flows, automating reconciliation, notifying users, securing access to accounts and facilitating the management of operations. Stablecoins, self-custody wallets and blockchain rails may then become additional building blocks for certain use cases, particularly where clients wish to access features related to digital assets or alternative payment rails.

One important point raised during the webinar was accessibility. TRACTIAL indicated that it wants to make the technology understandable and usable, without requiring end users to master the technical complexity of blockchain protocols. Security and identification mechanisms, including passkeys, Face ID and Touch ID, were presented as ways to simplify the experience while maintaining a secure usage framework.

Key takeaway: blockchain is positioned as a technological extension layer, not as a speculative argument disconnected from operational use cases.

5. Concrete use cases identified

The webinar illustrated several possible use cases around the integration of IBANs, payment accounts, wallets and APIs into business platforms. These use cases are not limited to invoicing, although invoice reconciliation is a simple example for understanding the interest of the model.

A platform may, for example, wish to assign an IBAN to its users in order to facilitate collection, receive notifications when funds arrive, automatically match a payment with a business operation, offer a payment account integrated into its service, or provide a euro gateway to clients who need to receive and use funds in a digital environment.

The types of platforms mentioned include freelance platforms, crowdfunding players, certain crypto platforms, SaaS solutions handling financial flows and, more broadly, companies whose activity requires a better connection between payments and their business software.

Key takeaway: the addressable market is not limited to crypto players. It more broadly includes platforms that need to collect, monitor, reconcile and automate financial flows.

6. A business model based on service provision

The webinar also clarified the economic logic of the model. TRACTIAL provides financial and technological services that may be billed under several arrangements, depending on the size of the partner, expected volumes, the selected structure and the way in which the platform intends to present the service to its own clients.

Several configurations are possible. The cost may be embedded in the partner platform's offer, billed directly to the end user, partially borne by the partner, or linked to the actual use of certain services. This flexibility makes it possible to adapt the model to each platform's needs without imposing a single commercial architecture.

For the platform, the benefit lies in enriching its offer and improving the user experience. For the end client, the benefit lies in simplifying payment journeys. For TRACTIAL, the benefit lies in the provision and monetisation of regulated and integrated financial building blocks.

Key takeaway: TRACTIAL presents a service-based model, built around the use of its payment infrastructure and technological building blocks, with economic arrangements that can be adapted according to partners.

7. A positioning distinct from traditional banks

TRACTIAL explained its positioning through a difference in logic. Traditional banking players generally start from the bank account and build products around their own environment. TRACTIAL's approach starts more from business usage: the user is already present in its software, and financial services should be able to integrate into that environment when doing so improves the journey.

This approach is not intended to replace all banking players. Rather, it addresses specific needs of platforms, SMEs, very small businesses and SaaS players that wish to offer financial features without becoming regulated institutions themselves.

Key takeaway: TRACTIAL positions itself as an infrastructure player serving partner platforms, with a logic based on integration, usage and compliance.

8. MiCA and the regulatory framework

The regulatory framework was addressed in a dedicated section of the webinar. TRACTIAL recalled that it has been a licensed payment institution for several years and has an existing regulatory foundation for its payment activities.

Regarding MiCA, the company indicated that it is continuing its exchanges with the AMF within the applicable framework and that it has scenarios intended to support the continuity of its development. It also recalled that certain governance, compliance, internal control and customer knowledge requirements are already familiar to regulated payment players.

TRACTIAL specified that the pilot presented is primarily based on a technological entry point and payment services, without the immediate launch of a specific crypto service within the scope of the pilot. This distinction helps clarify the articulation between the existing payment activity, the opportunities linked to digital assets and the European regulatory timetable.

Key takeaway: MiCA is an important regulatory framework for the digital asset ecosystem, but the model presented by TRACTIAL does not rely exclusively on the immediate activation of crypto services.

9. The Bitcoin strategy within TRACTIAL's trajectory

The Bitcoin strategy was discussed as a long-term topic, linked to TRACTIAL's crypto culture and its view of how financial infrastructures may evolve. The company nevertheless recalled that this strategy should not take precedence over the development of the operational business.

TRACTIAL indicated that any Bitcoin exposure must remain compatible with its own funds, prudential ratios and the conduct of its regulated activity. The objective presented is therefore not to replace the operational activity with an asset-holding strategy, but to place it within a disciplined long-term vision.

Key takeaway: the Bitcoin strategy is presented as a long-term axis, distinct from TRACTIAL's operational core, which remains focused on payments, APIs, platforms and client use cases.

Conclusion

This webinar represents an educational step in explaining TRACTIAL's blockchain-native embedded finance model. It helps clarify how the company combines its regulated payment infrastructure, APIs, business software, payment accounts, self-custody wallets and the possibilities opened up by blockchain.

The main takeaway is that TRACTIAL presents blockchain-native embedded finance as a gradual evolution of its infrastructure towards operational use cases, including collection, reconciliation, automation, SaaS integration and simplified access to certain technological building blocks.

The webinar replay enables investors, partners, potential clients and sector observers to gain a clearer reading of TRACTIAL's positioning, within an educational framework that is consistent with the information publicly released by the company.

FAQ

What is blockchain-native embedded finance according to TRACTIAL?

It is the integration of financial services, mainly payment services and related tools, directly into business software. The term blockchain-native refers to the possibility of using certain technological building blocks linked to blockchain when they bring a relevant use case for platforms and their users.

What services can be integrated into a partner platform?

Depending on the case, the services presented may include IBANs, payment accounts, payment notifications, automatic reconciliation, self-custody wallets, compliance tools and certain bridges between traditional finance and digital assets.

How do TRACTIAL's APIs make integration easier for a partner platform?

APIs allow a platform to call TRACTIAL's building blocks from its own environment. The platform retains its user journey, while TRACTIAL provides the financial services, payment tools and compliance requirements needed for their use.

What does the pilot announced by TRACTIAL consist of?

The pilot corresponds to a real-life usage phase with a limited number of representative users. It is designed to test the journey, adoption, usefulness of the service and the conditions for a potential broader deployment.

Why has the pilot partner not been named?

The disclosure of a partner's name depends in particular on that partner's authorisation and on commercial confidentiality considerations. TRACTIAL indicated that some partners may wish to preserve the confidentiality of a project until integration has reached a more advanced stage.

Do the use cases only concern crypto platforms?

No. The use cases presented more broadly concern platforms that need to collect, track, reconcile and automate financial flows. Crypto platforms may be among the players concerned, but they do not define the entire addressable market.

Are stablecoins immediately at the heart of the pilot?

Not necessarily. TRACTIAL explained that stablecoins and blockchain rails may open up future use cases, but that immediate needs remain mainly focused on payments, collection, IBANs, reconciliation and integration into business software.

Does the end client directly handle cryptoassets?

In a self-custody wallet model, users may retain control over their assets. TRACTIAL presents its role as an accessibility and security layer, intended to make the experience simpler, notably through appropriate identification and authorisation tools.

What is the impact of MiCA on the model presented?

MiCA is an important regulatory framework for cryptoasset-related services. TRACTIAL indicated that it is continuing its exchanges with the AMF and recalled that its payment activity already relies on an existing licence. The pilot presented does not rely on the immediate launch of a specific crypto service.

How can TRACTIAL monetise this model?

TRACTIAL provides financial and technological services that may be billed under different arrangements, including usage-based fees, billing through the partner, direct billing to the end client or as part of an integrated offer. The arrangements may vary depending on the partner, volume and selected service scope.

What is the role of Bitcoin in TRACTIAL's strategy?

The Bitcoin strategy is presented as a long-term vision linked to the company's crypto culture. TRACTIAL nevertheless recalled that the development of its operational business, focused on payments, platforms, APIs and client use cases, remains the priority.

When will TRACTIAL communicate on new partners or pilots?

TRACTIAL indicated that it favours communication based on concrete milestones, when the relevant elements are sufficiently materialised to be brought to the market's attention in compliance with the framework applicable to listed companies.

Disclaimer

This page is provided for general and educational information purposes only. It summarises elements presented during the webinar and does not constitute an investment recommendation or a solicitation to buy, sell or hold TRACTIAL securities. Information relating to strategy, ongoing developments and prospects should be read in light of the press releases, financial reports and regulatory documents published by the company. Any investment decision involves risks and remains the sole responsibility of each investor.