Skip to content

Object IDs and Payment Field URLS

As we expand our partnership network and optimize our underlying architecture, we will be making use of Object ID strings and dynamic payment URLs. In this post, we highlight how you can ensure your integration has been set up according to our documentation.

string string

Object IDs are Strings

In our documentation, IDs of objects are Strings and should be handled as such. Some engineers may have looked deeper at our object IDs over the years and noticed they contain numbers or, in some cases, UUIDs. There might be a desire to assume they can be treated as such in code such as converting to a Number or UUID. However, as Mangopay optimizes our underlying architecture, we require the freedom to change the internal format of these IDs. These changes allow us to use more advanced routing, sharding, and partitioning strategies while minimizing data lookup operations. So, be careful. Starting in Sandbox, in early Q1 2024, you will start to see the contents of our IDs change from containing Numbers  or UUIDs to more verbose intelligent strings. We estimate the changes will make it to production in mid-February 2024.


Payment Form URLs

If your platform is using card payments, you are familiar with getting a URL from Mangopay to present to your users to collect card details or a URL to POST card details to. As we expand our partnership network, this URL will need to vary. It is important to ensure that your engineers are presenting the URL exactly as it comes from the API. Especially if you are using the Card Registration API, The CardRegistrationURL is dynamic and must not be hard coded. Everything from the host, path, and query parameters must be preserved as they are presented to you. We anticipate the first variations of this URL pattern in Q1 2024.

For the latest information, please visit our docs.