Introducing Dev Corner: discover our new releases
At Mangopay, we believe the key to innovation also lies in empowering developers with the best tools and resources. To ensure that the developer experience remains at the heart of everything we do, we have introduced our new series of releases aimed at making development smoother and more efficient.
In this blog, we'll be showcasing each release, highlighting the new features and improvements we've made with the developer community in mind. From streamlined workflows to powerful new capabilities, our goal is to provide you with everything you need to succeed.
Say hello to our new and improved docs
Experience a more intuitive, efficient, and engaging way to access the information you need with features that include:
-
Improved search experience: Finding information has never been easier
-
Enhanced site performance: Enjoy lightning-fast page loads
-
Simplified navigation: Browse the new layout with ease.
-
Revamped UI: Check out our sleek new look, complete with dark mode
-
API reference: Focus on the endpoint you need, thanks to better organization.
-
Guides and how-to’s: Learn, test, and integrate features with step-by-step walkthroughs.
Industry standard for CardHolderName
The cardholder’s name can now be sent during card tokenization. This data point is then sent to card networks for use in risk analysis and returned to the Mangopay API's Card object. This update offers two key benefits:
- Improved performance with better card acceptance rates from the card schemes
- Potentially qualifying more transactions for SCA exemptions and reducing false positives, hence an improved customer experience.
Dev tip: keep your integration smooth and ensure you’re not hardcoding
As we grow our network of partners and optimize our underlying architecture, it's important for us to make sure that you integrate with the Mangopay API correctly. The ultimate scope is for you to keep getting the most out of the improvements we make.
For example:
1. 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 without any alterations.
2. If your platform uses bank wire pay-ins, it is crucial for you to dynamically retrieve bank account details such as IBAN, BIC, and Account Number.
We are making significant changes in the next few months, and these best practices will ensure that you benefit from these changes and that your payments remain smooth.
We're excited for you to check out these improvements firsthand and continue to enjoy a productive development experience. Contact us if you have any questions or remarks.