Request AMA Questions & Answers – May 2020


This week the team participated in answering all questions asked by the Request community during the AMA thread on Reddit in April. As a lot of valuable information has been shared, we’ve listed the questions & answers below for a broader audience to discover.

What happened to integrations with ‘traditional’ accounting solutions like Xero or Quickbooks? Is it still planned?

Answer by Bernardo Rittmeyer

We are currently focusing our efforts on the cryptocurrency environment. We believe this is the niche where we will find more adoption in the short term.

We didn’t abandon the idea of integrating with these traditional accounting solutions, but they are not a priority for now.

What are your plans to drive adoption and use of the request network?

Answer by Robbin Mazurel

The original plan we had since the start was to mainly focus on attracting builders towards the Request ecosystem, to build specific products/services for specific use cases, powered by the protocol built by our team. It’s safe to say that plan wasn’t as successful and widely adopted as we imagined it to be.

Because of that, we’ve switched strategy. We now focus on both creating a platform to collaborate/integrate with external developers (such as Gilded, Multis & Gnosis Safe), ánd to create products for end-users directly based on market & user research. Request Create & Pay are the most recent result of this strategy. These products have been entirely based on direct needs from one of the main users of the Request network today – MakerDAO.

Moving forward, we’ll both focus on driving adoption for our own product offering, as well as driving adoption towards products/services from external developers that are connected to the Request network.

Can you do online monitoring of the most important ecosystem indicators? For example the number of connected Internet sites, the total number of burned tokens, the number of users per day, etc.

Answer by Bernardo Rittmeyer

We recently worked on a set of internal monitoring tools that give us more visibility on some of these indicators. Some things are easy to measure, such as the number of requests created and the number of tokens burned.

Some other things, due to the decentralized nature of Request, are harder. For example, it’s harder to measure how many request nodes are running on the entire network, or from which Dapp a request comes (if the Dapp creator doesn’t want to share it).

Are developers still building on Request? It seems there was a Request fund set up a while back and a few apps were built, is there still any interest or new dApps being built on Request?

Answer by Robbin Mazurel

Yes, but we’ve chosen a different route lately to achieve this. As we’ve answered in some other questions, the “build it and they will come” approach we originally took, combined with the Request Fund, hasn’t worked out the way we’ve intended it to work out, with an exception for Gilded, who’s doing a great job at proving how valuable external developers are for a platform like the Request network.

Lately, we’ve focused largely on an integrations approach to get people to build with Request, rather than on Request, where we’ve reached out to 100+ organizations in the industry to see if there would be a mutual benefit to include (parts of) Request’s technology inside of their product/service, to better serve their customers. This strategy has proven to work very effectively, with more than a handful of organizations now either integrating and/or interested in integrating Request as a payment request feature in their product.

We aim to sustain this strategy and broaden up the scope of businesses we approach once the first integrations go live and show success for both their customer base and our network usage.

What is the number #1 priority for Request in the next 6 months?

Answer by Christophe Fonteneau

Follow up with the 100+ organizations we’re reached out to and make sure the first integrations like Multis and Gnosis are getting traction

What are your current plans to onboard new clients and what market are you targeting?

Answer by Christophe Fonteneau

We’re in contact with several crypto asset management platforms, exchanges and wallets who are integrating Request. We’ve released a website lately that showcases this a bit more in-depth.

Is there any interest from Enterprises or Companies outside of crypto for using Request or any of its dApps?

Answer by Christophe Fonteneau

Yes, we had discussions with companies from the non-crypto world for using Request as a trusted log for invoice statuses between companies. Request technology can be used by companies to share business trades lifecycle: from the purchase order, invoice, good delivery, to payment reception.

Do you have contacts of other crypto or non-crypto projects/entities that are interested in using Request, besides the ones already known?

Answer by Christophe Fonteneau

Yes. The launch of Request Create and the announce of the first one million $USD million transacted on the network generated leads and traction.

What’s the planned long term business model for Request and how are the current integration efforts contributing to it?

Answer by Christophe Fonteneau

Medium-term: share new revenue streams with customers

Long term: generate revenue from apps built on the network

How big of a threat are CBDCs (central bank digital currencies) on permissioned blockchains for Request’s business model?

Answer by Christophe Fonteneau

CBDC is a fantastic opportunity for digital currency adoption. Digitization of the economy and digital currencies are opportunities, not a threat, and showcase the need for an invoicing network that is interoperable with as many types of digital currency networks, both crypto and non-crypto based.

How long are you able to hold on with the project before mass adoption?

Answer by Robbin Mazurel

We’ve currently got multiple years of runway available to sustain further development of Request on all fronts (development, sales, marketing, etc.).

We’ll be working around the clock to find legitimate revenue streams to sustain & grow the business in the meantime.

It seems that a lot of projects from 2017 are gone and failed to deliver on their promises. How will Request avoid the same fate? How can we be confident that Request won’t disappear a year from now?

Answer by Yoann Marion

Since January we have positioned Request as the infrastructure for payment documentation in front of wallets and exchanges. Our value proposition was considered with great attention. Being blockchain and currency agnostic puts us in a great position.

If wallets are the banks of tomorrow, they need to onboard the corporate banking services and invoicing tools of tomorrow.

We released Create and Pay to ease this positioning and to make the transition from a self-standing position, that we had with The million-dollar milestone we reached recently is the proof that our value proposition is legit, and being positioned aside the banking infrastructure of tomorrow is very strategic.

Besides, our current runway (which depends on the price of ETH) is of more than 3 years.

What are the greatest challenges the Request team are finding at the moment?

Answer by Yoann Marion

Fiat! Everybody keeps talking about EUR, SGD, GBP or USD… And these legacy systems are harder to integrate 🙂

When will we be able to make purchases with Request using the currency of our choice (including USD) as stated in the whitepaper?

Answer by Yoann Marion

Request can support e-commerce in order to ease cryptocurrencies adoption, simplify the payer’s UX and provide merchants with cheaper and faster payment solutions. Request integration in wallets and exchanges is a good advantage for the payer’s UX, by linking invoices and receipts directly to his bank account.

We have launched a survey recently to better understand the current pains of paying in cryptos. Even within the Request community, not everybody is keen on replacing usual payment cards with cryptos. We are also looking for solutions to accept fiat payments aside cryptos because crypto adoption will be done gradually and shop owners should not have to choose.

Request seemed to have lost its community during the 2018 bear market (at least the Reddit community). Do you think Request will ever win them back?

Answer by Robbin Mazurel

You’re 100% correct that we’ve lost a vast majority of our active community, especially when comparing it to the numbers we once had during the (pre-)ICO/pre-2018 crash phases.

However, we still have a small but highly supportive community of (early) Request followers around, mainly on our discord channel & subreddit, which we will forever be grateful for. While it’s hard to say whether or not we’ll reach a similar amount of active people in the future, we all do agree internally that we’ll be able to rebuild a community once we’ve hit proper Product-Market Fit. We see this community’s majority consist out of people that also use one (or multiple) of our product(s)/services, or build on top of the platform we provide for external developers. Which channel we’ll use to support & nurture that community as an organization is based on what product finds the highest traction, which I’ll only be able to answer at a later date.

Can anything be shared transparently about any competitor analysis that has been performed?

Answer by Christophe Fonteneau

There is no competitor covering the full scope of what we do at Request.

Some companies overlap our value proposal in some domains. Some recent examples:

– overlaps on crypto invoicing with the recent launch of a new invoicing feature on March 24th

– FIO foundation is a naming service, competing with naming services such as ENS, Unstoppable Domains & IOV, which also provides kind of a request for payment. No feedback yet on this as they were not live until April 2020.

Looking back, do you feel that most crypto projects/investors were delusional back in 2017 and had unrealistic expectations?

Answer by Christophe Lassuyt

Sure. Even in 2017 that was clear. Better to be ambitious than not, imo

Honestly, what do you guys think about crypto ‘investors’? We aren’t necessarily stake holders/hold equity but we can be very demanding and sometimes hostile. Is this one of the reasons why the team goes ‘dark’ sometimes?

Answer by Christophe Lassuyt

Yes. Crypto investors brought value to projects, by providing financing, and that’s already a lot. However, all of them don’t seem to be crypto users. That’s challenging to get feedback about our tools, or just to get support for our launches (like the recent one on product hunt).

Hello guys, maybe a vague question – how would you describe the mood within the team nowadays?

Answer by Brice Sturms

Besides the eery backdrop of COVID, team spirit remains high. Our familiarity with remote work has made the transition pretty seamless. As far as mood goes, we’ve been getting some good rounds of feedback from our users that our product provides them value. Nothing puts a smile on our faces or motivates us more than that 🙂

Who are you targeting to become your next customer/user?

Answer by Yoann Marion

We work a lot with wallets and exchanges, they are the banks of tomorrow, and that’s were the invoicing of tomorrow should be positioned.

Who is currently your main customer audience and what are the main benefits of Request for them (Triple entry accounting solution, payment requests, etc.)?

Answer by Christophe Fonteneau

We’re currently mostly focusing on working together with crypto-native/crypto-first B2B & B2C companies like Multis, Gilded & Gnosis, who are creating products/services for a customer audience that is well versed & interested in using cryptocurrency as a means of payment for both business & personal expenses. As an effect, we’re slowly “filling” that triple entry accounting system to become valuable for deeper, more complex use cases which we’ve originally touched upon in our whitepaper two+ years ago.

Next to that, we’re also building our own products, starting with Request Create which recently launched. These products are currently targeted directly at crypto-enthusiasts & early adopters, to better understand their usage behaviour, to improve the Request network based on feedback.

With the trading pair of req/eth being shut down on Binance – is the team in talks with other exchanges to list req in the near future?

Answer by Christophe Lassuyt

The reason why it was delisted is because of a lack of volume, other exchanges will have the same issue. Though we have been in talks with exchanges over the last few days.

There were initial talks about a Fiat Gateway possibly using Chainlink and it seems that this is very challenging and put on the back burner. Are there still plans for this?

Answer by Brice Sturms

Fiat is how the world currently operates, so it is definitely still in our sightlines. That being said, proper fiat gateways are a huge challenge that other companies are attempting to solve. We monitor their progress closely and are ready to strike when the time is right.

What is the strategy of req on fiat? Fiat is the only thing which will give adoption right now. Integrating with other crypto companies which themself don’t have adoption might not help in the short term. In the long term, it might be good but req needs to survive till that time

Answer by Robbin Mazurel

We’re already seeing (early) adoption of our product in the crypto/DeFi ecosystem and have chosen to focus on these signals, as we believe this will be the best way forward to create a sustainable blockchain business.

We’re currently able to survive multiple years without the requirement of having adoption on a product level. Our strategy on fiat payment detection is to include it in our product offering once we validate there’s a high need in the market(s) we’re targeting. Until today we haven’t found clear indicators that integrating fiat payment detection has a strong demand from the (potential) users we’ve talked to.

What are your views at the moment on Fiat to Fiat using Request? Is it still a possibility? I still think it has the biggest potential to drive adoption forward. It would also be the first use case where I would use Request myself.

Answer by Robbin Mazurel

Recording fiat-to-fiat transactions with Request are definitely still a possibility, but it’s currently not our first priority.

The way we’re approaching adding new features to our products right now is by talking & listening to a handful of (very) early adopters and learning from their direct needs to build better products. For instance, the first one million dollar worth in crypto transacted through the network is a great milestone for us to reach, as it shows early validation of a specific product offering we’ve created for crypto-first companies. Analyzing the usage and drawing learnings has resulted in launching Request Create recently, an improved product based on talking with its early users.

Speaking for recording fiat-to-fiat transaction using Request, we’ve had little confirmation (yet) from markets we’re researching to make this into a priority. Did you already fill in our user research we’re currently conducting? We’re scheduling a lot of calls at the moment to talk with potential users of Request and would love to learn what makes fiat-to-fiat transaction recordkeeping attractive for you to use Request in the future.

The research we’re conducting can be found here:

After the poor decision making with the MakerDAO CDP (Collateral Debt Position) – does Request have a financial plan for the next bull run (i know this is premature but better to have a plan than not) – liquidating their ETH reserves for USD/stablecoin to support the future of the project – if so, what price points are we looking at – I can see ETH reaching $500-1000

Answer by Christophe Lassuyt

In the current context, I believe the decision had a bad outcome if we were to evaluate it at the very moment. We have a plan and part of it is to diversify. Request finances are my responsibility and I don’t intend to detail finances on social media. Such info is the kind of information we give to our biggest partners and contributors.

Also, will some of the funds (from the treasury) be used to;
  1. ‘burn’ some of the token supply (this will create a talking point about the token and reward long term holders)
  2. look at the possibility of market makers (will be good for volume with the looming risk of getting delisted for low volume)

Answer by Christophe Lassuyt

1. No

2. We started working with a market maker recently

How is the budget/runway doing? Can the team last a while considering we’ve been in a “bear” market for a couple of years?

Answer by Christophe Lassuyt

Multiple years in a bear market. A full breakdown can be found in my post here.

What is your runway stock? What business model to maintain the protocol is planned on an ongoing basis?

Answer by Christophe Lassuyt

We consider we have not reached the product-market fit yet, therefore no clear definition of our business model. However, it is likely that it will be a transactional one. + premium features such as invoice financing

What are your long term plans for solvency? We, of course, know about the amount of ETH you still have and that should last a couple of years. However, what do you guys have in mind to generate cash flow after those years?

Answer by Christophe Lassuyt

Transactional business model + premium features such as invoice financing

What do your finances look like if ETH were to stay under $100 for 6 months to a year?

Answer by Christophe Lassuyt

Our runway would still be multiple years

How come the team didn’t tether the ETH they raised from the ICO to a stablecoin to avoid the volatility in crypto?

Answer by Christophe Lassuyt

There were not many stablecoins in 2017, and we did not have an account at an exchange. The risks of putting a big volume of funds on an exchange (with no account) were important.

What are the ambitions for integration? Which are the preferred clients/users?

Answer by Brice Sturms

Our goal is for our technology to remain as open as possible. We think one of the biggest pitfalls that blockchain solves is the walled gardens that exist today where users are trapped in a product ecosystem.

This is natural for businesses; it allows them to maximize their revenue and control their users’ experiences. We want to integrate with other services to give users choice and flexibility. Wallets are our current focus. It is a compelling vertical because there are highly specialized wallets for different use cases.

For example, Gnosis Safe is the premier b2b wallet provider. Our integration with them will make it easier for businesses to harness crypto and improve the efficiency of their operations. This unlocks downstream b2b use cases for Gnosis Safe users that aren’t built by Gnosis themselves. This is incredibly powerful and is one of the big reasons why walled gardens will give way to open ecosystems, powered by blockchain.

Can you consider integrating with the Melonport project? they do not have an accounting report, maybe it will be interesting for both projects

Answer by Yoann Marion

We don’t know the project and got in touch with them to know more.

Mona El Isa from Melonport would be happy to get in touch with you in order to understand what you expect, @monaelisa on Telegram

Can you consider integration with the Status project? perhaps in the reporting section for all transactions, etc.

Answer by Yoann Marion

They should definitely integrate Request! If you know a contact to prioritize it, our documentation makes them totally autonomous to do so. We can also assist them with specific needs, of course.

Last year we got an update about the targets the team had for 2019. Can you share with us which are the goals for this year? I mean main milestones or volume of transaction expected or number of possible clients

Answer by Robbin Mazurel

Our main goal at Request is to find product-market fit.

We strongly believe in what we have created so far, and there are dozens of uses cases that can benefit from the core Request technology available today. Right now, we’re mainly looking at use cases that create real value for our users, increase adoption of the network and unlock other uses cases. For the first period in 2020, our focus has been the wallets use case, where the goal has been to get integrated with multiple wallets to create an interoperable ecosystem of payment requests for wallet & exchange users.

In terms of specific targets & milestones, we aim to integrate with at least two wallets and process at least 1,000 transactions in the coming months. It is essential to add that we mainly focus on learning as much as possible so we can improve with short iterations.

What kind of metrics and figures (e.g. transactions per day, or amount transacted) do you target to determine whether the business model was a success in the next 5 years?

Answer by Yoann Marion

Both kinds of metrics are interesting, it depends on what you want to know.

The number of transactions per day is directly correlated to REQ burn.

The average transacted amount shows who use the network. Additional services such as corporate finance, accounting or audit, will be most useful for B2B so probably bigger amounts.

The global amount transacted on the network is proof of trust and a good engine for adoption.

What do you consider as your biggest obstacle for long term success and how are you trying to overcome it? (Similar to Martin’s question, but more long term focused)

Answer by Bernardo Rittmeyer & Robbin Mazurel

The biggest challenge for Request at this point in time, as for many in the domain, is the adoption of cryptocurrencies in general as an alternative means of payment, rather than mainly being used as a speculative asset class. Reaching the tipping point of adoption is our main obstacle, which we try to overcome by building both a platform & products which are aimed at proposing the unique values of cryptocurrencies & blockchain to builders & end-users, while also providing them with an experience that is on par, or better than non-crypto alternatives.

We’re far from there yet, but our ultimate goal at Request is to make crypto used for payment purpose on a daily basis, in preferably all spaces, ranging from B2B to C2C.

One way we’re preparing that right now is to conduct a massive amount of 1-on-1 user interviews to learn how & why people are/are not using cryptocurrencies as a means of payment today. Contributing to this research helps us a lot to understand our potential audiences better – if you haven’t done so yet, we’d be more than happy to schedule a call to talk.

How many people are currently working on developing the protocol? How many more do you plan to attract people?

Answer by Laure Sassus-Bourda

We currently have 4 fulltime developers working at Request (Adam, Benjamin, Bernardo, Vincent), with Yoann assisting development part-time in his role as COO.

Recruiting is not a priority for us at the moment. We have job openings that you can find on our website and we are always interested in meeting with candidates that want to join the team now or in the future.

Updates on Christophe’s work with the EPC? Latvian government? Other governments? Banks perhaps?

Answer by Christophe Fonteneau

The work initiated with the Latvia government is stalled, we decided not to invest more time since they do not know exactly what they need, what they want. We do not have other initiatives at Government level.

First deliverables were submitted early 2020; interesting but very political and still bank-centric. Relevant info can be found here:

Have you had any partnership contacts with any financial institution?

Answer by Christophe Fonteneau

This was not on our roadmap, but we’ve had the opportunity to talk to the US clearing House and people from SEPA while representing EESPA E-invoicing association at RTP MSG working Group

What is the team’s vision and the timeline for non-crypto transactions and bookkeeping?

Answer by Brice Sturms

At this point in time, there is an untapped market to better serve users who already use or have ambitions to use crypto to power their businesses. We plan to address this market first before deciding to enter the more crowded sphere of non-crypto transactions and bookkeeping.

Have you thought about something like TransferWise is doing with their borderless bank accounts? Would something like that be possible with the Request Network? I see great potential in such a service where you don’t even need to convert the money to different currencies manually (which I still need to do using TransferWise), but one where you can pay everywhere with the same ‘bank’ card / app without having to have the money in the relevant currency as this would happen automatically by the Request Network).

Answer by Brice Sturms

Yep, cross-currency is hugely important to support borderless commerce. We would not be able to handle it the same way as Transferwise, as it seems that they are simply holding all of the funds themselves, earmarking any incoming funds as associated with your account. This allows them to maintain a log of your current balance and cash out when you want. This is cool, but dangerous as you are trusting Transferwise with your funds — they have the power to refuse a cash out request. Our challenge is approaching this in a way that is non-custodial. That was a long way of saying: Yes, it’s definitely part of our vision!

Are you planning to develop on the Polkadot network?

Answer by Bernardo Rittmeyer

No, we are not currently planning on using other blockchain than Ethereum on our protocol.

Can you please reflect on the Request Fund strategy? What where your learnings, have you as a team changed your mindset and your strategy regarding product (as in building ON Request) development?

Answer by Christophe Lassuyt

The Request Fund and Request Hub were not successful. However, we learnt that it was too early to create the ecosystem of builders and that we better build ourselves the first product to find product market fit.

Looking back at 2017, what are some things that you would have done differently?

Answer by Yoann Marion

Probably many things, we keep learning constantly. One thing that keeps hurting: the reference to our former brand name: Request Network.

In retrospect, we should have picked Request from day 1.

What are the quarterly goals for Request?

Answer by Yoann Marion

We now split the year into thirds and are achieving the first one of the year. We are currently working on 2 wallet integrations (Multis and Gnosis), and are ready to integrate many more, including wallets. Our documentation makes it possible for any wallet to exchange payment requests very fast, without our intervention.

We have also achieved the $1m milestone and released the first applications based on the protocol V2: Request Create and Request Pay. These two apps give a good glance at the Request UX to wallets, and they are also independent products. We received some relevant feedback during the Product Hunt campaign and will take it into account shortly by adding more currencies.

What is, in the team’s eyes, the single most important thing on a technical and on a business/acquisition level to develop in 2020?

Answer by Brice Sturms

Our biggest goal to reach as Request is adoption of cryptocurrency as a means of payment. As we strive to be a user-driven company, receiving feedback from early & potential users is very important for us in defining the best direction of both technical and product development.

Right now, we’re moving into a direction that looks like early potential product market fit on both an end-user product (Request Create) and on platform integration. The most important thing right now is to keep chasing these early signals and learn by listening to all feedback we receive.

How do transaction fees work now? I think I remember in the past they were moved from a % of the transaction cost to something relating to the amount of memory the transaction uses? Could there be some examples of how that would work in practice? This is not explained at all on the website

Answer by Robbin Mazurel

With v2 of the Request protocol, the way transaction fees are calculated has slightly changed compared to v1, while most of the mechanism to take & burn these fees remain the same.

Currently, the fee to create a request is calculated per byte, with a minimum fee set to prevent spam.

That calculation looks like this:



The current fee structure (snapshot was taken on 30th of April) are:

Fees per bytes: 0.000000000315549784 ETH

Minimum fees: 0.000465243024690420 ETH

To sketch an example, let’s take a simple request created on Request Create. A request created through this product specifies the amount to receive, with the option to specify the payer’s address and a reason.

Looking at an average use of this product over the last few weeks, we’re monitoring that the average payment request created ranges between 1200-1500 bytes in size. The fee of a request created through this product costs ~1500*0.000000000315549784 = ~0.00000047 ETH, which is an amount below the minimum set fee per request. Per the calculation, this means the fee taken is bumped to the minimum fee size, which is 0.000465243024690420 ETH, which is ~$0.10 translated to USD.

What we’ll do is create a section on our documentation page to address this specifically with some more explanations/calculations, and directly link to that part from the website you’ve mentioned.

Are there any plans to bring governance or staking options to the request token in the next 6 months? Year?

Answer by Yoann Marion

Nothing planned as of today, but we are in touch with interested projects. We encourage other organizations to host Request nodes and to participate in our decisions.

The team is already organized in a decentralized way, we are ready to welcome stakeholders in our decision processes. The token is a way to make it scalable, but we are the only node hosts today.

You repeatedly mentioned governance and staking as options, but after 2 years we dont have a lot of information on those topics. Could we perhaps get more specific information or ETA about them?

Answer by Yoann Marion

Governance and staking will be key for the network to remain independent and resilient. The REQ token is an important brick of our strategy.

There is no ETA to give, it will become a priority when it makes sense for other organizations to run their Request nodes.

Request Create & Pay were the first products we released on the Request protocol V2. The products are strong arguments for wallets and exchange to rely on an open network instead of closed loops. With adoption, truly decentralized actors may want to run their own node. We invite them to do so.

What is Request’s value proposition? It appears to have shifted over time.

Answer by Christophe Fonteneau

A trusted record where organizations, companies and individuals can share and retrieve invoices and transaction receipts of all their transactions made.

In order to benefit from this network’s features, users can for example:

– Create and retrieve transactions from their favourite DeFi products and dApps like Gnosis, Multis, Gilded, Request Create…

– Create and retrieve transactions from their usual e-invoicing or accounting software, once connected to Request

Some say that what this project is providing a ‘nice to have’ or that this project was built hoping for demand instead of building a solution to meet demand…Let’s face it, most people can get by without a decentralized invoicing system. What are your thoughts on this?

Answer by Christophe Fonteneau

Yes, this is right today – most people can get by without a decentralized invoicing system available to them.

Likewise, people could have kept horses instead of getting a car back when cars were being created.

We’re not addressing an existing market, we’re creating one. We are innovators, we are makers.

Our Vision is to enable a global cooperative financial system where people and organizations are in full control over their financial data and choices.

The “nice to have project hoping for demand” has so far:

– Positive feedbacks form the recent outreach towards over 100+ industry-leading organizations

– Recently crossed the 1st million USD transacted on the network, proving early market fit

– The trust form some of the most legit DeFi organizations like MakerDao or Gnosis

We’ll continue working hard to make this “awaken dream” a reality in the future.

Have you looked at the possibility on the integration of the request network into DeFi/mobile wallets like MetaMask, Argent, Pillar, or any other? Making/receiving a payment with a wallet and having the possibility of issuing/receive an invoice seems interesting.

Answer by Robbin Mazurel

Very interesting question and the answer is that we’ve been focusing on reaching this for the last months as a strategic push internally to get the network integrated into external products, specifically focused on wallets and/or other tools that people use to manage crypto funds.

The first showcase of this strategy producing results can be followed on the “Connect” page here, where we track early product teams like Multis, Gnosis Safe & Gilded that have given us a go on integrating (part of) the Request network functionalities into their product, to serve their customers better. We’ve also been in touch several times with the companies you’ve highlighted and are on their radar – time will tell if we will be working together on integrating Request.