TL;DR Key takeaways
- In this EU MiCA discussion, an order receipt acknowledges an instruction; it does not, by itself, establish a concluded sale.
- A provider named as counterparty may also execute on your behalf. Establish what it undertook to do, not just whose name appears.
- Request records that resolve the uncertainty: the handoff, concluded agreement and provider capacity, or applicable pricing and finality terms.
Your team is reconciling a crypto-to-fiat conversion. The provider has sent an “order received” message and a confirmation naming itself as counterparty. You have an order reference and a name against the trade. What you still need is an explanation of who concluded the agreement—and in what capacity.
That distinction determines what the records establish, what responsibility the provider assumed and which question to ask when the price or timing does not reconcile. The useful dividing line is the agreement that turned your instruction into a purchase or sale, not the status label in the provider’s system.
Find the agreement, not just the handoff
The legal framework here is EU MiCA and ESMA’s interpretation, not a universal classification of crypto services. It distinguishes receiving and transmitting an order from executing one on a client’s behalf.
Reception and transmission means receiving an order and passing it to a third party for execution. That recipient may itself be another intermediary. Article 80 of MiCA requires arrangements for prompt and proper transmission, but a proper handoff is not the same event as a completed trade.
Execution on behalf of a client means concluding the purchase or sale agreement as the client’s agent, whether directly with another party or on a trading platform.
For your reconciliation, an “order received” message establishes that the provider acknowledged the instruction. A transmission record identifying the next recipient can substantiate where it went. Neither, by itself, establishes that someone concluded a sale of your crypto.
A counterparty name does not tell you the whole role
The confirmation appears to provide a shortcut: if the provider names itself as counterparty, surely it traded with your PSP rather than acted for it?
Not necessarily. The counterparty field identifies who is named on the other side of the trade. It does not explain what that party undertook to do for you in concluding it. ESMA expressly explains that a counterparty can also provide execution services and be subject to best-execution requirements.
Trading with your PSP does not, by itself, rule out a responsibility to act on its behalf. If the provider undertook to conclude a sale as your agent, naming itself as buyer does not establish that it instead supplied only an own-account exchange. You still need to establish whether it offered its own deal for you to accept or undertook to act for you in concluding one. That is the useful business question behind principal vs agency trading.
Consider four hypothetical ways the same PSP crypto-to-euro conversion could happen:
- Introduction only. A contact introduces your PSP to a buyer but never receives or handles the sale order. Your PSP sends the order directly to the buyer, and those two parties conclude the sale. In this example, the contact connects the parties; it does not transmit or execute the order.
- Reception and transmission. A provider receives your actual sell order and forwards it to another firm, which concludes the sale as your agent. The first provider transmits the order; the second executes it.
- Execution on your behalf. The provider receives an instruction to sell for your PSP and concludes the sale as your agent. A confirmation naming that provider as buyer would identify its counterparty position, but would not, on its own, establish that the service was only an own-account exchange.
- Own-account exchange. Your PSP accepts the provider’s offered terms and places an order with it. The provider concludes the purchase with your PSP using proprietary capital. In this example, it offers its own deal rather than undertaking to act as your agent.
These examples distinguish actions, not labels that automatically settle the classification. ESMA’s assessment is fact-specific: the actual fulfilment flow, the relationship and what a reasonable client would understand all matter. Did you reasonably expect an agent seeking the best possible outcome, or understand that the provider only offered a firm price you could accept or compare elsewhere?
Different roles mean different undertakings
For an own-account exchange, the central question is whether the provider honoured its offered terms. Article 77 requires a published firm price or pricing method, disclosure of when an order becomes final, and execution at the displayed price when it does. ESMA explains that once an order meets the previously communicated commercial and finality conditions, the provider has no discretion to refuse fulfilment.
For execution on your behalf, Article 78 requires the provider to take all necessary steps to obtain the best possible result, considering price, costs, speed, likelihood of execution and settlement, and other relevant factors. That is broader than a promise about the headline price. Article 78 also contains an exception where orders are executed following specific client instructions, so those instructions matter to the assessment.
Neither model is inherently better. Each involves a different undertaking—and that undertaking gives your operations team the right basis for questioning an outcome.
Request the evidence that closes the gap
The most useful request is not “send us all the logs.” It is: show how this order became a concluded agreement, and in what capacity you acted. Each record should answer a particular uncertainty.
If the provider says it routed the order, request the transmission record identifying the next recipient. That supports the handoff, not a completed trade. To establish the trade, request an order-linked record of the concluded agreement showing the parties and who acted on whose behalf. Your existing confirmation may supply part of that answer; the missing element may be the provider’s capacity rather than another trade reference.
If the provider says it offered an own-account exchange, the applicable quote or pricing method and the finality terms connect the transaction to the deal your PSP accepted. Those are the relevant records for understanding when the order became binding and on what pricing terms.
Where the provider executed on your behalf, its execution policy describes the approach it promised to follow; order-specific evidence addresses what actually happened. Under Article 78(4), executing providers must be able to demonstrate to clients, on request, that their orders were executed in accordance with that policy. Receiving a policy document alone does not resolve an order-level question.
Keep one further distinction intact: evidence that the sale was concluded is not, by itself, evidence that the fiat proceeds have settled. Separating those events helps your team distinguish an execution question from a settlement delay.
Conclusion
The decisive question is who concluded the agreement and what they undertook to do for your PSP. A receipt message and a counterparty name are useful evidence, not a complete explanation. Connect them to the agreement and the provider’s role to reconcile both the transaction and the responsibility behind it.
For requesting more information about how we can help reach out to us. We're here to help and answer any questions you may have.