PayIn ID returned looks like not an integer (Mangopay Sandbox)

[Dekari]

Hello,
I noticed for some days now that Mangopay Sandbox environment returns back pay in ID as "payin_m_01HQRDVC0GQV3EQCZ7FT057EQG" :

MangoPay\PayIn Object
(
    [Id] => payin_m_01HQRDVC0GQV3EQCZ7FT057EQG  <========
    [Tag] => Book ID:87522
    [CreationDate] => 1709143077
    [AuthorId] => 214952666
    [CreditedUserId] => 9902479
    [DebitedFunds] => MangoPay\Money Object

Same for KYC and Transfers

kyc_01HPW0PJ7TFJ3A91TV8M04N4QJ
xfer_m_01HPW1KJ87DHN33PE6D0MQ5EF9

I wonder. Is this something normal? Is this something that will be start happening also on mangopay production system?

thanks

[Mynymoys]

Hi,

Yes they are changing to ID of every transactions in few weeks in production.

You should get an email talking about the action around the 7th February 2024.

When do you need to be ready?
We will be implementing descriptive Object IDs:
•	Sandbox – 7th February 2024
•	Production – 29th February 2024

[Dekari]

Oh really?? that seems to be today!! Missed it totally.

Is there anywhere written on mangopay website is the only information source is the email?

[slaubi]

@Dekari you can find it partially mentioned in this announcement and completely described in the docs under Object IDs

additional information from that email:

Why?

Our aim is to leverage more advanced routing, sharding, and partitioning strategies while streamlining data lookup operations.

What you need to do?

Ensure that your system supports these more descriptive Object IDs to ensure potential disruptions.

No action is required on your part if your system handles Object IDs as strings.

When do you need to be ready?

We will be implementing descriptive Object IDs:

• Sandbox – 7th February 2024
• Production – 29th February 2024

We appreciate your understanding as we work to provide you with a more robust and efficient experience. If you have any questions or concerns, feel free to reach out to our support team at support@mangopay.com.

[Dekari]

Many thanks siaubi! To be fair, this doesn't seem to be implemented on production still :) system keeps sending back "normal integer pay-in ids etc"... but at least now my DB schema is prepared to host the new IDs! cheers Στις Πέμ 14 Μαρ 2024 στις 11:58 π.μ., ο/η slaubi ***@***.***> έγραψε:

…

@Dekari <https://github.com/Dekari> you can find it partially mentioned in this announcement <https://blog.mangopay.com/en/home/object-ids-payment-field-urls> and completely defined in the docs <https://mangopay.com/docs/api-basics/data-formats> under Object IDs additional information from that email: Why? Our aim is to leverage more advanced routing, sharding, and partitioning strategies while streamlining data lookup operations. What you need to do? Ensure that your system supports these more descriptive Object IDs to ensure potential disruptions. No action is required on your part if your system handles Object IDs as strings. When do you need to be ready? We will be implementing descriptive Object IDs: - Sandbox – 7th February 2024 - Production – 29th February 2024 We appreciate your understanding as we work to provide you with a more robust and efficient experience. If you have any questions or concerns, feel free to reach out to our support team at ***@***.*** ***@***.***> — Reply to this email directly, view it on GitHub <#633 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABOGX5AVKKKTK3MZPXB6WIDYYFYEBAVCNFSM6AAAAABD7LO2NOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJXGA3DKOBSHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[emnbdx]

Mail received just now
Production – 26th March 2024

[slaubi]

seems like the production date got pushed to 26th March 2024
https://email.mangopay.com/update-object-ids-now-include-more-descriptive-values

[emnbdx]

It's live in production environment ;)