More of a question than an issue, I'm probably missing something obvious but how can a carpooling operator send carpooling proofs if at least the truncated phone number is unavailable (as required in https://tech.covoiturage.beta.gouv.fr/operateurs/api-v2.html)
For instance, in the "unauthenticated booking via API flow", the MaaS operator would only send the User Object which contains id, first name and last name https://github.com/fabmob/standard-covoiturage/blob/main/standard-covoiturage_openapi.yaml. The booking can proceed, but how can the operator then send a proof of travel after the booking is "validated" ie trip finished ?
The same question holds for the "authenticated booking via API flow" or "booking via deep link" if the user is authenticated through MaaS Connect but the phone number or even truncated phone number is not shared by the identity provider to the carpooling operator.