Thank you for your idea. Do you see this problem with the standard storefront as well or only with headless frontends?
Certainly, you do indeed need engineers to set up, test, and maybe build some front-end parts, but I wouldn't say it's like a constant re-implementation. If you choose a payment provider that already offers a variety of API endpoints, then you "only" need the frontend UI part in your headless setup and send all requested/needed data to that endpoint.
Also, agencies should work together so that everyone doesn't have to constantly reinvent themselves. For this team, frontends also collect solutions in the form of examples, packages, and documentation to help you complete projects faster.
You can send me a DM via Slack and I will send you a list of payment providers that should work well in a headless setup, especially for composable frontends.
Hello Richard,
Thank you for your idea. Do you see this problem with the standard storefront as well or only with headless frontends?
Certainly, you do indeed need engineers to set up, test, and maybe build some front-end parts, but I wouldn't say it's like a constant re-implementation. If you choose a payment provider that already offers a variety of API endpoints, then you "only" need the frontend UI part in your headless setup and send all requested/needed data to that endpoint.
Also, agencies should work together so that everyone doesn't have to constantly reinvent themselves. For this team, frontends also collect solutions in the form of examples, packages, and documentation to help you complete projects faster.
You can send me a DM via Slack and I will send you a list of payment providers that should work well in a headless setup, especially for composable frontends.
Best regards,
Björn.