Design to Duty: How we make architecture decisions at Adyen
From our server-side libraries, our plugins, and OpenAPI definitions - our team is committed to open source. Adyen Web has been developed internally for over a year now, and at this stage, we want to further our merchants’ experience by showing what goes on under the hood. In the end, opening our development to the community allows Adyen Web to be more secure, flexible, and transparent.
One of our goals is to make it easier for our merchants to keep track of releases and to see what we are preparing for the next versions of our web library. In addition, merchants can see the exact code that is running on their checkout page - which simplifies both the integration process as well as the debugging process in the event any issues arise.
Our developer community is a great source of feedback and ideas for our integrations. By opening up Adyen Web, we now have a new place to discuss feedback, new ideas, or bug fixes in the form of GitHub Issues. We are also open to Pull Requests for direct collaboration, allowing any developer to contribute to our source code.
By publishing our source code on GitHub, we can also leverage all their excellent tools for collaboration and continuous integration. We now have integrations that can run tests, look at code quality and security issues on every code change, and even publish a package to npm.
By submitting this form, you acknowledge that you have reviewed the terms of our Privacy Statement and consent to the use of data in accordance therewith.